"Goal First" — A Product Roadmapping How-To
May 28, 2013

"Goal First" — A Product Roadmapping How-To

by Brian de Haaff

The best boss I ever worked for (who was also one of my early mentors) beat into me the following: “She with a plan wins.” I hold on to that lesson today, and typically am the first in a meeting to ask the “wet blanket” question: “Why are we doing this?”

An answer of, “Because I said so” might work for kids, but should not fly at work. If you are a product or business leader, you probably find yourself in the same position asking similar annoying questions like, “What problem are we trying to solve?” or “What are we trying to achieve?”

In this post, we are going to focus on the importance of a “goal first” approach and how setting a product strategy and following a product vision are central to product roadmapping. These skills and not your technical acumen are ultimately what drive your company’s success.

We often ask questions about the driving goals before taking action because we know in our gut that “she with a plan wins.” Even if we have not intellectually thought about why we push for the big ideas first, we instinctively know that they need to be answered before the details are aligned. Unfortunately, most meetings and most organizations do not start with this “goal first” approach.

How many meetings have you left asking yourself, “What did that relate to?” or “What was that decision based on?” Aligning the “whats” and “hows” of business to the “whys” is critical to team motivation and success. And when this does not happen, startups fail and larger companies struggle to keep up. Larger companies have more girth to survive, but by the time they are talking about “failing faster” or “change management,” they have already lost.

Focusing on “goal first” is important in every business but fundamental in software companies. This is because the software that is produced by the team is the product that customers buy and thus the product is the company. Build the wrong product and you kill the company. Build the right product, define a market, and be loved.

While behemoth group-think processes, bureaucratic gating, and trickle-down-development destroy innovation and make it hard to define any product goals, blind obsession with agile methods of development carry their own risks. I have seen failures in both waterfall and agile development organizations. It is no secret that agile development emphasizes a heads-down, incremental approach, where major decisions are delayed. The methodology focuses on “sprinting” and “burning down” features to eliminate risk and increase predictability. No matter what development framework you prefer, a clear strategy for product success must come first.

Building great software is hard, but it should not be excruciating. We built Aha! with this goal in mind — we wanted to create a new way for product managers to create brilliant roadmaps. Aha! is purpose-built with the needs of the product manager and a growing software company at its core.

We view product roadmapping as the process of setting a product roadmap. And a product roadmap is nothing more than a plan for how the product is going to meet a set of business objectives. A great roadmap starts with a clear product vision and a canvas that explains the customer and market forces that will shape the product’s direction. In Aha!, we call this plan a strategy. A strategy has many components which cover: customer needs, market size, company strengths, sales channels, positioning, competition, partners, etc.

As a great product manager, you must establish a “goal first” approach and a true north for your product based on the best information you have. Reaffirm your strategy and tweak it as a necessary, but stay grounded in what you are trying to achieve. Explain to the company and product team where you are headed and the value new releases and features will deliver to customers and the business. If you do, your company and team will follow. Lose your direction or whip-saw the team back and forth and the complaints will smack you down.

It is important to note that this approach is consistent with the Lean Startup method of validating assumptions. Break-through strategy is always built on insight and a series of assumptions that have been validated. Use Aha! to set your base assumptions, track them as you prove or invalidate them, and record your findings for everyone to see. Your strategy can then be set, product elevator pitch written, and positioning defined for every relevant function in your organization to grok and use.

Starting with a “goal first” mindset separates great product managers and companies from their competitors and can lead to disruptive innovation. Leveraging a product roadmapping tool can provide a framework and make it easy to set and share the product strategy.

Brian de Haaff

Brian seeks business and wilderness adventure. He is the co-founder and CEO of Aha! — the world’s #1 product development software — and the author of the bestseller Lovability. Brian writes and speaks about product and company growth and the journey of pursuing a meaningful life.

Follow Brian

Follow Aha!

Related articles

January 8, 2018

The Product Plan vs. the Release Plan

Confused about the differences between product plans and release plans? Learn how to use both product plans and release plans to deliver a winning product.

January 23, 2018

User Stories vs. Requirements

Stories. You have hundreds of them if you are a product manager. Each one describes the awesome experiences you want your customers to have while using your product. And…

March 2, 2020

Agile vs. Roadmaps

Have you ever tried to follow a complicated recipe? Exotic ingredients, specialty cookware, and professional techniques — it takes more than instructions to cook a…