Purpose Is the Decision Procedure

operational84% High

Occurrences

76%

Success Rate

3.8

Avg Rating

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.

Trigger Conditions

Keywords:

boardprocessprioritizationvisibilitytrackingcolumnsfieldreporttoolJiraNGDproduct prioritiesJPDvalue driverswhere does this gohow do I showattendee listscopepurposeoverloadingtwo sources of truthmigrationdeprecated

Constraints: the artifact has acquired or is acquiring a second purpose, the asker wants the artifact widened to solve their problem, a tool or downstream view is being treated as a constraint on the design, the same question keeps recurring across different teams

People: Chris Baek on Jira structure and board mechanics, Ryan Smith on the TPS report and board migration, Justin Haynes and Brady Dibble on decomposition granularity, Nathan Blackham on JPD and board scope, Sarah Almaraz on meeting scope and attendee lists, any direct report presenting a use case the current artifact does not serve

Last applied: September 7, 2026

Created: July 29, 2026

Example Decisions (32)

Collapse nineteen engineering titles into four groups - and put senior principal back only if a manager makes the morale case

Sep 7, 2026 · operational

Purpose Is the Decision Procedure

Description

Typical Approach

Trigger Conditions

Example Decisions (32)

Collapse nineteen engineering titles into four groups - and put senior principal back only if a manager makes the morale case

Refuse an SDLC release-cadence contract that would bind engineering - prioritization authority stays with Product

Put the NVIDIA Spark bootable-Rocky USB on Justins org - and size it to carry meeting materials

Deliver the AI-spend message myself at an engineering all-hands instead of letting the AI committee write a policy

Diagnose every AI overage case individually and apply the remedy that case calls for - without squashing AI usage

Shut down department-heads as an intake path for engineering work - I raised it to product, they will either ask for it or they will not

Govern AI spend by notification and trust rather than a cap - alert at a thousand over, and if the person knows what they are doing get out of their way

Extend abort-the-loop authority from the hiring manager down to every individual interviewer - anybody can pull the ripcord alone, without a debrief or consensus

Move the metrics conversation with Nathan off the tooling and onto the why - which metrics, which were discarded, and how the team is told the reason

Restate every RESF request as a request to CIQ rather than to Nathan - publish the secure-boot ask to all of Linux Engineering so someone else can raise a hand

Approve the NVIDIA-supported Fuzzball hackathon at SC - with a Wolford engineer on site a day early and a month of hardware notice from NVIDIA

The five-week leader presentations are baseline once, then deltas forever - show me what you changed to move the number, not the same dashboard

Bake the confidence number on the scope in front of you today - and accept that a 90 percent can slip when scope changes

Refuse to act on the AI spend number until it is decomposed - one-time hardware out, recurring API in - then treat the remainder as usage discipline rather than a spend cap

Decline the DGX Spark allocation for now - a queue exists, Peter owns it, and the next batch is gated on CIQ showing Nvidia progress first

Require every five-week org review to show the delta against the prior review and what was done to move it - not a fresh static report

Refuse to start the incident-response conversation from the premise that an on-call system is needed - require an SLA first, and put accepting overnight downtime on the table as a real option

Redirect the entire Core42 solution-review effort away from the people on the call and toward whoever watches the recording afterward - and make every answer technical, never personal

Take the engineering re-leveling from principle to a concrete ladder - 13 levels down to 4 (open to a 5th), leadership down to Director and VP - and commit that no mapping ships without the direct report in the room

Force the stalled GB200 order to move the same day with time, not dollars, named as the governing constraint - and pre-absorb the over-utilisation complaint

Ratify sales engineers owning first-pass demos as the permanent structure - reframing Chris Wolfords self-reported staffing error as having kickstarted the right thing

Declare Jira a system of record and not a venue for process debate - shut the product-prioritization thread and move it into a room

Override your own teams stated intent to delete the RL 8.6 source tree, and apologize to Google directly rather than defend the position

No engineering team owns C3 - the content is wrong and outdated, so manage it or kill it, and Peter explicitly does not care which

The 1:1 tracking spreadsheet becomes Nathans choice - suggest, do not mandate - but whatever replaces it must be measurable and must never go to HR

Deliver the code-driven-not-agent-driven rule personally at Fridays AI committee as a single top-down message, because the first attempt did not land

No AI-tooling standard, no MCP catalog, not now - show the org how you built it and tell them to go build their own

Purchase approvals below a managers own threshold must never route to the CTO - told Nathan to expense it anyway and took the fight to Finance rather than the person executing the policy

The value-driver bottom row is the contract, not NGD - approved stripping target dates and confidence from product tickets and pointing them at NGD instead

Confidence numbers stay human and per-leader - Brady translates them, Engineering does not remap to his scale

The NGD board never bends to serve the TPS report - the report changes, and pulls from two data sources if it has to

Re-ruled the two boards from first principles in the room - prioritization vs dates-and-confidence - and told the org to delete any column serving a third purpose