The QRT Doctrine

After 25 years implementing ERP systems, I’ve noticed that project success or failure almost always traces back to three things — things that sit above any methodology or template. I call it the QRT Doctrine.

The name comes from my own name — Kurt without the vowels — but over the years it picked up real meaning through four phrases:

• Que Rien ne T’arrête — let nothing stop you.
• Questions Reveal Treasures — the right questions uncover what the customer actually needs.
• Quality Requires Training — excellence comes from discipline, not accident.
• Query, Relate, Transform — pull your data sources together, relate them, and turn them into insight.

Underneath those four phrases sit three pillars: Communication, Standardisation, Integration. They map to three phases — Understand, Build, Extend — and they build on each other in that order.

Communication — Understand

Before a single configuration is touched, you need to understand what the customer actually needs — not what they say they want, not what’s written in the spec. That means active listening, asking “why” before “how”, and being honest even when compliance would be easier.

When communication fails, everything downstream fails with it: requirements get misread, users feel unheard, and “scope creep” turns out to just be the slow discovery that nobody understood the need in the first place.

Standardisation — Build

Once you understand the need, default to standard functionality. This cuts two ways:

Product standardisation — every customisation carries an ongoing cost: maintenance, upgrade risk, knowledge loss. Standard should be the default; custom is for genuine competitive advantage only.

Process standardisation — the implementation process itself should repeat: gather, workshop, configure, train, validate, module after module. A predictable rhythm is a communication tool in itself — the customer learns to prepare, and always knows where they stand.

Integration — Extend

This is the forward-looking pillar. An ERP system isn’t an island — it’s a rich data source that becomes far more valuable once it’s queried alongside other systems, related across boundaries, and transformed into unified insight. For organisations on Microsoft’s stack, Microsoft Fabric is what makes this practical: combining Business Central data with CRM, IoT, or external data, and surfacing it through Power BI in ways the ERP alone never could.

Not a methodology — a lens

The QRT Doctrine doesn’t replace Prince2, Agile, or whatever framework a team runs. It sits above them. Whether you’re sprinting or following a waterfall plan, three questions still apply: Have we truly understood the need? Are we staying close to standard? Are we thinking about the bigger data picture?

Understand. Build. Extend. Communication • Standardisation • Integration