What Leaders/Managers Can Learn from Buy Then Build
When Priya was promoted to run the customer support department, she inherited a team of nine and a ticketing process that had evolved over six years. Eager to make her mark, she spent her first two weeks designing a brand-new workflow from scratch, confident that a fresh system built on modern best practice would beat whatever the old team had cobbled together. She rolled it out in week three without asking the two longest-tenured reps why the old process worked the way it did. Within a month, response times had gotten worse, not better, because her new system had quietly eliminated a manual check that had been catching a recurring billing error for years. Priya had never considered that the existing workflow might already encode hard-won knowledge worth understanding before replacing.
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
Resisting the urge to rebuild everything you inherit
New leaders are often rewarded for visible change, which creates pressure to treat every inherited process as something to replace rather than something to first understand. Before proposing a new system, a leader benefits from asking whether the existing one is actually broken, or just unfamiliar. Many "outdated" processes survive because they quietly solve a problem nobody explained to the newcomer yet.
A leader assumes silence about a process means nobody cares about it, when in fact no one has been asked directly and several people rely on it daily.
In your first two weeks in a new role, list every process you're tempted to change, and interview one person who depends on each before touching it.
Diagnosing team and system health before acting
A confident narrative from a predecessor or a glossy dashboard can hide real dysfunction, just as a seller's pitch can hide a struggling business. Leaders should independently check performance data, talk to people at every level, and notice where the official story and the lived experience diverge, rather than accepting the first explanation offered for how things really work.
A leader trusts an outgoing manager's exit summary at face value and misses that two key clients were already planning to leave.
Before forming an opinion about an inherited team, hold individual conversations with every member and compare what you hear to what the paperwork says.
Earning authority you were only assigned
Being named the leader does not make people follow you; it only grants permission to try. A team that didn't choose you needs to see consistency, fairness, and respect for what they already built before they extend real trust. Leaders who skip this step by leading with authority alone often get compliance without genuine buy-in, which shows up later as quiet resistance.
A new leader issues directives in week one without context, and the team technically complies while disengaging from any real initiative.
Spend your first month asking more questions than you answer in team meetings, and make your first changes small and visibly reversible.
Improving deliberately once you've earned the room
Once a leader has genuine credibility with an inherited team, the work becomes steady improvement rather than a single reset. Small, well-explained changes, tested and adjusted based on real results, tend to compound into lasting gains without triggering the defensiveness or turnover that a sweeping overhaul provokes, and they let the team see the leader as a steward rather than an outside disruptor.
Honest diagnosis of a struggling team can create real urgency to fix things fast, which pulls directly against the discipline of earning trust slowly. A leader who sees a genuine problem should still separate speaking up quickly from acting unilaterally; naming the issue early while building changes gradually resolves most of this tension without losing credibility or momentum.
Name one thing, honestly
What have you already assumed needs rebuilding in your current role, without yet asking anyone why it was built that way?
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
Spend your first month asking more questions than you answer in team meetings, and make your first changes small and visibly reversible.