Effort and confidence

Impact alone is misleading. A recommendation that would lift your score ten points is worth little if it takes eighteen months and three new hires. Forest pairs every recommendation with effort and confidence so you weigh it honestly.

Effort estimates the work to close the gap: the size of the maturity jump, how many capabilities or tools are involved, and whether you are refining an existing function or standing up a new one. A move from maturity 4 to 5 on a single capability is light. Building a missing function across a domain is not.

Confidence reflects how complete the underlying inputs are. When a capability has clear maturity scores, a defined target, and a set criticality, confidence is high and the recommendation rests on solid ground. When inputs are sparse or the assessment is partial, confidence drops, and the recommendation deserves a closer look before you commit.

Low confidence is not a reason to ignore a recommendation. It is a prompt to finish the assessment that produced it.

Read the three together. High impact, low effort, high confidence is your fast lane. High impact, high effort, high confidence belongs on the roadmap. Anything with low confidence points you back to your CAMP data first.

Once you have weighed a recommendation, you can accept or reject it and move accepted items into your plan.