Jonas Keller Leads Operations
- type
- organizational-decision-record
- status
- accepted
- date
- 2026-09-10
- decision-makers
- Mara Holt
- for-domain
- Head of Operations
- created_at
- 2026-09-17
Context
Until September 2026 every coordination question in Bakery Operations — a late van, a shop short on sourdough, a café asking for a standing order — landed on Mara Holt, usually while she was baking. With a second shop, a delivery team and a wholesale book that keeps growing, the owner had become the bottleneck of the day-to-day.
Decision
Create the Head of Operations role and give it to Jonas Keller. The two shop managers, Deliveries and Wholesale report to him; he chairs the Daily Production Sync whenever Mara is in the Bakehouse. Mara keeps range, brand and the final call on capacity.
Consequences
- One reporting line for everything operational; Mara’s mornings stay in the Bakehouse.
- Jonas becomes the single point of contact for the shops, the vans and the cafés — which is exactly the load that Head of Operations Is the Dispatch Bottleneck later reads as a risk.
- The role, not the person, carries the mandate: a hand-over does not reopen this decision.
Modeling note
This record is about a person, but it is anchored through the
role: for-domain names Head of Operations, not Jonas. The decision lands on the
box of whoever keeps that role — today Jonas — and the org chart says through which role
it arrived. The role’s own domain (Bakery Operations) learns nothing new from it.
Like what you see? → Start — build your own org folder in ~2 min