Market share business intelligence dashboards for Mastellone Hnos

Mastellone Hnos tracks its market share and claims management on business intelligence dashboards. The dashboards existed and the area was abandoning them.

The least glamorous phase of a data project is the decisive one: a report whose sales totals do not match the source system does not have a cosmetic problem, it has a credibility problem, and a dashboard nobody believes stops being used.

• Totals that do not add up: dashboard sales figures diverged from the source system.
• Desynchronized filters: selecting in one was not reflected in the rest, and the category filter altered totals.
• Dirty data: duplicates in the product list and a year selector returning wrong units.

Each on its own looks minor; together they explain why an area goes back to requesting the report by email.

The work was organized in successive phases, tackling data reliability and the functional expansion the area wanted in parallel.

Each phase had its assessment, its estimate and its close, so the area could prioritize between fixing and adding with the cost of each in view.

Data reliability first

• Removal of duplicates in the product filter, taking the code as the unique value.
• Resolution of the discrepancy between dashboard sales totals and the source system.
• Fix of the category filter, which was altering total sales values.
• Fix of the year selector, which displayed incorrect units.
• Synchronization of filters, so one selection is consistently reflected.

Functional expansion

• Market share report split onto its own page, outside the consumer trends block.
• Filter search with alphabetical ordering by description.
• Interactive titles on trend charts, reflecting the active selection.

More management dashboards

• Beyond market share tracking, claims and community dashboards were developed.

Architecture and technology

• Business intelligence dashboards over the group's sales and management data.
• Phased method with requirements assessment, per task estimation and closing document.

Learn more about software development.

The dashboard recovered the only thing that makes it useful, which is the business believing it.

Starting point

• Dashboard sales totals diverging from the source system.
• Filters that did not synchronize and a year selector with wrong units.
• Duplicates in the product list.

Strategic impact

• Reliability fixes were treated as a priority, not as background maintenance.
• The phased method with estimates let the area choose between reliability and new functionality with the cost in view.
• Market share, claims and community were left as dashboards of their own.
• The share report moved out of the trends block onto its own page.