Recommendation types

Recommendations are not one undifferentiated pile. Forest groups them by what they address, so you can read the list and understand the kind of action each one calls for.

The common categories are:

• Maturity improvement. Raise a capability from its current score toward its target. These come straight from CAMP priority and are usually the largest share of your list.

• Coverage gaps. A capability that is in scope but has little or no tooling or process behind it. The recommendation is to establish the function, not just refine it.

• Tool overlap. Two or more tools mapped to the same capability. The recommendation flags the redundancy so you can consolidate.

• Spend issues. Cost tied to a capability that does not match its criticality or maturity contribution. Contract data supports this view without driving the score itself.

Each recommendation names the capability it touches and, where relevant, the domain it sits in. A single capability can surface more than one type. A high-criticality function with a wide gap and a redundant toolset might generate both a maturity improvement and a consolidation recommendation.

Type tells you the shape of the work. A coverage gap means standing something up. An overlap means deciding what to retire.

To understand how each one is ranked, see expected impact and effort and confidence.