# A project kickoff that ends with owned work

Illustrative planning brief; no automatic product import.

Illustrative case: a small team is replacing a manual support intake form. The kickoff mentions faster routing, an admin view and a new customer portal.

## Decision

Commit to intake routing first; keep the portal outside this delivery until the routing trial is reviewed.

## Owned work

- Define the intake boundary
  - Owner role: Project lead
  - Acceptance evidence: A one-page brief lists supported request types and states that the customer portal is excluded.
- Build the routing trial
  - Owner role: Engineer
  - Acceptance evidence: Three invented requests reach the intended queues in a test environment.
- Accept the first delivery
  - Owner role: Support lead
  - Acceptance evidence: The support lead records the trial result and accepts or rejects the scoped routing outcome.

## Workflow

1. Write the customer-facing outcome and the exclusions before estimating tasks.
2. Ask each owner to confirm the evidence they will produce and the next handoff.
3. Close the kickoff with an acceptance review date; revisit deferred scope at that review.

## Judgment

An owner role is an example, not an assignment. Confirm a real person and their available time before making a commitment.


## Filled illustrative decision

The synthetic intake trial covers password questions, account changes and billing inquiries. Each reaches its agreed queue. The lead accepts routing as the first outcome, asks support to own the operating note, and records the customer portal as deferred scope. A successful routing trial does not approve a portal build.


## Workflow questions

### How much detail belongs in the kickoff?

Enough to choose the first delivery and identify its acceptance owner. Leave implementation details to the task brief unless they change scope.

### What happens to the portal idea?

Keep it in a deferred-scope note with the condition for reconsideration: evidence from the routing trial.

## Product connection

Bring the agreed kickoff outcome and first acceptance checks into your TeamBoostAI task-planning discussion before assigning work.

Confirm account availability before adopting this manual outline.