Dashboards fail when the underlying data model is wrong

Good delivery looks quiet from the outside. The noise shows up when cutover arrives and nobody can explain what “done” means in numbers.

In August 2025 we are still hearing the same request in different words: make data & analytics real for the business, without stopping the work people already depend on. That is harder than a feature list. It needs clear ownership, an honest cutover plan, and engineers who stay close after the first release.

The problem we keep seeing

Teams often treat data & analytics as a side track. Platform licences get approved. Workshops fill calendars. Then integrations, data quality, and support land in “phase two”. By the time phase two starts, leadership has moved on and the original process is still broken.

Scope that lives only in slide decks tends to expand the moment the first real user appears.

With Data & Analytics, the useful questions are practical:

• Which process fails today, and who feels the pain first?
• What does a successful week look like after go-live — in tickets, cycle time, or error rates?
• Which systems must stay in sync, and who owns the source of truth?
• What happens on day two if something breaks at 07:00?

If those answers are fuzzy, the build will look busy and still miss the mark.

What “good” looks like in practice

Good Data & Analytics delivery is boring in the best way: fewer surprises, clearer owners, and releases that do not need a war room.

We stay close to database design, governance, reporting, and KPI dashboards.

What that looks like with clients:

• Agree the business outcome before the architecture deck.
• Match the engagement model to the risk — hire experts, build the application, or run a wider programme.
• Prefer visible increments over a late big reveal.
• Plan hypercare and knowledge transfer as part of the build, not as an afterthought.

A short story from delivery

Imagine a mid-size organisation that already runs Salesforce or NetSuite, plus a handful of spreadsheets and an ageing portal. Finance wants cleaner reporting. Operations wants fewer manual handoffs. IT wants fewer late-night patches.

A common mistake is to start with a technology shortlist. A better start is one painful process — for example order-to-cash or supplier onboarding — and a definition of done that leadership already understands. From there, data & analytics becomes a set of concrete changes: data contracts, interfaces, screens, and operating routines. The platform choices follow the process, not the other way round.

We treat observability as part of the build. Dashboards, alerts, and a named on-call path should exist before users depend on the new flow — not three weeks later when something fails quietly overnight.

How we work with clients

We keep the engagement model flexible on purpose. Some clients need one senior engineer embedded for a quarter. Others need a full build with design, integration, and launch support. Larger programmes need a partner who can stay across CRM, ERP, cloud, and custom software without losing the thread.

Across Salesforce, Oracle, NetSuite, Rails, cloud, and integration work, the constant is the same: systems that have to work on Monday morning. If you want help with data & analytics, start with a short conversation about the process that hurts most. We will tell you plainly whether dedicated experts, a full application build, or a wider programme is the better fit — and what not to spend money on yet.

If you are planning work in this area, start with one process, one owner, and one measurable outcome. The rest of the programme becomes easier to defend.

What to decide before you buy more licences

Before another workshop or another tool evaluation, write down three things on one page: the process that hurts, the owner who can change it, and the metric that would prove the change worked. If you cannot fill that page, data & analytics spend will mostly buy activity.

If you can fill it, the rest gets simpler. You can choose an engagement model, set a first release boundary, and ask vendors — including us — for a plan that matches those constraints. That is how enterprise technology work stays human: fewer slogans, more decisions people can defend six months later.