Northwind: one dashboard instead of nine
Nine internal tools merged into one, with a permissions model that finally matched how the company actually works.
Every number here is the client's own measurement, taken at least three months after launch. Where a project did not move a number, we say so rather than finding a different number that moved.
Nine internal tools merged into one, with a permissions model that finally matched how the company actually works.
Identity, packaging and a storefront for a maker moving from market stalls to a permanent shop.
Rebuilt a reporting pipeline that had grown to a nineteen-minute wait. It now answers in under three seconds.
A scheduling tool designed for people standing in a hallway holding a phone and a bag.
"Our dashboard is ugly and slow. Redesign it."
There was no dashboard. There were nine internal tools, built by four teams over six years, and the "dashboard" was the one people had a bookmark for. Redesigning it would have made the prettiest of nine tools nobody could reconcile.
Two weeks of discovery, sitting with twelve people across three departments. The output was a map of which tool owned which piece of truth — and three places where two tools disagreed about the same number, which nobody had noticed.
We built one interface over the existing systems rather than replacing them, with a permissions model that matched the org chart instead of fighting it. Rollout was department by department over eleven weeks, with the old tools left running until each group stopped opening them.
We under-scoped the data reconciliation. Those three disagreeing numbers took three weeks to resolve, which we had not quoted for and absorbed. The lesson was to make "audit the data before quoting" part of discovery, which it now is.
"They spent the first fortnight telling us the thing we asked for would not work, and were right."
Priya Raghunathan — Operations Director, Northwind