airfocus-logoBlog
airfocus search loupe
airfocus search exit

Try for free

Roadmapping

Why Product Teams Should Be Outcome Optimized Instead of Feature-focused

22 Sep 20223 mins read
Tomas Prochazka
Why Product Teams Should Be Outcome Optimized Instead of Feature-focused
By Tomas Prochazka
CONTENTS

If features are good, then the more features your product has the better, right? Wrong!

It’s the classic quantity over quality debate, and for those of you who are still undecided here’s our take: Quality wins. And yet many product teams still operate like having more features is the main measure of success.

When the only roadmap your team is using is feature-driven — and performance is measured by how many features we can squeeze into the next release cycle — then your team may as well be a feature factory. Here’s why.

eBook

Roadmapping From A to Z

Read now
CTA eBook image background
airfocus eBook Roadmapping From A to Z

What does it mean to be a feature factory?

A feature factory is a product team or company that’s more focused on pumping out features than understanding whether those features should be pumped out… or not.

The phrase feature factory was coined by John Cutler to describe the experience of developers working in software companies but felt more like they worked on assembly lines in a factory.

As an expert in product management, Cutler identified feature factories as companies that focus on the number of features included instead of the quality of features and their impact on consumers.

5 critical problems that feature factories share

What’s so bad about being a feature factory, we hear you ask? Lots of companies develop products this way — and if it ain’t broke, don’t fix it.

But it is broken. Let’s look at some common feature factory problems.

Demoralized developers

When work is disconnected from objectives, it becomes valueless. If a developer has no feedback on their work or how it ultimately impacts consumers or the company’s strategic objectives, they realize that their work doesn’t matter. 

Teams organized around short-term convenience quickly become teams of 1 person. Workers are left demotivated, disconnected, and disenfranchised.

Bloated products

Stephen Covey, author of The 7 Habits of Highly Effective People said, “The main thing is to keep the main thing the main thing.”Feature factories create products that do the exact opposite. 

When users are forced to wade through layered menus of features that they will never use to find the one thing the product is meant to do, they go and find a more optimized solution. 

Features don’t always add value, they sometimes dilute it. 

Broken products

 Adding features adds complexity. Each added feature exponentially increases the possibility that one feature will break another. 

This complexity also means that if a feature breaks because it was dependent on a resource that has changed or is no longer available, product teams encounter the failure cascade. Truly as bad as it sounds, this makes finding and fixing issues in released products more difficult — and, sometimes, impossible.

Slower development

Added complexity makes everything slower. Features take more consideration before implementation to ensure they are truly new and not overlapping. New features must integrate with more existing systems. Testing needs to consider ever more complex and convoluted use-cases and corner-cases.

Skeptical users

Users love it when product owners listen to their feedback and respond appropriately. The answer, however, is not always a new feature. 

Constantly adding new features that have a minor impact, or only benefit a small subset of users, can cause most of your customers to be cynical of new releases — and new features end up being irrelevant.

If features are good, then the more features your product has the better, right? Wrong!

Why outcome-driven roadmaps are the way to go

So if product teams shouldn’t lean too heavily on feature-led roadmaps, then what can they do? Enter: the outcome-driven roadmap.

eBook

Roadmapping From A to Z

Read now
CTA eBook image background
airfocus eBook Roadmapping From A to Z

Outcome-driven roadmaps include features, but they look vastly different from feature-driven roadmaps. Every feature is tied to outcomes. Outcomes are measured through KPIs to understand success. And whether an outcome is successful or not, it is reviewed, and the impact of features is understood.

How a feature is implemented is as important as whether it is implemented. Teams are rewarded for innovative, excellent implementation because it impacts the outcome.

Features are strategically assigned to teams who develop towards outcomes that are already being worked on. Features are prioritized by impact as well as effort and time.

Features can also be incrementally improved to better meet outcomes — or canceled if they are not meeting the objectives. Developers understand why adjustments or pivots are necessary and can help with formulating the best solutions.

Optimizing outcomes instead of focusing on features removes the risk of feature factory behavior and keeps product people with their eyes on the prize!

Avoiding the feature factory mindset

If your product team exists in a feature factory already, or you’ve noticed your team is heading that way, there are actions you can take. Check out the airfocus ebook, to help you transition to a value-focused company.

Tomas Prochazka

Tomas Prochazka

Content Marketing Manager @ Usersnap
Tomas is a passionate content strategist with strong knowledge of SEO principles and organic growth models. Over the last years he has been working in various lead content and SEO roles for European companies in the B2B SaaS industry, as currently he leads all content activities at Usersnap....more
44 Articles
airfocus eBook Roadmapping From A to Z
eBook
Roadmapping From A to Z
Read now

Read also

Testimonial Company
Product Strategy 20 Feb 2024
Driving Success in Product Design With OKRs
Discover strategies for setting clear, impactful objectives, aligning your team, and measuring success to ensure your product design aligns with your vision and strategy.
By Adam Thomas
Testimonial Company
Testimonial Company
Product Management 11 Feb 2024
How to Write Effective OKRs in 5 Steps (+7 Mistakes to Avoid)
Objectives and Key Results (OKRs) are a powerful tool that companies and their product teams can use to align on goals and measure progress toward meeting those goals. How you write your OKRs gets you off to a great start toward accomplishing part or all of your objectives. Here’s a look at five steps to follow when writing both Company and Product OKRs.
By Kent McDonald
Testimonial Company

Build great
roadmaps

Book a demo

Instant tour

airfocus modular platform

Experience the new
way of doing product
management

airfocus modular platform
Top rated
on major platforms
g2 badge users love us
g2 badge momentum leader
GetApp badge category leader
software advice badge
capterra shortlist badge
proddy badge roadmapping
crozdesk badge
Company
All rights reserved. contact@airfocus.com
ENDE