The Most Impactful Thing Today (with the Honesty Test)
Wake up asking what maximizes impact — then interrogate your answer for skill-set bias.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 3
- Confidence
- 90%
A daily prioritization discipline paired with a bias-check. Each day you ask what single action most advances what you're trying to achieve, but the hard part is answering honestly rather than defaulting to work you enjoy or are already good at. Taylor pairs the question with a rule: whatever you name is at least 30% likely chosen for comfort, not truth.
Origin
Bret Taylor credits Sheryl Sandberg, who confronted him at Facebook about not holding his team to his own quality bar, which reframed how he approached his role from 'what I like to do' to 'what has the most impact.'
Core principles
- 01Optimize for impact, not for the tasks you personally enjoy
- 02Your identity should be flexible — be a 'builder', not just an engineer or PM
- 03The value you derive shifts from the activity to the outcome once you commit
- 04People subconsciously pick their superpower as the answer to every problem
- 05Naming the right priority is easy; naming it accurately is the hard skill
How to run it
- 1
Ask the daily impact question
Each morning, literally or figuratively, ask: what is the single most impactful thing I can do today to make what I'm trying to achieve more likely to happen? Imagine an external board of advisors telling you where to focus.
Pro tip Rotate honestly across functions — some days the answer is recruiting, some days product, some days sales.
- 2
Loosen your identity
Stop conforming the job to the tasks you think you like. Reframe from 'I'm the boss, I should focus on what I enjoy' to 'what does this role actually need from me right now?'
Watch out A rigid, ossified self-image ('I'm an engineer') will silently cap your success in a role that needs something else.
- 3
Run the 30% honesty check
Whatever action you named, assume there's at least a 30% chance you chose it out of comfort and familiarity rather than truth. If the solution happens to be the thing you've done your whole career, question it by default.
Pro tip Pressure-test your answer with a strong co-founder or cross-functional partner who won't share your bias.
Watch out 'Incorrect storytelling' — telling yourself and your team a false reason — turns an intuition into a 'fact' and can orient your whole strategy around the wrong problem.
In the wild
Newly running Facebook's ~1,000-person mobile and platform org, Taylor was 'doing okay but not great' and caught personally editing a partner presentation. Sandberg pulled him into a room and gave him 'management 101' about holding his team to his standard. He stewed, got defensive, then woke up and admitted she was right.
→ He reframed the job around impact rather than personal preference, did different things, discovered he enjoyed the impact more than the craft, and became materially better at the role.
Common mistakes
Being a single-issue voter
First-time founders default to their strength as the universal fix — great engineers say the answer is engineering, designers say a redesign ('the dead cat bounce') will save everything, BD people chase one magic partnership. The comfortable answer is rarely the correct one.
Taking stated reasons at face value
A salesperson says a deal died on price when the real problem was product differentiation — so you go optimize pricing and never fix the actual gap. Customer and user statements are usually related to the truth but rarely are the truth.
Is it for you?
Best for
Founders and senior leaders spread across many functions who must decide where their scarce attention goes each day
Not ideal for
Individual contributors with a single well-defined mandate where prioritization is already externally set
From the transcript
“what is the most impactful (19:00) thing I can do today”
“it's at least 30% likely that you've chosen that because of comfort and familiarity, uh not truth”
“you're often a single issue voter based on your skill set”
“people don't like my product because of X. And if you tell that to yourself and you tell it to your team, all of a…”
From the episode
He saved OpenAI, invented the “Like” button, and built Google Maps: Bret Taylor on the future of careers, coding, agents, and more