Wolfgang
Apr 27, 2026 - Oct 23, 2026
6
Decisions
0
Active Todos
13
Patterns
Categories
Decisions (6)
Core42 - hold to the SOW: stock Kubernetes plus Fuzzball before Oct 31, no CIQ-installed CozyStack, technical pushback routes to Peter
On 10/23 Core42 took Fuzzball out of the Oct 31 plan (no Fuzzball before deployment, look at it together later). Peter refused to let CIQ become a pure system integrator. As soon as the network is up, CIQ installs Ascender and Fuzzball; if Kubernetes is not there, CIQ installs stock K8s for Fuzzball to sit on, without CozyStack, and Core42 can add CozyStack later. Any pushback from Maxim or Sergei gets the scripted SOW answer (after consultation with Core42 engineering we have been told to follow the SOW; Fuzzball is an integral part of the CIQ stack and does not affect any other Kubernetes offering), and technical pushback routes to Peter. Builds on the 10/22 Ryan 1:1 where Peter made stock K8s plus Fuzzball plan A. The stock-K8s-then-Fuzzball shape was proposed by Bjorn; Peter adopted it and owns the engineering plan and the pushback routing.
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
Extending the 10/16 Core42 posture, Peter set a mechanism and a boundary. Mechanism: the last thing on the shared WhatsApp thread is always what CIQ needs from Core42 next - Wolfgang reposts the current blocker list (CIQ is blocked; this is what is blocking us), and Peter nudges when the thread goes quiet. Boundary: CIQ project-manages its own commitments hard and hits every at-bat as if the date holds, but does not hold any Core42 org accountable, because the org held accountable may be the one that ends up in the chair. Peter also suggested to Bjorn and Adam backchanneling to Alex that Core42 needs its own project manager - one adult in the room, and it cannot be a CIQ person - only if it can be done without blowing things up.
Core42 Kubernetes - never let anyone at Core42/G42 say CIQ cannot do Kubernetes; ask questions only, route Stratum to Bjorn
After a Core42 email raised Kubernetes questions, Peter set the posture: answer with capability (extensive K8s experience, a K8s offering in a month, able to configure or work with any K8s cluster); present Stratum as an option while saying off-the-shelf K8s is fine if required; do not tell Core42 what is unsupported, ask what they are trying to accomplish; stand nothing up; no engineer-to-engineer resolution - anything Stratum-shaped goes to Bjorn and their customer-facing people. On 10/21 he applied it by asking Sergei for a call with the CIQ Kubernetes team to learn whether they want CozyStack and why.
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
Peter bounded Wolfgang Resch hands-on role in Abu Dhabi to the window before VPN access exists; after that Ryan team picks it up, and his priority until then is whatever makes the VPN useful. Nobody else gets flown out. Once VPN was up on 10/15: Wolfgang comes home, nobody replaces him, and if a problem appears Peter will go himself. Peter intends to get Wolfgang bonuses, and wants someone more senior available to assist on future installs.
Clear Wolfgang for the UAE, cut the on-site window to week one, and hand the final pick to Wolford
Following the 9/16 decision to put a technical body on the ground in the UAE, Peter closed out the open questions in three moves across two days. He talked to Wolfgang, who wants to go. He asked Adam Jackson directly whether a German national can be sent and got a yes the same morning. He told Bjorn in the C-Suite Sync that he does not think the engineer needs to be there for the entire deployment - just the first week or so, when we are going to need to push a button. Then, when Chris Wolford raised Randy as an alternative, Peter said he is fine with it being Randy, that he does not mind, that it is 100 percent Wolford call, and attached the only real constraint: if it is Randy, tell Adam now so the security paperwork starts now for whoever is chosen.
Fuzzball PoC ownership belongs to Sales Engineering, supported by Engineering
When Bjorn asked who should own Fuzzball PoCs (Sales Engineering vs Wolfgang/Godlove vs Support), Peter answered definitively: Sales Engineering, supported by Engineering. Bjorn agreed with the framing — pushback was strictly about Sales Engineering not being enabled on Fuzzball today (resourcing gap), not the principle. The default routing stands.
Related Patterns (13)
Lead by Example with New Tools
When championing new tools or processes, personally use them and share results rather than just advocating. Learning by doing and demonstrating value through example is more effective than mandates.
Protect Engineering Focus Through Process
When faced with requests that would disrupt engineering focus (from sales, governance, product, or other stakeholders), establish processes that protect engineering ability to innovate while still satisfying legitimate concerns. Prefer systematic solutions over ad-hoc responses.
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict
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.
Purpose Is the Decision Procedure
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.
Route Non-Differentiating FTE Classes to Partners
When CIQ would otherwise need to staff a function whose work does not differentiate the company — compliance bureaucracy, audit/cert paperwork, ongoing regulatory attestation, etc. — Peter routes the load to a partner who already owns adjacent capability rather than adding the FTE class internally. Org-shape decision dressed as a partnership decision.
Demonstrate the Standard, Then Collect It
When a new leadership expectation has to land across multiple orgs, Peter does not write a spec. He runs a live exemplar in public with the strongest performer first, says openly that the ordering was deliberate, keeps the form of the deliverable open so the ask stays about the thinking rather than the artifact, lets the delta be self-evident to the people who will have to close it, and then collects the same from everyone else on a named rotation. He prefers showing imperfect work now over polished work later.
Decide on the Precedent, Not the Case
When a request arrives framed as a one-off, Peter does not evaluate the one-off. He evaluates the rule that granting it would write, and answers that instead. Peter generalized this himself on 2026-08-11: it is always about understanding precedent - whether it is a comp change or anything that structurally affects the company. It is therefore NOT a compensation pattern; the domain of the presenting request is incidental. The tell that this pattern is live is that the stated reason for the answer refers to future cases rather than to the merits of the present one.
Metrics Must Follow Strategy
When shifting team priorities or strategic direction, the communication alone will not drive behavior change. Engineers may acknowledge the new direction but continue existing behavior patterns without clear, explicit metrics holding them accountable.
Switch Instrument, Not Intensity
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.
Time Over Cost
Peter treats elapsed time as the scarce quantity and money as the abundant one, and will spend cash to buy schedule, clarity or optionality. Notable because he named it himself as a transferable principle on 2026-05-21 and coached the lens explicitly to a direct report, which is rare - most of his patterns are inferred rather than stated. It generalises past procurement: he will pay to convert an ambiguous dispute into a binary one, remove cost as a variable entirely when a priority has executive visibility, and reason about a commitment in terms of lead time rather than budget. Mined from 5 independent observations between 2026-02-01 and 2026-09-11.
Promise Only What Is Inside CIQ Control
Applies when someone asks CIQ to commit to an outcome whose delivery depends partly on something CIQ does not own - a lead time, a third-party publisher, a customer-provided environment, an unsigned contract. Peter does not accept or refuse the request as posed. He isolates the specific component that sits outside CIQ delivery chain, refuses that component by name, and substitutes an adjacent commitment CIQ can actually keep - then often adds a harder problem worth solving in its place, so the counterparty gets more engagement rather than less.
Measure, Commit Publicly, Then Execute
A three-beat escalation arc Peter runs when he needs a commitment from a peer or the CEO that private pressure has not produced. Beat one: measure the thing and get a number. Beat two: state the commitment in a venue where the people who matter are watching. Beat three: execute against it. The 2026-04-15 observation names the sequence explicitly and notes he does not skip steps, because each beat builds the legitimacy of the next. The venue choice is treated as a decision in its own right, separate from what the message says. Mined from 8 independent observations between 2025-12-29 and 2026-08-28. NOTE: scope this to the venue-and-sequence mechanism specifically - forcing function is a phrase that appears loosely across many unrelated decisions and should not be taken as a match on its own.
Install the Criterion Before the Argument
Applies to a contested question that has not been argued yet - a meeting about to start, a test about to run, an escalation just received, a proposal about to be written. Peter moves first to fix the criterion, the boundary or the posture, before anyone argues the substance. The consistent effect, named explicitly in the 2026-07-29 observation, is that the other party cannot win by being more persuasive on the merits, because the merits are no longer the axis. Distinct from Reclassify to Route in mechanism: that pattern reassigns who owns a question, this one controls WHEN the criterion lands relative to the debate. The two frequently co-occur. Mined from 7 independent observations between 2026-01-20 and 2026-08-31.