1) Leopoldo Almeida

How do you prototype your solution? How do you develop a product roadmap?

2) Wanderley Abreu
Product’s life cycle

3) Marco Mombelli
What techniques do you use to speak with your target customers and get feedback
on your solution?
 • In-depth analysis thanks to longer speaking time
• Diversity of interviewees’ profiles
• Higher potential for insights
• Enrichment of responses
• Possibility to use coding and perform statistical
• Cheaper than face-to-face interview in case you
analysis
perform only a light analysis of answers
• The statistical treatment of results makes it possible
• Is useful is confirm insights obtained through
to use those robust insights as the fundament of a
other qualitative methodologies
quantitative survey
• Easy to organize in a B2C case
• Less bias than with a focus group

• Speaking time of some attendees may be

• More complicated to organize (hence higher
considerably higher than that of others, making
organization costs), especially in case of no-show
their contribution disproportionate
(consider that 20% of interviews will have to be re-
• Lower average speaking time
scheduled)
• Moderator’s bias hard to prevent
• More complex to interpretate
• Difficult to organize in a B2B setting
• Treine com, e aperfeiçoe, com pessoas que
você conhece
• Guie, mas deixe aberto para inputs
• Faça perguntas de necessidade e solução
• Entenda o produto usado no momento
• Repita as perguntas em diversas formas
• Quando possível, fale em números
• Anote, não grave
• Se possível, leve um acompanhante
• Force a resposta Pos/Neg
• Force e/ou respeite o tempo pactuado
• Não foque só nos grupos mais acessíveis
• Evite perguntas tendenciosas
• Não venda! Pergunte!!!
• Não explique a pergunta
• Não comente ou influencie, nem com
gestos ou olhares
• Não tente agradar – bate papo só inicial!!
• Não pergunte/fale sobre a ideia principal
em entrevistas – Vc vai influenciar!!
• Não pergunte se funciona ou se está bom!
• Em grupos focais, “não seguir” o líder
 Trabalhe com Hipóteses

Se algumas a hipóteses não foram validadas, Parabéns.

Poupou tempo, dinheiro e energia!!!

Agora ache outros atributos e/ou produtos pra vender

 Analysis
1) Analysis
2) Design
Design
3) Implementation
4) Testing
5) Maintenance Implementation

Testing

Maintenance
• Research the problem/company/product/widget
• Poll/Survey user base
• Identify priorities of use
– Pare down extraneous requests that dilute the product
• Brainstorm potential solutions to the problems
• Present findings (Note: we haven't opened photoshop yet)
– Communicate plan for appealing to the largest demographic as well as
supporting minority users
– Negotiate an agreement on what the client wants and what their consumer
demand is
• Build user stories (I this than that)
• Site map development
• Time lining and phasing
– Identify the elements of the application that fulfill minimum business requirements
– Identify the elements of the application that fulfill scaleability requirements
– Identify the elements of the application that fulfill client wants
• Identify UI element needs (what
kinds of actions)
• Identify Master/Detail formatting
(if I click this I get that)
• Design mockups (Wireframe)
• Implement Wireframe as lo-tech
prototype (i.e. Invision, Axure)
• Usability testing
• Begin development lifecycle for approved functionality (Design Agnostic)
• Move through iterations of Development, QA, Staging, (DQS)
• Begin layout and design of UI elements and screens
• With approved design elements
• Integrate visual layer with functionality (Iteration until complete)
• Allow limited access for bug reporting, and usability testing
• Iterations of feature request and bug fix development
• We can start by understanding best practices in UI design.
Resource for psychology of aesthetic
http://en.wikipedia.org/wiki/Gestalt_psychology
• Understanding why we like something when we see it and
identifying areas we can put these ideas and theories into practice.
• Some more resources for UX UI design
http://developer.android.com/training/best-ux.html
http://uxmag.com/
• Understanding what can and can not be done
http://www.w3schools.com/
http://css-tricks.com/
• 1 - Responsive navigation on a complex website
http://smashingmagazine.com/2013/09/11/responsive-navigation-
on-complex-websites/
• 2 - Discovering the purpose of your website
http://res.im/feed/discover-purpose