Steve Wallace

Dec 19, 2025 - Jul 10, 2026

44

Decisions

0

Active Todos

8

Patterns

Decisions (44)

Sensitive Decision

Sensitive

Mandate Snyk vulnerability-remediation SLA compliance across all engineering teams

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.

Jun 30
operational

Rippling Jira Asset Mgmt add-on approved — 12mo commit + cancellation push

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.

May 29
operational

Sensitive Decision

Sensitive

Hire dedicated cloud-security engineer — Steve drafts JD, Peter champions, dovetail with Nathan STIG/FIPS gap

In Steve 1:1 5/21, TJ flagged CIQ is doing the bare minimum on infrastructure security across 4-5 clouds. Peter asked Steve to have TJ (or Steve) draft a quickie JD describing what the role does and is responsible for — explicitly NOT urgent, but needed as a champion artifact so Peter can take it to Bjorn/Greg with a concrete ask. Steve flagged that the same hire could dovetail with Nathans STIG/FIPS expertise need on the technical side; Peter agreed ("Awesome"). QBR 5/22 made it official as a Steve-owned area requiring formal assessment and potentially a new headcount.

May 26
people

Reward Yesh for responsible disclosure — CIQ first-ever bug bounty

When Yesh (pentestine@gmail.com) reported a ciq.com vulnerability on 5/21 via email, Peter responded within minutes to Steve Wallace and Bjorn: I would like us to reward here to encourage this behavior. He immediately forwarded the bug detail to Justin Haynes for the fix and aligned with Steve on severity. The reward is still pending execution as of 5/26 — this is the first bug bounty CIQ has ever paid.

May 26
strategy

Hardware lab: paint the full picture and buy the whole complement upfront

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).

May 26
operational

Sherif RESF hardware: Wallace owns directly — escalation triggered by Greg

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.

May 26
operational

Dedicated cloud security engineer role to be championed — dual-purpose JD covering cloud + STIG/FIPS

Committed in Steve 1:1 5/21 to champion a new dedicated cloud security engineer role. Steve will work with TJ to draft the JD; Peter will champion it to budget owners (Bjorn/Greg). Triggered by TJ flagging current cloud security as bare minimum and the proactive supply-chain projects (TJ on GitHub workflow SHA pinning, CeeLo on NPM package securing) needing a dedicated owner. Dual-purpose JD: also serves Nathans STIG/FIPS security expertise needs — one hire, two demand surfaces.

May 21
people

Rippling Asset Mgmt — time over cost; pay full $18k for end-of-June over $15k for December

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.

May 21
operational

Moody Citibank card hard cutoff 6/15 — force-action via past-tense framing after 9 months of soft asks

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.

May 21
operational

Discretionary bounty offered for Yeshs vulnerability disclosure — case-by-case mode, no formal program

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.

May 21
operational

Lab hardware acquisition shift — buy all 8-10 servers at once, Texas DC over Reno, NVIDIA+AMD outreach

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.

May 21
operational

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.

May 13
operational

CVE response strategy — three-pillar overhaul (process + tooling + strategic kernel review)

In Engineering Weekly Sync, Peter operationalized the 5/11 Leadership Roundtable vuln-handling commitment into three concrete pillars: (1) Chris Baek to restructure the embargo/CVE comms doc with Jamie, separating process from tooling/templates; (2) tooling strategy — Peter commits to email Greg requesting Claude Opus 4.7 whitelist for CIQ accounts AND to set up unbridled internal LLM models on Fuzzball for vuln investigations; (3) schedule strategic kernel philosophy review for early June, with Nathan and Justin to provide a list of downstream automation efforts to prioritize.

May 12
strategy

Late-August dedicated security hire timing (6 months post-Jasons departure)

Aligned with Steve in 1:1 that a dedicated security resource hire is appropriate in late August — six months after Jasons departure. Options on the table: full-time hire, fractional resource, or expanding the Shin Brothers role. Steve currently at 70% capacity on ISO 42001 documentation; workload expected to normalize after this week, with SOC 2 and ISO 27001 audits expected to be lighter.

May 7
people

Moody accountability: step up to senior contributor or be managed — framed as response to his growth ask

Flagged Moodys recent missed deadlines and failure to track work to Steve in 1:1, with explicit framing: this is a direct response to Moodys stated desire to become a senior contributor, not a punitive measure. Expectation set: Moody must step up and handle responsibility independently, not require close management. Steve aligned. Moody is out May 15-20 — coaching window is now.

May 7
people

Mariah escalates Stephen Moody project delays directly to Peter (bypass Wallace)

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.

May 4
operational

Ship CIQ kernel patch with extra fix; contribute upstream; race to be first/best on CVE response

Linux kernel CVE response: CIQ shipping 10 fixes vs CentOS Stream's 9 (CIQ found and is fixing an extra issue related to the CVE). Extra commit submitted upstream to centos-stream and acknowledged for inclusion. CIQ pushing to be first EL distro to release, with primary goal of customer reassurance and secondary goal of public proof point that CIQ contributes to security and is large enough to serve big customers. Also pushing patches to RLC kernels as fallback in case RH doesn't move quickly.

May 1
strategy

Approved ISO 42001 AI User profile addendum (~$30k)

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.

Apr 17
operational

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.

Apr 17
operational

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.

Apr 15
operational

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.

Apr 14
operational

Sensitive Decision

Sensitive

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.

Mar 13
technical

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.

Mar 13
operational

RESF Operational Security — Compartmentalize Until Board Action

Directed that Brian must not be told anything until after the RESF board notification. Emphasized extreme caution about leaks to Lewis. Approved Joseph being read into the initiative but warned about leak risk. Sequenced information flow: board action first, then notifications, then credential recovery.

Mar 10
strategy

Sensitive Decision

Sensitive

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.

Mar 4
people

Directed RESF counter-narrative to Bjorn to prevent premature escalation

Directed Steve Wallace to email Bjorn (CC Peter) with evidence of positive RESF engagement through Mirror Manager project before Bjorn potentially takes aggressive action. Steve's team has made progress with Neil — environment access granted, Mirror Manager epic unblocked — while other teams report significant friction.

Feb 20
strategy

Delegated Jason Lewis termination coordination to Mariah for March 3

While preparing for Dubai trip, delegated coordination of Jason Lewis termination logistics to Mariah Rippee, asking her to work with Steve Wallace during the week Peter is out, targeting the first Monday of March (March 2).

Feb 6
people

Jason Lewis Termination - Ready to Action

Confirmed readiness to proceed with Jason Lewis termination now that the ISO 27001 certification letter has been received. Will coordinate with Steve Wallace and Mariah Rippee (HR) to execute. Jason recently requested a seat at the table for self-service discussions, unaware of the pending action.

Feb 4
people

Infrastructure Cost Savings Approval

Approved a $10K infrastructure savings proposal from Steve Wallace with the condition that it does not burden development work.

Feb 3
operational

Clarified bonus evaluation framework - above and beyond for step-function impact

Clarified to Steve Wallace that bonuses are awarded for actions that are above and beyond standard role expectations and provide a step function for CIQ - not for standard job performance, which is covered by salary. Also confirmed TJ bonus (Greg approved Jan 23 via private DM) and committed to close the loop with Greg.

Jan 30
people

Approved transfer of Depot operations from Justin to Steve team

Approved transferring Depot operations from Justin team to Steve team as a test of Steve team SRE capabilities. Justin team will define the architecture for moving Depot to object storage, then hand off execution to Steve team who will own provisioning, infrastructure, and monitoring.

Jan 26
operational

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.

Jan 24
operational

Transfer Depot operations from Justin team to Steve team

Depot operations will transfer from Justin team to Steve team. Justin team will define the architecture for moving Depot to object storage, then hand off execution to Steve team for provisioning, infrastructure, and monitoring.

Jan 23
operational

Jason Lewis layoff with Steve Wallace as compliance owner

Decided to proceed with Jason Lewis departure (structured as layoff) due to expectation misalignment and damaged relationship with Bjorn. Steve Wallace will assume all compliance responsibilities (ISO 27001, SOC 2, ISO 42001). Budget reserved for full-time replacement after 6-month layoff waiting period. Fractional hire and external auditor approved for interim.

Jan 23
people

Depot Management Transfer to SRE

Decided to transfer Depot management (monitoring, maintenance) from Justin org to Steve SRE team. Committed to connecting Steve and Justin to define the work distribution.

Jan 16
operational

Jason Lewis Retention Review - Requested Written Impact Case

Paused final decision on Jason Lewis role and requested Steve write a formal case detailing the operational impact of Jason departure - specifically on ISO 27001/42001 certifications and CIQ Federal work.

Jan 16
people

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.

Jan 11
people

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.

Dec 31
strategy

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.

Dec 19
operational

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.

Dec 19
operational

Related Patterns (8)

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.

139 occurrences79% success

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.

136 occurrences79% success

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.

131 occurrences73% success

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.

129 occurrences73% success

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.

122 occurrences80% success

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.

118 occurrences78% success

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.

116 occurrences77% success

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.

89 occurrences74% success