Turning recommendations into roadmap items
Accepted recommendations become sequenced, projected roadmap work.
Last updated June 1, 2026
A recommendation describes a gap worth closing. A roadmap item is your commitment to close it on a timeline. Forest connects the two so your plan stays anchored to real capability data.
Once you accept a recommendation, you can promote it into the roadmap. The capability, the maturity delta, the criticality, and the expected impact carry over, so the roadmap item already knows what it is meant to achieve and how much it moves your scores when complete.
Sequencing follows priority. Because priority is (target maturity − current maturity) × criticality, the items that close the widest gaps on the most important capabilities naturally sort to the front. You can override that order when business context demands, but the default keeps you focused on what matters most.
FIS projects the result deterministically. As you schedule items, it recalculates how your domain scores and Forest Score evolve at each milestone using the same formulas applied to your current state. The projection is traceable to the maturity changes you have planned, not an estimate.
A roadmap built this way is defensible. Every milestone ties to a capability, a priority number, and a projected score, so progress reviews stay grounded in evidence.
The strength of all of this rests on one design choice. See why recommendations are capability-driven.