One-Page Boss Report

Problem

Many executive reports fail because the first page has no decision. Lengthy materials list activities, but they hide whether targets were met, where the risk is, and what the manager must approve. The result is an archived email, a delayed decision, and information that does not support action.

How It Works

This skill compresses input into a three-part structure:
- Conclusion: state the current judgment in one or two sentences, not the process.
- Evidence: keep one core number, with a comparison baseline and the anomaly.
- Recommendation: list options and the exact decision the manager should make.

It supports project progress, incident reporting, decision request, and business review. It checks whether the output can be read in about 30 seconds, whether the decision point is clear, and whether numbers have comparison context. When data is weak, it avoids beautification and instead explains cause and remediation.

Boundaries

It is best for internal upward reporting, not technical documentation, client proposals, or investor pitches. If detailed materials are required, keep the one-page report as the body and move details to an appendix. It does not write marketing copy or make business judgments; it only shapes available information into a decision-ready format.