Executive Reporting Skill
Creating effective executive communications that drive decisions and action.
Purpose
This skill provides a framework for:
-
Executive status summaries
-
Portfolio dashboards
-
Board packages
-
Escalation reports
-
Decision support materials
Executive Communication Principles
The Executive Pyramid
Level Content Time
Summary Key message in one sentence 10 seconds
Overview 3-5 key points 1 minute
Detail Supporting data and analysis 5 minutes
Appendix Full data for reference As needed
What Executives Want
They Want They Don't Want
Clear status (RAG) Ambiguous status
Actionable insights Information dumps
Decisions required Problems without options
Trends and patterns Raw data
Risks and mitigations Surprises
Confidence in team Excuses
Report Types
Type 1: Portfolio Status Dashboard
Audience: Executive team Frequency: Weekly/Monthly Length: 1-2 pages
Sections:
-
Portfolio health summary (RAG)
-
Key metrics (SPI, CPI, utilization)
-
Exceptions requiring attention
-
Upcoming milestones
-
Decisions needed
Type 2: Project Escalation Report
Audience: Sponsor/Executive Frequency: As needed Length: 1 page
Sections:
-
Issue summary (one sentence)
-
Impact assessment
-
Options with trade-offs
-
Recommendation
-
Decision requested
Type 3: Board Package
Audience: Board of Directors Frequency: Quarterly Length: 5-10 pages
Sections:
-
Executive summary
-
Portfolio performance
-
Strategic initiative status
-
Key risks and mitigations
-
Resource and financial summary
-
Decisions and approvals needed
-
Appendix (detailed data)
Type 4: Stakeholder Update
Audience: Key stakeholders Frequency: Weekly/Bi-weekly Length: 1 page
Sections:
-
Status summary
-
Accomplishments this period
-
Planned next period
-
Blockers/needs from stakeholders
-
Key dates
Executive Reporting Gates
Gate 1: Audience Analysis
Objective: Understand what the audience needs
Actions:
-
Identify primary audience
-
Understand their priorities
-
Determine decision authority
-
Assess communication preferences
Audience Questions:
-
What decisions can they make?
-
What do they worry about?
-
How much time do they have?
-
What format do they prefer?
Output: docs/pmo/{date}/audience-analysis.md
Gate 2: Data Gathering
Objective: Collect accurate, current data
Actions:
-
Gather project status data
-
Collect metrics (SPI, CPI, etc.)
-
Update risk information
-
Verify with project managers
Data Verification:
-
Cross-check with multiple sources
-
Validate with PM before publishing
-
Note any data gaps or assumptions
-
Date-stamp all data
Output: docs/pmo/{date}/report-data.md
Gate 3: Insight Development
Objective: Extract actionable insights from data
Actions:
-
Identify patterns and trends
-
Determine root causes
-
Develop recommendations
-
Prepare decision options
Insight Framework:
-
What? - State the fact
-
So What? - Explain why it matters
-
Now What? - Recommend action
Output: docs/pmo/{date}/report-insights.md
Gate 4: Report Creation
Objective: Create the executive report
Actions:
-
Apply appropriate template
-
Lead with conclusions
-
Support with evidence
-
Include clear call to action
Quality Checklist:
-
Summary captures key message
-
RAG status is clear and justified
-
Decisions needed are explicit
-
Recommendations are actionable
-
Data is current and verified
Output: docs/pmo/{date}/executive-report.md
Gate 5: Review and Delivery
Objective: Ensure quality and deliver effectively
Actions:
-
Internal review for accuracy
-
Get PM sign-off on project status
-
Prepare for questions
-
Deliver and follow up
Pre-Delivery Checklist:
-
Spelling and formatting checked
-
Numbers verified
-
PM approved their project status
-
Talking points prepared
-
Follow-up actions noted
Output: Final report delivered
Anti-Rationalization Table
See shared-patterns/anti-rationalization.md for universal anti-rationalizations.
Executive Reporting-Specific Anti-Rationalizations
Rationalization Why It's WRONG Required Action
"Bad news can wait" Delayed bad news = worse news. Executives need truth. Report immediately with context
"Too much detail for executives" Under-reporting creates blind spots. Provide right level of detail
"Green because no complaints" Silence ≠ health. Verify with data. Evidence-based status only
"They'll ask if they want to know" Proactive communication builds trust. Anticipate needs, don't wait
"Keep it positive" False positivity destroys credibility. Report reality with solutions
Pressure Resistance
See shared-patterns/pressure-resistance.md for universal pressure scenarios.
Executive Reporting-Specific Pressures
Pressure Type Request Agent Response
"Make the status green" "Status must reflect reality. I'll provide accurate status with context and recovery plan."
"Don't mention that risk" "Executives expect full picture. Including with mitigation status."
"Simplify it, they won't understand" "Executives understand complexity. Will provide clear summary with detail available."
"We need this in 30 minutes" "Quality over speed for executive comms. Will provide accurate summary in timeframe, full detail to follow."
Blocker Criteria - STOP and Report
ALWAYS pause and report blocker for:
Situation Required Action
Data integrity questionable STOP. Cannot report unreliable data. Verify before reporting.
PM disputes project status STOP. Resolve disagreement before publishing.
Asked to misrepresent status STOP. Cannot compromise integrity. Escalate if pressured.
Critical escalation discovered STOP. Immediate verbal communication before written report.
Cannot Be Overridden
The following requirements are NON-NEGOTIABLE:
Requirement Cannot Override Because
Accurate status reporting False status destroys credibility with executives
Complete risk disclosure Hidden risks become board-level surprises
Data verification Unverified data misleads executive decisions
Clear decision requests Vague asks don't get executive decisions
Balanced presentation Spin erodes trust and credibility
If user insists on violating these:
-
Escalate to orchestrator
-
Do NOT publish inaccurate report
-
Document the request and your refusal
Severity Calibration
When determining what to escalate in executive reports:
Severity Criteria Executive Action Required
CRITICAL Business viability impacted, material risk Immediate attention, decision this meeting
HIGH Significant objective impact, recovery needed Decision needed this week, intervention may be required
MEDIUM Notable but manageable deviation Awareness, monitor, may need decision next cycle
LOW Minor variance within tolerance FYI only, included for completeness
Escalate CRITICAL and HIGH. Report MEDIUM for awareness. Include LOW for transparency.
Output Format
Executive Status Report
Portfolio Status Report - [Date]
Executive Summary
[One paragraph: Overall status, key achievements, primary concerns, decisions needed]
Portfolio Health: [GREEN/YELLOW/RED]
| Metric | Value | Trend | Status |
|---|---|---|---|
| Projects On Track | X/Y (Z%) | Up/Down/Stable | G/Y/R |
| Budget Utilization | X% | Up/Down/Stable | G/Y/R |
| Resource Utilization | X% | Up/Down/Stable | G/Y/R |
| Open Critical Risks | N | Up/Down/Stable | G/Y/R |
Project Status Summary
| Project | Status | SPI | CPI | Key Issue |
|---|---|---|---|---|
| [Name] | G/Y/R | X.XX | X.XX | [Issue or "On track"] |
Items Requiring Attention
Critical (Action This Week)
- [Item] - Decision Needed: [Decision]
Important (Action This Month)
- [Item] - Owner: [Name]
Key Milestones (Next 30 Days)
| Date | Project | Milestone | Status |
|---|---|---|---|
| [Date] | [Project] | [Milestone] | [On Track/At Risk] |
Decisions Requested
| Decision | Options | Recommendation | Deadline |
|---|---|---|---|
| [Decision] | [A, B, C] | [Recommendation] | [Date] |
Appendix
[Detailed project status, full risk register, etc.]
Execution Report
Base metrics per shared-patterns/execution-report.md:
Metric Value
Analysis Date YYYY-MM-DD
Scope [Portfolio/Report type]
Duration Xh Ym
Result COMPLETE/PARTIAL/BLOCKED
Executive Reporting-Specific Details
Metric Value
projects_reported N
status_distribution G/Y/R
escalations N
decisions_needed N
When Executive Report Is Not Needed
Condition Verification
No active portfolio projects Verify no projects in tracking
Routine status unchanged No new risks, milestones, or blockers since last report
Stakeholders explicitly waived Written confirmation required
Recent report covers same period Reference recent report that applies
MUST: Full executive report REQUIRED for the following conditions:
Condition Why Required
Any project status change Stakeholders need current information
New risks identified Risk visibility is NON-NEGOTIABLE for executives
Milestone reached or missed Progress tracking required for governance
Resource or budget conflicts Decision-making requires current data
Board or sponsor meeting Cannot attend unprepared
MUST: When in doubt, produce the report. Incomplete executive reporting causes misaligned decisions and erodes trust.