Leadership

Delegation Starts With Knowing What You Want

Delegation Starts With Knowing What You Want

If you cannot explain exactly what you want, no one can deliver it. Delegation is not offloading what you dislike, it is collaboration built on clarity, and it costs you decisions, not just money.

Founders forget to delegate, or refuse to, or do not understand how. Part of the reason is a specific trap of the creative mind: when we see something done well, we believe we could do it at least as well ourselves. Look at a website, it seems easy to make. Look at a product, we could build it. Look at a design, or anything else, we could do it. And the truth is, we probably could. The real question is not can we. The question is, do we want to.

Time is the most precious resource in business. Remember that. Time is the one thing you cannot get back. You can make more money, lose it, make it again, but no one gives you time back. So the real question is what you do with it. What percentage of your work do you delegate to others, inside your company or to partners and freelancers, and what percentage do you do yourself, and which parts. That decision is one of the most important you will make.

At the start, when money is tight and resources are thin, it is best to try to manage on your own, with whatever tools and resources you have. There are many design tools that help you produce something better, many marketing tools, especially now with AI, people who will help you almost for free, near-free consultations, YouTube videos full of information at no cost. Your job is to choose. Doing things yourself early on brings two benefits. One, you save money, which means you have more to spend elsewhere. Two, you learn, and learning is another resource people do not take enough advantage of. Understanding things gives you a far clearer picture of how to run the business and how to build the product, which automatically helps you make better decisions. So early on, with a small budget, doing it yourself is usually preferable to delegating.

That second benefit is the one people undervalue, so let me be blunt about it. When you do a thing yourself early on, you are not just saving money, you are buying the knowledge you will need later to delegate it well. You cannot judge a designer's work if you have never wrestled with design. You cannot tell a good marketing hire from a confident one if you have never written a campaign. Doing the work yourself, badly, at the start, is how you earn the judgment to hand it off well at the end. The founders who delegate everything from day one never develop that judgment, and they spend the rest of the company's life unable to tell whether the people they hired are any good.

But there is a hard rule for the moment you do delegate: delegation should never begin without your own knowledge first. Not the other person's knowledge, yours. Studying the market better, studying the plan better, understanding what you actually want to build, all of that helps you understand the nature of your requirements when you delegate. And understanding the nature of your requirements is critical. Otherwise you risk wasting money on things you could have done for free, or things that should not have been done at all.

I have made this mistake. Out of the ego's desire to move faster, to save time, to collect shortcuts, I invested money in partnerships hoping they would speed up my projects. It turned out to be false, because I did not understand from the start what I wanted from those projects. When you delegate, you have to know very clearly what you want. If you do not know clearly what you want, you cannot explain it to others. And if you cannot explain it to others, they will do the work their way. The chances that the work comes out the way you, as the leader, wanted can be small. It depends on the other person's personality, their experience, their knowledge, their knowledge of the project, their intention, their desire within the project.

This is why I think of delegation as collaboration, not offloading. Delegation must come from a place of collaboration, not from a place of I do not want to do this but the books say I must. It should come from a place where the other person can bring their own contribution, in a different but constructive way, and create, even by paths that differ from yours, the things that lead to finishing the project. That framing changes everything, because you stop looking for someone to obey instructions and start looking for someone who can manifest your vision from a simple description.

That last phrase is the whole test of a good partnership. Any good partnership is one in which that partner can manifest your vision from a simple description of yours. Let me give you the counterexample. If I work with a recruitment agency, my condition is that I want to see the last, best candidate, and that is what should happen. What should not happen is that I end up doing their job, refining CVs, talking to people, and arriving at the final result myself. Same with organizing an event. A bad process is when the events agency sends me everything, from arrangements to chair types to every detail imaginable, and I have to sit and choose. That is inefficient, because it eats my time. A truly good process is when I have given you a description of what needs to happen, and you make it happen, with small questions here and there, but without making me the one who chooses. The goal is not for me to sit and choose. The goal is for you to do your job.

I violated my own principle recently, and it cost me. An agency was supposed to do the branding for one of our companies, and I sat with them for seven hours of calls, which was a huge mistake. They asked question after question, very technical, the kind learned in school, too much system, too much structure that has nothing to do with the refinement and finesse a brand actually needs. After seven hours they produced a disastrous mock-up. I ended the collaboration before it went further, paid them part of what we owed because we had to, and walked away. It is good to be ethical and pay your debts, sometimes a little more than you strictly should if you can, because it keeps the door open. And it reminded me again that a successful partnership happens when the people behind it understand what you want to convey and create it without bothering you too much. That saves enormous time, and that is a partnership worth keeping.

There is a cost to delegation that people never see, and it is not money. Things cost decisions, not just money. We tend to oversimplify. When you have a large sum to pay and cannot pay it, the money is not really the problem. The problem is that you will be forced to make decisions to the detriment of your business in order to pay it, decisions that likely lead to delayed success. This is why long-term contracts are dangerous early on. I have negotiated long contracts, and plans change, and a day comes when I no longer need what I signed for, but I still have to pay, and that costs both money and decisions. So especially at the start, keep collaborations temporary, shorten the contract's life as much as possible, and shorten the notice to terminate, so you are never forced to pay for something you no longer need. It keeps you healthy in mind and soul, which is what lets you make the decisions that actually grow the business.

That phrase, things cost decisions, is worth carrying with you, because it reveals the real price of a bad commitment. A payment you cannot afford does not just drain the account. It hijacks your judgment. Suddenly every decision is bent toward covering that obligation, and decisions bent by financial pressure are almost always worse than decisions made freely. You take the client you should have declined, keep the project you should have killed, accept the terms you should have rejected, all to service a commitment that made sense on the day you signed it and does not make sense now. The money is recoverable. The chain of compromised decisions is what actually sets your business back.

One more thing, because it is the failure I see most. We are, generally, complainers. We complain about everything. That partner did it wrong, that employee is not doing their job, the company is not working, there are so many problems, and yet we do nothing about it. We feed our own frustration, because some part of the brain seems to need a constant supply of it. That is a stupidity we should stop. It is fine to complain once or twice, or to say this partner is not working, but complaining to yourself is useless. You have to tell them, kindly and clearly, from the first day, exactly what your expectations are and exactly what final result you are after, in full sentences, in detail, but not restrictively. You do not want to constrain them. You want to explain, precisely, what you expect and what outcome you are chasing. And when you see they are not adapting or cannot meet your expectations, at seventy or eighty or ninety or a hundred percent, depending on your standards, end the collaboration and find someone else.

There is a version of the honeymoon problem that ruins negotiations, and it is worth naming because it is invisible while it happens. When you are in love with your idea, that emotion leaks into every conversation with a potential partner or hire, and experienced people read it instantly. They see the naivety of someone who wants this too much, and, not always out of malice, they price it in, and you end up agreeing to terms worse than you should have. So temper the emotion at the negotiating table. Not because passion is bad, it is the fuel for everything, but because a partner who senses you cannot walk away has already won the negotiation before it starts. Keep the passion for the building. Bring detachment to the deal.

And detachment is possible only if you genuinely believe there is another path, which there almost always is. We get trapped in a negotiation, or a hire, or a partnership, because we have convinced ourselves it is the only way, and that belief hands all the leverage to the other side. Even when it truly is the best option in front of you, act from the knowledge that other paths exist, because that knowledge changes your posture, and your posture changes the terms you get. The person who can walk away negotiates from strength. The person who cannot is not negotiating at all, they are begging politely, and everyone in the room can tell the difference.

So delegation is not the act of getting rid of what you dislike. It is the discipline of knowing what you want so clearly that you can hand it to someone as a description and have it come back as your vision. Do the work yourself long enough to understand it. Delegate from collaboration, not obligation. Keep the collaborations short and reversible early on. State your expectations on day one, in detail. And when someone cannot meet them, stop complaining and change the arrangement. Time is the only resource you never get back. Delegation, done right, is how you buy it. Done wrong, it is how you spend it twice.

← Back to the articles

Newsletter

What we shipped, what broke,
and what we learned