Skip to main content
Talk to an expert
Issue 030Field NoteRescueRef 077

Rescue debrief: the four signals that mean the platform is not the problem

When a commerce project stalls or fails, blaming the platform is often the default. However, our experience with rescue projects shows that technical problems are frequently symptoms. Deeper issues in governance, process, or strategic alignment are typically the root cause.

Neil Boughton· Technical Director
5 min readReviewed December 2024
"If every problem is blamed solely on the commerce platform, the real issue is likely elsewhere in the organisation or its processes."
Written by
Neil Boughton, Technical Director at iWeb
Neil Boughton
Technical Director
29 years at iWeb

Neil leads platform architecture and integration strategy at iWeb. He has designed ERP and commerce integration patterns across manufacturing, wholesale and retail, and writes about operational resilience, release governance, observability, and the infrastructure decisions that determine whether large programmes stay stable under pressure. Bias toward durable, measurable systems over architectural theatre.

Next in this thread

Operational notes worth reading next.

All notes in The Record →
Issue 048Field Note · Rescue

What a senior engineer actually does in the first 48 hours of a rescue project

The first 48 hours of a rescue are forensic, not creative. The principal engineer's job is access, containment, replication, and one defensible document by the end of day two.

Andrew··4 min read
Issue 029Field Note · Rescue

Rescue benchmark: build pipeline health, and the three numbers that predict the next outage

Proactive monitoring of build pipeline metrics, specifically build time, failure rate, and deployment frequency, can predict and prevent site outages.

Andrew··4 min read
Issue 030Position · Rescue

When the rescue is the supplier relationship, not the codebase

Addressing commercial issues within a supplier relationship is frequently the critical path to resolving systemic problems in a commerce operation, often before codebase intervention.

Neil··5 min read
The briefing · regular

A regular round-up of new notes.
No content marketing.

Sent on the last Thursday of the month. The most useful five notes from the previous four weeks, written by the operators, architects, engineers and commercial leads running the work.
Next step

Take this conversation private.

If this note matches the brief on your desk, the version we'd write for your platform, sector and trade-account model is the work itself. Send a short brief and a senior lead replies inside 48 hours.
Talk to an expertBack to The Record →