Ian
Jan 28, 2026 - Sep 11, 2026
4
Decisions
0
Active Todos
4
Patterns
Categories
Decisions (4)
Require archival and backup for anything in the Mother Brain warehouse that is not reconstructable from source
While Karl demoed the customer-journey view built on the data warehouse - 15 million events and growing, hosted on GCP - Peter asked how much of it is reconstructable if it is all destroyed. Karl said everything should be recreatable. Peter said he expects that is true and kept the instruction anyway: when Ian is slotted under Wallace, have Ian run archival and backup against anything that is not recreatable. He explicitly excused Karl from doing the work himself.
Proactive Retention Check-ins After Ian's Departure
Initiated proactive 1:1 check-ins with key staff to gauge morale and prevent surprise resignations after Ian's departure. In the Sultan check-in, clarified Michael Young's departure was performance-based, explained no company-wide announcement (no teachable moment), and affirmed Sultan's role is safe. Goal: replace underperformers with A players.
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.
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.
Related Patterns (4)
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.
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.
Constrain the Mechanism, Not the Access
When AI or automation raises a governance concern, Peter does not restrict who or what may reach the data. He constrains HOW the reach happens, so the pathway becomes auditable and deterministic. The failure mode he designs against is non-determinism, not leakage - a wrong filter in inspectable static code is a bug you fix once, while a model that sometimes pulls the wrong field is an unbounded, unauditable liability. He will therefore accept imperfect filtering and eventual leakage as the price of adoption speed, but will not accept a non-inspectable pathway.