The acquisition is behind them. Seven cities are live. The eighth – Hobart – launches next month. GreenBox has eighty people, thirty thousand subscribers, and a culture that was built for a room of five. Maya discovers that half the company is doing the practices without understanding why.
The message appears in the #brisbane-squad Slack channel on a Tuesday afternoon.
what’s the point of the Tuesday interviews? we already know what customers want. can we skip this week? we’re behind on the recipe card redesign
The message is from a developer named Liam, hired three months ago into the Brisbane squad. He’s 26, competent, joined from a mid-size agency in South Brisbane. He’s never met Maya. He’s never been to Perth. He’s never attended an Event Storm with Dave in the room or sat through a JTBD interview where a subscriber said “I just want dinner sorted” and the entire company’s direction shifted.
Sam sees the message first. She screenshots it and sends it to Maya with no comment. The screenshot is the comment.
Maya reads it in the Perth office, standing at the kitchen counter with a cup of tea going cold in her hand. She reads it three times.
The Tuesday interviews – the weekly customer conversations that Charlotte formalised into GreenBox’s continuous discovery cadence – are the single most important practice in the company. They’re the reason GreenBox pivoted from local-only to two-tier pricing. They’re the reason the recipe cards exist. They’re the reason the substitution engine catches preference patterns that no algorithm would find on its own. They’re the practice that connects GreenBox to the people who pay $20 or $25 a week for a box of vegetables.
And a Brisbane developer thinks they’re optional.
Maya’s first instinct is to message Liam directly. To explain the history. To tell him about Greg, the hostile churned subscriber who said “I switched to Freshly” and gave GreenBox its most actionable insight. To tell him about Mrs Patterson, who said “I’ve never met any of you, but I feel like you know me.” To tell him that the Tuesday interviews aren’t a process – they’re the soul of the company.
She doesn’t send the message. Instead, she sits down and thinks about why Liam doesn’t know any of this.
Cultural entropy
Charlotte has a name for what’s happening: cultural entropy. The natural decay of shared understanding when new people join faster than culture can absorb them.
She explains it to Maya on a video call that evening. Charlotte is at home in the northern suburbs – Maya can hear Max and Ollie arguing about something in the background, and James’s voice intervening with the patient firmness of a quantity surveyor who has measured everything, including his tolerance.
“Every organisation has a culture,” Charlotte says. “At five people, it’s implicit. Everyone was in the room when the decisions were made. Everyone knows why things are done the way they’re done. At twenty-five people, it starts to thin. Half the people were in the room. The other half learned by osmosis – working alongside people who knew, picking it up through conversation and example.”
“At eighty people across eight cities, osmosis doesn’t work. Liam wasn’t in the room. He wasn’t even in the same state as the room. He learned the Tuesday interviews from a process document that says ‘conduct one customer interview per week.’ The document tells him what. It doesn’t tell him why.”
Maya thinks about the Event Storm photos on the Perth office wall. The laminated sticky notes. The photo of Tom with his arms crossed and Lee pointing at the whiteboard. The photo of Dave looking sceptical. These aren’t decorations. They’re cultural artefacts from a time when the whole company was five people and a wall.
“The people in Perth and Melbourne understand the culture because they lived it,” Maya says. “The people in Brisbane, Adelaide, Sydney – they inherited the process but not the purpose.”
“That’s exactly right. They’re doing discovery as ritual, not as practice.”
Dunbar’s problem
The Tuesday interview issue is a symptom. The disease is scale.
Diane, who’s been advising on the national expansion from Sydney, puts it in biological terms. “Robin Dunbar – the anthropologist – proposed that humans can maintain about 150 stable social relationships. The actual number varies, but the principle is that there’s a cognitive limit to how many people you can truly know. Below that limit, you can maintain relationships through direct interaction. Above it, you need systems.”
GreenBox has eighty people. That’s below Dunbar’s number for the company as a whole. But the meaningful number isn’t total headcount – it’s the number of people any individual works with closely enough to absorb the culture. For the Perth team, that number is shrinking. For the Brisbane, Adelaide, and Sydney teams, it was never large to begin with.
“When I scaled Sunridge,” Diane says, “we went from 30 people to 180 in two years. By the time we hit 100, I didn’t know everyone’s name. I told myself it didn’t matter – we had processes, we had values on the wall, we had a mission statement. But values on a wall are wallpaper. Culture lives in the choices people make when nobody’s watching.”
“What happened?” Maya asks.
“The Brisbane warehouse started cutting corners on packaging because nobody from head office visited for three months. The Adelaide sales team invented their own pitch because they’d never heard the original one. A customer service rep in Perth told a farmer to ‘take it up with corporate’ – which was me, sitting in a room above a shop in Toowoomba.”
Diane pauses. “That’s when I knew Sunridge’s culture was gone. Not because anyone did anything wrong. Because they did things differently, and nobody noticed, and by the time we noticed, the differences had calcified into separate cultures.”
Maya thinks about Liam’s Slack message. “We already know what customers want.” He’s not wrong – from his perspective. The Brisbane squad has data. They have dashboards. They have the substitution engine and the customer preference profiles. They have so much information about customers that the idea of actually talking to one feels redundant.
But the information isn’t the point. The conversation is the point. The moment when a subscriber says something unexpected – “I stopped cooking on Wednesdays because I started taking my mum to physio” – and the team realises that their assumptions about dinner habits are wrong in a way no dashboard would reveal.
That’s what Liam doesn’t know. Not because he’s incurious. Because nobody told him.
The Brisbane visit
Maya flies to Brisbane the following week. She doesn’t announce it as a cultural intervention. She says she’s visiting the Brisbane squad for a day, joining their standup, sitting in on their sprint review. Normal stuff. CEO visibility.
The Brisbane squad works out of a co-working space in Fortitude Valley. Twelve people – a squad lead (Natalie, hired six months ago from Atlassian), four developers, two operations staff, two customer service reps, a product designer, a farm liaison, and a part-time data analyst. They’re good. The Brisbane metrics are strong – subscriber growth at 12% quarter on quarter, churn at 3.5% (below the national average), delivery reliability at 98.7%.
Maya sits in the back of the standup. It’s efficient – fifteen minutes, everyone reports, Natalie flags blockers, done. The sprint review is thorough – completed work, demos, metrics. Charlotte would approve.
After the sprint review, Maya asks Natalie if she can sit in on the Tuesday interview. Natalie hesitates.
“We actually – we pushed it to Thursday this week. The recipe card redesign is behind and Liam needed the time.”
“You moved the customer interview to accommodate a feature deadline?”
“Just this once.”
Maya doesn’t react. She’s learned – from Lee, from Charlotte, from Ren, from three years of getting it wrong before getting it right – that the response to a cultural gap isn’t anger or disappointment. It’s curiosity.
“Can I join the Thursday session?”
“Of course.”
On Thursday, Maya joins the Brisbane squad’s customer interview. The subscriber is a woman named Deepa, 41, a GP in New Farm who subscribes to the mixed-source box. Liam is conducting the interview because it’s his turn on the rota.
Liam is polite and efficient. He asks the standard questions from the interview template – satisfaction, box contents, delivery experience, any issues. Deepa gives standard answers – everything’s fine, she likes the variety, delivery is reliable.
The interview lasts twelve minutes. Liam wraps it up, thanks Deepa, hangs up the video call. He turns to Maya.
“See? They’re fine. Everything’s fine.”
Maya nods. “Can I ask you something?”
“Sure.”
“What does Deepa do on Wednesday evenings?”
Liam looks confused. “What?”
“Wednesday evenings. The night before the box arrives. What does she do for dinner?”
“I don’t – we didn’t ask that.”
“What does she do with the produce she doesn’t use?”
“I don’t know.”
“Does she cook every night, or does she have nights off?”
“I didn’t ask.”
Maya doesn’t lecture. She tells a story.
“Three years ago, we interviewed a subscriber named Patrick. Standard questions, standard answers – everything was fine. Then Lee – our first coach – asked: ‘What happens to the vegetables you don’t use?’ And Patrick said: ‘I was paying twenty-five dollars a week to feel bad about myself.’ He was throwing out half the box because he didn’t know how to cook kohlrabi and nobody had told him he didn’t have to.”
The room is quiet.
“That one answer changed the company. We added recipe cards. We changed the box composition. We lost Patrick – he’d already churned – but the insight prevented hundreds of other subscribers from churning for the same reason.”
Liam is listening. He’s not defensive – he’s twenty-six and smart enough to know when he’s learning something.
“The standard questions tell you if things are working. The unexpected questions tell you what’s about to break. The Tuesday interviews exist because the dashboards can’t hear what Patrick heard.”
She pauses. “And they happen on Tuesday because Tuesday gives us time to act before Thursday’s delivery. Moving them to Thursday means the insight arrives too late.”
Natalie, the squad lead, has been standing in the doorway. She heard everything. Her expression is complicated – part recognition, part embarrassment, part something else. She was hired from Atlassian, where the processes were mature and the reasons behind them were documented in wikis that nobody read.
“Nobody told us why Tuesday,” Natalie says. “The onboarding doc says ‘customer interviews happen Tuesdays.’ It doesn’t say why Tuesday. It doesn’t say what happened to Patrick.”
Maya looks at her. “That’s my fault.”
The culture problem, defined
Maya calls an all-hands video the following Monday. All eight cities. Eighty people on a Zoom call, most of them in small conference rooms or huddled around laptops in co-working spaces. It’s the first time Maya has spoken to the whole company at once since it was thirty people.
She doesn’t talk about culture. She tells three stories.
The first story is about Dave. The first farm partner. The handshake at the Margaret River farmers’ market. The $8K loss that made him sceptical of anyone promising guaranteed orders. The frost that killed a third of his crop and how GreenBox adjusted the boxes and didn’t miss a delivery. The room goes quiet the way it always does when Dave’s story is told – because it’s a story about trust, and trust is what makes GreenBox different from a logistics company.
The second story is about Mrs Patterson. The Stirling Highway subscriber who hates beetroot. The woman who’s been loyal since week two and who said, in a Tuesday interview, “I’ve never met any of you, but I feel like you know me.” The room is quieter still. Some of the newer team members have never heard this story. They’ve seen Mrs Patterson as a data point in the subscriber dashboard – high LTV, low churn risk, preference flag on beetroot. They’ve never heard her voice.
The third story is about the email Maya almost sent. The one about pausing operations. The one she drafted in her kitchen at midnight after the Business Model Canvas session showed her that the business model she’d built wasn’t sustainable. She didn’t send it. She deleted it. And then she spent two years rebuilding the company on evidence instead of conviction.
“I’m telling you these stories,” Maya says, “because I realised last week that half of you have never heard them. And the practices we follow – the Tuesday interviews, the retros, the Event Storms, the substitution engine – make sense if you know the stories. Without the stories, they’re just processes.”
She pauses. “Processes without purpose become rituals. Rituals without meaning become bureaucracy. I don’t want us to become bureaucratic about the things that matter most.”
The call is silent for a moment. Then Liam, from the Brisbane squad, unmutes his mic.
“Can we – can someone write these stories down? So the next person who joins doesn’t have to hear them by accident?”
Maya smiles. It’s the right question. And she doesn’t have a good answer yet.
Charlotte and Diane disagree
The question of how to codify GreenBox’s culture – how to make the implicit explicit without killing what makes it alive – produces the sharpest disagreement between Charlotte and Diane since the Series B pitch deck.
Charlotte wants to standardise the discovery cadence across all eight cities. The same practices, the same schedule, the same format. Tuesday interviews. Monday assumption checks. Wednesday Example Mapping. Fortnightly retros. Monthly Impact Map reviews. Quarterly theme planning. The planning onion – consistent, repeatable, measurable.
“If the practices vary by city, the quality varies by city,” Charlotte argues. “Brisbane moved the Tuesday interview to Thursday. Adelaide’s retros happen ‘when we have time,’ which means they don’t happen. The Sydney squad is still doing half their work in the Harvest Box system because nobody enforced the migration timeline. If we don’t standardise, we’re running eight different companies.”
Diane pushes back. “You can’t franchise culture. You can standardise a menu at McDonald’s because the menu is the product. Culture isn’t a product. It’s a set of beliefs that express themselves differently depending on context.”
They’re in Maya’s kitchen on a Saturday morning. Nadia has made coffee and left the room – she knows this conversation. She’s heard it before, in different keys, since GreenBox was five people arguing about whether to use sticky notes or a digital board.
Charlotte: “I’m not franchising culture. I’m ensuring that the practices which produce good outcomes are consistently applied.”
Diane: “And I’m telling you that consistently applied practices without local ownership become compliance, not culture. The Brisbane team moved the interview to Thursday because they don’t own the practice. They’re following a rule someone in Perth wrote. If they owned it – if they understood why it mattered and could adapt the format to their context – they’d never move it.”
Charlotte: “Adaptation is how practices degrade. You start with ‘adapt the format’ and end with ‘skip it entirely.’”
Diane: “Rigidity is how practices die. You start with ‘do it exactly this way’ and end with people doing it performatively, checking the box, learning nothing.”
Maya listens. She’s been doing this more – listening to Charlotte and Diane argue, finding the overlap, making the call. It’s the CEO skill she’s been building since the management gap conversation. Not choosing between two experts. Synthesising them.
“You’re both right,” Maya says. “Charlotte is right that the practices need to be consistent enough that we can tell when they’re degrading. Diane is right that the people doing the practices need enough autonomy to make them meaningful.”
She writes on a napkin. Nadia would recognise the handwriting – it’s Maya’s decision handwriting, the one she uses when something is about to become real.
Shared principles. Local implementation.
Three principles, non-negotiable:
- Talk to customers every week.
- Retro every fortnight.
- Plan every quarter.
The format – when, how, who facilitates, what questions are asked – is owned by each city’s squad lead. They can run the interview on Tuesday or Thursday. They can run the retro as a structured exercise or a walking conversation. They can plan the quarter in a day-long workshop or a series of one-hour sessions. But the principles don’t flex.
Charlotte considers this. She’s not fully satisfied – the engineer in her wants more consistency. But she recognises the pattern. It’s the same principle she applied to the bounded contexts in Series 4: define the boundaries, let each context own its implementation. The organisational architecture mirrors the technical architecture. Conway’s Law, again.
“I can work with that,” Charlotte says. “But I want a health check. Monthly. Each squad lead reports: did you talk to customers? What did you learn? Did you retro? What changed? If a city is consistently learning nothing, that’s a signal.”
Diane nods. “A health check I can support. It’s accountability, not control.”
Maya writes “monthly health check” on the napkin and circles it.
Dave’s unexpected role
While Maya, Charlotte, and Diane are debating culture codification, something is happening on the supply side that none of them planned.
Dave Morrison – sixty years old, semi-retired, Ben running the daily farm operations – has started visiting new-city farm partners. Not for operational reasons. For relationship reasons.
It starts in Adelaide. Ben mentions to Maya that the Adelaide farm partners are nervous. They signed contracts with GreenBox three months ago, but they’ve never met anyone from the company face to face. The Perth team visited once during setup. Since then, it’s been emails and portal notifications. The farms deliver produce, get paid, and wonder if anyone on the other end actually cares about what they’re growing.
Dave hears about this from Ben and drives to Adelaide. Not flies – drives. Eight hours across the Nullarbor approach roads in his ute, the same ute he’s had for fifteen years, with the GreenBox bumper sticker that Ben put on it as a joke and Dave never removed.
He visits four farms in two days. He tells the Margaret River frost story – the year the frost killed a third of the crop and GreenBox adjusted the boxes. He tells the $8K story – the scheme that folded and left him $8,000 out of pocket, and why he trusts GreenBox anyway. He listens to the Adelaide farmers’ concerns – the unfamiliar portal, the automated emails, the feeling of being a line item in someone else’s system.
He doesn’t solve the technical problems. He doesn’t promise anything on GreenBox’s behalf. He’s a farmer talking to farmers, and the language he speaks – weather, soil, seasons, the particular anxiety of growing something perishable and trusting someone else to sell it – is a language that no onboarding document can replicate.
The Adelaide farm partners stabilise. Their delivery reliability improves. Their surplus reporting (the data that feeds the substitution engine) becomes more accurate. Ben tells Maya: “Dad’s doing more for farm retention in two days than the portal does in a month.”
Dave doesn’t stop at Adelaide. He visits the Sydney farms – the ones Julian built relationships with, the ones that have been adrift since Julian left. He visits the Brisbane farms. He’s becoming something nobody planned for: the cultural carrier for the supply side of GreenBox. The person who transmits trust, not contracts.
Maya mentions this to Charlotte on a Tuesday call. Charlotte is quiet for a moment.
“That’s not scalable,” Charlotte says.
“No,” Maya agrees. “But it’s real.”
“It’s real and it’s a bus factor. Dave is sixty. If he stops doing this, who does it?”
“Ben. Ben already manages the relationships commercially. Dave adds the – I don’t know what to call it.”
“He adds the story,” Charlotte says. “He’s telling the GreenBox story to people who need to hear it from someone who lived it. That’s not a process. That’s an institution.”
Diane, who has been copied on the email thread, responds with a single line: “Every great company has a Dave. The ones that survive are the ones that figure out what Dave does and make sure it keeps happening after Dave stops.”
Values, written down
The culture work converges over the following three weeks into something concrete. Not a values poster – Maya vetoes the idea of laminated values on the wall (“We’re not a dentist’s office”). Not a culture deck – Diane vetoes the idea of a PDF that new hires read and forget. Something in between.
Jas leads the design. She’s grown into the product lead role over the past year, and culture work turns out to be design work – understanding what people need to feel, creating artefacts that communicate it, testing whether it lands.
Jas interviews fifteen people across all eight cities. Not the leaders – the newest hires, the people who joined in the last three months and experienced GreenBox’s culture as newcomers. She asks two questions: “What surprised you about working here?” and “What do you wish someone had told you in your first week?”
The answers cluster.
What surprised them: The customer interviews are real. People actually change their plans based on what subscribers say. The retros are honest – people say what went wrong and nobody gets punished. The farmers aren’t vendors – they’re partners, with names and stories and farms you can visit. The CEO actually reads Slack messages (Maya: “I do?”). The code reviews aren’t gatekeeping – they’re conversations.
What they wish they’d known: Why the practices exist. The stories behind the processes. That it’s okay to say “I don’t understand why we do this” without being seen as resistant. That the company was built by five people who figured it out as they went, not by experts who knew the answers from the start.
Jas distils this into a document. She doesn’t call it “values” or “culture code” or anything with a corporate suffix. She calls it “How We Work and Why.” It’s four pages. It tells the stories – Dave, Mrs Patterson, the JTBD pivot, the email Maya didn’t send, the substitution engine that started as a spreadsheet and became the technical heart of the company – and connects each story to a practice.
We talk to customers every week because of Patrick, who was paying twenty-five dollars a week to feel bad about himself. We didn’t know until we asked.
We retro every fortnight because the ensemble programming session showed us that the best code comes from the best conversation – and the best conversation requires psychological safety, which requires regularly asking: what’s working and what isn’t?
We plan every quarter because the planning onion – daily, weekly, monthly, quarterly, yearly – is how we connect what we do today to where we’re going. Without the outer rings, the inner rings spin without direction.
The document isn’t perfect. Charlotte thinks it’s too narrative and not enough process. Diane thinks it’s not narrative enough. Tom reads it and sends Jas a single message: “The section about the substitution engine made me feel something. I’m uncomfortable with that. It’s also good.”
Maya reads it and cries. Not in the office. At home, on the kitchen floor, while Nadia cooks. She cries because someone wrote down the things she’s been carrying in her head for three years and the words are right and the stories are real and for the first time, the culture exists outside of her.
“What’s wrong?” Nadia asks, not turning from the stove.
“Nothing’s wrong. Jas wrote – she wrote the thing. The culture thing. And it’s right.”
“Good. Now you can stop worrying about it.”
“I can’t stop worrying about it.”
“I know. But maybe you can worry about it 10% less.”
Maya laughs. It’s a small laugh, the kind that releases something that’s been held too tight for too long.
Hiring for culture-add
The culture document changes how GreenBox hires. Not radically – Sam and the squad leads were already doing structured interviews, following the process from the hiring at scale work. But the interviews were optimised for skill and experience. The culture dimension was “do they seem like a good fit?” – which, as Diane points out, is a question that selects for people who look and sound like the existing team.
“Culture fit is how companies stay small,” Diane says. “You hire people who remind you of yourselves, and the company never becomes more than a bigger version of the founders. Culture-add is how companies grow. You hire people who share your values but bring different perspectives.”
The interview process adds a question borrowed from Jas’s culture research: “Tell me about a time you disagreed with a process at work. What did you do?”
The answers reveal everything. Some candidates say they followed the process anyway – compliance. Some say they ignored it – rebellion. The candidates GreenBox wants are the ones who say they questioned it, understood why it existed, and either accepted the reason or proposed an alternative. That’s the GreenBox pattern: understand why, then decide.
Distributed rituals
The practical question remains: how do you run the practices across eight cities and four time zones?
Charlotte and Natalie (the Brisbane squad lead, who has become an unexpected ally in the culture work since the Tuesday interview incident) design a framework for distributed rituals.
Customer interviews: Each city runs its own, on its own schedule (within the “talk to customers weekly” principle). Insights are shared in a Monday digest – three bullet points per city, posted in #discovery-insights. The digest means every squad knows what every other squad is learning, without requiring synchronous meetings across time zones.
Retros: Each city runs its own, fortnightly, format of their choosing. The output – “what we’re changing” – is posted in #retro-outcomes. Cross-city patterns surface naturally. When three cities independently identify the same problem (the recipe card instructions assume a gas oven, but half the subscribers have induction cooktops), it escalates to the product team without any formal escalation process.
Quarterly planning: This is the one synchronous event. All squad leads, plus Maya, Tom, Sam, Jas, Marcus, Charlotte, and Diane, in one room for one day. Perth hosts. The day follows the planning onion structure: review the year’s strategy, set quarterly themes, cascade to monthly goals. The squad leads carry the themes back to their cities and run local planning sessions.
The quarterly planning day is also, deliberately, the one day a quarter when the leaders are in the same room. Natalie suggests adding a dinner the night before – “not an agenda, just a meal” – and it becomes the most valuable part of the cadence. By the third quarter, the dinner is where the real decisions happen. Not formal decisions – emotional ones. The Brisbane lead mentions she’s struggling with a developer who’s technically excellent but dismissive in retros. The Adelaide lead says he’s worried about farm partner satisfaction scores declining. The Sydney lead (Fiona, who’s moved from developer to squad lead in the four months since the acquisition) says the Harvest Box subscribers still think of themselves as Harvest Box subscribers, not GreenBox subscribers.
These conversations don’t have action items. They have understanding. And understanding, Charlotte concedes, is not something you can put in a spreadsheet.
What Tom sees
Tom has been quiet through most of the culture conversation. He’s not a culture person – he’s an engineer. His contribution to GreenBox has always been architectural: bounded contexts, the substitution engine, the API boundary for the Harvest Box integration.
But the culture work reveals something that he’s been circling for months.
The distributed rituals, the shared principles with local implementation, the bounded contexts in the organisation that mirror the bounded contexts in the code – it’s all the same pattern. Conway’s Law, which he first encountered in the DDD work: the architecture of a system mirrors the communication structure of the organisation that builds it.
GreenBox’s organisational structure – eight semi-autonomous squads, connected by shared principles and a quarterly planning cadence – is producing a technology architecture that matches. The squads own their local systems. The platform connects them. The API boundaries in the code map to the communication boundaries in the org.
This isn’t accidental. It’s the deliberate result of three years of architectural thinking applied to organisation design. But Tom only sees it now, looking at it from the outside, because for three years he was on the inside building it.
He mentions it to Priya on a code review call. “The culture work and the architecture work are the same work. The boundaries in the org are the boundaries in the code. The shared principles in the culture document are the shared interfaces in the platform. Conway’s Law isn’t a bug. It’s a design tool.”
Priya, who has been thinking about this since Melbourne, says: “I’ve been saying that for two years.”
Tom pauses. “You have?”
“The cross-squad integration failure in Two Squads. I said the architecture would mirror the org structure, and if we wanted a different architecture, we needed a different org structure. Charlotte agreed. You told me it was ‘a people problem, not a code problem.’”
Tom winces. “I said that?”
“You did.”
“I was wrong.”
“You were half right. It’s a people problem and a code problem. They’re the same problem.”
Tom texts Sarah that evening: Priya has been right about something for two years and I only just realised it.
Sarah: Just two years? That’s progress.
The culture holds – mostly
By the end of the quarter, the culture work has settled into something real. Not perfect – Diane reminds Maya regularly that “culture is never finished, it’s only ever being built” – but real.
Liam, the Brisbane developer who asked what the point of Tuesday interviews was, runs the best customer interview in the company three weeks after Maya’s visit. He asks a subscriber named Marco about his Wednesday evening routine and discovers that Marco has started a neighbourhood dinner club inspired by the GreenBox recipe cards. Six families, rotating houses, all using the same week’s GreenBox box. Marco has single-handedly created a word-of-mouth channel that’s brought in four new subscribers.
Liam posts the insight in #discovery-insights with a note: “This is why we do the interviews.”
Sam screenshots the message and sends it to Maya. The screenshot is the comment. But this time, it’s a different kind of comment.
The culture document is distributed to all new hires. Not as a required reading – as a welcome gift. Jas had it designed as a small booklet, printed on recycled stock, with Moleskine-style illustrations of the key moments. The Event Storm. The JTBD interviews. Dave at the farmers’ market. The planning onion on the wall. It’s the kind of thing you pick up and read because it looks interesting, not because your onboarding checklist says to.
Three new hires in Adelaide read it during their first week. One of them – a developer named Amara, 29, from Addis Ababa via Melbourne – messages Maya directly.
“I read the culture booklet. I have a question. The story about the email you didn’t send – the one about pausing operations. Was that real?”
Maya replies: “It was real.”
“That’s the bravest thing I’ve ever read in a corporate document.”
Maya sits with that for a moment. She’s not sure “brave” is the right word. At the time, it was terrifying. She was alone in her kitchen at midnight, writing an email to shut down the company she’d built, because the numbers said it might not work. She didn’t send it because she wasn’t ready to give up. And then the continuous discovery cadence showed her a different path.
But Amara is right about one thing: putting it in the culture document was a choice. It said: this company was built by people who didn’t know what they were doing, who almost gave up, who made it work anyway. That’s not a brand story. That’s the truth. And the truth, it turns out, is the most effective culture carrier of all.
What distance teaches
Maya is on the Fremantle waterfront on a Sunday evening. Ren is there, thermos of tea, the bench, the pelicans. The January heat is fading into a warm evening. The fishing boats are in.
“Eighty people,” Maya says. “Eight cities. Half of them have never met me.”
“Does that bother you?”
“It used to. I thought the company needed me to be present for the culture to work. I thought I was the culture.”
“And now?”
“Now I think the culture is the stories. And the stories belong to everyone who tells them. Dave tells them to farmers. Jas wrote them down. Liam is living one in Brisbane that he didn’t know he was living.”
Ren pours tea. The ceramic cup, the one she brings from home.
“When I ran the community organisation,” Ren says, “I had a mentor who told me something I didn’t understand at the time. She said: ‘Your job is to make yourself unnecessary.’ I thought it meant I should delegate. It doesn’t. It means you should build something that carries its own meaning. Something that doesn’t need you to explain it because the explanation is built into the thing itself.”
Maya watches the water. The light is doing the Fremantle thing – gold on blue, the Norfolk pines casting shadows that reach almost to the water.
“I think that’s what the culture document is. It’s not a document. It’s GreenBox explaining itself to itself.”
“Is that enough?”
“I don’t know. Ask me in a year.”
Ren smiles. “I’ll ask you in a quarter. That’s your cadence now, isn’t it?”
Maya laughs. Ren knows the planning onion. Of course she does. She’s been listening to Maya talk about it for three years.
The culture holds. Not perfectly, not uniformly, not in every city in exactly the same way. But the principles are shared. The stories are told. The practices happen because people understand why they matter, not because a process document says they should.
And then Tom calls Maya on a Monday morning and says something she’s been waiting to hear for six months.
“The platform is breaking. We need to talk about the platform (coming February).”