Operational Decisions
50+ recent decisions
Rule the Toyota kernel patch a feature not a bug; no automatic queue jump, escalate through normal priority
Jul 10, 2026 · operational · medium78% confidence
Nathan flagged a Toyota/Yoshi request (relayed via Art/sales) framed as a bug fix. Peter ruled it is a feature, not a bug, so it does not automatically jump the engineering queue on the bug argument. Support may still be offered, but the bug framing is off the table. If the business wants it prioritized it must go through normal escalation and trade-off (Peter + Bjorn), not a backdoor via mislabeling severity. Reinforced later the same day in the Ryan 1:1 (Peter rebuked Art for taking the bug-vs-feature fight to engineering).
People: Nathan Blackham, Art Tyde, Bjorn Hovland
Willing to pull C3 into engineering, gated on Product confirming it is a priority
Jul 9, 2026 · operational · medium61% confidence
In his 1:1 with Art Tyde, Peter said he is willing to pull C3 into his engineering org, conditional on Product (Bjorn) actually confirming it is a priority. C3 ownership is currently ambiguous (Peter was told Greg owns it, which he called a terrible answer, and nobody under Peter owns it), it is degraded (reported ~50 percent down, Fathom-approximate), and it is blocking a Huawei evaluation. Peter made a note to figure out who is responsible for keeping it up and how to fix that.
People: Peter Nelson, Bjorn Hovland, Greg Kurtzer, Arthur Tyde
Restructure the Tuesday staff meeting to org-by-org TPS ownership and un-fork the TPS report to one shared source
Jul 7, 2026 · operational · medium69% confidence
Peter is firmly changing how he runs his Tuesday staff meeting: instead of Peter walking the team through the TPS report, each org owner presents their own section and owns that part of the meeting. He also committed to un-fork his drifted TPS report back to a single shared report, visible to everyone three days ahead.
People: Peter Nelson, Max Spevack
Mandate Snyk vulnerability-remediation SLA compliance across all engineering teams
Jun 30, 2026 · operational · medium52% confidence
In his 1:1 with Steve Wallace, Peter committed to mandate Snyk vulnerability-remediation SLA compliance across all engineering teams, not just Steves. Snyk SLAs are being breached, putting the fall ISO 27001 audit (broader scope than SOC 2) at risk, and the breaches span other teams repos including the PIC team and Ryans customer-service app. Steve will draft a high-level doc of the required compliance behavior, and Peter will push it out across engineering with CTO authority behind it. The mandate is decided; issuance is pending Steves doc.
People: Steve Wallace
Engineering owns defining the ask, success criteria, and documentation; CS responds to specific asks
Jun 30, 2026 · operational · medium63% confidence
In a DM with Nathan about friction with Ryan, Peter drew the Engineering-CS interface boundary: core engineering owns defining the ask and the success criteria and owns ensuring documentation exists; it is not Customer Support job to dig out engineering details. CS cannot follow everything and is expected to respond to specific, well-defined asks. AI can do much of the doing, but engineering still owns defining the ask and what success looks like.
People: Nathan Blackham, Ryan Smith
TPM charter + one-owner-per-release accountability mandate (problem/solution/owner grid)
Jun 30, 2026 · operational · high66% confidence
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.
People: Chris Baek, Nathan Blackham, Justin Haynes
Repair the mis-framed Engineering All-Hands - hold a PIC/Fuzzball follow-up and proactively notify the slighted PIC team
Jun 18, 2026 · operational · low67% confidence
After Jonathan Anderson and others read the recent State of Linux session as the Engineering All-Hands - leaving the PIC team feeling ignored - Peter diagnosed it as a framing/naming failure (Linux-only, Wolford not on it, no Fuzzball content) and directed the fix: a PIC/Fuzzball-focused follow-up session in the next few weeks, Baek to own the Fuzzball angle, and the PIC team to be told now that it is coming because yesterday was bad for them - they felt completely ignored.
People: Chris Wolford, Chris Baek, Sarah Almaraz, Jonathan Anderson
Mandate 24-hour Sev-1 outage auto-escalation to estaff and AE
Jun 17, 2026 · operational · medium76% confidence
After the Fyr Fuzzball outage ran roughly 5 days without surfacing to leadership and the customer had to ping Horn directly to force escalation, Peter directed that any Sev-1 or customer outage open past 24 hours must automatically notify estaff and the account AE, built into tooling so it does not depend on a human judgment call. Ryan operationalized it as Zendesk automation plus CCing named-account AEs at ticket creation.
People: Peter Nelson, Ryan Smith, Bjorn Hovland, Chris Wolford, Jonathon Anderson
Fix performance-review confirm-receipt acknowledgment — hand-deliver packets now, push HR for global wording change
Jun 16, 2026 · operational · medium60% confidence
When Andrew Jorgensen objected that Ripplings mid-year review flow forces employees to click confirm receipt before they actually have the packet, Peter sided with him. In his lane he directed an interim fix: managers download and hand-deliver packets directly so employees physically have them before acknowledging (told Nathan to send Andrew his packet; floated telling all his managers to email packets to everyone this round). As advocacy in HRs lane, he asked Mariah to change the button globally to access your packet and remove the receipt-confirmation sentence. Final wording decision deferred to the 6/16 C-Suite.
People: Peter Nelson, Andrew Jorgensen, Mariah Rippee, Nathan Blackham
Re-institute and enforce monthly performance conversations across engineering managers
Jun 12, 2026 · operational · medium78% confidence
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.
People: Justin Haynes, Nathan Blackham
Value Drivers Board becomes source of truth for engineering dates and confidence; JPD dates become computed
Jun 4, 2026 · operational · high88% confidence
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.
People: Nathan Blackham, Justin Haynes, Chris Baek
Take on Value Drivers Board restructure as the next coordination lever after JPD doctrine
Jun 1, 2026 · operational · medium69% confidence
In the 6/01 Leadership Roundtable, Peter committed to bring a formal proposal to restructure the Value Drivers Board, explicitly sequenced as the next move now that the product-priorities board (the JPD-doctrine work, closed 5/29) is aligned where he wanted it. Took the Fathom action item to draft the proposal and share with Chris Baek and the group within a couple of days. Triggered by Lindsay surfacing marketing/product misalignment (premature RLC+AMD announcement before AMD validation; Fuzzball multicloud date churn May 28 to June 4).
People: Peter Nelson, Lindsay Aamodt, Bjorn Hovland, Chris Baek, Nathan Blackham, Greg Kurtzer
Rippling Jira Asset Mgmt add-on approved — 12mo commit + cancellation push
May 29, 2026 · operational · medium62% confidence
In a 5/29 Slack DM with Steve Wallace, Peter approved the Rippling Jira Asset Management add-on under negotiated terms. Rippling proposed a 19-month commit co-termed with the main Rippling agreement (~$21.9k total: $6,420 upfront after 2 free months due 8/21, then annual billing at $12/user/month for 107 users, includes monitoring/maintenance). Peter pushed back on lock-in, accepted one year, asked about cancellation terms. Steve replied he would offer 12-month commit with cancellation for convenience at month 11+ with 30 days notice. Peter said works for me. Decision is contingent on Steve actually securing the cancellation clause.
People: Steve Wallace
JPD board scope locked to ordered priority list — Peter drew the line in writing to Nathan
May 28, 2026 · operational · high80% confidence
In a long Slack DM thread on 5/27 (~25 Peter messages, 09:15–09:41 AM PDT), Peter rejected Nathan's draft framing for JPD scope and replaced it with an absolute definition: JPD is an ordered list of product's priorities used to drive company strategy, and nothing else. Not project planning, not marketing coordination, not a control surface for engineering order-of-operations. Tickets should be as large as possible and only split when product strategically cares about sub-priority. Value Drivers carry GTM linkage and dates. Every time someone tries to widen JPD scope, Nathan is instructed to push back. Reinforced same day in Baek 1:1 (Peter-recorded Fathom) and surfaces in the RLC cross-functional standup where Nathan is tasked with drafting the formal product-board structure proposal.
People: Nathan Blackham, Chris Baek, Bjorn Hovland
Hardware lab: paint the full picture and buy the whole complement upfront
May 26, 2026 · operational · high92% confidence
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).
People: Nathan Blackham, Steve Wallace, Justin Haynes, Bjorn Hovland, Scott (NVIDIA)
Sherif RESF hardware: Wallace owns directly — escalation triggered by Greg
May 26, 2026 · operational · high95% confidence
When Greg pinged Peter in #distinguished-leaders saying the RESF (Sherif) had been waiting on systems and Sherif had been emailing Moody for weeks, Peter took the heat publicly ("I do not need thanking. This is a disaster.") and re-assigned ownership directly to Steve Wallace. Steve had it on Moodys plate and it slipped while Moody was out for a bereavement. Peter then DMed Steve to take ownership ASAP — Steve confirmed and committed to staying on top of it through the vendor build/ship.
People: Steve Wallace, Greg Kurtzer, Sherif, Moody
Engineering owns docs content; Customer Engineering or Marketing owns customer-ready packaging
May 26, 2026 · operational · high93% confidence
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.
People: Ryan Smith, Nathan Blackham, Justin Haynes, Lindsay Aamodt
Slip Fuzzball V4 date now and drop confidence rather than fight to hit it
May 26, 2026 · operational · high95% confidence
In the Chris Wolford 1:1, Peter coached Chris to take the V4 target date (end of May, 80% confidence) out by ~2 weeks immediately, drop the confidence number now if his gut said 50-50, and tell the team explicitly: we are sliding so we hit. Frame the new date as a high-confidence communication contract with Go-to-Market (Lindsay) rather than a hope.
People: Chris Wolford, Lindsay Aamodt
Rippling Asset Mgmt — time over cost; pay full $18k for end-of-June over $15k for December
May 21, 2026 · operational · medium63% confidence
The Rippling Asset Management integration project was de-scoped to ~$15k from ~$18k. Peter decided the full-scope original at $18k is acceptable IF Rippling can deliver by end of June. Steve will get the timeline from Kelly Wall to inform the final decision. Explicit framing: time over cost. The principle is conditional — if Rippling slips on the end-of-June timeline, the math changes and $15k-for-December may be the right call.
People: Steve Wallace, Kelly Wall, Rippling (vendor)
Moody Citibank card hard cutoff 6/15 — force-action via past-tense framing after 9 months of soft asks
May 21, 2026 · operational · medium76% confidence
After Kelly Wall described 9 months of soft asks to Steve Moody to switch from the personal-history Citibank card to the Ramp card (forcing manual finance journal entries every month), Peter directed Kelly to send Moody a notice that the card has been disabled and will stop working on June 15. CC Steve Wallace. Phrase it past-tense (has been disabled) plus future-fact (stops working 6/15) — not request language. Peter explicitly affirmed his prior gate (Kelly checks with him before shut-offs) while greenlighting this one because Kelly is giving a month notice — the notice IS the legitimacy gate.
People: Steve Moody, Kelly Wall, Steve Wallace, Bjorn Hovland
Discretionary bounty offered for Yeshs vulnerability disclosure — case-by-case mode, no formal program
May 21, 2026 · operational · medium71% confidence
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.
People: Yesh (external), Steve Wallace, Bjorn Hovland, Justin Haynes
Lab hardware acquisition shift — buy all 8-10 servers at once, Texas DC over Reno, NVIDIA+AMD outreach
May 21, 2026 · operational · high72% confidence
Committed in Nathan 1:1 5/21 to a hardware acquisition strategy shift: buy all needed lab hardware at once (8-10 servers) instead of one-per-quarter. Cost is not the barrier; speed of development is. Reno office ruled out (1Gbps shared, no after-hours support, 5-6 server power/cooling cap). Texas DC preferred — to be re-evaluated against Reno after Nathan defines the full hardware list. Peter to email Scott at NVIDIA (H100/B200/B300) and discuss strategy with Steve directly. Nathan to email AMD for equivalent GPU hardware. Hardware sits inside the broader CI/CD acceleration goal — shift to Koji for automated signed kernel builds in a secure enclave to handle frequent builds and zero-day vulnerabilities. Hardware-acquisition shift is what unblocks the Koji shift.
People: Nathan Blackham, Steve Wallace, Scott (NVIDIA)
Engineering owns all QA — Nathan accountable; tests required for Done; Ryans team builds tooling not rescue
May 21, 2026 · operational · high79% confidence
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.
People: Ryan Smith, Nathan Blackham, Justin Haynes, Lindsay Aamodt
Jira confidence-as-contract doctrine codified across engineering directs
May 21, 2026 · operational · high84% confidence
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.
People: Justin Haynes, Chris Wolford, Nathan Blackham, Max Spevack, Brian Dawson, Lindsay Aamodt
No bugs, only change requests — structural reframe for product/engineering interaction
May 19, 2026 · operational · high88% confidence
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.
People: Brady Dibble, Brian Dawson, Chris Baek, Jamie, Nathan Blackham, Justin Haynes
Engineering QBR format — collaborative discussion with three topics, not a presentation
May 13, 2026 · operational · medium73% confidence
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.
People: Chris Baek, Nathan Blackham, Justin Haynes, Steve Wallace, Chris Wolford, Ryan Smith, Max Spevack
Eliminate one-off release processes — paved-paths Jira initiative Peter commits to prioritize
May 7, 2026 · operational · high92% confidence
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.
People: Justin Haynes, Brady Dibble, Brian Dawson
Add Justin to Binarly meeting; debrief AFTER, not before
May 5, 2026 · operational · low73% confidence
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.
People: Justin Haynes, Sarah Almaraz
Peter delivers Reno QBR C-suite intro Thursday — covering Bjorn late arrival
May 5, 2026 · operational · medium76% confidence
Peter will deliver the C-suite intro at Reno QBR Thursday morning, since Bjorn arrives Thursday afternoon. Peter arrives 8:45 AM Thursday. Greg travels to Houston with Adam for a 1 PM Thursday sales meeting.
People: Bjorn Hovland, Gregory Kurtzer, Sarah Almaraz, Ramesh Srinivasan, Chris Baek
Three-tier board hierarchy formalized — Strategic EPICs / Value Drivers / Tactical Jira
May 5, 2026 · operational · high93% confidence
Aligned with Bjorn on a 3-tier hierarchy: Strategic Board (EPICs requiring CEO-level prioritization), Value Drivers Board (GTM stories), and Tactical Boards (Jira execution). The current PPL board converts to the Strategic Board. Top ~50 only; anything below is wasted prioritization that will need redoing by the time it is worked on. Greg agreed to disagree-and-commit once Peter+Bjorn document the rules and walk him through.
People: Bjorn Hovland, Gregory Kurtzer, Brady Dibble, Nathan Blackham
Mariah escalates Stephen Moody project delays directly to Peter (bypass Wallace)
May 4, 2026 · operational · medium70% confidence
Mariah will notify Peter immediately when Steve Moody delays HR-relevant project work. Triggered by a 6-week unresponsiveness pattern on the Rippling/JIRA integration that Steve Wallace had not escalated. Direct-escalation bypasses the manager (Wallace) for HR-adjacent commitments while Peter assesses whether this is a Moody problem or a Wallace prioritization problem.
People: Mariah Rippee, Steve Wallace, Stephen Moody
PPL is being misused — push Bjorn to realign it to strategic priorities
May 4, 2026 · operational · high85% confidence
The Product Priority List has drifted from a strategic-priority list (epic-level) into a granular project tracker, obscuring strategic priorities (RLCAI on Spark buried at #88) and creating bottlenecks (Ollama package delayed to May 15). Peters position: PPL must return to defining company strategy at epic level; granular tasks belong in JIRA. Will engage Bjorn directly to realign — this is the framing decision; the implementation is the negotiation with Bjorn.
People: Bjorn Hovland, Greg Kurtzer, Brady Dibble
Documentation process — Product defines exit criteria in Jira, Engineering delivers
May 4, 2026 · operational · high77% confidence
Formalize documentation ownership: Product defines documentation requirements in Jira ticket exit criteria (e.g., docs suitable for blog post). Engineering delivers content meeting those criteria. Product or Marketing (Lindsay) refines technical content into user-friendly format.
People: Chris Baek, Brady Dibble, Lindsay Aamodt
Tighten Jira-as-system-of-record into active enforcement — instruct teams to ignore Slack-only requests
May 1, 2026 · operational · high80% confidence
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.
People: Peter Nelson, Justin Haynes
Ryan Smith owns docs.ciq.com
May 1, 2026 · operational · medium90% confidence
docs.ciq.com was orphaned after Gwen's departure. In Ryan's 1:1, Peter assigned ownership to Ryan, who will coordinate with Arian and Steven on the existing work.
People: Peter Nelson, Ryan Smith, Arian, Steven
Empower Nathan to defer Hassan secure-boot working session if engineering not ready
Apr 29, 2026 · operational · medium84% confidence
Apr 28 morning, Nathan flagged in #google-partnership-governance that he was not prepared for the Hassan working session that afternoon. Peter (at IAG, unable to attend) DMed Nathan: Youll be the senior guy in the room. If we arent ready for it tell Kelly we arent ready and to push it back. Brady and Kelly both signaled flexibility; the team coordinated and chose to proceed with a working-meeting framing. Peter closed the channel thread with Thank you all.
People: Nathan Blackham, Kelly Hall, Brady Dibble, Hassan (Google)
Fuzzball PoC ownership belongs to Sales Engineering, supported by Engineering
Apr 27, 2026 · operational · medium78% confidence
When Bjorn asked who should own Fuzzball PoCs (Sales Engineering vs Wolfgang/Godlove vs Support), Peter answered definitively: Sales Engineering, supported by Engineering. Bjorn agreed with the framing — pushback was strictly about Sales Engineering not being enabled on Fuzzball today (resourcing gap), not the principle. The default routing stands.
People: Bjorn Hovland, Ramesh Srinivasan, Jonathon Anderson, Wolfgang, Godlove, Sales Engineering team
Block Max's calendar — don't schedule anything for the time being
Apr 18, 2026 · operational · medium90% confidence
In a DM (4/17 11:10 AM Pacific), Peter directed Sarah (assistant) to stop scheduling anything for Max Spevack for the time being. This operationalizes the indefinite-leave posture triggered by Christina's 4/16 7:45 PM call telling Peter that Max needs time away. Rather than letting Max's calendar keep generating missed-meeting signals to the org (like the 4/16 1:1 and interview no-shows), Peter chose to block new scheduling entirely until further notice.
People: Peter Nelson, Sarah Almaraz, Max Spevack
Quality initiatives must be ticketed visible work, prioritized by Product
Apr 18, 2026 · operational · high87% confidence
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.
People: Peter Nelson, Brian Dawson, Brady Dibble, Justin Haynes, Ryan Smith
Approved ISO 42001 AI User profile addendum (~$30k)
Apr 17, 2026 · operational · medium68% confidence
Approved adding the optional AI User profile to CIQs ISO 42001 certification for approximately $30k, aligning the audit cycle for both Provider and User profiles over the three-year certification period.
People: Steve Wallace
Delivered Jira Hygiene Mandate to Engineering
Apr 17, 2026 · operational · high87% confidence
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.
People: Nathan Blackham, Justin Haynes, Chris Wolford, Chris Baek, Steve Wallace, Ryan Smith, Max Spevack, Brady Dibble
Committed CIQ Engineering Resources to Unblock RESF
Apr 15, 2026 · operational · medium69% confidence
Committed CIQ engineering resources (specifically Max Spevack) to unblock RESF, positioning RESF health as critical to CIQ success. Committed to asking Nathan to prioritize providing new AWS contacts for Leigh to bypass stalled Duncan access. Directed Chris to lock down internal-rasf Slack channel for Leigh's weekly write-ups. Clarified Max's role as Chief Architect for Everything Linux focused on upstream health and AI-automated CVE remediation. Agreed Brian's value is limited to admin tasks — Leigh will communicate this assessment to Greg.
People: R. Leigh Hennig, Max Spevack, Nathan Blackham, Brian, Greg Kurtzer
Delivered Jira Hygiene Mandate to Engineering
Apr 15, 2026 · operational · high87% confidence
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.
People: Nathan Blackham, Justin Haynes, Chris Wolford, Chris Baek, Steve Wallace, Ryan Smith, Max Spevack, Brady Dibble
Committed to engineering date hygiene confrontation with directs
Apr 14, 2026 · operational · high70% confidence
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.
People: Chris Baek, Nathan Blackham, Justin Haynes, Steve Wallace, Chris Wolford, Ryan Smith, Max Spevack
Sensitive Decision
Escalated Engineering Estimation Accountability — 58% Miss Rate
Apr 11, 2026 · operational · high68% confidence
Identified that 58% of engineering estimates are being missed, with most date changes occurring after the target date. Declared this unacceptable and directed Brady to present this data at the next Engineering Weekly (Apr 14). Peter committed to personally attending to ensure accountability and a clear plan to fix the process.
People: Brady Dibble, Brian Dawson
Reinforced Product Owns Exit Criteria — Engineering Cannot Unilaterally Remove Requirements
Apr 11, 2026 · operational · high74% confidence
Directed Brady and Brian that Product defines the 'what' and the 'when' while Engineering owns the 'how'. Engineering cannot unilaterally remove requirements from exit criteria. The correct response when a requirement is challenged is 'When can you deliver it?' not to debate or remove it. Forwarded the meeting recording to Bjorn and Chris Baek to align them on this prod/eng interface vision.
People: Brady Dibble, Brian Dawson, Bjorn Hovland, Chris Baek
Reinforced Product Ownership of Exit Criteria
Apr 10, 2026 · operational · high74% confidence
Engineering unilaterally removed the NVIDIA CUDA toolkit requirement from RLC Pro 9.6 LTS exit criteria, citing lack of automation. Peter clarified in the Brian/Brady sync that Product owns exit criteria and prioritization, Engineering owns the solution and date. When a requirement is challenged, Product asks When can you deliver it - not whether to include it.
People: Brady Dibble, Brian Dawson, Bjorn Hovland, Chris Baek
Google NEXT - Value-First Attendance Framework for Nathan
Apr 9, 2026 · operational · medium62% confidence
When Kelly asked if Nathan should attend Google NEXT (April 21-24), set a value-first framework: Nathan goes only if there's a concrete business objective. Pushed Kelly to define the business case rather than defaulting to sending people.
People: Nathan Blackham, Kelly Hall, Bjorn Hovland
Committed to Improve Team Bandwidth Visibility in Monday Meeting
Apr 7, 2026 · operational · low85% confidence
Committed to discuss with Nathan how to improve visibility in the Monday meeting on team bandwidth and impact, after Andrew raised he lacks visibility into other teams' work and hesitates to ask for help for fear of disrupting higher-priority work.
People: Nathan Blackham, Andrew Jorgens