How to Get Employees to Take Ownership: Authorship Equals Ownership

Delegation ·Published October 14, 2026 ·By Kasim Aslam

Every founder I know has said some version of this sentence: I just wish my people would take ownership.

I said it for years. I'd hand someone a project, explain exactly how I wanted it done, check in on it, fix the parts I didn't like, and then complain that nobody on my team thought like an owner.

It took me an embarrassingly long time to see the problem. They weren't refusing ownership. I was never giving it to them. You can't own something somebody else wrote.

You already know your team isn't taking ownership. That's why you searched. So I'm not going to spend this guide on morale, culture decks or engagement surveys. This is the mechanism, the one I teach in the Delegation Mastermind as a single law: authorship equals ownership.

01 · The Cause

Why won't my employees take ownership?

Because you authored the process. When the founder writes the how, the employee is executing your plan, not theirs. If it fails, they did what you told them. If it succeeds, it was still yours. Either way, there's nothing for them to own. Ownership shows up when they write the plan themselves.

Here's the bit most people miss. You'd think the worst outcome of handing over a detailed how-to is that the work comes back bad. It isn't. I put it this way on the call:

"The second worst thing that can happen is it sucks. The first worst thing that can happen is it's actually pretty damn good. Why? Because the resource who's actioning that doesn't feel any ownership over it."

Read that twice. Good work done to your script still trains your team to wait for the next script. You get the output and lose the person.

And it puts all the risk back on you:

"If you author the process, you're the single point of failure. If the process fails, then they get to say, like, I just did what you told me to do."

They're not wrong to say it. You built a system where the honest answer to "why did this go wrong?" is "because that's how you told me to do it."

02 · The Delusion

The SOP delusion: why more documentation makes it worse

Most founders think scaling means building a huge library of SOPs. They spend weekends recording Loom videos and writing step-by-step instructions for everything. I call this the SOP delusion, and it's the most expensive mistake on this list.

"If you provide how-to, you're hiring a pair of hands, not a brain."

A pair of hands used to be worth paying for. It isn't anymore. The hands are getting digitized, and the digital ones are faster, cheaper and never tired. What AI can't do is decide what should be built and why. That's the job of a thoughtful human, and a thoughtful human holding AI tools is unstoppable.

So when you hand someone a 14-step SOP, you're paying a human to be a worse version of a machine. Worse, you're building a fragile system. The moment a variable changes, the SOP breaks, and the person following it has been trained not to think past step 14. So they come back to you. You're the bottleneck again, and now you have documentation to maintain as well.

To be clear, I'm not against documentation. I'm against you writing it. When your assistant designs the workflow and writes the SOP, it gets better, because they're the one who has to live inside it. That's the whole point of this guide.

Here's a line from the first-principles document my team built for this session. I love it:

"Founder freedom is often sought through the delegation of tasks, yet true liberation is only achieved when the founder abdicates the how."

If you've read how to stop being the bottleneck, this is the same disease from the other side. The bottleneck isn't only the decisions you hold. It's the processes you wrote.

03 · The Science

Why people only own what they build: the IKEA effect

There's a name for this in behavioral economics, and it's one of my favorite findings: the IKEA effect.

In 2012, Michael Norton, Daniel Mochon and Dan Ariely published a set of experiments in the Journal of Consumer Psychology. In one, they gave some participants a flat-packed IKEA storage box to assemble and gave others the same box already built. Then they asked both groups what they'd pay for it.

The builders bid an average of 78 cents. The non-builders bid 48 cents. Same box. Roughly 63% more value, just from building it.

In a second experiment, people folded origami frogs and cranes. The people who folded them would pay about 23 cents for their own creation. Strangers would pay about 5 cents for the same piece of crumpled paper. The builders valued their amateur origami almost as highly as strangers valued origami folded by experts.

Source: Norton, Mochon and Ariely, "The IKEA Effect: When Labor Leads to Love," Journal of Consumer Psychology, 2012. Means from Experiments 1A and 1B.

Now apply it to your business. If your assistant designs the workflow, they'll fight to make it work. If you hand them the workflow, a quiet part of them is watching to see it break.

That isn't a character flaw. It's human. And it's usually the better employees who do it, the smart and industrious ones, because pushing back on a plan they didn't choose is the only way they can get their sovereignty back.

The same paper has a finding that matters just as much. The effect disappeared when people failed to finish, or built something and then had it taken apart. Labor only turned into love when the work was completed. So letting them author it isn't enough. You have to let them finish it, and not take it apart in review. Which brings us to the crayon.

04 · The Crayon

How one edit takes ownership away

Think back to being a kid with a coloring book. You're working on a page, and an adult or another kid leans over and adds one stroke. A different shade. A little fix.

How much did it take for that page to stop being yours? For me, one crayon tap. That was it. It wasn't mine anymore.

Your team works the same way, and founders are the worst offenders. Somebody hands you a finished piece of work and you say: change the red to blue, make the circle a square, move that line. Every one of those notes tells them the same thing. This is mine now. Any logical person, you included, responds the same way: fine, you're driving.

I've done it more times than I can count. Recently, a newer member of one of my teams built a full client dashboard nobody had asked for. Reputation audit, topical authority, content engine, all of it, already working. All we'd told him was the goal: make our clients authorities in their space through content. He understood the assignment and built something better than I would have specced.

For the first ten years of my career, I know exactly what I'd have done next. I'd have said: love it, but change these icons, and move this section up top. And I'd have sucked the soul right out of it. Every version after that would have been worse, because he'd be building for my notes instead of for the goal.

What I do now is say "this is amazing," mean it, and ask a goal question if I have one: how do we get this in front of clients faster? Not a pixel question.

There's a well-known 1998 study by Jeffrey Pfeffer, Robert Cialdini and colleagues on why managers overrate work they've supervised. I cover it in what to delegate to an executive assistant. The short version: your urge to touch the work feels like quality control. Mostly it's your own IKEA effect.

05 · The Control

You're not losing control. You're upgrading it.

This is where founders push back hardest. If I stop dictating the how, I lose control.

You don't. You move up a level. Here's a story I heard from Perry Belcher about General Douglas MacArthur. I'm quoting a quote, so the details may be off, but the point isn't.

MacArthur goes to the Army Corps of Engineers and says, "I need the tanks across the river by next week."

"Great. So, build a bridge?"

"Tanks. Across the river. Next week."

"So, a tunnel?"

"Tanks across the river."

Bridge, tunnel, boats, fly them over: not his business. He's the general. He names the outcome. The engineers own the how.

"You're not losing control. You're elevating your control, you're upgrading your control, and you're building yourself an army."

The veto list is what makes this safe. If you're a grammar perfectionist and you can't let it go, fine: make it an input. "Everything customer-facing goes through Grammarly before it ships." That's a standard given in advance, not a red pen after the fact. What kills ownership is the surprise critique, someone going through finished work like a middle-school teacher.

"If they offer the plan, they own the result. That's sovereignty."

The mechanics of handing over inputs and outputs while staying out of the middle are in how to delegate without micromanaging. That guide is the how of the handoff. This one is about why the handoff only works if the plan is theirs.

06 · The Review

Critique the output, and the critique is usually an apology

Once the work comes back, the rule is simple:

"Your job isn't to critique the system. Your job is to critique the output."

And only critique what is objectively true. Taste doesn't count. "I'd have used blue" doesn't count.

Here's the uncomfortable part. If you're honest with yourself, most objective critiques mean you failed on the input. Say the wall studs need to be 18 inches apart or the inspector fails the building. Fair critique. So why wasn't that in the brief?

That's why everyone who works for me knows this:

"If I have a critique, it's an apology."

It sounds like this: "I'm so sorry, I screwed up. I should have told you all our traffic is mobile. What you built is lovely on desktop, but on my phone it isn't engaging. Can you look at it from a mobile perspective?"

Notice what's missing. I don't tell them how to make it work on mobile. I give them the principle they were missing and let them solve it. If you know the answer for a fact, the worst thing you can do is give it to them. The best thing is a question that leads them there. Many times they'll get somewhere better than where you were pointing.

Assume the person doing the job knows more than you

I need to confess one, because I still get this wrong. I ran paid ads for about 15 years. Fifteen years ago, dark websites underperformed light ones. That was a statistical truism, and I made client after client switch.

My business partner sent me a beautiful new website on a dark background. I loved it, sent a couple of notes, and added: "I think we should switch to light, dark websites underperform." He came back with three specific, current data points showing why dark was the right call for what we were measuring.

I was judging his work by the wrong rubric and with 15-year-old data. And I'm the guy teaching this. Take yourself out of anything subjective, and assume the person doing the job knows better than you.

07 · The Phrase

"I trust you": what to say when they ask how

Your new rule. When your assistant or anyone on your team asks "how should I do this?", your answer is:

"Dude, I trust you."

That's my favorite phrase in business. Its siblings: "That's your decision." "Show me your version." "You're the author of this."

Two warnings come with it.

It has to be true. If you don't trust them, that's a heart check. Go figure out why. Have you not given them enough chances to earn it? That's on you. Have they lost it? That's on them, and you need a different conversation.

Some people need coaxing out. Depending on where someone has worked before, they may have been punished for every creative move they ever made. One of the best people I've ever worked with was an assistant in the Philippines. At first she wouldn't do anything outside the lines. Once she realized I really meant it, that she could build anything, she built our entire Airtable setup from the ground up. It became the most important part of our tech stack. She was brilliant the whole time. She just needed to learn that I trusted her first.

"Ownership, by the way, from an employee's perspective, is not taken, it's given."

You can tell someone "I need you to manage me." Good sentiment. But if you then rip the reins out of their hands every time they pick them up, how many times before they stop reaching? You'd have to be a little crazy to keep trying.

Expect less than perfect, and ship it

When the first version comes back at around 70% of what you pictured, that's a win. It's the same idea behind delegate messy and Parkinson's Law, two of the seven laws in the founder's guide to delegation: good enough, shipped today, beats perfect next week.

"The C-minus student that ships every day in this environment … beats the A-plus student who optimizes and takes a week."

And that 70% is by your subjective scoring. I'd bet money the person doing the job knows something you don't.

One caveat. Don't tell them "this is a C-minus, good enough." Labels like that demotivate. Accept the work, say what's good about it, and move forward.

08 · The Filter

Hire for will, train for skill

In the Mastermind, a founder asked the obvious question. Some of my people have the skill but not the will. Others have the will but not the skill. What do I do with each?

I'm blunt about this. Skill you can teach. Will you can't. My cousin, one of the best people-managers I've ever known, gave me the mantra:

"You hire for will, you train for skill."

If someone has the will but not the skills yet, they're extraordinarily valuable. Hand them authorship and they'll grow into it. If someone doesn't care, no amount of "I trust you" will make them an owner. I'm not a babysitter, and you shouldn't be either.

Watch for one pattern. Will tends to drop as skill rises. I had a man work for me who had more drive than anyone I'd ever met. He got so good at the work that he got a little famous, and his will fell off a cliff. He became hard to work with. We're still friends. I wouldn't work with him again.

When I see will dropping, I get on a call and ask straight out: "Do you still want to do this?" Sometimes the honest answer is that they've outgrown the role. Then it might be my failure: I'm asking the point guard to take out the trash. So I ask if I can level them up, or help them start their own thing. A loss of will always gets addressed. It never gets ignored.

And this is the brutal part of authorship. Some people can't do it. You say "I'm not going to tell you how," and they freeze. In a post-AI economy, a person who can only follow the path is doing a partial job that software can now do fully. You want people who build the road. Not all of the road (that's what the 262 rule in what to delegate to an executive assistant is for), but some of it, beyond what you expected. If you're hiring, test for this before the offer. A real work sample shows it, and an interview almost never does. I explain the test in how to vet a remote executive assistant.

09 · The Fuel

Say it out loud when it's good

Here's the part I got wrong for years, and it nearly cost me one of the best people I ever had.

A young man who worked for me built my old Montessori marketing agency from scratch. It took him about nine months: courses, community, all of it, done carefully and with real intent. Then one day he came to me and said he wanted to quit. He felt like he was failing and couldn't keep failing.

I was stunned. I'd been head-down on another business, and when his updates came in I'd reply "good job, thanks." Inside, I was blown away. I just never said so.

My business partner had nearly the same experience with a project manager. She was brilliant, and a few months in she told him she didn't think she could do the job. It was imposter syndrome: a couple of unhappy clients had convinced her she was the problem, when she wasn't. He asked her to give it one more month. A year later she was still there, doing better than ever.

"Bad employers can really kill good employees. As a matter of fact, good employees die first."

Mediocre employees survive bad management because they get pragmatic. The ones who care about excellence are the ones whose drive dies first. They tend to be the most self-critical people on your team, which is exactly why they look like they need encouragement least.

So I over-correct now. I never fake praise. If I'm not happy, I say so. But when I'm happy, I'm aggressive about it. When that team member sent me the dashboard, I wrote back that same day: this is unbelievable, I'm so proud of you.

Authorship without encouragement is lonely. Encouragement is the padding that makes it feel safe to own something.

10 · The Reset

Already trained them to wait for instructions? Reset it

If you've been writing the how for months, your team has learned to wait for it. Those habits aren't permanent, but they've hardened, and breaking them takes time and trust.

The fastest way through is to say it plainly:

"I want you to know I've made a mistake, and I'm sorry. I've been telling you how to do everything, and that's on me. I'm going to change how I work. From now on I'll give you the goal and the limits, and the how is yours. Can we hit the refresh button?"

This isn't just for your executive assistant. It goes for everyone who works for you. You're not getting the most out of anyone you haven't allowed to author something.

Then start small. Pick one project, give it over completely, and resist the crayon when it comes back.

11 · Free Tools

Two prompts to stop authoring the process

These are the two exercises from the session. Paste them into ChatGPT or Claude. For better results, give the AI your company values or first-principles notes too, so its suggestions sound like your business.

You won't run the detox on every message. Use it on the big ones: projects, new responsibilities, anything you'd normally explain for twenty minutes. What most founders find is that it's a relief. You end up writing less. Less context, less how-to, and more "here's what my world looks like if this goes perfectly."

12 · The Short Version

So how do you get employees to take ownership?

Here's the order I'd use, starting this week.

1. Stop writing the how. No step-by-step, no named tools, no recorded walkthrough of the way you'd do it.
2. Hand over inputs and an outcome. The goal, the resources, the budget, the constraints, and what success looks like.
3. Name your veto list up front. Two or three things you'd genuinely reject. Everything else is theirs.
4. Answer "how?" with "I trust you." And make sure it's true.
5. Let them finish. Labor only becomes ownership when the work is completed. Don't take it apart halfway.
6. Critique only what's objective, and treat most critiques as an apology for a missing input.
7. Say it out loud when it's good. Your best people need it most.
8. Hire for will. Train the skill. Address any drop in will the week you see it.

Do that and the sentence changes. You stop saying I wish my people would take ownership and start saying I didn't even ask for that. It's the same shift at the center of how to delegate as a founder: it was never about handing off tasks. It's about handing off the thinking.

Frequently asked questions

Sources

Sources

• Kasim Aslam, Delegation Mastermind session "Authorship = Ownership", March 20, 2026: the SOP delusion, the veto list, "I trust you", the critique-as-apology rule, the sovereignty brief and micromanagement detox exercises, and the quotes on this page.
• Michael I. Norton, Daniel Mochon and Dan Ariely, "The 'IKEA Effect': When Labor Leads to Love", Harvard Business School Working Paper 11-091 (2011), published in the Journal of Consumer Psychology 22(3), 2012. Box bids: builders $0.78, non-builders $0.48 (Experiment 1A, N = 52). Origami bids: builders $0.23, non-builders $0.05, expert-made $0.27 (Experiment 1B, N = 106). Opened October 14, 2026.
• Jeffrey Pfeffer, Robert Cialdini, Benjamin Hanna and Kathleen Knopoff, "Faith in Supervision and the Self-Enhancement Bias: Two Psychological Reasons Why Managers Don't Empower Workers," Basic and Applied Social Psychology, 1998.
• Pareto Talent: 100+ founders served, 40+ hours of training per Right Hand, first candidate profiles within 24 hours (company records, October 2026).

Written by Kasim Aslam from his own experience and the Delegation Mastermind. Reviewed and updated quarterly.