A room for Program managers

Program Managers' Roundtable

Help many related projects move toward one outcome without hiding local needs.

Why this might help

When you're managing several related projects at once, it's easy to lose the thread. Each team has its own rhythm, its own blockers, and its own way of talking about progress. A program story map helps you see all those projects together — not to flatten them into one plan, but to find where they connect and where they need room to breathe. Think of it like a neighborhood map: every house is different, but they all share the same streets. This room gives you practical ways to use that map with your team.

Does this feel familiar?

  • Two project leads keep solving the same problem separately because nobody told them the other team was working on it.
  • Your weekly status update sounds fine on paper, but you privately know three teams are quietly blocked on the same dependency.
  • A local team changes their timeline for a good reason, and suddenly three other projects are surprised by the ripple.
  • You're asked how all the projects add up to one outcome, and you realize you don't have a clear answer ready.

Try this together

  1. Start with the shared outcome first — write it in one plain sentence before you touch any project details.
  2. Ask each project lead to name their one biggest local constraint; put those on the map before you draw any connections.
  3. Look for the two or three places where projects hand something off to each other, and mark those spots clearly.
  4. Hold a short 'map check' every few weeks — not to review every task, but just to ask whether the connections still make sense.
  5. When a local team needs to change course, update the map together so everyone sees the shift at the same time.

Program Story Map

  1. Write the shared program outcome at the top of a blank page or board — one sentence, plain language, no jargon.
  2. List each project underneath it, and next to each one write what it contributes to that outcome in your own words.
  3. Draw a line between any two projects that depend on each other, and label the line with what actually moves between them — a decision, a deliverable, a piece of information.
  4. Add a small note beside each project showing its biggest local constraint right now, even if it feels minor.
  5. Step back and read the whole map out loud with your team — if anything sounds confusing or missing, fix it before you share it wider.

Questions worth talking about

If one of our projects had to pause for a month, which other projects would feel it first — and do those teams know that?

Are we treating every project the same way because it's easier, or because they actually need the same things?

When we say we're all working toward the same outcome, can we each point to the same sentence on the map?

A few common questions

How is a program story map different from a regular project plan?

A project plan tracks tasks inside one project. A program story map shows how several projects relate to each other and to a shared goal. It's less about what's due on Friday and more about why these projects exist together. You're looking at the neighborhood, not just one house.

What do we do when a local team's needs conflict with the shared outcome?

Don't hide it — put the tension on the map. Name the conflict clearly so everyone can see it. Sometimes the shared outcome needs adjusting. Sometimes the local need can be met a different way. Either way, making it visible is the first step. Pretending it isn't there usually makes things worse later.

Can Tindlo help us keep this map connected to actual work?

Yes, in a practical way. Tindlo lets you organize work items across teams and projects on a shared time axis, so you can see how different workstreams sit alongside each other in Day or Week view. It won't build the story map for you, but it can help your team stay oriented once the map exists.

Keep the story close to the schedule

A date makes more sense when you can also see the reason, the owner, and the work around it. Tindlo brings those pieces together when a calendar alone isn't enough.

See how Tindlo works →

Where would you like to go next?

Engineering Leadership ExchangeEngineering leadersProduct Operations CircleProduct operations teamsProject Managers' WorkshopProject managers