I moved closer to the decisions that turn customer evidence into an offer.

Mandate

Define the commercial undertaking behind repeatable services and partner-backed propositions without obscuring the customer work that remains different.

Outcomes

• Narrowed the 2021 channel proposition from nine proposed offerings to five supported by the reviewed arrangements.
• Supported eight standard and four bespoke programmes in the 2023 shared-core review, retaining CNY 8.4 million proposition expense.
• Selected a narrower partner-backed service in 2025 without calling the difference between unlike budgets a realised saving.

Decisions in context

The CSO remit requires me to connect the provider's strategic description with the customer undertaking it is prepared to make. A partner relationship, a shared technical asset and a development budget each describe part of a proposition. None alone establishes the whole offer. I work with colleagues who own the commercial, technical and delivery decisions to make those boundaries visible in the institutional account. My seventy-two-person function has a defined expense delegation, distinct from the resources involved in fulfilling every customer programme. Executive presentations to the board began with this appointment, but I have not served as a statutory director. The channel and standardisation cases show where the initial description was narrowed, while the make-or-partner choice retains the control given up. These are the decisions through which I would explain my contribution, rather than presenting all company revenue or technical development as my personal responsibility.

Reason for the move

Appointed CSO after responsibility for the service portfolio; current role.

Mandate

Examine how the provider’s service portfolio represented recurring work, initial transition and customer-specific responsibilities.

Outcomes

• Kept CNY 17 million initial transition and project work visible alongside CNY 48 million contracted annual service fees in the 2016 cohort.
• Supported CNY 2.1 million assessment and commercial redesign expense.
• Prevented unlike fee and cost quantities from being presented as a simple margin calculation in the strategic account.

Decisions in context

Portfolio responsibility widened my attention from an individual offer to the commercial model represented by the collection. The recurring-contract review became a useful test of the distinction. Annual service fees were relevant, but their label did not remove the initial work needed to establish the service. I wanted the account to describe where the business had become repeatable and where it remained dependent on project activity. Finance and contract colleagues retained their professional responsibilities, including the treatment of figures that were not a complete comparable-period margin account. The director title was functional and carried no statutory seat. The appointment prepared me for wider strategy work by requiring me to question an attractive category without dismissing the legitimate development it represented. A provider could be moving towards a different model while still needing to disclose the work that had not yet changed.

Reason for the move

Promoted to CSO as the business’s service and partnership choices broadened.

Mandate

Identify which elements of customer work could support a repeatable commercial proposition and which differences should remain explicit.

Outcomes

• Owned the 2009 decision to preserve fourteen local variants without sufficient evidence of separate buyer requirements.
• Reconciled the reviewed catalogue to six distinct needs and eight variants lacking an independent commercial reason.
• Retained CNY 1.9 million in catalogue and research correction expense.

Decisions in context

Joining Xunveris made the provider's own history part of my work. Customer projects had left technical material and commercial descriptions that could be useful again, but reuse required a more exact account than simply keeping everything visible. The fourteen-variant mistake came from my preference for preserving choice without first establishing what choice the buyer actually faced. Correcting it did not require denying the value of colleagues' earlier work. It required separating useful internal material from a distinct proposition the next customer should be asked to understand. Existing commitments and technical assets retained their responsible owners throughout the review. This role gave me a specific failure to carry into later standardisation discussions. I could see how a supplier might preserve too much complexity for its own reasons just as easily as it might standardise too much and overlook a legitimate customer difference.

Reason for the move

Promoted to service-portfolio responsibility after nearly seven years in planning.

Mandate

Turn research about customer requirements into a proposition assessment the responsible client leaders could examine.

Outcomes

• Distinguished supplier categories from the operating problems customers expected a service to address.
• Connected commercial recommendations with the responsibility the provider would need to undertake.
• Developed an interest in shaping a service portfolio from inside the provider rather than through external projects alone.

Decisions in context

As an engagement lead I had to make the team's research useful to people choosing what kind of service business to develop. The customer account could not remain a collection of interviews separate from the provider's proposed responsibility. I worked with colleagues to identify which differences mattered to the buyer and which reflected the supplier's preferred categories. My delegation paid for our work; it did not control the client's investment or contract decisions. That limit helped me learn to make a recommendation precise enough for another authority to assess. Moving into Xunveris was a deliberate change in relationship with the work. I wanted to follow the proposition after the initial assessment, including what happened when the catalogue, commercial terms and delivery experience began to diverge. The advisory appointment supplied questions I could carry into that continuing role without pretending it had already given me operating authority inside the client.

Reason for the move

Joined Xunveris to take continuing responsibility for enterprise-service planning.

Mandate

Examine customer requirements and the assumptions used to describe a proposed service.

Outcomes

• Learned to ask what operating problem sat behind a familiar supplier category.
• Identified when similar language concealed different customer responsibilities.
• Built research habits that later informed the distinction between technical reuse and a repeatable business proposition.

Decisions in context

I entered the research role after completing management studies in June 1991. The initial responsibility was to contribute a clear account of what the evidence showed, within an eight-person team. I did not own the client recommendation or the spending decisions that could follow it. I became interested in the way service descriptions could make different customer requirements appear similar, or make a common requirement appear fragmented across supplier categories. The work encouraged me to follow the customer's intended activity before accepting the name of the offer as a sufficient explanation. That habit did not prevent my later catalogue mistake; I still needed to learn how easily a provider's history could influence my own interpretation. The early appointment belongs in the record at its actual scale, as the beginning of a question I continued to refine rather than an invented claim to leadership before I held the responsibility.

Reason for the move

Promoted into engagement leadership after developing research and client-discussion experience.