This series of articles demystifies marketing myths and
jargon for software product design and MVPs.
Here is the summary:
This is the reason why I talked about specification and design in
this suite of articles. The reason for this is that these two parts are
dependent on and complementary to each other.
Design is about imagining and creating products that are meaningful
to people. Designers use a language based
on human senses to express the appearance and behaviour of a product.
Nowadays, we mainly use Vision, Touch and sometimes Hearing to interact
with digital products.
Defining the product using the User
Stories helps us to establish a common
language that everyone in the team understands: designers,
developers, the project manager and you.
Entities, sketches and mock-ups
Depending on the meeting points and User Stories, we will draw an
entity relationship diagram (ERD), representing the different entities
involved and the different stages of the product.
These will be important for this step as well as the Technical Stack
which will be discussed in the next article.
Based on the User Stories and Diagrams, the designer begins to do
sketches. Describing in general what your
product will look like and how it will behave. It will use thick lines and
large boxes, focusing only on the general appearance, ease of use of the
product, and its interaction with the user.
Your feedback is very important at this stage, but always keep in
mind to focus on the main features and the overall layout. This is not the time to decide if a button is too
The designer or designers will iterate and present several sketches
by studying the user's behaviour and interaction with the user
Puis, il établira ce que l’on appelle les .
Un ensemble d’éléments visuels et de design représentant votre produit et
identité de marque.
Then, he will establish what are called “Styles Tiles”. A set of visual and design elements
representing your product and brand identity.
It will also create mock-up:
graphical representations of product views, layouts and states. However,
one important thing to keep in mind: mock-ups are only a static representation of the
There are still many customers who complain when a view of their
mobile application does not exactly resemble the mock-up that has been
Many people and agencies working in the digital sector have the bad
habit of defining a product by a set of graphic data (a series of PSD
That, in my opinion, is what makes so many bad digital products and
applications. It often ends in unpredictable situations where what seemed
like a good idea on paper would produce a bad user experience directly on
An image will never represent a functional digital
The only purpose of mock-up and graphical data is to avoid making
early user experience (UX) errors. They are only a
guide for visual interaction and not a final representation of the
Following this feedback loop with your team or agency, you will
obtain a list of the main features and a set of mock-ups, the visual
elements that define the behavior and appearance of your MVP.
We are at the end of this first series of articles dealing with
"Design and Specifications"
I hope that these articles will help new entrepreneurs and start-up
founders to understand the first steps in building a minimum viable