The situation
An enterprise of this profile is a Malaysian mobile network operator that completed a substantive merger in recent years. The merged company runs consumer mobile and home broadband at national scale, an enterprise division serving GLCs and large corporates, a 5G access and services line, and a digital products division that includes fintech, content and adjacent ventures. The Malaysian Communications and Multimedia Commission is the sector regulator. Competition policy oversight is part of the operating reality. The shareholder mix includes long term institutional shareholders that expect a credible operating story alongside delivery.
The product organisation that triggers the engagement is in a particular phase. The first wave of integration is past. Network rationalisation is in flight. The product portfolios of the two heritage companies have been combined on paper. The actual operating cadence is still uneven. Some squads still use the framework they used before the merger. Others are using the new framework but in name only. The chief product officer has decided the operating model has to be built deliberately rather than emerge by accident.
The pressure that triggers the work is the compounding of three signals. Competitive pressure from a stronger merged operator and a more aggressive challenger. A board that is asking for a clearer story on how AI changes telco economics. A senior team that is exhausted by the integration and ready to commit to an operating model if one is offered with conviction. Engagements of this archetype begin when the chief product officer and the chief operating officer commission a deliberate operating model build rather than another tactical reorganisation.
What we observed
1. Two heritage cultures are still negotiating
The merged company is not yet a single culture. Decisions get re-litigated along heritage lines. Without naming the dynamic explicitly, the operating model cannot land.
2. Product lines do not share a planning rhythm
Consumer plans on one cadence. Enterprise plans on another. 5G plans on a third. The dependencies are real and they are not yet captured in a shared rhythm.
3. AI is being treated as a digital products venture, not as the operating model
The digital products division is doing AI. The rest of the company is consuming it second hand. This produces a two speed organisation and a poorer customer experience.
4. The regulatory conversation is fragmented
Different teams talk to MCMC on different cadences. A coherent regulatory narrative is not yet emerging from the merged company.
The engagement approach
Engagements of this archetype run as a sixteen to twenty week build with founder-led discovery, sponsor-led design and senior-trainer coached implementation.
Discovery and culture naming, weeks one to three
The founder, Prashant Shinde, an HRD Corp Train-the-Trainer certified founder, runs a structured discovery with the executive committee and the senior product leaders. A deliberate session names what each heritage culture brings and what the merged company has the chance to build. The output is a one page culture statement that the cohort works to.
Design, weeks four to eight
The cohort builds the target product operating model. AI for Malaysian Telco and 5G and Product Management for Malaysian E-Wallets are taught as the references for the consumer and digital products lines. ICP-APO and ICP-APM certifications are completed by the product leadership. The AI-Native Agile Operating Model is taught as the cross-line reference.
Coached implementation, weeks nine to sixteen
The new operating model is tested against live initiatives. Cross-line dependencies are mapped. Sponsor cadence is rewritten. The chief product officer and the chief operating officer run a fortnightly senior reviewer panel together. The founder reviews monthly. The MCMC regulatory conversation is treated as part of the operating model.
Embed, weeks seventeen to twenty
The operating model is published internally. The cohort moves into a coaching cadre role for the rest of the product organisation. Agile Visa moves to a quarterly senior reviewer role.
What changed
1. Single planning rhythm across product lines
Consumer, enterprise, 5G and digital products plan on a shared rhythm. Cross-line dependencies surface earlier. The integration noise reduces.
2. AI as the operating model, not a digital products venture
The rest of the company starts to operate as an AI-Native Agile organisation. The two speed pattern fades.
3. Coherent regulatory narrative
The MCMC conversation becomes one conversation. The board is reassured. The competition policy story is easier to tell.
4. Culture as a working artefact
The culture statement is used in real decisions. The two heritage cultures stop re-litigating decisions along old lines.
Lessons that transfer to other post-merger telcos and regulated infrastructure businesses
- Name the heritage cultures explicitly. Pretending the merger is settled when it is not produces a slow operating model.
- Build the shared planning rhythm before the new structure. A structure without a rhythm becomes a re-org for nothing.
- Treat AI as the operating model. A digital products venture cannot pull the rest of the company forward.
- Treat the regulator as part of the operating model. Fragmented regulatory engagement is a board level risk.
Honest framing. This case study describes an engagement archetype representative of Agile Visa work with post-merger telecommunications and regulated infrastructure businesses. Specific companies, dollar figures and individuals are not named here for confidentiality and out of respect for the regulator and shareholder relationships involved. 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 company is exploring a similar operating model build, the founder offers a private discovery conversation.
Discuss a post-merger operating model build
A private conversation about your merged organisation, the heritage cultures inside it and what a deliberate operating model build has to look like.
Talk to the founderFrequently asked questions
How soon after a merger does this engagement usually run?
Six to eighteen months after legal close. Earlier than that and the integration noise drowns out the operating model conversation. Later than that and the two heritage operating cultures have fused into a hybrid that is harder to reshape.
Does the engagement need MCMC visibility?
The Malaysian Communications and Multimedia Commission is part of the operating reality. The engagement does not require regulatory approval, but the product operating model is shaped to respect MCMC expectations on quality of service, consumer protection and competitive conduct.
Who is in the cohort?
The chief product officer, the heads of consumer, enterprise and 5G lines, the head of network strategy, the head of operations, selected senior product managers and the embedded risk and regulatory partners.
How are the two heritage cultures handled?
Explicitly. The engagement starts by writing down what each heritage culture is good at, what each is anxious about, and what the merged company has the chance to build that neither had alone.
Is AI inside the scope?
Yes, as the operating constraint on every product line. The merged telco has too much data and too few hands. AI-Native Agile is the only operating model that scales with the merged workload.
How long is the engagement?
Sixteen to twenty weeks. The first eight weeks are intensive design. The remaining weeks are coached implementation with monthly senior reviewer cadence.