Most organisations do not lack ideas. They lack the structure to turn those ideas into results on time, within budget and without exhausting their people. Whether the task is launching a new product line, moving to a new ERP system, opening a regional office or reorganising a supply chain, the difference between a project that delivers and one that drifts usually comes down to a small number of disciplines applied consistently.
This article sets out those disciplines in practical terms for owners, managers and project sponsors of business and operational projects.
Start with the outcome, not the activity
A project exists to create value for the business. Yet many projects begin with a list of tasks rather than a clear statement of what success looks like.
The Project Management Institute (PMI) reflects this shift in emphasis. The Eighth Edition of its PMBOK® Guide, published in late 2025, is built around a compact set of principles, including focusing on value and adopting a holistic view of the project. PMI's own research on project success likewise stresses alignment with business goals rather than delivery of outputs alone.
Before planning begins, agree on:
- The business objective – what will be different when the project is complete (for example, faster order processing or a new revenue channel).
- Measures of success – a small number of indicators that the sponsor and the team both accept.
- Constraints – budget, deadlines, regulatory requirements and resources that cannot move.
- What is out of scope – an explicit list prevents later misunderstanding.
A one-page project charter capturing these points is often more useful than a long document nobody reads.
Establish governance early
Governance answers a simple question: who decides what, and when? Without it, decisions stall, priorities change without notice and the project manager carries responsibility without authority.
Effective governance for a business project typically includes:
- A named sponsor with the authority to make decisions and release resources.
- A project manager accountable for day-to-day coordination, reporting and issue resolution.
- A decision log recording key choices, who made them and why.
- Defined escalation routes so that blocked issues reach the right person quickly.
- Stage gates or review points where the sponsor confirms the project should continue as planned, be adjusted or be stopped.
Governance should be proportionate. A three-month internal initiative does not need the same structure as a multi-year transformation, but every project needs clarity about decision rights.
Plan realistically, then plan again
A good plan is a forecast, not a promise. It should be detailed enough to coordinate work and honest enough to reveal where uncertainty lies.
Break the work down
Divide the project into deliverables and then into manageable work packages. Each package should have an owner, an estimate and a clear definition of "done".
Sequence and dependencies
Identify which tasks depend on others, which can run in parallel and which external parties (suppliers, authorities, technology vendors) sit on the critical path. Approvals and permits from external bodies are frequently underestimated; build in time for them.
Choose an approach that fits
Predictive (plan-driven) methods suit projects with stable requirements, such as an office relocation. Adaptive or agile methods suit work where requirements will evolve, such as a customer-facing digital service. Many business projects benefit from a hybrid: a fixed overall timeline with iterative delivery inside it. The current PMBOK® Guide explicitly accommodates predictive, adaptive and hybrid approaches.
Re-baseline deliberately
Plans change. When they do, record the change, its reason and its impact on cost and schedule, and obtain the sponsor's approval. Silent drift is far more damaging than a transparent re-plan.
Treat risk as a management activity
Risk management is often reduced to a spreadsheet completed at the start and never opened again. In practice, it should be a recurring conversation.
- Identify risks with the people closest to the work, not only senior management.
- Assess each risk by likelihood and impact, focusing attention on the few that matter most.
- Assign an owner and a response for each significant risk: avoid, reduce, transfer or accept.
- Review the risk register at every progress meeting and retire risks that no longer apply.
Common risks in business projects include dependency on a single key person, unclear requirements from internal users, supplier delays, data migration problems and competing priorities within the organisation.
Communicate with purpose
Stakeholders rarely complain about too much clarity. They do complain about surprises.
A simple communication plan should define who needs what information, in what format and how often. Typical elements include:
- A short weekly status update covering progress, upcoming milestones, key risks and decisions needed.
- A steering meeting at an agreed frequency for the sponsor and senior stakeholders.
- Working sessions for the delivery team, kept focused and time-boxed.
Status reporting should be honest. A "red" status raised early, with a proposed recovery plan, is a sign of good management, not failure.
Manage change and adoption
Many projects deliver their outputs on time but fail to deliver value because people do not adopt the new system or process. Change management is part of the project, not an afterthought.
- Involve future users early in requirements and testing.
- Provide training timed close to go-live.
- Identify internal champions who can support colleagues.
- Plan for a period of stabilisation after launch, with clear support routes.
Track the right measures
Measure progress against the plan, but also against the original business objective. Useful indicators include:
- Milestones achieved versus planned.
- Budget spent versus earned progress.
- Open risks and issues, and their ageing.
- Early indicators of benefit, such as adoption rates or process cycle times.
Close properly and learn
At closure, confirm that deliverables have been accepted, contracts and accounts are settled, documentation is archived and responsibility has been handed over to operational owners. Then hold a brief, blame-free review: what worked, what did not, and what should change next time. Organisations that capture these lessons steadily improve their delivery capability.
A practical checklist
Before your next project begins, ask:
- Do we have a written, agreed statement of the business objective and success measures?
- Is there a named sponsor with real decision-making authority?
- Has the work been broken down with owners and estimates?
- Have we identified external dependencies, including approvals and suppliers?
- Is there a living risk register reviewed at every progress meeting?
- Do stakeholders know when and how they will receive updates?
- Have we planned for user adoption, not just delivery?
Discuss your project with SOMAK
SOMAK Global Solutions provides project management services for business and operational initiatives, from structuring a new project to supporting governance, planning and reporting during delivery. If you are preparing a project and would like to discuss your requirements, our team would be pleased to hear from you.
