Brian Clemens
Dec 29, 2025 - Oct 30, 2026
6
Decisions
0
Active Todos
9
Patterns
Categories
Decisions (6)
Sensitive Decision
Sensitive Decision
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
In the 2026-08-18 C-Suite Sync, Greg proposed DMing Peter, Dieter, Lee and possibly Brian to reiterate that more CIQ people need to be involved and that things need to move faster on the RESF side. Peter agreed to the substance but asked to be removed from the recipient list: So yes, but play this game with me. I think if you send that DM to the list of people you said, which includes me, and now I ask myself how I can perceive that from Brian perspective. I can perceive it as Greg telling his employee, Peter, to involve more people, and you are just notifying Brian that Peter has been told. If I am not on the email, and it is just going to Brian and Lee and Dieter, do you see what I am saying? I think you can speak really differently. He asked instead for a copy sent separately - I would just send it directly to them and then send me a copy of it just so I know exactly what you said - and suggested Greg tell them he expects Peter to be receptive to anything they ask. Separately Peter asked Greg to secure a standing status cadence with Lee, explaining that Lee is the one with the broad overview but does not work for Peter in this capacity, whereas Dieter will supply status on request. Greg agreed to have Sarah set up a weekly or biweekly Peter-Lee meeting, and Peter accepted.
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
Ryan Smith sent Peter a note that Rocky usage via Fedora DNF count-me stats had reversed for the first time since RESF started, correlating with Alma rise, and that Brian Clemens attributed it mainly to Neil and Lewis leaving with Lewis publicly promoting Alma since. Peter posted the whole note to #distinguished-leaders on 2026-08-18 flagged for the next morning meeting, and rejected the attribution: I do not buy that caused 250k less downloads of Rocky Linux. Something smells funny there. When Greg asked for his gut feeling, Peter declined to give one on causation and reframed the agenda instead: What I want to talk about is whether we believe the number is the number we should be looking at. If we do, then I think it warrants attention. If it does not, then I want us tracking a different numbers. In the C-Suite Sync the same morning he repeated the magnitude objection to Greg and named where the analytics capability should sit - that is what Dieter should plug it into.
Brian Clemens — Loop In After Front Door Closes
Decided Brian Clemens should be brought into RESF matters only after the front door is closed, acknowledging he'll be critical for reconstruction but the current phase requires operational security. Conditional on his behavior: 'If he hasn't gone off the reservation at that point.'
RESF Management Model Needed
Identified that RESF needs a clear management person or model as part of short-term response. The lord of the flies approach does not work. Does not matter if its Leigh or someone else, as long as they have personal energy/bandwidth. But it needs to be managed/run with clear accountability.
Related Patterns (9)
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.
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.
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.
Redesign Conditions Over Policing Symptoms
When a direct report names a vulnerability and proposes surveillance-style verification mechanisms (breathalyzers, daily check-ins, monitoring rituals), Peter accepts the disclosure but pushes back on the surveillance model. Treats the verification proposal as a signal that the underlying environment needs redesign — and offers to change the conditions that produced the vulnerability rather than instrument the symptom. Costs Peter optionality (e.g., committing to broker work-hour expectations directly with the partner/spouse) — the asymmetry signals genuine retention vs transactional.
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.
Name It Without Staffing It
Applies when a structural change is directionally clear but the specific person, budget or reporting line is not settled. Peter names the structure - the role, the reorg, the governance reform, the ladder - and deliberately does not attach a name, a req or a commitment to it. The 2026-05-21 observation states the economics plainly: cost of naming is near-zero, cost of premature commitment is high, and he consistently chooses naming. The 2026-08-24 observation adds the sequencing reason: once a specific person is attached to a framework, the framework stops being the subject. Mined from 6 independent observations between 2026-01-12 and 2026-08-24.
Different Diagnosis, Different Remedy
Applies when a directive or a problem spans several people or cases that superficially look alike. Peter refuses a uniform answer and sorts by diagnosis first, then applies the remedy that diagnosis calls for. The 2026-08-28 observation states the consequence for recording his decisions: when he gives a directive spanning several cases, the decision is almost never any single remedy - it is the rule that produces DIFFERENT remedies, and four cases with four different answers under one rule means the rule is the decision. The 2026-04-17 observation confirms he holds this as an explicit framework rather than an instinct. Related to Three-Lever Talent Management but distinct: that pattern runs hire, develop and exit in parallel, this one is about diagnosis determining which lever a given case gets. Mined from 6 independent observations between 2026-02-03 and 2026-08-28.