lead & success

Most leadership books hand you slogans; this one hands you habits. Jacob is direct about the unglamorous work—listening, admitting mistakes, holding standards—because that is where trust is actually built. It suits new managers drowning in responsibility, mid-career leaders stuck on a plateau, and anyone promoted for competence who now must lead former peers. If you want influence that survives a bad quarter, start here.

1. 1Early chapters on credibility

   Trust is the currency you spend before you can lead

   A newly promoted team lead walks into her first Monday with a plan, a deck, and zero goodwill banked. The room is polite; the room is also unconvinced. She pushes the plan anyway and watches it stall in silence. Jacob's point lands hard: without deposited trust, even a correct idea reads as a threat. The lead starts over—small commitments kept, small confessions made—and the same plan, months later, passes without a fight.

   The idea

   Credibility is earned in small denominations, not grand gestures. People decide whether to follow you based on whether your past behavior matched your promises, so consistency beats brilliance. The surprise is how little it takes to lose it: one dodged admission, one quietly broken commitment. Leaders who treat trust as a reserve to draw on, rather than a balance to grow, spend down their authority without noticing until the room goes quiet.

   Try this: List every commitment you made last week; close or renegotiate each one today, in writing, with the person who heard it.

2. 2Communication chapters

   Clarity is a kindness, not a luxury

   A project team spends weeks building the wrong thing—not because they were lazy, but because the brief said 'improve engagement' and everyone filled that silence with their own guess. The reveal happens in a review meeting: three versions of the same product, three definitions of success. Jacob frames the wasted month as a leadership failure, not a team failure. The leader who left the goal vague owed the team a sentence they never got.

   The idea

   Ambiguity feels safe to the leader and expensive to everyone else. When you refuse to name the target, you delegate the decision to whoever speaks last or loudest. Specific, repeated, boringly clear goals are how teams move fast without constant supervision. What surprises people is that clarity costs courage: saying exactly what you want invites exactly what you will be judged on.

   Try this: Rewrite your team's current top priority as one sentence a stranger could act on; read it aloud at the next meeting and ask what's still unclear.

3. 3Delegation and empowerment chapters

   Delegate outcomes, not chores

   A manager hands off a task with the instruction 'do it this way,' then wonders why the report never thinks for herself. Jacob sketches the alternative: hand over the outcome, the constraints, and the deadline—then step back. The first attempts are messier than the manager would have made them. But the second and third attempts get better than the manager's own version, because the report owns the result, not the recipe.

   The idea

   Delegating method produces compliance; delegating outcomes produces judgment. If people only ever execute your instructions, you have hired expensive hands and wasted their heads. The uncomfortable part is tolerating a worse first draft so a better second one can exist. Leaders who cannot stand that gap end up as the bottleneck of everything, admired for quality and resented for pace.

   Try this: Pick one recurring task you own; hand it over with the goal and deadline only, and forbid yourself from specifying the method.

4. 4Feedback chapters

   Feedback lands when it is specific, timely, and yours

   In a performance conversation, a manager opens with 'you're doing great, keep it up' and the report leaves knowing nothing. Jacob contrasts this with the manager who says, on the same day as the event, exactly which behavior helped and which hurt. The first conversation is a ritual; the second is a gift. Over a quarter, the second team quietly outperforms, because nobody is guessing what 'great' means.

   The idea

   Vague praise is easier to give and nearly worthless to receive. Useful feedback names the behavior, the moment, and the effect—soon enough to matter. The reason it holds is that memory decays fast and specifics are actionable while adjectives are not. What surprises people is that withholding feedback is not kindness; it is choosing your comfort over someone's growth.

   Try this: Within 24 hours of your next observation, tell one person one specific behavior and its effect—no sandwich, no hedging.

5. 5Conflict and hard conversations chapters

   Conflict avoided is a decision made badly

   Two senior leads disagree about a launch date in a hallway and both decide to 'let it go.' The disagreement does not disappear; it goes underground and resurfaces as missed handoffs, duplicated work, and a launch that slips. Jacob traces the failure back to the hallway: the moment politeness won over the project. When the conflict is finally surfaced, the actual disagreement takes ten minutes to resolve.

   The idea

   Unspoken disagreement does not cost nothing; it compounds interest. Teams that surface conflict early spend minutes; teams that suppress it spend months. The skill is not aggression but directness with respect—naming the disagreement while it is still small. What surprises people is how cheap the hard conversation usually turns out to be compared to the soft avoidance.

   Try this: Name one disagreement you have been smoothing over; put fifteen minutes on the calendar this week to state your position plainly and ask for theirs.

6. 6Decision-making chapters

   Decisions beat deliberations

   A leadership team meets for the fourth time on the same decision, and everyone leaves with more information and less certainty. Jacob describes the pattern: endless analysis as a way to avoid accountability for choosing. The breakthrough is procedural, not intellectual—someone finally names who decides, by when, and on what criteria. The decision takes twenty minutes. The team's relief is visible.

   The idea

   Analysis has diminishing returns; accountability has none. Most stalled teams do not lack information, they lack a named owner and a date. Speed comes from deciding who decides, not from more meetings. What surprises people is that a reversible decision made fast usually beats a perfect decision made late, because you learn from the consequences either way.

   Try this: For your current stuck decision, write down who owns it, the deadline, and the criteria—then cancel the next meeting on it.

7. 7Leading by example chapters

   Your team watches your feet, not your slides

   A leader preaches work-life balance in an all-hands, then sends emails at midnight and praises the first person online each morning. The team hears the words and reads the behavior; the behavior wins. Within months, burnout spreads and the best performer quietly interviews elsewhere. Jacob's scene is uncomfortable because the leader means well—the failure is not hypocrisy intended, but example unexamined.

   The idea

   Culture is whatever you tolerate and model, not what you announce. Every exception you make for yourself becomes the real policy. The reason this holds is that people copy power, not posters. What surprises leaders is how small the telltale behaviors are: which meetings you skip, whose ideas you repeat, what you do at midnight.

   Try this: Pick one behavior you preach; audit your own last two weeks and change one visible habit to match it.

8. 8Failure and learning chapters

   Failure reviewed openly is tuition, not shame

   A team misses a launch badly, and the leader's first instinct is to find the person to blame. Jacob walks through the alternative: a review where the leader names her own missteps first, and the room relaxes enough to tell the truth. The real causes—unclear ownership, an ignored early warning—surface only after the fear does. The next launch is not perfect, but the same failure does not repeat.

   The idea

   Blame produces silence, and silence produces repeat failures. If people hide mistakes, you are managing a team that lies to you. Leaders who go first in admitting error buy honesty at a discount. What surprises people is that accountability and safety are not opposites: you can hold standards high and make it safe to report the truth about how things went.

   Try this: At your next review of a miss, state your own contribution first, then ask 'what made this hard to see coming?' and write down every answer.

9. 9Hiring and talent chapters

   Hire and promote for judgment, not just polish

   An interview panel falls for a confident candidate with a smooth story, and passes on a quieter one who asks better questions. Six months later, the smooth hire needs managing daily; the quiet one, hired elsewhere, is running her own project. Jacob uses the contrast to show how charisma in interviews predicts interview performance, not job performance. The panel's rubric, not its gut, was the missing tool.

   The idea

   Interviews reward rehearsed confidence, so structure beats instinct. Define the judgment you actually need, then test it with real scenarios rather than vibes. The reason it holds is that past behavior and live reasoning predict better than polish. What surprises people is that your gut is often just your affinity bias wearing a suit.

   Try this: For your next hire, write three scenario questions that test judgment on the actual job, and score answers against the rubric before discussing.

10. 10Vision and motivation chapters

    Vision is a story people can see themselves in

    A leader announces a vision in abstract nouns—excellence, innovation, synergy—and watches eyes glaze. Jacob contrasts it with a leader who describes a specific future scene: what a customer's day looks like, what the team is proud of, what is no longer true. The second vision gets repeated by employees in their own words, which is the only test that matters. The first vision survives only on posters.

    The idea

    A vision works when people can retell it without notes. Abstraction is forgettable because it asks nothing of the imagination; concrete scenes are memorable because they invite people to place themselves inside. The reason it holds is memory and motivation both run on images, not adjectives. What surprises leaders is that specificity scales better than grandeur.

    Try this: Rewrite your team's vision as a one-paragraph scene set two years out, naming who benefits and what is different; test it by asking a teammate to retell it a day later.

11. 11Recognition chapters

    Say thank you like you mean the work

    A team member does the unglamorous work that saves a client relationship, and it goes unmentioned in the meeting where the win is celebrated. She notices. Jacob shows the arithmetic of recognition: specific, public, and tied to the actual act—or it reads as noise. When the leader finally names the contribution precisely, in front of peers, the repair is real but late. The lesson is about the first meeting, not the apology.

    The idea

    Recognition is a signal system: what you praise is what you will see more of. Generic thanks teaches nothing; specific praise teaches everything. The reason it holds is that people repeat what gets seen. What surprises leaders is how much retention is quietly decided by whether good work is noticed within days, not quarters.

    Try this: This week, publicly name one person's specific contribution and exactly why it mattered—no generic 'great job' allowed.

12. 12Closing chapters on legacy

    Legacy is what continues without you

    The book closes with a leader preparing to leave a role and discovering what actually survives: not the strategy deck, but the habits she installed—how the team runs reviews, how it treats mistakes, how it hires. Jacob's scene is quiet: the successor changes the strategy and keeps the practices. The leader's real output was the system and the standards, not the artifacts. Influence, it turns out, is what keeps operating in your absence.

    The idea

    The measure of leadership is not what you achieved but what keeps working when you are gone. Systems, standards, and developed people outlast any single win. The reason it holds is that organizations run on defaults, and leaders author the defaults. What surprises people is that the most egotistical act—building everything around yourself—produces the least legacy.

    Try this: Write down three practices your team would lose if you left tomorrow; document one of them this week so it survives you.

New and mid-level managers who were promoted for competence and now need to lead humans. Also valuable for founders and team leads who want influence that outlasts their presence.

FAQ