Justin Haynes
Dec 19, 2025 - Nov 3, 2026
180
Decisions
0
Active Todos
24
Patterns
Decisions (180)
Make it up to Skip for working the GDC fire from a family vacation - money is a given, pair it with time away or something better, and ask him directly
Skip worked the Google kernel deadline from Disneyland during a family trip. Peter asked Nathan and Justin what CIQ is doing for him: money is a given, but asked whether it should be paired with more time away or something else, and proposed simply asking Skip what would make the rest of the trip more magical.
Award the Linux and RAT teams for the CVE onslaught - deliberately sequenced: Greg thanks them publicly, Peter praises them at the Wednesday on-site, award announced then; Greg disowns Ginux-as-replacement
Greg asked whether Peter had reservations about an award for everyone on the Linux and RAT teams dealing with the CVE onslaught. Peter said none and asked for it to be intentional: Greg posts publicly and thanks them (as agreed earlier), Peter praises them in person Wednesday at the Reno on-site, and the award is announced at that point. In the same thread he asked Greg to tell Arthur Tyde that Ginux is not the solution and does not compete with the RLC kernel, because the joke fed the team concern that Greg sees Ginux as a replacement. Greg then publicly called Ginux a research project that will never compete with Linux.
GDC targeted-CVE builds - what fits the existing build machinery ships Monday, everything else is quoted work, slips are attributed to the customer constraint, and a rough estimate is enough
Across 10/30 to 11/2 Peter applied one rule to Tissa asks for 1.16/1.17/1.18 kernels. Default: last week build plus CVE 9999, available Monday because it fits existing machinery. A March-kernel branch with only 9999 is a new branch with no build path or testing, so it gets an ETA, not a commitment. 1.18 by Monday holds only if CIQ can keep rebasing on upstream. He pressed Google to decide that day and asked why they would want one new CVE but not the 37 old ones. On 10/31 he directed that any date change on the sheet state it is caused by Google not wanting the latest driver, and that communicated dates be reinforced. On 11/2 he refused a two-day turnaround by email (dates stay 11/16, one could be pulled in and the other slid) and told Nathan and Justin the message is weeks not days, about 3 weeks, and a swag is sufficient - no more planning effort than that.
Public CVE claims match what is in customers hands - fixed internally is not fixed; engage fast with accurate words
During the CVE-2026-98432 (MPTCP) news on 11/1, Greg drafted Rocky Linux Pro had this fixed yesterday, CIQ customers are safe. Peter said no and rewrote it to separate fixed internally from delivered: We had a fix before you posted this, and are rolling it out across our distros in the next 36 hours. He had already pushed Greg to engage publicly right away. When Justin noted packages reach repos almost immediately and only images lag, Peter accepted patched kernel packages as accurate wording.
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
In the 10/23 Justin 1:1 Peter gave the mapping rules for collapsing titles: no senior or junior variants of any title; when torn, translate someone to the lower bound and keep the ability to promote them; do not bring promotions into the exercise; no salary changes, names only; have an honest conversation about who would be hurt and keep a wart (a senior prefix) rather than generate pain for a simpler map.
CVE automation framing - the goal is zero humans, assume tokens are free to test feasibility, and redesign the flow rather than swap human boxes for automation boxes
In the 10/29 Nathan 1:1 Nathan said CVE automation is moving too slowly and he will push it at next week onsite, using a 1,000-PRs-a-week, remove-the-humans thought experiment. Peter set the frame his org works from: (1) redesign the whole flow, not replace each human step with an automation step - removing humans changes the flow and leaves about a tenth of the cases as error paths for people; (2) assume tokens and machine time are free for the exercise - if zero-human is unreachable even then, stop; if reachable, then discuss cost; (3) parallel attempts in front of a trusted gate are fine, losers aborted. He called it one of his hot-button issues.
Every engineering team takes every product training, due in 30 days - manager carve-outs overridden
Mariah collected per-manager input on which product trainings teams should take; some managers narrowed the list (e.g. Rocky and Ascender only) or wanted 60 days. In the 10/27 HR sync Peter overrode the narrowing for his org: trainings are quick, and the rationale for the PIC team taking Rocky applies equally to the Linux teams taking Fuzzball and Warewulf. Everyone takes all trainings, 30 days. We got feedback otherwise, and we are ignoring it.
GDC new ask after landing Anthropic - write down what we believe, parrot it back, give an ETA assuming funded, and use it to win the added 300K without slowing the base contract
On 10/29-10/30 Tissa came back with a larger ask after Google landed a big opportunity (Anthropic). Peter directed Nathan and Justin: before spending any time, write down what CIQ believes is true and send it to Tissa to validate - (1) what is delivered Monday, (2) the additional ask parroted back to confirm version and build, (3) when CIQ could have it assuming it is funded. Tissa is working to get CIQ about 300K more, taking GDC toward 1M plus royalties next year, and this must not slow signature of the existing contract. Peter relayed Tissa request that CIQ engineers stop saying that is not in the contract and say we will talk to Pete instead. On 10/30 he asked for the CIQ ETA column filled, including future releases, to talk through any gap between desire and capability.
Rocky Linux Pro rename - one disruption, customers told first, structural RLC names stay until there is a value or a problem
Bjorn owned the RLC Pro to Rocky Linux Pro rename and Greg had no objection to Justin convergence doc. Peter set how it executes: Justin 8.10/9.2 convergence changes and the rename ship together so customers absorb one disruption; sales contacts every potentially affected customer first and only then does engineering flip its side (Justin could not action it that morning); structural RLC names (repos, Depot paths, CPEs, bootc and container names) stay as they are; and there is no hard company-wide switch - the public name can slide over a week or two. Jamie Brooks drives the project.
GDC full kernel with IBT off is not just sign the kmod - say no unless it fits, do not reopen the contract, Peter and Kelly own the Tissa conversation
On 10/29, with the GDC contract about to be signed, Google asked for a 6.18 full kernel with IBT off for the following week. Peter framed it in #google-partnership-governance: the ask pushes CIQ from just sign our kmod into supporting kernel development, which CIQ told Google it must staff up for and is still hiring for; it falls back into the CIQ needs to do the live patching work bucket and cannot be delivered in a couple of days. If Justin path works, fine; otherwise the answer is no. He told Nathan he did not need to manage the contract, stopped the engineering thread (Let us spend no more time on this and Kelly and I will talk to Tissa), and refused to change the order of anything or reopen any question while the contract was being signed. He emailed and then called Tissa; Tissa dropped the full-kernel requirement, and Peter confirmed in writing the plan is the minimal kernel with IBT disabled for next week, with Kelly, Nathan and Justin on the thread.
Customer-specific asks go through Work Ingestion and RAT build/validation - no side channels, even under deal pressure
On 10/23 two escalations from Justin hit the same rule. Toss (Viva Republica) AWS private offers, tied to a $2.4M TCV deal with a frustrated customer: Peter joined the channel to ensure the ask goes through regular Work Ingestion - in Jira, with Product visibility, balanced against other work - and aligned with Bjorn that it goes on the product priority list. OCI HPC base image being built outside the normal path: if CIQ will stand behind it, it must come through the main RAT org, which runs the consistent build and validation process; same message in #team-asia-pacific.
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.
Justin org becomes the platform team - and for more than Linux; deep Linux knowledge is needed to build the platform, not to run it
Justin described the shape he is building toward: his team runs the services, automations and connections so the trains just run, and Nathan team owns what goes through the pipes; Nathan dislikes it because he wants everyone to know Linux deeply. Peter sided with the platform shape: everyone knowing Linux is valuable but not central to success, and Justin will end up being a platform team for far more than Linux - Kubernetes, Fuzzball, Apptainer.
Justin - now is the cheapest time to break things; bring every go-faster option to Peter and Bjorn, even the ones you would veto
On the 8.10, 9.2 and 10 product-identity changes Brady wants, Peter told Justin there will never be a time with fewer customers, so do it now and do not wait on Peter reading the risk doc. Justin standing order to his team is to surface go-faster-by-breaking options and veto the too-big ones; Peter changed the filter: options Justin would veto still come to Peter and Bjorn, flagged as too big.
Jira confidence and date updates - the goal is org visibility, not leads pushing buttons; automate the manual part
Chris Wolford apologized for late Jira and value-driver updates. Peter said the goal is org visibility of confidence numbers and target dates, not that Chris personally pushes buttons in Jira, and if the second can be pulled out of the process he is all for it. He wants to discuss automating it at the next staff meeting. Chris noted he uses the updates as a check-in with engineers.
Desktop V1 - a minimum-requirements section from Product, a December to first-week-of-January window, latest-only as the working assumption, and an accepted black eye
With Brady desktop document in hand (the design-plan condition from 10/1), Peter asked for a paragraph or redline at the top listing the absolute minimum requirements for V1, as aggressive and small as possible, and offered a window: something in December or the first week of January. Nathan working assumption is that the first drop is on latest only, not LTS; Peter asked Brady to capture it and call it out if wrong. Brady will schedule a separate LTS discussion since Everfox technically needs it. Peter accepts burning a bridge with one or two customers and taking a short black eye, fixing UI/UX afterward.
Nathan next manager can be hired from outside if no internal candidate fits - and must have managed before, so Nathan never trains a first-time manager while learning to manage managers
Nathan has 16 reports heading to 20 with no manager headroom. Peter told Justin that one of the people Nathan hires into his five open roles must want to manage, have management experience, and be able to pick up about half the team. Internal promotion is preferred, but if none of the internal people can or want to manage, an external hire is fine. Peter does not want Nathan first manager-of-managers stretch paired with bringing up a first-time manager.
Sensitive Decision
Put dates out even at low confidence so the board shows reality, and leads keep evolving their metrics - dropping the ones that get gamed
At Eng Sync, when Nathan could not get the RLC-H compliance deliverables above 50 percent and did not know if four weeks of scope remained, Peter said to put the dates out even if low confidence so CIQ is communicating reality; same for desktop (we do not have a designer, but let us make some dates up). He set a standing ask that each lead update covers how their metrics thinking is evolving - which are valuable, which are not, and why - and that unvaluable metrics get dropped because they are anti-valuable and get gamed. He shaped Justin Thursday company walkthrough: pink (humans) goes away, triggers at the top, a column of what is true at each stage; an assembly line, not a loop, held against Ryan SDLC-loop framing.
Google live patching - set the near-zero-cost kernel flags now, nothing else before commercials, and treat the Tissa call as listen-not-commit
Before the 9/30 live-patch call with Tissa, Peter told Nathan and Justin it was not a commit meeting but a listen-to-them meeting, with the contract worked through later. In the follow-up mpdm, Kelly asked if he was agreeing to do this part now before commercials; Peter said no, then corrected within seconds that he did not mind setting those flags now because it costs almost nothing. Nathan confirmed about 30 minutes to stage plus a few hours testing, riding on a normal kernel rather than a special one. Afterward Peter told Kelly and Bjorn that Alyssa and Tissa were clearly allies on getting this across the line.
Everyone owns their AI spend - no gates or guardrails, but unaware spending is unacceptable
At the AI Committee, the spend dashboard showed Jamin at roughly 33-39k for September. Peter said he will not put gates or guardrails on AI usage, but every person at the company (not just engineers) must know their own spend, the caps and overage thresholds of the tools they use, and treat token spend as part of their cost to the company. A deliberate, informed overage is backed even if Peter would disagree with the math; blind spending is not. Michelle was approved to tell the whole company this is on each person. Ryan 1k overage notification line accepted as reasonable; only Jamin, Sultan and Justin warrant an actual conversation.
Vera Rubin access is drop-everything, the goal is proving it works for Google rather than benchmarks, and kernel pre-work starts now
NVIDIA is working to give CIQ a short window (likely about 5 days, one node) on Vera Rubin hardware, with no advance notice of when it opens. Peter set three things: when the window opens, whoever is involved drops all other work; the goal is getting Rocky/RLC working so CIQ can tell Google it works, not benchmarking; and Sultan starts pre-work now (patch identification, test branch) so the window is productive.
Set the Sr. Application Engineer comp anchor on internal team parity, not on the candidate Amazon total comp
Justin Haynes brought Peter a compensation question on Kristin Cox, a Sr. Application Engineer candidate coming from Amazon, whom Peter had interviewed four days earlier. Peter ruled the Amazon number out entirely - nowhere near that, you are not going to compete with Amazon on TC - and gave Justin the reference class to use instead: look at the rest of your team for the barometer. He named what CIQ is actually selling in place of cash, saying she comes to a startup for the moonshot. He gave Justin the barometer rather than a number, leaving the offer construction with him.
Documentation and training stay in Ryan org - development work does not belong there
Ryan Smith raised that the breadth of what his org produces has outgrown the label customer engineering and asked what Peter sees the function as. Peter separated the container from the placement. On placement he gave a clear two-sided answer: documentation and training legitimately sit with Ryan org and he likes them there, and development work does not belong in that org. Gauntlet was the worked example - Peter thanked Ryan for building it, said that in a perfect world it lived under Justin and should have been built by Justin org, and said explicitly that he does not want the fact that Ryan built it to reshape Ryan world so that more of that happens. He also said forward-deployed engineering will likely grow to dwarf customer support in Ryan purview, and that the title would be VP of Engineering with owned scope explained separately - both of which he treated as secondary to the placement rule.
Treat every RCA as a legal document - Legal review plus Peter personal clearance before it goes to a customer
Peter and Arthur Tyde issued a standing rule to all department heads: unless a customer contract specifically addresses liability, fault and the delivery of a Root Cause Analysis, an RCA is to be treated as an internal document. Before any RCA is shared externally, Legal must review it and confirm it is appropriate to provide, and it must be cleared with Peter personally. The stated reason is that an RCA is a legal document that can unintentionally create legal exposure through statements about fault, causation, or obligations beyond what CIQ has agreed to contractually. Arthur posted the note to #department-heads under a joint Peter-and-I attribution while Peter was in a critical meeting, at Peter request that it be posted with his agreement on the record.
Take the customer breakage now at 100 customers rather than at 300 - but run it through Ryan and sales before it ships
Pushing Justin Haynes and Nathan Blackham on getting three to five times the throughput out of their orgs, Peter asked where the big blocks of time are. Justin said he could do something immediately that would dramatically speed things up but would break some customers. Peter answer: do you want to break customers now when we have 100 customers, or break customers in a year when we have 300? He then attached a condition - everyone sits down, Justin explains what he wants to change and what the fallout looks like, Ryan Smith and sales both understand it, and then it goes. He pre-warned Ryan in their 1:1 that this is coming.
Refuse the Veeam rollback and the never-again promise - fix forward and hold the response until the RCA is understood
Veeam escalated for the third time after a CIQ portal output change broke their CVE scraping script. Melissa Kivisto asked for a rollback and, failing that, a call from Peter explaining a path forward that ensures this absolutely will not happen again. Peter rejected both halves in #department-heads: there is no world where we promise that something will not happen in the future, rolling back is not the right solution at all, we help them move forward and doing so is not complicated. A day later a second breaking change took down their rsync; Peter told the channel there is an RCA in progress and he wants the team to fully understand what happened before responding to the customer.
Hand the Dawson document-noise complaint back to Justin with an instruction - be done with subtle
Justin DMed Peter that Brian Dawson AI-generated document output is an increasing source of wasted time for more people than just him, attached the RLC Pro HPC specification document and a related Jira bug, and closed with no direct ask for you, just awareness. Peter declined that framing, asked whether working it from my side meant being very clear with Brian, got Justin admission that it meant being polite and probably too subtle, and answered - be done with subtle.
Serve Google security due diligence from the Core42 audit corpus rather than rebuilding it in a silo
Justin surfaced that a security organisation inside Google has been iterating on due-diligence requests for months - answers sent, then more questions, then demands for the actual documents, now a spreadsheet with links. Peter told him not to recreate the wheel, because the Core42 audit has already produced most of that material at a far deeper level. He confirmed he had read and approved the seven internal policy documents Steve sent him that morning, with one routed to Greg, and set the escalation line: involve Peter only if Google asks for something more technical than policy paperwork Steve can pencil-push.
Bound the NVIDIA driver auto-update ticket - 24 hours is the product ask, 30 days is the contractual floor
Brady brought a ticket asking engineering to move from manual to automatic NVIDIA driver updates, with a 24 hour target he said Justin and Nathan had already accepted with just prioritize it. Peter questioned whether that acceptance had been priced, then directed that both numbers be written into the ticket - 24 hours as product ask, 30 days as the contractual commitment - so engineering knows the real floor and can choose where between them to stop.
Put the lost-candidate accountability on Justin, and require him to make Jesse Hines say no a second time
Jesse Hines, the top candidate for the Senior Application Engineer role, accepted another offer before CIQ made one. In the 1:1, Justin asked for the miss to land on him so he could take learnings from it, and Peter answered Learn from it. That is good. Yes, please. Period. Full stop. Peter then directed Justin to email Jesse directly - congratulate him, say CIQ still wants him, and ask what it would take - while telling Justin the odds were about 3 percent. In the Mariah sync an hour later, Peter confirmed independently that the responsible party in this situation is Justin, and agreed with Bree that CIQ waited too long because Justin wanted Kristen so badly.
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.
Push speed-over-perfect down into the Justin org and ask him to produce a visible failure that goes unpunished
Peter opened the Justin 1:1 by reconstructing his own discomfort with how he had handled pushback after a talk on AI usage - the pushback was about corner cases, and Peter realised his own answer had been weak. He then asked Justin to reiterate the speed-over-perfection mantra to his people, and escalated the ask: go fast enough that a real mistake happens, so Peter can visibly decline to punish it. He paired this with a demand for QA automation investment rather than manual QA, and set up a next-week whiteboard exercise: what would have to be true to double throughput, what breaks, and what does it cost to stop each breakage.
Give the principle then ask for a map of the ChatGPT license ask - fund frontier-tool access for key people, but see the shape first
In the Sept 10 weekly 1:1, Steve Wallace raised that Moody had been pinged in one of the AI channels about getting more ChatGPT licenses, said he wanted to run it by Peter before enabling anything, and offered that what he owed Peter first was probably what this would cost. Peter neither approved nor refused. He named a specific person he was comfortable licensing, confirmed Sultan already has one, and asked Steve to get a map of the ask. He then supplied the governing principle: these tools leapfrog each other, so some of CIQ key people having access to the competing vendor tools is critical, and it is fine.
Evaluate Aisle AI for CVE discovery and pursue tool access - downgrade the urgency, upgrade the scope
Greg Kurtzer flagged a ZDNet article in #distinguished-leaders reporting that the AI tool Aisle found six curl vulnerabilities that Mythos and Codex missed. Peter answered Greg immediately that he had not seen it yet and would get the team on it that morning, and in the same window put Nathan Blackham and Justin Haynes on it in a group DM, forwarding the article with the instruction to take a look and be proactive here. About two hours later he came back to Greg with the substantive answer: the CVEs are low severity, CIQ is evaluating whether it can provide an easy fix, and CIQ is working to get access to the tool for future use.
Let the dual-loop candidate pick her team - then stop the other loop rather than finish it
Kristin Cox was interviewing for open roles in both Justin Haynes org and Chris Wolford org. Bree wanted her steered toward Wolford req on the grounds that it had been harder to find strong candidates for. Peter overrode that without debating it. His instruction: have Bree ask the candidate directly which role she is most interested in; if she picks Justin, stop the Wolford process immediately and get an offer out as fast as possible; if she picks Wolford, let that loop finish. He told Justin to be selfish about it and said he would write to Bree himself. He also stated plainly that all else equal his thumb is on Justin side of the scale, because he is far more worried about delivery on the Linux side of the house than on the Fuzzball side.
Sensitive Decision
Sensitive Decision
Stay current on NVIDIA drivers - build the automation, and do not ship RLC-AI again without the latest drivers
Greg flagged in #distinguished-leaders that the NVIDIA contract obliges CIQ to distribute the latest drivers within 30 days of release, and that CIQ has drifted. Peter took it to Nathan Blackham and Justin Haynes in their group DM the next morning, told both that he had not had the 30-day obligation in his head either, and asked them to put some sort of process in place to stay current. Nathan opened ENGD-839 for the automation; Peter told him to slot it right around where the next RLC-AI drop lands. Separately he told Product the gate plainly: it makes no sense to put out RLC-AI again without updating to the latest drivers at the very least.
Put the NVIDIA Spark bootable-Rocky USB on Justins org - and size it to carry meeting materials
On 9/2 Arthur Tyde asked whether CIQ could produce a Rocky-on-NVIDIA-Spark artifact for events. Peter confirmed the current Spark version of Rocky already is a bootable USB stick and called it super doable, then named the constraints and the owner. Constraint one: the image he holds is old, the current one sits with someone who is out, and he expects to have it in a couple of weeks. Constraint two: it only runs on an NVIDIA Spark - a Mac or other target would need different packaging and drivers, which is a separate ask. He then allocated the work outright: Justins org can build something. He also specified the form factor rather than leaving it open - small ones are fine, like a 128 gig would allow us to include additional meeting materials - turning a bare boot stick into a carrier for collateral.
Answer the Gauntlet adoption fight as a cross-team communication problem and take it to the managers meeting as a case study rather than mandating the tool
Ryan Smith team reads core engineering non-adoption of the Gauntlet test framework as a not-invented-here rejection. Justin Haynes team has an existing test harness that already meets their needs, so Gauntlet does not solve a critical pain point for them and the switching cost and risk are high. In the 2026-08-28 Justin 1:1 Peter diagnosed the friction as a communication breakdown rather than a technical one, and declined both available shortcuts - he did not mandate adoption and he did not arbitrate the tool. Instead he took it as the concrete case study on cross-team dynamics for the next managers meeting, with an action item on himself to add Gauntlet and cross-team communications to the Tuesday Horde agenda and to ask Justin to remind him.
Diagnose every AI overage case individually and apply the remedy that case calls for - without squashing AI usage
Facing an AI token run rate heading toward roughly 3 million dollars a year, with the top ten spenders accounting for about 95 percent of it, Peter refused both a spend cap and a single blanket fix. He directed each manager to work out why the overage is occurring for their own people, case by case, and to do whatever is appropriate for that specific cause - with the standing constraint that the answer must never be to suppress AI usage. He gave different answers for the cases he had already looked at himself: one engineer at roughly 60k a month is justified and was told to keep going; two others at roughly 100k a month between them are low-return and their manager was already digging in; Zorina team burned 12k in August purely because they were hitting the Claude API directly rather than the enterprise plan, so Justin Haynes action is a plan switch. Peter also declined Ryan Smith push to have the AI committee issue a company-wide best-practice policy on spend.
Sensitive Decision
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
Across the Friday roundtable and the Nathan 1:1 Peter restated a hiring rule he had previously given as no more Amazon blood. In the roundtable he opened on the first candidate by saying he almost wanted to disqualify him purely on years of Amazon experience, that it has become absolutely critical to get a broader set of blood into the organization, and conceded that since stating the rule he has let two more people in and gets why. He then corrected Nathan reading of it - it is not about bad Amazon, it is that there is so much Amazon that there is not enough discussion about how we solve problems. In the 1:1 he specified it precisely: the thing he is pushing on is how you internalize the risk of not moving quickly. At Amazon the cost of slowness is somebody misses a promotion or a bonus; at CIQ the company goes under. He said Nathan is not less aggressive because of ability but because he has not had a startup collapse underneath him, and that what it boils down to is a few more people in your org that just have experience at startups. He closed by saying explicitly he is not shooting for differences in how people think about Linux - it is differences in work experience.
The five-week leader presentations are baseline once, then deltas forever - show me what you changed to move the number, not the same dashboard
Closing the Engineering Weekly Sync on 2026-08-18, Peter defined what the recurring per-report presentations are for now that nearly every direct report has completed one iteration. He said he is deliberately giving little feedback on the first round because its only job is to set a baseline for each team. From the second round on he wants the conversation to be about what changes the leader is making to drive improvement in the metrics they report, what they are changing when those changes do not produce the expected movement, and whether the metrics themselves should still be the metrics. He explicitly said he does not expect the org to be tracking the same metrics a year from now and that this is fine.
Refuse to start the incident-response conversation from the premise that an on-call system is needed - require an SLA first, and put accepting overnight downtime on the table as a real option
Ryan brought Peter a plan: after the Portal outage he had asked Justin and Nathan whether engineering had an on-call rotation, got a no, and wanted to build one at the Tuesday Aug 18 meeting. Peter agreed to the meeting, added Chris Wolford to the invite, and then inverted the agenda. His first question would be do we need this - not dismissively, but because he wanted both branches evaluated: accept that some systems are down overnight and publish a status page the way Apple does, or commit to short SLAs and staff an on-call rotation to meet them. He named the decision rule: define the SLA for each class of thing first, and if any SLA is under 12 hours, that implies on-call; if none is, it does not.
Set a six-month horizon on migrating low-value work off Damens plate - naming it the one change he requires from Justin, while refusing the headcount answer until the work is concretely scoped
Following back-to-back 1:1s with Joseph and then Damen - the second scheduled entirely because of what Joseph said, which Peter confirmed unprompted as 100 percent of it - Peter reported one yellow flag. Damens interrupt load splits into two buckets: stuff that is worth his time and stuff that is a complete waste of someone with his brains time. His judgment: he is fine right now, but if he is still carrying that percentage in six months, I do not think he will be fine. So it is figuring out how we get stupid off of Damens plate. But that is it. That was the only significant takeaway for me of a change that I need to ensure happens. And it does not have to happen today. It is just, it is a migration. When Justin floated hiring college students, Peter declined the shape while keeping the door open: I do not want to bring in three college students just because, but if you can stare at something and go, one relatively smart kid could hold the reins on these things and free Damen up, yeah, I am happy to have that conversation - I am going to want to have a conversation in a concrete manner around what you want this person or persons doing. He tested the AI substitute first and rejected it for a specific reason: can AI do the stupid work in front of Damen, and when Justin said that is what he uses it for, Peter pushed back - that is what he uses it for, but it is still him driving it, somebody has still got to drive it.
Sensitive Decision
Declare Jira a system of record and not a venue for process debate - shut the product-prioritization thread and move it into a room
A process argument had been running in the #product-prioritization Jira-linked thread since Jul 29. Peter cut it off with a purpose statement rather than a position on the substance: I want to make one thing clear. Jira (and slack) are not conducive to good process debates. Jira is a great system of record. That is all. Lets just get the right people together in a room and talk - this should be a collaborative process on both sides. He tagged Bjorn to make sure it was seen, then closed the thread explicitly - then maybe we leave this thread alone until that meeting - and named the cost he was actually reacting to: the ripples this thing is creating across the company are substantial and unnecessary. All on the same team, all trying to get to the same place. Two days later he applied the same instrument to the adjacent board question in #department-heads-engineering: just remember the goals of the two boards, and that by definition it is not true that everything on Product Priorities has to move to the Eng board.
Treat prototypes crossing from Product into Engineering as a feature rather than a burden - the code is worth two days, the market learning is the payload, and every one arrives with headcount
Justin raised Elm - a prototype somebody had been building for about three weeks and which was apparently launching the following week - and assumed it would eventually become his problem without the bandwidth to carry it. Nathan had objected in stronger terms that we cannot launch things without engineering being deep into it. Peter sided against both of them and with Bjorn, and gave the reasoning in two parts. On the code: it is a prototype, nothing more than a prototype, the amount of code there is not more valuable than two days, it would take two days to recreate it from nothing, so when it does come over to our side of the fence it is not like we are burdened with a pile of architecture that is terrible and horrible to manage. On what actually transfers: all we are burdened with is what we have learned in the market about what people want from it, which is an awesome thing to be burdened with - because now we are burdened with these two customers wanted to do these things, instead of Brady woke up one day and had a brain fart and decided that this is what a product should do. He then removed the capacity objection three separate times: it will come with headcount. Two, and you are seeing Ascender come your way with headcount, period. Everfox desktop with headcount, Kubernetes with headcount. So it will come with headcount, period. He named the contrast with their shared past - it is a very different model than anything we would have done at Amazon - and pushed the logic further with Bjorn, suggesting Satellite be announced with a go-to-market and a feature list without actually making the software available, to see who rings our front doorbell. He also accepted Justins counter-constraint on feature bloat and added his own: we can cut features too, I do not mind us removing features and seeing if nobody ever notices.
Make the LG meeting 100 percent about understanding their problem - no selling, no refusing - and pull Justin in for that purpose only
After a Jul 30 pre-brief in which the sales team delivered what Peter called a giant mea culpa - we are sorry we have been pitching solutions that do not work, but we still want to do something for LG, and we have realised we do not understand LGs problem - Peter set the shape of the next meeting explicitly in his Justin 1:1. I want to make that meeting 100 percent about understanding their problem. Not telling them, no, we will not do this. Not telling them, no, we cannot. Just lets understand their problem. And then you and I will come back and we will write down what we think is a good thing for CIQ to do in response to that. One option might be walk away. One option might be, I do not know what. He was equally explicit about what the invitation was not: the signup is not, hey, Justin, look what you get to build. Step one is we are going to go chat, learn. He also drew the line he will hold once a response exists: I am going to stand on, if we provide it, we are giving some surety that it is supportable and that it will work. And even if we shake your hands on you are not going to come back and complain at us, we know you are going to. So I want to make sure we are staffed for that. He distinguished that from not blocking them - well, we are not going to stop you, and that is different from we are going to provide it. He admitted openly that he cannot currently explain what LG actually wants: they seem to want a repo that does not point at anything, and I do not understand why they would want it or what problem they think it is solving.
Crown Andrew owner of NARF with real authority and an explicit cannot-wait instruction - accepting the recommendation while rejecting its stated rationale out loud
The programs previous steward produced an assessment of why NARF had not moved forward during his absence, with recommendations. Peter read it and took the main one - hey, Crown Andrew is king of NARF, I am fine with that - but named his objection to the logic in the same breath: the one problem I have with it is it is Crown Andrew is king of NARF, in part because Andrew has not moved NARF forward. I have trouble with that linkage. But whatever, I can get over it. He then converted the recommendation into a delegation instruction for Justin with three distinct components: You need to tell Andrew he has to own this thing. And run it like he owns it. He has got the authority to do what he wants with it. He cannot wait on the previous steward. The last clause was the operative one - it pre-emptively removes the dependency that had produced the stall, rather than waiting to see whether it recurs. He linked it explicitly to the stewards impending step-back from day-to-day delivery. Three days later the org-wide announcement named the handover of NARF stewardship to Andrew and Nathan as a fact.
Price the Google live-kernel-patching ask at 2 HC for 3.5 months plus 1 ongoing, and take the honest slower timeline back to Tissa rather than fit their October date
Tissa asked for a quote on live kernel patching as paid work in addition to the existing monthly full-kernel contract: evaluate whether an incoming CVE patch can be delivered as a live patch, deliver it that way when it can, and still roll it into the next monthly drop. Volume unpredictable - might be 70 percent of a months patches, might be zero. Google wants something working by October so they can test before a January go-live. Peter opened the request to Nathan and Justin with a pre-commitment that removes the usual objection - assume we get headcount to cover this work - then interrogated the shape rather than the number: 2 engineers for 3-4 months and less ongoing, or 2 forever? He landed on 2 HC for 3.5 months and 1 ongoing after that. He then did the arithmetic out loud against Googles date - lets assume a month to hire, and 4 after that to have something, as the reasonable case - concluded I think that gets it to them too late and they will say no, and chose to go back with it anyway: but lemme go back to tissa with that and see where it lands. He closed with lets go fishing and see what we can catch. He also flagged that Tissa appeared unaware of internal discussion on the topic - Tissa seemed in the dark - and asked whether that discussion had ever reached Google.
Mondays session with the Linux org is universally positive - period, full stop - and any fix-things conversation goes to a separate meeting
Gregs company-wide 1:1s surfaced that the Linux organization - Nathans and Justins teams together - is measurably less optimistic about the future of the company than the rest of CIQ. Not massively unoptimistic, but a clear differential. Peter checked the instrument before trusting it: he watched a couple of recordings of Gregs 1:1s just to make sure that he was not leading the witness and asking the question the same way in all of them, and judged he was doing a pretty good job of it. His response is a Monday session with Nathans team, and he set a hard constraint on its contents. Content: state the finding transparently to the team, then walk them through what he is seeing in the Middle East from his second trip and from the Axiom Space meetings - we are seeing a massive uptick in our ability to do business - then walk them through what dealing with Google over the last week and a half has been like, explicitly attributing his own ability to do it to their groundwork: I got to do that because of the work that your team has done, laying the groundwork, and I want them to hear that, understand it, I want to thank them for it. Constraint: It should be just a universally positive meeting with your team on Monday. Period. Full stop. And I really want it to stay focused on being a universally positive meeting. If there are places where we want to talk about fixing things or tweaking things, that can be another meeting. But I do not want to muddy the message at all. He also gave Nathan the entire rationale in advance rather than staging it - I will say all of this to them, super transparently.
Nathans user-space recs are the highest-priority reqs in the company - told him to ask Brie directly whether they are her top priority and escalate to a three-way if the answer is no
Nathan said his biggest focus is hiring, that Brie had not moved anything on the Linux user-space side while he was away for two weeks, and that he would push her hard and dedicate his own time to it. Peter escalated the framing rather than the complaint: You should also be really comfortable asking Brie, hey, are my recs your highest priority? I am really curious what she would say. I hope she says yes. If she says no, it is probably worth a conversation with you, me, Brie, and whoever else rec she thinks is a higher priority. Then, unprompted: Because I think your recs are the highest priority in the company right now. Nathan has five open recs - three user space, two kernel. Nathan also floated an October/November Linux offsite for his team and Justins, and Peter tied its value to how much of the hiring is done by then.
Confidence numbers stay human and per-leader - Brady translates them, Engineering does not remap to his scale
Bjorn brought Brady Dibbles push for a uniform, consistent cross-team definition of the confidence column. Peter rejected it in a DM thread on 7/29 evening and repeated the same ruling to Nathan on 7/30. Confidence is a human thing. That is why we call the column that. It is not computed immutable expectation of delivery for a reason. Justin is risk averse, so he will not put a 99 when he can imagine millions of ways for something to go wrong. Another leader might. The team will learn over time what Justins 90 means. On Bradys ask: the real and only question is what does Brady want to do with these numbers that he cannot do - what is he going to do with a 95 different than a 90. If Brady wants to turn the numbers into high/medium/low or into ranges in his own process that is fine, but that is him translating, not asking Engineering to fit an arbitrary mapping. If he wants a structured definition of exactly what high/medium/low means, now he is losing the experience of engineering leadership and having a function fill out his numbers. Peter also rejected high/medium/low outright: the minute you have high/medium/low it is not functional enough and you end up with twelve gradations and the same problem. And he told Bjorn to test it empirically - ask Duane if he can work with the numbers Justin is providing, the answer will be yes.
Run a Monday state-of-the-Linux storytelling session on pipeline, and have Baek carry the same rah-rah into the all-hands
Acting on a morale signal that surfaced in Gregs round of one-on-ones, Peter committed to sitting down with the Linux org on Monday to walk them through what he is seeing in the Middle East and with Google. He framed it explicitly as storytelling and cheerleader rah-rah about why he feels so bullish, not as a status update, and asked Chris Baek to sprinkle a little bit of the same into the upcoming company all-hands. He gave the diagnosis comparatively - the Linux org is meh on our future while Fuzzball is gangbusters and Ryans org is gangbusters, and there is no reason for Linux to be less positive about our future than everybody else - and bounded the response with it is not a risk right now. Sarah had already blocked Monday for the session.
Confidence must rise as the target date nears - slide the date early rather than carry a 60 percent to the wire
Reviewing Justin Haynes automated-repo-testing item on the NGD board, Peter ruled that a low confidence number a few days from a target date is itself the failure. His instruction: this close to the end of the week we need to be communicating to the company, through those two numbers, whether they are getting something - so a few days from the end I do not want to see a 60 percent confidence number, what I want to see a few days ago is that date sliding out now so that we are communicating a higher confidence number when we are this close to a target date. He grounded it in consumer value: the company cannot do anything with 60 percent confidence July 31st, they cannot take attention on that. Immediately afterwards, when Duane Carson acknowledged a cross-team miss on the 10-2 bits, Peter drew the complementary line - I do not mind misses as long as the team recognizes, hey, we have a miss here, and here is how we are going to get better.
Sensitive Decision
Every org owes its own delivery-performance metric system, and Wolfords dashboard is the deliberate exemplar - used to train the Linux side of the house
Peter restructured the 7/28 Engineering Weekly into a fast breadth-first TPS pass followed by a single-org deep dive, and made Wolford go first on purpose. After Wolford walked through his PIC tooling - PR review latency, time-to-merge, bug-vs-feature ratio, commit distribution, release cadence, internal and external documentation coverage, plus a per-quarter epic assignment board - Peter named the ask explicitly: I dont care whether there is a dashboard or just a system that reports a set of metrics, but this is the kind of thing I am going to be looking for from every org. It is not an accident that Wolfords going first here. He then propagated the exemplar three ways: forwarded the Fathom recap to Bjorn saying he was using it to help train the Linux side of the house, told Nathan to watch the recording because there are critical things in there that will impact your teams and that I want to be able to talk through in terms of team management, and told Wolford directly that the presentation was exactly what I wanted/needed to kick that all off - while warning him you will not be impressed when Linux and the other portions of eng deliver theirs. Sarah set the rotation: Wolford, then Nathan, then Steve, Ryan and Justin.
Re-ruled the two boards from first principles in the room - prioritization vs dates-and-confidence - and told the org to delete any column serving a third purpose
Seventeen minutes of the 7/28 Engineering Weekly went to re-landing the board doctrine after Ryan reported that Chris Baek had told him all work must move to the Engineering Deliverables (NGD) board. Peter said flatly he is wrong, then re-derived both boards from purpose. Product Priorities board: prioritization only - not work tracking, not delivery dates, not confidence numbers - and engineering continues to own the engineering-order-of-operations column that has existed for nine months. NGD board: only work that must be visible to the company because it is tied through value drivers to go-to-market, with exactly two required fields kept current in real time, a confidence number and an engineering target delivery date, and no statement about whether items are epics, stories or tasks. He also ruled that Wolford does not get to choose whether his work appears in NGD, that internal-quality-only work should not be on NGD at all, and that where duplicate order-of-operations columns exist the answer is derivable from purpose - if there are columns there to serve any other purpose, they are wrong, remove them.
Kill the reuse justification - the LG solution does not get to be reused for other customers
In the multi-party LG group DM with Bjorn, Arthur Tyde, Ally Cho, Tommy Ho Sung Yi and Justin Haynes, Peter closed off the argument that building the LG package-layering solution would pay for itself across the customer base. His construction: either every customer would need different testing, or CIQ would be handing customers packages it had done zero testing on. He named the second branch as not good business, and restated the conclusion in plain form - that is another way of saying the solution for LG does not get to get reused for other customers.
Three non-negotiables on the LG U+ RHEL-layering path - drawn before the technical debate, with a lawyer-and-everybody-else escape hatch
After Howard produced a document mapping what is technically possible for layering CIQ/Rocky packages onto a RHEL host, Peter opened his reply to Bjorn with three flat lines: (1) we are not going to take CIQ packages and present them as RH packages, (2) we are not going to have CIQ repos that point to or include RH key files, (3) we are not going to host any RH files ourselves. He named the Oracle precedent Howard cited - listing RH as its own EFI vendor directory - as something CIQ can do technically but not legally or morally. He then supplied the only conditions under which he would revisit: a room where everyone confirms they understood the question, a lawyer who agrees, and evidence that CIQ would not be the only party doing it. Even then he held that it remains another release chain that is real work.
Team meetups are gated on a defined purpose and a purpose-derived attendee list, not on getting people together
Joseph Tate flagged that Justin intends to ask Peter about a team meetup. Peter pre-decided his answer: supportive in principle, conditional on sitting down and writing out what the gathering is meant to accomplish before it is scheduled. He extended it to the attendee list - the right set of people falls out of the purpose, so it may be a subset rather than the whole team. He anchored the default against the companys remote choice: the company chose to be a remote company and we kind of got to live with that.
Endura scope for CIQs own pipelines - include Fuzzball, Warewulf, Ascender and Depot; exclude Apptainer
Eric Sheridan of Infrared Security updated Peter on the Endura proposal for securing CIQ build pipelines, noting Nathan and Justin had reviewed the Koji integration strategy positively and that Bjorn was excited about using Endura to protect Rocky core packages. Eric asked whether scope should extend beyond Rocky to Fuzzball, Warewulf, Apptainer and Ascender. Peter replied to include Fuzzball, Warewulf and Ascender, said Apptainer should not be necessary, and added a product Eric had not asked about - Depot - on the grounds that projects which serve CIQ products to customers should be included as well. Pricing follows this scope, and a call with Greg and Bjorn was set for Wednesday.
Ascender-orchestrates-Warewulf belongs in Ascender Pro as paid-tier differentiation; route Josephs proposal to Zarina
Joseph Tate proposed tightening Ascender and Warewulf together - Ascender able to tell Warewulf to do things, and Warewulf passing data back at boot so a system auto-registers into Ascender Pro inventory and kicks off its own deploy, closing the gap between a system launching and being configured. Peter ruled it in immediately and specifically into Ascender Pro as paid differentiation, leaving open for debate whether any of it belongs in free Ascender. He directed Joseph to write a half-pager or one-pager and send it to Zarina, declining Josephs offer to build it himself and declining to take it into his own queue.
Let Brady raise the kernel-team cloud-resource block in Engineering Weekly, with the test being whether Justin agrees there is a problem
Brady Dibble DMed Peter saying he intended to surface in the Engineering Weekly a flag from Maple that the kernel team is blocked on cloud resources and is being redirected to Outfitter instead of getting the access it needs. Brady noted he had checked with Justin first, was raising it early because every day is precious for the kernel team, and explicitly offered to drop it if Peter preferred to handle it internally to Engineering. Peter replied: you can raise it, the only question I am going to ask is whether Justin agrees there is a problem.
Make metric design the single biggest ask of Max - 10 auto-reported metrics spanning Justin and Nathan, delivered by Thursday
In the Max 1:1 Peter redirected Max away from personally fixing NARF reporting bugs and toward crafting the metrics that Nathan and Justin will present against at the engineering all-hands and the Tuesday meeting. Peter framed it as if I have a single biggest ask of you, it is help craft that. Max committed to writing a list of the ten most interesting metrics he would want reported automatically in a dashboard anyone can look at any time, spanning both Justin and Nathan, by their Thursday 1:1. Peter stated he will work Nathan on the people-management side but wants to do it through the lens of achieving those metrics.
Codify how engineering answers sales - bugs get fixed, out-of-scope features get a no, and the only next step is Product not re-escalation
Coming out of the LG episode Peter laid down the operating rule in writing in the temp-lg channel: Engineering will respond to sales requesting a fix for a bug and will deliver that bug fix without product involvement. Engineering response to a sales request for a new feature that falls outside currently supported builds or plans is no. The step after that is for Product to get involved. In the meeting he attached three companion rules: re-escalation after an answer has to stop, engineering should stop saying you can try it and it might work in favour of that is not supported, and CIQ must present a unified front so no internal voice tells a customer something is a bug after engineering has ruled it is not. He also drew the line between discussion time and decision time - internal deliberation should not be shown to sales as if it were still open.
Definitive no to LG U+ cross-distro package support - the test is whether we would ship it down the middle for everyone
LG U+ wants to run DNF update on RHEL servers pointed only at CIQ/Rocky repos, which touches bootloader packages and breaks the system on reboot. They rejected the exclude-packages workaround. In the LG - Next Steps meeting Peter refused to let the discussion be about whether the ask is a bug or whether it closes the deal, and reframed it to a single question for Justin: is this something we would do down the middle for everybody, or is it one-off work for LG. Justin answered we cannot support it. Peter then gave the definitive verdict: no, this is not something CIQ Engineering is going to support. He posted the same conclusion in the temp-lg channel after aligning with Bjorn, and handed customer messaging to Bjorn with Tommy and Art.
Reclassify the GDC MIP-listing disclosure question as a contract-timing call and route it to Kelly Hall with a decision criterion
On 7/23 Brady Dibble escalated to Peter, Bjorn, and Kelly that CIQ still had not told GDC the 8/8 MIP listing was at risk because the ESV certificate had not arrived from NIST - and that atsec had flagged NIST not asking for review or comment, typically meaning they had not reached the certificate. Justin Haynes pushed back directly with why would we not let them know. Peter did not answer the disclosure question. He assigned it: this is a Kelly Hall call, and supplied the criterion - whatever path is most likely to get a contract signed in the next couple of days. The thread resolved as non-disclosure, with Bjorn stating he would not flag it and Justin later confirming they did not bring it up and neither did we.
Slow-roll Googles request for kernel-build documentation until the contract is signed
On 7/23 Google asked CIQ for documentation on how it builds its kernels. Peter decided to slow-roll any response until after the contract is signed, and said so in both a group DM and directly to Justin Haynes - correct, at least until contract is signed, after that I am fine. He read the motive out loud: they are asking so they can build their own.
Narrow the NGD board to cross-company coordination only - not a deliverables tracker and not a complete decomposition of product acceptance criteria
In the 7/24 Brian Dawson / Brady Dibble sync Peter ruled against the working assumption that the NGD board is the comprehensive ordered list of engineering deliverables. His ruling: the boards only purpose is coordination across the company for things that drive value. It is not for tracking deliverables, not for holding engineering accountable to delivery dates, and does not need to be a complete decomposition of the acceptance criteria in a product ticket. Anything that should not link to a value driver is a component and belongs in Jira, which Peter will never look at. Engineering may blend several product-priority items into one NGD ticket or ship one top-level ticket, as long as the board forms a palette that overlays the product priority and engineering can say when these are done, this product priority is complete. Separately he fixed the product priorities list as strategic priorities full stop - no delivery dates, plus an engineering order-of-operations column and nothing more.
Release the Google 6.18 build; hold the line on future deliverables until Google resolves the LTS question
On 7/22 Peter lifted his own 7/21 hold on the Google/GDC 6.18 image. He connected with Bjorn first, then told Justin Haynes in #google-partnership-governance and in DM to Kelly Hall: give Google the build. He emailed Tissa Senevirathne at Google the same morning confirming the release, restating a firm stance that the LTS work has already been provided to Google, and stripping Mahdu and Alyssa off the thread. He paired the release with an explicit condition: future deliverables are held until Google sorts out the LTS commitment.
Pull the business side (Kelly) into the FIPS 6.18 CAVP-retrigger vs fork call
Justin flagged that upstream 6.18 LT landed hundreds of CVEs/fixes touching the crypto code being FIPS-certified, forcing a choice between re-triggering CAVP (risking the 8/8 Google delivery) or forking/reverting the kernel (a growing maintenance burden). Justin was inclined to retrigger CAVP and risk the timeline. Peter did not make the technical call himself - he decided the business side must be convened, with Kelly Hall involved, because the choice puts the Google 8/8 delivery at risk.
Hold the Google 6.18 image as contract leverage - nothing ships to Google without Peter say-so
Both 6.18 kernels (default and minimal) were built and validated by 7/17, but Peter instituted a delivery-control gate: no kernels go to Google without his explicit say-so, and delivery-timing questions route to Kelly Hall. The build is done; the only remaining gate is contractual, so CIQ holds the finished image as leverage until GDC signs and resolves the outstanding payment. The ultimate release decision Peter deferred to Bjorn and Kelly.
Support Nathan CVE-first prioritization over the Google minimal-kernel delivery; own the customer comms
Nathan flagged that in-flight critical local-privilege-escalation CVEs collided with the committed 6.18 minimal-kernel delivery to Google and called for CVE remediation to come first. Peter backed that call rather than making it: agreed to a bounded slip (no more than a week, not three), was comfortable asking the team to work a weekend to verify already-built patches, and took personal ownership of communicating the slip to Google - framed as value-add (surface only the CVEs Google benefits from), not an apology. Peter wrote and sent the explanatory email to Tissa and the Google team the same day.
Reinforce that an automated Linux CI/CD pipeline is one of the top-3 H2 company objectives
Peter had already set an automated Linux CI/CD pipeline as one of CIQ three top company objectives for H2 (base decision not previously captured). In the Max 1:1 and Engineering Weekly he reinforced to people that it is there and that it is critical to Linux delivery - a company objective, not just a Nathan-team objective. Logged as reinforcement.
TPM charter + one-owner-per-release accountability mandate (problem/solution/owner grid)
In the TPM sync with Chris Baek, Peter locked an accountability framework: TPMs solve problems and coordinate but do not own engineering processes (engineering owns its own processes and its coordination with Product); every new process must be defined on a 3-column grid of Problem, Solution, and a single named Owner; and every release gets one clear accountable owner (one throat to choke) empowered to make the go/no-go call. The incomplete NGD board is the named blocker, with engineering managers (Nathan, Justin) accountable for completing it so it feeds dates and confidence into the Value Drivers Board bottom swim lane.
Re-institute and enforce monthly performance conversations across engineering managers
Peter decided to re-institute and enforce lightweight monthly 1:1 performance conversations (a few minutes each, using the shared spreadsheet) as the real accountability mechanism for managers and their directs — and to restart doing them himself with his own directs, having admitted he had fallen off. The point is catching misalignment on goals and deficiencies early rather than letting it fester for months.
Sensitive Decision
Intent to move Ascender to Zorina with dedicated headcount; stays under Justin for now
Peter decided the direction for Ascender (and Ascender Pro; Ledger Pro pending a Bjorn confirmation): move it under Zorina as a clean, dedicated product home, with headcount Peter has secured for Zorina to hire a team (Bay-Area-first, lightly). For now Ascender remains under Justin — NOT Nathan — and the move to Zorina is directional intent, not yet executed. Larry and Jimmy (original engineers) move to sales-support under Bjorn. Intent is to productize Ascender like any other shippable product rather than leave it an orphan.
Prioritize RLC 10.2 to the top, drop AI+H work — and validate the JPD deprioritization as correct
After a Citadel-driven escalation (10.2 needed for a ~$200k contract + expansion), Peter pulled Nathan, Justin and Max into a 5-minute call, made 10.2 priority-one for Linux eng above RLC AI and H work (only 3 critical CVEs rank higher), and was willing to drop other work if needed. He then posted an actionable timeline range to #department-heads (inner bound Fri 6/19, outside June 30, gated by CVEs). Crucially, he endorsed that the team had correctly deprioritized 10.2 per the JPD board and framed the whole episode as a communication failure (Bjorn got a single June-30 date without the range/assumptions), NOT an execution failure.
Mandate CIQ build/test pipeline converge with the RESFs — one unified project, Nathan accountable, coordination over speed
Peter laid down a mandate that CIQs Linux build/test pipeline will become functionally identical to the RESFs over time — a single consolidated project rather than parallel tooling. Nathan drives and is held accountable for closing the CIQ-to-RESF gaps (hardware parity, cut over to Koji, mirrored build infrastructure, a full validation framework that runs PR-specific tests). Justins build world must sign on and use it everywhere. Ryans gauntlet/outfitter tooling and Leighs RESF-side work are welcome only if they plug into the one project rather than forking. Peter explicitly chose coordination over speed even though it slows Ryans faster build-it-now instinct.
Value Drivers Board becomes source of truth for engineering dates and confidence; JPD dates become computed
In the 6/03 working session that Peter recorded (Peter + Nathan + Justin + Chris Baek, during the in-person engineering F2F), Peter locked the architecture that distinguishes the JPD from the Value Drivers Board. JPD stays purely for product strategy and prioritization (not work tracking). The Value Drivers Board is the Engineering-to-GTM coordination instrument that captures context (the why) and dependencies. The concrete decision: engineering target dates and confidence numbers live on the Value Drivers Board engineering lane as the source of truth, kept current on a tight cadence (always right on a Friday), and JPD dates and confidence become computed properties pulled from the Value Drivers Board rather than manually entered.
Reward Yesh for responsible disclosure — CIQ first-ever bug bounty
When Yesh (pentestine@gmail.com) reported a ciq.com vulnerability on 5/21 via email, Peter responded within minutes to Steve Wallace and Bjorn: I would like us to reward here to encourage this behavior. He immediately forwarded the bug detail to Justin Haynes for the fix and aligned with Steve on severity. The reward is still pending execution as of 5/26 — this is the first bug bounty CIQ has ever paid.
Joseph compensation bump approved; future raise asks must come with story not tenure
Joseph asked Peter directly for a comp bump citing financial hardship — Peter approved on the spot. In the Justin 1:1 5/21 Peter ratified this with Justin and used it to articulate the process going forward: raise asks should not be tenure-based ("we havent given Fred a raise in a year"); they should come with replacement-cost analysis, criticality justification, and a clear story. "In general I will say yes to that."
Hardware lab: paint the full picture and buy the whole complement upfront
When Nathan proposed buying one server per quarter to build out the engineering hardware lab, Peter pushed back: do it backwards. Define what we want the lab to be, then buy the full complement, not slice by quarter. Only chunk it if there is a real reason (cooling, ops bandwidth) — not for budget reasons. Tied to: NVIDIA H100/GB300/B200, AMD parity, and figuring out where to put it (Reno closet vs Texas DC).
Engineering owns docs content; Customer Engineering or Marketing owns customer-ready packaging
In Ryan 1:1, Peter split docs into two layers and assigned ownership cleanly: (1) the technical content, details, and accuracy IS engineering responsibility — same as QA. If Ryans org helps fine, but not held to it. (2) Making docs customer-ready/pretty is NOT engineerings responsibility — that lives with Ryan or Lindsay; they decide between themselves where it lives, Peter does not care which.
Ascender ownership moves to Nathan org with possible Zarina-led sister team
Peter decided Ascender does not stay parked between Jimmy and Larry as a half-supported side-project — it needs a real owner. Not adding a direct report to Peter; not adding to Justin who is at his limit. Lands in Nathans org. Possible structure: a sister group under Nathan (parallel to Justins org) for customer-facing delivery — would hold externally-facing Depot AND Ascender, led by Zarina, with one new engineer hired in for Ascender work. Decision contingent on Zarinas current Depot-Sodor commitment and the Wesley situation resolving.
Discretionary bounty offered for Yeshs vulnerability disclosure — case-by-case mode, no formal program
Yesh privately disclosed a vulnerability in ciq.com on 5/19. Peter forwarded to Greg/Bjorn asking if CIQ has paid bounties before. By 5/21 Peter emailed Steve+Bjorn endorsing reward: This is well done on his part, both technically and from a good-actor perspective. I would like us to reward here to encourage this behavior. Steve drafted a response: We do not currently operate a formal public bug bounty program, but would like to offer a discretionary reward for your efforts once validation is complete. Peter explicitly endorsed via DM (Yup!). Peter separately forwarded the disclosure to Justin to fix. Bjorn aligned on the wording earlier. Steve owns the response thread; Justin owns the fix; Bjorn owns sign-off; precedent-setting case for future disclosures.
Engineering owns all QA — Nathan accountable; tests required for Done; Ryans team builds tooling not rescue
Non-negotiable directive issued to Ryan: engineering is responsible for its own QA, Nathan is named accountable for quality, and a ticket is not Done until it has documented executed tests. Ryans role is re-shaped: build QA automation tooling (Gauntlet CLI, Outfitter, CIQCTL) that empowers engineers, NOT take over QA responsibility from engineering. Documentation also clarified: engineering provides all technical content; the customer-ready presentation layer is a Ryan-and-Lindsay conversation. Ryan to define a Definition-of-Done lifecycle visual for H2 to standardize across the org. Peter committed to email Nathan and Justin directly to reassert.
Jira confidence-as-contract doctrine codified across engineering directs
Codified explicitly in Justin 1:1 5/21 and same-day endorsed via Chris W DM: Jiras confidence number is a communication contract between engineering and GTM. Rules: (1) drop confidence immediately when a date is at risk (e.g., 80%→50%), (2) slide the date by a calculated intentional amount, (3) once confidence is high (95%), the date is a firm commit and must be hit even at extra cost, (4) treat ALL work as change-requests (no bug-vs-scope debate), (5) any change in understanding triggers immediate date/confidence updates. Engineering Order of Operations vs JPD prioritization formally separated: engineering owns operational/health priority (e.g., image build pipeline rework), JPD = product-value priority. Significant misalignment triggers a conversation. Same doctrine to be rolled out to Nathan and Max next.
Ascender consolidates under Nathan; opened customer-facing-delivery org reorg as a future possibility
The new Ascender application engineer hire (JD finalized 5/14, panel kickoff 5/20) will report to Nathan, not Justin. Reasoning: Nathans team has the necessary ecosystem breadth (OS + Depot + Ledger); Justins team is at capacity with narrower focus. Beyond the immediate staffing call, Peter opened a much larger structural question with Nathan: whether the engineering org should split along a new axis — a customer-facing-delivery group containing Ascender today, future external Depot, and other delivered-products — potentially led by Zarina. Wesleys uncertain future at CIQ surfaces as a blocker to firing that lever.
No bugs, only change requests — structural reframe for product/engineering interaction
Peter coached Brady (with Brian Dawson present) to eliminate the bug terminology in JPD/Jira entirely and replace it with change-request framing — borrowed from a CRM system Peter used at a smaller company earlier in his career, where the bug-tracking system had no bugs category type to eliminate the QA-vs-engineering-vs-product debate. Code works this way at this moment, I want to change it. Whether it's a bug or a new request — not material. Brady committed on the spot to roll out the change with Chris and Jamie and through Nathan's team. Brian aligned. Goal: remove the psychological/defensive trigger that makes prideful engineers slow to ship.
Engineering QBR format — collaborative discussion with three topics, not a presentation
Peter directed that the 5/22 Engineering QBR will be a collaborative working session rather than a formal presentation, organized around three questions: what is working well, what needs improvement, and how to streamline communication and increase work visibility. Chris Baek owns the shared prep doc that will collect bullet-point inputs from engineering leads ahead of the session.
CVE response strategy — three-pillar overhaul (process + tooling + strategic kernel review)
In Engineering Weekly Sync, Peter operationalized the 5/11 Leadership Roundtable vuln-handling commitment into three concrete pillars: (1) Chris Baek to restructure the embargo/CVE comms doc with Jamie, separating process from tooling/templates; (2) tooling strategy — Peter commits to email Greg requesting Claude Opus 4.7 whitelist for CIQ accounts AND to set up unbridled internal LLM models on Fuzzball for vuln investigations; (3) schedule strategic kernel philosophy review for early June, with Nathan and Justin to provide a list of downstream automation efforts to prioritize.
Open strategic review of RLC/RLK identity + upstream binding (Dirty Frag triggered)
Saturday 5/9 in #department-heads, in immediate response to Justin's Dirty Frag status table and Nathan's note about CIQ patches being shared with the RESF, Peter announced he wants the leadership team to take up a strategic question next week: what recurring vulnerabilities imply about CIQ's kernel posture, how tightly to bind to upstream, how to work with the RESF, and what it means going forward to be RLC and RLK. Aimed at framing input for the mid-to-late June LA in-person product-strategy session with Bjorn and Greg.
Reject open-ended LGU+ RHEL/OEL support commitments — best effort only
Nathan surfaced (via Justin) a CIQ <> LGU+ contract proposal requiring CIQ to provide workarounds and answer customer SR tickets for RHEL 6 (already EOL), RHEL 7/8/9, and OEL 6/7. Peter intervened in the same-day group DM with Bjorn, Art, and Ramesh to draw the line at best effort only — no commitments to deliver workarounds or answers. Asked Nathan if it is not yet in force so he can get in front of it before signing.
Prioritize build/test infrastructure to eliminate reactive engineering interrupts
After Dirty Frag CVE took Linux engineering offline for 24 hours, Peter committed to prioritize building robust build/test infrastructure as the proactive response. Told Brady/Brian this requires Product leadership to de-prioritize other work to make room. Surfaced publicly in #department-heads thread asking how to structure infra for the new normal of AI-assisted exploit cadence.
Eliminate one-off release processes — paved-paths Jira initiative Peter commits to prioritize
Mandated elimination of all one-off release processes. Justin to file a Jira ticket for the paved-paths initiative; Peter commits to prioritize it. Companion to the Jira-as-system-of-record mandate established the same meeting. Direct response to recent CVE post-mortem revealing most products run ad-hoc release flows.
Add Justin to Binarly meeting; debrief AFTER, not before
Peter added Justin Haynes to tomorrow Binarly meeting to ensure engineering representation. Explicit decision to debrief Justin AFTER the meeting rather than pre-coaching him beforehand.
Ryan to POC AI-driven Veeam image builder, gated on Justin-approved test suite
Ryan will POC an AI-driven image builder, starting with Veeam, that automates custom image builds, testing, and documentation. Hard gate: AI-generated images must pass a Justin-approved test suite to prevent hallucinations. Long-term vision: a 'Chipotle line' image configurator letting users compose custom, repeatable builds from validated components.
Tighten Jira-as-system-of-record into active enforcement — instruct teams to ignore Slack-only requests
All significant work must be in Jira to count as a commitment. Peter will instruct teams to actively ignore requests that exist only in Slack. This escalates the Apr 18 quality decision from policy ('ticket your work') to enforcement ('we will refuse to act on un-ticketed requests'). Justin owns the enforcement in Build/Test/Deployment, the function most contaminated by ad-hoc Slack asks.
Ship CIQ kernel patch with extra fix; contribute upstream; race to be first/best on CVE response
Linux kernel CVE response: CIQ shipping 10 fixes vs CentOS Stream's 9 (CIQ found and is fixing an extra issue related to the CVE). Extra commit submitted upstream to centos-stream and acknowledged for inclusion. CIQ pushing to be first EL distro to release, with primary goal of customer reassurance and secondary goal of public proof point that CIQ contributes to security and is large enough to serve big customers. Also pushing patches to RLC kernels as fallback in case RH doesn't move quickly.
Assign Justin (not Nathan) ownership of Binarly engineering relationship
When Brady asked via DM whether Nathan or Justin should own the Binarly engineering relationship from CIQ side, Peter answered More Justin.
Quality initiatives must be ticketed visible work, prioritized by Product
In the Brian/Brady weekly sync, Peter reinforced that quality cannot live as implicit expectations — Product must define and prioritize quality initiatives as explicit tickets that compete for resources against feature work. Engineering will only prioritize what is tracked. Companion frame: Exit Criteria are the product promise (Product owns, Engineering can challenge via debate); QA is delivery validation, split between Engineering (general releases) and Ryan's org (customer-specific fixes in mirrored environments). Brady to split test automation from build automation into a high-priority CI/CD ticket. Peter to verify with Justin that the build process at minimum runs a boot test.
Escalated Dieter/RASF urgency to Greg publicly — secured EOW commitment
Publicly escalated Dieters stress and lack of RESF authority in #distinguished-leaders (When are we actioning Dieter? Hes super stressed and feeling unsupported), forcing Greg to commit End of week is my target on finalizing the RASF.
Reframe Azure relationship — CIQ supports RLC, not all of RESF
Directed Justin to align with Kelly on Azure messaging, clarifying that CIQ supports its own RLC offering (not the entire RESF ecosystem). Protects Nathans team from unbounded support burden while preserving the January 2027 contract renewal opportunity.
Committed CVE categorization + kpatch estimates to Google by Monday
After Tissa agreed no one can answer Madhus blanket questions, committed CIQ to deliver a CVE-type classification table with kpatch coverage estimates by Monday. Reshaping an unanswerable request into a structured, defensible answer by category.
Delivered Jira Hygiene Mandate to Engineering
In Engineering Weekly Sync, mandated immediate improvement in Jira hygiene after presenting 3.5 months of data showing >50% of tickets updated after their due date (most slips 2-4 weeks). Prioritized communication over speed — proactive updates required, aggressive initial targets (20-30% confidence) acceptable. Directed Chris Baek to add a 'blocked reason' field to Jira for stakeholder visibility.
Delivered Jira Hygiene Mandate to Engineering
In Engineering Weekly Sync, mandated immediate improvement in Jira hygiene after presenting 3.5 months of data showing >50% of tickets updated after their due date (most slips 2-4 weeks). Prioritized communication over speed — proactive updates required, aggressive initial targets (20-30% confidence) acceptable. Directed Chris Baek to add a 'blocked reason' field to Jira for stakeholder visibility.
Committed to engineering date hygiene confrontation with directs
Peter publicly committed in Leadership Roundtable to holding a tough conversation with his directs about deliverable date hygiene. Requested date-slip magnitude data from Chris Baek (days vs weeks) to focus on significant delays rather than minor variance.
Proactive retention check-in with Alex after Ian's departure
Peter initiated a skip-level check-in with Alex de Wergifosse to assess retention risk after Ian's unexpected departure from the Fuzzball team. Committed to recurring check-ins every 3-4 months and established a mutual transparency pact — Peter will warn Alex of any job security issues, Alex will discuss external offers before accepting.
RESF JIRA Date Reset for Realistic Expectations
Peter directed Nathan and Justin to adjust April/May JIRA items with low confidence due to RESF resource drain. Move them out now to give marketing a high-confidence scope for 4-6 weeks.
Michael Young Termination Communication Approach
Peter set communication boundaries for Michael Young's termination: don't tell RESF people WHY, only 'we decided to part ways.' Advised Greg not to write specifics down. Declined to reply to Michael directly.
Sensitive Decision
Sensitive Decision
RESF Monday Cutover — Finalized 3 PM PT Execution Plan
Finalized the RESF infrastructure cutover plan for Monday March 16 at 3 PM PT, including DNS NS record flip, AWS VPC firewalling, account disabling (Lewis, Neal), and security audit — accepting up to 24 hours of DNS-related downtime.
TPS Report Visibility — Expand Justin's Reporting Scope
Directed Justin to update TPS reports to reflect current reality and add missing workstreams (Portal, Depot, Releases). Goal is independent progress tracking without needing Justin's verbal context.
Zorina LOA — Grant Extended PTO to Retain
Decided to grant Zorina 5 weeks of PTO (May 4–June 5) if her FMLA application is denied. FMLA application goes first for compliance, but the fallback is already decided. Remote work from Bulgaria for 2 weeks is also approved pending IT security check. Delegated execution details to Justin and Mariah.
RESF Operational Security — Compartmentalize Until Board Action
Directed that Brian must not be told anything until after the RESF board notification. Emphasized extreme caution about leaks to Lewis. Approved Joseph being read into the initiative but warned about leak risk. Sequenced information flow: board action first, then notifications, then credential recovery.
Sensitive Decision
Westley Transition — 70% Fuzzball, Maintain Depot Support
Westley will start transitioning to Fuzzball at 70% allocation while maintaining depot support work for Justin team until fit is confirmed.
Damen — Action-First Title Policy
Set clear position on Damen's request for an AI ownership title: titles are granted AFTER impact is proven, not as a motivator to drive it. Directed that Damen should escalate issues with other teams publicly rather than absorbing work and complaining privately. Asked Justin to get Damen to define specifically what 'owning AI' means and what title he wants.
Michael — Create-a-Hole Performance Framework
Coached Justin that the goal with Michael's performance management is to create a 'hole' for a high performer (like Ben), NOT to raise Michael to 'barely acceptable.' Framed 'barely acceptable' as worse than low performance — a barely-acceptable employee is hard to remove, creating permanent drag. Told Justin to leverage startup advantage (no HR handcuffs) to set higher bar, and shift mindset from 'fair for Michael' to 'fair for the team.'
Team Building Mandate — 6-Month Priority Over Features
Directed all engineering managers to prioritize team building over feature delivery for the next six months. Includes permission to swap out low performers, with Peter providing air cover for the risks involved.
Committed to RESF day-of execution planning meeting next week
Committed in #internal-resf-escalation to organizing a meeting next week to build an execution plan for the RESF day-of lockdown. Directed Sarah to invite Nathan, Max, Justin, and Dieter. Bjorn is finishing messaging drafts this weekend, so technical execution planning must be ready to match the communication track.
Coached Justin on Michael performance management with net-good framework
In Justin 1:1, directed Justin to deliver direct performance feedback to Michael next week with Andrew-level success metrics. Framed PIP as high-bar exercise to confirm exit decision. Differentiated Michael (low performer, manage out) from Brady (high potential, wrong role, coach/move). Used weeding the garden and Expedition 33 metaphors to help Justin reconcile empathy with accountability.
Rocky project contingency war room - infrastructure security planning
Committed to scheduling a war room meeting to create a detailed, step-by-step contingency plan for securing Rocky infrastructure (AWS, FreeIPA) against potential hostile action by former members. Plan assumes an outage will be necessary to revoke access. Technical cutover to be planned before legal letters are sent.
Risk tolerance recalibration - push and be wrong for low-risk releases
Established new release philosophy: 'push and be wrong' for low-risk changes, prioritizing speed over perfection. Directed Nathan to ship two approved CVE fixes for unused packages immediately as a precedent-setting test case, bypassing the usual review process.
Release artifact ownership assignment - Nathan RPMs, Justin images
Assigned clear ownership of release artifacts: Nathan is the final approver for RPMs, Justin for images. Each owner defines their own validation process and has autonomy to improve it without seeking permission. Creates a 'throat to choke' accountability model for release quality.
Personnel action plan from effort/impact matrix review
Conducted comprehensive effort vs. impact performance review of ~20 engineers across kernel and platform teams, resulting in specific personnel actions: underperformers on short improvement timelines or face replacement, one engineer to be replaced with a high-impact hire, one engineer requires direct performance conversation about ownership and visibility, one to be reassigned to simple packaging tasks.
Mandated Engineering double delivery pace in 6 months
Directed Justin Haynes and Nathan Blackham to double their teams' delivery pace within 6 months. Method: hire new talent to build a team capable of that pace; some current members may not be a fit. In-person planning session in San Jose on Feb 25 with Justin, Nathan, Max, Peter.
Sensitive Decision
Sensitive Decision
Directed Nathan to surface eng-product communication gaps
After Department Heads meeting, spent 30 minutes coaching Nathan 1:1. Praised his handling of the meeting despite frustration. Directed Nathan and Justin to be proactively transparent with product, and specifically to surface instances where engineering communicates clearly but product claims ignorance.
Mandated accelerated cadence with coordination accountability
In Department Heads meeting, mandated announcements every 2-4 weeks as non-negotiable. Drew accountability line: engineering protected for speed mistakes but NOT for coordination failures (status updates, product priorities, public channel decisions). Framed as make-or-break period driven by $30B revenue goal and Middle East partnership success.
Accepted priority churn during RLC Pro/Plus pivot
Explicitly approved Justin's explanation that priorities and confidence levels will shift as his team pivots to Pro/Plus work. Told Justin 'And that churn is fine.'
Leveraged TPS report visibility to drive accountability with Justin
Proactively messaged Justin that the Release All Things section of the TPS report looks bad, with a 2.5-hour deadline before C-Suite Sync presentation. Gave Justin a window to update Jira tickets to reflect reality.
Mobilized team for Saudi meeting prep and escalated NVIDIA DOCA blocker
Peter personally intervened to prepare team for critical Saudi Arabia partner meeting on RLC-AI. Posted in #product-rlc-ai asking about CUDA/DOCA availability, discovered NVIDIA written approval for DOCA OFED still pending. Emailed Scott Hara (NVIDIA) directly to advance the approval. Tagged Nathan, Justin, Jeff Uphoff, and Damen Knight demanding they answer Max's detailed technical questions within 24 hours. Set hard deadline: '24 hours from now.' Bjorn committed to calling Scott to reaffirm DOCA modification rights.
Demanded war-room or date ranges for RLC Pro release dates
Marketing (Lindsay Aamodt) published release dates in #department-heads: Feb 19 RLC Pro, Feb 26 RLC Pro AI, Mar 5 RLC AMD. Justin Haynes responded that dates were 'written in light pencil.' Peter directed Justin: if dates aren't confident, either commit with a war-room to hit them, or provide GTM with ranges now so they can plan. Justin acknowledged and scheduled time with leads.
Sensitive Decision
Enforced Product-owns-prioritization process with Greg
Pushed back directly on Greg when he tried to route engineering work outside the established prioritization process. Insisted Product owns the priority list and work requests must flow through the proper channel. Simultaneously reminded Chris Baek that his team owns signoff authority and should use it rather than escalating through Greg.
AMD RLC Plus Strategy: Speed-to-Market with Minimal Scope
Decided to prioritize speed-to-market for the RLC Plus AMD co-marketing launch. The initial build will use upstream AMD packages (pre-built ROCm), the kernel driver (not upstream DKMS), and enable EPEL. Deferring the more robust in-house rebuild until market traction is proven. Justin Haynes to draft proposal and decision matrix.
Rocky Security Updates Urgency - Competitive Gap
Flagged to Max, Justin, and Nathan that Rocky security update tagging is a critical competitive gap needing urgent attention. Shared community post recommending Alma over Rocky because Alma correctly tags security updates and has timelier updates.
New Engineering Mandate - 2x Velocity in 6 Months
Set new mandate for Justin and Nathan: top priority is building a team that can deliver twice as fast in six months. This is a shift from the previous coaching model to a performance-driven one - setting ambitious targets, holding people accountable, and replacing underperformers.
WBR restructuring to outcome-based commitments
Restructure the Weekly Business Review (WBR) to be outcome-based. At the end of the meeting, everyone has publicly committed to what they will deliver by Friday. The meeting should create social accountability through public commitment.
Focus CVE automation on top 5 priority packages first
Stack-rank the CVE priority package list and start automation with just the top 5 packages. Drive open CVE count for those 5 as close to zero as possible before expanding scope. Report closed-by-automation separately from will-not-do.
LTS roll-forward policy - small stable core, roll everything else
Define a small core set of packages (~5) that stay stable in LTS releases (kernel, glibc, gcc, and a few others). Everything else can be rolled forward aggressively. Customer-specific additions can be negotiated as needed.
CVE automation architecture - simple state machine, 1 CVE per commit
CVE automation should be built as a simple state machine with clear exit criteria at each step. Each commit addresses exactly one CVE. The orchestrator should be stupid-simple - just moving between states. Steps: Research -> Rebase -> Build -> Test -> MR -> Final Build -> Integration Test -> Promote to Beta -> Integration Test -> Production.
Redefine wins to only celebrate step-function improvements
Reset the definition of wins across engineering teams to only celebrate step-function improvements and exceptional contributions, not completing expected work. Use recognition strategically as a management lever to train teams toward higher performance.
Leadership meeting cadence - need-based, not scheduled
Leadership meetings will happen every 4-6 weeks based on need, not a fixed schedule. Buy refundable tickets ahead of time and cancel if there is not a full agenda worth discussing.
Approved transfer of Depot operations from Justin to Steve team
Approved transferring Depot operations from Justin team to Steve team as a test of Steve team SRE capabilities. Justin team will define the architecture for moving Depot to object storage, then hand off execution to Steve team who will own provisioning, infrastructure, and monitoring.
Empowered Justin to own RLC 9.7/9.6 LTS ship criteria
Directed Justin to define and own the ship criteria for RLC 9.7 and 9.6 LTS releases, bypassing Product inability to provide a clear definition of done. Justin will draft a 5-line definition and present it to Brady. Peter will provide air cover for any product fallout.
Committed to ensuring Greg technical direction reaches Justin
Committed to redirecting Justin to follow Greg architectural guidance on object storage/depot, and to be the conduit ensuring Greg technical direction reaches engineering clearly. Greg flagged that depot work was not in line with past directives.
Transfer Depot operations from Justin team to Steve team
Depot operations will transfer from Justin team to Steve team. Justin team will define the architecture for moving Depot to object storage, then hand off execution to Steve team for provisioning, infrastructure, and monitoring.
Empower Justin to own RLC 9.7/9.6 LTS ship criteria
Justin will define and own the ship criteria for RLC 9.7 and 9.6 LTS releases. He will create a 5-point launch checklist and share it with Brady for approval, bypassing Product inability to provide a clear definition of done.
Redirected Brady to use prioritization tools instead of pushing hard
Directed Brady Dibble to use the order of operations (prioritization list) as his tool for influencing engineering priorities, rather than pushing uncomfortably hard on individual teams. Emphasized that the prioritization list is his lever to move all of engineering, and if the order of operations is wrong, the fix is to change it formally with Peter, Bjorn, and Justin.
Mandate big leaps risk approach for H1
Directed Justin to take big leaps and calculated risks to meet H1 goals, especially with AI. Speed and learning prioritized over avoiding potential issues. Example: a vibe-coded Portal in one day is preferable to a 1.5-month architected build - worst case is a day lost, best case is massive time-to-market advantage.
Sensitive Decision
Empower Damon to execute on RLC-AI without being blocked by Jeff
Directed Justin to tell Damon that he should press ahead with RLC-AI/Basil work and not let himself be blocked by Jeff, who claims ownership but fails to deliver. Damon should inform Jeff what he is doing rather than wait for permission.
Depot Management Transfer to SRE
Decided to transfer Depot management (monitoring, maintenance) from Justin org to Steve SRE team. Committed to connecting Steve and Justin to define the work distribution.
Commit to increased visibility with engineering org
In response to employee feedback about low visibility creating a trust gap and fear-based culture perception, committed to: bi-weekly positive Slack updates, more 1-on-1s with key individuals, frequent positive feedback in public channels, weekly summary of focus areas, and an SF meeting with Nathan/Justin/Max.
Work intake must flow through managers, not directly to engineers
Established new process where small customer requests go to Engineering Managers (Justin, Chris W.) for approval. EMs will attend bi-weekly CECA board review to ensure they are in the loop on incoming work.
Justin Coaching - Ambiguity Tolerance and Explicit Pushback
Coached Justin on the Depot/Portal bounty disconnect. Addressed two issues: (1) Justin needs to get comfortable moving through ambiguity and letting his team explore before designs are fully baked - unlearning 10 years of Amazon training. (2) When Peter pushes for something, Justin needs to either do it or explicitly debate/push back - not quietly not execute.
Max Spevack Role Expansion - Formalized Authority
Announced to engineering that Max takes a dedicated leadership role spanning Linux Engineering and RAT, reporting directly to Peter. Max acts with Peters authority in meetings, serves as quality gate for major decisions, shapes engineering culture, and is an escalation point outside the management chain.
ICP Consolidation - RLCH and RLCAI into Fuzzball
Consolidated RLCH (Rocky Linux Confidential Hardened) and RLCAI ICPs with Fuzzball ICPs to simplify GTM. RLCH targets regulated industries, government, power distribution. RLCAI targets AI-inferencing and compute-heavy industries. Rocky Pro kept separate for mid-market RHEL/SUSE/Oracle replacement motion.
H1 Planning Framework - 3-Lane Model
Introduced a new 3-lane planning model to address GTM and Engineering misalignment. Top Lane (GTM): marketing campaigns, messaging. Middle Lane (Value Drivers): the why - market state change, ICP, business significance. Bottom Lane (Engineering): deliverables driven by Value Drivers.
Google Scope Change - Hold the Line on Commercial Terms
Google is pushing scope changes that bundle 8 versions into a 5-version contract, omit EOL dates, and include undefined dev streams. This creates scope creep risk and jeopardizes the Extended LTS revenue stream (~$300k/year per product). Decision to personally attend the Monday meeting with Tissa (with Max) to hold the line. Greg will NOT attend to preserve escalation path.
Verify Justin Offered Bounty Work Broadly
Investigating whether Justin followed direction to offer bounty work opportunities to everyone. Greg believes it was not offered to Westley. Peter committed to verify this week.
Build Culture That Moves With Ambiguity
Committed to teaching the org to start moving with imperfect information rather than over-designing before committing. Will provide cover from Bjorn holding teams accountable for early SWAG estimates, enabling faster iteration and learning.
Bounty Program Design: Open Incentives Over Prescribed Work
Established that bounties at CIQ should be open to all engineers, not targeted at specific individuals. Rejected Bjorn approach of incentivizing Jesus and Alex specifically to work over holidays on Portal. Bounties should be available for anyone to claim if they want to accelerate delivery.
Bounty Program Design Principles
Outlined design principles for bounty program: transparency in logging, substantial compensation for well-scoped work, quick delivery incentives.
H1 Planning Strategy - Aggressive Goals with Staggered Milestones
Articulated H1 strategy: shift from hope to concrete plan with aggressive audacious goals. Achieve goals differently not just faster. Staggered milestones every 4-6 weeks for course correction. Missed milestones trigger retrospectives for process or personnel changes. Clear prioritization at Reno eliminating everything is P0 problem.
Andrew Jorgensen Hiring Approved
Approved hiring Andrew Jorgensen for an IC role reporting to Nathan Blackham. Offered flexibility on level - he can come in at senior or less senior position based on his comfort.
Product-Engineering Quick Estimation Process
Articulated position on providing quick, low-confidence estimates for Product prioritization. Engineering should provide 20% confidence SWAGs on demand so Product can do early prioritization - these are not commitments engineering can be held to. Distinguished between committing to work without a design (bad) vs providing a quick guess marked as such (good).
RESF Infrastructure Independence - Technical Execution
Directed Nathan to mirror all RESF repositories and initiated build environment duplication. Created #internal-resf-escalation channel with strict confidentiality rules. Keeping technical circle small (Nathan, Max, Justin, Dieter) while moving quickly.
RLC 9.7 Launch Path Decision
Participated in RLC 9.7 Launch planning meeting to decide path forward on release and rework priorities.
Championing AI Butler Internal Adoption
Hosted and recorded the AI Dashboard/Butler setup session to drive internal adoption of Claude-based personal productivity tools across CIQ. Shared personal use case of creating meeting prep notes from Slack/email/docs.
Related Patterns (24)
Proactive Talent Pipeline Investment
Invest in building leadership bench and talent relationships before there is an urgent need. Use proven relationships from past experience to create optionality.
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.
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.
Accountability Follow-Through
When you issue a warning or mandate with stated consequences, you follow through. Warnings are not threats - they are commitments. The credibility of future accountability depends on following through now.
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.
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.
Three-Lever Talent Management
When pursuing a velocity or performance mandate, simultaneously operate on all three talent levers — upgrade (hire better), retain (protect key people), and exit (remove blockers) — rather than sequentially. This creates compounding momentum: exits free capacity for upgrades, retention preserves institutional knowledge during transitions, and upgrades raise the performance bar that justifies further exits.
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.
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.
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.
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.
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.
Conscious Tech Debt for Execution Speed
When facing time pressure, explicitly acknowledge and accept technical debt rather than blocking progress. The key is making the trade-off consciously and visibly so it can be addressed later.