My remit grew as the consequences of an interpretation stayed with me longer.

Mandate

Keep transaction meaning and observation conditions visible in data used for retail decisions.

Outcomes

• Released separate order-cohort and event-calendar views in December 2023, retaining the returns cutoff.
• Kept 140 missing stock observations distinct within the 2021 pilot instead of treating every zero-sale day as demonstrated weak demand.
• Withheld an all-catalogue preference claim from the 2025 recommendation replay because exposure constrained what had been observed.

Decisions in context

The current role brings together questions that arise in different parts of the retailer but share a need for a defensible account of evidence. I lead the data function, not the commercial decisions made from every report. Returns timing required a relationship between two operational views; the stock pilot required missingness to remain visible; recommendation evaluation required the history of exposure to stay attached to the observations. Those are different problems, and I want the team to explain the distinction before offering a common reporting solution. Executive presentations to the board began with this appointment. They do not create statutory-director experience, and the record contains no such seat. My expense delegation funds the data work. Finance, merchandising, store operations and technology owners retain their own responsibilities, so the company’s scale should not be mistaken for a personal claim to all of its systems or results.

Reason for the move

Appointed CDO following commercial-analytics leadership; current position.

Mandate

Explain the basis of comparisons used in trading discussions without allowing a convenient adjustment to imply complete comparability.

Outcomes

• Challenged the 2017 like-for-like label applied to EUR 156 million over 13 weeks versus EUR 144 million over 12 weeks.
• Retained full-period totals alongside explicitly defined comparison views.
• Supported EUR 1.8 million reconstruction without presenting a weekly division as a complete answer to perimeter and trading differences.

Decisions in context

This appointment moved my attention from the construction of a report to the claim it made in a trading conversation. The thirteen-week comparison was arithmetically simple and interpretively difficult. A total increase could be correct without establishing comparable performance. Dividing by the number of weeks supplied another view, but it did not eliminate every difference in the business being compared. I wanted the team to keep the transformation and its purpose visible rather than let the most convenient number become the only account. Commercial colleagues needed concise material, so the response had to improve explanation without requiring every meeting to reconstruct the analysis. Finance retained official reporting authority. The director title described my employment role; it was not a board appointment. This period prepared me to examine how a data conclusion travels between functions and acquires more certainty than its original definition supports.

Reason for the move

Promoted to CDO as the remit expanded from commercial analysis to the retailer’s wider data evidence.

Mandate

Maintain intelligible retail definitions as source records become recurring operating reports.

Outcomes

• Accepted responsibility for the 2009 report adding 4200 cartons and 5400 single items as 9600 units.
• Reconciled the documented twelve-item cartons to 55800 physical items while retaining the original handling account.
• Supported EUR 360000 review and reprocessing without claiming recovered inventory or additional sales.

Decisions in context

Joining the retailer meant living with definitions after the original project had ended. A report might become familiar enough that no one asked again what its unit represented. That familiarity contributed to the warehouse-transfer error I approved. Luc Tervalon’s challenge showed that the records and the interpretation needed to be examined separately: a count of handling units could be legitimate while the physical-item claim I endorsed was wrong. I wanted the correction to preserve both accounts so another reader could understand the conversion instead of simply accept a replacement total. My team owned review and reprocessing, while logistics colleagues retained the actual movement of goods. The experience made me more attentive to apparently ordinary words in a report. It also changed how I described success: correcting the evidence was consequential, but it did not entitle me to claim an operating benefit the record had not measured.

Reason for the move

Advanced to commercial-analytics leadership after responsibility for recurring retail data and its interpretation.

Mandate

Lead assignments whose conclusions retain their observational basis when reused in client reporting.

Outcomes

• Required the analytical question and the source observation to remain connected in delivered findings.
• Explained where a summary depended on a transformation rather than a direct observation.
• Sought an in-house role to remain responsible for definitions as they became part of routine retail work.

Decisions in context

Leading assignments required me to make the analytical work useful to people who would not inspect every source record. I wanted a clear explanation of what the finding meant and what change in circumstances would alter that meaning. The difficulty was often what happened after delivery. A definition carefully discussed once could be shortened as the report circulated, until the client used the measure for a question it had not been designed to answer. I could improve the handover, but I was increasingly interested in staying with that continuing responsibility. My delegated expense covered delivery of the assignments rather than the client’s business decisions. The move into retail was therefore a change in accountability as well as employer: I would help maintain the evidence over time and would have to respond when a familiar internal report acquired an interpretation I could no longer defend.

Reason for the move

Joined Bravernel to follow data definitions through continuing use inside one retail institution.

Mandate

Trace analytical findings to the records and definitions that determine their meaning.

Outcomes

• Checked whether quantities combined in a calculation shared a definition.
• Distinguished the question a dataset could answer from the broader question a reader might assume it answered.
• Developed an interest in the continuing use of analytical measures after a research assignment.

Decisions in context

I joined after applied-statistics study and worked on the less visible part of an analytical account: understanding what each observation represented before combining it with others. The calculations could be elegant while the source meaning was unsettled. I learned to ask who had recorded the event, at what stage and for which purpose, then consider how those conditions shaped the conclusion. My role was an individual contribution within a nine-person group, with senior colleagues responsible for delivery commitments and expense. The later scale of Bravernel does not belong to this period. What carried forward was an interest in the gap between the event and the measure presented to management. That interest did not prevent my later carton mistake, but it gave me a way to explain the failure and reconstruct the account when a colleague challenged the familiar unit label.

Reason for the move

Promoted to engagement leadership after developing analytical delivery and client-explanation experience.