{"id":2605,"date":"2023-11-09T12:00:31","date_gmt":"2023-11-09T12:00:31","guid":{"rendered":"https:\/\/itamargilad.com\/?p=2605"},"modified":"2023-11-21T10:53:46","modified_gmt":"2023-11-21T10:53:46","slug":"outcome-roadmaps","status":"publish","type":"post","link":"https:\/\/itamargilad.com\/outcome-roadmaps\/","title":{"rendered":"Planning With Outcome Roadmaps"},"content":{"rendered":"\n

As I\u2019m writing this, the dreaded yearly planning cycle is just around the corner and the debate over roadmaps is surfacing once more. On one hand it\u2019s clear that classic roadmaps that show releases on a timeline create both high planning overhead and high waste<\/a>. On the other hand, attempts to construct roadmaps around outcomes and themes (often with no timeline) may leave the organization wanting. Classic roadmaps come with a big promise: they allow you to plan resources, track progress, and coordinate launches. While they don\u2019t really deliver, the desire to have these things isn\u2019t likely to go away.<\/p>\n\n\n\n

So what if we try to combine both worlds \u2014 an outcomes roadmap that shows the real <\/em>work that goes into achieving the goals, on a timeline. Such a roadmap can create effectively communicate the things most roadmaps omit, while stressing the point that the plan has to be adapted as new information emerges.\u00a0<\/p>\n\n\n\n

The elements of this roadmap are: <\/p>\n\n\n\n