# Plan a week around one achievable outcome

Illustrative planning brief; no automatic product import.

Illustrative case: the team wants to complete an export filter this week while two members also cover support. A long wishlist exceeds available time.

## Decision

Commit to the date-filter outcome and defer the optional formatting upgrade.

## Owned work

- Confirm the weekly outcome
  - Owner role: Product lead
  - Acceptance evidence: The team agrees that an export respects the selected date range.
- Reserve implementation and review time
  - Owner role: Sprint coordinator
  - Acceptance evidence: Named owners confirm availability including their support duty and review workload.
- Validate and accept the outcome
  - Owner role: Reviewer
  - Acceptance evidence: Boundary-date evidence is reviewed before the weekly outcome is called complete.

## Workflow

1. Start with one outcome and identify the tasks that directly support it.
2. Compare owner availability against implementation and review needs.
3. Record deferred work and the reason, then review the outcome at the end of the week.

## Judgment

A weekly plan is a commitment discussion, not a guarantee that every task will finish.


## Filled illustrative decision

The fictional team reserves support coverage before committing delivery time. It keeps the export date filter and its review in the sprint, while deferring optional presentation formatting. The commitment names the filter outcome and reviewer window rather than promising every item discussed in planning.


## Workflow questions

### Should everything be estimated?

Estimate enough to expose a capacity mismatch. Investigate tasks whose uncertainty prevents a credible commitment.

### What about routine support?

Reserve time or a rotating owner explicitly. Treating support as invisible makes the delivery commitment misleading.

## Product connection

Take the proposed sprint outcome and acceptance boundary into your TeamBoostAI planning review before making a commitment.

Confirm account availability before adopting this manual outline.