A manager asked her team lead a simple question: “How do we onboard a new client?”
The answer: “It depends.”
Depends on the client size. Depends on who sold the deal. Depends on which team is handling it. Depends on whether it’s Q4.
That answer feels reasonable. Nuanced, even. But here’s what it actually does: it transfers the cognitive load from the organization to the individual.
Now the team lead has to figure it out. Every time. From scratch.
Cognitive load is the amount of mental effort required to process information and complete tasks.
What makes cognitive load heavier? Complex processes. Unnecessary task switching. Juggling too many things at once. Poorly designed systems. Unclear communication. Unfamiliar contexts.
What makes it lighter? Breaking down complex information. Simplifying workflows. Standardizing tasks. Clear organization. Visual aids.
The question is: is your organization making your employees’ cognitive load heavier or lighter?
“It depends” is a cognitive load problem hiding in plain sight.
How do I submit my expense report? It depends.
Which vendor do I call for this issue? It depends.
How do I escalate a customer complaint? It depends.
Every “it depends” is a decision your team has to make that the organization hasn’t made for them. Multiply that across dozens of tasks, dozens of employees, and hundreds of interactions per week. That’s a lot of mental energy spent figuring things out instead of doing the work.
When cognitive load is heavy, decisions get harder. Work gets slower. Mistakes increase. Team members burn out. Satisfaction drops.
When cognitive load is light, the opposite happens. People move faster. They make fewer errors. They feel more confident. They have energy left at the end of the day.
So what do you do about it?
Start listening for “it depends” in your organization. Every time you hear it, ask: could we make this decision once, for everyone, instead of making every person figure it out on their own?
Not everything can be standardized. But most things can be clearer than they are.
Document the decision. Create the framework. Build the flowchart. Write the SOP. Give people a path instead of a puzzle.
Your job as a leader is to absorb complexity so your team doesn’t have to.
Where is “it depends” showing up most in your organization? That’s where to start.