Chris Wolford
Dec 19, 2025 - May 13, 2026
31
Decisions
0
Active Todos
8
Patterns
Decisions (31)
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.
Sensitive Decision
Manage Wesley via Greg; set boat-anchor trigger with Chris (preserve optionality)
In the Chris W 1:1, Peter decided to manage Wesley's performance situation through his Greg relationship rather than moving Wesley onto a PIP or active weekly-1:1 performance track like Cole and Thomas Chin. Assessment: Wesley is capable but slow, requires handholding, won't operate at senior/principal level, but is not a net negative. Chris asked to proactively flag if Wesley becomes a boat anchor on team productivity — that is the threshold for escalation.
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.
Delayed HR action pending Chris feedback in upcoming 1:1
When Mariah proposed proceeding with an HR-related action, Peter declined, saying he wants to get feedback first from Chris about how it's going in his 1:1 with Chris this week. Mariah acknowledged and asked to be kept posted.
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.
Established Fuzzball AI validation process
Committed to validating Greg's Fuzzball AI marketing claims before they go external. New process: Greg/Jonathan provides desired story, Peter documents engineering tests required, engineering validates and gives thumbs-up/down. HumanX conference in 2 weeks is the forcing function.
Fuzzball SaaS Prepaid Token Billing Model with Unified Portal Backend
Drove adoption of prepaid token ('CIQ Tokens') billing model for Fuzzball SaaS MVP, with unified Portal backend as single source of truth for all user accounts and token balances. Free tier deferred to fast-follow. MVP requires account + credit card to run workflows.
RESF Impact — Consolidated Marketing Alignment Meeting
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.
Westley Transition — 70% Fuzzball, Maintain Depot Support
Westley will start transitioning to Fuzzball at 70% allocation while maintaining depot support work for Justin team until fit is confirmed.
Toyota POC — No Hotfix, Demo MPI and PBS Separately
Decided NOT to rush a hotfix for Toyota's urgent out-of-scope MPI-via-PBS request before their Thursday director meeting. Team will demo MPI and PBS as separate working components, explain the integration bug is known, and commit to fix in ~1 week by the March 17 Reno meeting.
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.
Escalated Ian Kaneshiro retention to CEO level
After learning Ian Kaneshiro (PIC team, reports to Chris Wolford) resigned to join an AI startup, Peter immediately directed a retention escalation: told Mariah to get Greg talking to Ian, told Greg to do anything to keep him. After learning Ian had already accepted and wouldn't go back on it, shifted to ensuring the door stays open for a future return.
Directed Fuzzball team to improve logging and error observability
After AMD MI300 troubleshooting meeting, directed Fuzzball team (Jonathon Anderson, David Horn) that the product needs better logging and error visibility. Customers should be able to self-diagnose issues via log files instead of requiring live troubleshooting meetings with CIQ engineers.
Coached David Godlove on sales-focused approach for AMD Fuzzball presentation
During the AMD Fuzzball overview meeting, coached David Godlove via DM to maintain a sales mindset rather than defaulting to engineering transparency about product limitations. Emphasized that the goal was to make AMD want to recommend Fuzzball, not to give a technical peer review.
Committed to Anduril attendance with Max
Committed that Peter and Max will attend Anduril events and meetings that are valuable.
Recommend partial bounty payout for Fuzzball single-binary work
Recommended paying out half of the originally established bounty to the team members who completed the Fuzzball single-binary work. Want to use bounties as a repeatable, low-friction model across engineering and ensure all of engineering knows about the payout.
Directed output-based management approach for underperforming engineers
Directed Chris Wolford to shift from activity-based to output-based management for engineers Kyle, Thomas, and Cole. Set ambitious goals (2x output), measure only results, give underperformers a short window (2 weeks) to meet targets, and replace them if they miss. Guaranteed headcount back for every open chair for the next 6 months.
Advocated for PIC team progress to Greg
Reported to Greg (CEO) about satisfaction with Chris Wolford team improvement and transparency. Thanked Greg for going into PIC Demos meeting with open mind despite having strong opinions. Highlighted Ian Kaneshiro as fantastic.
Approved Greg-Cedric engagement starting Monday
Approved Greg beginning conversations with Cedric on Monday to provide context on upcoming PIC work. Cedric will continue participating in epic scoping sessions to stay connected to the tactical work.
Conference Travel Approval - David Godlove HBCSF
Approved David Godlove travel to speak on Apptainer at HBCSF conference in Chicago in late March (~$2,200 cost). Required Chris Wolford to coordinate with Lindsay (Marketing) and Chris Baek (Finance) as part of the approval.
Product Roadmap Overload - Challenge Product on Prioritization
Directed Chris Wolford to push back on Product for a clear separation of critical path vs nice-to-have items in the H1 roadmap. Current roadmap is overloaded and risks critical path items.
Strategic Map Framework - Value Drivers vs Internal Efficiency Separation
Established new H1 strategic planning framework that separates customer-facing Value Drivers from Internal Efficiency Drivers. Framework uses three lanes: middle lane for Value Drivers (the WHY), top lane for GTM activities, bottom lane for engineering deliverables. Also established phased estimation process: low-confidence ballpark dates first, then engineering-only session to raise confidence.
Work intake must flow through managers, not directly to engineers
Established new process where small customer requests go to Engineering Managers (Justin, Chris W.) for approval. EMs will attend bi-weekly CECA board review to ensure they are in the loop on incoming work.
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.
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.
Fuzzball SaaS - Defer Pending Technical Alignment
Rather than making a call on Fuzzball SaaS viability concerns raised by Chris Wolford, directed Chris to align with Jonathan (who has pitched cloud-native ideas) to form a unified stance. If they reach opposing conclusions, escalate to Peter. H1 planning docs to proceed with caveat that SaaS initiative is pending alignment.
Talent Introduction for Fuzzball Org
Introduced Meena Rajvaidya to Chris Wolford via email, recommending her as a senior leader for the Fuzzball org with deep experience in monitoring/visibility.
Talent Introduction for Fuzzball Org
Introduced Meena Rajvaidya to Chris Wolford, recommending her as a senior leader candidate for the Fuzzball org, noting her deep experience in monitoring/visibility from when she previously worked for Peter.
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.
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.
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.
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.
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.
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 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.