Ampol Group
Product CoE
Mandate & Charter · v3

Product Centre of Excellence

A centralised function that guides through expertise, builds capability in domain teams, and creates the cross-domain visibility that no single team can achieve alone.

Owner
Products@Ampol
Facilitated by
Opposite
Review cycle
6 months
What the CoE is and why
01 · Why this exists

What the CoE is built to do.

The CoE exists to improve the performance and value of Ampol Group's products for customers and the organisation. It will address three key business problems and drive increased product performance across Ampol Group.

Problem 01
Product work is fragmented across domains.
The CoE brings an enterprise-wide view, surfacing risks, dependencies, and shared benefits that no single domain can see alone.
Problem 02
Decisions are made without consistent customer evidence.
The CoE connects leaders to evidence, making sure customer signal and commercial viability shape product decisions together.
Problem 03
Ownership and lifecycle discipline vary widely.
The CoE builds shared language and capability: common lifecycle stages, processes, named owners, and the dedicated time, advice and support to apply them well.
02 · Product Framework

The shared language that connects product work.

A common model for how Ampol Group defines, organises, and views its product portfolio.

Not everything the CoE works with is a Product. Some are systems that enable products to function. Others magnify the reach and value of existing products. Understanding these three layers matters because the CoE's involvement, recommendations, and lifecycle expectations differ depending on what type of item is being assessed.

Magnifier
Enabler
Product
Offerings directly bought, subscribed to, or consumed by customers that generate value and revenue. Products are what customers see, use, and pay for.
Systems, capabilities, and infrastructure that allow products to function and scale. Enablers power delivery.
Features and activities that amplify reach, differentiation, and competitiveness of the core product offer, such as marketing and digital engagement.

Products are grouped into four customer experience domains. These provide a portfolio lens for organising and aligning product work across the business, not a change to reporting lines.

Smart Mobility

Secure digital and payment experiences that unify mobility and energy offerings.

Everyday / Consumer

Convenient and predictable experiences across fuel, EV charging, food and amenities.

Operational Mobility

Reliable fuel, lubricant and energy solutions that prioritise safety, continuity and uptime.

Commercial Mobility

Integrated mobility solutions that optimise cost and simplify fleet operations.

In this charter, domain refers to one of the four experience domains. Portfolio refers to the collective set of products across all domains, viewed at group level.

03 · Authority

Advisory by default.

The CoE is here to help products perform. It advises, coaches, and connects, and raises visibility when something needs broader attention.

Default Mode

Advisory.

The CoE shares frameworks, provides coaching, documents observations, and reports insights. Domain teams decide whether and how to act.

Support is always accompanied by a specific action plan: what will be done, by whom, by when.

Default triggerA domain asks for help, or the CoE identifies an opportunity to improve product performance.
When more is needed

Connecting teams with the right support.

When a product needs attention beyond what a single domain can provide, the CoE connects the right people, evidence, and resources to help that product perform.

The CoE works to establish clear ownership and to make sure portfolio-level risks have the right visibility and accountabilities.

TriggersA product has more potential · ownership is unclear · cross-domain dependencies would benefit from coordination · evidence suggests a different lifecycle stage is warranted.

Discipline is expected to increase progressively over time as trust, evidence, and shared language are established.

04 · Known For

The story we want to tell.

When the CoE is live and working well, this is what the business will see, hear, and experience.

Building Capability
The CoE uplifts domain teams with the skills and frameworks to manage their products well. Offers of support come with action plans and tools.
Success means the CoE becomes less needed over time, not more. Teams are self-sufficient and confident in their product practices.
Creating Visibility
The business has a clear, enterprise-wide view of its product portfolio. Performance, dependencies, and opportunities are visible.
Leaders make decisions with confidence because they can see across domains, not just within them.
Creating Fitness for Purpose
Specific product challenges are catalysts for systemic improvement and assessing whether current models and ways of working are still right.
When something isn't working, the CoE helps the team redesign the approach.
Keeping Customer at the Centre
Customer evidence and commercial viability drive product decisions with the business.
Product decisions feel grounded. Teams can point to the evidence behind their choices.
Building Lifecycle Discipline
The business has a shared rhythm for how products move through a lifecycle. The CoE acts as a facilitator of consistency and portfolio health.
There's a common language, a shared playbook, and a clear sense of who owns what at each stage.
How the CoE works in practice
05 · Scope

What the CoE decides, recommends, and where it does not get involved.

Ownership of products remains with business units. The CoE works with the business and does not take over accountability for product performance.

AreaAuthorityIn practice
Dashboard metrics & reportingDecideDefines what gets measured and how it is reported at portfolio level.
Template & artefact designDecideOwns design and maintenance of lifecycle artefacts, stage transition templates, and assessment tools.
Lifecycle gate criteriaDecideDefines what each lifecycle stage transition requires. Domain teams apply the criteria to their products.
Product classificationDecideDetermines what counts as a Product, Enabler, or Magnifier.
Cross-domain coordinationDecideConvenes domain teams when dependencies or overlaps are identified.
Portfolio prioritisationRecommendProvides evidence-based recommendations at group level. Decisions sit with domain leadership and executive forums.
Lifecycle stage transitionsRecommendProposes stage changes (including launch and retirement) based on evidence. Domains decide.
Owner assignmentRecommendIdentifies ownership gaps and recommends named owners. Domain leadership decides.
Capability assessmentRecommendEvaluates product maturity and recommends capability interventions.
Day-to-day product deliveryOut of scopeOperational product management remains with domain teams.
Domain commercial decisionsOut of scopeThe CoE provides evidence; domains make commercial decisions.
Technology platform choicesOut of scopeTechnology decisions sit with Technology, Digital and Data.
Customer research executionOut of scopeThe CoE supports the use of evidence in decisions but does not conduct customer research directly.
Product & CX design executionOut of scopeDesign execution sits with domain teams.
Decision rights will be reviewed after the first six months of operation.
06 · The Model

How the CoE sits in the business.

The CoE provides an enterprise view, connecting decisions to evidence and coaching the business on language, process, and discipline. It indirectly strengthens Ampol Group's four customer domains.

Smart
Digital & payment
Everyday
Fuel · EV · food
Operational
Fuel · lubricants · energy
Commercial
Fleet & mobility
Business Operations
Domain teams own products, run delivery, make commercial decisions
Frameworks · Coaching · Visibility · Facilitation
Requests · Collaboration · Continuous improvement
Product Centre of Excellence
Lifecycle
  • Stage definitions & gate criteria
  • Lifecycle assessment & classification
  • Product Playbook ownership
Visibility
  • Portfolio performance data & insights
  • Dashboard metrics & reporting
  • Cross-domain dependency scanning
Capability
  • Product capability uplift & coaching
  • Product Library design & maintenance
  • Group-level prioritisation facilitation
Evidence
  • Customer evidence & commercial viability
  • Product positioning & market fit methodology
  • Evidence-based decision support
Authority is advisory by default. The CoE connects teams with the right support and raises visibility when a product needs broader attention. Discipline is expected to increase progressively as trust is established.
07 · Lifecycle Presence

Where the CoE shows up in the life of a product.

At each lifecycle stage, the CoE has a typical level of involvement. These were agreed in the second CoE design workshop.

The level shown for each moment is a starting position. The CoE may step up or step back depending on the domain team's needs.

Monitors
The CoE watches from a distance and acts when something signals attention is needed. The domain team leads.
Guides
The CoE provides advice, frameworks, and evidence when engaged. It brings structured support to help the team move forward.
Actively involved
The CoE proactively engages, brings evidence and support, and works alongside the team to ensure the right steps are taken and documented.
Initiate
Validating customer evidenceActively involved
Confirming lifecycle ownershipGuides
Checking for portfolio duplicationActively involved
Identifying products needing CoE guidanceMonitors
Develop
Revisiting the business caseActively involved
Aligning Enabler and Magnifier dependenciesGuides
Customer research or validationMonitors
Launch
Assessing launch readinessActively involved
Ensuring ownership continuityGuides
Defining customer and commercial success measuresActively involved
Ongoing Management
Maintaining performance visibilityGuides
Triggering lifecycle stage reviewsActively involved
Monitoring Enabler healthActively involved
Prioritised roadmap deliveryMonitors
Iterate / Retire
Initiating retirement conversationsActively involved
Structuring iterate or retire decisionsGuides
Active involvement is collaborative. When the CoE is actively involved, it works to make sure the right steps have been taken, evidence gathered, and justifications documented. This is about working alongside teams, not approving their work.
Visibility is foundational. Lifecycle stage and performance need to be understood for each product. Where issues emerge with Enablers, the CoE raises them to help responsible business units find solutions. The focus is business improvement.
Roll-out matters. Communication about what the CoE does will be critical. Changing behaviour takes time and needs to be approached deliberately.
08 · Operating Rhythm

The pilot cadence for the CoE.

The following activities form the CoE's initial operating rhythm, prioritised by the workshop participants for the pilot phase.

Weekly
CoE team sync
Internal alignment on priorities, workload, and blockers across CoE members.
Monthly
SteerCo briefing
Structured update to the steering committee on portfolio health and CoE impact. Quarterly deep dive.
Monthly
Sponsor briefing
Keeping the executive sponsor informed on CoE activity, progress, and risks.
As needed
Playbook refinement
Updating lifecycle templates and guidance based on lived experience.
Quarterly
Leadership sessions
Engagement with leadership teams on product capability and CoE progress.
Quarterly
Portfolio review
Big-picture strategic assessment of product health and lifecycle maturity. One domain per quarter.
Lifecycle review: yearly, providing a structured assessment of product performance against lifecycle criteria.
Domain coaching sessions: at a cadence determined at a point in time, providing 1:1 or small group capability uplift with domain teams.
One report, customised per forum. The CoE generates a single portfolio view and adapts it for different audiences as needed.
How we'll know it's working
09 · Success Markers

The Success Markers for the CoE.

The following summarises what would be seen if the CoE is successful.

Posture

Ownership is clear.

Ambiguity about who owns products and Enablers in target domains has measurably reduced. Named lifecycle owners exist where they did not before.

Practice

Shared language is in everyday use.

Lifecycle terminology and the Product / Enabler / Magnifier model are used consistently in governance forums, reviews, and everyday conversations.

Practice

Teams seek the CoE out.

Domain teams proactively request CoE help, facilitation, and input into product decisions rather than the CoE having to insert itself.

Proof

Risks surface and get acted on.

Cross-domain risks and dependencies are identified through CoE activity, business stakeholders are acting on them, and the CoE is consulted early in product-related decisions.

Proof

CoE tools and artefacts are in use.

CoE tools and artefacts have been designed, developed, launched and are in use across the business.

Practice

Accountabilities are reconciled.

Ownership in forums and decision-making is clearer with artefacts being used to reconcile accountabilities.

Practice

Product Playbook is guiding decisions.

The Product Playbook is being used to guide development and management decisions across the business.

Long-term

Customer domain performance has increased.

There is overall increased evidence of customer domain performance. Understanding of customers has deepened and product performance across Ampol Group has improved.

10 · Endorsement

Signatories.

This charter is endorsed by the following signatories, confirming the mandate, scope, and authority of the Product Centre of Excellence.

Executive Sponsor
[ Name ]
Signature 
Date 
CoE Lead
[ Name ]
Signature 
Date