Author: Santhana Krishnan G

Product Visioning: 2.3 Building Hypotheses

Product Visioning: 2.3 Building Hypotheses

Posted by | Mar 5, 2018 | , , |

Previous Articles in Product Visioning series: Product Visioning: http://pm-powerconsulting.com/blog/product-visioning-5-steps-scoping-software-projects/ Product Visioning: 1. Elevator Pitch: http://pm-powerconsulting.com/blog/product-visioning-elevator-pitch/ Product Visioning: 2.1 User Persona: http://pm-powerconsulting.com/blog/product-visioning-2-1-user-persona/ Product Visioning: 2.2 User Goals, Pains, and Gains: http://pm-powerconsulting.com/blog/product-visioning-identifying-right-target-persona/ Product Visioning: 2.3 Building Hypotheses using Persona and their Goals, Pains, and Gains. Strategyzer provides an effective template called Value Proposition Canvas. In our previous articles, we have built components of Value Proposition Canvas, User Persona, their Goals, Pains, and Gains.  After identifying our personas and detailing out their goals, motivations, pain points and gains, we have to arrive at certain hypotheses about target user segment so that we can build and prioritize...

Read More
CHOW #74- Persona: Roles, Pains and Gains

CHOW #74- Persona: Roles, Pains and Gains

Posted by | Aug 28, 2017 | |

Say, we are building a product for K12 segment.  We may map School Principal of a particular segment in the following manner: (Disclaimer: This is just an example. Resemblance to any individual or organization, if any, is not intended, may only be a coincidence) School Principal: Roles / Goals Teacher Hiring teacher Assess teacher capability Form and Execute training plan Mentoring Text book selection (map syllabus to book) Teacher scheduling & allocation Feedback / review cycle (teacher effectiveness) Setup & Monitor scoring rubric for assessment School admin reports and regulatory compliance School performance Engage with Peers (schools / principals) Participate...

Read More
Product Visioning: Identifying Right Target Persona

Product Visioning: Identifying Right Target Persona

Posted by | Aug 28, 2017 | , |

In our Product Visioning series, we have already explored Elevator Pitch and User Persona. Just to recap, the importance of identifying right target persona: Helps in building great products that our customers like and use Efficient product prioritization and smart investment  results in better ROI Helps in improving marketing teams’ productivity Improves our brands messaging After identifying the target personas, we have to detail out their goals / motivations, pain points and what they would gain by using the product / service. We collect these useful information through market research, user interviews, observing target users, by collecting information from their interactions...

Read More
Product Visioning: 2.1 User Persona

Product Visioning: 2.1 User Persona

Posted by | Mar 5, 2017 | , , |

User Persona What? Latin: Persona = Mask, Character played by an actor In large open air theatres, classical masks were able to bring a character’s face closer to the audience.  In the present scenario, in the field of Product Development, Marketing etc., actual customers are described by visual storiescalled Personas. Personas are fictional characters representing commonalities of a representative sample of a system. They draw a comprehensive picture of the users. The details include what our users want to accomplish, what skills they may or may not have and what their needs, wants and priorities are. Although the personas are hypothetical, they are defined with rigor...

Read More

CHOW #49– Common Pitfalls in building user persona?

Posted by | Mar 5, 2017 | |

We know User Persona is an incredibly powerful  tool when used properly with UX design philosophies. But, developing a good quality user persona is a time consuming and expensive activity. Some times, these challenges may lead to producing not so great output. Similarly, what are some of the common pitfalls / mistakes in builing user persona?   Suggested Solution: Here are some of the few common pitfalls in building user persona: • Rapid Persona ○ Due to time constraints or some other challenges restricting teams ability conduct meaningful user research, teams might come up with half baked Personas. This could lead to potential waster in product developmentl • Fake Persona ○ To justify a product feature the team have developed or planning to develop, one or more personas could be invented / created. Such fake personas may not represent a real customer. It would just satisfy teams wish to continue with development. Teams should be careful in avoiding Fake personas. • Averaging ○ Personas are not about covering as much ground as possible. Compared to traditional marketing, we would not use wide ranges like Female aged between 15 and 35. This doesn’t help innovation. We need personas as close to the real customer as possible. • Rusting Persona ○ Some teams come up with a lot of personas more than actually necessary. Some of the Personas would be a showcase piece never to...

Read More