Purpose Is the Decision Procedure

Description

When someone asks how a process, board, tool or artifact should handle their specific case, Peter refuses to answer on the askers terms. He re-derives the answer from what the artifact is for, states that purpose as the only decision procedure, and lets the answer fall out. Anything found to be serving a second purpose is deleted rather than debated. Tools and views are explicitly subordinate to definitions. He will accept that the askers real problem is simply not solved by this artifact rather than widen the artifact to cover it.

Typical Approach

Do not engage the specific use case on its merits. Restate the purpose of the artifact - the point of this board is prioritization, period; the point of that board is confidence numbers and delivery dates, that is it, nothing else - and then say the solution is derivable: you can understand what the solution should be just by asking yourself, what is the point of these two boards. Where duplicate or extra fields exist, instruct deletion rather than reconciliation: if there are columns there to serve any other purpose, they are wrong, remove them. Subordinate the tool: I do not care how JIRA is set up, if JIRA needs to change, JIRA needs to change. Subordinate the consumer: if the report is not showing the work, the report needs to change and maybe pull from two data sources, but the board stays the same. Name the uncomfortable conclusion explicitly - they are trying to figure out how my process solves their problem, and the answer to all of those is it does not. Correct a peer executive in the open if their directive violated purpose. Own any communication failure without conceding the substance. MINED REFINEMENTS (from 5 meta-learning observations, 2026-06-03 to 2026-08-13). The sharpest formulation anywhere in the corpus is the 2026-08-13 observation: he is INDIFFERENT to the parameters of his own frameworks and RELIGIOUS about their purpose. Four levels versus five is negotiable in the same breath that thirteen is not; which metrics a leader tracks is theirs to choose while showing the delta is not. Arguing the parameters with him is available; arguing the purpose is not. Practical consequence when reading him: a concession on a parameter is NOT softening on the rule. He separates coordination instruments by purpose and refuses to collapse them to fit a tool even when a stakeholder pushes for simplicity. He also names the diagnostic tell - he explains what an artifact is FOR while others explain what it is STRUCTURED like, and treats that difference as the explanation of why the tool is being misused. He protects a single-purpose venue from carrying a second message and states that constraint in absolute terms, because he knows his own default is to use an open floor to fix something.

Trigger Conditions