Culture Is Not Written Down. It Is Told: The Three Stories That Scale a Business
I have never seen a new hire been given a culture handbook and watched them actually absorb who/what/why the company is. It does not work that way. Culture does not travel through documents. It travels through stories, and this why we have onboarding, intro sessions and training.
If you are scaling a business right now, this distinction is not a nice philosophical observation. It is an operational problem with real consequences.
The moment you grow past the point where every person on your team has direct access to you, the stories circulating inside your organization become the culture. Not the values on the wall. Not the slide deck from your last all-hands and round tables. The stories people tell each other when you are not in the room. Get those right, and culture scales. Get them wrong, or worse, leave them to chance, and the culture you worked so hard to build quietly dissolves as headcount grows.
Here is the framework I use to think about this, grounded in what I have actually lived.
The Three Stories Every Organization Runs On
There are three types of stories that build and sustain culture inside a team. Most leaders obsess over one of them and can completely neglect the other two. That imbalance is usually where culture quietly dies during scaling.
The first is the founding story.
This is the story of why the team exists. What problem are you here to solve, and why does it matter enough to lose sleep over? A founding story is not a mission statement. It is a felt sense of purpose that makes people want to show up. When it is right, it answers the question every person on your team is quietly asking before they fully commit: do I actually believe in what we are building?
The second is the crisis story.
This is the one most leaders underestimate. When something goes wrong, and something always goes wrong, the way a leader shows up in that moment becomes a story. Fast. And that story spreads faster than any memo you will ever write. It answers the deeper question everyone on your team is asking: will this person have my back when it actually matters? (My numerous teams know this, and they have learned the importance of communication within our team and organization.)
The third is the everyday story.
This is the one almost everyone neglects entirely. The small repeated moments. The rituals. The habits that seem insignificant in isolation but accumulate over time into a team's sense of identity. These are the stories that answer the quietest question of all: who are we, really, when nobody is watching?
Miss the everyday stories, and the founding story becomes a relic. Miss the crisis stories, and trust erodes the moment pressure shows up. Miss any one of the three, and you are building culture on a shaky foundation.
What My Karachi Role Actually Taught Me About This
When I was scaling an office from a small team to a much larger one, I was not thinking about storytelling. I was thinking about getting shit done. Hiring, onboarding, clients, timelines. The usual chaos of rapid growth.
But looking back, what built that culture was not any process I deliberately designed. It was the moments that became stories.
There was a moment early on when something went wrong with a client. We showed up within hours. Not with a report, not with an email, with people physically present and ready to sort it out. That moment became a story. And that story told every person on that team something that no onboarding document ever could: this is how we handle things here. We show up.
There were the garden sessions, the chai conversations with field staff, the food that was always present whenever anyone visited. These were not perks. They were rituals. And rituals generate stories. The new person who joined six months later did not witness those early moments firsthand, but they heard about them. And those stories shaped how they behaved before anyone told them what the expectations were….and there were a lot of them.
That is the mechanism. Stories travel faster than memos, stick longer than training sessions, and carry emotional weight that a framework on a slide deck simply cannot replicate. The lesson from Karachi was not that culture is about being warm or generous. It is that you have to engineer the moments that become the stories, because those stories become the culture whether you intended them to or not.
The risk during rapid scaling is that the founding story gets diluted as you grow. New people arrive faster than the culture can absorb them. And if you have not built enough everyday rituals generating enough small stories, those new team members have nothing to anchor to. They fill the vacuum with their own assumptions. And that is when alignment cracks.
What TrendiTech Proved About the Founding Story
If Karachi showed me how storytelling builds culture from the inside, Trendy showed me what happens when a founding story works from the outside.
Trendy was an agri-tech company built around a simple, gutting idea: we grow food, and then we waste half of it, while people go hungry. The founding story was not about technology or market size. It was about not being able to finish your meal knowing how much was lost before it ever reached the table. It was about optimization as a moral act. About feeding people because we already had what we needed and were just failing to use it well.
That story raised $10+ million.
Not because the pitch deck was perfect. Because the values inside that story resonated with the people in the room. The founders were not selling a product. They were inviting people into a mission. And when a founding story is that clear, that felt, that human, it does not just attract investment. It attracts the right people, the right partners, the right talent, all of whom then become carriers of that story inside the organization.
That is the compounding effect nobody talks about. A great founding story does not just open doors. It becomes the first layer of culture, the one that everything else gets built on top of.
The contrast between Trendy and the companies that raise on numbers alone is instructive. Numbers tell people what. A story tells people why. And it is the why that gets people to fucking execute, especially when things get hard, which they will.
Engineer the Moments. Let the Stories Do the Work.
Here is the practical takeaway from all of this.
You cannot mandate culture into existence. You can document it, sure. You can put it on the wall. But the culture that actually governs how your team behaves when you are not in the room is the one transmitted through the stories they are already telling each other.
So the question is not "how do I write a better values document?" The question is: what moments am I creating that are worth talking about?
- Does your founding story answer the why clearly enough that a new hire could tell it to their family at dinner?
- When the last crisis hit, did your team walk away with a story that built trust, or one that quietly eroded it?
- What are the rituals, the small repeated acts, that accumulate into your team's sense of who they are?
If you can answer all three of those, you have got the raw material of a culture that can actually scale. If you cannot, that is your gap. Not the market. Not the product. The stories circulating inside your business right now are either doing the work for you or working against you.
Start there. Engineer the moments. The stories will take care of themselves.
Toodles for now.