Main data fields and structure
Last updated
Last updated
Luna is a platform that helps product teams ship faster and at a lower cost. We achieve this by focusing on:
Proactive project visibility for cross-functional and leadership teams, throughout the lifecycle of a project:
As a VP of Product or Marketing, Luna will keep you aligned with your team and informed about project progress, potential issues, key changes, and their reasons.
As a PM or PMM, you will spend significantly less time on reporting to keep stakeholders informed, allowing you to focus more on problem-solving.
Centralized cross-functional collaboration:
As a PM or PMM, you will be able to run cross-functional workflows in Luna (e.g., GTM, collaboration during the product lifecycle) without getting lost in a stream of spreadsheets and slides.
As a VP of Product or Marketing, you will be able to participate in the launch process at the right time, thus de-risking the project without needing constant reporting.
To achieve the above, leadership and cross-functional stakeholders need to speak a common language. This common language is often lacking in our organizations because teams tend to work in silos, using their respective task management and communication tools (e.g., Jira and Slack). The detailed nature of tasks makes it difficult for stakeholders to understand key progress and risks, and to collaborate effectively.
Luna creates this common language by establishing an uncluttered project-level data layer, which drives visibility and cross-functional collaboration. The data in Luna is organized around two main object types: launches and milestones.
Title
Title of the initiative you want to bring visibility around.
Description
A high-level description of the initiative to keep everyone informed about its key elements, such as the problem, solution, and potential impact.
Owner
Point of contact and main driver of the initiative.
Participants
Users who are actively collaborating on the initiative or need to stay informed.
Status
- Indicator of the overall health of the initiative: On track, Possible delays, At risk, Paused.
- Eg. Changing a status to "At risk" usually triggers a set of email/Slack notifications to the appropriate stakeholders, depending on the company.
Stage
- High-level indicator of the phase of the initiative in its lifecycle.
- Examples of stages based on different portions of the lifecycle:
1- For the GTM: Kickoff, Alpha, Beta, GA.
2- for the entire lifecycle: To be prioritized, Not started, Discovery, Scoping, Implementation, Testing, Launch, Post-launch analysis.
Launch and start dates
Planned and actual start and launch dates of the initiative.
Priority
Indication of the priority level for your list of initiatives: High, Medium, Low.
Progress score
Indicator of milestone completion ("Completed milestones" / "Total milestones").
Labels
- Criteria and attributes for categorizing and organizing your initiatives
- Eg. These can include metrics (e.g., "Conversion rate"), significant meetings (e.g., "Board meeting"), release names, etc.
Name
- Title of the milestone providing clear insights into the work progress.
Stage
- High-level indicator of the phase of the milestone in its lifecycle.
- Examples of stages:
1- Basic level: Not started, In progress, In review, Completed
2- Can reflect the linked Jira epic status within the list
Target and start dates
Planned and actual start and target dates of the milestone.
Owner
Point of contact and main driver of the milestone.
Approvers
Participants who will need to approve a milestone in due time.
Details
Behind-the-scenes view of daily work progress in Jira or other tools.
