So it might make sense to do this work at programme or organisation level instead. It also makes it easier for delivery teams to learn about what their users are trying to do, and to understand the journey they need to join up with. It can help you spot problems with the wider journey and make sure it’s user-centred from start to finish. ![]() That’s an issue, because this work is very valuable. They can scope their transactions in an intuitive way, but they won’t have the time or resources to research and map the user’s whole journey in detail. It’s probably not reasonable to expect individual delivery teams to build a detailed understanding of that themselves. To build things that join up coherently, teams need to understand what the user’s wider journey looks like. If they don’t, the user will get stuck and their journey breaks down. For instance, booking a theory test is just one part of learning to drive a car.įor users to complete complicated tasks like these successfully, all the different parts of the journey need to join up coherently. ![]() This is because what they’re working on is probably part of a bigger task that users are trying to complete. It’s important for teams to make sure the thing they’re building forms a coherent part of a user’s wider journey.
0 Comments
Leave a Reply. |