Process-First
Hidden assumptions erode your margin
One of the easiest traps for people to fall into is assumption.
In many business transactions the focus naturally falls on contracts and legal protections. People worry about the formal terms between the parties involved and what might happen in extreme situations such as insolvency.
Yet these are rarely the things that cause the real problems.
More often, difficulties arise from the everyday assumptions that were never fully defined.
“I thought that was included.”
“Can you not just change that?”
These small misunderstandings can undermine otherwise productive working relationships. They arise not from bad intent, but from the simple fact that different people have formed different assumptions about the same piece of work.
Over many years of engineering and project development, the challenge of defining exactly what is — and is not — included in a project became increasingly important.
Process-First grew out of that experience.
Defining the Real Problem
A good solution begins by understanding the real problem.
Process-First is built around that principle. The aim is to define the true starting point for a project or activity and then identify what may be missing from the description.
Often the most important information is not the material that has already been documented, but the details that everyone assumes are obvious.
In practice, businesses frequently rely on informal knowledge that never appears in formal procedures. It may be a note on a yellow post-it, a small workaround known to experienced staff, or an explanation passed on in conversation.
These elements are rarely captured in official documentation, yet they can be essential to how the organisation actually functions.
Process-First focuses on revealing these hidden assumptions so that they can be properly understood and recorded.
Creating a Clear Structure
Once these missing elements are brought into view, a much clearer picture of the work emerges.
The aim is not to create unnecessary bureaucracy, but simply to ensure that the description of a project or process reflects the reality of how the work is actually carried out.
When expectations are properly defined, communication improves. Buyers and suppliers understand each other more clearly, internal teams share a common understanding of the work, and misunderstandings are far less likely to arise.
Scope Profile and Automation
One practical outcome of the Process-First approach is Scope Profile.
Scope Profile provides a structured way to define the scope of a product or service, clarifying what is included, what is excluded, and where assumptions may otherwise lead to misunderstanding.
Establishing this clarity at the outset helps prevent the gradual erosion of scope, margin and trust that often occurs when expectations are left undefined.
The same underlying thinking also supports wider process analysis and the careful use of automation or AI. By understanding how work actually happens — including the assumptions that normally remain hidden — it becomes much easier to identify where intelligent systems can genuinely add value.
Automation should only be applied
once the process is properly understood
and a clear business case for ROI exists.
Start the conversation
If any of these ideas resonate with challenges you are facing,
feel free to get in touch
