Sultan Alsawaf
Apr 9, 2026 - Oct 1, 2026
6
Decisions
0
Active Todos
13
Patterns
Categories
Decisions (6)
Open-source Sultan diffofdiffs under Apache - routed through Greg open-source gate even though the answer was obvious
When Nathan flagged that Sultan wanted to make the internal diffofdiffs repo public, Peter posted in #distinguished-leaders that Greg wanted to be part of the decision any time anything CIQ was open sourced; this is slightly different (a tool Sultan wrote, used internally), Peter is a giant fan, but wanted Greg plugged in. Greg approved on condition of an Apache license, which Peter relayed to Nathan.
Vera Rubin to Google - commit to a bounded duration (at most 3 weeks after node access), not a date, and invite Google to supply its own hardware
Replying to Tissa request for Vera Rubin timelines, Peter wrote that NVIDIA has committed lab time but cannot confirm when; once CIQ has a node it needs at most 3 weeks to validate Rocky, ensure full functionality and performance, and fix issues; CIQ will update as soon as it has visibility; and if Google has a node it could provide, CIQ would happily do the 3 weeks on that instead.
Everyone owns their AI spend - no gates or guardrails, but unaware spending is unacceptable
At the AI Committee, the spend dashboard showed Jamin at roughly 33-39k for September. Peter said he will not put gates or guardrails on AI usage, but every person at the company (not just engineers) must know their own spend, the caps and overage thresholds of the tools they use, and treat token spend as part of their cost to the company. A deliberate, informed overage is backed even if Peter would disagree with the math; blind spending is not. Michelle was approved to tell the whole company this is on each person. Ryan 1k overage notification line accepted as reasonable; only Jamin, Sultan and Justin warrant an actual conversation.
Vera Rubin access is drop-everything, the goal is proving it works for Google rather than benchmarks, and kernel pre-work starts now
NVIDIA is working to give CIQ a short window (likely about 5 days, one node) on Vera Rubin hardware, with no advance notice of when it opens. Peter set three things: when the window opens, whoever is involved drops all other work; the goal is getting Rocky/RLC working so CIQ can tell Google it works, not benchmarking; and Sultan starts pre-work now (patch identification, test branch) so the window is productive.
Hire Hailey Mothershead without reservation, and take John Paul as a qualified yes with a standing instruction not to chase him if he declines
At the Aug 12 kernel round table Peter gave two very different verdicts. On Hailey he was unreserved - I would hire her today, I thought she was smart, I thought she was inquisitive, I think she will work incredibly well with the team - and said that at a smaller company he would have called Brianne right after the interview and not let her leave the building without papers in front of her. He named his one real concern, a complete lack of C experience, and dismissed it as learnable, and flagged that she will find CIQ feedback culture blunt. On John Paul he deferred entirely to the technical panel, said he did not enjoy the interactions, did not believe JP is interested in what CIQ is doing, agreed with Shreeya read that they are getting roughly a year, and said he would not block a consensus yes. He then added the operative instruction: if we make an offer to him and he does not accept, let us not kill ourselves to make it work out. He closed the meeting with I know this team has felt pressured. I do not want this pressure to bring in the wrong person.
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.
Related Patterns (13)
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.
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.
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.
Purpose Is the Decision Procedure
When someone asks how a process, board, tool or artifact should handle their specific case, Peter refuses to answer on the askers terms. He re-derives the answer from what the artifact is for, states that purpose as the only decision procedure, and lets the answer fall out. Anything found to be serving a second purpose is deleted rather than debated. Tools and views are explicitly subordinate to definitions. He will accept that the askers real problem is simply not solved by this artifact rather than widen the artifact to cover it.
Demonstrate the Standard, Then Collect It
When a new leadership expectation has to land across multiple orgs, Peter does not write a spec. He runs a live exemplar in public with the strongest performer first, says openly that the ordering was deliberate, keeps the form of the deliverable open so the ask stays about the thinking rather than the artifact, lets the delta be self-evident to the people who will have to close it, and then collects the same from everyone else on a named rotation. He prefers showing imperfect work now over polished work later.
Decide on the Precedent, Not the Case
When a request arrives framed as a one-off, Peter does not evaluate the one-off. He evaluates the rule that granting it would write, and answers that instead. Peter generalized this himself on 2026-08-11: it is always about understanding precedent - whether it is a comp change or anything that structurally affects the company. It is therefore NOT a compensation pattern; the domain of the presenting request is incidental. The tell that this pattern is live is that the stated reason for the answer refers to future cases rather than to the merits of the present one.
Switch Instrument, Not Intensity
Applies when a message, rule or ask has already failed through the channel Peter is currently using - repeated advocacy that has not landed, coaching that produced defensiveness rather than improvement, exhortation that did not change behaviour, or a rule that keeps losing case by case. His response is never to restate the same thing more forcefully. He changes the instrument and usually names the switch out loud. Mined from 7 independent observations between 2026-01-06 and 2026-08-21.
Time Over Cost
Peter treats elapsed time as the scarce quantity and money as the abundant one, and will spend cash to buy schedule, clarity or optionality. Notable because he named it himself as a transferable principle on 2026-05-21 and coached the lens explicitly to a direct report, which is rare - most of his patterns are inferred rather than stated. It generalises past procurement: he will pay to convert an ambiguous dispute into a binary one, remove cost as a variable entirely when a priority has executive visibility, and reason about a commitment in terms of lead time rather than budget. Mined from 5 independent observations between 2026-02-01 and 2026-09-11.
Promise Only What Is Inside CIQ Control
Applies when someone asks CIQ to commit to an outcome whose delivery depends partly on something CIQ does not own - a lead time, a third-party publisher, a customer-provided environment, an unsigned contract. Peter does not accept or refuse the request as posed. He isolates the specific component that sits outside CIQ delivery chain, refuses that component by name, and substitutes an adjacent commitment CIQ can actually keep - then often adds a harder problem worth solving in its place, so the counterparty gets more engagement rather than less.
Measure, Commit Publicly, Then Execute
A three-beat escalation arc Peter runs when he needs a commitment from a peer or the CEO that private pressure has not produced. Beat one: measure the thing and get a number. Beat two: state the commitment in a venue where the people who matter are watching. Beat three: execute against it. The 2026-04-15 observation names the sequence explicitly and notes he does not skip steps, because each beat builds the legitimacy of the next. The venue choice is treated as a decision in its own right, separate from what the message says. Mined from 8 independent observations between 2025-12-29 and 2026-08-28. NOTE: scope this to the venue-and-sequence mechanism specifically - forcing function is a phrase that appears loosely across many unrelated decisions and should not be taken as a match on its own.
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.
Conscious Tech Debt for Execution Speed
When facing time pressure, explicitly acknowledge and accept technical debt rather than blocking progress. The key is making the trade-off consciously and visibly so it can be addressed later.