Your Marketing Team Doesn't Have a Copy Problem. It Has a Question Problem.

The blunder was mine

In July 2026 I was running the marketing lane for TrueMD, a three-founder venture. My team was building its LinkedIn presence and the assets to go with it.

Then work started getting dropped. Assets started landing that made no sense. Not badly made. Wrong. The kind of wrong where you look at the work and think, who did you think we were?

I traced it back. Most of my team had never been told what TrueMD actually is. A subset knew. I had assumed everyone did.

That is not a team problem. That is a leader problem, and it was mine.

I had delegated tasks. I had not delegated the thinking. A team without the thinking produces confident work aimed at the wrong target every time, and they feel good about it while they do it.

Copy is the output. The question is the job.

Here is the part that should sting. My team did not fail at marketing. They succeeded at a smaller assignment than the one I thought I had given them.

Your team is doing the same thing right now. You ask for copy. They write copy. You ask for a content calendar. You get a content calendar. Every one of those is a task, and every one of them can be completed perfectly while the business gets no closer to a customer.

The volume of copy your team produces measures how busy they are. It tells you nothing about whether anyone asked what the copy was for.

A marketing team that only knows what to make will eventually make the wrong thing. The only question is how many weeks pass before you notice.

What you actually handed over

The framework underneath all of this is Delegation Leadership. It has one line at the center:

Delegate thinking, not tasks.

Most people nod at that and then go write an SOP. Writing the SOP is not delegating thinking. An SOP tells a person what to do when the situation matches the document. Thinking is what they need when it does not match. The situation never matches.

Delegation Leadership: handing over the reasoning that decides what work is worth doing, so the people on your team can choose the work correctly when you are not in the room. The destination is ownership: people who act like the business is theirs, because you gave them enough of it to act on.

Delegation Leadership stands on three things. Vision, openness, and asking great questions. Three legs wearing team-building clothes, and your marketing team lives or dies on all three.

Vision is the thing written down and visible. Plain language, no jargon, in a place every person on the account has actually opened.

Openness is the permission structure. Not the softer word people reach for. Openness means a person can say "I don't know what this is" and still be safe in the room. If they cannot say that, they will nod at the document and go build the wrong asset anyway.

Asking great questions is the leader's real output. Not better answers. Better questions. If the reasoning you hand over never includes a question, you have handed over a procedure and called it delegation.

Now rank them, because they are not equal weight and treating them as equal is how frameworks die on a slide.

Start with vision. It is the precondition for the other two, and it is also the only one you can finish this week, because it is a document, not a personality change. That is the exact gap I found when I traced the dropped work at TrueMD. Nothing downstream could work because nothing upstream had been said.

Openness is second, and it is the one you cannot do alone. You can write the vision by yourself. You cannot grant permission by yourself. It is decided in the first thirty seconds of the first meeting where someone says "I don't actually understand what this is," by what your face does.

Asking great questions never finishes. It is the leg you keep for the rest of your career, and it is the one that costs you your seat as the smartest person in the room. If you only have bandwidth for one thing this month, do vision. If you have bandwidth for two, do vision and then watch yourself the next time someone questions your brief.

Inconsistent delegation vs consistent delegation

The question on the surface is rarely the question

A surgeon in his sixties, an MMR client, was fired from his job as a surgeon. Retirement age in the US is 72, so being fired at sixty left him needing to build something rather than stop. He came to MMR to start his own practice.

Retirement age in the US is 72. He was fired at sixty. That is not a retirement story. That is a build-something-now story, and nobody inside one is thinking clearly about a content calendar.

I was describing the weekly reality of that engagement to a brand-new client success hire. The engagement he signed up for is a marketing programme. Most weeks, the actual work is talking him off the ledge. He arrives convinced the world is falling apart, and the questions he asks are not the ones that need answering.

If we answered the questions he asks, we would service him perfectly. We would also lose him. The thing keeping him from doing the work was never the thing he was asking about.

Here is the turn most people miss. He is not a difficult client. He is a person in a situation. So the job is not to answer the question he asked. The job is to ask the question that lets him keep going.

Which changes who you hire and what you measure. You do not staff that seat for the ticket queue. You staff it with people others find it easy to talk to. And you measure the call on whether he can keep going, not on whether his question got answered.

Now put your marketing team in that chair, and apply the same measurement to them.

They sit in it every week. Someone walks over with a request. Write this. Post that. Build the one-pager. The request arrives with urgency on it and usually something underneath it: a quarter is closing, a competitor shipped something, a founder is worried. Those are the questions your team is being asked. Answer them literally and you get a full content calendar and no customers. Same failure as my July, pointed inward this time.

So measure it the same way you measure the surgeon's calls. Not "did we produce the asset." Ask whether the person who made the request can now make a better decision, and whether the work moved anything. That is also a different hire. You staff marketing with people others find it easy to talk to, because half the job is getting the real question out of someone who does not know they are hiding it.

The awareness test

When someone names awareness as the problem, I do not argue and I do not buy more reach. I ask them to imagine it completely solved. A million people now know the name. What actually changes tomorrow?

Usually the honest answer is nothing, because the missing step was never awareness. Adding a service does not create customers, it creates something else nobody knows exists. A million of the wrong people knowing your name changes nothing about the constraint. And you cannot have a sales conversation without leads, so most sales-conversion answers turn out to be lead answers wearing a better suit.

Run the same test on your team's next request. When they say the problem is more copy, imagine the copy completely written. Every asset done, on brand, on time, nothing outstanding. What actually changes?

If the honest answer is "nothing, because nobody knows who we are for," or "nothing, because the offer is wrong," or "nothing, because we are talking to people who will never buy," then you never had a production problem. You had a question problem, and you were about to pay for it in output.

Why this is harder than it sounds

Nobody tells you what delegating thinking actually feels like. It feels like losing control of the one thing you are best at.

If you write down what the venture is, you might find out you cannot. That is not hypothetical. It is the exact moment waiting for you, and if you are not careful you will hit it after the wrong assets are already built, the way I did.

If you tell your team to ask better questions, the first better question may be aimed at you. If you stop approving every asset, you will spend a month not knowing whether the work is good, and that month will be far more uncomfortable than a full content calendar ever was.

The team pays too. Order-taking is safe. You get a brief, you fill it, you are done, and nobody can say you did it wrong. Asking "what is this actually for?" puts your name on the answer. Some of your people will resist that harder than you expect, and the ones who resist hardest will not be the lazy ones. They will be the ones who got burned before for questioning a brief.

So do not sell this as a process improvement. It is not one. It is a change in what you reward. As long as you reward volume, you will get volume, and you can put "ask better questions" on a slide and your team will read it as "and also ship more."

Two situations where you should not start here. If you are the whole team, skip to the awareness test and come back when you have someone to delegate to. And if you are inside the last two weeks of a launch, do not stop the machine to rewrite the vision. Note it and do it the week after, because a gate your team experiences as one more thing on top of the deadline is not a gate, it is a pile-on.

The Monday decision

Do not reform your department. Take your next project brief and treat it as a gate, not a form. Four lines. Each one has a price, and if nobody has named the price, you will quietly decide not to pay it.

Line 1. What this thing is, in plain language, no jargon. The cost: an afternoon, and the afternoon is the easy part. The hard part is that once it is written, you cannot adjust the story in your head in week three and blame the team for not following it. The fear: you will write it and find out it is fuzzy. That is likely, and it has been costing you assets for months. You just have not had to look at the fuzziness in one paragraph before. The resistance: yours. You will want to add a qualifier, an exception, a caveat, because the plain version feels too small for what you are building. Do not. The team needs the plain version. Then the step I skipped at TrueMD, and the reason this line is not optional: confirm every person working on the thing has read it. Not the subset you happen to speak with. Every person. Ask them to say it back in their own words. If they cannot, the document is not done and neither is the delegation. This is the gate. Everything after it is easier once it is passed, and decoration if it is not.

Line 2. Who it is for, and what they currently believe. The cost: you have to say who it is not for, which means someone's request becomes visible as a request from the wrong audience. The fear: you will find out you have been building for two audiences at once, or for one that does not exist. The resistance: whoever owns the relationship with the other audience will push back this week, and it will arrive sounding like a revenue argument.

Line 3. The one question this work has to answer. The cost: you stop being the person with the answers and become the person with the question, and for most founders that is a demotion in the only currency they have. The fear: you ask the real question and the answer is that the project should not happen. It happens. It is cheaper now than in week eight. The resistance: your team. Filling a brief is safe. Asking the question under it puts their name on the answer, and some of them got burned for that before they met you.

Line 4. What would have to change for us to call this a success, in something other than a count of assets. The cost: you cannot move the goalposts in the retro, and you have to look at whether the thing worked instead of whether everyone was busy. The fear: this is the line that can end a project you have already announced. The resistance: volume is always available. Volume will never refuse you. Whether a person can keep going, whether a decision moved, that requires a conversation, and conversations do not fit in a dashboard.

Then measure the whole thing the way we measure the surgeon's calls. Not "did the team produce." Ask whether the person who asked for the work can keep going now that they have it, and whether anything moved.

The whole argument in one picture

Everything above collapses to one move you can make this week. Write down what the venture is, and do not leave the room until every person working on it has read it and said it back to you in their own words. That is the gate I walked past in July. Your team is not going to tell you they do not know what the company is. They are going to keep making things, confidently, and you are going to keep wondering why the copy is fine and nothing is moving.