What a CDO should measure in their first 90 days

The risk of inheriting the dashboard

A digital executive joining an organisation receives, in their first week, a set of reports representing years of internal agreements: what counts as a conversion, how a sale is attributed, what qualifies as an incident. Those agreements are rarely neutral. They usually reflect which function needed to demonstrate what at the time they were defined.

Accepting that dashboard as a starting point means inheriting its blind spots too. The work of the first ninety days is not to improve the numbers, but to discover which questions they make impossible to ask.

Four checks before setting priorities

Verify the definition, not the value

Before debating whether conversion is high or low, it is worth establishing what counts as a visit, a session and a conversion, and checking whether that definition matches across analytics, the transactional system and the report the committee sees. Discrepancies between those three sources usually explain more than any subsequent analysis.

Reconstruct the economics, not just the volume

Many organisations know their digital volume and not their contribution. Reconstructing margin per order, associated cost to serve, returns and cancellations reveals whether channel growth is adding or consuming profitability. It is common to find segments that grow and destroy margin simultaneously.

Locate where decisions are actually taken

The org chart shows formal responsibility; the budget process shows real power. Identifying who approves a priority, who can veto it and who carries its outcome explains why previous initiatives stalled halfway. Without that map, any plan risks repeating the earlier blockage.

Measure the cost of the exception

Digital organisations tend to measure the happy path and ignore the cost of the detour: how many cases require human intervention, how long they take, what they cost. That figure has a useful property — it almost always points to the most profitable problem to solve, and it almost never appears on the inherited dashboard.

A reasonable calendar

Weeks 1 to 3: reconcile definitions across analytics, transactional systems and executive reporting.

Weeks 3 to 6: reconstruct unit economics by segment and channel.

Weeks 5 to 8: map decisions, vetoes and real dependencies.

Weeks 7 to 10: quantify the cost of exceptions and the support they generate.

Weeks 10 to 13: present three priorities with estimated contribution and declared risk.

The minimum dashboard at the end of the period

• Contribution by channel: margin after cost to serve, not revenue.

• Cross-source discrepancy: percentage difference between systems for the same metric.

• Cost of exception: annual value of cases leaving the automated path.

• Decision time: days between a prioritised proposal and effective approval.

• Critical dependencies: initiatives blocked by a single system or team.

Common mistakes in the early months

• Announcing targets before verifying definitions.

• Prioritising visible redesign over data reconciliation.

• Mistaking rising volume for a healthy business.

• Accepting the decision map the org chart describes.

A useful check at the close of the period: if the three proposed priorities match exactly those already on the table before the appointment, the diagnosis has probably confirmed assumptions rather than examined them.

Conclusion

The first ninety days produce a concrete asset: a dashboard the executive team can trust and a map of where decisions are really made. With those two things, subsequent priorities are debated on evidence. Without them, they are debated on reports nobody has verified.

Consumer Services Hub - Strategic ecommerce consultancy for B2C service companies

consumerserviceshub.com