Doing the Right Thing the Right Way

Definition

Pichler frames product and process correctness as two independent axes crossed in a 2x2 matrix (Figure 1.1). Building the right product with the right process yields enduring success. The right product built the wrong way is a "quick but unsustainable win." The wrong product built the right way is slow failure. The wrong product built the wrong way is fast failure. The two axes map directly onto the book's split between the product owner, "primarily responsible for the 'what' — creating the right product," and the ScrumMaster, "primarily responsible for the 'how' — using Scrum the right way."

In the Book

The matrix appears in Chapter 1 immediately after the book explains why product owner and ScrumMaster are distinct, complementary roles — never combined in one person. The two roles are deliberately built to check different failure axes: a product owner alone might optimize a process for speed while building something nobody wants (the "quick but unsustainable win" quadrant, cutting corners to hit a wrong target fast); a ScrumMaster alone enforcing perfect Scrum mechanics doesn't guarantee the backlog contains the right things. The book states directly that one individual should never hold both roles, because doing so collapses the deliberate separation between the two checks.

Why It Matters

When an effort fails, "did we build the wrong thing" and "did we build it badly" are different diagnoses requiring different fixes, and conflating them wastes the correction. This applies well past software: any endeavor benefits from separately checking that the target is correct and that the method reaching it is sound, because a team can be excellent at execution while chasing the wrong goal, or have the right goal and ruin it with a bad process — and only distinguishing the two axes tells you which lever to pull.