• Home
  • jajzbbod
  • 5 design workshop templates for agile experience design

5 design workshop templates for agile experience design

            [editor’s note] this article is reprinted from @ a soil thief’s personal blog. And in the same simple and crude "brainstorming", or "needs assessment" flat and uninteresting, agile experience in process design is always open, emphasizing the demand recognition in the interaction with customers, and output design of project deliverables to reach a consensus.

for the past five years, the author has been involved in dozens of customer design workshops, which we share with five frequently used design workshops.

template 1: user value definition

The definition of

user value is the basis of any software experience design – what exactly is the user’s problem?. For the problem of the definition of more accurate and clear, the more able to reach agreement on product characteristics or design direction, when all customers think, solve the user A in the context B C is the core of the delivery of the target, so natural, and any solution to this problem beyond the design, function, and even the discussion it should be placed in the low priority. This activity can be carried out regularly, and the user value board can be retained for a long time, and the identified user problems are put on the board for unified management and evaluation.


sorts out the typical user on the left hand side of the drawing board;

brainstorm issues that users might encounter;

expands on every issue – what happens in a situation? What is the pain of the problem? What does the user do now to solve this pain?

expands each problem and then digitally evaluate each dimension – the frequency and circumstances of the situation and the problem, the extent of the pain, and the risk size of the temporary solution.

summarizes all the questions, adds the numbers, matches the typical user’s priorities, sorts out the issues that should be paid attention to and solves them, and then goes into the design phase.


element explains


users: who’s going to have this problem,


situation: what kind of situations do you have,


question: how do you define this problem,


pain: what kind of pain (direct or indirect) does it cause,


temporary solution: what does this user do to alleviate this pain,



1, try to avoid descriptive Abstract expressions, and try to use fact based language, such as: express pain, avoid "inefficiency" and say "Daily"


Leave a Reply

Your email address will not be published. Required fields are marked *