Mariah Rippee
Dec 24, 2025 - Sep 7, 2026
58
Decisions
0
Active Todos
14
Patterns
Decisions (58)
Sensitive Decision
Sensitive Decision
Sensitive Decision
Sensitive Decision
Sensitive Decision
Trade a company-wide VP definition to get Greg to ratify the engineering ladder - structure first, names later
In the Aug 24 1:1, Peter walked Greg through the engineering leveling spreadsheet. He deliberately separated ratifying the STRUCTURE from mapping the PEOPLE, saying he wanted Greg bought into the structure and cared much less about the mapping for now. The ladder collapses roughly 27 levels to four IC levels - Engineer, Senior, Principal, Distinguished - plus Technical Fellow retained as a title outside the ladder rather than a level, and leadership reporting to Peter as either VP or Director with no Senior anythings. Greg objected to VP on optics grounds. Peter did not defend the word, he defended the need: I wanted a senior leader and a junior leader title, what we call them I am far less interested in. The two then jointly settled a company-wide convention: VP spans organizations and reports to a C-suite, SVP means junior C-suite where no CXO title is being given, Directors can report to either. Peter committed unilaterally: you will never see me arguing for a VP that does not report to me. Greg accepted, and asked that the ladder not be built in a vacuum but be made cross-applicable and run as an org-wide initiative with Mariah. Peter agreed and took the write-up. They ended at Peter stating they were 85 percent aligned.
Sensitive Decision
Sensitive Decision
Sensitive Decision
Sensitive Decision
Say yes to the Nikola Kolev hire only against a handshake that it starts a timer on Jason Rodriguez - and reject the three-or-four-more-people gate outright
Mariah reported that Nathan had told her he needs three or four more people in before anything moves on Jason Rodriguez, and would not be ready to start until October. Peter told Mariah flatly that is not going to be true, then took it to Nathan in their 1:1 the same afternoon. He drew the line precisely: he will shake hands on you can hire a Jason Rodriguez replacement before we do anything about Jason, but not on we filled every role that we could possibly fill before we are doing something. He then made Nikola conditional - if you want to move forward on Nick because you think it will allow you to remove Jason, then I will say yes, but I would like it to come with a handshake that you are getting super aggressive then with Jason. Nathan agreed to the handshake. In the roundtable an hour earlier Peter had held the same question open in front of the panel, saying the manager conversation had to happen separately.
Sensitive Decision
Take the engineering re-leveling from principle to a concrete ladder - 13 levels down to 4 (open to a 5th), leadership down to Director and VP - and commit that no mapping ships without the direct report in the room
Across three 1:1s on Aug 13 (Nathan, Steve, Ryan) Peter walked each direct report through a spreadsheet he had shown nobody, collapsing roughly 13 engineering levels into Engineer / Senior / Principal / Distinguished, and collapsing his own leadership layer from directors, senior directors and head-of titles down to Director and VP. Nathan argued for a fifth level (Staff) to separate Jeremy from Sultan; Peter took it as reasonable without committing. Ryan was placed in the VP bucket and told so directly. Peter named two hard constraints: nobody gets a pay cut, and existing option grants cannot legally be reduced. Timeline given to Ryan: weeks, not months. Sequence: get Mariah bought into the framework first, then walk each org through its own mapping.
Sensitive Decision
Proceed with the Patrick Culp offer as US-only and say absolutely nothing about the future - if we lose him, we lose him
Nathan raised that Patrick Culp intends to relocate to Japan with no firm date, and Brie asked whether to proceed and how to shape the offer. Nathan proposed telling him relocation is not something we would be open to in the short term and would have to be re-evaluated. Peter judged that about 80 percent correct and cut the remaining 20 percent hard: I would not make any future looking statements, even something - I would not make any future looking statements, period. We just do not know what is going to happen. Even in the short term, we do not know what is going to happen. What he authorized instead was a statement of present fact framed against Patricks own Amazon background: unlike Amazon, unlike Apple, unlike Google, we do not have a Japan entity right now, so there is no Japan CIQ to move you to. It is true that we have people working in Japan right now - they do not actually work for CIQ. And I would leave it at that. No more than that. He gave one reason for today - today I would not support moving an engineer to Japan because they do not work for CIQ and because the hiring policies make it prohibitively difficult - and then stopped. He accepted the cost out loud: and if we lose him, we lose him. But also, as long as he is willing to hear this is what is true today, and he is willing to sign on to it, I am happy backing it. Nathan and Brie agreed to have the conversation before writing the offer, with the US number known internally but not presented.
The engineering re-leveling lands as a conversation with each direct report, not a directive - and Wallaces org is over-titled but not over-paid
Peter settled how the engineering leveling and compensation review will be delivered. The artifact is a spreadsheet comparing each orgs leveling and compensation against all of engineering, and he will walk it through individually with each direct report next week. He pre-emptively stripped it of authority in both 1:1s where it came up. To Ryan: it is going to be the spreadsheet I am putting together is the beginning of a conversation with each of my direct reports to say, here is how your org is structured from a leveling perspective, here is how all of engineering is structured, here is how your org is compensated, here is how all of engineering is compensated. I am not going to shove it down your throat. To Steve, twice: it is not something I am going to force down your throat or anybody else throat, it is the beginning of a conversation, that is all it is - and I will get it in front of you sometime next week, but it is for a conversation, not for this is what I am doing to your team exercise. He also delivered the specific diagnosis for Wallaces org directly to Steve: your team has titles that are far above the rest of the organization, so there is going to be some leveling reset that ends up impacting your team - but from a comp perspective your team is not overly compensated, in fact they may be low in some places, so I think you are going to have a fine story to tell. To Ryan he was blunter about the same finding: the number of directors we have across Wallaces org is just stupid, and it does not fit what I am doing everywhere else in engineering. He deliberately left the remedy open - we could change it by making more people VPs, we could strip away VP titles, we could do a lot of different things to level it - and named Mariah as involved with probably Bjorn a bit. He deferred the Steve walkthrough to Monday because he was slammed both days.
Sensitive Decision
Sensitive Decision
Sensitive Decision
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.
Fix performance-review confirm-receipt acknowledgment — hand-deliver packets now, push HR for global wording change
When Andrew Jorgensen objected that Ripplings mid-year review flow forces employees to click confirm receipt before they actually have the packet, Peter sided with him. In his lane he directed an interim fix: managers download and hand-deliver packets directly so employees physically have them before acknowledging (told Nathan to send Andrew his packet; floated telling all his managers to email packets to everyone this round). As advocacy in HRs lane, he asked Mariah to change the button globally to access your packet and remove the receipt-confirmation sentence. Final wording decision deferred to the 6/16 C-Suite.
Sensitive Decision
Sensitive Decision
Engineering hiring forecast: 2-3 engineers every 6 months, Linux Security next, Bay Area preference
Peter committed to a 12-month engineering hiring cadence of 2-3 net new engineers every 6 months. Next 6 months: Linux Security Engineer (target hire 4-6 months out), plus potentially one more for Nathans team contingent on bug volume. Hiring location preference: Bay Area. Mariah updates the shared headcount/salary forecast spreadsheet to reflect this for Bjorn.
Kyle move conditions: permanent (no return) and gated on RLC completion
If/when Kyle moves to Gregs research team, the move is permanent with no path back to Wolfords org. The gate is Kyle completing his current RLC commitments first, not just Wolford filling the backfill rec. Greg owns the conversation and setting expectations with Kyle on self-management and performance; Greg will update Peter and Bjorn on Kyles decision.
Cedric placed full-time on Gregs research team; Kyle still pending Gregs conversation
After the C-Suite Sync surfaced the Kyle/Cedric risk asymmetry (Kyle = low performer needing hard deadlines, Cedric = high-output engineer well-suited for rapid POCs), the research-team assignment from yesterday flipped: Cedric is now the firm full-time mover to Gregs research org, while Kyles move is still open and gated on Greg-owned conversation + Kyle finishing his RLC commitments first. The Wolford backfill rec opens regardless of which one moves.
Refuse holiday-weekend pressure on people — Mariah review deadline AND Ryan reviews
Two paired actions on 5/24. (1) When Mariah pushed Peter Sunday evening that mid-year reviews were 50% complete on the day-of deadline, Peter held the line — no pushing direct reports who are on a 3-day holiday weekend. Drew distinction between the people who plan ahead (will finish on time) and those who do not (will finish Tuesday night either way). Committed to thinking about better engagement separately. (2) Same evening Peter DMed Ryan: I am not going to read your reviews today or tomorrow — you should take a break. Same posture applied to a direct report Peter could see was burning out from a hard week.
Kyle conditional move to Greg AI role gated by filling Wolfords rec first; Cedric written off the Fuzzball team
Kyle reached out to Greg directly about the AI role reporting into Greg. Peter aligned with Greg and Chris Wolford on the following: (a) Kyle stays in Wolfords org through end of June while the new tickets land; (b) Wolford receives Gregs open rec immediately and starts hiring; (c) Kyle does not move until that rec is filled; (d) Kyle is told this is a job change, not a trial — if it does not work in Gregs world he is out, same as any other role mismatch; (e) Peter will tell Greg that Cedric is NOT meaningfully delivering on Fuzzball today (he is a part-time advisor at best while building for Greg), and Wolford will plan as if Cedric does not exist on the team going forward.
Extend personal-health leave to 6/5 with explicit cap and revisit trigger
Peter agreed via DM with Mariah to extend a direct reports unpaid personal-health leave through 6/5, while explicitly stating that extending past 6/1 pushes past his comfort level and that any extension beyond 6/5 will trigger a revisit. The decision balanced Bjorns prior generosity preference (Bjorn was consulted before responding) against Peters own concern about open-endedness. Mariah immediately flagged precedent implications.
Sensitive Decision
Moody accountability: step up to senior contributor or be managed — framed as response to his growth ask
Flagged Moodys recent missed deadlines and failure to track work to Steve in 1:1, with explicit framing: this is a direct response to Moodys stated desire to become a senior contributor, not a punitive measure. Expectation set: Moody must step up and handle responsibility independently, not require close management. Steve aligned. Moody is out May 15-20 — coaching window is now.
Mariah escalates Stephen Moody project delays directly to Peter (bypass Wallace)
Mariah will notify Peter immediately when Steve Moody delays HR-relevant project work. Triggered by a 6-week unresponsiveness pattern on the Rippling/JIRA integration that Steve Wallace had not escalated. Direct-escalation bypasses the manager (Wallace) for HR-adjacent commitments while Peter assesses whether this is a Moody problem or a Wallace prioritization problem.
Coach Mariah toward sharper, peer-level feedback posture — Reno trip offered
Following a heated DM disagreement about how to handle a senior IC's return-from-leave conversation, Peter offered Mariah an explicit choice: be treated the way Peter treats Bjorn and Greg (sharp, direct, unvarnished disagreement) or stay softer. Peter framed the conversation as investment, named that Mariah is undersized for where she could be ('I would like to see you pulled more into the core of things here'), and offered to be in Reno end of next week (Thursday) to discuss over lunch.
Sensitive Decision
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.
Sensitive Decision
Open hiring for a dedicated Ascender engineer
In the Design Sync, Peter took the action item to draft an Ascender Engineer job requisition and start the hiring process. Root cause: engineers Jimmy and Larry rejected a UI update PR for Ascender Pro citing the internal Quantic design system is not open source — an objection that is irrelevant since Ascender Pro is a closed-source commercial product. Bjorn will handle the immediate Jimmy conversation next week. Peter's move is structural: create an engineering owner whose role explicitly covers the closed-source Ascender Pro commercial mandate, so the category of blocker goes away.
Sensitive Decision
Delayed HR action pending Chris feedback in upcoming 1:1
When Mariah proposed proceeding with an HR-related action, Peter declined, saying he wants to get feedback first from Chris about how it's going in his 1:1 with Chris this week. Mariah acknowledged and asked to be kept posted.
Michael Young Termination Communication Approach
Peter set communication boundaries for Michael Young's termination: don't tell RESF people WHY, only 'we decided to part ways.' Advised Greg not to write specifics down. Declined to reply to Michael directly.
Sensitive Decision
Asset Management — Backend-First, Bridge to Views
Advocated for deciding where the asset management backend should live first, then building bridges to expose it wherever needed (Jira, Rippling). Explicitly disagreed with Greg's framing that building bridges adds unnecessary complexity.
Zorina LOA — Grant Extended PTO to Retain
Decided to grant Zorina 5 weeks of PTO (May 4–June 5) if her FMLA application is denied. FMLA application goes first for compliance, but the fallback is already decided. Remote work from Bulgaria for 2 weeks is also approved pending IT security check. Delegated execution details to Justin and Mariah.
Approved retention check-in strategy for must-keep employee list
Approved the must-keep employee list prepared by Mariah and Chris. Committed to personally leading retention check-ins with must-keep engineering employees. Bjorn leads check-ins for his org. Mariah and Chris excluded their own teams (already monitored closely).
Sensitive Decision
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.
Override hiring freeze to hire Ben and Jamin for Linux engineering
Decided to bypass the company hiring freeze to bring on two key candidates: Ben (priority hire, competing with Anthropic offer) and Jamin (from Oracle, expensive but high-performing with strong ownership). Committed to sync with Mariah to clear headcount for both.
Delegated Jason Lewis termination coordination to Mariah for March 3
While preparing for Dubai trip, delegated coordination of Jason Lewis termination logistics to Mariah Rippee, asking her to work with Steve Wallace during the week Peter is out, targeting the first Monday of March (March 2).
Jason Lewis Termination - Ready to Action
Confirmed readiness to proceed with Jason Lewis termination now that the ISO 27001 certification letter has been received. Will coordinate with Steve Wallace and Mariah Rippee (HR) to execute. Jason recently requested a seat at the table for self-service discussions, unaware of the pending action.
Performance review redesign - define traits with observable behaviors
Committed to drafting a proposal to fix the performance review system for the April/May cycle. The approach keeps existing traits but defines each with observable behaviors so managers and employees have shared understanding of what success looks like.
Jason Lewis layoff with Steve Wallace as compliance owner
Decided to proceed with Jason Lewis departure (structured as layoff) due to expectation misalignment and damaged relationship with Bjorn. Steve Wallace will assume all compliance responsibilities (ISO 27001, SOC 2, ISO 42001). Budget reserved for full-time replacement after 6-month layoff waiting period. Fractional hire and external auditor approved for interim.
Jason Lewis Termination Timeline
Jason Lewis is slated for termination by end of January. Timing is delayed to allow ISO certification work to complete over the next two weeks, as his name is on that work.
Trinity Quirk & Chris Short Terminations Executed
Terminated Trinity Quirk for failing to progress NARF/CVE automation integration despite clear expectations. Terminated Chris Short for failing to deliver on critical RESF-related goals. Sent transparent communication to all of engineering explaining the WHY behind these decisions.
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.
Ali Contract Termination
Decided to end Ali's contract after he missed another check-in meeting and failed to demonstrate proactive delivery necessary for a remote contractor. Reached out to Mariah to understand the process steps.
Sensitive Decision
Culture Document Feedback - Focus on PMF Over Morale Programs
Gave negative feedback on culture document. Called morale initiatives (swag, customer presentations) rearranging deck chairs on Titanic. Only endorsed product training to build product-led company. Identified redundant work (H1 planning already happening) and premature planning (5-year plan).
Related Patterns (14)
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.
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.
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.
Resource Optimization Through Triage
Apply cost-benefit analysis to avoid spending disproportionate time and energy on low-impact activities. Conserve resources for high-impact work.
PMF Focus Over Morale Programs
At startup stage, finding product-market fit is the real driver of morale, not swag or programs. Resources should focus on core business problems rather than premature organizational investments.