Following the evidence from fieldwork to oversight

Mandate

Make analytical outputs usable with their timing, population and evidence limits intact.

Outcomes

• Withheld a credit prototype after identifying later-event inputs and revising validation
• Restated a regional growth comparison on consistent service-area boundaries
• Replaced unsupported zero defaults with explicit historical-coverage states
• Restricted small-group dashboard views after inference review

Decisions in context

The CDO appointment brought analytical development and stewardship into a common function while preserving the decisions held elsewhere. I organised four management responsibilities around source stewardship, analytical delivery, data quality and platform coordination. Technology operations, security, privacy and risk validation remain separately accountable. I spend much of my time making a technical limitation understandable to the executive who must decide what to do next. That can mean withdrawing a score from a release discussion or explaining why a chart now covers fewer records. I report to the CEO and present to directors when invited, without a directorship. The role has reinforced my view that useful data leadership includes an alternative and an owner for the next step. Merely identifying a problem is insufficient, but inventing certainty to keep a timetable is worse than explaining the work that remains.

Reason for the move

Current appointment; developing stewardship and review capability across the four management teams.

Mandate

Make definitions, source responsibilities and historical limitations explicit across management reporting.

Outcomes

• Assigned accountable owners to recurring ambiguous source fields
• Documented coverage differences in historical analytical extracts
• Introduced a review of definition changes before comparative reports were released

Decisions in context

Leading stewardship meant moving from solving a report to improving the conditions under which many reports were produced. I built a fourteen-person team and worked with the COO to identify business owners who could explain and authorise changes to source records. We documented the meaning of fields as systems and reporting needs evolved. The work required patience: a disagreement over a definition often reflected different legitimate uses rather than one careless department. I learnt to preserve those uses while making their boundaries explicit. Historical extracts were a particular concern because a complete technical transfer could still leave gaps in what had been observed. This appointment developed my ability to lead across functions without claiming their authority. It also showed the need for a data office that could connect stewardship with new analytical development before the two became separate conversations about the same records.

Reason for the move

Appointed to establish the chief data office as analytical demand expanded.

Mandate

Produce intelligible management comparisons from records owned by banking functions.

Outcomes

• Recorded the population and reporting period beside recurring management measures
• Reconciled operational and analytical totals without treating them as interchangeable
• Coordinated a small analysis team from 2012

Decisions in context

Joining the bank required me to learn the meaning of records before applying familiar statistical methods. Finance, operations and credit colleagues used related data for different responsibilities, and an internal management comparison was not automatically a formal financial statement. I worked under the planning head to explain those distinctions in recurring reports. The practical work involved tracing unexpected changes to their source, checking the reporting period and asking which population a manager meant to compare. From 2012 I coordinated three analysts, reviewing their reasoning as well as their calculations. I did not approve changes to customer records or credit decisions. The appointment gave me a banking foundation and exposed a recurring organisational problem: analysts were repeatedly resolving ambiguity that needed an accountable source owner. That became the central purpose of the stewardship role I took in 2014.

Reason for the move

Promoted to build a dedicated stewardship function after repeated definition and source-ownership issues.

Mandate

Explain district activity with its seasonal and coverage context.

Outcomes

• Separated seasonal reporting windows before comparing district activity
• Tracked service-territory changes alongside recurring reports
• Documented incomplete field returns rather than filling them with assumed zeros

Decisions in context

At Oshvera I worked close to a service operation whose activity changed with agricultural seasons. A busy district could reflect the timing of field work, a revised service territory or a genuine increase in demand. I learnt to ask district coordinators what had changed before presenting a rate of growth. The company coordinated soil-testing work and equipment service visits; it was not a lender, and my role did not involve advising farmers on credit. I prepared reports for the operations planning manager and had no budget authority. The experience made the calendar and the geographic boundary part of my analytical habits. It also taught me to explain a limitation in language that colleagues scheduling people and vehicles could use. When the bank recruited me, I wanted to bring that discipline into an institution where many decisions depended on shared records and carefully distinguished responsibilities.

Reason for the move

Moved into banking to apply reporting discipline to a broader and more consequential set of decisions.

Mandate

Preserve the meaning and limits of field observations during coding and analysis.

Outcomes

• Distinguished unanswered, declined and unrecorded responses in assigned datasets
• Documented coding changes before revised tables were issued
• Explained sample limitations in project reporting notes

Decisions in context

My first role began two months after graduation. I checked returned questionnaires, discussed ambiguous responses with field supervisors and prepared tables for a senior research manager. The work taught me that an empty field could have several meanings, none of which should be chosen merely to finish a calculation. I also saw how a small coding change could alter a conclusion when the respondent population was limited. I was not responsible for the client's policy or commercial decision, but I was responsible for explaining the evidence supplied. Keeping notes on definitions and changes became part of my craft. After five years, I wanted to see how analysis was used repeatedly inside an operating business rather than delivered at the end of a commissioned project. That interest led me to agricultural-service reporting and, later, to the bank's management-information function.

Reason for the move

Joined an operating company to follow how recurring analysis affected practical decisions over time.