.svg)
.svg)
Why Most Workflow Software Gets More Complex Over Time
Most teams try to simplify workflows by removing steps and hiding complexity. In reality, the challenge is helping users navigate complexity with confidence. Here’s what I’ve learned designing operational software across Facilities Management, Housing Associations and Build-to-Rent.
.svg)
.svg)
Complexity Doesn’t Come From The Interface
When people talk about simplifying workflows, the conversation often focuses on reducing the number of steps.
Fewer clicks.
Fewer screens.
Fewer fields.
While these improvements can help, they rarely solve the real problem.
After spending years designing products for Facilities Management, Housing Associations and Build-to-Rent operators, I’ve learned that workflow complexity rarely comes from the interface itself.
It comes from the business.
As organisations grow, they introduce new teams, suppliers, compliance requirements, approval processes and service levels. The software becomes a reflection of that operational reality.
The mistake many product teams make is trying to hide complexity rather than designing for it.
Once the foundation is set, the focus shifts to design, iteration, and execution. Prototypes are tested, feedback is analyzed, and features are refined until the product becomes something intuitive, functional, and meaningful.
Design Around Decisions
I now spend less time asking:
“How do we reduce steps?”
And more time asking:
“What decision is the user trying to make?”
A Facilities Manager reviewing hundreds of active jobs doesn’t care about seeing every piece of information at once.
They care about identifying risk.
A Customer Service Agent doesn’t need the entire operational history immediately.
They need enough context to respond confidently.
The most successful workflow products I’ve worked on didn’t become simpler over time.
They became clearer.
They provided better visibility, stronger accountability and more relevant context at the right moment.
Complex businesses will always have complex operations.
The role of product design isn’t to pretend that complexity doesn’t exist.
It’s to help people navigate it with confidence.
The Goal Is Clarity, Not Simplicity
A maintenance task sounds simple.
Someone reports an issue.
Someone fixes it.
The task is completed.
In reality, that same task may involve multiple suppliers, service level agreements, escalation rules, compliance checks, resident communication and asset information.
Removing this information doesn’t simplify the experience.
It simply forces users to find it somewhere else.
One of the biggest mindset shifts in my career was realising that users are often willing to work with complex systems.
What they struggle with is uncertainty.
They need to understand:
- What needs attention
- What happens next
- Who owns the task
- What is blocking progress
When those questions are answered clearly, even highly complex workflows become manageable.
Similar blogs
.svg){kind=small}
.svg)
LET’S MAKE CLARITY A HABIT.
Have a product, platform, or operational challenge in mind?
I help organisations simplify complexity, create scalable foundations, and build digital products that deliver lasting value.
