What Leaders and Managers Can Learn from Expecting Better
Expecting Better argues that a rule handed down without its reasoning is hard to use well. Told only what to do, people either comply anxiously or dismiss the instruction, and neither response is real understanding. Broad guidance is usually built for the most cautious version of a large, varied population, not your specific case, so it tends to be more conservative than the evidence for your situation actually requires. Real understanding, in turn, grows from asking good questions over time, in small doses, rather than from one panicked research binge attempted right before a big decision. None of this licenses acting alone, though. The point is always a sharper, more specific conversation with whoever holds real responsibility for the outcome, not a reason to override them. For leaders and managers, the inherited rules arrive as management best practice: review formats, feedback frameworks, policies copied from a larger company without anyone asking why they existed there in the first place. This edition adapts the same four ideas to the guidance you inherit from HR playbooks, leadership books, and organizational habit.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Questioning the inherited policy
Every organization accumulates rules nobody remembers commissioning: mandatory stand up meetings, rigid promotion timelines, review cycles borrowed from a prior employer. Repeated long enough, these become instructions leaders enforce without knowing why.
A manager keeps a rigid weekly status meeting because "that's how we've always done it," long after the team's structure that once required it has changed.
Before enforcing an inherited policy, ask one person who was there at its creation what problem it was meant to solve.
Recognizing guidance built for the average team
Most management advice is calibrated for a broad, anonymous population of teams, not for yours. It has to be cautious enough to work everywhere, which often makes it more restrictive, or more permissive, than your specific team needs.
A leader imposes a strict approval chain meant for large, high-turnover teams onto a small, trusted group, slowing decisions that never needed the extra layer.
When adopting a widely used practice, ask what size or type of team it was designed to protect, and compare that to your own.
Treating understanding as an ongoing habit
Leaders often try to master an entire framework in one intensive workshop, then never revisit it. Real understanding of your team comes from asking small questions continuously, in one on ones and retrospectives, not one session before a rollout.
A manager absorbs a leadership book over one weekend, applies it rigidly for a month, then abandons it when reality does not match the framework.
Pick one open question about how your team actually works, and spend fifteen minutes each week testing it against what you observe.
Using it to sharpen the conversation, not skip it
None of this is grounds for overriding the people whose judgment carries real weight, whether your manager, an HR partner, or a mentor who has led similar teams before. Understanding the reasoning behind a practice is meant to help you ask sharper questions of them, not hand you license to discard established process on your own authority.
Sometimes questioning an inherited policy and needing to roll something out quickly pull against each other, especially when you suspect a new process will not fit your team. Favor the shorter version of the habit: ask one direct question of whoever owns the policy, rather than enforcing it silently or ignoring it. A specific question keeps both the relationship and the decision open.
Name one thing, honestly
- Which policy on your team have you enforced lately without knowing what problem it was meant to solve? - Where are you being more restrictive, or more permissive, than your team's actual situation calls for? - What is one question about your team's dynamics you have been meaning to test for weeks?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Pick one open question about how your team actually works, and spend fifteen minutes each week testing it against what you observe.