ProductiveQ starts a six-step method at the function map. The steps find where work has become complicated, establish why, and remove what does not add value.
The method comes from co-founder Howard Thomas’s consulting practice at TAM Consultants. ProductiveQ ties the method back to the function map.
Each step answers one question. Together they move from what the business does, to why the work became complicated, to a simpler way of working that people will keep.
01
Define the complexities
Where is work harder than it needs to be?
Look for where work has become harder than it needs to be: extra approvals, duplicated records, steps nobody owns. Most of it was added with good intentions.
On the map
The function map and its eight checks show where records, owners and process steps do not line up.
02
Identify the causes
Why did it become this way?
Establish the facts before forming a view. Ask what each function is for and why the work is done this way. The aim is to separate what adds value from what has only accumulated.
On the map
Follow a function into its workflow, then a step into its documents, roles and systems. A finding can be opened to see its source and date.
03
Engage the people
What do the people doing the work know?
The people doing the work know how it grew this way. Listen before proposing anything. A change that ignores the reasons behind current practice will not be adopted.
On the map
Two teams may have a good reason to work differently. The map gives the conversation something specific to point at.
04
Develop the plan
What will change, and who decides?
Once the what and the why are settled, decide how, who, when and where. Put the process right first. Then bring in technology to support it.
On the map
Compare the options, estimate the benefit and state the assumptions. The responsible person approves the change.
05
Embed simplicity
Will the simpler way last?
People keep what they help to build. Have teams map their own work, so they can judge which steps add value and which do not.
On the map
The agreed process stays in view: what must happen, who does the work and who decides.
06
Eliminate the complexities
What can now be removed?
With the simpler way in place, remove what it has made redundant: the duplicated, the unused and the unnecessary. This is where the cost comes out.
On the map
Compare the result with the starting point, account for the cost of the change, and keep checking that the improvement lasts.
The public demo follows one improvement from detection to a checked result, using sample data. Connections to customer systems are proposed for pilots.
Technology makes it easy to add: another form, another approval, another report. Used that way, it moves paperwork faster without asking whether the paperwork is needed. Put the process right first. Then let technology do the work that remains.
01
Rules added on top
A problem appears and a control is added. The root cause stays where it was, and the control becomes one more thing to manage.
02
Paperwork made faster
A system speeds up the forms and approvals around a task, when it could have done the task or shown that it was not needed.
02 / Four ways to make work simpler
Adding is easy. Removing takes thought.
When a problem appears, the usual answer is to add something: a rule, a role, a system. Ask four questions first. They come from safety engineering, in the tradition of Trevor Kletz: what is not there cannot hurt you.
01
Eliminate
Can the work stop?
If nothing depends on the output, remove the task.
02
Substitute
Can something simpler do the job?
Use a standard form in place of a bespoke one.
03
Minimise
Can there be less of it?
Fewer handovers, fewer approvals, fewer copies.
04
Simplify
Can what remains be made clear?
A step people can follow without having to interpret it.
Only then consider adding. “Any fool can add” is the moral of Howard Thomas’s book, Simplicity from Complexity.
03 / What holds throughout
Three habits behind every step.
The steps change from one business to the next. These habits do not.
01
Facts before opinions.
Experience is valuable, but it is not evidence. Check what the records show before acting on what everyone believes.
Record the starting point, the cost and the result. Keep what was expected separate from what was measured.
Where the method comes from
Developed in practice.
The method was developed at TAM Consultants (Thomas and McKinlay Consulting), the consultancy Howard Thomas founded to reduce complexity so that organisations can make good decisions. It draws on the specialists TAM has worked alongside over many years. The step descriptions on this page are ProductiveQ’s adaptation.
ProductiveQ builds its function map on that method. The software is new. The way of working behind it is not.