I am a junior product manager. What do I do for market research, Ram?

Ram Almog
  • Ram explained what design sprint methodology is. The sprint starts with an idea, and the results are tested with a prototype in only one week. This extensive procedure of product designing is built to produce better products at a very much faster rate. In this Ideation process, the type of product is characterized, and all key stakeholders are gathered. The challenges associated with the product are identified. The most promising solution is selected, porotype, and validated by five users. An interview takes the feedback from the users.
  • He guided us about deciding a particular feature or capability addition to a product. First, we need to be clear about what are we trying to achieve, what kind of problem or challenge we are going to solve? The core feature we are going to add should be the answer. Starting the thinking process from the top will save enough time and resources by testing the product before release.
  • His experience has proved you can collect sufficient qualitative research data from five actual users. It provides 80% of the total input data needed to move forward. The feedback from users is collected in the context of the product directly in an empathetic way.
  • The solution is half-baked during the prototype testing, but it should be presented as accurate for evaluation. The evaluation should avoid yes/no or multiple-choice survey forms. The information collected firsthand from the user’s mouth is accurate and reliable.
  • Ram told about the procedure of design sprint at his company. It starts with a one-week interview session of all stakeholders of a project like customer care, sales, marketing, R&D, product, designer, facilitator, and a decision-maker like CEO or product manager. The interviews provide information to understand the client’s schedule. After this research, the team decides how success will look like and run the first design sprint. Then the second round of design sprint is carried to fill the gaps called Iteration sprint.
  • The theme of sprint methodology is, getting started is more important than being right. The cost of failure is very low for a weeklong practice instead of spending so much time on user interviews, analyzing opportunities, collecting numbers for months.
  • The design sprint is a short process, and for large projects, only a tiny portion is selected. The priorities are established, and multiple product design sprints are created, each focusing on small portions.
  • Regardless of sprint numbers, the context is always the center of focus. Creativity always goes together with design and engineering. Sprints should be designed to reduce the time interval without compromising the quality of the product.
  • Ram explained the benefits of online qualitative research. With current online communication tools available like zoom, conducting qualitative user testing from the actual target region is now possible. It provides the flexibility to schedule the interviews anytime, and the option to record the interview can be used later as proof of work. In qualitative research, usability testing is not necessary and can perform passive testing. For example, the users can show a video of the product and asked what they think, expect, and want to happen in the product.
  • Ram suggested viewing a video by Jake Map on 5-Act user interviews outlining all the steps required for online user interviews. Getting the conducting user is a hugely painful process. Ram has done several videos on his YouTube channel on how to get users and conduct the testing.
  • Having an idea of the market before the product is beneficial. If the testing user is searched at the potential market, it will double the customer reach. For example, most consumer products are sold, so testing should be done using the Facebook platform. For B2B type products, advertising in Facebook groups and craigslist advertising are helpful. Getting managers and CEO-level users for testing, LinkedIn is the better place to search.
  • Ram strongly advised the product managers in the tech industry to develop a lot of technical knowledge and know-how to code and programming if not, then take courses. Understanding business context is critical to do a job successfully. You are assigned to develop a great product, not just the delivery of features. They usually start with the word why are we doing and how will success look like, how might we do that. Ask right questions you will be valuable.
  • When the cost of failure in actual testing is not significantly high, one can test the actual product.
  • When the product feature can be tested only by the designed prototype.
  • When designing the sprint method cannot identify the challenge.
  • When the actual prototype does not cost much time and money, it is better to test rather than design a sprint.
  • When you do not have a good idea of what you are going to check.

Discover More opportunities From other founders 1–1 At Potlatch




Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


1–1 personalized matching and scheduling platform for professionals to expand opportunities.