Many business transformation projects begin with enthusiasm.
Senior management supports the idea.
Employees attend meetings.
A provider is appointed.
A project team is formed.
Technology is purchased.
Workshops are conducted.
Updates are circulated.
But eventually, a critical question emerges:
Who actually owns the project?
The answer is sometimes unclear.
The CEO believes the operations manager is responsible.
The operations manager believes the IT team owns implementation.
The IT team believes the external provider is managing the project.
The provider is waiting for management decisions.
Employees assume someone else will decide what happens next.
The project has many participants.
But no clear owner.
This is one of the most common structural weaknesses in enterprise transformation.
A project does not become accountable simply because many people are involved.
In fact, excessive participation without clear ownership can create:
Delayed decisions.
Conflicting instructions.
Unresolved problems.
Scope confusion.
Provider dependency.
Weak employee adoption.
Poor benefits realisation.
A transformation initiative requires a clear answer to one fundamental question:
Who is accountable for ensuring that this business change succeeds?
That question becomes increasingly important as businesses prepare for EDGE.
EnterpriseSG has announced that EDGE will streamline the existing EDG, MRA and PSG schemes into a more seamless single enterprise-support framework, allowing businesses to seek support based on intended activities and business needs rather than first determining which separate scheme applies.
A more integrated grant environment does not reduce the need for internal accountability.
It increases the importance of it.
Consider a company implementing a major digital transformation project.
The company appoints:
An external consultant.
A technology provider.
An internal IT manager.
An operations manager.
Several department representatives.
A finance representative.
Senior management sponsors.
The project appears well staffed.
But then problems emerge.
A business process needs to change.
Who decides?
The provider requires additional information.
Who supplies it?
Employees resist the new workflow.
Who manages adoption?
The budget increases.
Who approves the change?
The system is implemented.
Who owns it after the provider leaves?
If these questions were not answered at the beginning, the project can become dependent on informal assumptions.
That is not governance.
That is organisational ambiguity.
A person can attend every project meeting and still not be accountable.
A provider can perform substantial work and still not own the business outcome.
A senior executive can support a project without managing daily decisions.
These roles are different.
Strong transformation governance distinguishes between:
Accountability.
Responsibility.
Authority.
Participation.
Without these distinctions, projects can become difficult to manage.
An external provider can contribute expertise.
A consultant can recommend a strategy.
A technology company can configure a system.
A specialist can conduct training.
But none of these parties should replace internal ownership of the business transformation itself.
The company must ultimately own:
The business problem.
The strategic objective.
The management decisions.
The process changes.
The employee adoption.
The long-term capability.
The expected enterprise outcomes.
This is particularly important for projects intended to build sustainable business capability rather than simply purchase an external service.
EnterpriseSG's existing enterprise-development approach has consistently focused on projects that help businesses upgrade, innovate, grow and transform, while its broader capability framework spans areas including digitalisation, productivity, talent and growth.
A business appoints a provider.
The provider begins work.
Management gradually becomes less involved.
The company assumes:
“We hired experts. They will handle it.”
But transformation usually requires internal decisions that only the business can make.
For example:
Which process should change?
Which employees should be involved?
What level of risk is acceptable?
Which customer requirements matter most?
What information is commercially sensitive?
What operating model should exist after implementation?
An external provider may advise.
But the business must decide.
The more strategically important the project, the more important internal ownership becomes.
A provider may leave after the project.
The business remains.
Therefore, the organisation must retain ownership of the capability being created.
A practical project structure can separate five important roles.
The executive sponsor provides senior-level authority.
This person should:
Support the strategic purpose of the project.
Resolve major organisational barriers.
Make significant management decisions.
Ensure the project remains aligned with business strategy.
Maintain leadership attention.
The sponsor does not necessarily manage daily project activities.
But the sponsor should have sufficient authority to intervene when necessary.
The business owner should own the business problem being addressed.
For example:
An operations transformation project may have an operations leader as business owner.
A financial management project may have a finance leader.
A customer experience initiative may have a commercial or customer leader.
The business owner should understand:
Why the project matters.
What must improve.
Which employees are affected.
What successful adoption looks like.
This role connects implementation with real business operations.
The project owner manages the transformation initiative as a coordinated programme of work.
This may involve:
Project planning.
Meeting coordination.
Timeline management.
Risk monitoring.
Dependency tracking.
Decision follow-up.
Provider coordination.
Management reporting.
The project lead ensures the project moves.
But the project lead should not automatically be expected to make every business decision.
Functional owners are responsible for specific parts of the transformation.
For example:
IT may own technical integration.
Finance may own financial controls.
HR may support workforce change.
Operations may own process redesign.
Department managers may own adoption within their teams.
This creates distributed responsibility without removing central accountability.
External providers may contribute:
Technology.
Consulting expertise.
Implementation capability.
Training.
Specialist knowledge.
Technical support.
Their responsibilities should be clearly defined.
But the provider should not become the informal decision-maker for the business.
The EDGE direction is intended to support business activities across areas such as digitalisation, enterprise efficiency and internationalisation through a more streamlined approach. EnterpriseSG has stated that businesses will no longer need to determine which of the previous EDG, MRA or PSG schemes their activity falls under before seeking support.
This means businesses should increasingly focus on defining:
What transformation is required.
Why it matters.
Who owns it.
What capability will be developed.
What outcome is expected.
Project ownership is therefore not an administrative issue.
It is part of the business case.
These terms are often confused.
Project management focuses on coordinating execution.
Typical responsibilities include:
Timelines.
Tasks.
Meetings.
Risks.
Milestones.
Documentation.
Project ownership focuses on accountability for the business transformation.
Typical responsibilities include:
Business decisions.
Strategic alignment.
Outcome ownership.
Resource commitment.
Employee adoption.
Long-term capability.
A project manager can keep a project moving.
But the project owner must ensure the business is moving in the right direction.
A project can be:
On schedule.
Within budget.
Technically complete.
Well documented.
And still fail to solve the business problem.
Why?
Because project management tracked activity.
But nobody remained accountable for the business outcome.
This is why ownership must extend beyond implementation.
The executive sponsor should usually be a person with sufficient authority to influence:
Resources.
Priorities.
Business decisions.
Cross-functional cooperation.
The sponsor does not always need to be the CEO.
But the person should have genuine organisational influence.
For a major transformation, the sponsor should be able to answer:
Why are we doing this?
Why now?
What business value do we expect?
What trade-offs are acceptable?
What happens if departments disagree?
Sometimes a senior person is named as sponsor for appearance.
But the individual:
Rarely attends discussions.
Cannot make decisions.
Does not understand the business problem.
Has limited influence over affected teams.
The project then lacks leadership when difficult decisions arise.
A sponsor should be more than a name on an organisation chart.
The strongest project owner is usually close to the business problem.
For example:
If a company wants to improve warehouse productivity, ownership should not automatically sit with the IT department simply because technology is involved.
The operational leader may better understand:
Current bottlenecks.
Employee workflows.
Customer requirements.
Process constraints.
Operational consequences.
Technology may be an important part of the solution.
But the business problem may still belong to operations.
Many companies classify projects based on the technology being implemented.
But the better question is:
Which business capability is changing?
A CRM project may really be a sales-management transformation.
An AI project may really be a customer-service transformation.
An ERP project may really be an operating-model transformation.
An automation project may really be a productivity transformation.
Technology should support the business owner.
It should not automatically replace business ownership.
Businesses sometimes say:
“Everyone owns the project.”
This sounds collaborative.
But it can create a problem.
If everyone owns everything, who makes the final decision?
Shared participation is valuable.
Shared accountability can become ambiguous.
A stronger structure may involve:
One accountable owner.
Several responsible contributors.
Clear decision rights.
Defined escalation routes.
This allows collaboration without confusion.
A business can define major decisions using four questions.
Who has final ownership?
Who performs the work?
Who provides specialist input?
Who needs to know what was decided?
This creates a practical discipline around decision-making.
The objective is not to create bureaucracy.
The objective is to prevent decisions from disappearing between departments.
A transformation project should identify which decisions belong to whom.
Examples include:
Usually owned by senior management or the executive sponsor.
Usually owned by the relevant business function.
Usually owned jointly by technical specialists and relevant business owners.
Usually require defined management authority.
Should follow a formal decision process.
May be delegated to the project lead.
Without defined decision rights, small issues can become management bottlenecks.
Senior leaders should make strategic decisions.
They should not need to approve every operational detail.
If every decision requires executive approval:
Projects slow down.
Employees become passive.
Management becomes overloaded.
Accountability weakens.
A strong governance structure delegates decisions appropriately.
Clear ownership becomes especially important when the project scope changes.
Suppose an employee requests:
“One additional workflow.”
A provider recommends:
“A more advanced module.”
Management asks:
“Can we include another department?”
These changes may be reasonable.
But someone must decide whether they:
Improve the business outcome.
Create additional cost.
Delay implementation.
Introduce new risks.
Require additional resources.
A project owner should ensure that changes are assessed against the original transformation objective.
This is closely connected to strong project scoping.
Without ownership, a project can gradually become a collection of unrelated requests.
The original business problem becomes less visible.
The project becomes larger.
The budget increases.
The expected outcome becomes harder to measure.
A strong owner continually asks:
Does this decision still support the transformation we intended to achieve?
External providers should have clearly defined responsibilities.
Businesses should understand:
What the provider will deliver.
What information the provider requires.
Which decisions remain with management.
Who approves deliverables.
Who validates quality.
Who manages changes.
Who owns the capability after completion.
This prevents provider relationships from becoming overly dependent.
A dangerous situation occurs when:
Only the consultant understands the strategy.
Only the technology provider understands the system.
Only the implementation specialist understands the process.
Only the external project manager understands the project history.
The provider may eventually leave.
The business must remain capable of operating and improving the new capability.
Knowledge transfer should therefore be considered part of the transformation.
A project owner should not assume that implementation automatically creates adoption.
Employees may need:
Clear communication.
Training.
Process guidance.
Management support.
Time to adapt.
An owner should understand which behaviours need to change.
For example:
A new reporting platform does not improve management performance if managers continue using spreadsheets.
An automated workflow does not improve productivity if employees continue performing the old manual process.
An AI tool does not create value if employees do not understand when and how to use it.
Ownership must therefore continue beyond go-live.
EDGE Change Management: Why Employee Adoption Will Determine Whether Transformation Actually Works
This is one of the most important questions.
A provider may deliver the project.
But who owns the benefit?
Suppose the intended outcome was:
Reduce reporting time.
Who monitors whether reporting time actually improved?
Suppose the objective was:
Increase employee productivity.
Who measures whether capacity improved?
Suppose the project was intended to support overseas growth.
Who evaluates whether the business developed stronger market capability?
The business owner should normally remain accountable for benefits realisation.
A transformation project has a formal implementation period.
Business ownership should continue afterwards.
The business must ask:
Are employees using the capability?
Are the expected outcomes appearing?
What problems remain?
What should be improved?
What capability should be developed next?
The project may end.
Transformation does not necessarily end.
The person requesting a project should not always be the only person involved in budget decisions.
However, there should be clarity around:
Who owns the business case.
Who approves expenditure.
Who monitors costs.
Who approves changes.
Who confirms value.
A budget without accountability can create weak discipline.
The business should understand not only:
“How much will the project cost?”
But also:
“Who is accountable for ensuring that this investment creates value?”
EDGE Project Budgeting: How Singapore Businesses Should Build a Credible Transformation Budget
Many transformation projects cross departmental boundaries.
For example:
A customer-data project may involve:
Sales.
Marketing.
Customer service.
IT.
Finance.
Operations.
No single department can complete the transformation alone.
But this does not mean accountability should disappear.
A strong model may involve:
One executive sponsor.
One accountable business owner.
One project lead.
Multiple functional owners.
Defined provider responsibilities.
This creates coordination without creating confusion.
A company may give a project to whichever department appears least busy.
But capacity and ownership are different.
The right owner should understand:
The strategic objective.
The business problem.
The operating environment.
The intended outcome.
An available employee may manage the project.
But they may not be the right person to own the business transformation.
Businesses often have multiple potential EDGE initiatives.
The challenge is deciding:
Which project matters most?
Which one should happen first?
Which project has the right internal owner?
Which initiative lacks sufficient management attention?
A project without a credible owner may not be ready to begin.
That should influence prioritisation.
If management cannot identify a credible project owner, it should ask why.
Possible reasons include:
The business problem is not sufficiently understood.
The project crosses too many functions.
Management is not aligned.
The initiative is still too vague.
The company lacks internal capability.
The project may need further preparation.
The absence of an owner can reveal a deeper readiness problem.
The strongest project owner usually has several characteristics.
They understand the problem being addressed.
They can make or escalate relevant decisions.
They have sufficient time and management attention.
Affected employees recognise their role.
They focus on business value rather than simply completing tasks.
They will remain connected to the capability after implementation.
The owner does not need to know every technical detail.
They need to own the business transformation.
Usually, no.
The CEO may sponsor major enterprise transformation.
But individual projects may require different accountable owners.
The CEO should avoid becoming the operational bottleneck for every initiative.
However, leadership should remain sufficiently involved to ensure:
Strategic alignment.
Resource discipline.
Cross-functional cooperation.
Enterprise priorities.
A transformation portfolio requires leadership oversight even when individual projects have different owners.
Smaller businesses may not have dedicated transformation offices or project managers.
The structure can therefore be simpler.
For example:
Executive sponsor and strategic decision-maker.
Business owner.
Coordinates implementation.
Provides specialist expertise.
The key principle remains the same.
Every major responsibility should have an identifiable owner.
A small company does not need a large project office.
It does need clarity.
Employees should know:
Who decides.
Who coordinates.
Who provides input.
Who approves.
Who owns the outcome.
Simple governance is often more effective than complicated governance that nobody follows.
Before implementation begins, businesses can document a short ownership charter.
It may include:
What transformation is being undertaken?
Who provides senior leadership?
Who owns the business outcome?
Who coordinates implementation?
Which departments own specific responsibilities?
What will external parties deliver?
Who approves major decisions?
What happens when a major issue cannot be resolved?
Who remains accountable for benefits after implementation?
This document does not need to be complicated.
Its purpose is to prevent ambiguity.
As businesses prepare EDGE-related initiatives, strong ownership can improve the quality of internal project planning.
Management should be able to explain:
Why the business needs the project.
Who owns the problem.
Who will participate.
How the business will manage implementation.
How the capability will be used.
What outcome is expected.
EnterpriseSG has stated that EDGE is intended to support businesses through a streamlined approach to transformation, operational efficiency and growth-related activities, with existing EDG, MRA and PSG schemes remaining accessible until EDGE is launched.
A business with unclear ownership may struggle to demonstrate internal readiness even before implementation begins.
Some companies wait until a project is approved before deciding who will manage it.
This can be risky.
Ownership should be considered during planning.
Before committing to a project, management should know:
Who will lead the business change?
Who has authority?
Who will provide information?
Who will make decisions?
Who will monitor outcomes?
A project should not become “someone’s problem” after approval.
Before beginning a transformation initiative, ask:
If these questions cannot be answered, the project structure may not yet be ready.
Strong project ownership is not simply about assigning names to an organisation chart.
It reflects organisational maturity.
A mature business understands:
Who owns strategic decisions.
Who owns business problems.
Who manages execution.
Who provides specialist expertise.
Who remains accountable after implementation.
This distinction becomes increasingly important as businesses undertake more complex transformation initiatives involving:
Digitalisation.
AI.
Automation.
Capability development.
Internationalisation.
Process redesign.
Multiple providers.
Cross-functional change.
The strongest EDGE projects will not simply have good technology or well-written plans.
They will have clear internal ownership.
Because transformation does not succeed when responsibility is everywhere.
It succeeds when accountability is clear.
If your business is planning an EDGE transformation initiative and needs to clarify project ownership, accountability, management responsibilities or provider roles, speak with us before implementation begins.
We help Singapore businesses structure transformation projects around clear ownership, governance, decision rights, internal responsibilities and measurable enterprise outcomes.
WhatsApp us
```