Define the business change
A capability describes what the business needs to be able to do. A project describes a temporary effort to change something. Beginning with capabilities helps a portfolio team compare investments that affect the same business outcome even when they belong to different departments. Choose an explicit scope, a business owner, and a measurable outcome before creating a large capability hierarchy.
Assess with evidence
Define the criteria for a capability assessment before assigning a score. Separate process consistency, people and ownership, technology support, data quality, and controls. Record evidence and uncertainty for each dimension. A missing assessment should remain unknown; it should not silently become a low score. Review findings with the people who operate the capability and distinguish current maturity from the target the initiative is intended to achieve.
Map applications and data dependencies
For each material gap, identify the applications and data products supporting the work. Capture accountable owners and dependencies that might affect several initiatives. A finance improvement may depend on supplier master data managed by another team. That dependency should influence sequencing and acceptance criteria rather than appearing late as a project issue. Start with the relationships necessary to make the decision; a complete enterprise inventory is not a prerequisite.
Describe current, transition, and target states
A useful roadmap explains what changes at each stage, why it matters, who owns it, and what evidence allows the next stage to begin. In an illustrative finance rollout, the current state might have inconsistent supplier records. A transition state establishes stewardship and validation before a controlled regional rollout. The target state describes the adopted operating arrangement, not simply the software go-live date.
Bring the model into delivery
Link the initiative and its deliverables to the capability context. Revisit the map when scope or a shared dependency changes. Judge the model by whether it improves prioritization and exposes constraints, rather than by the number of nodes it contains. Neurofolio connects capability, application, data, and initiative context; an assessment engagement can help establish the evidence and roadmap around that context.