Unit 5 · Lesson 17 of 20
Make a responsible release decision
Stage an improvement around system limits, owners, and patient needs.
01 / Learn
Learn the method
Fictional case
The clinic can update kiosk wording this month. A change to the appointment service and staff queue requires a later release.
Terms for this lesson
- Constraint
- A service condition that shapes a feasible design choice.
- Dependency
- A required event, system, or owner supporting a release.
- Release condition
- A check that must pass before a proposed change reaches patients.
A constraint describes a condition that shapes what the team can deliver. The clinic's release calendar, the queue refresh interval, and reception capacity all matter to the check-in design. Record each condition with its owner and the evidence that supports it. This turns a vague limit into a concrete planning input.
Separate what the current release can improve from what a later release can improve. Kiosk wording can describe the service receipt accurately and guide patients during a delay. Reception can use a shared status-check script. A later service change can shorten the queue interval or provide direct staff visibility.
Give every interim route an operational owner. A reception-help link works when staff can query the appointment service and explain the result. A status message works when engineering ties it to the right event. A staged decision names these dependencies, the patient consequence, and a check after release.
Define a release condition and a pause condition. The team can release wording after verifying receipt behavior and staff support. A service state that leaves staff unable to confirm arrival calls for a different interim route. These conditions keep the recommendation connected to the clinic's actual capabilities.
Use the method
- Record the current service limits and their owners.
- Separate the improvement available now from later system work.
- Set release checks and a condition for revisiting the plan.
A practical constraint becomes part of the design when the team names its owner, patient effect, and release condition.
- GOV.UK Service Manual: How the discovery phase works ↗Surface policy, technical, and organizational constraints before choosing scope.
- GOV.UK Service Manual: Designing good government services: an introduction ↗Consider a service from beginning to end, front to back, and across channels.
- GOV.UK Service Manual: Sharing user research findings ↗Bring evidence into team decisions while it can still affect the work.
02 / See the reasoning
Worked example
The team schedules receipt-backed copy for the current release and gives reception a lookup script for delayed requests. Engineering verifies that the receipt trigger matches an accepted arrival. Operations tests the script during a busy morning. A later release targets the staff queue refresh. The decision record includes a check on repeat entry and reception questions after launch.
Try a decision →03 / Decide
Guided decision
The kiosk copy can change now, and the staff queue integration is scheduled later. Which current release plan connects patient status to operational support?
Feedback on your choice
What could change the answer: A direct lookup that becomes unavailable during outages would require a different delayed route or a narrower release.
Use this feedback to examine your choice and written reasoning.
Build your case file →04 / Build the case
Your case file
Fictional case update
The clinic's evening reception team has fewer staff members and a longer response time for status questions.
Evidence and constraints
- Fictional delivery fact: kiosk copy can change in the current release.
- Fictional delivery fact: staff queue integration belongs to a later release.
- Fictional operations fact: reception can query the appointment service directly during staffed hours.
- Fictional extension: the evening team has fewer available staff.
Add the evening condition to the staged plan. Name the owner, patient route, and a release check for that period.
Create: A staged release memo with patient status, dependencies, owners, checks, and a pause condition.
The plan gives patients an accurate current route and assigns ownership to every supporting service step.
- The current and later releases have distinct outcomes.
- The staff route has a named owner and check.
- The release condition follows actual receipt and lookup capability.
The release plan reaches several channels. The next lesson aligns their messages and owners.
Lesson complete
You added to your case file.
You studied the method, practiced a decision, and added an artifact to your case file. Carry that reasoning into the next lesson.
05 / Keep working