Skill Hub — Productivity and Execution Control

Daily Execution Review Working Skill

Run a 10-minute structured daily review that tracks what was done, surfaces what is blocked, and resets priorities so the team starts each day with clarity and alignment.

What this skill is for

Most teams lose half a day to context switching, status hunting, and priority confusion. The Daily Execution Review is a disciplined 10-minute habit that replaces chaos with a single shared record. The output is a Daily Execution Review Record: a brief document that states what was completed yesterday, what is in progress today, what is blocked, what changed overnight, and what the top priority is for the next day. The record is not a status report for management; it is a planning tool for the team. It ensures that everyone knows what matters today, that blockers are surfaced before they become crises, and that yesterday's decisions are not forgotten by tomorrow.

When to use this skill

At the start of each workday, before the team begins execution.
After a weekend or holiday when context has been lost.
When a new critical issue has arrived overnight and the day's plan must be adjusted.
When a team member is returning from absence and needs to catch up quickly.
When a distributed team needs asynchronous alignment across time zones.
When an AI agent is reviewing a project's status and needs a structured daily summary to base decisions on.

Real work situations

AMS support team: Monday morning chaos

An AMS support team starts Monday with 15 new tickets, three weekend alerts, and a pending system maintenance window. Without a daily review, each analyst picks their own starting point. Two analysts start on the same ticket. One analyst spends an hour on a low-priority issue while a credit block goes unaddressed. The team lead discovers the duplication at 11:00. With a Daily Execution Review, the team spends 10 minutes at 08:30: review the weekend alerts, identify the credit block as today's top priority, assign tickets to analysts, and flag the maintenance window as a capacity constraint. The team is aligned by 08:40 and executes with purpose.

Project team: mid-sprint drift

A project team is two weeks into a four-week sprint. The sprint plan is outdated because three new requirements arrived and two tasks took longer than estimated. Without a daily review, the team continues working on the original plan, completing tasks that are no longer on the critical path while the real deadline approaches unnoticed. With a daily review, the team notices the drift on day 8, adjusts the plan, cuts two low-priority stories, and reassigns capacity to the critical path. The sprint delivers its committed scope.

Remote consultant: solo work with multiple clients

A consultant works remotely for three clients. On Tuesday morning, they have pending work from all three. Without a daily review, they switch between tasks based on which email is most recent, making no progress on any single client. With a daily review, the consultant spends 10 minutes reviewing yesterday's record, confirming that client A's critical fix is today's top priority, blocking out four hours for it, and scheduling client B's work for tomorrow. The record is shared with each client so they know when to expect updates. The consultant's work is transparent and predictable.

Inputs required

Yesterday's Daily Execution Review Record (if available).
Current task or ticket queue with status updates from the previous day.
Calendar of meetings, deadlines, and system maintenance windows for today.
New items that arrived overnight: tickets, emails, alerts, or messages.
Blocker status: any escalations awaiting resolution.
Team capacity: who is available, who is on leave, who has reduced capacity.
Priority Triage Result or sprint plan that defines what should be worked on today.
Notes from any stakeholder communications that affect today's plan (optional).

Questions to ask

What did I complete yesterday that I can mark as done?
What did I start yesterday but not finish, and what is the next step?
What is blocking me today that I need help with?
What arrived overnight that changes my priorities?
What is the single most important thing I must finish today?
What meeting or commitment consumes my capacity today?
What did I learn yesterday that changes how I approach today's work?
What am I at risk of forgetting if I do not write it down?

Working method

Review yesterday's record. Read the previous day's record. Check what was planned, what was completed, and what was deferred. This is the starting point for today's review.
Record completed work. List every task or ticket that was completed since the last review. Include the task ID and a one-sentence outcome. This builds a visible track record of progress.
Record in-progress work. List every task that is currently being worked on. Include the task ID, the next step, and the estimated time to completion. This shows what is active and where the team is invested.
Surface blockers. List every task that is blocked, with the blocker description, the escalation status, and the expected resolution time. If a blocker has no escalation, create one now using the Blocker Escalation skill.
Record new arrivals. List every new task, ticket, or request that arrived since the last review. For each, decide whether it displaces existing work, is added to the queue, or is declined. Use the Priority Triage skill if the queue is full.
Record plan changes. List any decision, discovery, or communication that changes today's plan. Example: "Vendor API delayed by 2 days. WP-005 shifts to next week. WP-006 moves up."
Define today's top priority. State the single most important task or outcome for today. This is the task that, if completed, makes the day a success even if everything else fails.
Confirm today's plan. List the tasks that will be worked on today, in order, with owners and time estimates. Include a buffer for unexpected work. The plan should fit within available capacity.
Write the Daily Execution Review Record. Use the template below. Keep it to one page. The record is for the team, not for management reporting.
Share the record. Publish the record in a shared channel, document, or tool where the team can see it. For distributed teams, the record replaces the stand-up meeting. For co-located teams, the record is the input to a 5-minute stand-up.
Review the record at the end of the day. Spend 2 minutes updating the record with what actually happened. This becomes the input for tomorrow's review.

Decision rules

If a new arrival has higher priority than an in-progress task, stop the in-progress task and start the new one. Do not try to do both unless capacity allows.
If a blocker has been open for more than one day without escalation, escalate it now.
If yesterday's top priority was not completed, it is today's top priority unless a new critical arrival displaces it.
If the plan exceeds available capacity, remove the lowest-priority task from today's plan, not the lowest-effort task.
If the team has more than three blockers, the review is a blocker resolution session, not a planning session. Focus on removing blockers before planning new work.
If the record is longer than one page, it is too detailed. Move details to the task or ticket and keep the record at the summary level.
If no work was completed yesterday, the record must explain why, not hide it.

Deliverables

Daily Execution Review Record — One-page summary of completed work, in-progress work, blockers, new arrivals, plan changes, today's top priority, and today's plan. See template below.
Blocker Update — If any blockers are surfaced, an escalation note or status update is produced.
Priority Adjustment Log — Record of any tasks that were re-prioritized, deferred, or declined due to new arrivals.

Templates

Daily Execution Review Record (compact)

---
artifact: Daily Execution Review Record
date: YYYY-MM-DD
reviewer: <name>
status: draft | confirmed | closed
---

## Completed yesterday
- <Task ID>: <One-sentence outcome>
- <Task ID>: <One-sentence outcome>

## In progress
- <Task ID>: <Next step> — ETA <time>
- <Task ID>: <Next step> — ETA <time>

## Blockers
- <Task ID>: <Blocker description> — Escalation: <ID or status> — Expected: <time>
- <Task ID>: <Blocker description> — Escalation: <ID or status> — Expected: <time>

## New arrivals
- <Task ID>: <Description> — Decision: <accept / defer / decline>
- <Task ID>: <Description> — Decision: <accept / defer / decline>

## Plan changes
- <Change description> — Impact: <what changed>

## Today's top priority
<Single task or outcome that defines success for today>

## Today's plan
| Time | Task | Owner | Notes |
|------|------|-------|-------|
| 08:30 | Daily review | team | 10 min |
| 09:00 | <Task ID> | <name> | <notes> |
| 13:00 | <Task ID> | <name> | <notes> |
| 16:00 | End-of-day update | <name> | 2 min |

## End-of-day actuals
- Completed: <list>
- Deferred: <list>
- Blockers added: <list>
- Notes for tomorrow: <list>

Quality checklist

The review is completed within 10 minutes.
Every completed task has a one-sentence outcome, not just a title.
Every in-progress task has a clear next step and an ETA.
Every blocker has an escalation status or a planned resolution action.
New arrivals are classified as accept, defer, or decline with a rationale.
Today's top priority is a single item, not a list.
Today's plan fits within available capacity, including a buffer.
The record is one page or less.
The record is shared with the team before work begins.
End-of-day actuals are recorded for use in tomorrow's review.

Common mistakes

Turning the review into a 30-minute status meeting. Consequence: the team spends more time talking about work than doing it. The review becomes a burden and is skipped. The discipline collapses.
Reporting only to management instead of planning for the team. Consequence: the record is polished to impress rather than accurate to guide. The team does not trust it and maintains a separate private plan.
Hiding blockers or missed deadlines. Consequence: blockers fester until they become crises. The team loses the habit of surfacing problems early, which is the main purpose of the review.
Listing every task in detail instead of summarizing. Consequence: the record is unreadable and the review takes too long. Details belong in the task or ticket system, not in the daily record.
Not updating the record at end of day. Consequence: the next day's review starts with outdated information. The team must reconstruct what happened, wasting time and introducing error.

Weak output vs Strong output

Weak output

A long chat thread on Monday morning where each team member says what they did last week and what they plan to do this week. No written record, no priorities, no blocker tracking. Some people join late and miss the context. Others multitask during the call. By Tuesday, no one remembers what was decided. The team reverts to email-based coordination.

Why it fails: The review is ephemeral and unaccountable. There is no artifact to refer to, no shared agreement on what matters today, and no mechanism to track blockers. The time is spent on storytelling rather than planning. The team is no more aligned after the review than before it.

Strong output

---
artifact: Daily Execution Review Record
date: 2026-06-12
reviewer: Maria Chen
status: confirmed
---

## Completed yesterday
- CTB-2026-044: Updated payment terms for C-10001 to ZB15. Confirmed by AR team.
- WP-101: Credit management setup complete. Test customer C-10001 blocked at 50k EUR.

## In progress
- WP-102: Incompletion procedure mapping — next step: assign procedure ZO2C-01 in VA01 — ETA 4 hours
- BEN-2026-089: Transport authorization resolution — next step: basis team confirmation — ETA 2 hours

## Blockers
- WP-102: Blocked by BEN-2026-089 (missing S_TRANSPRT). Escalation: BEN-2026-089 open. Expected: 2026-06-13.

## New arrivals
- INC-2026-512: Report ZREPORT timeout in company code 200. Decision: accept — displaces WP-103 for today due to month-end impact.
- REQ-2026-089: Update API contract documentation. Decision: defer — no consumer deadline, triaged to next sprint.

## Plan changes
- Vendor API spec v2.1 delayed by 2 days. WP-005 shifts to 2026-06-16. WP-006 moves up to 2026-06-13.

## Today's top priority
Resolve BEN-2026-089 so WP-102 can proceed and test execution stays on schedule.

## Today's plan
| Time | Task | Owner | Notes |
|------|------|-------|-------|
| 08:30 | Daily review | team | 10 min |
| 09:00 | Follow up BEN-2026-089 | Dmitri | Contact basis lead if no response by 10:00 |
| 10:00 | INC-2026-512 diagnosis | Maria | Check SM50 and ST22 for timeout pattern |
| 14:00 | WP-102 (if unblocked) | Dmitri | Assign incompletion procedure and test |
| 16:00 | End-of-day update | Maria | 2 min |

## End-of-day actuals
- Completed: —
- Deferred: —
- Blockers added: —
- Notes for tomorrow: —

Agent instructions

AI Prompt Pattern

Role: Daily execution reviewer for a project or support team.

Context: You have yesterday's review record, the current task queue, new arrivals, and blocker status. You need to produce a Daily Execution Review Record that the team can use to plan today's work.

Task: Summarize completed work, in-progress work, blockers, new arrivals, and plan changes. Define today's top priority and today's plan. Keep it to one page.

Output format: Structured Daily Execution Review Record per the template, followed by end-of-day actuals.

Never skip the blocker section. If there are no blockers, state "None." If there are blockers, include escalation status and expected resolution time.
Always define a single top priority. Not two, not three. One task that defines success for the day.
Keep the record to one page. Details belong in the task or ticket system. The review is a summary, not a dump.
Classify every new arrival. Accept, defer, or decline with a one-word rationale. Do not leave new items unclassified.
Plan must fit capacity. Include a buffer. If the plan exceeds capacity, remove the lowest-priority item.
Record end-of-day actuals. Update the record with what actually happened so it becomes the input for tomorrow's review.
Do not hide missed deadlines or incomplete work. State what was planned, what was completed, and what was deferred with a reason.
Do not report to management in the review record. The record is for the team. If management needs a separate report, produce it as a different artifact.
Link to Atlas diagnostics when blockers involve SAP technical issues. Reference the relevant diagnostic page for context.

Related skills

Priority Triage Working Skill — Use to rank new arrivals and decide what displaces existing work.
Blocker Escalation Working Skill — Use when a blocker surfaced in the review needs formal escalation.
Follow-Up Tracking Working Skill — Use to track commitments made during the review.
Task Clarification Working Skill — Use when a new arrival is vague and needs clarification before it enters the plan.

Related Atlas pages

Operational Memory for SAP AMS — How daily execution records build operational knowledge.
AI-Ready Process Documentation — Context for structuring daily records so AI agents can consume them.

Verification status and limitations

This skill is a public working interpretation of daily execution review practices. It is not official Scrum, SAFe, ITIL, or SAP methodology. It focuses on a practical daily habit for enterprise teams where alignment and blocker visibility matter more than ritual adherence.

Known limitations: the skill is designed for teams with a shared task queue or ticket system. It may need adaptation for teams that work on long-cycle tasks with no daily granularity. It assumes the team is available for a 10-minute review or can consume a written record asynchronously. For teams with extreme time-zone dispersion, the review may need to be purely asynchronous with a longer feedback loop. The skill does not replace project management tools or sprint planning ceremonies; it complements them with a daily tactical layer.