I like the idea but I didn't find the article to be clear.
I feel like the last section was the most helpful but still very high level:
So how do we learn to recognise problems?
We learn to recognise problems by being exposed to many problems and understand these subproblems. Through these reflective cycles where we conceptualise based on our experience, we build concepts of problematic s.
Especially deep understanding of the underlying mechanisms that give cause to problems casts a wider net in recognising them, such as the calory intake and physical activity example for the dietician.
Recognising problems is essentially building new concepts by engaging directly in the situation. That’s why problem interviews or observing your customers are important ways of researching, they give you concrete experiences to reflect on and conceptualise problems.
Thanks for your feedback Josh, appreciated. I admit I struggled with getting the idea accross, or figuring out what the core idea is. I rate this article 6/10 or so, at best. Still, I wanted to get something out. So, I feel you. It is very high level. The issue is, that when describing something very abstract, such as learning, conclusions often will often be high level, because describing learning from a 3rd person perspective, gives this level. It's generic. Perhaps a next article, I could contextualise it more. Perhaps a difficult question, but what were you hoping to get out of this article?
I like the idea but I didn't find the article to be clear.
I feel like the last section was the most helpful but still very high level:
So how do we learn to recognise problems?
We learn to recognise problems by being exposed to many problems and understand these subproblems. Through these reflective cycles where we conceptualise based on our experience, we build concepts of problematic s.
Especially deep understanding of the underlying mechanisms that give cause to problems casts a wider net in recognising them, such as the calory intake and physical activity example for the dietician.
Recognising problems is essentially building new concepts by engaging directly in the situation. That’s why problem interviews or observing your customers are important ways of researching, they give you concrete experiences to reflect on and conceptualise problems.
Thanks for your feedback Josh, appreciated. I admit I struggled with getting the idea accross, or figuring out what the core idea is. I rate this article 6/10 or so, at best. Still, I wanted to get something out. So, I feel you. It is very high level. The issue is, that when describing something very abstract, such as learning, conclusions often will often be high level, because describing learning from a 3rd person perspective, gives this level. It's generic. Perhaps a next article, I could contextualise it more. Perhaps a difficult question, but what were you hoping to get out of this article?
I was hoping to get examples of how to learn to better recognize problems.
Have you checked out my previous articles:
https://iwantproductmarketfit.substack.com/p/customerproblemfit#details
and
https://iwantproductmarketfit.substack.com/p/problem-red-flags
I hadn't. Reading them now, thanks!