Startup ops with milestones and cross-department rollups

The roadmap and the work that delivers it live apart

A founder or COO running a small leadership team has a strategic roadmap — the milestones the company is rowing toward this quarter. But the roadmap sits in one tool, the engineering work that delivers each milestone sits in Linear, the weekly meeting where progress gets reviewed sits in a doc, and the leadership channel where everyone expects an update sits in Teams. Keeping them aligned is a manual job that lands on someone every week.

The pieces are connected in principle. A roadmap item becomes a to-do; a cross-team to-do becomes engineering work; a milestone has a review date; progress on milestones is what the weekly rollup reports. Because each lives in its own tool, the connections get maintained by hand — copy a to-do into Linear, add a calendar invite for the review, write the Monday update from memory.

One model behind the roadmap, the meeting, and the board

The workspace covers four areas that share one underlying model. A roadmap page is where the COO plans strategic items — each with an area, a priority, and a state. From a roadmap item you spin off the things that actually move it: a headline, a to-do, an obstacle or opportunity, a quarterly goal. A weekly meeting page runs the leadership meeting itself — start it, triage the headlines each area submitted, review obstacles and opportunities, capture new to-dos, archive it when done.

The personal board is the home page: each team member sees their own to-dos, headlines, and stats. An overview hub adds a weekly dashboard of to-do progress, a calendar-and-deadline view, and KPI tracking — the numbers each area logs every week. Members, areas, roadmap items, to-dos, and KPIs are all first-class records, so the same data shows up in every view without anyone re-entering it.

From a roadmap item to Linear, the calendar, and Teams

1. Plan on the roadmap. The COO adds a strategic item — its area, priority, and target — then spins off the work that moves it: a to-do, a headline, an obstacle or opportunity, a quarterly goal. The plan and the work stay one step apart.
2. Cross-team to-dos become Linear issues. When a to-do is handed to engineering, the workspace mirrors it into Linear as an issue, so the eng team tracks it where they already work — still linked to the meeting-driven plan.
3. A milestone entering review lands on the calendar. When a roadmap item moves into its review state, the workspace drops a review event onto the team’s Outlook Calendar, so the deadline appears where everyone already looks.
4. The weekly rollup posts to Teams. A weekly rollup of roadmap progress, grouped by area, goes to the leadership Teams channel. People who weren’t in the meeting see where each area stands without booking a sync.
5. The meeting closes the loop. In the weekly meeting the team triages headlines, works through obstacles and opportunities, and captures new to-dos; closed items move to the archive and open ones carry into next week.

Areas, channel, calendar, and what counts as “in review”

• Team areas and members — define the areas your team is split into (product, growth, ops…) and who owns each. Areas drive the headline rows and how the Teams rollup groups progress.
• Rollup channel — pick the leadership Teams team and channel the weekly milestone rollup posts to.
• Review calendar — choose which team Outlook Calendar milestone-review events land on.
• Roadmap states — define the states a roadmap item moves through, including which one counts as “in review” — the point a calendar event gets created.
• KPI list — the metrics the team logs each week, each with an owner and a target.
• Meeting cadence and participants — weekly is the default; set who sits in the leadership meeting and how often it runs.

One plan, mirrored where each team already works

What holds this together is that the roadmap is the single source — the to-dos, the Linear issues, the calendar events, and the Teams rollup are projections of it, not separate copies someone keeps in sync. The shape of a leadership team’s plan is stable: areas, milestones, weekly to-dos, a recurring meeting. Because the workspace models those directly, changing how it behaves is a matter of changing the description, not rebuilding — point the rollup at a different Teams channel, pick a different Outlook calendar for reviews, redefine the areas your team is split into, or change which roadmap state opens a review event. The plan stays in one place; each team sees the part they care about in the tool they already live in.