Open wamps-jp opened 10 months ago
Thank you for your input. We believe that this interaction should be quite clear for the user and there is no need for a visual example. In addition, adding a visual example requires two images, one to show the starting state and one to show the results after add
. This might result in too many examples and hence hinder the reader.
Team chose [response.Rejected
]
Reason for disagreement: You have said that "adding a visual example requires two images, one to show the starting state and one to show the results after add." This is incorrect.
To show a visual example of what add
entails, simply showing the results will do.
Additionally, the argument that having too many examples cannot apply here, since the commands add
, list
, edit
, delete
, find
, and sort
all have no visual examples to explain. Having a visual for the add
command - the most important command in the application - is almost necessary for user clarity.
While not all commands may require a visual example of the result, since the
add
command is the primary way to input data, having a visual example of what happens after an employee is added would help the user greatly in understanding the interface of the application.