GreenBox has 12,000 subscribers, three cities, twenty-five people, and a quarterly planning cadence that connects daily work to yearly strategy. The product works. The team works. The board has a question Maya isn’t ready for.
The board meeting is on a Thursday afternoon in early November. Maya has prepared a deck – she’s good at decks now. Quarterly themes, throughput forecasts, churn metrics by city. Charlotte helped her build the format over the past two quarters and the board engages with it. The conversation flows.
Then Diane, the seed investor, asks: “Maya, how many people report directly to you?”
Maya counts. Tom. Sam. Jas. Anika. The Brisbane squad lead. Charlotte, sort of – she’s a coach, not an employee, but she joins every leadership meeting. Lee, in an advisory capacity. The finance contractor. The part-time HR person.
“Eight. Maybe nine, depending on how you count Charlotte.”
“And how many of those people can make a decision without you?”
The room goes quiet. Maya starts to answer, then stops. She’s thinking about last week. Sam needed to approve a new courier contract for Brisbane – routine, within budget, terms consistent with the Perth contract. But Sam waited for Maya to review it. Jas had a pricing question about the B2B pilot – should the corporate boxes include a premium for custom branding? She messaged Maya on Tuesday and Maya didn’t reply until Thursday because she was in customer interviews. Tom wanted to hire a contractor for three months to cover paternity leave – Ravi’s baby is due in six weeks – and he waited for Maya to approve it even though the budget existed and the role was already scoped.
Three decisions. Three days of waiting. All three could have been made without her.
“Not enough of them,” Maya says.
Diane doesn’t push. She makes a note on her pad and the meeting moves on to Brisbane margins. But Maya can feel the note sitting there, three words or four, like a stone in her shoe.
After the board meeting, Charlotte walks with Maya to the car park. It’s late afternoon and the Perth sun is doing what it does in November – making everything look slightly too sharp, slightly too bright. Maya puts her sunglasses on and doesn’t say anything for a while.
“You know what she was asking,” Charlotte says.
“She was asking whether the company works without me.”
“She was asking whether it works with you. Right now, you’re the bottleneck for every decision above squad level. Three cities, twenty-five people, and one person who signs off on everything.”
Maya stops walking. “I’ve heard this before.”
“You have. Event Storming – month one. Lee said the domain was stuck in your head. Same pattern, different level.”
Maya remembers. The wall of sticky notes. Tom’s frustration. The discovery that GreenBox’s entire business logic lived inside Maya’s skull and nobody else could build anything without asking her first. They fixed it – Event Storming got the domain into shared understanding, decision tables codified the matching rules, the Business Model Canvas captured the business model. The knowledge left Maya’s head and entered the system.
But the decisions didn’t. The domain knowledge is shared. The authority isn’t.
“In month one,” Charlotte says, “you were the domain bottleneck. The team couldn’t build without your knowledge. We fixed that. Now you’re the authority bottleneck. The team can’t act without your permission. It’s the same instinct.”
Maya knows it’s her parents’ pattern. She’s known it since the JTBD crisis, when her founding assumptions were challenged and she nearly sent the “pausing operations” email. The farm her parents lost – partly because they couldn’t ask for help, couldn’t let anyone else carry the weight, couldn’t delegate the soul of the thing they’d built. She inherited the pattern. She’s aware of it. And she’s doing it again.
“I know,” she says. “I just don’t know what to do about it.”
Charlotte says: “You’ve built a product. Now you need to build a company.”
The pattern
Charlotte has seen this transition in every subscription business she’s coached. There’s a moment – usually between 15 and 30 people – where the founder’s decision-making capacity becomes the binding constraint on the organisation. Below 15 people, the founder can hold everything. Every decision can route through one brain and the delay is minutes, not days. Above 30, it’s obviously impossible and most founders have already hired managers. But the 15-to-30 range is dangerous because it almost works. The founder is stretched but not broken. Decisions are slow but not stopped. The team compensates by working around the bottleneck – Sam approves the courier contract herself and tells Maya after the fact, Tom hires the contractor on a verbal agreement and gets formal approval later. The organisation learns to route around the founder, which feels efficient but creates a shadow decision-making structure that nobody has authorised and nobody trusts.
“The symptoms are always the same,” Charlotte tells Maya. “People waiting for you to respond. People making decisions without you and feeling guilty. People escalating things that shouldn’t need escalation. Meetings that exist because you need to be in the room, not because the room needs you.”
Maya thinks about her calendar. Monday: leadership standup (all squad leads, Charlotte, Sam). Tuesday: Perth sprint planning. Wednesday: customer interviews. Thursday: board prep or board meeting. Friday: catch-up on everything she missed Monday through Thursday. Plus ad hoc decisions – Slack messages, email, the corridor conversations that turn into thirty-minute sessions because someone has been waiting three days for her opinion on something.
“How many hours a week do you spend making decisions that someone else could make?” Charlotte asks.
Maya estimates. “Fifteen? Maybe twenty.”
“That’s half your week. And every hour you spend making a decision someone else could make is an hour you’re not spending on the decisions only you can make.”
“Like what?”
“Strategy. Culture. Board relationships. Partnerships. The question of where GreenBox goes in three years. The things a CEO does that nobody else in the organisation can do.”
Diane Kerrigan
Two weeks after the board meeting, a woman in boots walks into the GreenBox Perth office. She’s tall, late forties, with greying hair pulled back and the kind of tan that comes from years outdoors rather than holidays. She’s carrying a leather satchel that looks like it’s been through a decade of use and a takeaway flat white from the cafe on the corner.
“Diane Kerrigan,” she says, shaking Maya’s hand. “The board asked me to come in for the Series B prep. Charlotte and I have spoken. I’ve read her notes. I’d like to spend a week just watching.”
Maya has done her research. Diane built Sunridge – an organic food brand that started as a market stall in regional Queensland and grew to 200+ retail outlets before Diane sold it to a private equity firm. She knows consumer brands, supply chains, retail partnerships, and what investors actually care about. She’s on the advisory circuit now, brought in by boards when companies are scaling from startup to institutional investment.
Charlotte knows of her by reputation. “She’s a business operator, not a process coach,” Charlotte told Maya. “We’ll see things differently. That’s probably the point.”
Diane spends the first three days in the office watching. She sits in on the Monday leadership standup, the Tuesday sprint planning, a customer interview on Wednesday, and Charlotte’s quarterly theme review on Thursday. She takes notes in a leather-bound notebook with handwriting that’s barely legible. She asks almost no questions. On Friday afternoon, she asks Maya for thirty minutes.
They sit in the small meeting room that used to be a storage cupboard. The Event Storm photos are still laminated on the wall behind Maya. Diane glances at them.
“You have 25 people and zero managers,” Diane says.
“Charlotte coaches –”
“Charlotte coaches process. She doesn’t manage people. Tom leads the engineering work but he doesn’t approve leave, set salaries, or conduct performance conversations. Sam runs operations but she has no authority to sign contracts or approve spending. Jas has grown into a product role but there’s no product function – there’s Jas, and whatever Maya has time to discuss with her.”
Diane puts her coffee down. “Everyone reports to Maya, and Maya reports to everyone. That’s not a management structure. That’s a solar system with one sun.”
“We’re not a hierarchy,” Maya says. “We’re collaborative. Flat.”
“You’re flat because you haven’t grown up yet, not because you’ve chosen a better model. Flat at five people is a philosophy. Flat at twenty-five people is a bottleneck. You already learned this once.”
The words land. Maya recognises the callback – it’s exactly what Charlotte said in the car park, what Lee said in month one. The pattern repeating at a higher level.
“I don’t want to become corporate,” Maya says. “I’ve seen what happens. Middle managers who exist to justify their own existence. Meetings about meetings. Approvals for approvals.”
“That’s bad management. I’m not recommending bad management. I’m recommending a minimum structure that lets twenty-five people make decisions without waiting for you.” Diane opens her notebook. “Let me show you what I mean.”
The minimum management layer
Diane draws a diagram. It’s simpler than Maya expects.
At 25 people, GreenBox needs four roles that carry genuine authority – the ability to make decisions, allocate resources, and be accountable for outcomes within their domain. Not new hires necessarily. Mostly existing people with formalised responsibility.
“Three promotions and one hire,” Diane says. “That’s it. Not a corporate restructure. A minimum structure that removes you as the bottleneck for day-to-day decisions.”
Charlotte, who’s been listening from the doorway, adds the management theory. “The typical span of control research says a manager can effectively support five to nine direct reports. You have nine, plus the informal reports – Charlotte herself, Lee in advisory, the finance contractor. You’re at twelve or thirteen. The research says that’s the point where quality of attention degrades. Not dramatically. Just enough that everyone gets slightly less of you than they need.”
Diane is less interested in the theory. “The practical test is this: if Maya goes on holiday for two weeks, what breaks?”
The room goes quiet. They all know the answer. Everything.
“Not the product,” Diane continues. “Tom can keep the squads running. Not the logistics – Sam handles that day to day. What breaks is decisions. The courier contract that needs signing. The pricing question for the B2B pilot. The hiring approval for Ravi’s parental cover. Every cross-functional decision that requires authority. Right now, all of that authority lives in Maya.”
Delegation of authority
Diane introduces a concept she calls “decision rights” – borrowed from RACI matrices but stripped to the essentials. For every type of decision the company makes, one person needs to be clearly Responsible (they make the call), one person needs to be Accountable (they’re on the hook for the outcome), and everyone else needs to be Consulted or Informed.
“The problem at GreenBox,” Diane says, “isn’t that nobody knows who’s responsible. It’s that Maya is responsible for everything and accountable for everything. Nobody else has permission to make the call.”
They build a decision rights table in thirty minutes. Diane facilitates, Maya and Charlotte contribute, and Sam joins halfway through because she’s the person most affected by the current ambiguity.
| Decision | Responsible | Accountable | Consulted |
|---|---|---|---|
| Hiring (engineering) | Tom | Maya | Charlotte |
| Hiring (operations) | Sam | Maya | Tom |
| Courier contracts | Sam | Sam | Maya |
| Pricing changes | Jas | Maya | Charlotte, Sam |
| Technical architecture | Tom | Tom | Charlotte |
| Customer escalations | Sam | Sam | Jas |
| Sprint priorities | Squad leads | Tom / Jas | Charlotte |
| Quarterly themes | Maya | Maya | Charlotte, squad leads |
| Partnerships / B2B | ??? (new hire) | Maya | Jas, Sam |
| Spending < $10K | Department lead | Department lead | Maya (informed) |
| Spending > $10K | Maya | Maya | Board |
Sam looks at the table for a long time. “You’re saying I can sign the courier contract without Maya reviewing it?”
“If it’s within the terms we’ve agreed and under $50K, yes,” Diane says. “You’re the operations lead. You understand the terms better than Maya does. You’ve been making the recommendation every time and then waiting for Maya to rubber-stamp it. The rubber stamp adds delay and no value.”
Sam’s expression is complicated. She’s relieved. She’s also a little terrified. She’s been at GreenBox since the beginning, when she was the person who “did everything else.” She’s grown into operations – she runs the logistics for three cities, manages the courier relationships, oversees the warehouse operations. But she’s never had formal authority. She’s never signed a contract with her own name on it. She’s always been the person who prepared the decision for Maya to make.
“What if I get it wrong?” Sam asks.
Diane looks at her steadily. “Then you learn from it and make a better decision next time. That’s what authority means. It means you’re trusted to be wrong occasionally.”
Maya watches Sam absorb this. She recognises the look – it’s the same look she had when Lee first suggested she let the team map the domain without her. The fear of letting go, mixed with the relief of not having to hold everything alone.
Tom’s promotion
Tom takes the engineering lead title with less enthusiasm than Maya expects.
She tells him on a Tuesday morning, in the small meeting room. Charlotte is there. Tom listens, nods, and says, “I know. It’s fine. I’ll do it.”
“You don’t seem excited,” Maya says.
Tom is quiet for a moment. He’s thinking about the substitution engine he rebuilt in an ensemble session three months ago – six people in a room, the LLM typing, everyone navigating. That was the best day of work he’s had in months. The code was elegant, the team was sharp, the output was something none of them could have built alone.
“I became a developer because I like building things,” he says. “Now I spend half my day in meetings about things other people are building.”
Charlotte hears the echo. Tom said something similar in month two, when Lee first introduced workshops. We’re going to spend three hours sticking notes on a wall? And then the Event Storm changed how he thought about his work.
“The meetings will get better when you’re actually making decisions in them,” Diane tells him, joining the conversation. “Right now your meetings are information-sharing sessions because you don’t have authority to act on the information. When you can approve a hire, choose a technical direction, or allocate squad resources without waiting for Maya, the meetings become shorter and more useful.”
Tom isn’t convinced, but he accepts the role. That evening, Sarah asks how his day was. Tom is loading the dishwasher while Leo draws on the kitchen table and Ava reads on the couch.
“They promoted me,” he says.
“Engineering lead. That’s good.”
“Is it? I spend half my time in meetings already. This is more meetings.”
Sarah dries her hands. “You said the same thing about workshops in month two. And then you said they were the best thing that ever happened to your code.”
Tom opens his mouth to argue, then closes it. She’s right. She usually is. But the workshops changed what he built. This changes what he does. He’s not sure the two are the same thing.
He texts Priya after the kids are asleep: They made me engineering lead. Tell me it’s not the end of building things.
Priya replies at eleven, because Priya always replies at eleven: You’re still building. Just building a team instead of a feature. Also, congratulations.
The deploy queue
The management conversation isn’t the only thing building pressure. Tom notices something during the same week: the deploy pipeline is backing up.
Three PRs waiting for review. Two waiting for the staging environment. One blocked because Brisbane and Melbourne both need the staging environment at the same time and there’s only one.
At five people, deploys were simple. Tom reviewed everything. The staging environment was free. Push, test, ship. At fifteen people, they added a review rota and it mostly worked. But at twenty-five people, with three squads shipping independently, the single staging environment is a chokepoint and the review process doesn’t scale.
Tom mentions it to Charlotte after the Wednesday standup. “We need a proper pipeline. Three squads can’t share one staging environment. The review rota is a fiction – people skip it when they’re under pressure and then we get incidents.”
Charlotte nods. “That’s a delivery infrastructure problem. It’s real, but it’s not this week’s problem. Park it. We’ll come back to it.”
Tom parks it. But he opens a document on his laptop and types: Deploy pipeline – three squads, one staging, review bottleneck. Fix before it breaks something. He saves it in a folder labelled “Engineering Lead” and feels a small, complicated thing – something between responsibility and loss. This is what the new role feels like. Not building the pipeline. Noticing that it needs building, and making sure it gets built.
Ren
Maya drives to Fremantle on Saturday morning. It’s one of those November days where the Indian Ocean is absurdly blue and the Norfolk pines along the waterfront throw long shadows across the limestone.
Ren Tanaka is sitting on a bench near the fishing boat harbour, drinking tea from a thermos. She’s 55, Japanese-Australian, with close-cropped grey hair and the kind of stillness that makes other people slow down. She’s wearing linen pants and a faded denim jacket. She looks like she has nowhere to be, which is accurate. Ren runs a community development organisation in Fremantle now. Before that, she managed Maya at a consultancy – the job Maya had before GreenBox. She left consulting because she said it was “helping people optimise things that shouldn’t exist.” Maya calls her at 10pm sometimes. They meet on the waterfront when it matters.
Maya sits down. Ren pours her tea from the thermos without asking. It’s green tea, slightly too hot, in a ceramic cup that Ren has brought from home because she doesn’t believe in takeaway cups.
“The board hired a scaling advisor,” Maya says. “She told me I have twenty-five people and zero managers.”
“Is she right?”
“Yes.”
“How does that feel?”
Maya watches a fishing boat motor out of the harbour. The wake spreads behind it, white on blue, widening until it’s indistinguishable from the ocean.
“It feels like I’ve been told I’m doing it wrong. Again. In a new way.”
Ren drinks her tea and doesn’t respond for a while. A seagull lands on the railing near them and makes an outraged noise about nothing in particular.
“Are you building the company you want to work in,” Ren says, “or the company you think investors want to see?”
Maya turns to look at her. “What do you mean?”
“I mean that you’ve told me about the board’s question, the advisor’s recommendation, the management structure, the decision rights table. You haven’t told me what you want. You haven’t told me whether this is the company you’d build if nobody was watching.”
Maya doesn’t answer. She doesn’t have an answer yet. She thought she was building GreenBox for the farmers and the families. Now there’s a board and an advisor and a Series B and a valuation conversation, and she’s not sure when the thing she was building turned into the thing other people want it to become.
“I don’t know,” Maya says.
Ren nods, as if that’s the right answer. “That’s worth sitting with.”
They sit. The fishing boat is small now, heading for the open water. The seagull leaves. The tea cools. Maya watches the water and thinks about her parents’ farm – the one that became a subdivision, the one in the photo on her desk. Her parents built something they loved and couldn’t let go of, and the world changed around them until the thing they’d built didn’t fit any more.
Is that what’s happening? Or is this different? Is the management structure the thing that saves GreenBox, or the thing that turns it into something she doesn’t recognise?
Ren refills her cup. “You’ll figure it out. You always do. Just make sure the answer is yours.”
What this changes
Monday morning. Maya walks into the Perth office and does something she hasn’t done before: she doesn’t check Slack.
Instead, she opens the decision rights table and sends it to Tom, Sam, and Jas with a note: “This is real. Starting today. If a decision falls in your domain, make it. Tell me after if you want, but don’t wait for me.”
Sam signs the Brisbane courier contract that afternoon. She’s been sitting on it for a week. Tom approves the contractor hire for Ravi’s paternity cover. Jas makes the call on B2B branding – premium pricing, custom labels, minimum order of ten boxes per week.
Three decisions. Three people. Zero delays.
Maya spends the time she would have spent on those decisions preparing for a conversation she’s been avoiding: the sales and partnerships role. GreenBox has grown to 12,000 subscribers entirely through word of mouth, customer referrals, and Sam’s occasional social media posts. There’s no sales function. No outbound. No pipeline. No partnerships strategy beyond Maya’s personal network.
The board has been asking about this for two quarters. Diane’s first question when she reviewed the business: “Who sells?”
Maya: “Nobody. People find us.”
Diane: “That’s not a strategy. That’s luck.”
The management gap wasn’t just about authority. It was about capability. GreenBox doesn’t have the commercial muscle to grow beyond word of mouth. The discovery cadence finds out what customers need. The product team builds it. The operations team delivers it. But nobody is out there finding the next ten thousand subscribers. Nobody is building B2B partnerships. Nobody is thinking about go-to-market as a function rather than an afterthought.
Charlotte, reviewing the org chart with the new management layer, puts it plainly: “You have four leadership roles. Three are filled by people who’ve been here since the early days. The fourth – sales and partnerships – is empty. It’s empty because it’s a capability GreenBox has never had.”
But before Maya can hire for the role, Diane raises a different question at the next board meeting. One that nobody has answered.
“We’re preparing for Series B,” Diane says. “Investors are going to ask what the company is worth. Maya, do you know the answer?”
Maya doesn’t. Nobody at GreenBox does. They know the subscriber count, the churn rate, the revenue per box, the margin per city. They’ve never translated those numbers into a valuation.
“That,” says Diane, “is where we start (coming 10 November).”