Lead by Example with New Tools
57
Occurrences
52%
Success Rate
3.7
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: March 13, 2026
Created: December 28, 2025
Example Decisions (56)
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