
Stop Funding Projects That Solve the Same Customer Problem Separately
The marketing team wants a clearer booking journey. Operations wants fewer booking errors. The people team wants employees to handle booking questions more confidently. Three proposals reach the budget process with different sponsors, suppliers and measures, even though they may all be responding to the same customer problem.
Approving each proposal independently can fund overlapping work while leaving the underlying decision unresolved. The website may become clearer about an offer that is still difficult to deliver. Training may help employees explain a process that another project is about to change. The organisation pays for progress in separate places without gaining a coherent result.
Organise the portfolio around the intended outcome
Before approving projects, ask which customer outcome each is meant to improve. Use a concrete description: customers understand the package, can book it accurately and receive the agreed inclusions. That makes it easier to see where projects depend on the same decisions or evidence.
This does not mean combining every related activity into an enormous programme. Different specialists may need to do distinct work. The requirement is to understand the dependencies and sequence them sensibly, so that one project does not build on assumptions another is about to overturn.
In a hypothetical spa, rewriting package descriptions should follow agreement about what the operation can reliably provide. Training should reflect the revised offer and booking rules. System changes should support those decisions. Starting all three in parallel without resolving the offer can create avoidable rework.
Make the shared decision visible
Identify the choices that no individual project can settle alone. These might concern the level of flexibility promised, the information required before arrival or the authority employees have when a booking does not fit the standard pattern.
Give those choices an owner with access to the relevant leaders. A coordination meeting without decision authority can become another place where teams report that they are waiting for someone else.
Set a shared outcome measure alongside the project-specific delivery measures. Completing a website update, a training programme and a system configuration may all be necessary, but the organisation should also know whether the customer problem improved. Otherwise each team can declare success while the reason for the investment remains.
Review duplication before adding more capacity
When the portfolio feels overloaded, examine whether the business has divided one problem into several initiatives. There may be opportunities to use the same research, align briefings or stop work that a more fundamental decision makes unnecessary.
Be careful not to remove specialist work simply because it appears similar. The point is to eliminate duplicated diagnosis and conflicting assumptions, not to pretend that communications, capability and operational design are interchangeable skills.
Ask project sponsors to explain how their work will fit the changed operating reality and who will maintain the result. A launch is a transition into everyday management. If ownership ends at delivery, the organisation may soon commission another project to repair the same issue.
The FUSION approach helps connect the investment conversation around Brand Strategy, People Development and Operational Excellence. The budget should reflect how the customer experience is created, even when the work remains distributed across specialist teams.
Illustrative photograph; pictured people and businesses are not case studies in this article. Photo source: Pexels.






Comments