A practical guide to identifying a problem worth solving — why problems beat solutions as a starting point, how to find genuine pain, assessing problem intensity and frequency, and where good problems come from.

seen from United Kingdom

seen from Vietnam

seen from United States
seen from United States
seen from United States

seen from China

seen from United States
seen from South Africa
seen from United States
seen from United States
seen from China

seen from France
seen from Malaysia

seen from Brazil

seen from United States

seen from United States
seen from Germany
seen from United States
seen from United States
seen from China
A practical guide to identifying a problem worth solving — why problems beat solutions as a starting point, how to find genuine pain, assessing problem intensity and frequency, and where good problems come from.
Solve Every Problem Twice - DZone Web Dev
Solve Every Problem Twice – DZone Web Dev
I recall initially studying about a similar concept in Joel Spolsky’s site, Joel on Application, in which he wrote back in 2007: Fix All the things Two Ways Just about each tech support problem has two solutions. The superficial and instant remedy is just to fix the customer’s problem. But when you assume a minor more challenging you can typically uncover a further answer: a way to avert this…
View On WordPress
Palmer (2007) developed the PRACTICE model of coaching which is an adaptation of Wasik’s (1984) seven-step sequence.
(D’Zurilla and Goldfried, 1971; D’Zurilla, 1986; D’Zurilla & Nezu, 1999). Wasik (1984) described a simple seven-step problem-solving model that has been applied to the fields of counseling, psychotherapy, management, coaching and training. This is the PRACTICE model. The steps are (Wasik, 1984):
Problem identification
Goal selection
Generation of alternatives
Consideration of consequences
Decision making
Implementation
Evaluation
Fixing problems is not always easy
Fixing problems is not always easy
“We cannot solve our problems with the same thinking we used when we created them.” ~Albert Einstein.
As Einstein’s quote put it so nicely, you have to change if you wish to fix any problem you face.
Given that information the answer to the following question should be easy. The most important part of any problem solving process is?
Admitting you are the problem.
Identifying solutions.
Id…
View On WordPress
Problem Identification of the theme or the broad area of research is the first and most important step in any research.
Problem Identification of the theme or the broad area of research is the first and most important step in any research.
Planning: Risk Management to Manage Uncertainty - #Ankaa
Planning: Risk Management to Manage Uncertainty Many organizations plan to create certainty, guarantees of some variety. What if we thought about Agile planning as a way to manage uncertainty? When I look at long roadmaps with all the "must-do" feature sets and the pressure managers put on teams to commit to delivery, I wonder... https://ankaa-pmo.com/planning-risk-management-to-manage-uncertainty/ #Agile #Iterations #Problem_Identification #Roadmap #Uncertainty #User_Feedback
Problem Identification
Purpose of Assignment
For this assignment, the Learning Team conducts basic research related to a business problem. This allows students to use critical thinking in their research to identify problems and discuss how to develop potential solutions. This will build a foundation for the rest of the Learning Team’s assignments.
Assignment Steps
Select a business situation such as reorganization,…
View On WordPress
Solving for Jobs to be Done vs. task usability
Struggles that people encounter while trying to make progress in their lives are customer struggles, or jobs they want done.
Struggles that customers face when they are trying to use the product or service they’ve chosen to help them make that progress are solution struggles or task usability problems.
“... usability only matters as much as our ability to solve their Job-to-be-done.”