← Back to Patterns

Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict

strategy81% High

42

Occurrences

80%

Success Rate

4.0

Avg Rating

Description

When a question arrives at Peter framed in one domain, he often does not answer it in that framing. He reclassifies it into the domain that actually governs the outcome, which relocates ownership to whoever owns that lane, and then hands down a decision criterion rather than a verdict. The reclassification IS the decision - it determines who decides. He does this rather than adjudicating on the merits himself, even when he was explicitly cc-ed and even when a direct report challenges him on the substance.

Typical Approach

Identify what the question really turns on rather than how it was presented. Name the owner of that lane explicitly and publicly (this is a Kelly Hall call). Supply the criterion the owner should optimize for, scoped and time-bounded where possible (whatever path is most likely to get a contract signed in the next couple of days), so the rule can be reapplied as facts move and expires rather than becoming standing policy. Do not debate the original framing - route instead of arguing, leaving a legitimate objection unanswered if answering it would pull the decision back to Peter. Reserve this for questions where the risk or lever sits outside engineering control, or where the presenting frame would put engineering in charge of a commercial or product judgment.

Trigger Conditions

Keywords:
disclosurecustomer commsescalationwho decidesdelegateroutecriterioncontractsignaturetimingclassificationfeature not a bugcommercialexogenous riskout of our hands
Constraints: the presenting frame assigns the call to the wrong lane, the risk or lever is outside engineering control, facts are still moving so a fixed verdict would go stale, a near-term commercial objective bounds the decision
People: Kelly Hall on anything that turns on getting a contract signed, Bjorn Hovland on product-market and go-to-market judgment, Brady Dibble and Justin Haynes escalating compliance or delivery risk to Peter, any direct report presenting a transparency question with no accompanying customer action

Last applied: September 7, 2026

Created: July 24, 2026

Example Decisions (42)

Let the dual-loop candidate pick her team - then stop the other loop rather than finish it

Sep 7, 2026 · people

Pending

Defend the net-new engineering reqs to Greg by naming them - and pay for them with an explicit churn commitment

Sep 7, 2026 · strategy

Pending

Take the KT 9.8 one-year bridge - engineering will figure it out as long as the million dollars comes with headcount

Sep 7, 2026 · strategy

Pending

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

Sep 7, 2026 · strategy

Pending

Refuse to green-light the HPE indemnity escalation - this is a Bjorn call, not an Engineering call

Sep 3, 2026 · strategy

Pending

Refuse the 9.10-as-of-today letter for KT - give them 9.6 LTS now with its real support window and a required migration, and correct the numbers publicly when they turn out to be wrong

Sep 2, 2026 · strategy

Pending

Put the Core42 deployment on Ryan org to resource - Nathan stays advisor and the unfilled Forward Deployed Engineer goes on the contract list

Aug 31, 2026 · strategy

Pending

Hold the Core42 commitment at five weeks, signal two-to-three as likely, and trade the compression for topology data

Aug 31, 2026 · strategy

Pending

Attack the live-patching gap through Google co-development as a paid deliverable while keeping the req open - buy the timeline, do not just wait for the hire

Aug 28, 2026 · strategy

Pending

Hold the CISO requisition and the September security hire pending the Atomicorp acquisition

Aug 28, 2026 · strategy

Pending

Broken-in-production is an automatic fast path - small thing with embarrassing impact jumps the queue regardless of the size of the epic around it

Aug 28, 2026 · strategy

Pending

Accept Bjorn conclusion on the Stratum name while refusing his reason - dont make a decision now that you dont have to make

Aug 24, 2026 · strategy

Pending

Call the Core42 SOW1 won mid-call and forbid reopening anything that does not need reopening

Aug 24, 2026 · strategy

Pending

Claim the Core42 Dubai build-out for engineering outright - there is no sales engineering function, so if it gets built it gets built by engineering, and every scope increase still arrives with headcount

Aug 21, 2026 · strategy

★★★★

Show Core42 the responsibility matrix filled in, not blanked - a first cut we are flexible on beats arriving with an empty working sheet

Aug 19, 2026 · strategy

Pending

Pre-empt a three-week delivery commitment to Core42 before the deal closes - hand Bjorn the real sequencing mid-call so the number dies before it is said

Aug 19, 2026 · strategy

★★★★★

Value delivering things over doing work - ship three items all the way out the door and nothing elsewhere, rather than move nineteen forward

Aug 19, 2026 · strategy

Pending

Fork the Core42 engagement into two SOWs and let nothing delay the first - land the GB300 paper now, put the expanded security architecture in a separate SOW

Aug 19, 2026 · strategy

★★★☆☆

Answer a CEO escalation about interview-feedback conduct by naming the owner rather than absorbing it - Nathan talks to Jeff, off-channel

Aug 18, 2026 · people

Pending

Ask Greg to take Peter off the RESF directive so it reads as CEO-to-RESF instead of CEO-correcting-his-CTO - and pair it with a standing Lee status cadence

Aug 18, 2026 · strategy

Pending

Refuse to debate the cause of the Rocky download reversal until the metric itself is validated - either it is the number we track and it warrants attention, or we track a different one

Aug 18, 2026 · strategy

Pending

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

Aug 13, 2026 · operational

Pending

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

Aug 13, 2026 · strategy

★★★★

RevOps does not become an engineering organization - it becomes a product-management organization that feeds engineering requirements

Aug 11, 2026 · strategy

Pending

Treat prototypes crossing from Product into Engineering as a feature rather than a burden - the code is worth two days, the market learning is the payload, and every one arrives with headcount

Aug 11, 2026 · strategy

★★★★

Make the LG meeting 100 percent about understanding their problem - no selling, no refusing - and pull Justin in for that purpose only

Aug 11, 2026 · strategy

Pending

Price the Google live-kernel-patching ask at 2 HC for 3.5 months plus 1 ongoing, and take the honest slower timeline back to Tissa rather than fit their October date

Aug 11, 2026 · strategy

★★★★

Core 42 delivery will not land on Nathans org - it needs a purpose-built deployment team, likely based in the Middle East, under Bjorns forward-deployed structure

Jul 30, 2026 · strategy

★★★☆☆

Endorse a radical open-source-forward external position with no gate, and pre-commit CIQ to the spark-arena seat

Jul 29, 2026 · strategy

Pending

Took the Fuzzball pitch to Axiom Space himself rather than letting Sales carry it - and set the closing path at NDA then contract

Jul 29, 2026 · strategy

★★★★

Google ELTS: pay or I stop the work - and CIQ eats the disputed 150k out of the existing discount to remove the excuse

Jul 29, 2026 · strategy

★★★★★

Kill the reuse justification - the LG solution does not get to be reused for other customers

Jul 29, 2026 · strategy

Pending

Three non-negotiables on the LG U+ RHEL-layering path - drawn before the technical debate, with a lawyer-and-everybody-else escape hatch

Jul 29, 2026 · strategy

Pending

Route the coordination gap on the CEOs public posting to Marketing and Bjorn

Jul 28, 2026 · strategy

★★★★

Ascender-orchestrates-Warewulf belongs in Ascender Pro as paid-tier differentiation; route Josephs proposal to Zarina

Jul 28, 2026 · strategy

Pending

Everfox desktop - CIQ is an integrator, not a builder of novel desktop technology; convert the ambiguity into integrator-shaped requirements

Jul 27, 2026 · strategy

★★★★

Definitive no to LG U+ cross-distro package support - the test is whether we would ship it down the middle for everyone

Jul 27, 2026 · strategy

★★★☆☆

Clear Greg to proceed on the open-source AI-training-data initiative with no CTO gate

Jul 24, 2026 · strategy

★★★★

Reclassify the GDC MIP-listing disclosure question as a contract-timing call and route it to Kelly Hall with a decision criterion

Jul 24, 2026 · strategy

★★★★★

Endura / Eric Sheridan: yes as a pass-through go-to-market offering only, no engineering pipeline work this half

Jul 24, 2026 · strategy

Pending

Pull the business side (Kelly) into the FIPS 6.18 CAVP-retrigger vs fork call

Jul 21, 2026 · strategy

★★★★

Rule the Toyota kernel patch a feature not a bug; no automatic queue jump, escalate through normal priority

Jul 10, 2026 · operational

★★★★

Pattern ID: 7c01dd1e-95e0-4d2c-8de6-b15d008c131d