← Back to Patterns

Switch Instrument, Not Intensity

operational75% Medium

42

Occurrences

67%

Success Rate

3.4

Avg Rating

Description

Applies when a message, rule or ask has already failed through the channel Peter is currently using - repeated advocacy that has not landed, coaching that produced defensiveness rather than improvement, exhortation that did not change behaviour, or a rule that keeps losing case by case. His response is never to restate the same thing more forcefully. He changes the instrument and usually names the switch out loud. Mined from 7 independent observations between 2026-01-06 and 2026-08-21.

Typical Approach

Treat a track record of the informal channel failing as the trigger, not as a reason to try harder. Diagnose why the current instrument is unenforceable rather than re-asserting it - and if the rule was named after the wrong thing, rename it after the deficit it was actually pointing at. Then move to a different class of instrument: coaching to a contract or SLA, persuasion to structural authority, an exhortation to a demonstration the room watches happen, a behavioural ask to a role whose description makes the stance non-negotiable, a metrics lecture to asking the person who runs the org for the reasoning behind their own metric set. Name the switch as a switch so the change of instrument is itself legible. Concede the limit of your own knowledge inside the switch where it applies. Important refinement from 2026-08-11: when a message fails, the fix is usually demonstration rather than greater directness - a self-diagnosis of I was not clear enough has been wrong at least once.

Trigger Conditions

Keywords:
repeatedagainstill notkeeps happeningcoachingexhortationpersuasionadoptionnot landingunenforceablerestateignoredpushbackrulemandateinstrument
Constraints: the same ask has already been made through this channel at least once, the failure is of the channel rather than of the substance, escalating intensity in the same channel is the available but wrong move

Last applied: November 3, 2026

Created: September 11, 2026

Example Decisions (42)

Public CVE claims match what is in customers hands - fixed internally is not fixed; engage fast with accurate words

Nov 3, 2026 · operational

Pending

Reinforce: confidence numbers are machine-read interfaces between teams and must be right in real time

Oct 30, 2026 · operational

Pending

Advertise the Kubernetes req on launch Thursday - no extra week of waiting

Oct 30, 2026 · operational

Pending

Title mapping rules for Justin org - no senior or junior variants, map to the lower bound and promote later, no comp or promotions in the exercise, no zealotry where someone gets hurt

Oct 30, 2026 · operational

Pending

Core42 10/29 - CIQ is not the bottleneck; the only CIQ task is a best-practice doc for Warewulf in secure environments, routed to Michael Shinn

Oct 30, 2026 · operational

Pending

ISMS council - accept Risk 33 (vendor breach) and accept a binding legal-review obligation for externally shared incident reports

Oct 30, 2026 · operational

Pending

The RESF operations lead joins department heads so the RESF can ask CIQ for help without knowing who will provide it

Oct 30, 2026 · operational

Pending

Grenoble pitch - Peter quarterbacks the technical answers and capabilities due within 6-8 weeks are presented as in final test

Oct 30, 2026 · operational

Pending

Every engineering team takes every product training, due in 30 days - manager carve-outs overridden

Oct 30, 2026 · operational

Pending

No data gatekeeping - access to company data by default unless a signed compliance or legal rule requires a block; tool owners can request features but cannot stop work

Oct 30, 2026 · operational

Pending

Apptainer - hold Bjorn to zero engineering hours and let things fall on the floor so the maintenance cost becomes visible

Oct 23, 2026 · strategy

Pending

Reinforce: Wale stays where he is - solve the Lee need by Lee asking for help and joining department heads, not by a reporting change

Oct 23, 2026 · people

Pending

Customer-specific asks go through Work Ingestion and RAT build/validation - no side channels, even under deal pressure

Oct 23, 2026 · operational

Pending

AI spend - the 100k card limit stays as a runaway tripwire while Baek plans 120k per month for 2027

Oct 21, 2026 · operational

Pending

Bjorn post-training / sovereign-stack ask goes on the Value Drivers board as a product block; engineering hangs a learn-first research effort off it

Oct 21, 2026 · operational

Pending

Core42 - the last line in every shared thread is the Core42 action item; project-manage our own work and stay out of their internal accountability fights

Oct 21, 2026 · operational

Pending

Blockers get raised at department heads so the whole company hears them

Oct 16, 2026 · operational

Pending

Wolfgang on-site role ends at the pre-VPN window - no extra travel, send someone only if a problem appears, Peter is the backstop, bonuses earned

Oct 16, 2026 · operational

Pending

Core42 partner posture - plan only in CIQ-only rooms, never program-manage Core42, zero friction, Adam coordinates

Oct 16, 2026 · operational

Pending

Jira confidence and date updates - the goal is org visibility, not leads pushing buttons; automate the manual part

Oct 2, 2026 · operational

Pending

Approve the Spark benchmark claim in the RLC Pro AI press release - correct and defensible beats preferred wording

Oct 2, 2026 · operational

Pending

Internal tools come under Wallace IT umbrella - he owns the map, hosting, DR and access, builders keep maintaining, and unused tools get an evaluation date and are shut down

Oct 2, 2026 · operational

Pending

Approve the SOC 2 three-year extension on Steve renegotiated terms - same rate, payment deferred, penalty-free cancellation

Oct 1, 2026 · operational

Pending

Put dates out even at low confidence so the board shows reality, and leads keep evolving their metrics - dropping the ones that get gamed

Oct 1, 2026 · operational

Pending

Jira stays the system of record - a shared git context repo is welcome, a centralized program-management engine everyone must use is not

Oct 1, 2026 · operational

Pending

Vera Rubin to Google - commit to a bounded duration (at most 3 weeks after node access), not a date, and invite Google to supply its own hardware

Oct 1, 2026 · operational

Pending

Everyone owns their AI spend - no gates or guardrails, but unaware spending is unacceptable

Oct 1, 2026 · operational

Pending

Vera Rubin access is drop-everything, the goal is proving it works for Google rather than benchmarks, and kernel pre-work starts now

Sep 25, 2026 · operational

Pending

Build Engineering All-Hands section on Bjorn joint-win narrative - no separate engineering highlights

Sep 24, 2026 · operational

Pending

Unhold the security-engineer req and carry it to Greg in conversation rather than clicking approve

Sep 23, 2026 · strategy

Pending

Treat every RCA as a legal document - Legal review plus Peter personal clearance before it goes to a customer

Sep 23, 2026 · operational

Pending

Clear Wolfgang for the UAE, cut the on-site window to week one, and hand the final pick to Wolford

Sep 23, 2026 · operational

Pending

Refuse the Veeam rollback and the never-again promise - fix forward and hold the response until the RCA is understood

Sep 23, 2026 · operational

Pending

Route all new Shin-brothers requests through Bjorn for a month, in writing, with technical direction staying with the asking manager

Sep 16, 2026 · operational

Pending

Put a technical body on the ground in the UAE through Oct 5 rather than run the Core42 deployment fully remote

Sep 16, 2026 · operational

★★★☆☆

Serve Google security due diligence from the Core42 audit corpus rather than rebuilding it in a silo

Sep 11, 2026 · operational

Pending

Bound the NVIDIA driver auto-update ticket - 24 hours is the product ask, 30 days is the contractual floor

Sep 11, 2026 · operational

★★★☆☆

Refuse to write the RLC-AI contrivance down - say it to Justin, Nathan and Andrew, never in a company-wide channel

Sep 11, 2026 · operational

Pending

Push speed-over-perfect down into the Justin org and ask him to produce a visible failure that goes unpunished

Sep 11, 2026 · operational

Pending

Re-anchor the no-more-Amazon-blood rule on the deficit it was actually naming - what the org is short of is people who have had a startup collapse under them, not people with different opinions about Linux

Aug 21, 2026 · people

★★★★☆

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

Aug 21, 2026 · operational

★★★☆☆

Engineering veto required on custom deals and new lines of business

May 4, 2026 · strategy

★★★★☆

Pattern ID: 9d6efd62-fe2d-49ce-b0fe-dcde8cf55288