The feedback interaction of the Design Process Modeler

You-et / Mar 6, 2020

The Design Process Modeler personalizes a model that represents the design process by adapting to a series of questions. The intention is to explore different phases of the design process. The user can select and alter answers. This has consequences. In this blog, we discuss the feedback to explain what the consequences were, such as changes in the model and disabling a question. Try the modeler for yourself.

The Design Process Modeler

The modeler builds a model in real-time with a series of questions. The user responses to a question by selecting one of the buttons. The 'Why?' button shows an explanation of the question and options. When an option is selected, the model changes and the next question appears. Sometimes the answer does not impact the model because it already matches the answer. Furthermore, some answers have impact on another question.

Should Test be a separate phase? - [Yup] [No] [Why?]

Feedback when the model changes (or not)

The model can change based on the selected answer. There are basically two options to a question. One button will change the model and the other keeps the model the same. However, as it turns out, it only remains the same for the initial answer. If the user first selects 'change' and secondly selects 'remain', then the model has changed two times! Fig 1 shows this process visually.

The response can changes the state or the state remains the same

Fig 1. The response can changes the state (green) or the state remains the same (orange). It's possible that the state has changed and changes back to the original state (green dashed). This last case is special because it's textual different.

The question has room for text to explain what changed in the model (Fig 2). It will show text in all three cases:

  • The model remains the same.
  • The model changed aspect A.
  • The model changed back aspect A to B.

The second question shows feedback based on the implications of the selected button

Fig 2. The second question shows feedback based on the implications of the selected button.

Feedback when the question becomes disabled

There are questions that depend on other questions. Let's look at an example.

Add element X? - [Yup] [Nope]

Which shape for element X? - [Round] [Square]

In the example, selecting a shape for a non-existing element is not relevant. Therefore, the question about the shape is invisible when the user chooses against the element. However, users can change their answers. What happens to the depended question that's already shown?

For the modeler, the question remains visual but becomes disabled. This way, the feedback shows the consequence by color and text. Fig 3. shows an example. The user has changed the answer to the second question and therefor the third question becomes disabled. The buttons become inactive but do not explain to the user WHY this has happened. The textual feedback helps to explain what caused this.

Four states of buttons

Fig 3. The disabled question explains why it is disabled.

You might also like...

Design Process Modeler

BLOG - January 12, 2020

The Design Process Modeler personalizes a model that represents the design process by adapting to a series of questions. Here is a little warning: it is work in progress. > Read