Most management problems are not skill problems. They are attitude problems. The way you treat the people working for you determines how they work—and over time, it determines whether they stay, grow, and produce results worth having.
These are not theories. They come from running a business that works primarily with freelancers, watching what happens when you give people room, and seeing what happens when you do not.
—
## Treat People With Respect
This should go without saying, but it does not. A lot of managers confuse authority with disrespect. They speak down, interrupt, dismiss, or ignore. Then they wonder why morale is low and output is mediocre.
Respect costs nothing. It does not mean you agree with everything or that you avoid difficult conversations. It means you treat the person in front of you like their time, effort, and opinion have value.
A simple example: someone sends you work they put real effort into. You respond with a one-line dismissal and no explanation. They do not know what was wrong, they feel like they wasted their time, and next time they will put in less effort because the result felt the same either way. Now compare that to taking two minutes to explain what needs to change and why. Same correction, completely different outcome.
When people feel respected, they bring more to the table. When they do not, they do the minimum and wait to be told what to do next.
—
## Give Space for Mistakes
Mistakes happen. If you react to every mistake with frustration or punishment, people stop taking initiative. They do only what they are certain will be approved, which is usually the safest and least creative option available.
Say a freelancer builds something the wrong way. It needs to be redone. Your reaction in that moment sets the tone for everything that follows. If you make it painful, they will never take a risk again — they will check with you before every small decision, which slows everything down and puts the entire mental load back on you. If you treat it as part of the process, they fix it, they understand why, and they rarely make the same mistake twice.
The person who made the mistake and was treated fairly will work harder not to repeat it. The person who was humiliated will spend their energy protecting themselves, not improving.
—
## Listen to Their Ideas and Concerns
People bring ideas and concerns to you because they see something you might not. Even when the idea is not applicable, or the concern does not match your understanding of the situation, listen to it fully before you respond.
Picture this: someone on your team flags that a process is taking too long and suggests a different approach. Your instinct says the current way is fine. You shut it down and move on. Three months later, the same bottleneck causes a delayed delivery. That person saw it coming. They told you. They will not bother telling you the next thing they notice.
You do not have to implement every idea. You do not have to agree with every concern. But you do have to listen — fully, not just long enough to form your rebuttal.
—
## Pay for Lunch Time
If your employees or contractors are on the clock, pay for lunch. This is not a major financial decision. For most businesses, the cost of a paid lunch break across a team is negligible. What it communicates, however, is not negligible at all.
A business that docks lunch breaks is telling its people that every minute must be accounted for and extracted. That message travels. People talk. The reputation you build as someone who watches the clock on a sandwich will cost you more in turnover and morale than the lunch ever would.
The same logic applies to small things across the board — covering a work-related expense without making someone fight for reimbursement, not counting the minutes when someone is five minutes late because their child was sick. These things are small to you and large to them. Get them right and people remember. Get them wrong and they remember that too.
Your business is not going to close because you paid for someone’s lunch break.
—
## Give Them Room to Make Decisions
Micromanagement produces one kind of result: people who stop thinking for themselves. When every small decision has to pass through you, people learn that their judgment does not matter. Over time they stop using it, and you end up doing two jobs — yours and theirs.
If someone is handling the design of a project, let them make the design decisions. If someone is managing a client relationship, let them manage it. Check in, stay available, but step back. You hired them for a reason. Let that reason show up in the work.
The decisions they make may not be identical to the ones you would make. That is not a problem. Different is not wrong. And a person who is trusted to decide shows up differently than one who is managed on every detail.
—
## Trust Their Instincts, Even When You Are Not Sure
At SJ Notebook, the majority of the work runs through freelancers. In practice, when a freelancer made a decision I was not fully comfortable with — a direction I would not have chosen — the result came out better than I expected. That has happened enough times that it is no longer a surprise. It is now the expectation.
There was a project where I would have taken a more structured, conventional approach. The freelancer went a different way — looser, more direct. I let it go. The client responded better to that version than they had to anything previous. I would not have arrived there on my own.
When you bring someone onto a project, you are not just renting their hours. You are accessing their way of seeing the problem. If you override every instinct they have, you get your solution executed by someone else — which defeats the purpose. Let it go. See what happens.
—
## Retrain Without Making It a Confrontation
Not everyone will admit when they do not know something. Some people will push forward, hoping to figure it out as they go. When you notice this — and if you are paying attention, you will notice it — the wrong move is to call it out directly and put them on the spot.
Here is a common version of this: a freelancer is handling a task they said they could manage, but the output shows clearly that they are guessing. You have two options. You can say “I do not think you actually know how to do this.” That conversation ends badly. They get defensive, the relationship takes damage, and you have solved nothing. Or you can sit alongside them, work through it together as a review, ask questions that lead them in the right direction, and introduce the correct approach as if you are both just making sure everything is aligned.
Done the second way, they gain the knowledge. The work improves. They never feel exposed. And the next time they hit something they are unsure about, there is a better chance they will bring it to you instead of hiding it.
—
## Give Them Time to Finish Properly
If a project has a tight deadline, that is usually a planning problem, not the person’s fault. Dropping a rushed project on someone and expecting them to absorb the pressure is not management — it is offloading a problem onto someone who already has a full life outside of your project.
Think about what a tight deadline actually does to the work. Corners get cut. Things get missed. The output is worse than it would have been with a reasonable timeline, which means you will spend time fixing it anyway. The urgency did not save time. It just moved the problem.
If the timeline is genuinely unavoidable, say so honestly, explain why, and work through it together. Remove every obstacle you can. If you are asking someone to move fast, make sure you are not the bottleneck — slow approvals, unclear briefs, and late feedback are the most common reasons projects get delayed, and all of those sit on the manager’s side of the table.
If the pressure is too much for the person handling it, either help them directly or reconsider whether they are the right fit for this particular job. Do not just hand them the stress and hope for the best.
—
## Train Them to Eventually Not Need You
This is the part most managers get wrong. They train people just enough to be useful, and no more. They hold back knowledge because capable people might leave, might compete, or might stop needing to be managed. That thinking is backwards, and it produces a team that never grows.
At SJ Notebook, several freelancers who came in with limited experience now run their own projects entirely. Some have grown their own client base. Some have become fully independent. That outcome is not a loss — it is the goal. When you develop someone to that level, two things happen. First, the quality of work they produce while they are with you is exceptional, because they are operating at their ceiling, not held below it. Second, your reputation as a place where people grow attracts better people to work with you.
A freelancer who left SJ Notebook more capable than they arrived is not a failed hire. They are proof that the environment worked.
Train the people around you as if someday they will not need you at all. The ones who stay will stay because they want to, not because they have no other option. That is the only kind of loyalty worth having.
—
## Acknowledge Good Work
Most managers are quick to point out what is wrong. Few are as quick to point out what is right. That imbalance wears people down over time.
When someone delivers work that is solid, say so. When they solve a problem without being asked, notice it. When they handle a difficult client with patience, mention it. You do not need a long speech. A direct acknowledgment goes a long way.
Think about the freelancer who stays up late to finish a project on time and hears nothing back — just the next task in their inbox. They start to feel like a machine. Now compare that to a short message: “This came out well. I appreciate the effort.” Same person, same work, completely different motivation on the next project.
People repeat what gets recognized. If you only react when something fails, you train them to avoid failure. If you also react when something succeeds, you train them to reach for better work.
—
## Pay on Time
With freelancers, this matters more than almost anything else. They are not on a salary. They plan around what you owe them. When payment is late, they carry that stress into the work — and into every future conversation with you.
Late payment tells a freelancer you see them as an invoice, not a person. It tells them their time has less value than your cash flow. Even when the delay is small, the message is clear.
Pay on the date you agreed to. If something will be late, tell them before the due date, not after. If you need to adjust terms, discuss it upfront. A freelancer who knows they will be paid reliably will give you their best work. One who has to chase payment will eventually stop answering your messages.
—
## Pay for the Time They Give You
Some managers treat extra time like a gift the company is entitled to. It is not. If someone works beyond their normal hours to get something done, that time belongs to them — and it should be paid.
I saw this clearly when I worked in a hospital as an activity director. Work piled up during the day, and the only way to finish was to stay after hours — on my own, outside normal business time. There was no real choice. The work had to get done. The company was bringing in over a million dollars a month. There was no shortage of money. There was a shortage of respect for the people doing the work.
That is the part managers get wrong. They focus on whether the task could have been finished faster. They ask why it took so long. They act like the extra hour was a failure instead of a sign that the person did not walk away when things got hard.
It is not about how long it took. It is about the fact that they did not give up.
If someone stays late because they care about the outcome, add the hours. Pay them. Do not quietly accept the extra work as if it cost you nothing. Even when someone is willing to push through without being asked, that does not give you permission to take their time. Willingness is not a reason to skip payment. It is a reason to recognize what they gave you and treat it fairly.
A business that can afford to operate can afford to pay for the hours its people actually work. When you refuse to do that, you are not saving money. You are spending trust — and trust runs out faster than most managers realize.
—
## Be Consistent
People work better when they know what to expect from you. When your mood sets the rules, when praise and criticism come without pattern, when standards change depending on the day — people spend energy reading you instead of doing the work.
Consistency does not mean being rigid. It means your baseline stays the same. The same respect on a good week and a bad week. The same standards for everyone. The same follow-through on what you said you would do.
A freelancer who never knows whether a small mistake will be ignored or blown up will play it safe every time. A freelancer who knows exactly where the line is will work with confidence. That confidence shows up in the output.
—
## Set Clear Expectations Upfront
A lot of mistakes are not skill problems. They are clarity problems. The person did not fail — the brief failed them.
Before work begins, be clear about what success looks like. What is the deadline. What is in scope and what is not. What format you want. What decisions they can make alone and what needs your approval. What done actually means.
Picture handing someone a project with a one-line message: “Handle this.” They deliver something reasonable based on their interpretation. You are disappointed because you had something else in mind — but you never said it. That is not their mistake. That is yours.
Clear expectations at the start save corrections at the end. They also save the relationship, because the person is not left guessing whether they failed or were simply working from the wrong map.
—
## Do Not Play Favorites
When one person gets special treatment — more flexibility, more praise, more forgiveness for the same mistakes — everyone else notices. They may not say anything. They notice.
Favorites create quiet resentment. They also create a team that stops trusting you. People start performing for your attention instead of for the work itself. They compare themselves to whoever you favor and either give up or start cutting corners.
Treat people fairly. Apply the same standards. Give the same respect. When someone earns extra trust through consistent results, that is different from playing favorites — that is recognition based on behavior, not preference.
—
## Lead by Example
You cannot ask people to meet standards you ignore yourself. If you want timely work, be timely in your responses. If you want honesty, be honest when you make a mistake. If you want people to stay calm under pressure, do not explode when something goes wrong.
People watch what you do more than they listen to what you say. A manager who sends work at midnight and expects a reply by morning is teaching their team that boundaries do not matter. A manager who admits they got something wrong is teaching their team that accountability is safe.
Set the tone you want reflected back at you.
—
## Know When to Step In and When to Step Back
Good management is not always hands-off, and it is not always hands-on. The skill is reading the moment.
Step in when someone is stuck and asking for help. Step in when a project is heading in a direction that will cost everyone time to undo. Step in when you see someone struggling silently and the quality is slipping.
Step back when someone is finding their way and making progress. Step back when they are learning through doing, even if it is not perfect yet. Step back when your involvement would slow them down more than it would help.
The wrong timing in either direction causes damage. Stepping in too early kills confidence. Stepping back too long lets a small problem become a large one. Pay attention. Adjust as you go.
—
## Be Aware of Their Mental Load
Freelancers carry more than the project you gave them. They have other clients, other deadlines, bills, family, health, and the normal weight of daily life. You see the task. They see the task plus everything else.
That does not mean you lower your standards or accept poor work. It means you read the person, not just the output. When someone is quieter than usual, slower than usual, or missing small details they normally catch — something may be going on beyond the project.
A simple check-in can change the dynamic. Not a lecture. Not suspicion. Just asking how they are doing and meaning it. Sometimes the answer gives you what you need to adjust — more time, a lighter load, or a direct conversation about whether this project is the right fit right now.
People do better work when they feel like a person, not a delivery slot.
—
## What Good Management Actually Looks Like
Good management is not about control. It is not about being the smartest person in the room or having the final word on everything. It is about creating the conditions where good work can happen and good people can develop.
That means respect as a baseline, not as a reward for performance. It means room for mistakes, room for decisions, room for growth. It means listening even when you disagree, paying fairly without counting every minute, paying for every hour someone actually works, acknowledging what goes right, and training people so well that they could go elsewhere — and choosing not to.
The best measure of how well you manage is not what happens when you are watching. It is what happens when you are not.