Assumptions are not a system
Common sense isn’t so common, which is why communication is important.
A client once told me it was “common sense” to update ClickUp when a task was finished.
So they were shocked when tasks kept falling through the cracks.
Some people thought updates happened in Slack
Others assumed the project manager handled it
No one was wrong, but no one was clear.
That’s when I reminded them, common sense isn’t common.
Someone who lives in Florida might not know that you shouldn’t lick a metal pole in the winter or your tongue will stick to it. As a Canadian, that’s common sense… as someone in a warm climate, it’s probably never even been considered.
Clarity fixes what “common sense” breaks
Most problems at work aren’t because someone’s lazy or bad at their job, they happen because nobody clearly defined what “done” actually means.
You asked for a report > they sent a spreadsheet
You wanted detailed notes > they gave bullet points
You said “update the client” > they thought that meant an email, not a meeting
None of those people were wrong… they were guessing.
This is where “common sense” falls apart because what feels obvious to you (common sense) isn’t universal.
It comes from your experience, your standards, your preferences and how you’ve always done things. Other people don’t have access to that unless you give it to them.
Most business owners didn’t build their business by waiting for instructions…
They figured things out as they went
They Googled
They used trial and error
They made calls with incomplete information
They adjusted on the fly
And after years of doing that, that kind of problem solving becomes second nature.
So when something feels obvious to you, it genuinely feels like it should be obvious to everyone else too. Buuuuut, it’s not.
They didn’t live through the same mistakes, the same context, or the same years of figuring things out the hard way, and even if they did… they did it in their way… not yours.
“Just know what to do” feels normal to you because that’s how you’ve always operated as a solopreneur. But, that’s not fair, clear, or realistic for anyone else.
The good news is that it’s not a failure of your team, it’s a gap that needs communication instead of assumptions.
The fastest way to fix this, is instead of saying “just use common sense,” explain what that actually looks like in practice.
Say things like:
“When you upload a file, save it in this folder and name it with the date and client name.”
“Always reply to client messages within one business day, even if it’s just to say you’re on it.”
“If you can’t find something, check the shared folder first before asking.”
These sound basic.
YES, that’s the point! Basic removes guesswork, removing guesswork removes mistakes.
Communication makes systems work
Everyone talks about systems like they’re magic. A system that doesn’t include communication is just a pretty process nobody follows.
ClickUp doesn’t fix misunderstandings
Slack doesn’t solve bad instructions
Templates don’t stop people from interpreting things differently
You can have the most beautiful SOP in the world, but if nobody understands why it matters, how to use it, or even where to find it, it’s useless.
It can feel faster to skip explaining, you don’t want to spend 10 minutes delegating that task, you just want it done.
It’s not.
You pay for it later in rework, follow ups, and frustration.
Communication tells people what matters, what order things should happen in, and what success looks like when they’re done. It helps them know what to prioritize when everything feels urgent and lets them ask better questions because they understand the bigger picture.
When “common sense” fails in real life
You’ve already seen how this plays out.
Nothing was broken in that ClickUp example I mentioned earlier. No one was careless or ignored instructions, they were just working off assumptions because they weren’t given enough information.
When what you think is “common sense” isn’t explained or documented, gaps form, tasks get missed, tasks get done differently and frustration and blame creep in.
Well, truth be told, there is someone to blame… it’s you… the instruction giver.
BUT, even though it’s the task giver that’s wrong, not the task doer, the task doer starts feeling like they’re failing because they’re constantly wrong…but you set them up for that.
Once the expectation is said out loud and written down, the problem disappears.
Talk about it before it becomes a problem
You can save yourself so much frustration by catching these gaps early. Before assuming someone should know, ask yourself:
Have I explained this clearly?
Have I shown what “done right” looks like?
Have I documented this anywhere?
Have I made it easy to ask questions?
Half of managing a team is learning how to communicate (or even over communicate) without being annoying. And yes, this is something I’ve had to learn the hard way.
It’s giving people enough direction that they can do their jobs confidently, without second guessing their every move
It’s checking in without hovering or micromanaging
It’s creating a culture where asking for clarity isn’t seen as a weakness, it’s encouraged to do the job properly
Communication builds trust
When people understand what’s expected of them, they relax, they stop guessing, stop walking on eggshells, and start performing better.
Clear communication makes your team faster, more confident, and more accountable.
Always delegating tasks in the “figure it out” style is lazy and sets everyone up for disappointment. I’m not saying there aren’t times where “figure it out” is needed, but it shouldn’t be how all tasks are handled. I personally use “figure it out” when there’s a task I can’t get to, and if they can figure it out, awesome, if they can’t… I’ll do it later. There is no punishment if it’s not done how I want it.
So here’s your reminder
Common sense isn’t common
Assumptions kill productivity
Communication is the glue that keeps your systems, your team, and your sanity intact
So before you roll your eyes and think “Why don’t they just get it?”
Ask yourself “Did I actually say it?”
If you’re annoyed that someone didn’t do something the way you expected, that’s a signal something needs to be clarified, not corrected.
If your team’s running on assumptions instead of actual instructions, it’s time to fix your systems.
Let’s make “common sense” optional and communication non-negotiable.
