Strategic Comms & Roadmapping

Overview

Most roadmaps fail before anyone reads them. Not because the strategy is wrong, but because the story is missing. A list of features on a timeline does not unlock decisions. It creates more questions: why this order, what are we saying no to, how does this connect to what leadership cares about.

I help product leaders build roadmaps and vision documents that actually land. The kind where an exec reads the first paragraph and understands why this matters, where engineering sees a clear throughline from current work to future state, and where the board stops asking "but what's the plan?"

This is where my theater background quietly pays off. Every story has structure, and the right structure unlocks decisions. I've built roadmaps and vision docs for teams at Kaiser Permanente, Rise8, and multiple startups, always with the same principle: tell the story of why, not just what.

Who this is for

This works well when you're:

• A product leader preparing for a board meeting, exec review, or funding conversation and the current deck isn't landing
• A director who inherited a roadmap that's just a backlog in disguise and needs to reframe it around outcomes
• A team navigating a pivot or reorg and needing a clear story to rally stakeholders
• A founder trying to communicate product vision to investors, advisors, or a new hire class
• A product org that keeps getting "what's the strategy?" questions despite having a roadmap

If your team needs someone to own the roadmap long-term, Fractional Product Leadership or Fractional Head of Product is a better fit. This engagement is about building the narrative foundation.

What you get

1. Strategy narrative document. A written artifact that tells the story of where you're going, why, and what you're choosing not to do. Not a slide deck, a document that can stand on its own.
2. Outcome-oriented roadmap. A roadmap organized around outcomes and milestones rather than features and dates. Designed for the audience that matters most: execs, board, engineering, or cross-functional partners.
3. Stakeholder alignment session. A facilitated working session where we pressure-test the narrative, surface disagreements, and leave with a shared understanding of the plan.

Typical engagement

• Duration: 2-4 weeks
• Commitment: 8-15 hours total (interviews, drafting, facilitation)
• Format: Remote, with 2-3 working sessions and async review cycles