Purchase approvals below a managers own threshold must never route to the CTO - told Nathan to expense it anyway and took the fight to Finance rather than the person executing the policy

July 30, 2026 at 10:39 PMoperationalmedium

Situation

Nathan bought a roughly 100 dollar remote KVM for the NVIDIA DGX Spark so other engineers could access it, after asking Peter first and being told yes. Erin Fong flagged that company-funded equipment must be tracked through an IT ticket before purchase; Nathan said it was not worth the hassle and would pay out of pocket. Peter intervened in three places. In DM to Nathan: No. Tell them No and that the CTO said it was fine. I do not want stuff like this to continue - and, repeatedly, But I already just said you can just expense these things. In the group DM he took the diplomatic line publicly - Nathan asked me prior to purchasing if it was ok. I said yes. Did not know this policy existed. If a ticket can be created rapidly in a way that does not burden Nathan, great - and Stephen Moody opened IT-6605 to document the approval. Then he located the real owner: he asked Steve Wallace whether the policy came from him (it did not, it came from Finance via Erin), and stated the fight he intends to pick: you have a threshold you can approve up to, Nathan has a threshold, I have a threshold. If it is below your threshold and you approved it, I do not want it routing to me. I do not want to know about it. I do not want to think about it. I never want to see it. Separately he coached Nathan on target selection: ask yourself whether you are solving this for yourself, for CIQ, or trying to make Erin recognize the policy is stupid - Erin works for us a couple hours a week and her job is to click buttons on the policy, she does not own it, so there is nothing you can say that will change it.

Reasoning

Two things at once. First, unblock his direct report immediately and absorb the policy risk himself so a 100 dollar item does not cost a Senior Director an afternoon - Nathan noted he had already spent more of his own time than the item cost. Second, fix the class of problem at its source rather than the instance: delegated spend authority is meaningless if approved items still route upward, so the ask to Finance is a threshold regime, not an exception for this purchase. And he deliberately protected Erin from the blast radius, because escalating at a part-time contractor executing someone elses policy cannot produce the change and only damages the relationship.

Additional Context

Steve independently confirmed he had hit the same thing - TJ bought a 100 dollar display adapter and Steve told him to put it in RAMP and he would approve it, no questions. Steve: I think we should have a threshold where we need a ticket and approval, and 100 dollars is - we have wasted 100 dollars talking about the damn thing.

Observed Evidence

Five direct sources across Slack DM, group DM and two 1:1 transcripts, all within a three-hour window. The decision statement is a verbatim quote to Steve Wallace.

Matching Patterns

53%
Demonstrate the Standard, Then Collect It(involves Nathan Blackham, Steve Wallace, same category (operational))
38%
Purpose Is the Decision Procedure(involves Nathan Blackham, Steve Wallace, same category (operational), restated what an approval threshold is FOR rather than litigating this purchase)

Confidence Breakdown

35/35
Evidence
26/30
Pattern
20/20
Source
14/15
Corroboration

Reasoning Depth Analysis

Org Signal:Delegated authority is real authority. A manager who has been given a spend threshold will not be second-guessed inside it, and the CTO will absorb policy friction on his orgs behalf rather than pass it down. It also signals that escalation should be aimed at whoever owns the policy, not whoever is enforcing it.
Who Affected:Every engineering manager with a spend threshold. Erin Fong and Finance, who will receive the actual challenge. Stephen Moody and IT, who now have a documented approval trail for this purchase. TJ in Steves org, who hit the identical issue.
Precedent:Sets that the CTO will say the CTO said it was fine in writing to unblock a small purchase - a deliberate use of positional authority to absorb process risk. Also sets the norm that a policy complaint gets routed to the policy owner, not the executor.
Consequences:Real on both axes. The IT ticket was actually created and the expense path unblocked today. The threshold conversation with Finance and Steve is a live commitment, not an aspiration.
Timing:Now because Nathan was visibly about to eat the cost himself out of frustration - a Senior Director opting out of expense reporting is a signal Peter would not let stand, and the incident gave him a concrete case to take to Finance.

Source

reflection

AI Confidence

95%

Related Context

💬
DM with Nathan Blackham

slack

No. Tell them No and that the CTO said it was fine. I do not want stuff like this to continue.

💬
Group DM with Erin Fong, Stephen Moody, Nathan Blackham

slack

Nathan asked me prior to purchasing if it was ok. I said yes. Did not know this policy existed. If a ticket can be created rapidly in a way that does not burden Nathan, great.

🎥
Steve <> Peter Weekly 1:1

fathom

I am going to go pick a fight, and the fight I am going to pick is - you have a threshold you can approve up to. Nathan has a threshold. I have a threshold. If it is below your threshold and you approved it, I do not want it routing to me. I never want to see it.

🎥
Nathan <> Peter Weekly 1:1

fathom

Recognize who Erin is. Erin works for us a couple hours a week, and her job is to click buttons on the policy. Erin does not own the policy. So there is nothing you can say that is going to make Erin go, oh, well, this has changed.

Outcome

No outcome recorded yet.

Decision ID: a83205f5-3cc9-48ba-a7a2-5b08b36462a1