Ryan Smith
Dec 23, 2025 - Jul 10, 2026
54
Decisions
0
Active Todos
9
Patterns
Decisions (54)
Sensitive Decision
Sensitive Decision
Sensitive Decision
Engineering owns defining the ask, success criteria, and documentation; CS responds to specific asks
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.
Mandate 24-hour Sev-1 outage auto-escalation to estaff and AE
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.
Establish 3 as the performance-review norm — close alignment with Bjorn and Greg
Peter established that a 3 on the 5-point scale is the expected/solid norm in performance reviews (not a 5), and closed alignment on this calibration standard with Bjorn and Greg, resolving a leadership split that had become visible to the org during the active review cycle.
Sensitive Decision
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.
Refuse holiday-weekend pressure on people — Mariah review deadline AND Ryan reviews
Two paired actions on 5/24. (1) When Mariah pushed Peter Sunday evening that mid-year reviews were 50% complete on the day-of deadline, Peter held the line — no pushing direct reports who are on a 3-day holiday weekend. Drew distinction between the people who plan ahead (will finish on time) and those who do not (will finish Tuesday night either way). Committed to thinking about better engagement separately. (2) Same evening Peter DMed Ryan: I am not going to read your reviews today or tomorrow — you should take a break. Same posture applied to a direct report Peter could see was burning out from a hard week.
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.
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.
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.
Ask Bjorn to deliver ARR/dilution/Series-B rationale to engineering org
Committed to ask Bjorn to clarify the link between doubling ARR (to $20M), Series B funding with minimal dilution, and employee stock value — to be delivered in All Hands or in Peters org meeting. The intent is for Bjorn to walk the team through the knife-edge: failure forces more investor funding with significant dilution; success enables Series B with minimal dilution and a clear path to profitability.
Icicle viability gate: AI inference benchmark on H100 decides go/no-go
Set a clear decision gate for the Icicle project: viability is determined by performance on a real-world AI inference workload, not synthetic benchmarks. Omer to run the RLC Pro AI benchmark on an H100 GPU. 2-3x synthetic CPU/memory degradation is acceptable IF power savings are significant for AI inference; otherwise project gets punted.
Reassign Owen to Maxs AI tooling for definitive performance evaluation
In Ryan 1:1, decided to assign Owen to Maxs AI tooling projects when Max returns from leave (~3 weeks). Defines the project with Nate beforehand so it is ready to deploy day one. Resolves conflicting feedback: Ryan sees senior Golang engineer underutilized; Bjorn questions value; Max and Nathan have called recent work AI slop.
Assign Owen to Max AI tooling for definitive performance evaluation
Decision in Ryan 1:1 (Wed 5/6 12:30 PM) to assign Owen Wood to Max Spevack AI tooling projects on Max return from leave (~3 weeks). Definitive evaluation to resolve conflicting team feedback — Ryan sees senior Golang underutilized; Bjorn questions value; Max and Nathan have called recent work AI slop. Peter confirmed in DM with Ryan: We will get it rolling.
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.
Ryan Smith owns docs.ciq.com
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.
Manage Max situation — protect privacy, halt org outreach, decline his calendar
Peter is actively shielding Max Spevack from organizational pressure during a personal/private situation. Directed Sarah to access Max's calendar and decline all his meetings for the week, told Ryan to stand down ("No reaching out"), told Nathan to stand down ("worst thing Ryan can do is involve himself"), declined Mariah's offer to use Max's emergency contact ("let's give it a little more time"). Committed to talk with Max himself early this week.
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.
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.
Sensitive Decision
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.
Agent IQ: Requiring Bjorn to Justify Before Supporting
Peter directed that Bjorn must articulate how Agent IQ augments CIQ's portfolio before it gets engineering resources. Not killing the project outright but requiring strategic justification.
Sensitive Decision
Sensitive Decision
Shared Mini-Me Source Code to Internal Org
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.
RESF Operational Framework — CIQ Resources Work Under RESF Direction
Established and communicated to entire engineering org that all CIQ work for RESF must be done 100% at RESF direction, with every request flagged for Peter's visibility. Reinforced individually with Ryan (get accounting of in-flight work, ensure RESF person directing), Nathan (hold then green-light Taylor contact with specific messaging), and Mustafa (offer resources under RESF direction, recommend MatterMost for coordination).
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.
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.
Sensitive Decision
Custom Engineering Scoping Process — Nathan as Gate
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.
Sensitive Decision
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.
Sensitive Decision
Decided to carefully surface Icicle results to Bjorn
After validating Icicle test methodology with Ryan (BIOS change applied before both with/without comparisons — apples-to-apples), and learning Ani was told by Bjorn to stand down on Icicle, Peter decided to personally and carefully bring the validated results to Bjorn's attention.
Shaped Ryan's H-1 strategic plan with specific direction
Reviewed Ryan's H-1 plan and gave specific strategic direction: reframe team skill tracking to outcome metrics, loop Product into GTM translation validation, create simplified 4-page sales pitch deck, align with Max on Rocky Linux upstream strategy (pure RESF vs hybrid best-of-breed) before engaging community, and present AI-assisted goal-setting process at Engineering Weekly Sync.
Sensitive Decision
Set AI adoption/spending policy: pace over cost, fund passion project tokens
Codified org-wide AI tool policy: pace is priority over cost, high token spend signals productivity. CIQ will fund tokens for passion projects (learning) but not work-hour time for non-core work. Work-hour AI projects must align with core responsibilities.
Approved Professional Services strategy pivot
Approved Ryan proposed PS strategy pivot: align PS with Ramesh product-first vision, discontinue unprofitable standalone training deals and custom engineering work, focus only on product-aligned services (Rocky Linux migrations, dedicated support engineers/TAMs, HPC services) delivered through third-party vendors to scale without increasing headcount.
Sensitive Decision
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.
COGS data access unblocked for Ryan - Bjorn to grant via Kelly
Convened Bjorn and Ryan to resolve Ryans 6-month block on accessing official COGS data. Ryan had been forced to recreate the data independently, which conflicted with Bjorns H1 directive to use a single official source. Bjorn agreed immediately and will email Kelly Marlin today to grant Ryan full access.
COGS Visibility - Escalate Finance Data Access via Bjorn
Committed to scheduling a tri-party meeting with Ryan and Bjorn to secure finance data access (loaded rates) for Ryan's Intelligence Hub. Finance (Marlon, Kelly) previously denied Ryan's direct requests.
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.
Trinity Quirk & Chris Short Terminations Executed
Terminated Trinity Quirk for failing to progress NARF/CVE automation integration despite clear expectations. Terminated Chris Short for failing to deliver on critical RESF-related goals. Sent transparent communication to all of engineering explaining the WHY behind these decisions.
NARF Performance Accountability - Public Termination
Decided to execute a public termination within Nathan's org on Monday if NARF deliverables are not met. This is specifically intended as organizational signaling to drive accountability and force motion across the team. A second termination (Chris) may be required for legal reasons.
Advocate for Ryan's Strategic Seat
Committed to securing Ryan Smith a seat at the strategic decision-making table for RESF/Rocky Linux matters. Specifically promised to advocate for his inclusion in key meetings with Bjorn and Greg.
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.
Bonus Criteria - Strategic Alignment Required
Established bonus criteria: bonuses should be for accomplishments aligned with strategic goals that help scale or deliver faster, not just for being an awesome developer.
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.
RESF Crisis Response - Infrastructure Independence
After learning of hostile plans by RESF board members (Louis, Neil, Brian Clemens) to publicly attack CIQ, dismantle Rocky Linux infrastructure, and damage the project, initiated emergency response to replicate RESF infrastructure for Rocky 8, 9, 10 with minimal team awareness.
Related Patterns (9)
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.
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.
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.
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.
Strategic Alignment for Rewards
Compensation and bonuses should reward outcomes aligned with company strategy, not just individual talent or performance in isolation.