Give design feedback that moves the work forward.
A shared goal, a real task, and specific observations make a review easier to act on.
Add the features your customers need, improve journeys, or extend what your product can do. We design and develop the next release around the product you already have.
A live product creates new opportunities as well as feedback. Connect the next release to what customers and the business need to do next.
Users need help at the same point in the journey. Bring the feedback and the product behaviour together to understand what needs to change.
Requests compete for attention, but their purpose and dependencies are unclear. Choose a set of changes around a useful outcome.
You want to add a service, reach a new audience, or give users more control. The change needs to fit the product and systems already in use.
Move the sample changes into a proposed update. Use the plan to discuss the affected journeys, dependencies, and checks before implementation.
Choose the improvements to include in this example plan.
Start with the product, the next business goal, and the team maintaining it. The release can add new functionality or improve the experience already in use.
Group the next website or product improvements around a task your customers need to complete.
More for sole proprietorsBring early feedback into the product decisions, then design and implement a focused next update.
More for startupsAdd the features or operational capabilities the business now needs, with input from the people maintaining and using the product.
More for small & medium businessesSupport your existing product and engineering team on an agreed set of changes within its review and release requirements.
More for enterprisesUnderstand the existing product before changing it. Review the design and implementation impact, then check the affected journeys before release.
An improvement brief grounded in available feedback.
Review the product and identify the tasks and dependencies involved.
Share feedback, product access, and the relevant implementation context.
A prioritised change set and proposed direction.
Outline the changes, their dependencies, and the areas they affect.
Confirm priorities and include the people responsible for product and technical decisions.
Implemented changes and findings from the agreed regression checks.
Design and develop the scoped changes and check affected interactions.
Try the revised tasks and consolidate feedback on the agreed changes.
A reviewed update and release notes.
Prepare the release checks, change notes, and agreed handover.
Approve readiness and confirm ownership of the release and subsequent improvements.