# Main data fields and structure

The data in Luna is organized around **four main object types: Objectives, Key Results, Launches,** and **Milestones.**

## Hierarchy

Objectives → Key Results → Launches → Milestones

* Objectives are qualitative goals that set the strategic direction.
* Key Results are quantitative goals that measure progress toward an Objective.
* Launches are initiatives that drive Key Results
* Milestones track progress within each launch

{% hint style="info" %}

* One launch can contribute to multiple Key Results, allowing for strategic flexibility.
* Objectives, Key Results, and Launches can be created and used independently. 
* The data below can either be entered directly in Luna, synced from integrations, or enriched by AI.
* You don’t need to adopt the OKR framework to use these fields. If you simply want to track KPIs, you can use the Key Result fields on their own.
  {% endhint %}

## **List of key fields** 

### **Objective level**

<table><thead><tr><th width="180.41015625">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Title of the strategic objective</td></tr><tr><td>Contributors</td><td>Users or Teams working toward this objective</td></tr><tr><td>Date</td><td>Timeline for achieving the objective</td></tr></tbody></table>

### **KR level**

<table><thead><tr><th width="179.90234375">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Specific, measurable outcome</td></tr><tr><td>Target date</td><td>When this Key Result should be achieved</td></tr><tr><td>KR score</td><td>Progress score toward the target = <code>((actual - (starting)) / (target - (starting))) * 100</code></td></tr><tr><td>Status</td><td>Current health: On track, At risk, Off track</td></tr><tr><td>Target value</td><td>The goal you're aiming to achieve</td></tr><tr><td>Start value</td><td>Baseline measurement</td></tr><tr><td>Actual value</td><td>Current measured progress</td></tr><tr><td>Owner</td><td>User or Team responsible for this Key Result</td></tr><tr><td>Contributors</td><td>Users or Teams supporting this Key Result</td></tr><tr><td>Linked Launches</td><td>Initiatives driving progress on this Key Result</td></tr><tr><td>External dashboard link</td><td>Link to external tool to track progress</td></tr></tbody></table>

### **Launch level**

<table><thead><tr><th width="180.1875">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Title</td><td>Title of the initiative you want to bring visibility around</td></tr><tr><td>Description </td><td>A high-level description of the initiative to keep everyone informed about its key elements, such as the problem, solution, and potential impact</td></tr><tr><td>Owner</td><td>Point of contact and main driver of the initiative</td></tr><tr><td>Participants</td><td>Users or Teams who are actively collaborating on the initiative or need to stay informed</td></tr><tr><td>Status</td><td><p>- Indicator of the overall health of the initiative: On track, Possible delays, At risk, Paused</p><p>- E.g., changing a status to "At risk" usually triggers a set of email/Slack notifications to the appropriate stakeholders, depending on the company </p></td></tr><tr><td>Stage</td><td><p>- High-level indicator of the phase of the initiative in its lifecycle </p><p>- Examples of stages based on different portions of the lifecycle: </p><p>1- For the GTM: Kickoff, Alpha, Beta, GA</p><p>2- for the entire lifecycle: To be prioritized, Not started, Discovery, Scoping, Implementation, Testing, Launch, Post-launch analysis</p></td></tr><tr><td>Launch and start dates</td><td>Planned and actual start and launch dates of the initiative</td></tr><tr><td>Priority </td><td>Indication of the priority level for your list of initiatives: High, Medium, Low</td></tr><tr><td>Progress score</td><td>Indicator of milestone completion ("Completed milestones" / "Total milestones")</td></tr><tr><td>Link to external source</td><td>Link to external tool (e.g., Jira issue + child issues progress from Jira)</td></tr><tr><td>Labels</td><td><p>- Criteria and attributes for categorizing and organizing your initiatives</p><p>- E.g., these can include metrics (e.g., "Conversion rate"), significant meetings (e.g., "Board meeting"), release names, etc.  </p></td></tr><tr><td>Milestones</td><td>Deliverables and checkpoints within the launch, with owners, approvers, and target dates</td></tr><tr><td>Success metrics</td><td>Outcome-focused measurements to track launch impact, with confidence levels, pre/post shipping values, and link to Key Results for strategic alignment</td></tr><tr><td>Resources</td><td>Documentation, links, and reference materials associated with the launch</td></tr><tr><td>Updates</td><td>Progress updates, status changes, and upcoming priorities</td></tr><tr><td>Risks</td><td>Identified potential blockers, issues, or concerns that could impact launch success</td></tr><tr><td>Decisions</td><td>Key decisions made during the launch process with context and rationale</td></tr></tbody></table>

### **Milestone level**

<table><thead><tr><th width="179.8203125">Data field</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td><p>- Title of the milestone providing clear insights into the work progress</p><p><a href="https://withluna.ai/blog/why-we-focus-on-milestones-not-on-tasks">At Luna, why we focus on milestones, not on tasks - blog post</a></p></td></tr><tr><td>Stage</td><td><p>- High-level indicator of the phase of the milestone in its lifecycle</p><p>- Examples of stages: </p><p>1- Basic level: Not started, In progress, In review, Completed</p><p>2- Can reflect the linked Jira epic status within the list </p></td></tr><tr><td>Target and start dates</td><td>Planned and actual start and target dates of the milestone</td></tr><tr><td>Owner</td><td>Point of contact and main driver of the milestone</td></tr><tr><td>Approvers</td><td>Participants who will need to approve a milestone in due time</td></tr><tr><td>Details</td><td>Behind-the-scenes view of daily work progress in Jira or other tools </td></tr><tr><td>Link to external source</td><td>Link to external tool (e.g., Jira issue + child issues progress from Jira)</td></tr></tbody></table>