Insights

Written when we have something specific to say.

This section is being built deliberately. We would rather publish three articles that change how a decision is made than thirty that restate what a search result already told you.

In preparation

What we are writing first.

Each of these comes from a decision we are repeatedly asked to help with. They are listed here in outline so you can see the direction; they are not published yet and are not linked as articles.

01In preparation

ERP selection for growing businesses

How to evaluate ERP platforms against how your business actually works, and how to tell the difference between a genuine requirement and a preference that will cost you a customization.

Written forFinance and operations leaders evaluating their first ERP, or replacing one that no longer fits.

Questions it will answer
  • How do we tell a real requirement from a preference?
  • When is configuring the business to the platform the cheaper answer?
  • What does a defensible selection process actually look like?
  • Which costs are routinely missing from an ERP business case?
02In preparation

Building a digital transformation roadmap that survives contact with the organization

Why most transformation roadmaps fail on sequencing rather than strategy, and how to plan change against the organization's actual capacity to absorb it.

Written forExecutives and transformation leads responsible for a multi-year change programme.

Questions it will answer
  • How do we sequence change so the organization can absorb it?
  • What has to be true before a programme starts, not during it?
  • How do we structure a roadmap so it can be re-planned without restarting?
  • What are the early signals that a programme is failing?
03In preparation

When custom software makes sense — and when it does not

A practical test for whether a process justifies a custom build, including the cases where the honest answer is to fix the process or configure an existing product instead.

Written forTechnology and operations leaders weighing a build against a packaged product.

Questions it will answer
  • Is this difference a genuine advantage or an accumulated habit?
  • What is the real total cost of ownership of a build?
  • When is configuring a packaged product the better answer?
  • How do we avoid rebuilding a process nobody has documented?

Editorial standard

What will and will not appear here.

01

Specific, not general

Every article has to change how a decision is made. If the conclusion is available from a search result, it does not need us to restate it.

02

No unverifiable claims

No client names, outcomes or figures we cannot substantiate. Where we describe a pattern, it is described as a pattern.

03

Written by the people who do the work

Articles come from delivery experience, not from a content calendar.

04

Published in both languages

Articles are published in English and Arabic together. Neither language is a translation queue behind the other.

Not what you were looking for?

If you have a specific decision in front of you, a conversation will be faster than waiting for us to write about it.