Strategy18 September 20263 min read

Business impact is the goal. The rest is a means.

Begin with the pain in your business. The platform comes later.

Ruud KuilCo-founder MAD-Quality ·
Two people sketch a plan on a whiteboard

Does the end justify the means, or is the sacred means looking for an end? In most IT consolidation programmes and data strategies the answer is clear: the means wins. The choice of platform is fixed before anyone has named the underlying problem out loud.

Where does it actually hurt in your business?

That question is usually missing from this kind of programme, whether it's about IT consolidation, an AI application or data-driven working. The things that bother people in the organisation, and that they keep talking about, usually affect business results. That's the gain of Business First: you automatically bring focus to the business and data strategy that's actually needed.

The wishful thinking of the handy tool

Buying a tool feels like progress. A contract is signed, a project gets an inspiring name, and a dashboard appears.

The tool only solves the problem you put into it. Software processes the data you feed it and changes nothing about the reason that data was wrong.

Start with technology and you close your eyes to the real problems.

IT consolidation is not a strategy

IT consolidation is the clearest example. Systems are merged, processes standardised, teams squeezed into agile ways of working.

A programme like that usually starts with a good intention: one truth, one platform, one process. Along the way the original question drops out of sight and the programme itself becomes the goal.

Attention shifts to the operational layer: sprints, backlogs, speed of delivery. The business has to go along with that mode. Product owners plan releases, stakeholders join refinements, and the question of which data matters to the business disappears beneath the question of what this sprint will deliver.

Movement for movement's sake is expensive. The organisation ends up paying twice: first for the consolidation or implementation, then for the correction that turns out to be needed after all.

Pain is a signal, not noise

The complaints that keep coming back in an organisation are rarely a coincidence. A report that's never right, a team correcting numbers by hand, a process that regularly runs late: those signals point to time and money. In other words, concrete impact on the business.

Pain is the best gauge there is. Follow it, and the question of which data gets priority answers itself.

Prioritising means having your hands on the wheel

A supplier sells their own agenda. Base your priorities on that and you hand over control.

Initiatives that respond to pain the organisation already feels get support almost automatically, because nobody needs convincing that the problem exists. The reverse route, setting up a project and finding a problem for it afterwards, rarely sells itself so easily.

Focus comes by itself when you start with your business

So a priority order emerges by itself. The data at the root of the biggest bottlenecks is also the data that needs to be in order first for data-driven working.

That same data contributes most to successful AI applications. Makes sense: AI doesn't feel the pain. We do.

Reversing that order has been backfiring for years. Building an application on a means instead of a problem does nothing for reliable data.

From pain to priority

An integrated approach starts with a concrete question: which problem hits business results hardest, and what data lies behind it?

That takes conversations with the people who feel the pain every day, and the willingness to act on what you hear. Buying a tool is more tempting. So is saying "yes" to the big consultants' beautiful slide deck. Those options earn their money mainly from the means itself.

The Business First route has a slightly longer run-up, and it wins that back with ease during implementation. Architects have known this for decades: time spent on the design up front pays for itself in the execution.

Board members and senior management who take their business and data strategy seriously start with the business: where does it hurt, what does that cost, and what data is needed. The form, whether that's IT consolidation, AI or something else, then follows by itself.

At MAD-Quality we call that Business First, the basis of our Go-MAD! approach: first the problem, then the strategy, and only then the form.

Data doesn't need to be perfect. It needs to be adequate.

Ruud Kuil

Written by Ruud Kuil

Co-founder of MAD-Quality. Helps leadership teams move from data chaos to data they dare to manage by. Want to know more about data quality? Follow Ruud on LinkedIn.

Worked example

What does inadequate data cost you?

Slide in your annual revenue and see at a glance what poor data costs you per year, per day and per hour.

Call RuudBook half an hour