This example is fictional — an invented organization in a situation the sector will recognize. The skills it names are real library skills; the people and the organization are not.
Who: The ED of a mid-size youth-services organization — 30 staff, a stretched finance manager, and a board that keeps asking for "more of a dashboard."
Skills: CEO-board partnership for the report and the relationship; Executive dashboard for the numbers underneath it.
Each example shows one or two skills at three depths: beginner (one draft), intermediate (a repeatable rhythm), and advanced (a connected workflow). Human review remains part of every level.
Beginner — one solid board report
Turn the month's bullet points into a report the board can act on — conclusions first, exceptions highlighted, no surprises buried on page four.
- Install the CEO-board-partnership skill and prepare your raw notes: numbers, wins, misses, decisions needed. Before uploading, remove identifiable client details and confidential personnel material that the tool or intended audience is not authorized to receive.
- Ask for a board report draft with the "decisions needed" section on page one.
- Edit for candor and your own voice; add anything you would feel wrong surprising the board with.
- Have each metric owner verify the figures and reporting period; confirm decision authority and confidential material with the ED or chair. Then send the approved report with the packet several days ahead, not the night before.
Worked example: a decision the board can make
What you bring: Fictional raw notes: 24 young people on the transport-related waitlist; a 12-week shuttle pilot estimated at $18,000; finance has identified $18,000 of unrestricted funds available for this purpose; recurring funding is not secured. In this scenario, board approval is required.
What you ask:
Use the CEO-board-partnership skill to turn these notes into a decision request. State the recommendation, evidence, spending limit, uncertainty, and follow-up. Do not imply that the pilot has already been approved.
What comes back, excerpt:
Decision requested: Authorize up to $18,000 in unrestricted funds for a 12-week shuttle pilot.
Recommendation and evidence: Approve a time-limited test addressing the transport barrier affecting 24 young people on our waitlist. Finance has identified funds for the pilot, not an ongoing commitment.
Uncertainty and follow-up: A shuttle may not resolve every enrollment barrier. The program director will report participation, actual cost, and remaining barriers at the next quarterly meeting before recommending continuation.
What the human changes: The ED verifies that transport is the documented barrier, not an assumption, and that this decision actually belongs to the board under local delegation rules.
Ready-to-use check: Finance confirms available funds and the estimate; the program owner confirms the count and date; the packet contains no identifiable client information or personnel details outside its authorized audience.
Intermediate — a standing monthly rhythm
Build the dashboard once, then let the rhythm carry it: data updates, narrative on top, one review with the chair before every meeting.
- Use the executive-dashboard skill to pick 8–15 cross-functional KPIs with targets and thresholds.
- Set a monthly data-pull day and an owner for each metric.
- Each cycle, update the dashboard, then run the beginner workflow on top of it.
- Send the same scorecard to the board quarterly — same measures, no churn.
- Spend 30 minutes on trend reading instead of formatting.
Advanced — the full partnership system
Extend the rhythm to the governance work around it: executive sessions, the chair relationship, and the annual evaluation.
- Add exec-session prep to the monthly cycle.
- Add a standing chair 1:1 agenda the week before each meeting.
- Keep a running decisions log and open-questions list the board can see.
- Once a year, use the skill to draft your own self-evaluation against agreed criteria.
- Use the evaluation to reset targets and dashboard thresholds with the chair.
- Propose one generative discussion topic per meeting — strategy the board should chew on.