A crucial component of implementing Design Thinking in the project is to extract information from testers – functional consultants, end-users or business users – when they are sharing feedback. The difference between the two iterations of the prototype depends on the quality of the feedback.

Consider the example shared in Part 01.

If the end-user is an analyst using the ALV Output to perform some task X followed by task Y and task Z. At each iteration, the development team needs to understand whether the analyst is able to complete task X, Y and Z successfully using the output. The test scripts need to take these considerations into account.

Another factor the team needs to take into account is the diversity of the end-users. An end-user in India might perceive things differently than someone in Canada or Japan. If and when applicable, the testing after every iteration of the prototype should be done with a variety of end-users keeping into account the length and breadth of the audience.