The thing a chairman would want before every board meeting.
Not another deck. A chairman's operating system that separates what is reported, what is inferred, and what management must answer next so the board can spend its time on decision quality instead of packet archaeology.
Chairman agenda
One screen that tells the chairman what matters
Three board questions that turn slides into governance.
The original deck was already strong. This makes it operational. Every lane below changes with the board perspective toggle so the discussion can move between the question a chairman should ask and the exact packet management should bring back.
What should the chairman ask next?
This is the reusable core: a board-ready ranking engine that can flex by lens. Margin mode surfaces pricing and booked revenue. Moat mode surfaces experience and defensibility. Growth mode reweights for demand creation and channel architecture.
Ranking controls
Adjust the weight of urgency, unknowns, and cross-enterprise impact. The selected lens sets a smart default, but it can be overridden in seconds.
Top questions
The live board queue, ranked against the current lens and weighting mix.
Show the math, then move the levers.
The board does not need a perfect model to have a sharper conversation. It needs a visible frontier, transparent assumptions, and a way to test whether pricing, distribution, or designed experience is the highest-value move.
Fleet levers
These sliders are intentionally transparent. They are not pretending to be diligence. They are a board conversation device that turns abstract levers into visible trade-offs.
Memory engine
The deck already makes the right point: satisfaction is not the same as rebooking. This makes the difference tangible. Drag the voyage arc. Watch the economics move.
What is reported, inferred, and still unknown.
This is what makes the experience feel credible rather than salesy. Every board discussion needs the same evidence architecture: reported facts, inference labels, and explicit unknowns that management must answer.
Board facts already in hand
What the board can responsibly infer
The unknowns management must surface
The board flow a chairman could use every time.
This is the part that turns a cool one-off briefing into something he would actually keep. It tells the board how to spend 90 minutes, what management owes in the next packet, and what commitment should leave the room.
90-minute chairman ritual
What makes this feel chairman-ready
It starts with booked-revenue quality, channel economics, and capital allocation logic - not brand adjectives.
Every section asks the same governance question: what decision is the board trying to improve, and what evidence would change that decision?
It does not reduce guest experience to NPS. It shows how memory design, rebooking, referral, and system dependence connect.
Sources and modeling notes
This prototype was built from the supplied briefing deck, the research memo, the HX prototype bundle, and the supplied HX / H&K evidence-base artifacts.
- HX chairman appointment, dedicated CEO, and annual report references come from the provided source list embedded in the briefing and research memo.
- The frontier numbers, fleet revenue estimate, and simulator assumptions are adapted from the provided HX HTML prototypes and kept explicitly labeled as public-data estimates.
- The guest portfolio, commercial discipline, and experience design language traces back to the supplied deck and the named academic sources cited there.