Brett Mastbergen
Sep 11, 2026
4
Decisions
0
Active Todos
14
Patterns
Categories
Decisions (4)
Refuse to write the RLC-AI contrivance down - say it to Justin, Nathan and Andrew, never in a company-wide channel
Nathan asked Peter to post the full rationale for the deliberately contrived RLC-AI Spark build into the public RLC-AI channel. Peter declined outright and said he would say it to Justin, to Nathan and to Andrew, but would not write it anywhere the whole company can see. The same boundary appears in Slack the same morning, where he told Brett that he wanted the message going to Brett, Andrew and Jeff rather than wider, and said plainly that it is not a message for the whole company.
Pull Max Spevack Spark work into a CIQ-managed repository before the announcement, and define the outbound publication path
In the group DM with Nathan Blackham and Brett Mastbergen on Sept 9, Peter pointed at Max Spevack NVIDIA Spark work living at github.com/maxspevack/spark-rocky, noted Brett already has access, and said he would like to get it pulled into a CIQ managed repository, asking one of them to make that happen. He paired that with a request to talk about a process for making it available to the world on the heels of the announcement Lindsay Aamodt wants to make in the coming week or so. He did not route the request through Max. In the same window he told Brett he would try to chat with Max but that Max can be hard to reach currently, and told Lindsay and Bjorn that Max is so hit-miss on getting back to him on things like the benchmark publication.
Cap the Spark benchmark chase at one or two wins - the deliverable is bits in RLC-AI on Portal, not a leaderboard listing
Across four channels Peter set the scope of the NVIDIA Spark benchmark work ahead of the Tuesday announcement. To Nathan Blackham and Brett Mastbergen he said not to spend too much time there, that all CIQ really needs is one test to point to, two is awesome, more is not necessarily better, and that after one or two what is actually needed is the right bits baked into RLC-AI and available on Portal for download, at which point CIQ can declare victory. He also directed benchmark selection by relative rather than absolute result - pick whichever benchmark showcases Rocky best against the other distros on the leaderboard and can produce results quickly, because this is not about the raw number. In the group DM with Brian Dawson, Bjorn Hovland and Lindsay Aamodt he corrected the plan: the leaderboard is third party, not controlled by NVIDIA, CIQ cannot guarantee any posting there by any date, so make plans that involve self-reported benchmarks. With Lindsay and Bjorn he put the third-party publication odds at about fifty percent while calling confidence in CIQ own benchmarks high.
Route the RLC-AI latest-driver override through Bjorn rather than overrule Dawson in the public channel
Peter pushed in #product-rlc-pro-ai that RLC-AI should not sit on an LTS NVIDIA driver, told Brian Dawson to have a conversation with Bjorn that day because Bjorn wanted to go out with benchmarks on Tuesday, and stated that if CIQ is bundling LTS driver versions it should NOT be going out with benchmarks. He then took the resolution off the public channel: in the group DM with Nathan Blackham and Brett Mastbergen he wrote that he had talked to Bjorn, that the team should get moving on the latest driver in RLC-AI right now, and explicitly that he was not putting this in the public channel because he did not want to publicly defang Dawson - Bjorn would talk to Dawson and the team would see a note greenlighting it.
Related Patterns (14)
Executive Sponsorship for Strategic Partnerships
Strategic cross-company initiatives and major client partnerships require executive-level accountability to move at the right pace and ensure proper prioritization.
Protect Engineering Capacity
When external demands threaten to overload engineering capacity, protect capacity by either requiring the demand to come with additional resources, or forcing hard prioritization choices upstream.
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.
Small Circle for Sensitive Operations
When executing sensitive strategic operations, keep the circle of informed people as small as possible to prevent leaks that could accelerate hostile action or undermine the initiative.
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.
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.
Constrain the Mechanism, Not the Access
When AI or automation raises a governance concern, Peter does not restrict who or what may reach the data. He constrains HOW the reach happens, so the pathway becomes auditable and deterministic. The failure mode he designs against is non-determinism, not leakage - a wrong filter in inspectable static code is a bug you fix once, while a model that sometimes pulls the wrong field is an unbounded, unauditable liability. He will therefore accept imperfect filtering and eventual leakage as the price of adoption speed, but will not accept a non-inspectable pathway.