Journey Mapping
Part of Customer experience for digital services
Comparing account creation with guest access from a CX perspective
Compare account and guest routes by task completion, return access, recovery and service security needs.
Consider an account when a customer needs continuing access to information or an ongoing service. For a one-off task, test whether they can complete it and check its status without creating one. Compare what each route lets the person do, when it interrupts the task and how it protects their information. An account, sign-in and an identity check solve different problems.
Compare the same customer goal
Start with a specific task, such as submitting a one-off request or returning to update a saved application. Sketch both routes from entry to a confirmed outcome. Include sign-in recovery, returning to saved work and how a guest retrieves a result; counting registration screens alone misses these parts of the experience.
| Decision point | Account route | Guest route |
|---|---|---|
| First visit | The customer may need to create and verify credentials before continuing. | The customer may begin sooner if the service permits it. |
| Return visit | A signed-in area may support saved work or repeated updates. | A suitable reference or recovery method may support a one-off status check. |
| Support and security | The service needs a workable sign-in and recovery process. | The service still needs to protect information and check who may retrieve it. |
Test the interruption and the return
Ask participants to complete the same goal with each proposed route. Watch whether they understand the choices, recover from an error and reach the correct outcome.
For recurring tasks, include a later return: does the account save meaningful effort? For guest access, check whether the customer can find the request again without exposing information to someone else.
Repeated access or a need to resume work may support an account, but neither automatically means asking for one on the first screen. Explain its value when the customer needs it, and distinguish creating an account from signing in to an existing one.
If a guest route is offered, make it visible and explain what the customer can do afterwards. Assess identity checks separately against the service’s risk and access needs.
For a one-off transaction, a guest route can let customers check its status using a unique reference sent by email or text, rather than creating an account.
If customers need to regularly access or update their data, an account may be appropriate; let them use as much of the service as possible before asking them to create one.
Decide with an outcome check
Compare unaided completion, errors, return success and requests for account help. Review these alongside the service’s security and record-keeping needs.
If guest access works for submission but fails when customers need to amend a request, redesign the follow-up path. If an account is required, reduce repeated data entry and test recovery.
