Wesley
Dec 31, 2025 - May 27, 2026
5
Decisions
0
Active Todos
8
Patterns
Categories
Decisions (5)
Peter Computex condition: product must be production-ready, not a POC
For the proposed early-June Computex Fuzzball-on-DGX-Spark announcement, Peter set one engineering-side condition: the product must be production-ready (not just a POC). Bjorn separately set the GTM-cadence gates (max 6-week lag between announcement and delivery; sufficient PR-runway for Lindsay and Cathay). Peter held the engineering line cleanly and let Bjorn hold the product-marketing line.
Ascender ownership moves to Nathan org with possible Zarina-led sister team
Peter decided Ascender does not stay parked between Jimmy and Larry as a half-supported side-project — it needs a real owner. Not adding a direct report to Peter; not adding to Justin who is at his limit. Lands in Nathans org. Possible structure: a sister group under Nathan (parallel to Justins org) for customer-facing delivery — would hold externally-facing Depot AND Ascender, led by Zarina, with one new engineer hired in for Ascender work. Decision contingent on Zarinas current Depot-Sodor commitment and the Wesley situation resolving.
Ascender consolidates under Nathan; opened customer-facing-delivery org reorg as a future possibility
The new Ascender application engineer hire (JD finalized 5/14, panel kickoff 5/20) will report to Nathan, not Justin. Reasoning: Nathans team has the necessary ecosystem breadth (OS + Depot + Ledger); Justins team is at capacity with narrower focus. Beyond the immediate staffing call, Peter opened a much larger structural question with Nathan: whether the engineering org should split along a new axis — a customer-facing-delivery group containing Ascender today, future external Depot, and other delivered-products — potentially led by Zarina. Wesleys uncertain future at CIQ surfaces as a blocker to firing that lever.
Sensitive Decision
Bounty Program Design: Open Incentives Over Prescribed Work
Established that bounties at CIQ should be open to all engineers, not targeted at specific individuals. Rejected Bjorn approach of incentivizing Jesus and Alex specifically to work over holidays on Portal. Bounties should be available for anyone to claim if they want to accelerate delivery.
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.
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.