26. Board Brief — The brief builder (light, executive maroon)

Audience: operations analysts and team leads reporting to a board · Artifacts: brief.html (2D builder) · 3d.html + brief.js (3D boardroom) · shared data brief-data.js · Case study: index.html

In one line: build a one-page board brief from twelve data cards, then watch the board's fifteen minutes: which cards carried the claim, which raised questions, and whether a decision was taken.

Why this kit exists

Board items fail in two ways: the numbers dump (everything reported, nothing asked) and the confident claim (a cause the page itself contradicts, or a cost kept out of view). Both survive because analysts rarely see what happens to their page in the room. The builder makes that visible and repeatable.

What the artifact does

Twelve cards with neutral notes. Up to five go on the page. A three-part claim (what is happening · because · so we ask the board to), a trade-off line and a written opening sentence. Then a fixed, illustrative read model turns each element into minutes and questions, and gives one of seven outcomes. The debrief scores the brief /14 (pass: approved in the meeting and ≥ 12), explains each claim part and each card, and the learner revises and runs again.

The design decisions worth noticing

• No feedback until the read. The minutes are the feedback; the debrief explains them.
• Missing evidence is not neutral. A wrong cause is only challenged if the card that contradicts it is on the page; otherwise the board approves the wrong fix.
• The cost decides the ending. A visible cost is approved; win-win is approved with doubt; an appendix cost is approved and then reopened.
• One data file for both builds so the 2D and 3D versions cannot drift.

Honest limitations

Certum Opleidingen, its board and every number are fictional. The read model is a teaching device with fixed minute costs; it does not predict a real board. Real packs carry legal and financial constraints this builder leaves out. Not piloted.

Part of I Wayan Usada's learning-design portfolio · all clients and scenarios are fictional composites built from realistic domain patterns · drafted with AI assistance and fully rewritten, fact-checked and owned by a human.

Process deliverables

• action-map.md — Action map — the behaviors the artifact must produce, traced to the business goal
• storyboard.md — Text-based storyboard — the scene plan, revised to match the build
• visual-mockups.md — Visual mockups & style guide — mood, type, key screens, component decisions