You wouldn't ask your accountant to design your logo and then wonder why it looks terrible. That's obvious. But founders do the equivalent of this constantly, just with more polite framing.
You ask your web developer to handle client communication because they're already on the project. You ask your copywriter to design a banner because surely writing and design are related. Two weeks later, the result is unusable, and you've wasted everyone's time, including your own.
The problem isn't the employee. The problem is the assignment.
Why employees don't perform the way founders expect
When you hire your first few people, there's a temptation to see them as flexible resources. Surely they can stretch. Surely, with a bit of guidance, they can handle more than what they were hired for.
Sometimes they can. But most of the time, asking someone to do something outside their actual skill set produces slow, stressful, expensive results. A developer asked to manage third-party relationships will struggle not because they're bad at their job, but because communication and negotiation are completely different skills from building software.
Employees care about three things: their workload, their pay, and what they're actually learning. They are not thinking about your vision for their growth. That's your vision, not theirs.
Thinking you can shape someone into who you need them to be is not leadership. It's ego. It's the belief that your vision for them matters more than who they actually are. Some founders dress this up as mentorship or investment in people. But if the person didn't ask to grow in that direction, you're not developing them. You're trying to turn them into someone more convenient for you.
"You hired someone to write. Not to present, negotiate, manage relationships, and also write."
What your job actually is when managing your first employees
Your job is not to grow people. If someone is going to grow, they will grow themselves. Your job is to put the right person in the right role and get out of the way.
That means being honest about what each person is actually good at, not what you hope they'll become. A person who is naturally detail-oriented will do excellent work in the right lane. Ask them to be spontaneous and creative, and they'll deliver something mediocre that takes twice as long.
Discover what someone does well and build their tasks around that. Most founders don't do this because they're too busy hoping people will stretch rather than observing where they actually thrive.
When results aren't coming, look at the assignment first
If an employee consistently underdelivers, the first question is not what's wrong with them. It's whether you assigned them something they were ever going to be good at.
This is uncomfortable because it means the responsibility sits with you. You hired them. You assigned the task. If it isn't working, something in that chain needs to change, usually the task, not the person.
That doesn't mean keeping people who genuinely aren't a fit. It means being honest about whether the problem is performance or assignment before drawing conclusions.
How to get the best out of a small team without burning everyone out
Watch what people do when they're not being asked to do anything specific. What do they fix without being told? What do they gravitate toward? That's usually where they're most useful.
Keep task assignments as close to someone's actual strengths as possible. When you need something outside those strengths, hire freelancers specifically for it or outsource rather than stretching the person who's already there.
And lower the expectation of perfection. Getting 50% of what you hoped for from someone genuinely suited to the role is more valuable than getting 5% from someone you've assigned the wrong thing to and told to figure it out.
The goal is not to build people. The goal is to build something. Use the people you have for what they're actually good at and hire for what they're not.
