# An Elegant Puzzle
*Will Larson's handbook for engineering managers in fast-growing tech companies. He wrote it while running Stripe's Foundation Engineering group, after earlier jobs at Yahoo, Digg, SocialCode and Uber. It treats management as a set of interlocking systems rather than a list of personal habits: how big teams should be, what a struggling team needs next, how to pay down technical debt (through migrations), how to run a reorg, how to write strategies and visions, how to say no, and how to design hiring loops, career ladders and performance cycles. It is short, opinionated and built from about 50 short essays. Almost all of them began as posts on Larson's blog,* Irrational Exuberance*. Stripe Press published it in May 2019.*
> **What I read.** I did **not** read the printed book or the ebook. No legal free copy of the book exists (see section 2). However, Larson says he "wrote each of the chapters as a blog post" before the book was assembled ([What I learned writing a book](https://lethain.com/learned-writing-book/)). I found and read a blog counterpart for each of the book's 47 numbered sections on [lethain.com](https://lethain.com/) (about 60,000 words in total, listed in the outline below). For 3.13 and the two appendix lists (7.2, 7.3), the match is the closest post rather than one with the same title. Every post predates the book. The book's text was edited after the posts were written: Larson says "everything changed a bit and a few things changed a lot, particularly the chapter transitions". So the outline describes the **blog versions**. Quotations come from those posts and are marked "(blog)". I did not check them against the printed text. **No page numbers.** The table of contents comes from a bookseller listing and Google Books (see section 5). Full copies of the book are on piracy sites; I did not use or link them.
Related in this vault:
- Publisher folder: [[Book Summaries/Stripe Press/Stripe Press|Stripe Press]]. This is the fifth Stripe Press book by release date, after [[Book Summaries/Stripe Press/High Growth Handbook - Elad Gil|High Growth Handbook]], [[Book Summaries/Stripe Press/The Dream Machine - M. Mitchell Waldrop|The Dream Machine]], [[Book Summaries/Stripe Press/Stubborn Attachments - Tyler Cowen|Stubborn Attachments]] and [[Book Summaries/Stripe Press/The Revolt of the Public and the Crisis of Authority in the New Millennium - Martin Gurri|The Revolt of the Public]].
- Closest companion: Elad Gil's *High Growth Handbook* (also Stripe Press) covers the same "hypergrowth" setting from the founder and executive side. Larson covers it from inside the engineering organization.
- Still in the queue and relevant: Claire Hughes Johnson's *Scaling People* (#370, Stripe Press 2023), another Stripe operator's management handbook, and Eliyahu Goldratt's *The Goal* (#481), which is on Larson's recommended-reading list.
## 1. Book facts
| | |
|---|---|
| Title | *An Elegant Puzzle: Systems of Engineering Management* (often shortened to "AEP" by Larson) |
| Author | Will Larson |
| Publisher | Stripe Press, the publishing imprint of Stripe ([Stripe Press](https://press.stripe.com/an-elegant-puzzle); [Stripe Press catalog data](https://stripe.press/catalog.json)). Google Books names the publisher "Stripe Matter Incorporated" |
| Hardcover | Stripe Press, publication date **20 May 2019**, 288 pages, 6 × 9 in., ISBN 978-1732265189 / 1732265186, list price $35 ([Amazon](https://www.amazon.com/dp/1732265186); [Stripe Press catalog data](https://stripe.press/catalog.json); [Abbey's](https://www.abbeys.com.au/api/product.do?isbn=9781732265189)) |
| Release date note | Larson's launch post says "On May 28th, we released An Elegant Puzzle" ([lethain.com, 29 May 2019](https://lethain.com/elegant-puzzle-press/)), and the queue entry uses 2019-05-28. Retailers and OverDrive give 20 May 2019, and Larson's later "by the numbers" post also says it "was released on May 20th, 2019" ([lethain.com](https://lethain.com/aep-five-months-later/)). Both dates are in Larson's own writing. 20 May appears to be the formal publication date and 28 May the announced launch day |
| Kindle | ASIN B07QYCHJ7V, publication date 28 May 2019, print length 289 pages ([Amazon](https://www.amazon.com/dp/B07QYCHJ7V)) |
| Audiobook | Unabridged, read by Tiffany Morgan, 6 h 36 min, Stripe Press, 30 May 2019, ASIN B07SH1DXXM ([Amazon audiobook listing](https://www.amazon.com/dp/B07SH1DXXM)) |
| Ebook ISBN | 9781953953339 (Stripe Matter Inc., per [Open Library OL48516606M](https://openlibrary.org/books/OL48516606M)) |
| Blurbs | Cindy Sridharan, Jeffrey Meyerson (Software Engineering Daily) and Oren Ellenbogen (Software Lead Weekly) (Amazon Kindle page; Larson thanks the same three in [What I learned writing a book](https://lethain.com/learned-writing-book/)) |
| Design note | All the endnotes are printed as QR codes linking to the sources (Larson, [What I learned writing a book](https://lethain.com/learned-writing-book/); see also [Using QR Codes in printed books](https://lethain.com/qr-codes-in-books/)) |
| Sales (author's figures) | 12,780 copies sold from 20 May to 22 Oct 2019; 27,000 printed; about 60% hardcover, 30% Kindle, 10% audio in Q2–Q3 2019; Larson's share "$2, roughly" per copy ([An Elegant Puzzle by the numbers](https://lethain.com/aep-five-months-later/)) |
| Library data | Open Library work [OL20641522W](https://openlibrary.org/works/OL20641522W) (hardcover edition [OL27905593M](https://openlibrary.org/books/OL27905593M)); [WorldCat OCLC 1105154200](https://search.worldcat.org/title/1105154200); [Google Books _eKnkw8cYssC](https://books.google.com/books?id=_eKnkw8cYssC) (285 pp., "illustrated"). Open Library also tags the work with the subject "Long Now Manual for Civilization"; I did not confirm that on Long Now's site |
**Where it came up.** On 2026-11-13 Marshall asked for the whole current [Stripe Press catalog](https://press.stripe.com/) to go into the queue (relayed by Obsidian Author). The queue block is in Stripe Press release order, earliest first. This book (2019) is the fifth, after *The Revolt of the Public*. Catalog page: [press.stripe.com/an-elegant-puzzle](https://press.stripe.com/an-elegant-puzzle).
## 2. Book resources
**Free (legal).**
- **No legal free full text of the book.** Stripe Press and Larson have not posted it. Complete PDFs and "read online" copies on file-sharing sites are unauthorized, so I did not use or link them.
- **The author's own free versions of nearly every section.** Larson's blog, [Irrational Exuberance (lethain.com)](https://lethain.com/), still hosts the posts that became the book's sections. Each one is linked in the outline in section 5. They are earlier drafts, not the book text, but together they cover almost all of its substance. Larson's tag page [elegant-puzzle](https://lethain.com/tags/elegant-puzzle/) collects his posts about the book itself.
- **Free excerpt-length article:** [First Round Review, "How to Size and Assess Teams From an Eng Lead at Stripe, Uber and Digg"](https://firstround.com/review/how-to-size-and-assess-teams-from-an-eng-lead-at-stripe-uber-and-digg/) (24 May 2019), built on the team-sizing and four-states material.
**Where to get it.**
- **Publisher:** [Stripe Press](https://press.stripe.com/an-elegant-puzzle) ($35 hardcover; the catalog also links to Amazon, Bookshop and Barnes & Noble).
- **Amazon print:** [hardcover, 1732265186](https://www.amazon.com/dp/1732265186), Stripe Press, 20 May 2019, 288 pp. $23.16 (list $35) when checked on 2026-11-18. No paperback edition is listed.
- **Kindle:** [Kindle edition, B07QYCHJ7V](https://www.amazon.com/dp/B07QYCHJ7V). Available; $12.99 when checked on 2026-11-18.
- **Audible:** available, read by Tiffany Morgan, 6 h 36 min, unabridged ([B07SH1DXXM on Amazon](https://www.amazon.com/dp/B07SH1DXXM)). Audible's own page returned 404 from my box ([audible.com/pd/B07SH1DXXM](https://www.audible.com/pd/B07SH1DXXM)).
- **Other retailers:** [Bookshop.org](https://bookshop.org/books/an-elegant-puzzle-systems-of-engineering-management/9781732265189); [Barnes & Noble](https://www.barnesandnoble.com/w/an-elegant-puzzle-will-larson/1141909303?ean=9781732265189) (hardcover, $35, in stock on 2026-11-18).
- **Libby/OverDrive:** the ebook is available (OverDrive title 6494508, distributed through Kobo Writing Life, added to OverDrive August 2021). On 2026-11-18 it was in the Los Angeles, New York and San Francisco public library catalogs ([LAPL](https://lapl.overdrive.com/media/6494508); [NYPL](https://nypl.overdrive.com/media/6494508); [SFPL](https://sfpl.overdrive.com/media/6494508)). Chicago Public Library's OverDrive search returned nothing. I found no OverDrive audiobook.
- **Hoopla:** not checked reliably. Its search needs JavaScript and returned nothing usable to my box.
- **Internet Archive lending / Open Library borrow:** not available. The Internet Archive has no copy of the book (only podcast mirrors of the Developer Tea episodes), and Open Library marks the work "no ebook".
- **Project Gutenberg:** not applicable (in copyright).
**Catalog records.** [Google Books](https://books.google.com/books?id=_eKnkw8cYssC) (Stripe Matter Incorporated 2019, 285 pp., partial contents: Preface p. 7, Organizations p. 31, Tools p. 61); [Open Library](https://openlibrary.org/works/OL20641522W); [WorldCat OCLC 1105154200](https://search.worldcat.org/title/1105154200).
**Cover:** [Open Library cover image](https://covers.openlibrary.org/b/id/9260083-L.jpg).
## 3. Author biography
**Will Larson** is an American software engineering leader and writer. He has no Wikipedia article. Wikidata describes him as "Software engineering leader and technology writer" ([Q136799836](https://www.wikidata.org/wiki/Q136799836)).
- **Early life and education.** "I grew up in North Carolina, studied computer science at Centre College in Kentucky, and spent a year in Japan on the JET Program" ([lethain.com/about](https://lethain.com/about/)). The book's author note says he taught English in Japan through the JET Programme ([Abbey's](https://www.abbeys.com.au/api/product.do?isbn=9781732265189)). Imprint's 2025 press release confirms a BS in Computer Science from Centre College ([Business Wire](https://www.businesswire.com/news/home/20250603237278/en/Imprint-Appoints-Will-Larson-as-Chief-Technology-Officer)).
- **Career before the book.** He co-founded a now-defunct iOS game studio, Monocle Studios, with Luke Hatcher ([lethain.com/about](https://lethain.com/about/)). The book's author note lists Yahoo!, Digg, SocialCode, Uber and Stripe. His public profile (as summarized by a search engine; I did not open LinkedIn) gives Yahoo 2008–10, Digg (director of engineering) 2010–12, SocialCode (VP of platform technology) 2012–14, Uber (senior engineering manager, infrastructure) June 2014–June 2016, and Stripe (founding head of Foundation Engineering) June 2016–January 2020 ([LinkedIn](https://linkedin.com/in/lethain); [Cosign](https://cosign.co/lethain)). Treat the exact months as **unverified**. The Digg-to-SocialCode move followed Digg's sale and is the setting of the "growth plates" essay.
- **After the book.** CTO of Calm (2020–23), then CTO of Carta (2023–25), and since mid-2025 CTO of Imprint, a co-branded credit card company ([Business Wire, 3 June 2025](https://www.businesswire.com/news/home/20250603237278/en/Imprint-Appoints-Will-Larson-as-Chief-Technology-Officer); [FinTech Futures](https://www.fintechfutures.com/job-cuts-new-hires/former-stripe-exec-will-larson-named-new-imprint-cto); [lethain.com/about](https://lethain.com/about/)).
- **Writing.** He has kept the blog *Irrational Exuberance* since 2007. His four books are *An Elegant Puzzle* (2019), *Staff Engineer* (2021), *The Engineering Executive's Primer* (2024) and *Crafting Engineering Strategy* (2025) ([lethain.com/about](https://lethain.com/about/)). He lives with his family in San Francisco.
- **How the book was made.** He wrote about seventy blog posts in 2018 and was approached by several publishers. He chose Stripe Press partly because it "typically buy[s] completed manuscripts, rather than proposals". He outlined the book, wrote each section as a blog post ("roughly eight hours each week from early mornings and weekends"), and then worked with Stripe Press's Brianna and Tyler on the cover, diagrams and layout. The release slipped from late March to late May 2019 ([What I learned writing a book](https://lethain.com/learned-writing-book/); [An Elegant Puzzle coming in late May](https://lethain.com/elegant-puzzle-update-april/)).
## 4. Author interviews and talks
Larson's own list is [Elegant Puzzle press, reviews and podcasts](https://lethain.com/elegant-puzzle-press/). By October 2019 he counted "twelve podcast episodes across 8 podcasts". Several of the original links have since gone dead.
- **Software Engineering Daily, "Elegant Puzzle with Will Larson" (14 June 2019).** Larson called it his favorite podcast appearance: distributing desirable and undesirable work, Stripe's incident program and more ([SE Daily](https://softwareengineeringdaily.com/2019/06/14/elegant-puzzle-with-will-larson/); [Larson's note](https://lethain.com/aep-software-engineering-daily/)).
- **Software Engineering Daily, "An Elegant Puzzle Virtual Book Club" (11 Aug 2019, about 43 min).** Larson with Uma Chingunde of Stripe and host Jeff Meyerson on engineering-management techniques for scaling organizations ([SE Daily](https://softwareengineeringdaily.com/2019/08/11/an-elegant-puzzle-virtual-book-club/)).
- **Know Your Team podcast, Episode 45 (21 Aug 2019).** Interview covering decisions that are not final, self-awareness, and modeling behavior. Video on YouTube ([Know Your Team](https://knowyourteam.com/blog/podcast/episode-45-interview-with-will-larson-head-of-foundation-engineering-at-stripe-and-author-of-an-elegant-puzzle/); [YouTube](https://youtu.be/vvswruOi4nE)).
- **Programming Leadership with Marcus Blankenship, Episode 20, "Managing to Solve an Elegant Puzzle" (2019).** The episode page's summary is about giving feedback ([Marcus Blankenship](https://marcusblankenship.com/managing-to-solve-an-elegant-puzzle-with-will-larson/)).
- **Developer Tea, "An Elegant Puzzle Book Discussion," Parts 1–3 (6, 8 and 10 July 2019).** A three-part conversation about the book. The original spec.fm links are dead. Internet Archive podcast mirrors exist: [Part 1](https://archive.org/details/1tpedmo69s4wa6rdgz6eq1uoivojz5ktewkkryt1), [Part 2](https://archive.org/details/eaanbpgk1ehtktrbuszavvrgup1davvkwhjlwfir), [Part 3](https://archive.org/details/3oh7vu0lagtup9qkdnh6hz88gky2lzdqjgroaixh). I did not listen to them.
- **Greater Than Code, Episode 142, "Modeling Constraints in Human Systems with Will Larson" (7 Aug 2019).** Systems thinking applied to teams. The original link is now 404 ([as listed by Larson](https://lethain.com/elegant-puzzle-press/)).
- **Also listed by Larson, links now dead or unreachable:** Frontier @ Gun.io, Episode 75 (17 June 2019, author interview); People Stack, Episode 77 (7 July 2019); Woven, "An Elegant Puzzle," Parts 1 and 2 (16 and 23 July 2019).
- **Print:** [First Round Review feature](https://firstround.com/review/how-to-size-and-assess-teams-from-an-eng-lead-at-stripe-uber-and-digg/) (24 May 2019) on team sizing and the four team states. Charity Majors ran a summer 2019 reading group ([charity/elegant-puzzle-discuss](https://github.com/charity/elegant-puzzle-discuss)).
- **Larson writing about the book:** [What I learned writing a book](https://lethain.com/learned-writing-book/) (8 June 2019): process, marketing, Amazon economics, the Accelerate misattribution. [An Elegant Puzzle by the numbers, five months later](https://lethain.com/aep-five-months-later/) (23 Oct 2019): sales and reach.
## 5. Summary
**Thesis.** Engineering management in a fast-growing company is a puzzle made of systems. Team size, team health, technical debt, hiring and career levels all interact, and they respond to structural fixes far more than to individual heroics. Larson's recurring advice is to diagnose which system is binding (for example, is the team falling behind or treading water?), apply the one fix that fits that state, and then keep faith with it long enough to work. He pairs this with an explicitly ethical view of the job: managers shape people's pay, opportunities and working lives, so consistency and fairness are themselves goals.
**Outline.** The table of contents is from the bookseller listing at [Abbey's](https://www.abbeys.com.au/api/product.do?isbn=9781732265189) (as indexed by a search engine; the page did not render the contents to my fetch). It matches the chapter and section headings in [Keyvan Akbary's reading notes](https://keyvanakbary.github.io/learning-notes/books/an-elegant-puzzle/) and the partial contents on Google Books (Preface p. 7; Organizations p. 31; Tools p. 61). The front matter has a Preface and Acknowledgments. Each section is followed by its blog counterpart and that post's date.
- **1. Introduction.** No blog counterpart found; not read.
- **2. Organizations.**
- *2.1 Sizing teams* ([Sizing engineering teams, 14 Jul 2018](https://lethain.com/sizing-engineering-teams/)). Managers should support 6–8 engineers; managers of managers 4–6 managers; a two-tier 24/7 on-call rotation wants 8 engineers. "Small teams (<4) are not teams", and on sponsoring 1–2 person teams: "I have regretted it every single time" (blog). Playbook: grow a team to 8–10, then split into two teams of 4–5; "Never create empty teams" (blog).
- *2.2 Staying on the path to high-performing teams* ([durably-excellent-teams, 17 Jun 2018](https://lethain.com/durably-excellent-teams/)). The **four states of a team**: *falling behind* (backlog grows weekly), *treading water* (critical work done, no debt repayment), *repaying debt*, *innovating*. Each has one system fix: hire (falling behind); consolidate and limit work in progress (treading water); add time (repaying debt); add slack (innovating). Concentrate limited resources on a few teams rather than "peanut buttering" them across all of them. The fixes are slow but durable.
- *2.3 A case against top-down global optimization* ([23 Jun 2018](https://lethain.com/case-against-top-down-global-optimization/)). Don't break up gelled, high-performing teams to chase shifting priorities ("team first"). Teams have high fixed costs and need slack. Instead, shift *scope* between teams, or rotate individuals.
- *2.4 Productivity in the age of hypergrowth* ([10 Oct 2016](https://lethain.com/productivity-in-the-age-of-hypergrowth/)). From his Uber years ("almost 1,000 employees and doubling headcount every six months" when he joined): "We're growing so quickly, that every six months we're a new company" / "Which means our process is always six months behind our headcount" (blog). More engineers bring more coordination load; **systems survive about one order of magnitude of growth**; to manage entropy, concentrate hiring rather than spreading it, and make sure some projects actually finish (a lesson he takes from *The Phoenix Project*).
- *2.5 Where to stash your organizational risk?* ([13 Jun 2018](https://lethain.com/organizational-risk/)). Organizational debt (biased interviews, inequitable pay) and its volatile subset, organizational risk. Don't spread risk thin: pick a few areas to fix, "give yourself permission to do the rest poorly" (blog), agree the plan with your manager, and keep unsolvable risks yourself rather than pushing them into healthy teams.
- *2.6 Succession planning* ([23 Jul 2018](https://lethain.com/succession-planning/)). List what you actually do (starting from your calendar, among other angles) and find the gaps that would open if you left. Then split them into the easiest gaps to close and the riskiest ones.
- **3. Tools.**
- *3.1 Introduction to systems thinking* ([4 Sep 2018](https://lethain.com/systems-thinking/)). Stocks and flows (after Donella Meadows's *Thinking in Systems*). It models developer velocity using the four measures from *Accelerate*: delivery lead time, deployment frequency, change fail rate and time to restore service. It closes by urging readers to model hard problems as systems ("Model away"), with tools such as Stella or InsightMaker.
- *3.2 Product management: exploration, selection, validation* ([Problem exploration, selection and validation, 20 Aug 2018](https://lethain.com/intro-product-management/)). For engineering managers covering a product role: problem discovery (starting from users' pain and users' purpose), problem selection, and cheap solution validation, run as an "iterative elimination tournament".
- *3.3 Visions and strategies* ([Writing strategies and visions, 9 Jul 2018](https://lethain.com/strategies-visions/)). Strategies are grounded documents about specific challenges; visions are aspirational, long-term documents that let teams who don't work closely together make decisions that fit together. Covers what goes into a vision (beginning with a one- or two-sentence vision statement and a value proposition) and advises refreshing it every year.
- *3.4 Metrics and baselines* ([Goals and baselines, 5 Jul 2018](https://lethain.com/goals-and-baselines/)). A good goal combines a target, a baseline, a trend and a timeframe. Baseline metrics guard against regressions while you pursue other goals.
- *3.5 Guiding broad organizational change with metrics* ([Guiding broad change with metrics, 6 Jul 2018](https://lethain.com/guiding-broad-change-with-metrics/)). From managing infrastructure cost at Uber and Stripe: explore the data, dive into the three or four biggest drivers, attribute costs to the teams that really drive them, contextualize with benchmarks, nudge, set baselines, and review. This is change led with little or no formal authority.
- *3.6 Migrations: the sole scalable fix to tech debt* ([15 Apr 2018](https://lethain.com/migrations/)). "Migrations are the only mechanism to effectively manage technical debt as your company and code grow" (blog). The playbook is **derisk** (shop the design doc with the hardest teams first), **enable** (make migrating cheap for the teams), **finish** (first "stop the bleeding" so all new code uses the new approach, then push to 100% adoption, and finish it yourself if you must). The case study is Uber's move from Puppet-managed services to two-click self-service provisioning.
- *3.7 Running an engineering reorg* ([17 Mar 2017](https://lethain.com/running-an-engineering-reorg/)). Validate that a reorg is the right tool. The two best reorgs are one that solves a structural problem and "the one that you don't do"; the worst is "the one you do because you're avoiding a people management issue" (blog). Then project headcount a year out, set a manager-to-engineer ratio, define teams and groups, staff them, commit, and roll out.
- *3.8 Identify your controls* ([21 Jul 2018](https://lethain.com/identify-your-controls/)). When you manage managers, agree explicitly on the mechanisms by which you engage: metrics, visions, strategies, roadmaps, org design, headcount, performance reviews. Then agree the degree of alignment for each one, for example "I'll do it", preview, review, notes, "let me know" or "no surprises".
- *3.9 Career narratives* ([26 Sep 2018](https://lethain.com/career-narratives/)). Most people default to "get promoted" or "switch companies" ("artificial competition"). A written career narrative names real goals, and a manager helps translate them into projects that also serve the business.
- *3.10 The briefest of media trainings* ([24 Jun 2018](https://lethain.com/briefest-of-media-trainings/)). Five minutes of training he got at Digg: answer the question you want to be asked, stay positive, speak in threes.
- *3.11 Model, document, and share* ([26 Apr 2018](https://lethain.com/model-document-share/)). Instead of mandating a practice (his example is Kanban), try it on your own team, measure, write it up and share it, and let others adopt it. This works when a great approach adopted slowly beats a good one adopted quickly.
- *3.12 Scaling consistency: designing centralized decision-making groups* ([Scaling technical consistency, 30 Jul 2018](https://lethain.com/scaling-consistency/)). Use positive and negative freedoms to judge when an architecture or review group is warranted. Design choices include influence, interface and size (six or fewer can gel into a real team; more than ten struggles to discuss). Failure modes: such groups "tend to be domineering, bottlenecks, status-oriented or inert" (blog).
- *3.13 Presenting to senior leadership* ([Presenting to executives, 6 Aug 2018](https://lethain.com/presenting-to-executives/)). Communication norms are company-specific, so study successful presenters. Frame why the topic matters, prepare for detours, answer directly, and close with an explicit ask. Template: tie to business value → history → explicit ask → data-driven diagnosis → principles → what's next.
- *3.14 Time management* ([Time management: the leadership meta-problem, 27 Aug 2018](https://lethain.com/time-management/)). Quarterly time retrospectives, stop doing things, size backwards, trust the systems you build, hire slightly ahead of growth, block your calendar, get administrative support.
- *3.15 Communities of learning* ([1 Sep 2018](https://lethain.com/communities-of-learning/)). Running learning groups for managers: small breakouts that report back, topics people already know something about, optional pre-reads, check-ins.
- **4. Approaches.**
- *4.1 Work the policy, not the exceptions* ([23 Sep 2018](https://lethain.com/work-policy-not-exceptions/)). Good policy is opinionated, a small strategy. Each exception adds "exception debt". Rather than granting exceptions, collect each escalation as a test case and periodically revise the policy's constraints. His example is a policy for which teams remote and multi-office employees can join.
- *4.2 Saying no* ([23 Sep 2018](https://lethain.com/saying-no/)). Saying no well means explaining constraints. Show how the team *finishes* work (velocity), then move the discussion to explicit priorities. If neither lands, the problem is the relationship.
- *4.3 Your philosophy of management* ([7 May 2016](https://lethain.com/philosophy-of-management/)). Management as an ethical profession; strong relationships beat any problem; people over process ("With the right people, any process works, and with the wrong people, no process works", quoted from a colleague; blog); do the hard thing now; "do the right thing for the company, the right thing for the team, and the right thing for you, in that order" (blog); think for yourself rather than cargo-cult.
- *4.4 Managing in the growth plates* ([21 Mar 2018](https://lethain.com/managing-growth-plates/)). After Digg was acquired by SocialCode he learned that leadership differs by context. In fast-growing areas "execution is the primary currency in the growth plates" (blog); away from them, where problems have known solutions, new ideas are what get prized. Align with your company's values.
- *4.5 Ways engineering managers get stuck* ([3 Mar 2017](https://lethain.com/ways-engineering-managers-get-stuck/)). Lists of failure patterns for new managers (only managing down, only managing up, never managing up, optimizing locally), for experienced managers, and for everyone.
- *4.6 Partnering with your manager* ([13 Mar 2017](https://lethain.com/partnering-with-your-manager/)). What your manager should know about you (problems, approach, progress, preferences, goals, where you are between bored and challenged), and the reverse.
- *4.7 Finding managerial scope* ([31 Oct 2016](https://lethain.com/finding-managerial-scope/)). Don't equate growth with headcount. Leading a broad project across fifty managers teaches more than managing fifty people, so look for gaps and fill them.
- *4.8 Setting organizational direction* ([9 May 2018](https://lethain.com/setting-organizational-direction/)). As your scope grows, feedback becomes scarce and direction vague. Mine for direction by talking to colleagues, peers and peer companies, and by reading technical papers.
- *4.9 Close out, solve, or delegate* ([29 Mar 2018](https://lethain.com/close-out-solve-or-delegate/)). "The skill that scales the worst is outworking your problems" (blog). Each incoming problem should be closed out permanently, solved for the next six months with a process or norm, or delegated.
- **5. Culture.**
- *5.1 Opportunity and membership* ([Opportunity & Membership, 17 Jul 2018](https://lethain.com/membership-opportunity/)). His framework for inclusion: "Opportunity is having access to professional success and development. Membership is participating as a version of themselves they feel comfortable with" (blog). Includes notes on investment and measurement for each.
- *5.2 Select project leads* ([Selecting project leads, 12 Jul 2018](https://lethain.com/selecting-project-leads/)). A wide cohort of people who lead critical projects is a sign of organizational health. Replace pinging a favored person with a slower, deliberate selection process. Larson calls this "the most important change in my approach to leadership over the past few years" (blog).
- *5.3 Make your peers your first team* ([8 Aug 2018](https://lethain.com/first-team/)). Managers often belong to no real team. Build the peer group into the "first team", starting with awareness of each other's work and getting to know peers as people rather than characters.
- *5.4 Consider the team you have for senior positions* ([internal-candidates-for-senior-management, 19 May 2018](https://lethain.com/internal-candidates-for-senior-management/)). For manager-of-managers searches, run a fair process for internal candidates. The post also cites processes like the Rooney Rule.
- *5.5 Company culture and managing freedoms* ([9 Feb 2014](https://lethain.com/company-culture-and-managing-freedoms/)). Reads company culture through positive freedoms (freedom to) and negative freedoms (freedom from), the distinction he reuses in 3.12. The blog version opens with "Me and Bobby McGee".
- *5.6 Kill your heroes, stop doing it harder* ([25 Nov 2012](https://lethain.com/doing-it-harder-and-hero-programming/)). "Work harder" breeds hero programmers who burn out and shut others out. Reset broken systems instead.
- **6. Careers.**
- *6.1 Roles over rocket ships, and why hypergrowth is a weak predictor of personal growth* ([2 Jan 2018](https://lethain.com/roles-over-rocket-ships/)). Careers alternate between eras and transitions. Choose roles that make you learn, because "growth only comes from change" (blog), and a fast-growing company does not guarantee it. He challenges the "seat on a rocket ship" advice (see section 6).
- *6.2 Running a humane interview process* ([9 Jun 2016](https://lethain.com/running-humane-interview-process/)). Be kind; know what role you're hiring for; find signal; be prepared; deliberately express interest; build feedback loops; optimize the funnel.
- *6.3 Cold sourcing: hire someone you don't know* ([8 Jan 2018](https://lethain.com/cold-sourcing/)). Referrals reproduce your network's sameness. A recipe for reaching strangers, mainly through LinkedIn, and a judgment that this is high-leverage work for managers.
- *6.4 Hiring funnel* ([Your hiring funnel, 1 Aug 2018](https://lethain.com/hiring-funnel/)). Funnel stages from identify and motivate through evaluate and close. Instrument and optimize them, and extend the funnel to onboarding, impact, promotion and retention.
- *6.5 Performance management systems* ([Designations, levels and calibrations, 10 Aug 2018](https://lethain.com/perf-management-system/)). Career ladders, performance designations and cycles. Calibration advice: read, don't present; compare against the ladder, not against others; study the distribution, don't enforce it. Points to Laszlo Bock's *Work Rules!*.
- *6.6 Career levels, designation momentum, level splits, etc.* ([Career levels, designation momentum, etc., 11 Aug 2018](https://lethain.com/career-levels-and-more/)). Named failure patterns in leveling: designation momentum, tit for tat, level expansion and drift, opening of the gates, time-at-level limits, level splits, crisis designations.
- *6.7 Creating specialized roles, like SRE or TPMs* ([Introducing SREs, TPMs and other specialized roles, 13 Aug 2018](https://lethain.com/specialized-roles/)). Challenges (class systems, brittle organizations, task offloading, roles "too trivial" to value or promote, hard to recruit or evaluate). What makes them succeed: an executive sponsor, a recruiting partner, a self-sustaining mission, a career ladder, a role model.
- *6.8 Designing an interview loop* ([Designing interview loops, 2 Sep 2018](https://lethain.com/designing-interview-loops/)). Metrics first; learn from the current loop and from peers; identify the skills; test each one with a rubric (avoid boolean rubrics and testing for polish); group tests into interviews; run the loop and review the funnel.
- **7. Appendix.**
- *7.1 Tools for operating a growing organization* ([18 Nov 2017](https://lethain.com/tools-for-operating-a-growing-org/)). Toolkits by level: line management (for example, well-run sprints), middle management (roadmaps, supporting two to five line managers), and managing an organization.
- *7.2 Books I've found very useful* (closest blog counterpart: [Book recommendations, 24 Jul 2018](https://lethain.com/best-books/)).
- *7.3 Papers I've found very useful* (closest blog counterpart: [Some of my favorite technical papers, 7 Apr 2018](https://lethain.com/some-of-my-favorite-technical-papers/)). The Pragmatic Engineer singles out this appendix list ([Gergely Orosz's reading list](https://blog.pragmaticengineer.com/my-reading-list/)). I did not see the book's actual lists, so the blog lists may differ.
**Key ideas.**
- **Diagnose the team's state, then apply that state's one fix.** Hiring helps a team that is falling behind; adding more people to a team that is treading water mostly adds work in progress.
- **Team size is the base of organizational design.** 6–8 engineers per manager; teams below four are not teams; grow teams and then split them; never create empty teams.
- **Technical debt is paid down by migrations,** and good migrations are mostly about tooling, defaults and finishing.
- **Lead change through models, metrics and documents, not mandates.** Systems models, baselines and goals, strategies and visions, written policy, and "model, document, share" let leaders steer without micromanaging.
- **Structural fixes over heroics.** Kill hero culture, don't outwork your problems, work the policy rather than the exceptions, and protect slack.
- **Management is ethical work.** Fair processes (interviews, calibrations, project-lead selection, opportunity and membership) are central to the job, not soft extras.
- **Your own growth comes from scope and change, not headcount.**
**Reception.** Gergely Orosz (The Pragmatic Engineer) called it "the most hands-on perspective on engineering management within a high-growth, tech-first organization" he had read. He noted it skips the generic manager's toolkit (1:1s, feedback) and "starts right where the others end", and that it best fits "top tier" Silicon Valley-style engineering cultures ([review, 31 Jul 2019](https://blog.pragmaticengineer.com/an-elegant-puzzle-book-review/)). Cindy Sridharan reviewed it on Medium ([link](https://medium.com/@copyconstruct/book-review-an-elegant-puzzle-f787ad381ce0); 403 to my box, not read). Amazon showed 4.4/5 from 1,425 ratings on 2026-11-18. Among the review highlights Amazon displays, the critical ones say it reads like a collection of the author's articles with no connecting story. Larson himself said the book "would have been stronger" with more rework time, and that it "annoyed a decent number of people".
## 6. Fact-check
Claims below come from the blog versions of the sections (and Larson's posts about the book), since I did not have the printed text.
| Claim | Verdict | Evidence |
|---|---|---|
| Published by Stripe Press in 2019; ISBN 9781732265189 | Supported | [Stripe Press catalog data](https://stripe.press/catalog.json); [Amazon](https://www.amazon.com/dp/1732265186) |
| Release date 28 May 2019 (queue entry; Larson's launch post) | **Partly disputed** | Retailers, OverDrive and Larson's own Oct 2019 post give 20 May 2019. 28 May was the announced launch day and the Kindle date ([lethain.com](https://lethain.com/aep-five-months-later/); [Amazon Kindle](https://www.amazon.com/dp/B07QYCHJ7V)) |
| Page count 288 | Supported, with variants | 288 (Stripe Press, Amazon hardcover, Abbey's); 285 (Open Library, Google Books); 289 (Kindle print length) |
| Larson's experience "at Digg, Uber, and Stripe" | Supported | [lethain.com/about](https://lethain.com/about/); [Business Wire](https://www.businesswire.com/news/home/20250603237278/en/Imprint-Appoints-Will-Larson-as-Chief-Technology-Officer); author note lists Yahoo!, Digg, SocialCode, Uber, Stripe |
| Uber had "almost 1,000 employees and doubl[ed] headcount every six months" when Larson joined (mid-2014) | Supported (consistent) | Kalanick said Uber had about 550 employees in January 2014 and expected 1,500–2,000 by year end ([The Verge](https://www.theverge.com/2014/1/8/5287900/uber-ceo-defends-surge-pricing-promises-rapid-growth-in-2014)); over 3,500 by Aug 2015 ([Forbes](https://www.forbes.com/sites/liyanchen/2015/08/11/the-most-valuable-employees-snapchat-doubles-facebook/)) |
| *Accelerate*'s four measures are delivery lead time, deployment frequency, change fail rate and time to restore service | Supported | The DORA "four key metrics" ([Wikipedia: DORA](https://en.wikipedia.org/wiki/DevOps_Research_and_Assessment)) |
| *Accelerate* is based on "surveys from tens of thousands of organizations" (blog 3.1) | **Disputed (overstated)** | The authors report "over 23,000 survey responses" from "over 2,000 unique organizations" ([IT Revolution excerpt, PDF](https://itrevolution.com/wp-content/uploads/2022/06/ACC_excerpt.pdf)). Book wording not checked |
| Lead author of *Accelerate* (as printed in the book) | **Disputed (author's admission)** | Larson says he "misattributed the lead author – the remarkable Nicole Forsgren" in print and could only fix the digital versions ([What I learned writing a book](https://lethain.com/learned-writing-book/)). DORA was founded by Forsgren, Humble and Kim ([Wikipedia](https://en.wikipedia.org/wiki/DevOps_Research_and_Assessment)) |
| "If you're offered a seat on a rocket ship, don't ask what seat! Just get on." attributed to Sheryl Sandberg (blog 6.1) | **Partly disputed** | Sandberg used it in her 2012 HBS speech, but she was quoting Eric Schmidt's advice to her in 2001 ([Business Insider](https://www.businessinsider.com/the-brilliant-career-advice-google-ceo-eric-schmidt-gave-sheryl-sandberg-2012-5); [Barry Popik](https://barrypopik.com/blog/if_youre_offered_a_seat_on_a_rocket_ship)). Whether the book keeps the Sandberg attribution is unverified |
| "Forty years ago Roger Miller (and later, much more famously, Janis Joplin) sang: 'Freedom's just another word for nothing left to lose'" (blog 5.5, 2014) | Supported (approximate) | Kris Kristofferson and Fred Foster wrote the song. Roger Miller recorded it first (May 1969), and Joplin's version topped the charts in 1971 ([Wikipedia](https://en.wikipedia.org/wiki/Me_and_Bobby_McGee)). "Forty years" from 2014 is closer to 45 |
| Pearl Buck's *The Good Earth*: "All power comes from the Earth" (blog 4.5) | Unverified | The novel (1931) is real ([Wikipedia](https://en.wikipedia.org/wiki/The_Good_Earth)); I did not find this wording in it |
| *The Phoenix Project*: "you only get value from projects when they finish" (blog 2.4) | Unverified (paraphrase) | Larson presents it as his "favorite observation" from the novel, not a quotation. Not checked against the text |
| *Thinking in Systems* by Donella Meadows as the systems-thinking primer | Supported | [Wikipedia](https://en.wikipedia.org/wiki/Thinking_In_Systems%3A_A_Primer) |
| The Rooney Rule as a model for fair senior searches | Supported (as described) | The NFL rule requiring minority candidates to be interviewed for head-coach jobs ([Wikipedia](https://en.wikipedia.org/wiki/Rooney_Rule)) |
| Team-size numbers (6–8 engineers per manager; 4–6 managers per manager of managers; 8 for on-call) | Opinion / rule of thumb | Larson calls them "short, opinionated" guidelines, not empirical findings |
| "Migrations are the only mechanism to effectively manage technical debt" | Opinion | An argued position, not a factual claim |
| 12,780 copies sold by 22 Oct 2019; 27,000 printed | Supported (author's self-report) | [An Elegant Puzzle by the numbers](https://lethain.com/aep-five-months-later/); no independent sales data checked |
| Endnotes printed as QR codes | Supported (author's statement) | [What I learned writing a book](https://lethain.com/learned-writing-book/) |
## 7. Citations and references
**Notable sources the book uses or recommends** (from the blog counterparts; I did not see the book's endnotes or appendix lists)
- Donella Meadows, *Thinking in Systems: A Primer* (2008), the basis of 3.1 ([Wikipedia](https://en.wikipedia.org/wiki/Thinking_In_Systems%3A_A_Primer))
- Nicole Forsgren, Jez Humble & Gene Kim, *Accelerate* (2018): the four delivery metrics ([IT Revolution excerpt](https://itrevolution.com/wp-content/uploads/2022/06/ACC_excerpt.pdf))
- Gene Kim, Kevin Behr & George Spafford, *The Phoenix Project* (2013) (not linked)
- Camille Fournier, *The Manager's Path* (2017), which Larson credits with opening the market for engineering-management books (not linked)
- Laszlo Bock, *Work Rules!* (2015), on performance systems (not linked)
- Larson's 2018 book list (blog counterpart of 7.2), ordered roughly most to least valuable: *Thinking in Systems*; George Lakoff, *Don't Think of an Elephant!*; DeMarco & Lister, *Peopleware*; Tom DeMarco, *Slack*; Fred Brooks, *The Mythical Man-Month*; Richard Rumelt, *Good Strategy Bad Strategy*; Eliyahu Goldratt, *The Goal* (queue #481); Patrick Lencioni, *The Five Dysfunctions of a Team* and *The Three Signs of a Miserable Job*; James Carse, *Finite and Infinite Games*; Marty Cagan, *Inspired*; Clayton Christensen, *The Innovator's Dilemma*; Michael Gerber, *The E-Myth Revisited*; Susan Scott, *Fierce Conversations*; and, later in the list, Andy Grove, *High Output Management*; Michael Watkins, *The First 90 Days*; Tom DeMarco, *The Deadline*; Gerald Weinberg, *The Psychology of Computer Programming*; and Lencioni, *Death by Meeting* ([Book recommendations](https://lethain.com/best-books/))
- Larson's 2018 paper list (blog counterpart of 7.3), including the Dynamo paper (DeCandia et al. 2007), Lampson's "Hints for Computer System Design", "Big Ball of Mud", the Google File System, Hamilton's "On Designing and Deploying Internet-Scale Services", MapReduce, Dapper, Kafka, Borg and Omega, Raft, "Paxos Made Simple", SWIM, "The Byzantine Generals Problem", "Out of the Tar Pit", Chubby, Bigtable, Spanner, BeyondCorp, and Google's papers on ClangMR refactoring and build debt ([Some of my favorite technical papers](https://lethain.com/some-of-my-favorite-technical-papers/), which links each paper)
- Pearl S. Buck, *The Good Earth* (1931), quoted in 4.5 ([Wikipedia](https://en.wikipedia.org/wiki/The_Good_Earth))
- Kris Kristofferson & Fred Foster, "Me and Bobby McGee", quoted in 5.5 ([Wikipedia](https://en.wikipedia.org/wiki/Me_and_Bobby_McGee))
**Every link used**
- Publisher and catalog: [Stripe Press book page](https://press.stripe.com/an-elegant-puzzle); [Stripe Press catalog](https://press.stripe.com/); [Stripe Press catalog data](https://stripe.press/catalog.json); [Open Library work](https://openlibrary.org/works/OL20641522W); [OL hardcover OL27905593M](https://openlibrary.org/books/OL27905593M); [OL ebook OL48516606M](https://openlibrary.org/books/OL48516606M); [Open Library cover](https://covers.openlibrary.org/b/id/9260083-L.jpg); [Google Books](https://books.google.com/books?id=_eKnkw8cYssC); [WorldCat OCLC 1105154200](https://search.worldcat.org/title/1105154200); [Abbey's listing](https://www.abbeys.com.au/api/product.do?isbn=9781732265189); [Wikidata Q136799836](https://www.wikidata.org/wiki/Q136799836)
- Retail and libraries: [Amazon hardcover](https://www.amazon.com/dp/1732265186); [Amazon Kindle](https://www.amazon.com/dp/B07QYCHJ7V); [Amazon audiobook listing](https://www.amazon.com/dp/B07SH1DXXM); [Audible](https://www.audible.com/pd/B07SH1DXXM); [Bookshop.org](https://bookshop.org/books/an-elegant-puzzle-systems-of-engineering-management/9781732265189); [Barnes & Noble](https://www.barnesandnoble.com/w/an-elegant-puzzle-will-larson/1141909303?ean=9781732265189); [OverDrive LAPL](https://lapl.overdrive.com/media/6494508); [OverDrive NYPL](https://nypl.overdrive.com/media/6494508); [OverDrive SFPL](https://sfpl.overdrive.com/media/6494508)
- Larson on the book: [An Elegant Puzzle: Systems of Eng Management](https://lethain.com/elegant-puzzle/); [elegant-puzzle tag](https://lethain.com/tags/elegant-puzzle/); [coming in late May](https://lethain.com/elegant-puzzle-update-april/); [press, reviews and podcasts](https://lethain.com/elegant-puzzle-press/); [What I learned writing a book](https://lethain.com/learned-writing-book/); [by the numbers](https://lethain.com/aep-five-months-later/); [SE Daily note](https://lethain.com/aep-software-engineering-daily/); [QR codes](https://lethain.com/qr-codes-in-books/)
- Blog counterparts of the sections: [sizing-engineering-teams](https://lethain.com/sizing-engineering-teams/); [durably-excellent-teams](https://lethain.com/durably-excellent-teams/); [case-against-top-down-global-optimization](https://lethain.com/case-against-top-down-global-optimization/); [productivity-in-the-age-of-hypergrowth](https://lethain.com/productivity-in-the-age-of-hypergrowth/); [organizational-risk](https://lethain.com/organizational-risk/); [succession-planning](https://lethain.com/succession-planning/); [systems-thinking](https://lethain.com/systems-thinking/); [intro-product-management](https://lethain.com/intro-product-management/); [strategies-visions](https://lethain.com/strategies-visions/); [goals-and-baselines](https://lethain.com/goals-and-baselines/); [guiding-broad-change-with-metrics](https://lethain.com/guiding-broad-change-with-metrics/); [migrations](https://lethain.com/migrations/); [running-an-engineering-reorg](https://lethain.com/running-an-engineering-reorg/); [identify-your-controls](https://lethain.com/identify-your-controls/); [career-narratives](https://lethain.com/career-narratives/); [briefest-of-media-trainings](https://lethain.com/briefest-of-media-trainings/); [model-document-share](https://lethain.com/model-document-share/); [scaling-consistency](https://lethain.com/scaling-consistency/); [presenting-to-executives](https://lethain.com/presenting-to-executives/); [time-management](https://lethain.com/time-management/); [communities-of-learning](https://lethain.com/communities-of-learning/); [work-policy-not-exceptions](https://lethain.com/work-policy-not-exceptions/); [saying-no](https://lethain.com/saying-no/); [philosophy-of-management](https://lethain.com/philosophy-of-management/); [managing-growth-plates](https://lethain.com/managing-growth-plates/); [ways-engineering-managers-get-stuck](https://lethain.com/ways-engineering-managers-get-stuck/); [partnering-with-your-manager](https://lethain.com/partnering-with-your-manager/); [finding-managerial-scope](https://lethain.com/finding-managerial-scope/); [setting-organizational-direction](https://lethain.com/setting-organizational-direction/); [close-out-solve-or-delegate](https://lethain.com/close-out-solve-or-delegate/); [membership-opportunity](https://lethain.com/membership-opportunity/); [selecting-project-leads](https://lethain.com/selecting-project-leads/); [first-team](https://lethain.com/first-team/); [internal-candidates-for-senior-management](https://lethain.com/internal-candidates-for-senior-management/); [company-culture-and-managing-freedoms](https://lethain.com/company-culture-and-managing-freedoms/); [doing-it-harder-and-hero-programming](https://lethain.com/doing-it-harder-and-hero-programming/); [roles-over-rocket-ships](https://lethain.com/roles-over-rocket-ships/); [running-humane-interview-process](https://lethain.com/running-humane-interview-process/); [cold-sourcing](https://lethain.com/cold-sourcing/); [hiring-funnel](https://lethain.com/hiring-funnel/); [perf-management-system](https://lethain.com/perf-management-system/); [career-levels-and-more](https://lethain.com/career-levels-and-more/); [specialized-roles](https://lethain.com/specialized-roles/); [designing-interview-loops](https://lethain.com/designing-interview-loops/); [tools-for-operating-a-growing-org](https://lethain.com/tools-for-operating-a-growing-org/); [best-books](https://lethain.com/best-books/); [some-of-my-favorite-technical-papers](https://lethain.com/some-of-my-favorite-technical-papers/)
- Author: [lethain.com/about](https://lethain.com/about/); [Irrational Exuberance](https://lethain.com/); [LinkedIn](https://linkedin.com/in/lethain); [Cosign](https://cosign.co/lethain); [Business Wire](https://www.businesswire.com/news/home/20250603237278/en/Imprint-Appoints-Will-Larson-as-Chief-Technology-Officer); [FinTech Futures](https://www.fintechfutures.com/job-cuts-new-hires/former-stripe-exec-will-larson-named-new-imprint-cto)
- Interviews: [SE Daily, 14 Jun 2019](https://softwareengineeringdaily.com/2019/06/14/elegant-puzzle-with-will-larson/); [SE Daily book club](https://softwareengineeringdaily.com/2019/08/11/an-elegant-puzzle-virtual-book-club/); [Know Your Team #45](https://knowyourteam.com/blog/podcast/episode-45-interview-with-will-larson-head-of-foundation-engineering-at-stripe-and-author-of-an-elegant-puzzle/); [YouTube](https://youtu.be/vvswruOi4nE); [Programming Leadership #20](https://marcusblankenship.com/managing-to-solve-an-elegant-puzzle-with-will-larson/); [Developer Tea Part 1 (IA)](https://archive.org/details/1tpedmo69s4wa6rdgz6eq1uoivojz5ktewkkryt1); [Part 2 (IA)](https://archive.org/details/eaanbpgk1ehtktrbuszavvrgup1davvkwhjlwfir); [Part 3 (IA)](https://archive.org/details/3oh7vu0lagtup9qkdnh6hz88gky2lzdqjgroaixh); [First Round Review](https://firstround.com/review/how-to-size-and-assess-teams-from-an-eng-lead-at-stripe-uber-and-digg/); [Charity Majors's reading group](https://github.com/charity/elegant-puzzle-discuss)
- Reviews and notes: [Pragmatic Engineer review](https://blog.pragmaticengineer.com/an-elegant-puzzle-book-review/); [Pragmatic Engineer reading list](https://blog.pragmaticengineer.com/my-reading-list/); [Cindy Sridharan review](https://medium.com/@copyconstruct/book-review-an-elegant-puzzle-f787ad381ce0); [Keyvan Akbary's notes](https://keyvanakbary.github.io/learning-notes/books/an-elegant-puzzle/)
- Fact-check: [The Verge, Jan 2014](https://www.theverge.com/2014/1/8/5287900/uber-ceo-defends-surge-pricing-promises-rapid-growth-in-2014); [Forbes, Aug 2015](https://www.forbes.com/sites/liyanchen/2015/08/11/the-most-valuable-employees-snapchat-doubles-facebook/); [Wikipedia: DORA](https://en.wikipedia.org/wiki/DevOps_Research_and_Assessment); [IT Revolution, Accelerate excerpt](https://itrevolution.com/wp-content/uploads/2022/06/ACC_excerpt.pdf); [Business Insider, Schmidt's advice](https://www.businessinsider.com/the-brilliant-career-advice-google-ceo-eric-schmidt-gave-sheryl-sandberg-2012-5); [Barry Popik](https://barrypopik.com/blog/if_youre_offered_a_seat_on_a_rocket_ship); [Wikipedia: Me and Bobby McGee](https://en.wikipedia.org/wiki/Me_and_Bobby_McGee); [Wikipedia: The Good Earth](https://en.wikipedia.org/wiki/The_Good_Earth); [Wikipedia: Thinking in Systems](https://en.wikipedia.org/wiki/Thinking_In_Systems%3A_A_Primer); [Wikipedia: Rooney Rule](https://en.wikipedia.org/wiki/Rooney_Rule)