I believed control meant caring

I've been doing digital archaeology for the past few weeks. Digging through old emails from a decade ago. Financial spreadsheets from twenty years back. Confluence pages from five years ago. JIRA artifacts. Looking for pieces of memory I've lost. There's something weird about memory... I remember emotions vividly. Some moments are so clear it's like I lived them yesterday. But the facts? The sequence of events? The actual decisions that led to outcomes? Those blur over time. We fill in gaps, rewrite narratives, smooth out the sharp edges.

‍

I started these excavations because Claude suggested a few methodologies for unpacking memory when I realized I couldn't remember crucial details. So now I'm building a complete timeline of my agency — the path, the decisions, the scars, the mistakes. And looking at this map, several critical turning points jump out. I found an Excel file from 2004. Back when I was still a freelancer. Before the agency, before partnerships, before I understood anything about business or finance. Just me, tracking income, expenses, clients, payments in a makeshift CRM and accounting system I'd built intuitively because I knew I needed to keep track of something.

‍

I opened the file and stared at those rows for a while. Simple. Clean. Just me and the work. And then, in my mind, I saw a different scene entirely.

‍

I'm standing at a window in our first real office. It's 2012, maybe early 2013. The office is modest — an old Soviet-era factory building converted into office spaces, tucked in an industrial zone. There's a park nearby, abandoned and overgrown, but still beautiful in a forgotten kind of way. I'm standing at this window, next to the desk of our first sales hire. A young woman, maybe in her early twenties. She's going through leads, drafting messages, showing me responses. We do this almost every day for three months. I'm teaching her, checking her work, discussing strategy. Who to target, what to write, how to position us. She asks questions. I give answers. We iterate.

‍

I loved those conversations.

‍

I told myself it was mentorship. Leadership. Making sure things were done right. But really? I loved being needed.

‍

What I loved about being needed

‍

Around that same time, I read a book that cracked something open for me. Ichak Adizes, Managing Corporate Lifecycles. It walks through the stages companies go through: infancy, go-go, adolescence, prime, stability, aristocracy, bureaucracy, death. I wasn't reading it because I felt trapped. I read it and saw a map. I saw where I was — infancy, maybe edging into go-go — and what I needed to do to move forward. Systems. Structure. The PEI matrix: who does what, where my zone of genius actually is, who else I need. For the first time, I understood: I was the bottleneck. Not because I wasn't working hard enough. Because everything flowed through me.

‍

But here's what I didn't understand yet... I liked being the bottleneck. Standing at that window every day, talking through every decision with my sales hire, feeling essential to every deal — that felt like leadership. It felt like I cared.

‍

By 2014, we started opening offices in other cities. New hires in places I couldn't visit every week. Managers running teams I couldn't see daily. And that's when I realized — looking back years later, not in the moment — that I'd loved the chaos. Not because it was efficient. Because it made me feel important. When everyone needed me to make decisions, when nothing moved forward without my input, when I was at the center of every conversation — I felt like I was building something meaningful. But what I was actually building was a bottleneck with my name on it.

‍

When the offices spread out and I couldn't physically be in every room, couldn't stand at every window and review every message — that's when I had to let go. Not because I wanted to. Because I had to.

‍

A few weeks ago, I was talking to a founder who runs a small marketing agency. Social media management, ad campaigns for clients. Eight people on his team. He told me about his daily routine: Zoom calls every morning, going through every client, every campaign, every decision. His team gathers information, proposes ideas. But he makes the call. Every time.

‍

"I want to understand what we're doing and why," he said. "I need to know."

And I saw it — his eyes lit up when he talked about those calls. The same way mine used to.

He wasn't describing a problem. He was describing what made him feel valuable. I recognized it instantly. Because I'd been him. Standing at that window in 2013, feeling indispensable, thinking that was what caring looked like.

‍

What changed when I let go

‍

We started building what I later learned to call a decision ladder. It happened organically around 2015, when we had offices in multiple cities and countries. I couldn't be everywhere. So we had to define: what decisions could office managers make locally? What required escalation? It started small. Office expenses. Team events. Budgets for local spending. Then it expanded.

‍

Sales team: which leads to pursue, what tools to buy, how to allocate their CRM budget — all within agreed parameters.

IT department: servers, cloud infrastructure, configurations, equipment purchases — within their budget and authority.

Project managers: which freelancers to bring on, how to staff projects, when to push back on scope creep — within defined thresholds.

‍

The pattern was simple. If the cost of a wrong decision wasn't catastrophic — if it didn't risk the client relationship, our reputation, legal issues, or something we couldn't quickly fix — it didn't need to come to me.

‍

And here's what shocked me... things didn't fall apart. They got better.

‍

Not because I wasn't involved. I just stopped being the gate everything had to pass through. People started proposing solutions, not just problems. They started thinking like owners of their domain, not employees waiting for instructions. And the warmth I'd been so afraid of losing by adding structure didn't disappear. It deepened. Now my people had clarity. They knew what they were responsible for. They had authority to act. They weren't afraid to make the wrong call because we'd defined what "wrong" actually meant.

‍

Structure didn't kill the culture. It gave the culture room to breathe.

‍

I see this pattern everywhere now. Founders who believe that their value comes from being in every conversation. That delegation means caring less. That structure will somehow make things cold and mechanical. But the opposite is true. When you're the bottleneck, people stop thinking for themselves. They wait for you. They bring you problems because that's their job — to escalate, not to solve. When you build a system where people know what they're empowered to decide, they start acting like the leaders you need them to be.

‍

And you? You get to do the work only you can do. The strategic stuff. The direction-setting. The culture-building. Not reviewing every email your sales team sends.

‍

Here's what you can do this week:

‍

Sit down and write out every decision you made in the past week. Everything. Big, small, trivial, important. Then for each one, ask: What would happen if someone else made this decision and got it wrong?

If the answer is "we could fix it quickly without major damage" — that's a decision you should delegate. Write down who on your team should own that decision. Not "help with" or "contribute to." Own.

‍

Then tell them. Give them the authority. Define the boundaries: budget limits, client relationship thresholds, whatever matters. But make it clear: inside these boundaries, this is theirs.

‍

Start with one. Just one decision type you currently own that doesn't need you. Watch what happens when you let go.

‍

So here's the question I've been thinking: What decision are you holding onto because letting go feels like you'd be caring less? Hit reply and tell me. I read every response, and we love hearing from you.

‍

P.S. That Excel file from 2004 reminded me of something I'd forgotten. Back then, when it was just me, I made every decision because I had to. But I didn't confuse that with caring. I knew the difference. Somewhere along the way, I forgot. Building structure isn't about caring less. It's about caring enough to build something that doesn't need you to be everywhere at once.