My process for creating experiences and product that people love.


Brainstorm ideas to improve existing plans, or identify problems that need solving. Some questions to consider:

  1. Why is this a problem?
  2. How are we going to solve the problem?
  3. How are we going to market the product with customers?
  4. What is the expectation on the adoption on the product?
  5. How is this adoption going to affect the ecosystem of products and customers?
  6. What is the ROI in this solution?
  7. How can we achieve a great product with technical feasibility?
  8. Do we have a technical solution?
  9. Do we need to involve other departments or resources?
  10. Do we need to purchase new technology or tools?
  11. How are we going to track the success of the product?
  12. Is there further research needed?


How can the problem be solved or the existing plan improved?

  • Competitive analysis
  • Industry trends analysis
  • Data analysis
  •  User interviewers, stakeholder interviewers
  • Observing users with product or without product

The data collected here is synthesized and developed into a Pitch.

The Pitch

Sonam Pitching

Write here…

The Pitch includes all stakeholders that will make the product a success. The UX and PO will pitch to stakeholders to receive investment to move forward. Occasionally a stakeholders will cut down the MVP down in order to cut timelines. Stakeholders tend to ask many questions to understand clearly the scope and the solution.



The design begins after stakeholder buy-in. The designer will start with high-level wireframes and test the concepts with users to understand if they are in the right area to solve the problem. The designer will seek feedback and conduct a design review ceremony. Following this, the designer may take their wireframes to testing and start creating higher fidelity. The process of design, review, and testing may continue for a few rounds in order to get the design a bit fleshed out. The design language system is applied during the high fidelity stage. Occasionally a new element will arise from the solution that needs to go into the Design Language System


Sprint 0

The PO and UX on the product will seek an agile coach to do a sprint 0 for the product. The product is explained to the team in depth, stories are fleshed out and pointed, and  the design is explained. The team spends some time on working agreements and team building. Sprint 0 is demoed to stakeholder. The team begins their development work. The product owner and Ux designer spend 30% of their time with the developement team and 70% of their time getting thier next product ready.