The selected direction still had to account for what remained incomplete.

In 2023, Rellaveth Communications considered an 1800-kilometre owned-fibre proposal for two industrial corridors, with an estimated A$210 million capital requirement. A leased-access service proposal carried A$36 million over three years. The figures described different kinds and periods of commitment. I did not want their difference presented as a saving, or ownership treated as the natural starting point before the customer proposition had been tested.

Owen Darswell favoured the owned-network direction. He argued that greater control could support a more distinctive position and that leasing might leave us dependent on another provider at an important moment. Those concerns belonged in the choice. The alternative was not a simple contest between expensive ownership and inexpensive access; it involved different responsibilities, flexibility and commercial assumptions that engineering, operations and finance needed to examine.

I recommended a leased-access pilot focused on the intended service for twenty contracted sites, with A$4.6 million implementation expense. The purpose was to learn whether the proposition could be delivered in the selected setting before asking the company to commit to the wider ownership model. Network engineers and service teams owned the technical and activation work. I was responsible for connecting the pilot's evidence with the subsequent strategic question, rather than presenting myself as the designer or operator of the connections.

By June 2024, twelve of the twenty sites had been activated and eight remained pending. I reported both figures. The completed activations established a partial delivery outcome; they did not demonstrate full coverage, a finished corridor network or the economics of every future customer. The pending sites also meant the pilot could not be used as an unqualified endorsement of the selected approach. We still needed the responsible teams' account of what remained and what it meant for the broader proposition.

The choice postponed the ownership commitment and surrendered some of the control Owen wanted to establish early. It also made the next discussion more specific than a comparison of network maps. My lesson was to define what the pilot can teach before selecting a headline from its outcome. Every company, site and amount here is invented; a real account would need authorised customer evidence and professional assessment of the technical and financial alternatives.

A 2016 acquisition review at the fictional Rellaveth Communications covered a business with A$92 million trailing revenue, of which 61% came from project work. Some colleagues introduced the acquisition candidate through the enlarged scale it could bring to our connectivity portfolio. I thought the more important question was what kind of business we would be adding. The total alone could make the combined proposition sound more recurring than the underlying activity justified.

The acquisition sponsors wanted to integrate the acquisition candidate quickly into the main commercial account. A single proposition could be easier to explain, and separate reporting could make the company appear less unified just when it wanted customers to see a broader capability. I supported the attraction of that capability. My disagreement concerned whether a simpler presentation would obscure how the acquired work was actually sold, delivered and earned.

I recommended proceeding with a clear account of the project business and a distinct initial operating identity. The company completed an A$74 million purchase in 2017 under capital approval separate from my delegation. For the first eighteen months, the project unit remained distinguishable, with A$6.2 million integration expense. Commercial and delivery leaders retained responsibility for the actual work. Strategy's contribution was to ensure the acquisition rationale did not rely on relabelling the acquisition candidate's historical revenue as a different commercial relationship.

That approach did not provide the immediate simplicity some colleagues preferred. Customers and internal teams needed an explanation of how the capability fitted alongside connectivity services, and the institution had to tolerate a less uniform portfolio account while it learned. Nor did distinct reporting settle the long-term structure. It created a more honest starting point from which the company could examine what should be combined and what retained a different pattern of commitment.

The result claimed is the completed fictional acquisition and its initial treatment, not a recurring-revenue conversion, a margin improvement or an investment return. I learned that an acquisition can be strategically attractive precisely because it adds a different capability. The leader's job is to explain that difference and its consequences, rather than make the purchase appear coherent by giving every part of the revenue total the same name. A real public case would require verified financial definitions and permission to describe the transaction.

In 2021, a direct-retail proposal would have placed Rellaveth Communications in competition with six wholesale partners representing 28% of its 2020 service income. The new offer had its own attraction: a direct relationship could teach us more about the end customer and provide a clearer public identity for the service. I did not want the institution to discuss those advantages without also naming the position it would take relative to partners already using its network proposition.

The retail sponsors believed both channels could coexist. They argued that customers had different needs and that a direct offer need not displace every partner relationship. I agreed that conflict was not inevitable simply because two channels existed. But the proposal had not yet explained the boundaries convincingly enough for us to tell partners what would change. Treating the question as a communications exercise after the launch decision would have made the underlying strategic choice harder to assess.

I recommended a partner-only offer at that stage, with A$7.8 million in two-year enablement expense. The work focused on how the company would support the proposition through its existing route to market. Commercial and legal teams owned the actual partner arrangements; product and operations retained responsibility for deliverability. My role was to make the selected position explicit and ensure that the investment account reflected it, including the direct customer learning and public presence we were choosing not to pursue through retail.

Three partner addenda were signed by 2022. That was a documented outcome within the invented case, but it did not establish that all six relationships were retained or that the full 28% of service income was secured. It also did not prove the direct-retail proposal would have failed. The selected response produced a more defined partner proposition and agreements with three parties, while leaving the wider portfolio and future channel choices open to further assessment.

I learned to ask whether a strategy can describe its relationship with the market from the counterpart's perspective. A company may choose to compete with a partner, support it or distinguish different offers carefully. What it should not do is leave that position implicit while presenting growth as though relationships remain unchanged. All counterparties and results are fictional; no conclusion about a live commercial agreement or competition requirement is offered.

Soon after joining Rellaveth Communications, I helped prepare a 2009 market account that described 52000 premises passed as service-ready. Only 18500 had been verified under the definition used for the stated offer. Catrin Velmsley challenged the wording. I had taken a useful footprint measure and allowed it to stand for a more specific commercial condition. The error was mine to correct, even though the larger number made the proposed opportunity easier to present.

Some colleagues wanted to keep the stronger wording while the remaining premises were assessed. They regarded the footprint as a substantial advantage and worried that a smaller verified figure would understate the opportunity. I understood that concern. Premises passed still described reach relevant to future work; the correction did not make the wider footprint disappear. But an opportunity to investigate could not be described as though the offer-specific readiness work had already been completed.

I withdrew the service-ready claim attached to the 52000 total and supported A$1.3 million assessment expense. The revised account retained the footprint as one measure and the 18500 verified premises as another. Engineering and commercial colleagues owned the relevant evidence and definition. I did not infer that the remaining 33500 were impossible to serve, nor treat them as lost customers. Neither conclusion followed from the difference between the two recorded measures.

The immediate consequence was a less expansive readiness story and additional work. I had to explain why the earlier description should no longer be used, rather than quietly replacing the wording in the next presentation. That made my responsibility visible to people who had relied on the original account. The case contains no claim that the assessment converted the remaining premises or produced a resulting sales increase. It describes the corrected interpretation and the work commissioned to understand what the institution could actually offer.

The experience changed how I read network propositions. A large map may be accurate about physical reach while saying less about the service a customer can order. I now ask which definition a measure supports and which professional assessment establishes it. The numbers and people here are invented; a real public description would need its own documented definitions. The leadership lesson is to preserve the useful footprint without borrowing a readiness conclusion that its evidence cannot carry.

In 2025, a proposed change to Rellaveth Communications' enterprise offer involved 9200 sites using an existing service bundle. The new proposition could simplify the future catalogue, but it did not remove the commitments around those sites. I wanted the strategy to explain the transition as part of the offer decision, rather than treat the existing base as an operational detail to be resolved after the company had presented its new direction.

Product colleagues preferred a more decisive change in the public proposition. Continuing to support an older bundle could complicate sales conversations and divide attention across two sets of arrangements. That was a legitimate cost. I did not argue that every previous offer must remain indefinitely. My concern was that the pace of the strategic announcement should be connected to an account of what customers would actually encounter and what the responsible teams were prepared to support.

I recommended an eighteen-month staged transition plan with A$12 million allocated to service support. The plan required product, commercial, operations and customer teams to explain the conditions for moving the affected sites. They retained responsibility for specific arrangements and delivery. Strategy's work was to connect the future portfolio with the continuing promise, making the transition expense and attention visible within the choice rather than presenting the new bundle as if the existing one had already disappeared.

The outcome described is approval of that plan and allocation. It does not mean that 9200 sites were migrated, that customer consent had been obtained in every case or that the transition was completed without interruption. Those would be separate claims requiring their own evidence. The institution accepted a longer period with parallel support and the associated expense in order to prepare a change whose customer consequences could be addressed explicitly.

This decision reinforced my view that portfolio strategy includes the promises it supersedes. A clearer future catalogue can be worthwhile, but its simplicity should not be achieved by leaving the current customer's experience outside the account. The fictional case offers no advice about telecommunications obligations or technical migration. It shows how a strategist can make the next offer and the existing service population part of one assessable decision, while preserving the professional authority and evidence needed to carry out the work.