Culture shapes behaviour.
Behaviour shapes workflow.
Workflow eventually becomes embedded in technology.
I’ve been thinking about that a lot recently.
Over the years, I’ve worked with firms across Europe and elsewhere.
The markets were often the same.
The regulations were increasingly shared.
The technology could even come from the same vendors.
Yet the way people worked was frequently very different.
In Sweden, I saw decisions built through consultation and consensus. A meeting was often the beginning of the decision-making process, not the end of it.
In Denmark, the approach felt more immediate and pragmatic.
Here is the market.
Here is the price.
Take it or leave it.
In Italy and Spain, relationships and informal conversations often carried as much weight as the formal process. People wanted to understand and trust one another before committing to a course of action.
In France, I once tried to discuss business over lunch and was politely stopped by the prospective client.
“We don’t discuss business until we’ve finished eating. This is the time to decide whether you’re someone I want to work with.”
Lesson learned.
None of these approaches was inherently right or wrong.
Each had strengths.
Each had inefficiencies.
Each reflected the culture around it.
But repeated behaviour gradually becomes an accepted way of working.
That way of working becomes a process.
The process acquires policies, controls, approvals and exceptions.
Eventually, technology is built or configured around it.
A consensus-led organisation may create more review stages and shared approvals.
A firm that values individual judgement may allow wider authority and faster decisions.
A relationship-led business may rely more heavily on conversations, personal knowledge and informal exceptions.
Over time, all of that becomes visible in the workflow.
Who is allowed to decide?
How many people must approve?
Can someone make an exception?
Does the process assume trust or demand control?
Is knowledge documented, or does it live inside relationships?
Does the technology help people make decisions, or simply record them afterwards?
These are not only design choices.
They are cultural habits that have gradually become embedded in systems.
That is why two organisations can buy exactly the same platform and end up with completely different working environments.
The software may be identical.
The configuration, governance and user experience will reflect the organisation that implemented it.
And once behaviour becomes embedded in technology, it can be remarkably difficult to change.
The original people leave.
The business evolves.
The assumptions become outdated.
Yet the approvals, restrictions and workarounds remain because nobody can quite remember why they were introduced in the first place.
Culture shapes behaviour.
Behaviour shapes workflow.
Workflow eventually becomes embedded in technology.
And once that happens, yesterday’s habits can quickly become tomorrow’s constraints.