Is your product team obsessed with numbers?

If they are, then they are probably an outcome-driven team

If they aren’t, then they are probably a feature-driven team

What’s the difference?

An outcome-driven team focuses on building solutions that will have a positive impact on the business. They celebrate the outcome of their work. They will have goals that are determined by hard numbers. Those numbers guide their overall success, which is why they are obsessed with them.

A feature-driven team focuses on simply building the features given to them. They celebrate the launch of those features, with little to no regard for the overall impact on the business. The volume of features churned out over time is the primary measure of success.

So if you are wondering if your product team is outcome-driven or feature-driven, look to see if they are obsessed with the numbers.  

Previous
Previous

Why I like the Kano model for building innovative products.

Next
Next

Don’t let the product become the strategy