Operational Decisions
49+ recent decisions
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
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
CentOS Bridge Deprioritization Held Despite Customer Risk
Apr 7, 2026 · operational · medium90% confidence
Confirmed to Andrew Jorgens that CentOS Bridge is consciously deprioritized. Acknowledged customer reputation risk (customer re-evaluating contract after only 4 CVE fixes) but held the line, explaining that 'important' is insufficient justification - a project must be more important than something else currently being worked on.
People: Andrew Jorgens
Set April Engineering Delivery Miss Target at 3-6 Items
Apr 7, 2026 · operational · medium82% confidence
Set a specific target of missing 3-6 items out of ~50 April engineering deliverables at Leadership Roundtable. The list contained mis-categorized items, granular sub-tasks, and placeholder dates. Follow-up: Chris Baek and Bjorn to prune the list tomorrow, engineering leads must update Jira with realistic dates by 9am.
People: Chris Baek, Bjorn Hovland, Engineering leads
RESF JIRA Date Reset for Realistic Expectations
Apr 4, 2026 · operational · high93% confidence
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.
People: Nathan Blackham, Justin Haynes, Max Spevack, Lindsay Aamodt, Chris Baek
AI/Data Security Audit Commitment to Greg
Apr 4, 2026 · operational · medium91% confidence
When Greg raised concerns about CIQ leaking data through AI agents/bots/services, Peter committed to getting Michelle's oversight team to do an assessment/audit of what's running and with what access.
People: Greg Kurtzer, Michelle, Moody, Chris Baek
Sensitive Decision
Accepted CLK 6.18 delay to March 31
Mar 25, 2026 · operational · medium96% confidence
Approved Jonathan Maple's request to slip CLK 6.18 from March 27 to March 31, due to kernel source-git conversion process. Positively reinforced Maple's proactive escalation.
People: Jonathan Maple, Nathan Blackham, Brett
Saudi training — Confirmed Dieter for May 5-6 Linux training program
Mar 24, 2026 · operational · medium68% confidence
Confirmed Jonathan Dieter as the trainer for Saudi Arabia Linux training program (May 5-6). Discussed in Dieter 1:1 and relayed confirmation to Adam Jackson. Pending security review.
People: Jonathan Dieter, Adam Jackson
RESF — Orchestrated demand-pull approach for CIQ help
Mar 24, 2026 · operational · medium67% confidence
Directed that CIQ help should come through RESF team requests (especially Taylor/Sherif) rather than being imposed from above. Reinforced 'CIQ will help if you ask' messaging through Greg and Leigh. Wants RESF work driven like a project with visibility into requests.
People: Greg Kurtzer, Leigh Hennig, Taylor, Sherif, Mustafa, Jonathan Dieter
Start Skip-Level 1:1s Next Week — 30 Min, 1-2 Per Week
Mar 21, 2026 · operational · medium95% confidence
Approved starting skip-level 1:1s with 12 key engineering ICs (Dieter, Maple, Skip, Jeremy, Andrew, Sultan, Alex, Mustafa, Joseph, Zorina, Giovani, Rahul). 30 minutes each, 1-2 per week, random order. Sarah to schedule.
People: Sarah Almaraz
Shared Mini-Me Source Code to Internal Org
Mar 18, 2026 · operational · low72% confidence
Shared Mini-Me source code by creating repo at ctrliq/min-me in CIQ GitHub org, after Ryan, Nathan, and Michelle independently asked for it. Proactively noted never having seen the code, setting quality expectations. Requested internal-only repo visibility.
People: Ryan Smith, Nathan Blackham, Michelle Novicio, Max Spevack, Norm Bhatti
RESF Communication & Information Control Strategy
Mar 18, 2026 · operational · high91% confidence
Established multi-layered communication control for RESF transition: (1) Posted own #engineering message with different language than Greg's draft, emphasizing visibility requirement. (2) Told eng-management nobody talks on RESF Zoom calls because RESF members can hear. (3) Asked Lindsay to confirm no social media leaks. (4) Told Max to keep RESF off Department Heads agenda Thursday.
People: Max Spevack, Lindsay Aamodt, Greg Kurtzer
Reaffirmed Speed-First Culture to Brady Before Leave
Mar 13, 2026 · operational · medium90% confidence
Reaffirmed to Brady that the directive is move fast and break things — leadership provides air cover. Corrected a team perception that leadership expects both speed AND perfect quality.
People: Brady Dibble, Brian Dawson
RESF Internal Comms — Slack Post Not AMA
Mar 13, 2026 · operational · high92% confidence
Decided to announce RESF engineering support via a Slack post (not company-wide AMA) to control narrative without signaling alarm. Nathan follows up with team Q&A for project impacts.
People: Nathan Blackham
RESF Monday Cutover — Finalized 3 PM PT Execution Plan
Mar 13, 2026 · operational · critical97% confidence
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.
People: Nathan Blackham, Max Spevack, Greg Kurtzer, Steve Wallace, T.J. Gohl, Jonathan Dieter, Ryan Smith, Justin Haynes, Leigh Hennig, Mustafa Gezen, Joseph Tate
RESF Impact — Consolidated Marketing Alignment Meeting
Mar 11, 2026 · operational · medium50% confidence
Decided to schedule a single, consolidated meeting with Chris Wolford and Marketing to align on a new delivery schedule once the full RESF impact is known, rather than piecemeal schedule updates.
People: Chris Wolford, Marketing team
Enforcing Product Process for Greg's RLCAI Requirements
Mar 11, 2026 · operational · high60% confidence
Enforcing the correct process by directing all of Greg's RLCAI requirements to the Product team rather than allowing Greg to bypass Product and give direct requirements to Engineering. Brian Dawson raised the concern; Peter is supporting and enforcing.
People: Greg Kurtzer, Brian Dawson, Brady Dibble
Coordinated Google Post-Mortem Alignment Between Nathan and Bjorn
Mar 11, 2026 · operational · high69% confidence
Ensured Nathan's Google post-mortem document was reviewed by Bjorn before sending to Google, because Bjorn has a Thursday call about contract changes and the doc could undermine his asks.
People: Nathan Blackham, Bjorn Hovland, Max Spevack
Claude Government Use — Restrict Shipping, Internal Use Fine
Mar 10, 2026 · operational · medium90% confidence
Directed AI committee not to ship products to the government with Claude use embedded, while clarifying that internal CIQ use of Claude remains fine. Shared Microsoft's statement about Anthropic products remaining available except for Department of War. Framed as 'don't overreact' — risk mitigation, not panic.
People: AI Committee
TPS Report Visibility — Expand Justin's Reporting Scope
Mar 10, 2026 · operational · medium70% confidence
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.
People: Justin Haynes
Custom Engineering Scoping Process — Nathan as Gate
Mar 6, 2026 · operational · medium80% confidence
Established formal process for unplanned custom engineering requests from sales: Nathan provides quick effort estimate (days/weeks/months), enabling formal prioritization. Nathan can say no, escalation goes to Peter.
People: Ryan Smith, Nathan Blackham, Dave Dickerson
Push for Continuous Sales/Support Enablement
Mar 4, 2026 · operational · medium76% confidence
Aligned with Greg on pushing for continuous product enablement (demos, walkthroughs) for Sales and Support on every new engineering feature, overriding Bjorn's resistance. Peter committed to re-engaging Bjorn on this.
People: Greg Kurtzer, Bjorn Hovland
Directed March engineering priorities to come from Bjorn (Product)
Mar 3, 2026 · operational · medium71% confidence
When Chris Baek asked Peter to present engineering deliverables for March at the Leadership Roundtable, Peter redirected: the top priorities for March should come from Bjorn (Product), not from Engineering. Peter offered to go over them but insisted the framing should come from Product.
People: Chris Baek, Bjorn Hovland
Set maximum urgency on LTS 9.6 i686 package crisis
Mar 3, 2026 · operational · high65% confidence
Nathan escalated that i686 multilib packages were never built for LTS 9.6 — the S3 bucket and Peridot config were never created. Every LTS 9.6 package with i686 variants is missing them. Brady flagged Siemens as a customer that specifically cares about i686. Peter acknowledged the escalation and set maximum urgency expectation.
People: Nathan Blackham, Jeff Uphoff, Brady Dibble
Committed to RESF day-of execution planning meeting next week
Feb 27, 2026 · operational · high78% confidence
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.
People: Nathan Blackham, Max Spevack, Justin Haynes, Dieter, Bjorn Hovland, Leigh Hennig, Sarah Almaraz
Release artifact ownership assignment - Nathan RPMs, Justin images
Feb 26, 2026 · operational · high72% confidence
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.
People: Nathan Blackham, Justin Haynes, Max Spevack