My responsibility grew from interpreting a proposition to explaining the portfolio it creates.

Mandate

Choose the commercial promise and ownership boundary of the connectivity portfolio.

Outcomes

• Selected a two-corridor leased-access pilot with A$4.6 million implementation expense; twelve of twenty contracted sites activated by June 2024, with eight pending.
• Recommended the 2021 partner-only proposition; three partner addenda signed by 2022 following A$7.8 million two-year enablement.
• Connected a proposed bundle change for 9200 sites with an eighteen-month transition plan and A$12 million service-support allocation.

Decisions in context

The CSO appointment brought responsibility for the commercial choices connecting the portfolio, rather than ownership of network engineering or operations. I began executive board presentations in February 2020 and needed to show how the selected proposition affected customers, partners and the capital question. The corridor pilot made that practical: twelve activations were a meaningful partial result, while eight pending sites remained part of the strategic evidence. The partner-only decision required me to state what direct-retail advantages the company was giving up. My current function expense supports strategy work; it does not make company acquisition or network budgets my delegation. I want the record to preserve those boundaries because they help a search reader understand the actual role. I would bring the same clarity to a first-board discussion, without equating the ability to present a recommendation with experience of holding a statutory seat.

Reason for the move

Current appointment; any outside board contribution requires permission, preparation and a separate time assessment.

Mandate

Explain the capability and commercial model each portfolio addition would bring.

Outcomes

• Identified 61% project-based income within the acquisition candidate’s A$92 million trailing revenue in the 2016 review.
• Supported the company’s separately approved A$74 million 2017 acquisition without relabelling the acquisition candidate’s total as recurring connectivity revenue.
• Kept the project unit distinguishable for eighteen months with A$6.2 million integration expense managed through its authorised programme.

Decisions in context

This appointment changed my question from where the company could offer a service to what kind of business it wanted to become. The acquisition case showed why a larger revenue total could be an incomplete explanation of growth. Project work could add valuable capability while retaining a different commercial pattern from the existing service base. I supported the purchase on that basis and accepted a less uniform initial portfolio account. The eighteen-month distinction gave colleagues room to examine combination without describing it as already complete. I worked through the responsible commercial, financial and delivery leaders; capital approval for the purchase was not part of my function delegation. The move to CSO followed experience in making those differences understandable at enterprise level, including the consequences of a choice that remained attractive even when its business model could not be compressed into the company's most familiar headline.

Reason for the move

Appointed CSO to connect individual portfolio choices with the company-wide service and partner position.

Mandate

Connect market opportunity with the evidence behind the offer the company could supply.

Outcomes

• Withdrew the 2009 description of 52000 premises passed as service-ready when 18500 were verified for the stated offer.
• Supported A$1.3 million assessment while retaining separate footprint and readiness measures.
• Developed market recommendations that identified the evidence required from engineering and commercial owners before a reach claim became an offer claim.

Decisions in context

Joining a connectivity company made the consequences of research language more immediate. My 2009 overstatement showed that a footprint measure could become a promise as it moved into a market account. I corrected the description rather than treating the discrepancy as someone else's technical qualification. The broader reach still mattered, but the verified offer-specific figure had a different meaning and needed its own place in the recommendation. I learned to ask the people responsible for service readiness to define what their evidence established before I used it to describe commercial opportunity. The role combined team leadership with a bounded expense remit; neither made me responsible for every network asset or customer contract. Portfolio strategy was the next step because I increasingly wanted to understand not only where an offer could be supplied, but which capabilities and relationships the company should choose to develop around it.

Reason for the move

Promoted into portfolio strategy after broadening market interpretation into capability and ownership questions.

Mandate

Lead research that connects a market finding with the terms of an actual customer proposition.

Outcomes

• Distinguished broad supplier presence from evidence about the particular offer a client wanted to introduce.
• Led research discussions that retained the customer question and the assumptions requiring further work.
• Developed the team’s ability to explain a finding without presenting the recommendation as an operating result already achieved.

Decisions in context

Research leadership added the responsibility to help colleagues explain uncertainty without making their work sound inconclusive. Clients needed a clear recommendation, but clarity could not come from suppressing the conditions that made the finding useful. I learned to ask which customer proposition the evidence concerned and whether the client was carrying it into a broader claim. Leading ten colleagues also meant deciding where further research would make a material difference and where it would simply add detail to the same unanswered question. My expense authority covered the team's delivery, not the capital decisions clients might make later. The move into Rellaveth reflected a wish to stay with the consequences of those decisions. I wanted to learn how an institution handled the period after a persuasive research presentation, when the proposition had to be reconciled with its capabilities, partners and commitments to customers.

Reason for the move

Joined Rellaveth to take continuing responsibility for how research informed an institution’s own strategic choices.

Mandate

Understand the customer need and the assumptions connecting it with a supplier’s proposed offer.

Outcomes

• Prepared findings that separated observed customer needs from a supplier’s desired market position.
• Learned to identify the question a study could answer and retain the conditions attached to it.
• Built the commercial interpretation skills that supported promotion into research leadership.

Decisions in context

My first role followed a commerce degree and involved learning how to listen to a business customer without immediately turning the answer into support for the client's preferred offer. A supplier could be well known and still need to explain why a specific proposition suited the customer. I worked in a five-person analyst group and had no budget authority or direct reports. The contribution was analytical: recording the question, interpreting the evidence and keeping the scope of the finding clear. I was drawn to work where an apparently simple growth idea contained a more difficult commercial choice. Those early habits later helped me in connectivity, although the service-readiness mistake shows they were not automatically preserved under pressure. The promotion gave me responsibility for how a team carried such distinctions into recommendations, rather than only for the accuracy of my own research notes.

Reason for the move

Promoted to lead commercial research after developing client-explanation and team-support experience.