Arrow icon
Ness Labs: Make the most of your mind
Learn more about Joggo

A Summary of

Balancing outcome-thinking with design and technical requirements

by
Lenny Rachitsky
Lenny's Newsletter
View original

Being an outcome-thinking team means that work is prioritized, and teams are structured around the outcomes that the company wants to achieve. A strong correlation was evident between those outcome-oriented teams and teams that drove significant impact. To find that balance between outcome-thinking and engineering needs you simply need to think further out into the future: 1. How much would this work benefit your outcome 1+ years out? 2. What happens if you don’t do it? 3. What are the chances of it being successful? Finding this balance can is never an easy call, but it’s normal.

Related content
See all posts
Arrow icon
April 11, 2020
/
Ravi Mehta
/
Ravi Mehta

Becoming A Peak Product Manager

Read more
September 1, 2020
/
Marty Cagan
/
Silicon Valley Product Group

Discovery – Learning vs. Insights

Read more
July 11, 2011
/
Andrew Chen
/
Andrew Chen

Don’t compete on features

Read more
/
/
First Round Review

How to Engage Your Users to Build the Product They Actually Want

Read more
August 19, 2018
/
Brandon Chu
/
Black Box Of Product Management

Product Management Mental Models for Everyone

Read more