Senior Partner – Transformation — Digital-Services Division

The mandate

An integrated telecommunications group has expanded its digital-services portfolio across managed cloud, cyber security, workplace, networking and service integration. Growth has brought capable people and valuable customer relationships, but investment decisions have accumulated by product and acquisition. Shared network capacity, automation, observability, identity, service management and migration tooling now compete with new offers for funding. Delivery teams carry more customer commitments than the underlying platforms and specialist workforce can reliably support.

The advisory partnership is creating a Senior Partner – Transformation role to lead a board-sponsored reprioritisation. The partner will determine which investments protect contracted outcomes, which create defensible growth, which should be sequenced and which no longer warrant capital. They will then remain through mobilisation, ensuring that approved choices change engineering queues, commercial behaviour and customer delivery rather than ending as a portfolio presentation.

The assignment requires independence from both cost reduction and technology advocacy. Deferring essential resilience would create false savings; continuing every strategic initiative would preserve the current overload. The Senior Partner must make the opportunity cost visible and help executives take decisions that their matrix structure has repeatedly postponed.

Scope and operating context

Based onsite in Sydney, the role influences approximately 925 employees and material partners across Australia and a wider international region. The client perimeter includes digital-services management, network and cloud engineering, cyber operations, product, enterprise sales, service delivery, finance, procurement and workforce planning. Some assets and specialist teams remain in group functions, while customer accountability sits in the division.

The portfolio mixes recurring managed services, project-led migrations and usage-linked products. A platform investment may improve several services but lack a single sponsor; a customer-specific workaround may appear modest while consuming scarce engineering capacity for years. Business cases frequently use different assumptions about customer adoption, delivery labour, vendor cost, depreciation and benefit timing. Comparing them requires a common economic and operational language.

Customer obligations impose constraints that a normal zero-based review could miss. Security controls, recovery, data location, response time and migration dates may be contractual or regulated. At the same time, commercial teams sometimes promise road-map features before architecture and capacity are funded. The transformation must reconcile commitments with a supportable service catalogue and a transparent path for affected customers.

First-year agenda

The first eight weeks will produce a single investment and obligation map. The Senior Partner's team will catalogue active initiatives, remaining spend, engineering demand, vendor commitments, customer dependencies, risk consequence and expected benefit. They will trace a selection from original approval to current status, testing whether scope, cost and adoption assumptions still hold. Unrecorded work and capacity consumed by bespoke customer changes will be included.

The partner will establish decision categories rather than apply a uniform reduction. Mandatory resilience and compliance work will be tested for efficient design but protected where evidence supports it. Contracted customer enablers will be ranked by consequence and value. Shared productivity and automation will compete on measurable capacity released. Growth propositions will require credible demand and delivery readiness. Experiments will receive bounded funding, and stranded or duplicative initiatives will be candidates for closure.

A cross-portfolio capital council will make the choices. Each proposal will state its customer or control outcome, total cash and labour requirement, architecture dependencies, operating-cost effect, risk, milestone evidence and stop conditions. The Senior Partner will provide a fact base and recommendation but preserve executive ownership of the decision. Deferred work will remain visible with the consequence of deferral, preventing it from returning informally through functional budgets.

Capacity planning will be joined to the portfolio. The team will identify constrained engineering skills, security approvals, test environments, migration factories and service-transition leaders. Demand will be shaped to those bottlenecks while recruitment, partners, simplification and automation address them. Buying more contractor hours will not be treated as a substitute for removing avoidable custom work or clarifying product standards.

The commercial contract between product and sales will also change. Offers that depend on unfunded road-map capability will require explicit approval, price and delivery conditions. Product leaders will publish supported configurations and retirement paths. Exceptions for strategic customers will carry lifetime service cost and an accountable exit plan. Customers affected by sequencing decisions will receive a credible explanation and alternative, not an internal-budget excuse.

Implementation will begin while the review continues. A small number of overextended platforms will be stabilised through work-in-progress limits, clearer service ownership and targeted tooling. At least one low-confidence build will be stopped or redesigned, with people and capital visibly redirected to a higher-value constraint. These early cases will demonstrate that reprioritisation changes real work.

By year-end, the division should have fewer active initiatives, stronger delivery predictability, reduced high-risk capacity gaps and a portfolio whose financial forecast reconciles with engineering reality. The client team must own the method and be able to repeat the choices without permanent adviser dependency.

Leadership responsibilities

The Senior Partner will lead the transformation office and counsel the division executive, group technology leadership and board sponsors. They will create a common account of investment and delivery, surface conflicts early and prevent functional negotiation from obscuring enterprise trade-offs. When evidence is insufficient, the partner must recommend a bounded discovery or test rather than allow false precision.

They will appoint workstream leaders, integrate technical and commercial analysis, and review client-ready conclusions personally. The partner is responsible for engagement quality, benefits integrity, team safety and fee economics. They must distinguish a client request that adds necessary evidence from scope expansion that delays decision.

The role will also coach executives through the human consequence of closure and delay. Teams that have invested professional identity in an initiative deserve direct explanation and fair redeployment. Candour must coexist with respect; transformation cannot depend on ambiguity until people quietly leave.

Measures of success

The board will review capital and operating spend released or redirected, initiatives stopped, work in progress, milestone reliability, engineering capacity against demand and platform risk. Benefits will be classified as realised, contracted or forecast and reconciled to finance. Moving cost between budgets or postponing necessary work will not count as value.

Customer and operational measures include delivery lead time, missed commitments, service incidents, security exceptions, migration throughput and recurring gross contribution. Leadership measures include decision cycle time, clarity of ownership, workforce redeployment and adoption of the portfolio method. The advisory partnership will examine client confidence, quality, contribution and whether the team exits on schedule.

Candidate profile

Candidates should have more than 28 years in major technology transformation, telecommunications, cloud or digital-services leadership, including senior advisory responsibility. They must have led capital reprioritisation where network or platform interdependence made simple project ranking inadequate. Experience carrying recommendations through delivery and customer consequence is essential.

The partner council will seek examples of stopping a politically sponsored initiative, protecting unglamorous resilience funding and converting technical capacity into an executive portfolio constraint. Candidates should understand managed-service economics, cloud and network architecture, cyber control, enterprise contracts, workforce capacity and capital governance.

The right leader will earn credibility with engineers without becoming captured by solution detail. They must challenge commercial optimism, translate uncertainty for a board and hold a firm line when every sponsor argues that their project is exceptional. A calm, evidence-led style is more valuable than theatrical transformation language.

Compensation and appointment terms

The indicative base salary is AUD 620,000–850,000, with annual incentive and long-term participation. Reward will reflect client value realised, decision quality, delivery adoption, engagement contribution and development of client and advisory talent. Any result-linked element will use board-approved definitions and independent finance validation.

Confidentiality

The client remains confidential because investment choices, capacity gaps, customer commitments and potential programme closures could affect commercial relationships and employees. Detailed information will be provided only after identity, conflict and confidentiality review. Applicants must not submit another client's road maps, architecture, contracts or transformation materials.