The reading room · Digna Legi
‘Give Away Your Legos’ and Other Commandments for Scaling Startups
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. Evidence is sampled with gaps, so completeness and balance of the full article cannot be verified.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Why read this
Fast-growing companies require people to surrender work they built before they can grow into the next level of responsibility.
AI brief · Checked against source text
The main idea
Molly Graham’s central claim is that scaling feels chaotic because both jobs and companies change faster than people’s identities adjust. The counterintuitive move is to give away responsibilities instead of defending them: new hires do not simply reduce work, they let the organization take on larger work while early employees redefine their jobs. Leaders can reduce damage by normalizing the emotions and pointing people toward the next, larger problem.
Go a little deeper
Job loss can be promotion in disguise
The Lego metaphor is useful because it names a specific emotional trap: people experience delegation as dispossession even when the company still has more work than capacity. Graham argues that the successful pattern is not clinging to the original project, code, channel, or process, but repeatedly treating a handed-off job as permission to find the next larger version of one’s role.
Scale breaks implicit coordination
The 30-to-50-person stage is where informal communication stops carrying the company. Graham’s remedy is not heavy process, but explicit principles: mission, values, philosophies, compensation philosophy, what high performance means, and what managers are for. The mechanism is durability: principles let systems evolve without copying another company’s mature machinery too early.
Early hiring compounds culturally
Graham treats the first 100 to 200 hires as formative because hiring quality propagates through referrals, expectations, and tolerated behavior. Keeping weak performers is not just a local performance problem; it teaches strong employees what the organization accepts and shapes who arrives next. The advice to fire quickly follows from that compounding effect, not from a generic toughness posture.
Politics signals weakened common purpose
After roughly 750 employees, Graham says identity shifts toward teams and politics begins when people act for themselves rather than the company. Her response is behavioral and communicative: connect team work to company goals, state what behavior is rewarded, and make leaders responsible for calling out bad conduct before it hardens into the operating culture.
A case from the article
The larger assignment releases the old one
At Facebook, Graham was asked to take over a project started by a close co-worker, who struggled to let go despite trusting her. Their boss solved the problem by giving the co-worker a larger, more important version of the same kind of challenge. The point is not that anxiety disappears through reassurance; it can be redirected by making the next opportunity concrete and big enough.
How the case is made
The case is made through Graham’s operating experience at Google, Facebook, and Quip, plus repeated observations from startups scaling through headcount thresholds.
Where the idea has limits
Graham explicitly treats headcount phases as patterns, not laws: company character, founders, product, and prior habits can make the same employee count feel very different.
A question to take away · from Digna Legi
What responsibilities are you protecting because they prove your past value, rather than because they are still the highest-leverage use of you?
What the original adds
The source adds a staged map of scaling from 30 to 750+ employees, including when to write principles, protect hiring quality, address bad habits, and watch politics emerge.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.