Jagadeesh P. explains why over 60% of designers struggle with problem statements, which are usually too broad or too narrow and missing user context. He shows how to frame one properly, claiming it can make projects at least 2x faster.
Questions this video answers
More than 60%.
At least 2x faster.
More than 60% of the designers are very much struggling in choosing the right problem statement for their project. More importantly, even if they choose it, they are still not clear whether it is correct or not. They don't know how to define it. They don't know how to convince their stakeholders and boss and other people to do it. Can I tell you, problem statements are always too broad for the people or maybe they are too narrow. It is very very difficult for anybody to really start that people use lot of assumptions instead of getting a proper validated fact and insight. They are writing statements without a proper context and a user Persona well defined. They are not focusing towards a solution within that question. They are too much broadening the game. They are not testing out this with a real time user. In this video I am going to be telling about what exactly a problem statement should look like and how to exactly frame it in a proper way. This will increase your project speed at least 2x faster if you start your project right. Let's jump in.