In Brief
- “Nice” bosses often confuse kindness with avoidance.
- Without clear expectations, flexibility turns into resentment.
- Work the team should be doing ends up back on the boss’s desk.
- The fix isn’t being harder — it’s pairing consideration with structure.
- One founder I spoke with had to let a third of his staff go to fix a “too nice” culture.
There’s a particular problem almost every small business owner runs into eventually. They built the workplace they wanted to work in — flexible, warm, understanding. People were trusted. Rules were light. Lives outside of work were respected.
And then, somewhere around month nine or eighteen, things started to drift.
People came in late. Deadlines slipped. The boss who had been so proud of the culture they’d built now found themselves doing work that wasn’t theirs — because if they didn’t, it wouldn’t get done. The flexibility they’d offered had quietly turned into something else.
This is the hidden cost of being a “nice” boss. And the fix isn’t to become a worse one.
The trap: nice isn’t kind
In leadership research from the 1950s, Fleishman and Harris identified two independent qualities in good supervisors. They called them structure and consideration.
Consideration is the warmth — caring about people as humans, listening, being flexible, respecting that life happens outside of work.
Structure is the clarity — defining what the work is, what’s owed, when it’s due, and what good looks like.
The key word in that research is independent. You can have one without the other. And most “nice” bosses have built workplaces with high consideration and almost no structure. They think they’re being kind. What they’ve actually done is left their team to guess at the rules. That pairing — structure with consideration — is one of the eight conditions that show up in workplaces people actually want to stay in.
Pure niceness without structure isn’t kindness. It’s avoidance dressed up as kindness.
What it looks like in real life
I was helping a small business owner a while ago who had this exact problem. She told me she knew some of her employees were running personal errands during work hours. Others were studying for university courses at their desks. She was uncomfortable about it — but she also didn’t want to be “the bad one.” So she said nothing.
Work was slipping. Deadlines were missed. She was staying late to catch up on tasks her team should have completed.
Her instinct was to crack down. To stop the flexibility entirely. I told her she had the wrong fix.
The problem wasn’t that her team was studying or shopping. The problem was that she had never made the expectations clear. She had said “you’re flexible here” without ever saying “and these are the deadlines that hold no matter what.” There was consideration without structure. So her team did what most people do when the rules are vague — they assumed the most generous interpretation.
The fix wasn’t ending the flexibility. It was naming it properly. You can take an afternoon for a doctor’s appointment. You can study, but not on company time. You can leave early, but the project deadline is Friday. Once the expectations were visible, most of the team adjusted in two weeks. One didn’t, and that became a different conversation — which was also clearer because the rules were now on the table.
The founder pattern
In my PhD research with 19 Australian founders, one of them described the exact same arc. He’d built a “nice” workplace. Flexible. Friendly. Trusting. Then his lead programmer pulled him aside and said something that changed his thinking.
“You had a chance at making a good company, but the place is filled with dead wood. You’ve been too nice.”
He told me afterwards: “I never thought of that as a concept. Too nice leads in the wrong direction? Isn’t good and nice always the thing that leads the right way? No. There is a balance.”
He ended up restructuring the company and letting about a third of his staff go — people he’d protected through their underperformance because he didn’t want to have the hard conversation. The remaining team became dramatically more effective. The culture didn’t get colder. It got clearer.
His final reflection was sharp: “If you’re not prepared to cause a bit of pain sometimes, then you shouldn’t take that position.”
That’s not a hard-line leadership philosophy. It’s a recognition that avoiding short-term discomfort creates long-term harm to the people you actually care about.
Why “nice” bosses end up doing the work
Here’s the mechanical reason this pattern leaves you exhausted.
When expectations aren’t clear, people drift. When people drift, work doesn’t get done. When work doesn’t get done, you have two choices — have the hard conversation, or do the work yourself. A “nice” boss avoids the hard conversation. So the work lands on their desk by default.
This is what Chris Argyris called a Model I behaviour — protecting your relationships at the cost of honest communication. The boss tells themselves they’re being kind. The team knows the work isn’t getting done. The boss burns out trying to plug the gap. Nobody benefits.
Over time, the team learns that raising concerns leads nowhere and that gaps get absorbed by the boss anyway. That’s a defensive routine forming on both sides. The team stops pushing. The boss stops asking. The work stops moving.
The Model II alternative isn’t being harder. It’s being honest. You can be warm and direct in the same conversation. “I know your kids have been sick this month, and I want to support that. And the report deadline is Thursday, and I need a plan for how it gets there.” Both statements true. Both said with care. Neither one avoided.
What to do instead
Three moves rebuild structure without losing consideration.
1. Make the expectations explicit. Write down what the role requires. Hours, deliverables, decisions the person owns. Then share it. Most “nice” bosses have never done this because it feels rigid. Without it, every disappointment is a surprise.
2. Separate flexibility from obligation. Flexibility is about how the work gets done. Obligation is about whether it gets done. The first is yours to give generously. The second isn’t negotiable. Say both out loud.
3. Have the conversation when it’s small. The hardest part of a hard conversation is that it’s been postponed for months. If you flag concerns when they first appear, you don’t need a confrontation — you need a check-in. Most “nice” bosses skip the check-in and end up needing the confrontation.
If your team has been operating under vague rules for a while, this shift will feel uncomfortable for everyone. Some people will leave. Most will respect the change, because vague rules are exhausting to live under too. People want to know what good looks like.
What to do this week
Pick one person on your team where you’ve been quietly disappointed for a while but haven’t said anything. Schedule a 30-minute conversation. Don’t lead with the disappointment. Lead with the role.
“I want to talk about what I expect from this role and check we’re aligned.” Then describe what you actually need — concretely. Then ask them what’s getting in the way. Then agree what changes from this week.
You’ll find one of two things. Either the person realigns and your problem solves itself. Or you discover something you needed to know — and the next conversation becomes obvious.
Neither of those outcomes were available to you while you were being “nice.” If you’d like a structured way to spot where these patterns are operating across your whole team, the workplace diagnostic can walk you through it.
For the broader picture across all seven patterns, see What 19 Australian founders taught me about workplaces people don’t leave.
