Scaling People
Write it down, decide who owns it, and set a steady cadence.
Essence (why this landed for me)
This is a field guide for building a team that can run without heroics. It pushes me to move from intuition to written clarity, from ad hoc to cadence, from shared vibes to explicit decision rights. The work becomes simpler when roles, principles, and rhythms are written and followed. It feels directly useful across product, design, and engineering.
Insights (mapped to mental models)
Takeaways grouped by mental models, with a short action you can use now.
Clarity scales faster than charisma
Owners beat committees
Cadence creates compound learning
Write roles so people can self-serve
Decide once, document forever
Meetings are tools, not habitats
Hiring is a system, not a vibe
Raise the bar with written scorecards
Feedback works when it is specific and routine
Org design is product design for people
Decision rights beat seniority
Plan for handoffs as design, not afterthought
Protect focus with explicit priorities
Write one-pagers to think together
Escalate on principles, not personalities
Risk lives at interfaces
Promote for outcomes and teaching
Reduce WIP to raise quality
Make retros short and relentless
Absorption Notes (short essay)
Start with writing. Principles, decision rights, and roles go in the open so speed does not depend on memory or proximity. Give every recurring meeting a job and an owner. Set a simple weekly review that looks at plans, commitments, and one metric that matters. Keep a short decision log so context is easy to reuse and reversals are rare. Hire with scorecards and structured questions. Keep feedback short, specific, and on a steady rhythm. Align teams to the value stream and draw the interfaces so handoffs are predictable. Limit work-in-progress and name the top three priorities each quarter. After each retro, ship one change that improves flow. Simple moves, steady rhythm.
Reflection Prompts (product × design × engineering)
Questions to apply the ideas across projects. Pick one or two and use them today.
Owner check
Who is the single owner for this work
Single-threaded OwnerName the DRP.
Decision rights
Who decides, who inputs, and who executes
Decision HygieneWrite the list.
Cadence
What weekly ritual keeps this moving
Feedback LoopsPut it on calendar.
Role clarity
Is the responsibility written where anyone can find it
Information ArchitecturePublish the page.
Interface risk
Where is the riskiest handoff in this flow
Bottleneck TheoryStress test it.
Bar raising
What must-have would raise the hiring signal
Base RatesAdd to scorecard.
One-pager
Can this plan fit on one clear page
SimplicityWrite the brief.
WIP limit
What can we pause to finish faster
QueuingCut one stream.
Retro to action
What single fix do we ship after the retro
KaizenOne change only.
Top three
What are the three priorities this quarter
FocusMake them visible.