One milestone, many projects.
Linear’s posting for Product Manager asks for discovery presented with conviction and rigor, messaging that resonates with users, and a sales team that can win with it. This is one finding taken through all three. I built it in one day from Linear’s public pages, with AI agents doing the reading.
The same initiative, twice
A made-up launch with four projects. The numbers on the right match the prototype.
Today
Each project makes its own copy. The copies drift.
“Are we ready for beta?” Open four projects, or keep a spreadsheet.
Proposed
One milestone on the initiative. Each project keeps its own slice.
“Are we ready for beta?” One page. It also says what beta handed to launch.
The finding
The user is the person leading a launch that spans several projects and has a date that matters.
I do that job now, for ten vendor teams with a date that does not move. So I read Linear’s docs the way I would use the product.
What I cannot see from outside: how many customers repeat a milestone name across projects. Linear can count that in an afternoon. It is the first thing I would ask for.
- Linear’s docs say a milestone cannot be shared.The milestones FAQ says it has to be recreated in each project. Project milestones, FAQ
- The docs describe a workaround.On an initiative you can filter projects by the text of their milestone names. That works while every project spells it the same way. Milestones and Initiatives
- A customer story shows the review living in a spreadsheet.Sierra’s Monday product meeting runs from a sheet that the API refills with milestones, statuses and next steps. Linear tells it as a strength of its API, and it is. It also shows where the cross-project view sits. Sierra
- Moves between milestones are recorded, and never added up.The public API records the milestone an issue moved from and to. I found no page in the docs that sums those moves for a milestone. API schema
What Linear already has
- Milestones with progress, on every plan.Each has a date and a completion percentage, and shows on the timeline.
- Initiatives that roll projects up.The initiative timeline already shows each project’s current milestone.
- A record of every move.For cycles, the API even keeps the list of what was unfinished at close.
- Health that goes grey when nobody has reported.It does not stay green. The same rule belongs on a milestone.
The proposal
- Define a milestone once, on an initiative.A name and a date. Any project in the initiative can share it.
- Each project keeps its slice.Its own issues, progress and lead. Inside the project it is an ordinary milestone, so guests who cannot see initiatives still see it.
- One line on the initiative timeline.Move the date once and every project follows.
- Carried over, shown.Each slice shows what arrived from the last milestone and what moved on to the next.
- Merge what exists.Milestones with the same name become one shared milestone. Nobody starts over.
What I would cut
- A new time box.Linear has cycles for rhythm and milestones for outcomes. A “program increment” would be a third thing with an invented name.
- Automatic rollover at the date.A cycle is a rhythm, so it rolls. A milestone is a promise, so a person decides what moves.
- A locked baseline.Linear keeps scope honest by showing change, not by freezing it.
- Capacity across teams.A real need, and a different problem.
- Sign-off at the date.An approval step is busy work until a customer shows me otherwise.
What would change this
- If few initiatives repeat milestone names,the problem is smaller than the FAQ suggests, and I would stop.
- If Linear already has this under way,I join that work instead of starting it.
- If leads want carry-over across team cycles more than across milestones,that view goes first. It reads the same record.
- If customers model phases as sub-initiatives,the shared date belongs there, and this needs no new object at all.
How I would take it from here
Four steps, each with what ships, who it involves and how I will know. The Linear Method asks for projects that one to three people finish in one to three weeks. I cut the first version with that in mind. Whether it fits is the engineers’ call.
Check the finding
A count of initiatives where projects repeat a milestone name, and notes from calls with the leads who run them.
DataCustomer experienceSales
How I will know. I can name five customers who keep this view by hand, and say what is in it.
Build the smallest version
A shared milestone with a name, a date and a slice per project, plus the carried-over record. Linear’s own launches use it first.
A designerOne or two engineers
How I will know. Linear’s next launch is reviewed from the milestone, not from a document.
Private beta
The feature goes to the customers from the first step. I sit in on one milestone review with each.
Customer experienceBeta customers
How I will know. One lead retires the spreadsheet, and tells me what it had that the page lacks.
Launch
The changelog entry, the docs page and the page for sales, all saying the same thing.
MarketingSalesDocs
How I will know. Sales uses the page in a live deal and reports the buyer’s next question.
The announcement
The posting asks for messaging that resonates with users. This is the draft I would bring.
Shared milestones
A launch has one date, even when five projects are working toward it. You can now define a milestone once on an initiative and share it with the projects that contribute.
- One name, one date. Change it once and every project follows.
- Each project keeps its own slice. Its own issues, its own progress.
- See what carried over. When unfinished work moves to the next milestone, both milestones show it, project by project.
Already have the same milestone in several projects? Merge them into a shared one from the initiative.
Why it reads this way: it opens with the user’s situation, names one thing, and uses the word Linear already uses. The Method says not to invent terms.
The page for sales
The posting asks for a sales team that can win with customers. This is the page I would hand them.
Shared milestones, in a deal
When it comes up. A buyer moving from Jira asks how a release across several teams is planned in Linear.
Say
- Define the milestone once. Every project on the initiative shares the name and the date.
- Each team keeps its own slice and its own lead.
- When work moves to the next milestone, Linear shows what moved. Nobody keeps that list by hand.
Do not say
- That it is program increment planning. It is a milestone.
- That it plans capacity or locks a baseline. It does neither.
Questions it answers
- “Can we see one date across teams?”Yes, as one line on the initiative timeline.
- “What happens to unfinished work?”It stays until someone moves it. The move is recorded and shown.
- “Can contractors see it?”In their own project, yes. Initiatives stay hidden from guests, as they are today.
Proof
- None yet. The private beta produces the first customer quote.
What I would watch
Linear says it does not use OKRs or run A/B tests. So there is no target here and no experiment.
Three things to watch, with customers telling me why. I can see no baseline for any of them from outside. How we hire at Linear
- Shared milestones on initiatives with three or more projects.Use where the problem is, not use overall.
- Date changes made once.Each one is several edits nobody had to make.
- Leads who say the spreadsheet is gone.The only one of the three that is the outcome.