Slot Karl under Wallace rather than take a new direct report - with a stated escape hatch and a three-month contract extension

September 11, 2026 at 10:24 PMpeoplemedium

Situation

Peter told Karl the HR paperwork was signed and moving, encouraged him to meet Steve Wallace whenever he wants, and confirmed the intent for Karl to report to Wallace. He named his own constraint plainly - he does not want to add direct reports right now - and in the same breath acknowledged Karl will be a different animal from anything else under Wallace, told him to reach out directly if he is not getting what he needs, and pre-committed to changing the arrangement if the fit does not work. In parallel over Slack, Peter asked Chris Baek who to talk to about extending Karl contract by three months and offered to do it himself. Karl is evaluating one other option and will confirm Monday morning.

Reasoning

Peter stated the span-of-control constraint as a personal preference rather than dressing it as an org-design principle, then priced the cost of his own rule in the same sentence - the fit under Wallace is genuinely uncertain because Karl work does not resemble anything else in that org. The open line to Peter is the mitigation for that uncertainty, not an invitation to route around Wallace. The three-month extension applies the same instinct on the time axis: do not commit permanently to a structure that has not been tested.

Additional Context

Karl is currently under Chris Baek. He is partly absorbing scope that had sat with Tabatha, whose 100-page responsibilities document he walked Peter through in the same meeting. Karl said he would take the weekend to think and decide Monday.

Observed Evidence

Direct quote from the Fathom transcript of the Karl sync, corroborated by two Slack messages to Chris Baek the same day covering the contract extension and Karl deliberation.

Matching Patterns

30%
Name It Without Staffing It(names the structure and the exception to it in the same breath, same category)
25%
Protect Engineering Capacity(span-of-control protection)

Confidence Breakdown

33/35
Evidence
20/30
Pattern
19/20
Source
12/15
Corroboration

Reasoning Depth Analysis

Org Signal:A contractor is told both the reporting line and its escape hatch before he accepts, rather than discovering the mismatch later. Peter is willing to say the constraint is his own preference rather than manufacture a principle for it.
Who Affected:Steve Wallace, who inherits an unusual report without having asked for it; Chris Baek, the current owner who handles the extension; Tabatha, whose scope Karl is partly absorbing.
Precedent:Span of control is allowed to stand as a stated personal constraint rather than a justified rule, and the person affected by it gets told the cost out loud.
Consequences:Real - the HR paperwork is already signed and moving, and Karl decides Monday against a competing option.
Timing:Now because Karl is weighing another offer and needed both the structure and the escape hatch in hand before deciding over the weekend.

Source

reflection

AI Confidence

84%

Related Context

🎥
Karl <> Peter sync

fathom

feel very comfortable reaching out to me directly if there is anything you are not getting from him. I just, I do not want to add direct reports to me right now, but you will be a different animal than anything else underneath him. So if it does not work well under him, we will make a change.

💬
DM with Chris Baek

slack

Chris - who do I (or you since he is currently under you) talk to in order to extend Karl contract by 3 months. I am happy to do it. ... He will confirm on Monday if he will extend the contract. ... Sounds like he is evaluating one other option.

Outcome

No outcome recorded yet.

Decision ID: 16917381-c2ed-4577-8231-01e92444a145