Skip to content
experience

Our Q3 roadmap had 9 items. We shipped 2. A calm post-mortem

September 21, 2026 · 3 min read

We are a 30 person health tech startup in Stockholm. In June I presented a Q3 roadmap with 9 items. Leadership nodded. Engineering nodded slightly less. On 30 September we had shipped 2. Here is what happened, without drama, because I think it is useful and because I promised my team I would write it down.

The 9 items, and what happened to them

  1. Patient reminders v2: shipped.
  2. Clinic dashboard export: shipped.
  3. New clinic onboarding: 60% done, paused.
  4. Integration with a second journal system: blocked, waiting for the vendor's API access since July.
  5. Medical device documentation update: not a feature, but it took 6 weeks of two engineers. Part of our software is regulated as a medical device, so a change in intended use means documentation. Nobody had put it on the roadmap, because nobody thinks of paperwork as work.
  6. Self-serve billing: deprioritised in August for a sales promise.
  7. The sales promise: a custom report for one large region. Not on the roadmap. Shipped, actually. So we shipped 3 things, but only 2 of the 9.
  8. AI-assisted triage notes: paused for a legal review of how the EU AI Act applies to us.
  9. Performance work: half done, the way performance work always is.

What I would do differently

  • Plan for 60% capacity. We planned for 90%. Support, on-call, sick children, vacations (it is Sweden, July does not exist) and regulatory work ate the rest.
  • Put compliance on the roadmap. If it takes engineers, it is roadmap work. Hiding it makes the roadmap a lie and makes the engineers look slow.
  • Now, Next, Later instead of quarters. Quarters suggest dates. Dates become promises. Promises become sales decks.
  • One person says no to sales. Me. I did not, in August. I should have, or at least made the trade explicit in writing: "the custom report means self-serve billing moves to Q4". I said it in a meeting. I should have written it down.
  • External dependencies get a give-up date. If the vendor API is not there by a set date, we stop waiting and replan.

What went right

The two things we shipped are used by clinics every day. The team did not burn out. Nobody worked weekends. That is lagom, and I will take it over 9 half-shipped features.

Roadmaps are hypotheses, not promises. I believe it more after this quarter. Happy to be proven wrong!

Get the best of #roadmap_roulette weekly

One email each Monday with the most useful posts. No spam; unsubscribe in one click.

Comments

13

Sign in to join the conversation.

Sign in to comment
Rachel Kim@rachelkim#2 in Roadmap Roulette
"Nobody thinks of paperwork as work" is the most important sentence here. I started putting compliance work on the roadmap in its own color so leadership can see what it costs. It changed the conversation.
0 net votes
Elin Sjöberg@elin_pm#1 in Roadmap Roulette
A colour of its own is a lovely idea. Making the invisible work visible without making it a complaint. Thank you Rachel
1 net votes
Karl Lindqvist@kernel_karl#4 in Roadmap Roulette
"Roadmaps are hypotheses, not promises." That is the fourth post where you say it. I have started a counter.
1 net votes
Elin Sjöberg@elin_pm#1 in Roadmap Roulette
Karl, my hypothesis is that I will keep saying it. So far the data supports it.
0 net votes
Giulia Bellandi@giulia_designs#5 in Roadmap Roulette
Elin this is so you! Calm, honest, zero drama ✨ and "July does not exist" made me laugh, in Italy it is August that does not exist ahah
1 net votes
Wolfgang Engel@dsgvo_wolf#5 in Roadmap Roulette
I would like to point out that the medical device documentation exists because software in healthcare can harm patients. Six weeks of paperwork is a cost, yes. It is not a mistake.
1 net votes
Elin Sjöberg@elin_pm#1 in Roadmap Roulette
I agree it is not a mistake, Wolfgang. My point is only that it is work and should be planned as work. Where we disagree is how much of it a reminder feature needs. 🙂
1 net votes
Wolfgang Engel@dsgvo_wolf#5 in Roadmap Roulette
That is a fair distinction. We can disagree on the amount.
1 net votes
Alasdair Reid@onprem_or_die#7 in Roadmap Roulette
nine features for a 30 person company. bet half of them were waiting on some cloud vendor
1 net votes
Jo Brennan@jo_ships1 rep in Roadmap Roulette
team of 1 here and i also ship 2 of 9. comforting to know it scales
2 net votes
Divya Ramanathan@divya_ramanathan#7 in Roadmap Roulette
The 60% capacity rule is the one I fight for every planning cycle. Leadership hears "my team is slow". What they should hear is "my team is honest". Very well written, Elin.
0 net votes
Deniz Yıldırım@deniz_cto#7 in Roadmap Roulette
Same, regulation ate our Q2. Different law, same pain 😅 the give-up date for external dependencies is gold
3 net votes
Hiba Osman@hiba_dxb1 rep in Roadmap Roulette
Saving this for my next planning meeting. "Promises become sales decks", khalas, that is the whole problem in one line
0 net votes