When a website redesign needs workflow changes

If people struggle to understand your offer, start with the content and design. If the difficult part comes after they inquire or book, look at the workflow too.

Trace one customer action through to your team's next step. It can show whether the project needs better pages, changes to existing tools, or a connected system.

Your preparation checklist

Use the checkboxes while reading, or copy the list into your project notes. Your selections are not saved.

Choose one customer action. An inquiry, a class booking, or an order is enough to start. Note how the person reaches it.
List what they need to know. Include the service, price or estimate, availability, and information needed to take that step.
Define what completion means. A request received, a place reserved, and a payment completed are different states. What should the customer see next?
Follow the information to your team. Where does it arrive, who handles it, and which record do they rely on?
Mark the awkward steps. Note repeated typing, missing details, lost selections, failed notifications, cancellations, and work that has no clear owner.
Name the tools and decision-maker. List the accounts involved and who can approve changes. Bring an inventory first, rather than passwords or customer records.

You can leave questions unresolved. The checklist is a starting point for agreeing on the work, not homework you must finish before contacting us.

Use the journey to choose the scope

Content and design: people need a clearer explanation, better service pages, useful photography, or a more obvious next step.
Existing tools: the page works, but form questions, settings, notifications, or handoffs need attention. Review what the tools can already do.
Connected workflow: booking rules, payments, records, or owner tools need to work together. Assess suitable connections and custom development against those requirements.

You may need more than one. Define each part clearly, including tool access, migration, testing, approvals, and ongoing costs, before committing to the build.

Two different project examples

For Aloha Florals 808, photography and published pricing help people explore the flowers. Wedding and lei inquiries ask different questions, giving each request a useful starting point. This example concerns the released website and its inquiries.

Migiwa Yoga Space carries a selected class through sign-in and booking. Ticket credits, card payment, and cash at the studio connect to owner tools for classes, attendance, and payment records. It illustrates a broader custom workflow with its own support responsibilities.

The examples show different scopes. A custom studio platform is not a default requirement for a useful website.

Details when you need them

Try the existing tools before replacing them

Review the questions your forms ask, where messages go, available settings, exports, and connections. A small configuration change may address the problem. Confirm the tool's permissions, limits, fees, and failure behavior before depending on a connection.

If custom work is justified, define the rules and acceptance checks before building. Include hosting, maintenance, support, and handover in the comparison. More software still needs a clear operating process.

Check what the customer sees after acting

Write down the success and failure messages for the action. Tell people what happened, what they can do next, and how to correct a problem. W3C's form-notification guidance describes clear feedback for successful submissions and errors.

Also test what reaches the team. A confirmation shown to a customer and an email received by staff are separate checks. Name who reviews failed work and what the manual fallback is. Use sample data for the agreed tests.

Keep useful pages and links through the redesign

Workflow changes can happen without changing every public URL. Inventory the pages and links worth retaining before replacing a site. If addresses change, agree on relevant destinations and test the redirects at launch.

Google's site-move guidance recommends mapping old URLs to their new locations and avoiding unrelated redirects to the homepage. Keeping this plan explicit does not guarantee rankings; continuing SEO and content need their own scope.

Agree on who runs the result

Name the people responsible for customer replies, bookings, cancellations, and daily records. Agree who owns the accounts, pays third-party bills, grants access, and approves the launch.

Document the operating instructions and technical support boundary. Building a system and staffing the business are different responsibilities. Optional website care and future changes can be scoped separately, with their fees and limits clear.

Bring the journey to the first conversation

Share your website, the customer action you chose, the tools involved, and the step that causes difficulty. Leave private customer information and access credentials out of the initial inquiry.

Explore our website design and redesign service and business systems service, or tell us about your project. We can help turn the unknowns into a defined scope.

If you're still deciding, a free website review offers three practical suggestions about your homepage and one customer journey, with no obligation to hire us.