Results Over Processes Plans: Why Outcomes Win

Strong project management favours results over processes plans, because outcomes create the real value a business pays for. Processes still matter. Plans still matter. Yet the question this article asks is simple. Should outcomes outweigh the processes and plans that surround them? The answer shapes how teams spend their time, and it shapes whether a project ultimately succeeds.

What Are Processes

Processes transform inputs into outputs through the application of tools and techniques (PMI). Each process forms part of a project phase. Teams therefore repeat a process as often as needed, since it runs until the completion criteria for that phase are met (PMBOK). Processes give a project order. They also give a team a shared rhythm.

The processes are divided into groups, including:

- Initiating Process Group: defines a new project or a new phase within an existing project - Planning Process Group: establishes the scope of the project, refines the objectives and defines the course of action that is required to attain the objectives of the project - Executing Process Group: completes the worth defined in the project management plan to satisfy the project requirements - Monitoring & Controlling Process Group: tracks, reviews and regulates the progress and performance of the project; identifies any areas of change required in the plan; and initiates the corresponding changes - Closing Process Group: formally completes or closes a project, phase or contract

According to The Digital Project Manager, proper processes are vital for efficiency, because they let teams know exactly who is doing what, when and how. Clear roles, anticipated risks and steady alignment with strategy all flow from this clarity. Disorder, by contrast, breeds trouble. Hard-to-follow processes can therefore lead to project failure, weakened trust in business relationships and wasted resources.

What Are Plans

Planning is an essential part of project management, since it can reduce uncertainty, oversights and rework (PMBOK). Teams develop a plan for each aspect of a project. Many teams also devise an overarching project management plan (PMBOK). A solid plan matters for another reason too, because it stops teams from setting overly ambitious budgets and delivery timelines (The Digital Project Manager).

There are a number of different plans. Teams present some as written documents, while others appear as visual or virtual whiteboards. A few examples of plans include:

- Communications management plan: a description of how, when and by whom information regarding the project will be administered - Cost management plan: a description of the costs involved and how they will be planned, structured and controlled - Risk management plan: a description of how risk management activities will be structured and performed

What Does A Plan Look Like

A full-length plan can run long. Here is an example of what one may look like, drawn from a risk management plan for a council planned event. A simplified communications management plan, meanwhile, may look far lighter than that.

Although planning is vital, it only helps up to a point. Too much time spent on plans can therefore cause a loss of efficiency. Consequences of prolonged planning may include less return on investment and increased loss of market share (PMBOK).

The Significance Of Outcomes

Outcomes differ from outputs, because outcomes create benefits and value for the business. For example, in an IT project the outcome may be an improved user interface, which then leads to greater consumer satisfaction. A project exists to achieve an outcome. Teams should therefore define that outcome early and reassess its progress throughout the work. So the real question follows naturally. What balance should outcomes strike against processes and plans?

Research has found a clear pattern (Musawir et al., 2017). Reviewing and realigning project outcomes has a strong positive effect on a project's success. The effect holds when "actual project outcomes adhered to the target outcomes planned in the business case" (Musawir et al., 2017). Such findings support a clear idea. Projects should widen their focus onto outcomes, instead of pouring too much time and resource into planning and processes alone.

In a report published by PMI (2016), only half of organisations said project benefits were well aligned with business strategic goals. Many professionals, including chief information officers, project managers and stakeholders, therefore lack focus on defining a project's outcomes. Attention drifts onto project outputs instead of business outcomes. The same PMI report shows the cost of that drift, since poor project performance wastes a large share of every sum invested. Such waste illustrates the immense scale of weak project management and missed benefits realisation.

Choosing Results Over Processes Plans

So the planning and processes within a project clearly help a team reach efficiency and success. Still, every team should question how far that truth really stretches. Should project teams focus more on outcomes, rather than investing more time than needed on plans and processes? Heavy financial losses are the last thing an organisation wants. The evidence above shows this can happen when outcome focus slips. Sean Whitaker, an internationally recognised project management consultant, puts it plainly. "Focusing on outcomes will result in a greater chance of project success, happier clients and an improved reputation".

The lesson is practical. Choosing results over processes plans does not mean abandoning either one. Instead, build sound processes, write a solid plan, then point both relentlessly at the outcome. Project managers who learn this balance tend to learn it through structured training, such as a globally recognised credential. Our PMP certification course teaches that outcome-first mindset alongside the process discipline of the PMBOK Guide. Build the skill, and you build better results.