[{"data":1,"prerenderedAt":236},["ShallowReactive",2],{"tags":3,"books":49,"feed":171},[4,11,15,22,29,36,42],{"slug":5,"name":6,"title":6,"shortTitle":6,"description":7,"hue":8,"aliases":9,"order":10},"direction","Direction","Learn about growth and what an institution should refuse in order to keep it.","green",[],10,{"slug":12,"name":13,"title":13,"description":7,"hue":8,"aliases":14,"order":10},"growth","Growth",[],{"slug":16,"name":17,"title":17,"description":18,"hue":19,"aliases":20,"order":21},"decay","Decay","Learn about institutional decay and how organizations lose the ability to act.","orange",[],11,{"slug":23,"name":24,"title":24,"description":25,"hue":26,"aliases":27,"order":28},"leadership","Leadership","Learn about leadership and who is accountable for a decision.","pink",[],12,{"slug":30,"name":31,"title":31,"description":32,"hue":33,"aliases":34,"order":35},"teams","Teams","Learn about teams and how a group holds a problem.","cyan",[],13,{"slug":37,"name":38,"title":38,"description":39,"hue":33,"aliases":40,"order":41},"architecture","Architecture","Learn about architecture and how a system is cut into parts people can own.",[],15,{"slug":43,"name":44,"title":45,"shortTitle":44,"description":46,"hue":26,"aliases":47,"order":48},"strategy","Strategy","Strategic thinking for","Defining a clear strategy.",[],19,[50,73,87,104,117,130,143,158],{"id":51,"title":52,"aliases":53,"body":55,"description":62,"extension":63,"hue":19,"image":64,"meta":65,"name":66,"navigation":67,"order":68,"path":69,"seo":70,"shortTitle":64,"stem":71,"__hash__":72},"books\u002Fbooks\u002Fddd.mdc","Domain-driven design",[54],"domain-driven-design",{"type":56,"value":57,"toc":58},"minimark",[],{"title":59,"searchDepth":60,"depth":60,"links":61},"",2,[],"Learn about domain-driven design and how a domain is cut into models people can own.","mdc",null,{},"DDD",true,16,"\u002Fbooks\u002Fddd",{"title":52,"description":62},"books\u002Fddd","6MgU8Zl_sSMracZF9w-_ECDAuRDfEZKuEjzbmb4obhk",{"id":74,"title":75,"aliases":64,"body":76,"description":80,"extension":63,"hue":81,"image":64,"meta":82,"name":64,"navigation":67,"order":64,"path":83,"seo":84,"shortTitle":64,"stem":85,"__hash__":86},"books\u002Fbooks\u002Fhigh-output-management.mdc","High Output Management",{"type":56,"value":77,"toc":78},[],{"title":59,"searchDepth":60,"depth":60,"links":79},[],"High Output Management is a book by Andrew S. Grove, the longtime CEO of Intel, first published in 1983. It treats management as a production process, where a manager's output is the output of the organization they run and influence. It covers leverage, indicators paired with counter-indicators to guard against overreacting to a single number, one-on-ones, meetings, decision-making, and task-relevant maturity.","blue",{},"\u002Fbooks\u002Fhigh-output-management",{"title":75,"description":80},"books\u002Fhigh-output-management","n2pHvK5R3MMO3Rv5f61jnsd-LhBbtrNgA6IEjK0QFyQ",{"id":88,"title":89,"aliases":64,"body":90,"description":94,"extension":63,"hue":64,"image":64,"meta":95,"name":64,"navigation":67,"order":64,"path":100,"seo":101,"shortTitle":64,"stem":102,"__hash__":103},"books\u002Fbooks\u002Fmbo.mdc","Management by Objectives",{"type":56,"value":91,"toc":92},[],{"title":59,"searchDepth":60,"depth":60,"links":93},[],"a management model by Peter Drucker, most notably described in the book *The Practice of Management* (1954). MBO emphasizes the importance of managers and employees defining clear, measurable objectives together. Progress is assessed regularly and tasks are aligned with these objectives to improve performance and organizational focus.",{"author":96,"year":97,"category":98,"type":99},"Peter F. Drucker",1954,"management","book","\u002Fbooks\u002Fmbo",{"title":89,"description":94},"books\u002Fmbo","RJRA-o3NpSPZm2YEIWQM9XDZbev8m6AITT2NLOz9Zsk",{"id":105,"title":106,"aliases":64,"body":107,"description":111,"extension":63,"hue":81,"image":64,"meta":112,"name":64,"navigation":67,"order":64,"path":113,"seo":114,"shortTitle":64,"stem":115,"__hash__":116},"books\u002Fbooks\u002Fteam-topologies.mdc","Team Topologies",{"type":56,"value":108,"toc":109},[],{"title":59,"searchDepth":60,"depth":60,"links":110},[],"Team Topologies by Matthew Skelton and Manuel Pais explores four fundamental team types and three essential team interaction modes, providing practical guidance for structuring technology organizations to improve flow and reduce cognitive load.",{},"\u002Fbooks\u002Fteam-topologies",{"title":106,"description":111},"books\u002Fteam-topologies","62Pg4IQXhUFKrHH0EIuNyLALnYRWrl2HKgLoirXYQ-k",{"id":118,"title":119,"aliases":64,"body":120,"description":124,"extension":63,"hue":81,"image":64,"meta":125,"name":64,"navigation":67,"order":64,"path":126,"seo":127,"shortTitle":64,"stem":128,"__hash__":129},"books\u002Fbooks\u002Fthe-goal.mdc","The Goal",{"type":56,"value":121,"toc":122},[],{"title":59,"searchDepth":60,"depth":60,"links":123},[],"The Goal is the foundational text for operations management, Lean manufacturing, and modern DevOps. It is where the concepts of bottlenecks, the illusion of local optimization, and the Five Focusing Steps were originally codified. It is a business novel by Eliyahu M. Goldratt first published in 1984. It introduces the Theory of Constraints: a system's throughput is limited by its bottleneck, and improving anything else does not improve the system.",{},"\u002Fbooks\u002Fthe-goal",{"title":119,"description":124},"books\u002Fthe-goal","9NGbv6RhcVxCeTObzeZo5ZKGeuYPnZDqYbNwnZpgPZk",{"id":131,"title":132,"aliases":64,"body":133,"description":137,"extension":63,"hue":81,"image":64,"meta":138,"name":64,"navigation":67,"order":64,"path":139,"seo":140,"shortTitle":64,"stem":141,"__hash__":142},"books\u002Fbooks\u002Fthe-mythical-man-month.mdc","The Mythical Man-Month",{"type":56,"value":134,"toc":135},[],{"title":59,"searchDepth":60,"depth":60,"links":136},[],"Essays on Software Engineering is a book on software engineering and project management by Fred Brooks first published in 1975, with subsequent editions in 1982 and 1995. Its central theme is that adding manpower to a software project that is behind schedule delays it even longer. This idea is known as Brooks´s law, and is presented along with the second-system effect and advocacy of prototyping",{},"\u002Fbooks\u002Fthe-mythical-man-month",{"title":132,"description":137},"books\u002Fthe-mythical-man-month","xBXostdKJRex7YjSwW5FDsZ8-iaRsAUjrUf1sY1N_yg",{"id":144,"title":145,"aliases":146,"body":148,"description":152,"extension":63,"hue":81,"image":64,"meta":153,"name":64,"navigation":67,"order":64,"path":154,"seo":155,"shortTitle":64,"stem":156,"__hash__":157},"books\u002Fbooks\u002Fthe-practice-of-management.mdc","The Practice of Management",[147],"practice-of-management",{"type":56,"value":149,"toc":150},[],{"title":59,"searchDepth":60,"depth":60,"links":151},[],"The Practice of Management is a book by Peter F. Drucker, first published in 1954. It was one of the first books to treat management as a distinct discipline, and it introduced Management by Objectives and self-control, where managers and their teams agree on clear objectives and measure their own progress against them. It also argues that the purpose of a business is to create a customer, and includes the parable of the three stonecutters.",{},"\u002Fbooks\u002Fthe-practice-of-management",{"title":145,"description":152},"books\u002Fthe-practice-of-management","SW0d06PxnIsHp3t9r7PVZCZs9QGSOhmuuJlfhaaH2dA",{"id":159,"title":160,"aliases":64,"body":161,"description":165,"extension":63,"hue":81,"image":64,"meta":166,"name":64,"navigation":67,"order":64,"path":167,"seo":168,"shortTitle":64,"stem":169,"__hash__":170},"books\u002Fbooks\u002Ftheory-of-constraints.mdc","Theory of Constraints",{"type":56,"value":162,"toc":163},[],{"title":59,"searchDepth":60,"depth":60,"links":164},[],"Eliyahu M. Goldratt’s 1990 exposition of the Theory of Constraints: how to identify, exploit, subordinate to, and elevate the system’s bottleneck so throughput rises instead of local efficiency.",{},"\u002Fbooks\u002Ftheory-of-constraints",{"title":160,"description":165},"books\u002Ftheory-of-constraints","vfEJgiHLqOmiH3k7tScju0AmQnoHLgyi5XA8dsfN_Co",[172],{"id":173,"title":174,"author":175,"body":176,"category":225,"description":59,"draft":226,"extension":63,"lead":227,"listed":67,"medium":228,"meta":229,"navigation":67,"path":230,"published":231,"seo":232,"shortTitle":64,"sources":64,"stem":233,"tags":234,"updated":64,"__hash__":235},"feed\u002Ffeed\u002Famazons-fulfillment-collapse.mdc","Amazon’s Fulfillment Collapse (1999–2002)","cb",{"type":56,"value":177,"toc":223},[178,182,186,189,192,201,214,217,220],[179,180],"img",{"src":181},"\u002Ffeed\u002Famazon.png",[183,184,185],"p",{},"Warehouses were in total disarray: inventory was misplaced, employees were manually running across massive floors to hunt down items, conveyor systems jammed, and thousands of orders missed the Christmas shipping deadline. It was an operational nightmare that bled cash and threatened to destroy customer trust permanently.",[183,187,188],{},"Most tech executives would have treated warehouse logistics as unglamorous, blue-collar back-office maintenance. The conventional move would have been: keep the top engineers and high-performers focused on \"opportunities\" (launching new digital retail categories, building auction platforms, redesigning the website) while hiring cheap third-party logistics consultants to patch the warehouse problem.",[183,190,191],{},"Bezos did the opposite. He realized that fulfillment was the singular constraint throttling the entire economic engine of the company.",[183,193,194,195,200],{},"He hired Jeff Wilke, a manufacturing systems leader steeped in lean production and ",[196,197,199],"a",{"href":198},"\u002F%C2%A7goldratts-theory-of-constraints","Goldratt’s Theory of Constraints",", and gave him total organizational backing. They didn't treat logistics as a janitorial task. They deployed their sharpest technical and mathematical talent directly into the fulfillment centers:",[202,203,204,208,211],"ol",{},[205,206,207],"li",{},"They rewrote warehouse management algorithms from scratch.",[205,209,210],{},"They applied first-principles flow dynamics to conveyor belts, picking paths, and inventory placement.",[205,212,213],{},"They eliminated every manual friction point in the handoff between order placement and carrier dispatch.",[183,215,216],{},"Breaking that single operational bottleneck did not just restore basic order to the warehouses. It transformed fulfillment into a mathematically predictable, high-velocity machine.",[183,218,219],{},"That restored throughput became the foundation for Amazon Prime.",[183,221,222],{},"Because they had eliminated the fulfillment bottleneck, Amazon could offer guaranteed, free two-day shipping at scale—something no competitor could replicate for a decade. The bottleneck wasn't a problem to be patched; solving it was the greatest offensive opportunity in the history of e-commerce.\n.",{"title":59,"searchDepth":60,"depth":60,"links":224},[],"case-study",false,"In 1999 Amazon nearly died from its own success—then Bezos put his best people on the warehouse bottleneck, and Prime became possible.","article",{"notion":59},"\u002Ffeed\u002Famazons-fulfillment-collapse","2026-10-24",{"title":174,"description":59},"feed\u002Famazons-fulfillment-collapse",[43,12],"na5tbr3UV_IGMxOWc_ElOPq78RU70uiA550rtX0Ghzg",1792828494037]