Sarah Almaraz
Dec 19, 2025 - Nov 9, 2026
34
Decisions
0
Active Todos
22
Patterns
Decisions (34)
RESF and OpenELA asks are real work - the answer is yes, it goes to your manager and into Jira at high priority, and refusals escalate to Peter
At the Reno onsite Peter told the whole Linux org that when Lee or Jonathan Dieter asks for help with the RESF the answer is yes: tell your manager, get it into Jira, treat it as real work and prioritize it super high. On 11/5 Arthur Tyde described OpenELA as unsupported and himself burning out; Peter applied the same rule to Arthur asks and gave him an escalation path - if anyone says they are too busy, bring it to Peter and make it his problem. Peter committed to talk to Lee about OpenELA from his own perspective, to keep dialing into OpenELA calls, and asked Sarah for an ongoing biweekly meeting with Dieter.
Sensitive Decision
Sensitive Decision
Sensitive Decision
Clear Wolfgang for the UAE, cut the on-site window to week one, and hand the final pick to Wolford
Following the 9/16 decision to put a technical body on the ground in the UAE, Peter closed out the open questions in three moves across two days. He talked to Wolfgang, who wants to go. He asked Adam Jackson directly whether a German national can be sent and got a yes the same morning. He told Bjorn in the C-Suite Sync that he does not think the engineer needs to be there for the entire deployment - just the first week or so, when we are going to need to push a button. Then, when Chris Wolford raised Randy as an alternative, Peter said he is fine with it being Randy, that he does not mind, that it is 100 percent Wolford call, and attached the only real constraint: if it is Randy, tell Adam now so the security paperwork starts now for whoever is chosen.
Sensitive Decision
Cover the OpenELA TSC seat gap personally with Nathan and Leigh, and put Tim Pepper on the RESF relationship question
Sarah Almaraz relayed Arthur Tyde concern in #ea-team that CIQ holds two OpenELA TSC seats assigned to Nathan Blackham and Damen Knight, neither had been participating, and SUSE and Oracle were showing up consistently while CIQ as a founding member was not represented. Arthur asked for three things before the Sept 10 call: confirm Nathan and Damen or name replacements, get a PR submitted for OpenELA issue 36 with confirmed prod access, and name one CIQ engineer to own the import queue. Peter answered with the attendance roster - Myself, Nathan, and Leigh. Separately in the window he told Nathan he has Tim Pepper on as a contractor to look at CIQ relationship with the RESF and how CIQ grows community there, described the role as an OSPO advisor sort of guy here on a contract, asked Nathan for pointers to docs on unifying build infrastructure, and told Nathan to talk to Tim about the structure of his team, how he interfaces with the RESF, and how he wants to evolve that interface. Peter also forwarded Arthur OpenELA TSC threads to Tim Pepper directly.
Ask Greg to take Peter off the RESF directive so it reads as CEO-to-RESF instead of CEO-correcting-his-CTO - and pair it with a standing Lee status cadence
In the 2026-08-18 C-Suite Sync, Greg proposed DMing Peter, Dieter, Lee and possibly Brian to reiterate that more CIQ people need to be involved and that things need to move faster on the RESF side. Peter agreed to the substance but asked to be removed from the recipient list: So yes, but play this game with me. I think if you send that DM to the list of people you said, which includes me, and now I ask myself how I can perceive that from Brian perspective. I can perceive it as Greg telling his employee, Peter, to involve more people, and you are just notifying Brian that Peter has been told. If I am not on the email, and it is just going to Brian and Lee and Dieter, do you see what I am saying? I think you can speak really differently. He asked instead for a copy sent separately - I would just send it directly to them and then send me a copy of it just so I know exactly what you said - and suggested Greg tell them he expects Peter to be receptive to anything they ask. Separately Peter asked Greg to secure a standing status cadence with Lee, explaining that Lee is the one with the broad overview but does not work for Peter in this capacity, whereas Dieter will supply status on request. Greg agreed to have Sarah set up a weekly or biweekly Peter-Lee meeting, and Peter accepted.
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
Sarah Almaraz relayed a request for a DGX Spark unit for Brian on 2026-08-15. Peter refused flatly and gave the conditions that would change the answer: You cannot. When Nvidia has more to give us I can put Brian on the list. But there are other people first. And we need to show some progress to Nvidia first. Realistically it is going to be a few more weeks before we might get more. He closed by taking the explanation upward himself - I will walk Bjorn through it though.
Run a Monday state-of-the-Linux storytelling session on pipeline, and have Baek carry the same rah-rah into the all-hands
Acting on a morale signal that surfaced in Gregs round of one-on-ones, Peter committed to sitting down with the Linux org on Monday to walk them through what he is seeing in the Middle East and with Google. He framed it explicitly as storytelling and cheerleader rah-rah about why he feels so bullish, not as a status update, and asked Chris Baek to sprinkle a little bit of the same into the upcoming company all-hands. He gave the diagnosis comparatively - the Linux org is meh on our future while Fuzzball is gangbusters and Ryans org is gangbusters, and there is no reason for Linux to be less positive about our future than everybody else - and bounded the response with it is not a risk right now. Sarah had already blocked Monday for the session.
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
Peter restructured the 7/28 Engineering Weekly into a fast breadth-first TPS pass followed by a single-org deep dive, and made Wolford go first on purpose. After Wolford walked through his PIC tooling - PR review latency, time-to-merge, bug-vs-feature ratio, commit distribution, release cadence, internal and external documentation coverage, plus a per-quarter epic assignment board - Peter named the ask explicitly: I dont care whether there is a dashboard or just a system that reports a set of metrics, but this is the kind of thing I am going to be looking for from every org. It is not an accident that Wolfords going first here. He then propagated the exemplar three ways: forwarded the Fathom recap to Bjorn saying he was using it to help train the Linux side of the house, told Nathan to watch the recording because there are critical things in there that will impact your teams and that I want to be able to talk through in terms of team management, and told Wolford directly that the presentation was exactly what I wanted/needed to kick that all off - while warning him you will not be impressed when Linux and the other portions of eng deliver theirs. Sarah set the rotation: Wolford, then Nathan, then Steve, Ryan and Justin.
Bring Ryan to SKO (Aug 19-21, LA) - make the ask on his behalf and let him choose his own duration
In the 7/23 Ryan 1:1 Peter learned nobody had asked Ryan about the sales kickoff. He decided support should be represented, said he would take it to Chris Baek himself, and explicitly refused to dictate how long Ryan should attend - I am going to turn it around, I am going to support whatever you want. He called Baek the same evening and confirmed back to Ryan an hour later that Baek was on board. Peter himself attends only Thursday the 20th.
Approve the Tim Pepper consulting proposal, then push back on the absence of a standard contracting process rather than hand-roll the SOW
Greg forwarded Tim Peppers consulting proposal to Peter on 7/21 with apologies for the latency, and Peter approved it flatly the same afternoon - I am good with this - without asking cost, scope, or management in the thread. He forwarded it to Sarah on 7/23 to get it moving. On 7/24 when Sarah relayed that Gregs next step was for Peter to follow through with the contract, Peter declined to hand-roll it and asked where the standard process was. Sarahs answer confirmed there is not a reliable one - CIQ has done things fast and not by the book with other people, case by case - and she took an action to check with HR.
Institute a rotating per-team deep dive at the Tuesday staff meeting, anchored on empirically measurable metrics co-designed in the room
Peter gave the same instruction independently to Chris Wolford and Steve Wallace on 7/23. Each org lead will take roughly 45 minutes of the Tuesday staff meeting on a five-week rotation. Three parts: a functional overview or demo of what the team delivered in the last month and is working on next; a project-plan view with milestones, tracking, who is on what, and how team time is being spent; and a set of empirically measurable metrics. The metrics do not have to be right the first time - the explicit purpose of doing it in front of peers is to argue out which metrics are the correct ones for each org. Metrics differ by domain: on the Linux side Peter wants automation measures such as the percentage of PRs auto-approved by Nerf versus human-approved; on PIC Chris proposed PR volume and the rate at which releases require bug fixes over time. Chris Wolford presents first, Tuesday.
Repair the mis-framed Engineering All-Hands - hold a PIC/Fuzzball follow-up and proactively notify the slighted PIC team
After Jonathan Anderson and others read the recent State of Linux session as the Engineering All-Hands - leaving the PIC team feeling ignored - Peter diagnosed it as a framing/naming failure (Linux-only, Wolford not on it, no Fuzzball content) and directed the fix: a PIC/Fuzzball-focused follow-up session in the next few weeks, Baek to own the Fuzzball angle, and the PIC team to be told now that it is coming because yesterday was bad for them - they felt completely ignored.
Add Justin to Binarly meeting; debrief AFTER, not before
Peter added Justin Haynes to tomorrow Binarly meeting to ensure engineering representation. Explicit decision to debrief Justin AFTER the meeting rather than pre-coaching him beforehand.
Peter delivers Reno QBR C-suite intro Thursday — covering Bjorn late arrival
Peter will deliver the C-suite intro at Reno QBR Thursday morning, since Bjorn arrives Thursday afternoon. Peter arrives 8:45 AM Thursday. Greg travels to Houston with Adam for a 1 PM Thursday sales meeting.
Manage Max situation — protect privacy, halt org outreach, decline his calendar
Peter is actively shielding Max Spevack from organizational pressure during a personal/private situation. Directed Sarah to access Max's calendar and decline all his meetings for the week, told Ryan to stand down ("No reaching out"), told Nathan to stand down ("worst thing Ryan can do is involve himself"), declined Mariah's offer to use Max's emergency contact ("let's give it a little more time"). Committed to talk with Max himself early this week.
Block Max's calendar — don't schedule anything for the time being
In a DM (4/17 11:10 AM Pacific), Peter directed Sarah (assistant) to stop scheduling anything for Max Spevack for the time being. This operationalizes the indefinite-leave posture triggered by Christina's 4/16 7:45 PM call telling Peter that Max needs time away. Rather than letting Max's calendar keep generating missed-meeting signals to the org (like the 4/16 1:1 and interview no-shows), Peter chose to block new scheduling entirely until further notice.
Sensitive Decision
Start Skip-Level 1:1s Next Week — 30 Min, 1-2 Per Week
Approved starting skip-level 1:1s with 12 key engineering ICs (Dieter, Maple, Skip, Jeremy, Andrew, Sultan, Alex, Mustafa, Joseph, Zorina, Giovani, Rahul). 30 minutes each, 1-2 per week, random order. Sarah to schedule.
Prioritize Google Exec Meeting — Adjust Reno Travel
Agreed to meet a confidential new Google executive (distinguished engineer from Google Cloud, came through Tissa) for Monday dinner or Thursday lunch. Thursday option requires returning from Reno Wednesday night. Directed Greg to cover Toyota in person on Wednesday if needed.
Committed to RESF day-of execution planning meeting next week
Committed in #internal-resf-escalation to organizing a meeting next week to build an execution plan for the RESF day-of lockdown. Directed Sarah to invite Nathan, Max, Justin, and Dieter. Bjorn is finishing messaging drafts this weekend, so technical execution planning must be ready to match the communication track.
Pushed for March ARR review, rejected April as too late
Directed Sarah and Greg to schedule an ARR targets review meeting in March, pushing back on an April date as too late. Wants to ensure the company is on track for revenue targets and can pivot anything needed. Offered personal availability and said format doesn't matter.
Shared Mini-Me delegate access with Bjorn for collaborative todo management
Gave Bjorn delegate access to Mini-Me web app so he can see Peter's todo list, enabling collaborative work on shared priorities during Dubai travel week. Walked him through the limited view and how it works. Also instructed Bjorn to have Sarah coordinate with Moody for Google/Slack permissions setup for a new person.
Value Drivers document cannot be automated from Jira - fills a gap Jira lacks
Clarified that the Value Drivers Release Plan document cannot be automated from Jira. The document was created specifically to fill a gap in Jira - linking engineering deliverables to GTM deliverables around WHY certain work is being done. Since Jira does not contain this linkage data, automating from Jira would just reproduce the gap.
NVIDIA partnership scope agreed - CIQ Rocky Linux for NVIDIA AI at GTC
Agreed with Scott Hara on NVIDIA partnership deliverable: CIQ will deliver a free CIQ Rocky Linux for NVIDIA AI (with AI patches + NVIDIA drivers) for GTC showcase in ~8 weeks. No requirement to upstream to community Rocky short-term. Support cadence: 1-2h kickoff Q&A, then 3 weekly 1h sessions, then ad hoc. CIQ maintains distro with minimal NVIDIA intervention; NVIDIA supplies patches, system access, and optimization guidance.
Estimation philosophy: move dates early, hold them late
Project dates should be moved when new information is learned, rather than just dropping confidence when dates pass. Early SWAG dates should be updated once actual scoping begins. Red patterns in dashboards reflect engineers being trained not to move goalposts - this needs to change.
All-Hands messaging: acknowledge Q4 miss, pivot to pipeline optimism
Aligned with leadership on All-Hands messaging strategy: directly acknowledge Q4 revenue miss, then pivot to optimistic outlook highlighting $22M H1 pipeline and unified GTM plan. Peter to present tech updates (service endpoints, Nerf) and guide Mural board walkthrough. No naming specific deals to avoid premature expectations.
Ali Contract Termination Executed
Sent termination email to Ali Erdinç Köroğlu on Jan 5 after missed Dec 31 sync meeting and other missed meetings. Coordinated with Mariah (HR) and Sarah to cancel calendar invites and deactivate systems.
Friday Layoff List Finalized
Finalized the layoff list for Friday Jan 9: Eli, Derek, Chris Short, Craig, and Trinity. Jason deferred due to ISO certification needs.
AI Bot Architecture Decision
Decided to build a web app to front the AI bot, allowing curated outputs to be shared with Sarah and others without granting direct data access to underlying Slack/email/Jira data.
RLC 9.7 Launch Path Decision
Participated in RLC 9.7 Launch planning meeting to decide path forward on release and rework priorities.
Championing AI Butler Internal Adoption
Hosted and recorded the AI Dashboard/Butler setup session to drive internal adoption of Claude-based personal productivity tools across CIQ. Shared personal use case of creating meeting prep notes from Slack/email/docs.
Related Patterns (22)
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.
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.
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.
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.
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.
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.
Reclassify to Route - Decide Who Owns It, Then Give a Criterion Not a Verdict
When a question arrives at Peter framed in one domain, he often does not answer it in that framing. He reclassifies it into the domain that actually governs the outcome, which relocates ownership to whoever owns that lane, and then hands down a decision criterion rather than a verdict. The reclassification IS the decision - it determines who decides. He does this rather than adjudicating on the merits himself, even when he was explicitly cc-ed and even when a direct report challenges him on the substance.
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.
Route Non-Differentiating FTE Classes to Partners
When CIQ would otherwise need to staff a function whose work does not differentiate the company — compliance bureaucracy, audit/cert paperwork, ongoing regulatory attestation, etc. — Peter routes the load to a partner who already owns adjacent capability rather than adding the FTE class internally. Org-shape decision dressed as a partnership decision.
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.
Redesign Conditions Over Policing Symptoms
When a direct report names a vulnerability and proposes surveillance-style verification mechanisms (breathalyzers, daily check-ins, monitoring rituals), Peter accepts the disclosure but pushes back on the surveillance model. Treats the verification proposal as a signal that the underlying environment needs redesign — and offers to change the conditions that produced the vulnerability rather than instrument the symptom. Costs Peter optionality (e.g., committing to broker work-hour expectations directly with the partner/spouse) — the asymmetry signals genuine retention vs transactional.
Metrics Must Follow Strategy
When shifting team priorities or strategic direction, the communication alone will not drive behavior change. Engineers may acknowledge the new direction but continue existing behavior patterns without clear, explicit metrics holding them accountable.
Name It Without Staffing It
Applies when a structural change is directionally clear but the specific person, budget or reporting line is not settled. Peter names the structure - the role, the reorg, the governance reform, the ladder - and deliberately does not attach a name, a req or a commitment to it. The 2026-05-21 observation states the economics plainly: cost of naming is near-zero, cost of premature commitment is high, and he consistently chooses naming. The 2026-08-24 observation adds the sequencing reason: once a specific person is attached to a framework, the framework stops being the subject. Mined from 6 independent observations between 2026-01-12 and 2026-08-24.
Different Diagnosis, Different Remedy
Applies when a directive or a problem spans several people or cases that superficially look alike. Peter refuses a uniform answer and sorts by diagnosis first, then applies the remedy that diagnosis calls for. The 2026-08-28 observation states the consequence for recording his decisions: when he gives a directive spanning several cases, the decision is almost never any single remedy - it is the rule that produces DIFFERENT remedies, and four cases with four different answers under one rule means the rule is the decision. The 2026-04-17 observation confirms he holds this as an explicit framework rather than an instinct. Related to Three-Lever Talent Management but distinct: that pattern runs hire, develop and exit in parallel, this one is about diagnosis determining which lever a given case gets. Mined from 6 independent observations between 2026-02-03 and 2026-08-28.
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.
Pragmatic Technical Middle Ground
When facing competing concerns (security vs innovation, access vs protection), find technical solutions that satisfy multiple stakeholders rather than debating policy or picking sides.