The Unfix Model: An Org Design Pattern Library
The Unfix Model treats org design like a Lego set, not a pre-built model. It's a library of patterns for companies moving beyond rigid agile frameworks to build dynamic, self-managed teams. The footgun is treating it as another framework to install wholesale.
Holacracy: An Operating System for Your Organization
Holacracy replaces a management hierarchy with a formal constitution, vesting authority in roles, not people. It provides a structured way to scale self-management.
Bimodal IT: Running Your IT Org at Two Speeds
Bimodal IT runs IT at two speeds: a stable, predictable "Mode 1" for core systems and an agile, experimental "Mode 2" for innovation. This allows enterprises to build new digital products without breaking the essential legacy systems that run the business.
The Satir Change Model
The Satir Change Model maps a team's emotional journey through disruption. When a new process is introduced, performance doesn't just improve; it first dips into resistance and chaos.
Management 3.0: Manage the System, Not the People
Management 3.0 treats leadership like tending a garden, not commanding an army. You manage the system—the environment and constraints—to let empowered teams flourish. It's used in agile contexts to boost engagement with hands-on tools and games.
Inspect & Adapt: SAFe's Formal Improvement Event
Inspect & Adapt is a formal 'pit stop' for an entire Agile Release Train (ART) to improve its process. At the end of each Program Increment, teams demo the solution, review metrics, and identify improvements.
RTE: The Conductor of the Agile Release Train
The Release Train Engineer (RTE) is the master facilitator for a group of agile teams, acting as a servant leader and coach. They orchestrate large-scale planning and ensure smooth value delivery.
PI Planning: Aligning an Entire Agile Release Train
PI Planning gets an entire 'team of teams' (an ART) in one room to plan the next 8-12 weeks. This two-day event aligns development with business goals and identifies cross-team dependencies.
The Agile Release Train: How Multiple Teams Ship Together
An Agile Release Train (ART) is a 'team of teams' that aligns 50-125 people to ship a complex product together. It's used in SAFe to coordinate multiple Agile teams on a shared roadmap, ensuring they all pull in the same direction.
Escaped Defects Rate: Measuring What Slips to Production
Escaped Defects Rate is your quality report card from users, measuring the percentage of total bugs that your internal testing missed. Teams use it to gauge QA effectiveness. The footgun is using it to blame individuals, which just encourages hiding bugs.
STATIK: Designing a Kanban System from First Principles
STATIK is a diagnostic recipe for designing a Kanban system tailored to your team's actual work, not just copying a template. Use it when starting a new implementation or when an existing process is stuck. The footgun is skipping the analysis.
.png&w=3840&q=75)
Kanban: A Strategy for Optimizing Flow
Kanban isn't just a board with columns; it's a strategy for optimizing the flow of value through your process. It helps teams visualize work, manage bottlenecks, and deliver value predictably.
The Opportunity Solution Tree: Connecting Outcomes to Solutions
An Opportunity Solution Tree is a visual map connecting a business goal to the customer problems you could solve to achieve it. Product teams use it to explore paths to an outcome, ensuring features address real user needs.
Pretotyping: Build The Right It, Not Just It Right
Pretotyping tests if anyone wants your product before you build it, ensuring you build 'The Right It.' Use it to validate market demand with minimal resources, gathering real data. The footgun is confusing it with prototyping, which tests implementation.
Dual-Track Agile: Discovery Before Delivery
Dual-Track Agile runs two parallel streams: a Discovery track to quickly validate ideas and a Delivery track to build releasable software. It prevents waste by testing concepts with cheap prototypes before writing code.
Design Sprint: From Idea to Prototype in 5 Days
A Design Sprint fast-forwards you to see customer reactions without building a real product. In one week, your team goes from a big question to a realistic prototype and user feedback.
Jobs to be Done: Sell the Hole, Not the Drill
Jobs to be Done (JTBD) says people don't buy a drill, they buy a hole. It focuses on the customer's underlying goal, not your product. This helps uncover new opportunities, but the footgun is defining the job too narrowly, limiting innovation to your current…
Lean Canvas: A Startup's Reality Check on a Page
A Lean Canvas is a one-page business plan that forces you to define and test your riskiest assumptions first. Startups use it to validate their core idea before building. The biggest mistake is treating it as a one-time exercise instead of a living document.
Strangler Fig Pattern: Replace Legacy Systems Safely
The Strangler Fig pattern lets you replace a legacy system by gradually growing a new one around it, eventually choking out the old code. It's used for modernizing critical systems where a "big bang" rewrite is too risky, routing traffic feature by feature.
The 4Ls Retrospective: Loved, Loathed, Longed For, Learned
The 4Ls retrospective is a structured way to capture a team's feelings after a project. It asks what they Loved, Loathed, Longed for, and Learned to create an action plan. A common pitfall is only focusing on negatives, missing key insights from the other Ls.