Menu

macroseam / Method

Map.Develop.Optimise.

How macroseam works. Three moves, repeated: map how the work really flows, develop the processes that are missing or broken, and optimise what runs. All of it happens while the company keeps operating.

Step 01 of 03

Map

What happens
We go into the running operation and record how work really flows today, at the macro scale and at the fine scale. We follow real cases from start to finish instead of reading the manual.
What you have at the end
A map of the actual process, with every handoff, system and waiting point marked, and the seams where time and information are lost.

Step 02 of 03

Develop

What happens
We design the process that is missing or replace the one that is broken, and decide what each team and each system has to do. Then we bring it into daily work with the people who will run it.
What you have at the end
A process that is running in operation, not a document describing one.

Step 03 of 03

Optimise

What happens
We measure the new flow against the old one, tighten what works and remove what does not. Then we move on to the next seam.
What you have at the end
A process with a known lead time and a clear owner, and a list of what to improve next.

Fig. 04 / The loop

A loop, not a one-off project.

The three steps repeat. When one seam holds, the next one is mapped.

Principles

Three rules we do not bend.

Rule 01

Process first, software second.

Software runs a process; it does not design one. We settle how the work should flow before deciding what the tools must do.

Rule 02

Both scales at once.

A change to the big flow fails if the single task underneath it does not change too. We work on the macro process, the fine process and the seam between them together.

Rule 03

Never stop the company.

Our clients are already operating. Processes are mapped, built and improved while they are in use.

Comparison

How this differs from the usual routes.

Compare macroseam with

macroseam

Starts from
How the work actually runs today
Looks at
Macro flow, fine detail and the seam between
Role of software
Follows the process
Leaves behind
A process running in operation

Management consultancy

Starts from
Strategy and a target model
Looks at
Mostly the macro level
Role of software
Usually out of scope
Leaves behind
A report and a roadmap

New software project

Starts from
The features of the tool
Looks at
The fine level, inside one system
Role of software
Defines the process
Leaves behind
A system to adopt

Internal project

Starts from
The pain of one team
Looks at
One department's part of the flow
Role of software
Works around what exists
Leaves behind
A fix that depends on a few people

A general comparison of typical approaches. Individual firms and projects differ.

NextLogistics and freight