Most Power Platform CoEs do not stall because of a lack of effort or investment. They stall because of how they were set up. This article covers the four patterns that cause it and the specific changes that reverse them.
At some point, most Power Platform CoEs hit a slowdown they did not plan for.
It usually happens after the initial push. The platform is live. Teams are interested. A few early use cases have landed.
Then things get harder.
Requests start building up. Governance conversations take over. Delivery slows. Some teams stop engaging altogether and find their own way forward.
Six months in, the CoE exists. But it is no longer driving momentum.
If you have seen that pattern before, you are not alone. We see it regularly in organisations that have invested in Power Platform but are struggling to turn early adoption into something that scales.
The issue is rarely the platform. It is how the CoE has been set up around it.
Where Most Power Platform CoEs Lose Traction
These issues are consistent. They tend to show up regardless of industry or organisational size.
Governance Introduced Before Value Is Established
Most organisations start by putting a governance framework in place. Environment strategy, access controls, approval flows, documentation.
It feels like the right place to begin.
In practice, it often creates friction before value is properly established.
At that stage, there is limited visibility of how Power Platform will actually be used. Governance is based on assumption rather than real behaviour.
What tends to happen is predictable. Business users exploring Power Platform for the first time hit process straight away. Some disengage. Others carry on without involving the CoE.
Either way, influence is lost early.
Microsoft’s own adoption guidance reflects this directly: governance needs to evolve alongside adoption, not get ahead of it.
A CoE Without a Clear Mandate
Without visible executive backing, a CoE spends most of its time negotiating.
Standards exist, but they are not consistently followed. Engagement becomes optional across business units.
In most cases, the issue is not just mandate. It is how that mandate is framed.
A CoE positioned around control is harder to sustain. One linked to outcomes like productivity, cost reduction, or speed to delivery gets considerably more support.
Without that alignment, adoption fragments. Teams move at different speeds, take different approaches, and visibility starts to drop.
Positioned as a Control Function
When a CoE becomes associated with approvals and restrictions, engagement falls away quickly.
This matters more with Power Platform than most platforms. Accessibility is part of the value. If that gets constrained too early, teams will find other ways to deliver.
We see this play out in predictable ways. Work gets duplicated. Standards drift. IT loses clarity on what is being built and where.
At that point, governance becomes reactive rather than preventative.
Measuring Activity Rather Than Impact
Many CoEs track what they manage rather than what they enable.
Apps reviewed. Policies applied. Environments created.
Those metrics show movement, but not value.
From a leadership perspective, the question is simple. What has improved?
If that answer is not clear, it becomes harder to justify continued investment. Over time, the CoE loses attention and priority.
The difference between a CoE that stalls and one that scales is not effort. It is how the model was built and whether it is willing to change.
What High-Performing Power Platform CoEs Do Differently
Start With Just Enough Structure
High-performing CoEs do not remove governance. They sequence it.
They begin with a small number of non-negotiables. Security, access, and a few standards that genuinely matter.
Then they let real usage shape what comes next.
This is where organisations tend to unlock progress. Instead of designing for hypothetical risk, they respond to actual behaviour — where demand is building, where patterns are emerging, where controls are really needed.
Governance becomes easier to follow because it reflects reality.
Enable Delivery Where the Work Happens
Strong CoEs do not try to centralise everything.
They support people in the business who are already using Power Platform to improve processes. These are often the individuals closest to the problems that matter.
The CoE provides structure around that. Shared approaches, reusable components, and support when complexity increases.
This model scales because it aligns with how work actually gets done. Forrester’s research on digital transformation consistently finds that organisations enabling distributed innovation scale faster than those that keep delivery centralised.
Make Value Visible
Successful CoEs are deliberate about showing impact.
Time saved in finance. Reduced manual processing in operations. Faster turnaround in customer workflows.
These are captured and shared regularly.
Once that happens, momentum builds. It becomes easier to justify investment. More teams want to get involved. Conversations shift away from risk alone.
In practice, this is often the point where the CoE starts to regain influence.
Design the CoE to Flex
Demand for Power Platform changes over time.
Some areas adopt quickly. Others lag. At different points, the organisation needs different levels of support.
A fixed CoE model struggles to keep up with that.
The ones that work are built to flex. They adjust how they engage based on demand. Sometimes hands-on. Sometimes stepping back and enabling self-service.
That flexibility is what keeps the CoE relevant as the platform grows.
Extend the CoE’s Remit to Copilot
For many organisations in 2026, the Power Platform CoE now carries a responsibility it did not have twelve months ago: governing the deployment and use of Microsoft Copilot.
Copilot sits on top of the same Power Platform infrastructure the CoE manages, and its risks are closely related. Data governance, sensitivity labels, access controls, and usage policies all need to be in place before Copilot is rolled out broadly. Organisations that have been building out their CoE capability are well-positioned to lead on this. Those that have not may find Copilot governance defaults to whoever deploys it first.
The CoEs that get ahead of this now are the ones that will be seen as genuinely strategic by leadership, rather than a necessary overhead.
The Power Platform CoE Your Organisation Will Actually Engage With
Most organisations do not lack a Power Platform Centre of Excellence framework.
They have one. It just is not being used in the way it was intended.
Shifting from control-first to outcome-led sounds straightforward. In reality, it means rethinking how governance is applied, where capability sits, and how value is surfaced. The longer a CoE is bypassed, the harder it is to reposition- which is why it is worth addressing the signs of stall early rather than waiting for a reset conversation.
At Flyte, we work with IT leaders to reshape Power Platform CoEs so they reflect how the organisation actually operates. In many cases, that means simplifying what is already there, reconnecting it to real delivery, and identifying where Copilot governance needs to be built in before deployment decisions are made.
If your CoE is in place but not driving the impact you expected, speak to a Flyte consultant today.