Operational Decisions
14+ recent decisions
Collapse nineteen engineering titles into four groups - and put senior principal back only if a manager makes the morale case
Sep 7, 2026 · operational · low74% confidence
In the Nathan 1:1 Peter walked the leveling sheet and set the target explicitly: nineteen distinct titles across sixty people becomes four titling groups. He opened by declining the framing Nathan offered - this is not about correcting overinflated titles, it is about simplifying titling - and said his religion is the simplification, not any specific person. He asked Nathan to validate the mappings for his own people and to build planned promotions into the exercise rather than run them separately. On the senior principal tier, which the collapse removes, he did not decide unilaterally: he asked Nathan to probe Andrew Jorgensen and Jamie Maple on how much they actually care, and said if Nathan argues that senior principals are needed to manage morale on his team, Peter can get his head around engineer plus senior engineer and principal plus senior principal. He also told Wallace the same day that the leveling has cleared Greg and Mariah and that he will sit down per-org to make a plan, committing to Wallace next week after slipping the intent to do it this week.
People: Nathan Blackham, Steve Wallace
Deliver the AI-spend message myself at an engineering all-hands instead of letting the AI committee write a policy
Aug 28, 2026 · operational · medium77% confidence
In the 2026-08-27 Ryan Smith 1:1, Ryan argued that the next AI committee meeting should produce a company-wide best practice on AI spend - consensus around spend, do not use Fable for everything, be self-aware of usage. Peter declined the policy framing but conceded the underlying point: the conversation has to happen and has to be delivered directly to engineering rather than routed through a committee or left to individual managers. He committed to an engineering all-hands the following week and flagged it verbally for capture in the moment. He scoped it explicitly to engineering, excluding Ryan own organization.
People: Ryan Smith, Chris Wolford, Steve Wallace, Steve Moody
Diagnose every AI overage case individually and apply the remedy that case calls for - without squashing AI usage
Aug 28, 2026 · operational · medium81% confidence
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.
People: Justin Haynes, Chris Wolford, Ryan Smith, Nathan Blackham, Steve Wallace
Shut down department-heads as an intake path for engineering work - I raised it to product, they will either ask for it or they will not
Aug 28, 2026 · operational · medium89% confidence
In a #department-heads thread about who owns and maintains the C3 RPMs and about hardware certification playbooks, Ryan Smith offered to tweak Gauntlet to run certification playbooks and asked for hardware to be sent to him. Peter cut it off directly: this channel is not how work gets in front of engineering. He restated the path he had actually used - he asked who maintains it, got back currently nobody, and took the follow-up question of whether it should be publicly visible to product, where Brady Dibble owns it. If product asks for it, it becomes a project and gets the right people and the right hardware support.
People: Ryan Smith, Nathan Blackham, Brady Dibble, Dave Dickerson, Greg Kurtzer
Govern AI spend by notification and trust rather than a cap - alert at a thousand over, and if the person knows what they are doing get out of their way
Aug 24, 2026 · operational · medium87% confidence
Peter met with Steve Wallace and Scott Moody on AI and cloud costs Aug 24 at 11am, then recounted the outcome to Ryan and Bjorn an hour later. What he asked for is visibility plus a Slack notification when someone goes a thousand dollars over their limit, followed by a second one. The rule attached to the notification is not a stop - it is: if you do not know you are doing that, stop what you are doing and figure it out, and if you do know what you are doing and it is right and you are a smart person and it is right, I do not want to get in your way. He explicitly declined a single best-practice standard, differentiating by workload: Sultan costs are fine because he is dealing with a CVE swarm and the right behaviour is solve it as fast as you possibly can, whereas Jason Rodriguez spinning up 13 Opus or Fable agents makes no sense - but Peter attributed that to missing visibility rather than to judgment. He named his own next step as a person-by-person conversation with each leader over what he can now see. Separately on cloud costs he closed the question rather than opening it: the split is 100 percent Fuzzball, and he told Bjorn and Ryan they just need to get used to that being the new normal, while committing to sit with Wolford to slice it up.
People: Steve Wallace, Scott Moody, Ryan Smith, Bjorn Hovland, Chris Wolford
Extend abort-the-loop authority from the hiring manager down to every individual interviewer - anybody can pull the ripcord alone, without a debrief or consensus
Aug 21, 2026 · operational · medium70% confidence
At the close of the Friday roundtable the hiring manager mentioned that he already pulls candidates before they reach a debrief, so the panel will not see a roundtable for everyone they interview. Peter extended that authority downward rather than leaving it with the manager. He said he is a huge believer, we are a small team, everybody on this call is a super smart individual, and he is really comfortable with anybody just pulling the ripcord on an interview and saying this one is not moving on. He added that in past environments he was fine with someone standing up and walking a candidate out mid-loop on the grounds of not wasting anybody else time. He explicitly declined to impose it - the hiring manager might not be comfortable with it and Peter said he would leave that up to him. The hiring manager then agreed, saying at this stage in the game he was happy to do that. The exchange happened immediately after a debrief in which the panel had spent roughly twenty minutes on a candidate they all ended up rejecting, and after two of them had traded stories about aborted loops at a previous employer.
People: Nathan Blackham, Andrew Jorgensen, Jonathan Dieter
Move the metrics conversation with Nathan off the tooling and onto the why - which metrics, which were discarded, and how the team is told the reason
Aug 21, 2026 · operational · medium89% confidence
Peter closed the Nathan 1:1 by resetting what he wants from the metrics workstream. He stood it on the foundation that if you do not measure it, it does not change. He then said Max document was a fine first cut and he does not know whether Nathan wants to use it, but that is not the conversation - it is not about what Butler shows. Butler is just building a tool and it will not show me the whys, and it is the whys I want to talk about. He named the specific agenda for the next 1:1: why this metric, why this metric, which metrics you have discarded, and how you are communicating them to your team so they understand why you are tracking certain things. He connected it to his standing complaint that he is not seeing the change in pace he wants and that pounding that drum gets him nowhere - he wants to engage in the concrete bits of what Nathan is holding people to and why, acknowledging that Nathan knows how his own org will respond to a given metric better than Peter does. Nathan took it further himself, saying he should start adding the why to the dashboard, and Peter agreed with a second reason: it keeps people from making an incorrect assumption about why you care and gaming it through misinterpretation rather than intent.
People: Nathan Blackham, Steve Wallace, Max Spevack
Restate every RESF request as a request to CIQ rather than to Nathan - publish the secure-boot ask to all of Linux Engineering so someone else can raise a hand
Aug 21, 2026 · operational · medium88% confidence
Nathan reported that Dieter had asked him explicitly to help with a secure boot POC, and that he would demo it to Sharif, Scott and Dieter on Monday, building it on CIQ hardware because CIQ needs it too. Peter approved the substance and re-cut the framing: let me tweak things ever so slightly to the RESF has asked CIQ to do this, not Nathan. It may be Nathan who is doing it, but the ask should be published in Slack to all of Linux Engineering - the RESF has asked for help with secure boot, I know secure boot, so I am sitting down with them Monday, and if anybody else is interested in understanding how this works or how they can plug into that world, here is the opening. Peter said chances are it is nobody and everyone just pats Nathan on the back, but he wants to buy the chance that one person wakes up and goes that is interesting. He tied it to the wider problem: the RESF needs to stop being five or six people who think it is their clubhouse, and Nathan should be willing to say this contributor should get a structure and a title inside the RESF. In the Steve Wallace 1:1 the same day he committed to pressing Dieter on the same point next week - nobody at the RESF is asking CIQ for things directly, and both Nathan and Steve orgs have resources available.
People: Nathan Blackham, Steve Wallace, Jonathan Dieter, Gregory Kurtzer
Approve the NVIDIA-supported Fuzzball hackathon at SC - with a Wolford engineer on site a day early and a month of hardware notice from NVIDIA
Aug 19, 2026 · operational · medium80% confidence
In the L/P Quick Sync on 2026-08-18, Lindsay Aamodt brought the NVIDIA hackathon she has been building - in person in Chicago, Friday November 13 kickoff, build Saturday and Sunday, judging Monday, winner presented in the booth Tuesday as SC opens - and asked Peter to name the risks that would make it a flop in person. Peter approved it and attached conditions: someone who works for Chris Wolford goes on site a day ahead to stand the clusters up, explicitly not Lindsay; and NVIDIA must confirm exactly what hardware they are providing a month in advance so the networking is handled beforehand. He committed himself as a judge alongside Bjorn, Greg and Scott, and Wolford as mentor staying through Saturday.
People: Lindsay Aamodt, Chris Wolford, Scott Shinn, Bjorn Hovland, Greg Kurtzer
The five-week leader presentations are baseline once, then deltas forever - show me what you changed to move the number, not the same dashboard
Aug 19, 2026 · operational · medium88% confidence
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.
People: Nathan Blackham, Steve Wallace, Chris Wolford, Ryan Smith, Justin Haynes, Max Spevack
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
Aug 13, 2026 · operational · medium87% confidence
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.
People: Ryan Smith, Justin Haynes, Nathan Blackham, Chris Wolford, Steve Wallace
Override your own teams stated intent to delete the RL 8.6 source tree, and apologize to Google directly rather than defend the position
Aug 11, 2026 · operational · high88% confidence
Tissa Senevirathne emailed Kelly Hall on Jul 30 saying CIQ had informed Google it wanted to delete the RL 8.6 OS and kernel source tree, and asked that it be preserved for contractual traceability and auditability. Peter replied to Tissa the next morning without consulting his team first: I do not know why my team informed you they wanted to delete that tree. I apologize. There is little cost associated with us keeping it live. I hope it was presented as a discussion, not as CIQ is doing this. I will dig in with them to understand what was motivating that, but your request is more than reasonable. In parallel he told Nathan in DM: we cannot shut this down right now, it does not cost us to leave it up except for a few dollars, and pressed for the reason - but why would we need to delete it? I do not want to do anything at all to rock the boat with them right now unless we need to. He named the underlying stake: I want to make sure we have the actual contracts completely signed in blood, and pushed back on the suspected motive - I do not want to do anything that they are nervous about right now, especially if the reason is that its existence makes our metrics look bad.
People: Tissa Senevirathne, Nathan Blackham, Kelly Hall
Purchase approvals below a managers own threshold must never route to the CTO - told Nathan to expense it anyway and took the fight to Finance rather than the person executing the policy
Jul 30, 2026 · operational · medium95% confidence
Nathan bought a roughly 100 dollar remote KVM for the NVIDIA DGX Spark so other engineers could access it, after asking Peter first and being told yes. Erin Fong flagged that company-funded equipment must be tracked through an IT ticket before purchase; Nathan said it was not worth the hassle and would pay out of pocket. Peter intervened in three places. In DM to Nathan: No. Tell them No and that the CTO said it was fine. I do not want stuff like this to continue - and, repeatedly, But I already just said you can just expense these things. In the group DM he took the diplomatic line publicly - Nathan asked me prior to purchasing if it was ok. I said yes. Did not know this policy existed. If a ticket can be created rapidly in a way that does not burden Nathan, great - and Stephen Moody opened IT-6605 to document the approval. Then he located the real owner: he asked Steve Wallace whether the policy came from him (it did not, it came from Finance via Erin), and stated the fight he intends to pick: you have a threshold you can approve up to, Nathan has a threshold, I have a threshold. If it is below your threshold and you approved it, I do not want it routing to me. I do not want to know about it. I do not want to think about it. I never want to see it. Separately he coached Nathan on target selection: ask yourself whether you are solving this for yourself, for CIQ, or trying to make Erin recognize the policy is stupid - Erin works for us a couple hours a week and her job is to click buttons on the policy, she does not own it, so there is nothing you can say that will change it.
People: Nathan Blackham, Erin Fong, Stephen Moody, Steve Wallace
I dont know is the right answer - Support does not guess how Oracle does it, and LG questions are an Engineering/Product call not a Support call
Jul 29, 2026 · operational · high92% confidence
With Bjorn about to dig into the LG U+ escalation and likely to reach out directly to support engineers, Peter set an information-hygiene rule and had Ryan Smith push it to his team. The rule has three parts: if the team does not know how Oracle is doing it, the answer is we do not know - not they must be doing blah blah blah; answer his questions truthfully but do not lead the witness; and the LG question itself is an Engineering and Product call, not Support. Ryan confirmed his team had acked it and named Amr as the likely contact point, and Peter said he was doing the same thing with Howard. Peter closed with answer his questions. No guessing.
People: Ryan Smith, Bjorn Hovland, Howard, Amr Mumtaz