- The Automation Playbook
- Posts
- If You Notice It, It’s Probably Wrong
If You Notice It, It’s Probably Wrong
Why internal UX isn’t a luxury, it’s a systems problem
Read time: 4 mins
Welcome back everyone 👋
This week’s Automation Playbook covers:
🧩 Invisible systems are designed, not accidental
⚙️ What internal UX actually means
💡 A real example of invisible systems done right
Let’s get into it 👇
Before we dive in, a quick personal note.
This year, one of the themes I am leaning into is consistency and showing up.
I have started the NHS Couch to 5K programme. I used to call myself a runner. I ran a half marathon years ago. But for the last decade, that identity has been more memory than reality.
Last night was a perfect example.
The UK finally had a brilliantly sunny day after weeks of rain.
And yet, I only managed to get out in the dark.
The photo included in this email is intentionally bad. Grainy. Low light. Majorly unflattering.
But that is the point.
It was not about perfect conditions. It was about following through.
Consistency is rarely cinematic.
It is usually quiet, repetitive and slightly inconvenient.
That same principle applies to internal systems.
They do not need to be flashy.
They need to work.

Not glamorous. Not golden hour. Just consistency in the dark. Systems should feel the same.
Which brings me to today’s topic.
Last week, I watched someone on an ops team hesitate before clicking a button.
Not because the task was difficult.
Not because the outcome was unclear.
Because the interface made the obvious feel uncertain.
Menus inside menus.
Labels that meant different things in different places.
A workflow that required remembering steps instead of guiding them.
She laughed and said, “If I notice it, it’s probably wrong.”
That line stuck with me.
Internal systems should not demand attention. They should remove it.
Invisible systems are designed, not accidental
Most companies obsess over customer UX.
Internal tools? Not so much.
They evolve organically. A spreadsheet becomes a tracker. A tracker becomes “the system”. A workaround becomes policy.
And because internal users are employees, not customers, friction gets tolerated.
But friction compounds.
If your team notices the tool more than the outcome, your system is absorbing cognitive load it should not.
Nugget #1: If people talk about the tool more than the task, something is wrong.
What internal UX actually means
Internal UX is not about aesthetics.
It is about clarity.
Good internal UX:
Shows only what is needed at the moment of action
Uses consistent language across flows
Removes unnecessary choices
Provides feedback instantly and predictably
It reduces thinking where thinking is not valuable.
It supports judgment where judgment matters.
Nugget #2: Great internal systems reduce decision fatigue, not increase it.
Why this matters now
Operations are getting more complex.
More integrations.
More data.
More moving parts.
Without intentional UX, complexity leaks into the user experience.
And when that happens:
Errors increase
Training takes longer
Work slows down
The irony is that many “powerful” internal tools are powerful because they are flexible. But flexibility without guidance creates hesitation.
Invisible systems win because they make the right path the easiest path.
A real example of invisible systems done right
I worked with a team that manually checked task statuses across three platforms.
The capability to automate it existed. It just was not surfaced clearly.
We redesigned the workflow so that:
Status updates happened automatically
Notifications triggered based on logic, not manual chasing
Ownership was visible in one place
The result?
Fewer interruptions
Less internal messaging
More trust in the system
No major rebuild. Just better experience design.
Nugget #3: When systems become invisible, productivity becomes visible.
What you can do today
🔹 Watch where your team pauses before clicking
🔹 Ask what parts of the tool feel confusing
🔹 Remove one unnecessary step this week
You do not need a full redesign.
You just need to stop accepting friction as normal.
If your team notices the system, it is probably wrong. Until next time, Paul Rhodes Founder & CEO | ![]() |
P.S. Whenever you’re ready, here’s how I can help:/
You can check out the latest episode of the Ctrl Alt Dev podcast where I break down what's working right now in detail with my co-host Sean Sale.
Take our Escape the Chaos audit to learn the critical factors to scaling businesses with automation in 5 minutes.
Need a fresh perspective? I’m here to help. Book a 1-1 call with me, and we’ll figure it out together.
Before You Go…How did you enjoy this email? I really value your honest feedback. |
