Jonathan Maple

Jan 23, 2026 - Aug 13, 2026

5

Decisions

0

Active Todos

8

Patterns

Decisions (5)

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.

Aug 13
people

Sensitive Decision

Sensitive

Gate Rakuten 8.6 / RT-kernel support work on a signed 1.6 to 1.8M expansion that funds dedicated headcount

Decided that the risky, currently unsupportable Rakuten 8.6 / RT-kernel support work will either not be done at all or only be delivered tied to a signed contract expansion in the 1.6 to 1.8M range that funds dedicated Rakuten headcount on CIQ side. The bar is enough to cover roughly two dedicated engineers, not an arbitrary large number. Peter forwarded the engineering teams infrastructure objections to Bjorn to arm the customer conversation.

Jul 6
strategy

Accepted CLK 6.18 delay to March 31

Approved Jonathan Maple's request to slip CLK 6.18 from March 27 to March 31, due to kernel source-git conversion process. Positively reinforced Maple's proactive escalation.

Mar 25
operational

Considering transition period policy for departures

Agreed to consider a policy change where departing staff could be offered a choice: immediate exit or a paid transition period (e.g., 2 weeks) for a clean handoff. This came from Maple feedback about Trinity terminations creating project handoff gaps.

Jan 23
people

Related Patterns (8)

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.

175 occurrences67% 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.

173 occurrences67% success

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.

172 occurrences78% 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.

169 occurrences78% 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.

161 occurrences79% 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.

159 occurrences77% 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.

156 occurrences77% 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.

137 occurrences65% success