VR Games

WHEN VISION MEETS REALITY

"We have a great idea, but product delivery is so slow"

Many start-ups take a top-down approach to building their product. They focus on the idea, a high-level goals, and a vision for the next few years. Whilst often well-crafted by the founders and successfully validated with stakeholders, the roadmap is usually hard to assimilate by those who need it most:

  • Emerging middle-management, program and project management roles need actionable units of work to plan ahead and track;

  • Engineering and QA teams need details of the Product Roadmap for execution; and

  • External vendor teams lacking the integration of internal teams

The result is loss of investor confidence and delay to development. This usually means a delay in, for example, Series B funding (or a need for a bridge round of finding).

ACTIONABLE PRODUCT ROADMAPS

"Investors can see how the roadmap will be achieved"

Your roadmap needs to be actionable. This means it:​

  • Supports the owner’s vision

  • Is clear to all

  • Has sufficient detail needed to develop software

  • Breaks down strategic goals into actionable steps

  • Provides unambiguous and value-driven priority​

The roadmap has typically one Product Owner, but many active contributors from your engineering teams. Being actionable means being useful to those not only developing your solution, but also those monitoring and guiding that development. You will know where you are, where you need to be, and how much effort it will take to get there.


Investors like this approach: by breaking down the vision into actionable (and quantifiable) steps, you not only move faster, but also more predictably.

Actionable Product Roadmaps.jpg

OUR APPROACH

  1. Workshop with owner of the strategic product roadmap
    - Elaborate overall vision and high-level goals
    - Identify product areas and corresponding stakeholders/owner 

  2. Per product area: workshop with area owner/stakeholder
    - Elaborate overall and high level product goals and their value using “working backwards” formulation​

  3. Per product area: translate strategic product goals into product features that define actions. Depending on clarity use brainstorming workshops; focus groups / surveys; interface study and reverse engineering

  4. Go back up, group features into epics, conceptualise to produce actionable product roadmap

  5. Revisit and validate the strategic product roadmap, comparing it with the actionable product roadmap

Actionable Product Roadmaps (1).jpg

WHAT TO EXPECT

  1. Connect your strategic vision to what's happening on the ground so that everyone is motivated and working towards the same goal

  2. Vision expressed in non-technical terms, but still actionable by the dev teams so delivery is fast and predictable 

  3. A consolidated view of priorities and progress across multiple teams: everyone's working on the right things

We want to ensure you get your next round of funding. In our experience, this happens when investors can see everyone is working towards a valuable and achievable goal. Actionable Roadmaps are often the one change you need to make.