Tim Pepper
Jul 24, 2026 - Oct 30, 2026
7
Decisions
0
Active Todos
13
Patterns
Categories
Decisions (7)
Tim Pepper - push now for an RESF board or leadership role, paid not volunteer, with Peter carrying it to Greg and Bjorn
A long-standing RESF director is stepping off the board. In the 10/28 sync with Tim, Peter said that director had been the adult in the room who built much of the RESF-CIQ relationship over six to nine months and that he feels exposed without him. Tim said a board role is something he could do. Peter said it is not a volunteer seat - CIQ pays people to serve there - and that he would broach it with Greg and Bjorn and carry that ball forward. He also asked Tim to send Xander a no-harm-no-foul note with an open door.
Start the long-tail work to position Tim Pepper for an RESF executive role, as the fallback if Lee does not grow into it
In the 10/22 C-suite sync, after agreeing that the current RESF operations lead gets strategic coaching, Peter added a contingency and asked to start acting on it now: if Lee does not work out, Tim Pepper should already be positioned for an RESF leadership role, including within the RESF. That means building relationships now and working out whether Tim should be a CIQ employee. Peter explicitly framed it as not a change right now. Bjorn pushed for an elevated Tim role regardless; Greg was nervous about the employee question either way and proposed Lee bring Tim in as president.
Get CIQ onto the embargoed security lists, Linux first - treat the absence as our failing; give upstream hours from the Stratum engineers to wherever Tim directs, and let Tim move without waiting on Peter
In the 10/21 Tim Pepper 1:1 Peter set three things. CIQ getting onto embargoed security lists is a goal - Linux matters more to him than Kubernetes - and he views not being admitted as a failing on CIQ side to be fixed by building community trust; Tim brokers the conversations. Weekly hours from both Stratum/Kubernetes engineers (one hired, one req open) go to upstream work wherever Tim directs. And Tim moves things forward without waiting on Peter: invite him to meetings rather than reschedule around him, and Peter will tell his team and Marketing to jump when Tim asks. The upstream/downstream development training Tim plans will include the Linux org.
Six-month push for CIQ to be a better steward of its open-source work beyond Rocky - Tim Pepper advises, with full transparency and a seat in the Stratum open-core call
At Eng Sync Peter introduced Tim Pepper, a contractor helping him think about CIQ positioning across all its open-source efforts (not just the RESF), including Warewulf ahead of the Warewulf offering launch. Tim will join Eng Sync from time to time; his engineering asks go through Product prioritization. Peter named it his big push for the next six months. In Slack, when Brian Dawson opened a task to decide the Stratum open-core vs open-source approach by 10/16, Peter said need to talk sooner and involve Tim; when Ryan omitted a sensitive RESF staffing detail from his OSS summary for Tim, Peter said there is no need to hide anything from Tim.
Affirm CIQ needs an OSPO and commit engineering time to upstream contribution as the entry ticket to new ecosystems
After spending time with Tim Pepper during the week, Peter settled a question Max Spevack had repeatedly challenged him on - why CIQ should have an OSPO office at all - and landed on the opposite of the challenge. He concluded that CIQ must have an OSPO, and that engineering has to spend materially more time upstream to be taken seriously in the ecosystems it wants to sell into: if CIQ is going to put out a Kubernetes offering, it had better be committing upstream to Kubernetes and be valued in that community. Tim gave him the magnitude - roughly a quarter of one percent of commits is enough to be seen and recognised as invested. Peter asked Tim to start building a map of where upstream activity buys the most impact and opens the doors CIQ needs, and said he will task engineers against it.
Cover the OpenELA TSC seat gap personally with Nathan and Leigh, and put Tim Pepper on the RESF relationship question
Sarah Almaraz relayed Arthur Tyde concern in #ea-team that CIQ holds two OpenELA TSC seats assigned to Nathan Blackham and Damen Knight, neither had been participating, and SUSE and Oracle were showing up consistently while CIQ as a founding member was not represented. Arthur asked for three things before the Sept 10 call: confirm Nathan and Damen or name replacements, get a PR submitted for OpenELA issue 36 with confirmed prod access, and name one CIQ engineer to own the import queue. Peter answered with the attendance roster - Myself, Nathan, and Leigh. Separately in the window he told Nathan he has Tim Pepper on as a contractor to look at CIQ relationship with the RESF and how CIQ grows community there, described the role as an OSPO advisor sort of guy here on a contract, asked Nathan for pointers to docs on unifying build infrastructure, and told Nathan to talk to Tim about the structure of his team, how he interfaces with the RESF, and how he wants to evolve that interface. Peter also forwarded Arthur OpenELA TSC threads to Tim Pepper directly.
Approve the Tim Pepper consulting proposal, then push back on the absence of a standard contracting process rather than hand-roll the SOW
Greg forwarded Tim Peppers consulting proposal to Peter on 7/21 with apologies for the latency, and Peter approved it flatly the same afternoon - I am good with this - without asking cost, scope, or management in the thread. He forwarded it to Sarah on 7/23 to get it moving. On 7/24 when Sarah relayed that Gregs next step was for Peter to follow through with the contract, Peter declined to hand-roll it and asked where the standard process was. Sarahs answer confirmed there is not a reliable one - CIQ has done things fast and not by the book with other people, case by case - and she took an action to check with HR.
Related Patterns (13)
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.
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.
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.
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.
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.
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.
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.