Strategic Planning in Development Projects

Picture a rural water program that closes all fourteen of its projects on time and within budget. Three years later the ex-post evaluation finds a third of the wells out of service and household income unchanged. Every project was delivered. The program failed.

That gap is why development work needs a different management discipline from commercial delivery. A finished deliverable is not a result, and a program that measures only deliverables discovers the difference years after it could have done anything about it.

Results-based management judges a development intervention by the socio-economic or environmental change it produces, not by whether its projects came in within scope, time and cost.

What results-based management actually asks of you

It is not a methodology to adopt wholesale. It is a small set of obligations that all have to hold at once:

• Strategic planning that links goals to programs, so every project on the list can name the objective it serves.
• Alignment of programs with targets, so intermediate results become visible while there is still time to correct course.
• Risk management proportionate to environments where access to resources, technology and counterparts can change without warning.
• Assessment and follow-up of results, including evaluation after the project closes, not only at handover.

Drop any one of them and the program quietly reverts to delivery management wearing a development vocabulary.

Strategic planning is what makes project selection defensible

Strategic planning orders the cause and effect relationships between the goals to be achieved and the programs meant to achieve them. In practice it means answering two questions for every candidate project: which objective does this advance, and by how much compared with the alternatives.

Answering them properly needs a framework consistent enough to compare unlike projects and flexible enough to survive a change in conditions. Funding entities rarely commit to a single future. A drought year, a currency movement or a change of counterpart government produces a different budget envelope and a different set of viable projects, so the analysis has to hold across several scenarios rather than one.

This is where the tooling earns its place. In ITM Platform, a program’s strategic alignment runs the exercise in three phases: goals are prioritized first, usually by the steering body, then each component project is scored for its contribution to those goals, deliberately by a different group so the selection stays unbiased, and only then is the portfolio chosen. Optimistic, realistic and pessimistic scenarios each hold their own prioritization and their own selection, so the pessimistic list exists before the budget is cut rather than being improvised afterwards. Where goals are hard to weigh directly, pairwise comparison scores them with the Analytic Hierarchy Process and reports a consistency ratio; anything above 0.1 flags the judgments as potentially inconsistent and worth revisiting before they harden into a portfolio.

Two graphs then do work that argument alone cannot. The efficient frontier shows which combinations deliver the most value for a given budget. The comparison of selected components against the original goal weighting shows whether the portfolio you picked actually reflects the priorities you agreed: if the top-ranked goal carries 40% of the strategic weight and 8% of the selected budget, that is visible before the money moves.

The prioritization mechanics deserve a closer look on their own, and they are covered in strategic alignment and selecting the most valuable project portfolio.

Long horizons need intermediate results you can actually see

Development projects aim at changes that do not show up at handover. Behavior change, institutional capacity and environmental recovery play out over years, which is why ex-post evaluation exists at all, and why the program rather than the project is the unit that has to be managed.

A long horizon is not a license for a long silence. Successful management produces intermediate results that accumulate into the sustainable outcome, and each of those has to be observable while the program is still running.

Grouping projects and services as components of a program gives that structure somewhere to live. Program management in ITM Platform pulls goals straight from the organization’s strategic plans, so the program’s objectives are the institutional ones rather than a restatement of them. Budget is held in both directions, top down for the program and aggregated from its components, which is what lets you discuss the cost of the outcome instead of the cost of the wells. The Progress section tracks the status of every component alongside Special Events, the milestones important enough to surface in portfolio progress. A project belongs to one program at a time, which reads like a restriction and behaves like a discipline: it forces a decision about which result a given project is accountable for.

The triple constraint still applies, and still moves as one piece

Development projects are bound by scope, time and cost exactly as any other project is. What matters is the measures taken to keep them in balance, because none of the three moves alone.

Constraint	What moves it in development work	What it drags with it
Scope	An extra community added mid-program, a counterpart requesting new activities	Cost rises, the schedule extends, or both
Time	A delayed disbursement, a rainy season, an election	Cost rises through idle teams, or scope is cut to hold the date
Cost	An exchange rate move, a fuel price, a tranche withheld	Scope narrows, or delivery slows

Scope, time and cost move together. Changing one without deciding which of the other two absorbs the change is not a decision, it is a deferral.

The constraint set is not the whole test either. The goals that justify the program have to be met inside those boundaries, but the stakeholders are the ones who ultimately judge the quality of what was delivered. That calls for meticulous planning, indicators read throughout implementation rather than at closure, and priorities the parties have genuinely agreed rather than assumed.

Different stakeholders need different reports, not the same one

The distinguishing feature of development work is stakeholder diversity. The implementing organization, the promoting or financing entity and the end beneficiaries hold different needs, expectations, spheres of influence and interests, and they do not converge by being sent the same document. Add complex environments and restricted access to certain resources or technologies, and the design has to be able to absorb changing conditions without losing the expected results.

Planning therefore has to be participatory. The results to be achieved are agreed rather than announced, and the beneficiaries’ interests carry particular weight: a program that hits every planned figure on cost, time and scope while missing what the beneficiaries needed will struggle to be called a success.

Communications management is where this either works or quietly fails. The project manager stays in constant contact with the team and the other parties, and handled well, communication connects the different perspectives on the development result and reports performance in terms each audience recognizes. Handled badly it produces one monthly report that satisfies nobody. Communications management as a knowledge area covers how to plan that deliberately instead of improvising it.

The practical move is to stop trying to make one view serve everyone. Customizable dashboards build charts on any entity and take business goal as a category, so a funder’s view can be organized around objectives while the implementing team’s view is organized around tasks and cost. Each dashboard carries a single global filter, and the guidance is explicit that an audience needing different filtering should get its own dashboard rather than a compromise. Permissions are granted per user and per role, as editor or as viewer, so the financing entity’s contact can be given a viewer seat on the board built for them without acquiring rights over anyone else’s.

None of this substitutes for judgment about what a community actually needs. What it removes is the excuse for finding out three years too late. “The projects were delivered” answers a question nobody asked. The discipline is being able to show, while the program is still running, which results are accumulating and which are not.

Next steps

• Start a free ITM Platform trial and set up your program with its business goals and component projects.
• See how programs and portfolio management keeps objectives, budgets and component progress in one place.
• Before you commit to a portfolio, review how strategic alignment scores projects against prioritized business goals.