Choose the first release by the task a person can finish

A first release can be small without being unfinished. The useful boundary is a task that a customer or staff member can complete with an understandable result. A collection of half-connected screens is harder to evaluate.

Choose one journey

For a Costa Rican service business, a first release might explain the offer, collect a request and let staff reply with the information they need. Instant payment or a custom portal can come later if the initial process works deliberately without them.

Name what remains manual

Manual checks are acceptable when somebody owns them. Write down who checks availability, sends confirmation and handles changes. Avoid implying that an unfinished integration will silently fill the gap.

Agree acceptance before building

Give reviewers a normal request and an exception. Ask them to follow the whole task on an appropriate device and explain the current status afterward. A visual approval and an operational acceptance answer different questions.

W3C's accessibility planning material illustrates the value of assigning responsibilities early. Use the project-notes worksheet to identify your own responsibilities and the smallest useful release. We can then discuss whether design, a focused repair or a new application is the right piece of work.