Turn a Meeting Decision Into Follow-Up
Design a post-meeting flow that converts one agreed decision into a durable record, owned actions, and visible follow-up.
The brief
Understand the problem
Background
Notes often capture discussion but leave the actual decision buried. Days later, participants disagree about scope, nonparticipants lack context, and action items have no owner or due date.
User context
Keiko facilitated a pricing review where the group agreed to delay annual-plan changes and test a smaller onboarding message first. She needs confirmation from the decision owner and follow-up from marketing and analytics.
Product problem
A facilitator needs to summarize an outcome accurately, resolve disagreements quickly, and connect the decision to work that can be tracked.
Objective
Create a focused decision-capture and follow-up experience for the hour after a meeting.
What to design
Define the experience
Required experience
- Draft a decision from the meeting record
- Confirm scope, rationale, and decision authority
- Assign follow-up actions with due dates
- Resolve a participant's correction without rewriting history
Screens and states
- Meeting outcome review
- Decision record
- Action assignment
- Correction and follow-up status
Core user flow
Follow the critical path
- 01
Keiko opens the ended meeting and selects the discussion segment
- 02
She writes the decision, excluded scope, and rationale in plain language
- 03
The accountable product lead confirms it while one attendee suggests a correction
- 04
Keiko accepts the factual correction and assigns two follow-up actions
- 05
The published record links back to the meeting and shows action progress
Product rules
Requirements and constraints
Requirements
- Distinguish discussion notes, proposed decisions, confirmed decisions, and actions
- Name the person with decision authority and the confirmation time
- Capture excluded scope and unresolved questions alongside the outcome
- Let corrections amend the record while preserving prior versions
- Link actions to existing work rather than duplicate them where possible
Constraints
- A transcript excerpt is supporting context, not proof of agreement
- Only authorized participants can confirm or amend the decision
- Meeting access rules must carry through to sensitive records
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens showing a decision draft, confirmation, correction, and action tracking
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Playfair Display & Source Sans Pro
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Playfair Display & Source Sans Pro
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Theory to review
UX principles for this brief
Use these as decision lenses, then validate the design with the people and context in the brief.
