This series of articles demystifies marketing myths and
jargon for software product design and MVPs.
Here is the summary:
You are now ready to present your idea to the team. Among the
participants, there should be at least: a software
architect, a designer and
a project manager. It is possible for a person to take on two of
these roles at the same time
Don't be more than 4 people. It is about keeping to a minimum in
order to express your ideas in an effective way. Large meetings always end
in even more confusion, without a clear result and without an action
At the kick-off meeting, we always start by asking the founder to
present his idea to us as simply as possible, answering the questions I
have described above. We take the role of a stranger who hears it for the
first time. So explain your start-up idea as you would with your family,
friends or investors.
We will then continue with a series of questions to establish what
is called Brand Personality. We will ask
questions about the personal traits and characteristics you would
recognize about your start-up if it were a person.
This strategy is very effective, since it frees up the pressure of
the founder who would like to express too many details at once. New
entrepreneurs are generally overexcited with their projects. At the same
time, they want to explain how it works and how extraordinary their
At this point, we understand what your product is and what you want
to accomplish. It's time to go into a little more detail. This is a
crucial step that defines the main functionalities. We call it the
This means that we take on the role of a potential user who is ready
to try your product for the first time. We describe each user's action in
a very concise and objective way, the sentence should fit on a
We track the price of the actions the user takes, keeping it as
simple as possible. Remember to write down your ideas and group the main
features in the previous article? It is time to present them.
Finally, we end up with a list of User Stories that needs to be
The kick-off meeting should end with a coherent set of User Stories
(features) and a good understanding of your product personality.
Refining the User Stories
Depending on the project, after the meeting, iterations will be
performed on the User Stories, functions will be removed or modified, but
The addition of new functions should be avoided at all times. There
will always be the temptation to include a new function that you consider
important. Remember! Remember! If this function is not absolutely
necessary for the first prototype to work, do not include it.
Later, you will often find, based on the comments and measurements,
that the "cool" function you wanted to add is not what your users "really"
need and would not have brought any value to your business.
That is why your decisions will always be based on comments and
measures, that is the whole point of a Viable Minimum Product.