Create & Communicate a Strategic Product Road Map.

Communicate strategic, customer-need based and scientifically tested roadmaps. Show what your organization is working on and has planned in.

Align Everyone Around an
Agile Product Roadmap

Building products which really solve people's problems is hard. Getting each step along the road to that right, first time, is harder. Hirundin is designed for product and UX teams, to ensure you don't miss opportunities, validate ideas, prioritize effectively and only work on ideas which solve real user needs.

Your team's time is the most precious resource a company has at it's disposal, and if part of your job is to direct that time, you need to become great at it. It’s a craft, and one that you can deliberately get better at with practice.

Brandon Chu

Communicate outcomes being developed, not work being done

As someone involved in designing, delivering or marketing a product or service, your goals should get set over a fairly broad timeframe; say, three months or so. Those goals will have results to be delivered under them, but invariably how that work gets done will get shifted around as the day to day of project management occurs. The end result is that, if you have a roadmap planned out with dates on it, you're invariably going to hit some things early (woohoo!), and some things late (not so good).

The only sane way around this is to take the timelines out of your roadmap. The goal of a roadmap is to show what you're working on, what's coming soon, what's been recently done, and what you'd like to do at some point in the future. It lets you visualize and show people what's being worked on. Especially as more companies start using agile processes, the idea of the time-based, gantt chart style roadmap becomes less and less feasible, and just leads to frustration from stakeholders.

It's time we re-oriented our main focus of our roadmaps to be outcomes delivered to meet real user needs, based on proper user research. Users should be at the heart of what we do and the strategy we set, and our roadmaps should reflect that, and help teams to understand the thinking behind every outcome which goes on them.

The problem with dates is that no matter how big of a caveat you put above that roadmap, people are going to take it as gospel.

Janna Bastow

Prioritize based on user needs

If you're going to work that way, that means you need to start by uncovering and prioritizing user needs. That should be based on what percentage of users the problem affects, how important it is to them, how expensive it is to the user, how satisfied they are with their current solution and how hard it'd be for you to address it.

Only then can you start to create hypotheses around how you might meet those needs, and develop and challenge ideas around those to find the best work to do. Start using the only roadmapping tool which puts user outcomes and scientific process at the center of your work.

Everything you need, nothing you don't

We've also built seamless sharing functionality so you can share archetypes, user stories and journey maps, user research & prioritization and now, next, future outcome roadmapping with people who aren't on Hirundin, without them having to sign up. However, we don't have any user limits, so feel free to add as many people as you like.

Hirundin: helping you do less, but better.