Pencil and paper vs design tools
Janne is a PhD in software engineering and has been involved in research and development in the field of software usability and user interface design for more than 7 years in cooperation with leading Danish companies. Works as an interface designer in key Trifork mobile application related projects (KMD, DSB, Danske Bank, Radiometer A / S, Roskilde Festival).
We invite you to get acquainted with one of its publications, which is dedicated to the choice of tools for design.
Over all these years, I was repeatedly asked why I, the designer of interaction and user interfaces, did not use any drawing tools or prototyping systems, and still prefer pencil and paper, despite the availability of all these really smart and convenient tools. Well, try to explain.
Usually, I never get to make the first draft of a prototype software at once, even though I carefully study the wishes of the customer and users. Understanding the new field is a time consuming process. Before I demonstrate the first draft of a prototype to a customer and users, I always learn a lot about a particular subject area. However, it always happens that the customer forgot to tell me about something very important, or I myself could not understand the importance of something. These amendments, as a rule, require adjustments in the design. And here begins the complexity ...
')
I have noticed that it is much harder for me to force myself to make the necessary changes when I create a prototype using software tools rather than on paper. I noticed the same thing about my colleagues. Why? The answer is simple and lies on the surface.
The fact is that one of the main thrusts to the use of frame representations before starting to write code was the fact that the developers reluctantly took to rework the design, because this meant massive code changes, a waste of time and money. To limit the amount of transcoding, frame models appeared (among other things), because to sketch a model frame on paper takes less time than writing code, and therefore it is easier to change if necessary.
But with the increasing popularity of frame drawings in the development process, tools such as Axure, Omnigraffle and Balsamiq began to appear. I noticed that it takes me a lot more time to sketch the framework in any of these programs than on paper by hand. So, if the first time I did not work out, you will need to redo the prototype. In order to remake the prototype in the program, I will have to spend a lot of time again and the very thought of it discourages any desire to start working.
It is noticed that the more time and effort we spent on some task (programming or drawing is not important), the less we want to change something and the sooner we begin to resist the rational arguments in favor of the need to change something. It is for this reason that I returned to drawing prototypes by hand. This method requires a minimum of time, even in the case when you need to completely redraw the model.
So take a pencil, a sheet of paper, an eraser and a ruler and start working in the old fashioned way!
Posted by Janne Jul Jensen. Original web-site
We invite you to get acquainted with one of its publications, which is dedicated to the choice of tools for design.
Pencil and paper vs design tools
Over all these years, I was repeatedly asked why I, the designer of interaction and user interfaces, did not use any drawing tools or prototyping systems, and still prefer pencil and paper, despite the availability of all these really smart and convenient tools. Well, try to explain.
Usually, I never get to make the first draft of a prototype software at once, even though I carefully study the wishes of the customer and users. Understanding the new field is a time consuming process. Before I demonstrate the first draft of a prototype to a customer and users, I always learn a lot about a particular subject area. However, it always happens that the customer forgot to tell me about something very important, or I myself could not understand the importance of something. These amendments, as a rule, require adjustments in the design. And here begins the complexity ...
')
I have noticed that it is much harder for me to force myself to make the necessary changes when I create a prototype using software tools rather than on paper. I noticed the same thing about my colleagues. Why? The answer is simple and lies on the surface.
The fact is that one of the main thrusts to the use of frame representations before starting to write code was the fact that the developers reluctantly took to rework the design, because this meant massive code changes, a waste of time and money. To limit the amount of transcoding, frame models appeared (among other things), because to sketch a model frame on paper takes less time than writing code, and therefore it is easier to change if necessary.
But with the increasing popularity of frame drawings in the development process, tools such as Axure, Omnigraffle and Balsamiq began to appear. I noticed that it takes me a lot more time to sketch the framework in any of these programs than on paper by hand. So, if the first time I did not work out, you will need to redo the prototype. In order to remake the prototype in the program, I will have to spend a lot of time again and the very thought of it discourages any desire to start working.
It is noticed that the more time and effort we spent on some task (programming or drawing is not important), the less we want to change something and the sooner we begin to resist the rational arguments in favor of the need to change something. It is for this reason that I returned to drawing prototypes by hand. This method requires a minimum of time, even in the case when you need to completely redraw the model.
So take a pencil, a sheet of paper, an eraser and a ruler and start working in the old fashioned way!
Posted by Janne Jul Jensen. Original web-site
Source: https://habr.com/ru/post/203086/
All Articles