Thinking
What we have learned, written down
Articles and guides from the people doing the work. Each argues from a pattern rather than a named client.
Filter insights2 chosen
6 pieces matching
PinnedArticle · 5 min read
When access is solved by copying
Nobody decides to build six copies of the same dataset. It happens one reasonable decision at a time — and the fix is governance, not a tidying exercise.
Read
Article · 6 min read
When procurement runs on two ERPs
Dual-ERP environments are common in manufacturing and rarely written about. The systems are not the problem — the undocumented space between them is.
Read
Article · 5 min read
The integration opportunities nobody owns
Every business unit optimizes what it can see. The gaps between them belong to nobody, and that is where the largest inefficiencies live.
Read
Article · 5 min read
Let the data move on status, not on somebody remembering
Most failed integrations are not technical failures — they are a person who was on vacation. The hard part of fixing it is not the code, it is agreeing what the statuses mean.
Read
Guide · 6 min read
Why knowledge transfer slips, and how to stop it
Transition plans assume the people who do the work will find time to explain it. They will not. Treat knowledge transfer as a project you run rather than something you receive.
Read
Article · 6 min read
Building a capability center that works as part of the client team
A capability center is not offshore staffing with better marketing. The difference is whether the team understands the work well enough to make decisions in it.
Read
Want a second opinion on your own estate?
Tell us what it looks like today and we will tell you what we would look at first.