Katie O'Malley

Feb 4, 2026 - Mar 5, 2026

4

Decisions

0

Active Todos

8

Patterns

Decisions (4)

Ascender Developer Hiring — Network-First Sourcing Strategy

Decided to hire a dedicated AWX developer for Peter's team to offload maintenance from Jimmy Conner, freeing him for strategic architecture, sales engineering, and customer engagement. Hiring strategy: Jimmy sources from AWX network first (leveraging dissatisfaction with project's shift to internal repos), Brianne as fallback. Compensation: culture-forward, candidates may accept $25-50K pay cut for culture/stock options, $100K+ gap is non-starter.

Mar 5
people

Unified Google Proposal — Present Combined GDC/GCE to Rohan

Aligned Kelly and Bjorn on presenting a unified GDC/GCE proposal to Rohan (Google senior director) instead of negotiating separately. Reframing from pro-serve/ticket model to value-driven partnership with a large fixed annual fee ($8-9M).

Mar 4
strategy

Demanded war-room or date ranges for RLC Pro release dates

Marketing (Lindsay Aamodt) published release dates in #department-heads: Feb 19 RLC Pro, Feb 26 RLC Pro AI, Mar 5 RLC AMD. Justin Haynes responded that dates were 'written in light pencil.' Peter directed Justin: if dates aren't confident, either commit with a war-room to hit them, or provide GTM with ranges now so they can plan. Justin acknowledged and scheduled time with leads.

Feb 11
operational

RESF Strategy: Remove Lewis with Legal Leverage, Engage Neil Collaboratively

Approved plan to remove Luis (Lewis) from the RESF board using a Quinn Emanuel memo documenting a potential federal law violation and breach of fiduciary duty, then send a collaborative letter to Neil offering a path forward to avoid a public fight. Greg will present the memo to board members to secure their support. Shadow infrastructure (Koji, clones) is confirmed ready.

Feb 4
strategy

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.

77 occurrences75% success

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.

74 occurrences74% success

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.

61 occurrences87% success

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.

60 occurrences79% success

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.

59 occurrences86% success

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.

57 occurrences52% success

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.

55 occurrences48% success

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.

19 occurrences0% success