Why true stewardship means making commitments only as fast as reality becomes clear
The Comfort of the Binder
A project team sits before a community oversight board. Between them rests a sixty-page plan covering the next three years. It contains budgets, milestones, specifications, and completion dates. Everyone feels safer because the future now has numbers attached to it.
There is only one problem. Much of that future has not happened yet. The team knows this, and the board probably knows it too. Yet everyone accepts the ritual because precision feels responsible. Uncertainty feels like poor preparation.
That is where trouble begins.
The real danger is not uncertainty. Every serious project contains things nobody can know beforehand. The danger begins when organizations make commitments more certain than their evidence allows. Good stewardship requires something harder than producing confident forecasts.
It requires telling the truth about what we know. It also requires saying what we do not know. Then we explain how we intend to learn.
Precision Is Not Knowledge
A number can be precise without being reliable.
Suppose a project team estimates a future phase at exactly $2,417,650. The figure looks disciplined. But labor rates may change, regulations may shift, and technical problems may emerge. Those extra digits create precision, but they do not create knowledge.
Precision has outrun evidence.
This matters because estimates slowly become promises. Budgets become commitments, dates become expectations, and assumptions become accepted facts. Soon, the organization becomes trapped by numbers created when knowledge was weakest.
When better evidence arrives, the team faces an uncomfortable choice. It can change the plan and appear unreliable. Or it can defend the original plan against what reality is revealing.
That is how an innocent estimate becomes institutional pressure.
The Earliest Plan Knows the Least
There is a strange contradiction inside traditional planning.
We often demand the greatest detail when we know the least.
At the beginning of a complicated project, many important facts remain hidden. Local behavior has not been observed. Technical problems have not surfaced. Suppliers have not been tested. Regulations and market conditions may still change.
Yet this is often when organizations demand fixed schedules and detailed budgets.
Later, the team finally possesses better information. But changing those early commitments can now look like failure. Learning becomes inconvenient because yesterday's assumptions have acquired institutional authority.
That reverses the proper relationship between planning and reality.
A plan should express our best current understanding. It should never become more authoritative than the evidence that created it.
Navigate by the Lighthouse
A lighthouse offers a better picture of responsible planning.
It does not reveal every rock and current along an entire coastline. It provides a stable direction while sailors deal with the waters around them. The destination can remain clear even when the exact route must change.
Good planning can work the same way.
The destination should be clear. Important boundaries should also be clear. Near-term work should contain enough detail for responsible execution. The distant future needs a different kind of planning.
It needs direction, ranges, assumptions, and decision points. It also needs questions that remain honestly unanswered.
As the team moves forward, reality supplies information. Assumptions become observations. Estimates become better grounded. Decisions that were premature become possible.
The plan gains precision because knowledge has gained precision.
That is not weak planning. It is planning honestly.
Buy Knowledge Before Buying Infrastructure
This becomes especially important in complex community projects.
Imagine a food organization considering a large central distribution facility. Demographic models suggest the location should work. Transport maps support the choice. Consultants produce convincing forecasts.
But people do not live inside models.
Before spending millions, the organization could test the idea cheaply. Temporary distribution points could reveal where people actually travel. They could show when people arrive and what prevents participation. They could reveal whether the original model matches daily life.
The experiment does something valuable.
It buys knowledge before the organization buys infrastructure.
If the experiment succeeds, confidence increases. The organization can commit more resources with stronger evidence. If it fails, the financial loss remains small.
More importantly, a small failure may prevent a very expensive one.
A safe-to-fail experiment is therefore not hesitation. It is disciplined stewardship when important uncertainty remains.
Certainty Should Be Staged
This suggests a different way to talk about plans.
Not every part of a project deserves the same confidence. The first phase may be fully designed and funded. The second may have a reasonable cost range. The third may depend on information that does not exist yet.
Those are not three failures of planning.
They are three different states of knowledge.
A responsible leader can tell the board that the next phase has been fully costed. Later phases remain provisional because their costs depend on evidence still being gathered. The estimates will become firmer at agreed review points.
That answer may sound less impressive than a perfect three-year forecast.
But it is far more useful.
It tells decision makers where they can rely on the plan. It also tells them where they should remain watchful.
The System Must Permit Honesty
Individual courage is not enough.
If organizations punish every revision, people will hide uncertainty. If funders reward confident forecasts but reject honest ranges, project teams will learn to manufacture precision.
The system gets the behavior it rewards.
Boards can change those incentives. They can ask which assumptions support each estimate. They can establish review dates and define conditions requiring earlier review. They can separate approved commitments from provisional forecasts.
That changes the conversation.
A revised estimate no longer automatically means somebody failed. It may mean the organization learned something important. New information may have exposed an assumption that no longer holds.
Accountability remains, but its purpose changes.
Instead of defending yesterday's forecast, leaders explain today's evidence. Then they show how that evidence changes tomorrow's decision.
Uncertainty Is Not an Escape Hatch
None of this means leaders can avoid commitments.
Some things must remain firm. Safety requirements cannot drift whenever convenient. Legal obligations matter. Spending limits matter. Communities deserve deadlines when deadlines can reasonably be established.
Adaptive planning is not permission to improvise forever.
Its discipline is stricter.
Commit firmly where knowledge justifies commitment. Stay provisional where reality remains genuinely uncertain. Then make the difference visible.
That is the integrity of uncertainty.
What Stewardship Really Requires
People entrust organizations with more than money.
They entrust them with time, labor, attention, confidence, and sometimes years of community effort. Those resources deserve more than impressive forecasts. They deserve truthful ones.
A good steward does not promise perfect foresight. A good steward explains what is known and what remains uncertain. Larger commitments wait until enough has been learned to justify them.
That changes planning from a performance of control into a process of learning.
The plan still matters. The budget still matters. Deadlines still matter. But none should pretend to know more than reality has revealed.
The deepest integrity in planning may begin with a sentence leaders often fear saying.
We do not know that yet. Here is how we intend to find out.
That is not the absence of a plan.
It may be the beginning of an honest one.
Credits
Developed through ONES Thinking Version 3.2, particularly its ideas on Complexity Thinking, Dynamic Governance, Systems Thinking, and stewardship. The article also draws on established project management ideas including progressive elaboration, rolling-wave planning, staged commitment, and learning through small experiments.
The examples in this essay are illustrative. They are used to explain the planning principles rather than presented as documented case studies.
Tags
#Leadership #Project_Management #Systems_Thinking #Decision_Making #Community
No comments:
Post a Comment