A sample weekly executive brief
This is what a weekly brief looks like, built from made-up programs and numbers. Executives receive it by email with a PDF, or in Slack or Google Chat. Every statement points to the records it rests on; here those references are shown in brackets.
By the Tarivra team · · 4 min read
This week in one line
2 of 6 programs report a better status than the work supports: Payments Modernization and Mobile App 3.0. 1 decision is overdue.
Needs your attention
- Payments Modernization: reported Green, the work supports Red. At 4 items a week, the 46 open items finish around March 2, 2027, 11 weeks after the December 15 target. [Jira PAY-120 and 46 child issues]
- Mobile App 3.0: reported Green, the work supports Amber. Scope grew 24% since the October 1 baseline (19 items added) with the date unchanged. [Azure DevOps Epic 4410]
- Data Center Migration: 2 of the last 5 changes failed and 1 caused an incident; status is Amber and matches the evidence. [ServiceNow CHG0031207, CHG0031244, INC0098812]
- Decision overdue: 'Add two engineers from the Cards team to Payments until go-live', owner Priya Shah, due November 13. [Decision 14, Jira PAY-131]
Program by program
Payments Modernization (Jira)
Reported Green; evidence Red; integrity score 22 of 100.
- How to check:
- Finish rate fell from 7 to 4 items a week; 9 of 31 in-progress items untouched for 14 days; 6 items blocked.
- Red flag:
- Forecast misses the December 15 target by about 11 weeks.
Mobile App 3.0 (Azure DevOps)
Reported Green; evidence Amber; integrity score 58 of 100.
- How to check:
- Scope up 24% since baseline; finish rate steady at 5 items a week.
- Red flag:
- Forecast reaches the January 29 target only if no more scope is added.
Customer Portal Redesign (GitLab)
Reported Green; evidence Green; integrity score 94 of 100.
- How to check:
- Finish rate steady; 2 items blocked; no scope growth this month.
- Red flag:
- None. On track for February 12.
Decisions
- Done this week: 'Move fraud rules to phase 2' (Payments), closed when PAY-133 was completed.
- Open: 'Re-plan the go-live date with the card processor', owner Dana Lee, due November 27.
- Overdue: 'Add two engineers from the Cards team to Payments', owner Priya Shah, due November 13.
About this sample
The programs, people and numbers here are made up to show the format. A real brief is written each week by Tarivra's built-in writer from the work in your teams' tools, sends no program data to an outside AI provider, and leaves out any sentence the evidence does not support.
Questions
How is the brief delivered?
By email with a PDF, or to a Slack or Google Chat channel, to the people you choose. Each person can also read it in Tarivra.
Who writes the brief?
Tarivra's built-in writer, from the work in your tools. Every statement cites its records, and a sentence the evidence does not support is withheld.
Can each executive get a different brief?
Each person sees only the programs their access allows, so restricted programs appear only in the briefs of people listed on them.