You wake up in the morning, you turn off your alarm, and as you lie there in bed, you check you facebook, your Instagram, your WhatsApp, your Twitter, your texts, your emails and then the news. Then you go to the bathroom, you use the toilet, brush your teeth, take a shower, get dressed and then head for the kitchen. You drink some coffee and eat breakfast. Maybe you watch the news or check your emails again. It’s the same routine you follow everyday.
There are many kinds of informal user research methods. Examples are focus groups, contextual inquiries, coffee shop intercepts, and the like. These informal qualitative methods of user research have proved popular among UX practitioners for their simplicity, low cost, and reduction of the intimidation barrier. But we are experimented with a slightly sideways method of informal user research—drunk user testing (DUT).
Globally many companies are going remote-first, fully distributed or changing their current people strategy to allow remote work as a viable option and we are talking more than just a WFH policy.
The OKR process is centered on the principle of setting ambitious goals (Objectives) then breaking those Objectives down into Key Results (KRs) which are highly measurable. Underneath each Key Result will be a list of tasks (ToDos) which are the actual things you will do to deliver your Key Results. The results of those elements are typically graded once per quarter.
The big product idea – where it all begins
I have come across several startup projects during this pandemic and thought it would be good to share some insights. We all have ideas and think we know how it should be executed. Whenever I catch up with a close family member and share a few beers, we talk about startup ideas and wonder how great it would be if we could pull it off. I must admit some of it is just pie in the sky. How do we then proceed with that idea and don’t just throw money down the drain?
Time to spill the beans on making the perfect product
Here’s your three-step process for turning a dream into a real product:
- Everything is created twice, first in mind then in reality. Have a vision statement.
- You cannot manage what you cannot measure. Define success measures.
- Success is the progressive realization of a worthy goal or ideal. Validate continuously.
The product vision statement
For: «target customer» Who: «needs» The: «product name» Is a: «product category» That: «product benefit. Reason to buy»
Unlike: «competitors» Our product: «differentiation or value proposition»
A simple, clear and concise vision statement helps you and others understand what the product idea is and whether it is going to stack up against other solutions out there. Follow the format given above and it will help you start off on the right foot.
How to define product success
Great! You are ready to hire some developers and start executing. Have you thought about how you will know whether the right functionality is being delivered? You need to define what your objective is and how you will know whether you have met that objective. Objective and Key Results format created by Andy Grove is a useful tool. Another way is to define a goal for a quarter and the metrics i.e. success criteria to determine if the goal has been met.
Continuous product validation
In this digital age, product development i.e. Execution has become easy due to availability of cloud services i.e. Software as a Service, Infrastructure as a Service, Platform as a Service, Development as a Service?, * as a service. This allows ideas to be tested and developed quickly. As you can imagine there might be others out there thinking of developing a similar product.
To test your idea, you need to launch quickly. Change is the only constant these days and the availability of the * as a Service allows us to pivot when needed without too much effort. Quite a few founders fall into the trap of spending too much effort on defining a solution without knowing whether there is a market for their product. It is OK not to have a “normalized” database or not to know exactly how the users will interact with the system.
Take an iterative approach and release early and often. Measure the response from your users and learn from them.
Did you just think of a product idea while reading through this blog? Create your vision statement and define success measures. Get in touch and let us turn your idea into reality through continuous deployment and validation.
Whatever your natural way of understanding the world is, wouldn’t it be good to step into someone else’s shoes and see the world the way they see it?