What Entrepreneurs Can Learn from Team of Teams
Priya had built her packaging startup from a spare bedroom to forty employees in three years, and she still signed off personally on any discount over five percent. One Tuesday, her best sales rep had a longtime customer ready to double an order if she would approve an eight percent discount before the customer's board meeting ended at four. Priya was in back-to-back investor calls until five. The rep texted, then routed the request through two managers, and each said the same thing: only Priya signs off above five percent. By the time she saw the message, the customer had accepted a competitor's offer. The rep wasn't careless — he simply had no authority to act on information he already had. Priya had built a company that could only move as fast as her own calendar, and that calendar had just cost her the year's second-largest account.
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
Building shared consciousness across a growing venture
In a startup, shared consciousness means every team works from the same live picture of customers and cash, instead of learning about problems through updates that trickle down from you days later.
Support fields two weeks of complaints about a shipping defect before the news reaches the product team, because the only channel connecting them is a status meeting you run once a month.
Replace one recurring status meeting with an always-open shared channel where every team posts what changed that week, in plain language, so any other team can see it without asking you first.
Empowering execution instead of approving every decision
Once your team shares the picture you have, most decisions that used to require your sign-off are ones they can make as well as you, because they sit closer to the problem.
You write a discount-approval rule for the sales team but still ask to personally review every deal above the threshold, so the rule exists on paper while the bottleneck survives in practice.
Pick one recurring approval you currently give — discounts, refunds, minor hires — and hand the decision to the team with the most direct customer context, then stay out of that loop for thirty full days.
Small, connected teams inside a growing company
As departments multiply, the instinct is to route every cross-team question through you as the connector; instead, small teams should reach each other directly, the way two people on the same team already do.
Your product and support teams both report to you but never talk to each other, so every bug report crosses your desk twice before either team actually learns anything from it.
Assign one person from each department to sit in on another department's weekly meeting, so information travels team to team instead of depending on your calendar as the only bridge between them.
Your changed role as founder
As your company grows, your job shifts from making the most decisions to designing conditions that let good decisions happen without you: which information is visible to whom, which teams talk directly, and which choices no longer need your signature. This is not a smaller job, but a different one, closer to architect than operator, and the only version that can scale past the limits of your own attention and calendar.
Widening who can see financial data can pull against giving teams real authority to spend against it: transparency without limits invites chaos, while limits without transparency just recreates the bottleneck under a friendlier name. Pair open information with clearly stated boundaries — tell teams everything about the numbers, then specify exactly what they are trusted to decide inside them, so visibility and freedom expand together instead of one standing in for the other.
Name one thing, honestly
Which decision did you approve this week that someone closer to the situation already had enough information to make without you?
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
Assign one person from each department to sit in on another department's weekly meeting, so information travels team to team instead of depending on your calendar as the only bridge between them.