- Core
- 60 min
- 6 min read
After this lesson you can
- Write all seven ORBITAL elements for a product.
- Connect an objective to measurable, time-bound indicators.
- Link activities to your epic roadmap.
- Tell a measured result from a statement of intent.
Read these first
ORBITAL is layer 2 of the catalogue framework. It turns the product idea into an organised objective and a resource plan. It makes visible the outcome you want, the money and people you need, how you will measure success, the work, and the practical arrangements.
The name is a list of seven letters. Each letter is a short section.
Why it matters
Many plans fail between “we have a product” (Master) and “we shipped something” (ANDROID). The gap is: why, with what, for how much, measured how, in what order. ORBITAL is that gap written down. When someone asks “why are we doing this?”, you point to Objective. When someone asks “how do we know it worked?”, you point to Indicators.
Key ideas
- Seven elements, all required. A gap in one makes the plan weak.
- Objective in one outcome sentence. If it is a list of tasks, it is not an objective.
- Indicators are numbers with a date. Observable and time-bound.
- Evidence over intention. “We will improve returns” is intention. “Return status visible for 90 percent of cups by 30 June” is an indicator.
- Activities link to epics. Your epic roadmap is the source.
The seven elements, explained
| Element | What to document | TrailMug example (fictional) |
|---|---|---|
| O Objective | The outcome, scope and intended result | A commuter always knows the status of her deposit. Scope: Dublin cafés, mobile app, refunds only. |
| R Resources | People, skills, tools, systems, data, vendors | One product manager, two engineers (part-time), a payments provider, the returns service, an email sender |
| B Budget | Costs, funding source, assumptions, timing, owner | 18,000 euro over six months. Funded by the pilot grant. Assumes 2,000 active cups. Owner: finance lead. |
| I Indicators | Targets, baselines, how measured, how often reported | Refund status visible for 90 percent of cups by 2027-06-30. Baseline today: 0. Measured from the returns database each Monday. |
| T Transport | How people, equipment, information and deliverables move | Cups move from café to wash site by weekly pickup. Return data moves from tablet to returns service by API. |
| A Activities | Workstreams, milestones, dependencies, owners | Epic 1 returns status (Leo). Milestone 1.1 status field live by 2027-04-15. Depends on payments provider approval. |
| L Logistics | Access, scheduling, buying, facilities, coordination | Tablets bought for 12 cafés; weekly café check-in call; read access to the provider dashboard for finance |
Use this table shape for your own page. One row can have several lines if needed.
Steps
- Write the objective first. One sentence, one outcome, one measure you could name.
- List resources from the Master layer. Use the same names.
- Budget with assumptions. Write the assumption beside every number.
- Write two or three indicators. Each has a number, a date, a baseline and a source.
- Describe transport. Include physical items and information.
- Copy activities from the roadmap. Keep milestone dates and owners.
- List logistics that could block work: access, buying, scheduling.
- Link back to the Master page and forward to ANDROID.
The measurement principle
Indicators should be observable and time-bound wherever possible. Prefer evidence of completed outputs and measured outcomes to statements of intention.
| Weak | Strong |
|---|---|
| Improve customer experience | 80 percent of returns confirmed within one hour by 2027-06-30 |
| Be more reliable | Refund job succeeds 99 percent of days, measured daily from the returns log |
| Launch the pilot | Twelve cafés live, each with a signed check-in, by 2027-05-31 |
Working with AI agents
- May: check that each indicator has a number, a date, a baseline and a source. Compare resource names with the Master layer. Calculate totals you give them.
- May not: invent a budget, set a target, or decide the objective. Numbers without assumptions are fiction.
- A safe brief: “For each indicator in this table, say whether it has a number, a date, a baseline and a source. Report missing parts. Do not suggest values.”
Common mistakes
- An objective that is a task list.
- Indicators with no date or baseline.
- A budget without assumptions.
- Forgetting transport. Information and goods both move.
- Logistics left until the week of launch.
- Resource names that do not match the Master layer.
Practice
- Write your objective in one sentence. Check it names an outcome, not a task.
- Rewrite two weak indicators as strong ones.
- Add the assumption to every number in your budget.
- List three logistics items that could stop you in week one.
Checklist
- All seven elements are filled.
- The objective is one outcome with a measure.
- Every indicator has a number, date, baseline and source.
- Budget numbers carry assumptions and an owner.
- Activities match the epic roadmap.
- Resources match the Master layer.
The 2030 Product Development Manager lens
- You decide: the objective, the targets, the budget and the order of activities.
- You delegate to agents: consistency checks, arithmetic, drafting the indicator table from numbers you provide, and tracking activity status from the tracker.
- A sample brief: “Read the milestone list and the activity table. List any milestone missing from the table, and any table row with no milestone. Do not change dates.”
- You verify by: recalculating one budget line and opening the source of one indicator.
- Disciplines involved: strategy, finance, operations, procurement and delivery.
- On the agent ladder: delegate the checking and the tracking. Govern the targets: only a person sets them.
Further learning
Go deeper in the frameworks track: objective, resources and budget, indicators, transport, activities and logistics, ORBITAL in full for TrailMug and from ORBITAL to milestones and issues. Next: the ANDROID layer. Review roadmap standard and the epic roadmap template for the activities.
Go deeper
Further learning
Free or low-cost material from other publishers. We opened every link; check the cost label before you start.
Atlassian
How to write SMART goals (with examples) (opens the publisher's site in a new tab)
- Free
- Article
- Beginner
A short article that explains the five SMART tests (specific, measurable, achievable, relevant, time-bound) and works through an example. Use it when you rewrite a vague task into one that an agent or a colleague can finish and you can check.
Atlassian
Product Roadmap Guide: What is it & How to Create One (opens the publisher's site in a new tab)
- Free
- Article
- Beginner
A step-by-step guide to what a product roadmap is, the common formats and the questions it must answer. Read it before you write your own roadmap so you know the standard shapes and can explain why you chose one.
Atlassian
Project dependencies (opens the publisher's site in a new tab)
- Free
- Article
- Intermediate
Explains the kinds of dependency between pieces of work and how to track them. Read it before you order your epics.
Silicon Valley Product Group
SVPG: The alternative to roadmaps (opens the publisher's site in a new tab)
- Free
- Article
- Intermediate
A short essay that argues for stating problems to solve rather than lists of features. It supports writing epics as changed situations. A good second opinion after the Atlassian guide.
Google
Google SRE Book: Service level objectives (opens the publisher's site in a new tab)
- Free
- Book
- Intermediate
Defines SLIs, SLOs and SLAs and shows how to choose them. It gives the vocabulary for the service level sheet in the capstone. Read the first sections for the definitions.
GitLab
Milestones (opens the publisher's site in a new tab)
- Free
- Docs
- Beginner
Explains GitLab milestones: dated goals that group issues and merge requests, with progress tracking. Milestones are how you give dates to a plan on the free plan.



