Brian
Dec 19, 2025 - Mar 13, 2026
32
Decisions
0
Active Todos
10
Patterns
Decisions (32)
Reaffirmed Speed-First Culture to Brady Before Leave
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.
AI Governance Single-Track Pivot for ISO 42001
Pivoted AI governance from dual-track (internal vs products) to single rigorous model because CIQ products (RLCAI, Fuzzball, Werewolf) now directly integrate AI, changing the liability profile.
Excluded Brian from RESF Pre-Transition Planning
Decided to exclude Brian from pre-transition RESF planning based on synthesizing risk signals from multiple sources. Brian's role will be carefully managed post-transition.
Enforcing Product Process for Greg's RLCAI Requirements
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.
Brian Clemens — Loop In After Front Door Closes
Decided Brian Clemens should be brought into RESF matters only after the front door is closed, acknowledging he'll be critical for reconstruction but the current phase requires operational security. Conditional on his behavior: 'If he hasn't gone off the reservation at that point.'
Sensitive Decision
Challenged RLC-AI performance claims before NVidia/Humain use
Peter personally interrogated the RLC-AI 9-10% performance advantage claim by going directly to Damen Knight (engineer who ran benchmarks) and Max Spevack. Discovered gains largely disappear when benchmarking code is properly optimized (uses torch.compile, etc.). Then asked Damen to evaluate whether Brian's marketing write-up is accurate or misleading: 'makes it sound awesome instead of pointless for data center deployments.'
Demanded proper advance coordination for customer meetings involving engineering
Pushed back strongly on a Volvo customer meeting that appeared on calendar at 5pm the day before. Demanded that important customer meetings involving senior engineering staff be scheduled with proper advance notice and coordination.
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.
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.
Established 'what vs how' framework for Product-Engineering communication
In weekly sync with Brady and Brian, established a clear framework: Product defines the 'what' (exit criteria with specific, aggressive targets like 'ISO builds <4 hours'), Engineering defines the 'how'. Vague communication to leadership creates unnecessary reactive work and must stop. Escalation path defined: weekly syncs or on-demand to Peter for process breakdowns only.
Committed to creating CVE remediation value driver for GTM
Committed to creating a value driver for CVE remediation work after learning that remediation volume jumped from 1 to 86 per week. Timeline is ~2 months to develop the story after validating the new process is sustainable.
Approved RLC+ and Pro product hierarchy with new naming and de-risked launch cadence
Approved a new product hierarchy: Stock Rocky (pure community mirror), RLC+ (free with NVIDIA/AMD drivers), RLC Pro (paid tiers). The RLC name now signifies CIQ value-add. Also approved a de-risked 3-phase launch cadence: Phase 1 (Feb) bundles RLC Pro + RLC Plus NVIDIA; Phase 2 (Feb) RLC Pro AI; Phase 3 (Mar) RLC Plus AMD partnership. Identified backporting vs roll-forward policy gap as a pre-launch blocker.
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.
PRD first drafts are gravel - meant to be thrown away
Get product to understand that the first iteration of a PRD exists to be thrown away. Its gravel, not precious. Engineering questions should come fast and furious, and the document should go through massive churn. Pride of authorship must be eliminated.
Stop coaching product, move to SLAs
Stop trying to teach product managers (Brady, Brian, Dawson) how to do their jobs better. Instead, provide prescriptive SLAs - clear timelines and direct questions. If they dont like the dates, they can restructure their requirements. Leave it on the floor and walk away.
PRD contract process - stop teaching product
Stop trying to teach product how to write PRDs. Define acceptance criteria for PRDs, respond within 24-48 hours, rearrange and cut scope ourselves, and hand back a contract. They can accept or negotiate, but no endless back-and-forth. Engineering restructures the work and presents how we will deliver.
Reinforced Product-Engineering handoff process with tighter SLAs
Reinforced existing handoff process between Product and Engineering: simplified 2-page PRDs with clear Exit Criteria, one-business-day feedback SLA from Engineering Managers, and all communication in Jira (not Slack) for audit trails.
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.
Require mandatory tagging of all fully AI-generated content
AI Committee established policy that all fully AI-generated content must be tagged to manage user expectations. Applies only to fully AI-generated content, not human-reviewed or AI-assisted work. Format and placement of tags is flexible.
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.
OSPO Restructure - New Mandate and Leadership
OSPO moved under Customer Engineering (Ryan Smith). Chris Short removed as head. New leadership: Brian Clemons (VP, RESF) and Lee Hennig (former RESF MD). New mandate: govern ALL open source CIQ touches, not just RESF. Top priority: eliminate extinction event risks. RESF board resolution target by H1 2026. Self-sufficiency goal: enable CIQ to internally reproduce Rocky Linux.
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.
CVE Automation Prioritized Over EUS Daily Numbers
Decision to push the EUS catch-up deadline to prioritize automating CVE work. Automation is a higher priority than hitting daily EUS numbers manually.
RESF Management Model Needed
Identified that RESF needs a clear management person or model as part of short-term response. The lord of the flies approach does not work. Does not matter if its Leigh or someone else, as long as they have personal energy/bandwidth. But it needs to be managed/run with clear accountability.
Engineering Blockers - Immediate Escalation Required
Established that engineering blockers (being stumped) must be escalated to Peter immediately. Product should not bail out engineering by providing solutions (like YAML files with business logic).
ProServe Work Prioritization Process
Established new process for handling professional services work: ProServe work will be prioritized against existing roadmap, not by dropping in-flight work. Product (Brady) owns prioritization decision, Engineering determines timing based on capacity.
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 Adoption Internally
Shared detailed Slack MCP setup instructions with team members. Hosted/recorded AI Dashboard session demonstrating Butler setup. Personally using and advocating for meeting prep automation.
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 (10)
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.
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.
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.
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.
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.
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.
Systemic Investment Over Short-Term Metrics
When short-term metrics conflict with systemic infrastructure improvements, invest in the infrastructure. Systems that prevent future problems are more valuable than optimizing current metrics.