Effort, and how far to trust an estimate
What the effort estimate accounts for, and how much weight to put on it.
Last updated September 22, 2026
Impact alone is misleading. Something that would lift your score meaningfully is worth little if it takes eighteen months and three new hires. Pytheus pairs every suggestion with an effort estimate so you can weigh the two together.
What effort accounts for
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 a function you already have or standing one up from nothing. Moving a single capability one level is light. Building a missing function across a whole domain is not.
How far to trust it
An estimate is a starting point for a conversation, not a quote. It is derived from your assessment, so it is only as good as the assessment behind it: a capability with a clear current maturity, a defined target and a set criticality produces a far more useful estimate than one assessed in a hurry or left partly blank.
If a suggestion looks wrong, it usually means the underlying assessment needs another pass rather than that the suggestion is broken. Check the capability behind it first.
Effort and impact together tell you what is worth doing next. Neither decides for you.