Skip to main content
Engagement archetype, Malaysian oil and gas

Building a Digital Coaching Cadre Across the Petronas Vendor Ecosystem

A representative engagement pattern from the Malaysian oil and gas ecosystem. A group of tier one and tier two vendors and partners serving the national oil company builds a shared coaching cadre, anchored on ICAgile certifications and the AI-Native Agile Operating Model.

Sector, Oil and gas ecosystem Cohort, 3 to 8 vendors Format, cross-vendor Duration, 9 to 12 months

The situation

An enterprise of this profile is a group of tier one and tier two vendors and partners operating around the Petronas value chain. Upstream services, subsurface engineering, drilling and well services, facilities engineering, integrated operations support, refining and petrochemical maintenance, and the growing digital and field operations support sector. The vendors are independent commercial entities. They compete in some segments and collaborate in others. They share, however, a common operating reality. The national oil company has set the digital direction. The vendors are expected to deliver against that direction without slowing the production cadence.

The cadre being built draws from delivery managers, engineering leads, digital transformation managers and senior operations supervisors from each participating vendor. The cadre is typically thirty to sixty people across three to eight vendors. The intent is not to train one vendor better than the others. The intent is to lift the ecosystem so that the principal operator sees a more consistent partner bench across the value chain.

The business pressure that triggers the work is the compounding of three signals. A principal operator that has formally set an AI agenda. Cost discipline that is pushing every tier one and tier two vendor to do more with the same headcount. A workforce realisation that the engineering supervisors of today will be retiring inside the planning horizon, and that the next generation needs to be coached, not just hired. Engagements of this archetype begin when one or two anchor vendors decide to commission a cross-vendor cadre rather than continue with isolated training spend.

What we observed

1. Coaching language differs across vendors

Each vendor has its own framing of Agile, transformation and AI. The same word means different things. Without a shared vocabulary, the ecosystem cannot move together.

2. Field operations is the missing seat

Discussions about AI tend to happen in head office. Field operations is treated as the user, not as the participant. The coaching has to bring field supervisors into the cadre or the work does not land.

3. Compliance and contract teams are a constraint that is not coached

The vendor compliance and contract management teams are the gate to deploying AI tools across the value chain. They are rarely in the coaching room. Inviting them changes the conversation.

4. The principal operator is watching

The principal operator is watching how the ecosystem matures. Vendors that move together are easier to partner with. This is a commercial signal as well as a capability signal.

The engagement approach

Engagements of this archetype run as a cross-vendor cadre build over nine to twelve months. The shape below is representative.

Anchor design, month zero

The founder, Prashant Shinde, an HRD Corp Train-the-Trainer certified founder, runs an anchor session with the sponsoring vendors. Output is a shared coaching maturity ladder, a shared vocabulary glossary and a sponsor map naming the cadre champion at each vendor.

Foundation, months one to three

The cadre takes ICP-ACC Agile Coaching, the ICP-ACC for Petronas and Malaysian Oil and Gas contextual module, and the AI Productivity Foundations module. Sessions are delivered in person in Kuala Lumpur and rotated through vendor offices when commercially comfortable.

Supervised practice, months four to nine

Each cadre member runs a live coaching assignment inside their own vendor. The senior Agile Visa coach reviews a sample. The founder runs a monthly cross-vendor review where one cadre member from each vendor presents a coaching engagement. This is the forum where the ecosystem starts to move together.

Embed and extension, months ten to twelve

The cadre extends into ICP-ENT Enterprise Agile Coaching for the senior members who will coach at the vendor leadership level. The cross-vendor community of practice is formalised with rotating chairs. Agile Visa moves to a quarterly senior reviewer role.

What changed

1. Shared coaching vocabulary across the ecosystem

Vendors meeting in joint workshops with the principal operator describe their work in compatible language. Misunderstandings reduce. Conversations get sharper.

2. Internal coaching coverage at each vendor

Each vendor has internal coaches who can hold a team through an AI-Native Agile delivery without paying for outside coaching every time. The economics of capability improve.

3. Field operations engagement with AI

Field operations supervisors are now part of the AI conversation. The proposals coming out of the cadre are more grounded in operational reality.

4. Talent retention

Vendor delivery managers and engineering leads who were considering leaving stay, because the cadre is a visible investment in their development.

Lessons that transfer to other Malaysian oil and gas vendor ecosystems

  • Anchor on a shared coaching maturity ladder. Without it, the ecosystem cannot move together.
  • Bring field operations into the cadre. Head office only cadres fail to land.
  • Bring compliance and contract teams in for the AI sessions. They are the gate.
  • Let the principal operator see the cadre. A cross-vendor cadre is a commercial story as well as a capability one.

Honest framing. This case study describes an engagement archetype representative of Agile Visa work with the Petronas vendor ecosystem and analogous oil and gas vendor groupings. Specific vendors, dollar figures and individuals are not named here for confidentiality. Agile Visa is an ICAgile Member Organization with a learner record of 75,000+ professionals across 140+ countries and Cohorts since 2017. The founder Prashant Shinde is an HRD Corp Train-the-Trainer certified founder. If your vendor group is exploring a similar cadre build, the founder offers a private discovery conversation.

Discuss a vendor ecosystem cadre build

A private conversation about which vendors should anchor the cadre, how the principal operator sees the work, and what the cadence needs to look like.

Talk to the founder

Frequently asked questions

Is Petronas the only national oil company this archetype applies to?

The archetype is shaped by the Petronas vendor ecosystem because that is the most mature integrated oil and gas operating environment in the region. The same shape applies to vendor ecosystems serving Pertamina, PTT and the Middle East national oil companies.

Does the engagement require coordination with the principal operator?

Where the engagement is sponsored by the principal operator, coordination is built in. Where the engagement is sponsored by a tier one vendor independently, the vendor coordinates with the operator on its own terms.

Is the engagement HRD Corp claimable?

Where the participating vendor is registered under Pembangunan Sumber Manusia Berhad and the engagement scope aligns with HRD Corp claim policy, the vendor applies for SBL Khas claims through its own HRD Corp account.

How many vendors typically participate?

Three to eight tier one and tier two vendors is typical.

What is the focus, classical Agile or AI?

AI-Native Agile. The ecosystem is past the point where classical Agile alone is the relevant offer.

How long is a cadre build?

Nine to twelve months. The first three months are an intensive coaching foundation. The remaining months are supervised practice.