What capability are we actually funding?
An investment proposal should explain what the organisation will be able to do better. That question changes how we compare projects, assign ownership, and assess results.
Before approving a project, I want to understand what the organisation will become better at doing. A proposal can describe the software, staffing, budget, and implementation schedule in considerable detail while leaving that question surprisingly difficult to answer.
My business architecture studies have given me a useful way to examine this gap: begin with the capability the investment is intended to strengthen. A business capability describes an ability the organisation needs, such as managing inventory, planning production, or resolving customer issues. It provides a point of reference that can span several teams and systems.
In a collaborative course project, we developed the case for a business architecture practice that would connect strategic priorities to capabilities and coordinated initiatives. The question I carried forward was practical: how can leaders tell whether several apparently sensible investments are improving the same business ability, duplicating effort, or leaving an essential dependency unfunded?
Follow the investment through to the work
Imagine a manufacturer considering a new production-planning tool. The proposal promises better schedules. That is a useful ambition, but a dependable schedule also relies on material availability, accurate inventory information, capacity assumptions, and a process for resolving changes.
If those conditions are weak, the tool may produce a schedule that people have to keep repairing. The purchase could still have value, but the investment case needs to explain which parts of the planning capability it will improve and which dependencies require separate attention.
This is why I would put the intended business improvement near the beginning of the proposal. For example, the organisation wants to make more reliable production commitments. The planning tool is one contribution. Data discipline, material readiness, and decisions about schedule changes may also need work. Making those relationships visible gives leaders a more complete basis for approval.
Compare projects against a shared outcome
Now imagine separate proposals from planning, purchasing, and the warehouse. Each team has a legitimate problem. Reviewing each proposal only within its departmental boundary can conceal both overlap and dependency.
A capability view gives the conversation a common reference. Leaders can ask which proposal addresses the most important constraint, whether one improvement depends on another, and who will coordinate the combined result. They can also identify useful work that should wait until a prerequisite is in place.
That does not require a complete model of the enterprise before any project can begin. For a specific decision, I would start with the relevant capability, the teams contributing to it, the current constraint, and the proposed changes. Add detail when it helps resolve a real uncertainty.
Give the capability an owner and a measure
A project manager can be accountable for delivering the agreed project. Someone in the business also needs responsibility for whether the resulting capability performs as intended. Where the outcome crosses functions, that responsibility needs explicit support from the other leaders involved.
The measure should make the business improvement observable. In the planning example, implementation milestones describe delivery progress. Measures such as schedule adherence or missed commitments attributable to material availability may help assess operational results, provided their definitions and baselines are agreed first.
I would bring five questions to an investment review: What ability must improve? Where is it currently constrained? What dependencies must change with it? Who owns the result? What evidence would justify continuing, changing, or stopping the investment?
Business architecture earns its place in that discussion by making the choices clearer. Its value should show up in the investments leaders select, the dependencies they address, and the results the organisation can sustain after the project closes.
Developed from a collaborative BA 809 Strategic Business Architecture course project on Rose Manufacturing Company. The production-planning example here is illustrative; it does not report a client engagement or measured project result.