Lead by Example with New Tools
159
Occurrences
77%
Success Rate
4.0
Avg Rating
Description
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.
Typical Approach
Personally adopt and use the tool/process. Share what works and what doesnt. Build shared knowledge base through practice. Standardize on tooling that creates reusable patterns across the organization.
Trigger Conditions
Last applied: August 28, 2026
Created: December 28, 2025
Example Decisions (158)
Shut down department-heads as an intake path for engineering work - I raised it to product, they will either ask for it or they will not
Aug 28, 2026 · operational
Govern AI spend by notification and trust rather than a cap - alert at a thousand over, and if the person knows what they are doing get out of their way
Aug 24, 2026 · operational
Extend abort-the-loop authority from the hiring manager down to every individual interviewer - anybody can pull the ripcord alone, without a debrief or consensus
Aug 21, 2026 · operational
Move the metrics conversation with Nathan off the tooling and onto the why - which metrics, which were discarded, and how the team is told the reason
Aug 21, 2026 · operational
Restate every RESF request as a request to CIQ rather than to Nathan - publish the secure-boot ask to all of Linux Engineering so someone else can raise a hand
Aug 21, 2026 · operational
Approve the NVIDIA-supported Fuzzball hackathon at SC - with a Wolford engineer on site a day early and a month of hardware notice from NVIDIA
Aug 19, 2026 · operational
The five-week leader presentations are baseline once, then deltas forever - show me what you changed to move the number, not the same dashboard
Aug 19, 2026 · operational
Bake the confidence number on the scope in front of you today - and accept that a 90 percent can slip when scope changes
Aug 19, 2026 · operational
Refuse to act on the AI spend number until it is decomposed - one-time hardware out, recurring API in - then treat the remainder as usage discipline rather than a spend cap
Aug 19, 2026 · operational
Decline the DGX Spark allocation for now - a queue exists, Peter owns it, and the next batch is gated on CIQ showing Nvidia progress first
Aug 18, 2026 · operational
Require every five-week org review to show the delta against the prior review and what was done to move it - not a fresh static report
Aug 13, 2026 · operational
Refuse to start the incident-response conversation from the premise that an on-call system is needed - require an SLA first, and put accepting overnight downtime on the table as a real option
Aug 13, 2026 · operational
Force the stalled GB200 order to move the same day with time, not dollars, named as the governing constraint - and pre-absorb the over-utilisation complaint
Aug 11, 2026 · operational
Ratify sales engineers owning first-pass demos as the permanent structure - reframing Chris Wolfords self-reported staffing error as having kickstarted the right thing
Aug 11, 2026 · operational
Declare Jira a system of record and not a venue for process debate - shut the product-prioritization thread and move it into a room
Aug 11, 2026 · operational
Override your own teams stated intent to delete the RL 8.6 source tree, and apologize to Google directly rather than defend the position
Aug 11, 2026 · operational
No engineering team owns C3 - the content is wrong and outdated, so manage it or kill it, and Peter explicitly does not care which
Jul 30, 2026 · operational
The 1:1 tracking spreadsheet becomes Nathans choice - suggest, do not mandate - but whatever replaces it must be measurable and must never go to HR
Jul 30, 2026 · operational
Deliver the code-driven-not-agent-driven rule personally at Fridays AI committee as a single top-down message, because the first attempt did not land
Jul 30, 2026 · operational
No AI-tooling standard, no MCP catalog, not now - show the org how you built it and tell them to go build their own
Jul 30, 2026 · operational
Purchase approvals below a managers own threshold must never route to the CTO - told Nathan to expense it anyway and took the fight to Finance rather than the person executing the policy
Jul 30, 2026 · operational
The value-driver bottom row is the contract, not NGD - approved stripping target dates and confidence from product tickets and pointing them at NGD instead
Jul 30, 2026 · operational
Confidence numbers stay human and per-leader - Brady translates them, Engineering does not remap to his scale
Jul 30, 2026 · operational
Show the half-migrated TPS report to the whole leadership room even though it was not perfect
Jul 29, 2026 · operational
The NGD board never bends to serve the TPS report - the report changes, and pulls from two data sources if it has to
Jul 29, 2026 · operational
Confidence must rise as the target date nears - slide the date early rather than carry a 60 percent to the wire
Jul 29, 2026 · operational
Every org owes its own delivery-performance metric system, and Wolfords dashboard is the deliberate exemplar - used to train the Linux side of the house
Jul 29, 2026 · operational
Re-ruled the two boards from first principles in the room - prioritization vs dates-and-confidence - and told the org to delete any column serving a third purpose
Jul 29, 2026 · operational
I dont know is the right answer - Support does not guess how Oracle does it, and LG questions are an Engineering/Product call not a Support call
Jul 29, 2026 · operational
Team meetups are gated on a defined purpose and a purpose-derived attendee list, not on getting people together
Jul 28, 2026 · operational
Let Brady raise the kernel-team cloud-resource block in Engineering Weekly, with the test being whether Justin agrees there is a problem
Jul 27, 2026 · operational
Make metric design the single biggest ask of Max - 10 auto-reported metrics spanning Justin and Nathan, delivered by Thursday
Jul 27, 2026 · operational
Grant Max standing permission to publish public Spark/Nemotron benchmarks with no pre-approval
Jul 27, 2026 · operational
Codify how engineering answers sales - bugs get fixed, out-of-scope features get a no, and the only next step is Product not re-escalation
Jul 27, 2026 · operational
Approve a single-seat ChatGPT CVE-model trial for Sultan, narrowing Steves small-group ask to one named person
Jul 24, 2026 · operational
Approve the Tim Pepper consulting proposal, then push back on the absence of a standard contracting process rather than hand-roll the SOW
Jul 24, 2026 · operational
Block the AI-cost workstream on complete per-individual measurement before any optimization - so each persons correct plan can be determined
Jul 24, 2026 · operational
Hand mainline TPS report ownership to Ryan pointed at the NGD board; abandon Peters private fork and deprioritize the Linux software-delivery lifecycle doc
Jul 24, 2026 · operational
Narrow the NGD board to cross-company coordination only - not a deliverables tracker and not a complete decomposition of product acceptance criteria
Jul 24, 2026 · operational
Institute a rotating per-team deep dive at the Tuesday staff meeting, anchored on empirically measurable metrics co-designed in the room
Jul 24, 2026 · operational
Codify the Product-Engineering operating model: value drivers are context, product demands date+confidence and owns prioritization
Jul 21, 2026 · operational
Rule the Toyota kernel patch a feature not a bug; no automatic queue jump, escalate through normal priority
Jul 10, 2026 · operational
Willing to pull C3 into engineering, gated on Product confirming it is a priority
Jul 9, 2026 · operational
Restructure the Tuesday staff meeting to org-by-org TPS ownership and un-fork the TPS report to one shared source
Jul 7, 2026 · operational
Mandate Snyk vulnerability-remediation SLA compliance across all engineering teams
Jun 30, 2026 · operational
Engineering owns defining the ask, success criteria, and documentation; CS responds to specific asks
Jun 30, 2026 · operational
TPM charter + one-owner-per-release accountability mandate (problem/solution/owner grid)
Jun 30, 2026 · operational
Repair the mis-framed Engineering All-Hands - hold a PIC/Fuzzball follow-up and proactively notify the slighted PIC team
Jun 18, 2026 · operational
Mandate 24-hour Sev-1 outage auto-escalation to estaff and AE
Jun 17, 2026 · operational
Fix performance-review confirm-receipt acknowledgment — hand-deliver packets now, push HR for global wording change
Jun 16, 2026 · operational
Re-institute and enforce monthly performance conversations across engineering managers
Jun 12, 2026 · operational
Value Drivers Board becomes source of truth for engineering dates and confidence; JPD dates become computed
Jun 4, 2026 · operational
Take on Value Drivers Board restructure as the next coordination lever after JPD doctrine
Jun 1, 2026 · operational
Rippling Jira Asset Mgmt add-on approved — 12mo commit + cancellation push
May 29, 2026 · operational
JPD board scope locked to ordered priority list — Peter drew the line in writing to Nathan
May 28, 2026 · operational
Hardware lab: paint the full picture and buy the whole complement upfront
May 26, 2026 · operational
Sherif RESF hardware: Wallace owns directly — escalation triggered by Greg
May 26, 2026 · operational
Engineering owns docs content; Customer Engineering or Marketing owns customer-ready packaging
May 26, 2026 · operational
Slip Fuzzball V4 date now and drop confidence rather than fight to hit it
May 26, 2026 · operational
Rippling Asset Mgmt — time over cost; pay full $18k for end-of-June over $15k for December
May 21, 2026 · operational
Moody Citibank card hard cutoff 6/15 — force-action via past-tense framing after 9 months of soft asks
May 21, 2026 · operational
Discretionary bounty offered for Yeshs vulnerability disclosure — case-by-case mode, no formal program
May 21, 2026 · operational
Lab hardware acquisition shift — buy all 8-10 servers at once, Texas DC over Reno, NVIDIA+AMD outreach
May 21, 2026 · operational
Engineering owns all QA — Nathan accountable; tests required for Done; Ryans team builds tooling not rescue
May 21, 2026 · operational
Jira confidence-as-contract doctrine codified across engineering directs
May 21, 2026 · operational
No bugs, only change requests — structural reframe for product/engineering interaction
May 19, 2026 · operational
Engineering QBR format — collaborative discussion with three topics, not a presentation
May 13, 2026 · operational
Eliminate one-off release processes — paved-paths Jira initiative Peter commits to prioritize
May 7, 2026 · operational
Add Justin to Binarly meeting; debrief AFTER, not before
May 5, 2026 · operational
Peter delivers Reno QBR C-suite intro Thursday — covering Bjorn late arrival
May 5, 2026 · operational
Three-tier board hierarchy formalized — Strategic EPICs / Value Drivers / Tactical Jira
May 5, 2026 · operational
Mariah escalates Stephen Moody project delays directly to Peter (bypass Wallace)
May 4, 2026 · operational
PPL is being misused — push Bjorn to realign it to strategic priorities
May 4, 2026 · operational
Documentation process — Product defines exit criteria in Jira, Engineering delivers
May 4, 2026 · operational
Tighten Jira-as-system-of-record into active enforcement — instruct teams to ignore Slack-only requests
May 1, 2026 · operational
Ryan Smith owns docs.ciq.com
May 1, 2026 · operational
Empower Nathan to defer Hassan secure-boot working session if engineering not ready
Apr 29, 2026 · operational
Fuzzball PoC ownership belongs to Sales Engineering, supported by Engineering
Apr 27, 2026 · operational
Block Max's calendar — don't schedule anything for the time being
Apr 18, 2026 · operational
Quality initiatives must be ticketed visible work, prioritized by Product
Apr 18, 2026 · operational
Approved ISO 42001 AI User profile addendum (~$30k)
Apr 17, 2026 · operational
Delivered Jira Hygiene Mandate to Engineering
Apr 17, 2026 · operational
Committed CIQ Engineering Resources to Unblock RESF
Apr 15, 2026 · operational
Delivered Jira Hygiene Mandate to Engineering
Apr 15, 2026 · operational
Committed to engineering date hygiene confrontation with directs
Apr 14, 2026 · operational
Directed RESF/Dieter justification effort for board meeting
Apr 14, 2026 · operational
Escalated Engineering Estimation Accountability — 58% Miss Rate
Apr 11, 2026 · operational
Reinforced Product Owns Exit Criteria — Engineering Cannot Unilaterally Remove Requirements
Apr 11, 2026 · operational
Reinforced Product Ownership of Exit Criteria
Apr 10, 2026 · operational
Google NEXT - Value-First Attendance Framework for Nathan
Apr 9, 2026 · operational
Committed to Improve Team Bandwidth Visibility in Monday Meeting
Apr 7, 2026 · operational
CentOS Bridge Deprioritization Held Despite Customer Risk
Apr 7, 2026 · operational
Set April Engineering Delivery Miss Target at 3-6 Items
Apr 7, 2026 · operational
RESF JIRA Date Reset for Realistic Expectations
Apr 4, 2026 · operational
AI/Data Security Audit Commitment to Greg
Apr 4, 2026 · operational
Open Source Repo Release Process — Testing Greg's Boundary
Mar 30, 2026 · operational
Accepted CLK 6.18 delay to March 31
Mar 25, 2026 · operational
Saudi training — Confirmed Dieter for May 5-6 Linux training program
Mar 24, 2026 · operational
RESF — Orchestrated demand-pull approach for CIQ help
Mar 24, 2026 · operational
Start Skip-Level 1:1s Next Week — 30 Min, 1-2 Per Week
Mar 21, 2026 · operational
Shared Mini-Me Source Code to Internal Org
Mar 18, 2026 · operational
RESF Communication & Information Control Strategy
Mar 18, 2026 · operational
Reaffirmed Speed-First Culture to Brady Before Leave
Mar 13, 2026 · operational
RESF Internal Comms — Slack Post Not AMA
Mar 13, 2026 · operational
RESF Monday Cutover — Finalized 3 PM PT Execution Plan
Mar 13, 2026 · operational
RESF Impact — Consolidated Marketing Alignment Meeting
Mar 11, 2026 · operational
Enforcing Product Process for Greg's RLCAI Requirements
Mar 11, 2026 · operational
Coordinated Google Post-Mortem Alignment Between Nathan and Bjorn
Mar 11, 2026 · operational
Claude Government Use — Restrict Shipping, Internal Use Fine
Mar 10, 2026 · operational
TPS Report Visibility — Expand Justin's Reporting Scope
Mar 10, 2026 · operational
Custom Engineering Scoping Process — Nathan as Gate
Mar 6, 2026 · operational
Push for Continuous Sales/Support Enablement
Mar 4, 2026 · operational
Directed March engineering priorities to come from Bjorn (Product)
Mar 3, 2026 · operational
Set maximum urgency on LTS 9.6 i686 package crisis
Mar 3, 2026 · operational
Committed to RESF day-of execution planning meeting next week
Feb 27, 2026 · operational
Release artifact ownership assignment - Nathan RPMs, Justin images
Feb 26, 2026 · operational
Mandated Engineering double delivery pace in 6 months
Feb 25, 2026 · operational
Commit to benchmark accuracy sign-off by tomorrow
Feb 20, 2026 · operational
Demanded proper advance coordination for customer meetings involving engineering
Feb 20, 2026 · operational
Set Google GDC meeting strategy: build direct relationship and manage attendee roles
Feb 17, 2026 · operational
Accepted priority churn during RLC Pro/Plus pivot
Feb 12, 2026 · operational
Leveraged TPS report visibility to drive accountability with Justin
Feb 12, 2026 · operational
Demanded war-room or date ranges for RLC Pro release dates
Feb 11, 2026 · operational
Shared Mini-Me delegate access with Bjorn for collaborative todo management
Feb 8, 2026 · operational
Delegated week's priorities to Nathan and Justin via detailed handoff email before Dubai trip
Feb 8, 2026 · operational
Established 'what vs how' framework for Product-Engineering communication
Feb 8, 2026 · operational
Enforced Product-owns-prioritization process with Greg
Feb 6, 2026 · operational
Shared AI development velocity guidance with Max
Feb 2, 2026 · operational
Protected Max from meetings for NARF focus
Feb 2, 2026 · operational
PRD first drafts are gravel - meant to be thrown away
Jan 30, 2026 · operational
Stop coaching product, move to SLAs
Jan 30, 2026 · operational
RESF crisis comms - single source of truth
Jan 30, 2026 · operational
Trustless processes over building trust
Jan 30, 2026 · operational
PRD contract process - stop teaching product
Jan 30, 2026 · operational
AI ownership standard - own everything you submit
Jan 30, 2026 · operational
WBR restructuring to outcome-based commitments
Jan 30, 2026 · operational
Leadership meeting cadence - need-based, not scheduled
Jan 30, 2026 · operational
Reinforced Product-Engineering handoff process with tighter SLAs
Jan 28, 2026 · operational
Empowered Justin to own RLC 9.7/9.6 LTS ship criteria
Jan 26, 2026 · operational
Transfer Depot operations from Justin team to Steve team
Jan 23, 2026 · operational
Empower Justin to own RLC 9.7/9.6 LTS ship criteria
Jan 23, 2026 · operational
Established escalation protocol for Product blockers
Jan 23, 2026 · operational
Redirected Brady to use prioritization tools instead of pushing hard
Jan 22, 2026 · operational
Estimation philosophy: move dates early, hold them late
Jan 19, 2026 · operational
COGS Visibility - Escalate Finance Data Access via Bjorn
Jan 15, 2026 · operational
Work intake must flow through managers, not directly to engineers
Jan 14, 2026 · operational
Marketing ICP Validation - Collaborative Research Approach
Jan 12, 2026 · operational
H1 Planning Framework - 3-Lane Model
Jan 12, 2026 · operational
Commitment to Present Engineering-to-GTM Messaging Framework
Jan 2, 2026 · operational
Build Culture That Moves With Ambiguity
Dec 31, 2025 · operational
Bounty Program Design: Open Incentives Over Prescribed Work
Dec 31, 2025 · operational
NARF Monday Deadline Set
Dec 31, 2025 · operational
Product-Engineering Quick Estimation Process
Dec 29, 2025 · operational
NARF Launch as Forcing Function
Dec 29, 2025 · operational
Engineering Blockers - Immediate Escalation Required
Dec 24, 2025 · operational
ProServe Work Prioritization Process
Dec 24, 2025 · operational
Championing AI Butler Adoption Internally
Dec 19, 2025 · operational
Championing AI Butler Internal Adoption
Dec 19, 2025 · operational
Pattern ID: e7c993cd-8991-40a3-b519-b0ae42adaeac