The Org Chart Won't Save You

Why declared ownership never sticks, and the three-step framework that actually transfers responsibility to your team

Every founder eventually hits the same problem. Things keep falling through the cracks. A customer complaint goes unanswered for a week because nobody actually owns customer support. A vendor invoice gets paid twice because two people thought they handled it. A hire gets botched because nobody owns the offer letter process.

The standard founder response is to open a spreadsheet. Make a list of every function in the business. Assign a name to each one. Send it around. Done.

Six weeks later, the same things are still falling through the cracks. The spreadsheet doesn’t fix anything because the spreadsheet is a top-down assignment. You’re declaring ownership instead of building it. And declared ownership doesn’t stick.

The opt-in problem

Real ownership has to be chosen, not assigned. If you tell someone, “You own customer support now,” what you’ve actually done is give them a new task on their plate. They didn’t ask for it. They didn’t define it. They might not even agree that it’s the most important thing for them to be doing. You also haven’t agreed on what success looks like.

You’ve created the appearance of ownership without any of the substance. They’ll do it for a while because you said so. They’ll let it slip the first time something more urgent comes along. And when it slips, they won’t feel wholly responsible, because deep down they never opted in.

Compare that to a team member who takes initiative and says “I want to own customer support, here’s how I’d structure it, here’s what I’ll measure.” That person is going to fight for their function. They proposed it. They defined it. They own it.

The difference isn’t the words on the spreadsheet. It’s whether the person on the other end actually agreed to the mission.

Describe the box, draw the box, fill the box

Here’s a helpful framework that Charles has been teaching for years: three steps to handing off ownership of any function or process.

1. Describe the box. This is the leader’s job. You name the high-level functional area. “We need someone owning customer support.” “We need someone owning finance.” Big shapes, no detail. You’ll need to do this for every major function in the company. This becomes the outline of your Area of Responsibility registry.

2. Draw the box. This is where you define the boundaries. What’s in scope, what’s not, how it connects to the rest of the business. Early on, you as the founder may have to draw the boxes yourself because nobody else has enough context. As the team matures, the team draws the boxes.

3. Fill the box. This is the specific detail. What does this function actually do day-to-day? What does success look like? What metrics matter? The leader should never fill the box. That has to be the eventual owner’s work, every time. They may need your help at first, but you should never do it for them.

Most founders mess this up by doing all three steps themselves and then handing the finished package to someone. “Here’s what you own, here’s what’s in scope, here’s what you’ll be measured on.” It feels efficient. It feels like leadership. And it produces zero ownership.

The discipline is to describe, draw if you need to, and then stop. Let the team fill it in. Be ready for their first attempt to be way off. Don’t just fix it for them. Get curious. Ask questions. Help them see what they missed without telling them the answer.

Then comes the hard part

Mapping ownership across the business is a lot of work. Most founders underestimate how long it takes. But the harder part is what comes after. The follow-up.

Without a consistent cadence of review, the Area of Responsibility registry becomes a museum piece. Something that lives in a Notion doc nobody opens. The follow-up takes as much effort as the initial mapping, sometimes more.

The cadence that works is layered: weekly staff meetings, one-on-ones for details, monthly check-ins on the quarterly goals. Quarterly one-on-one performance reviews where each owner walks through how their area is performing against the metrics they set themselves.

OKR-style goal calibration helps here. Aim for around 70% completion on goals. If your team is hitting 100%, the goals are too soft. If the team is hitting 30%, they’re too hard and people get demoralized. 70-80% means everyone is stretching and pushing forward.

The pattern under all of this

We write a lot about ownership culture, and you might be noticing the pattern. Alignment, accountability, autonomy. Mission, metrics, areas of responsibility. Different angles, same core idea.

The work isn’t telling your team what to do. The work is building the conditions where they tell you, and then holding them to what they said.

Describe the box. Let them fill it in. Then check in, every week, every month, every quarter, until the system runs itself.