Board reports

A board does not need your full capability inventory. It needs a defensible picture of where the program stands, where it is going, and what that costs. Pytheus gives you the inputs to build that picture without manual spreadsheet work, and the Brief assembles them for you from the same model the export uses.

Start with the headline. Your Pytheus Score, on a 0 to 100 scale, is the single number a board can anchor on. Because it combines Org Score, goal alignment, coverage, and execution discipline, you can explain not just the number but what moves it.

What to include

• The Pytheus Score and its trend. One number, plus direction since the last review.

• Domain scores. Twelve domains let you show strength and weakness without drowning the room in detail.

• Top priorities. The highest-priority capabilities, ranked by (target maturity minus current maturity) times criticality. This is where requested budget goes.

• Peer comparison. How your performance compares to an anonymized peer cohort for your sector and size. Frame a peer delta as a performance difference, not a deficiency.

Every number traces to its inputs. If a director asks why a domain scored low, you can point to the specific capabilities and maturity levels behind it. Pytheus is deterministic, so the same assessment always produces the same result.

Keep the deck short and let the detail live in Pytheus. See Explaining scores to leadership for language that lands with a non-technical audience, and Exporting summaries to pull the figures out.