What does it mean that Wicked Problems have no Stopping Rule?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
4
down vote
favorite
I'm studying Design. One of the concepts is Wicked Problems.
I don't understand, re: Wicked Problems: No Stopping Rule
I looked up further and found:
" You can tell when you’ve reached a solution with an ordinary problem. With a wicked problem, the search for solutions never stops."
Does that mean you don't know before you actually IMPLEMENT the solution?
(I.e., we don't know if the rocket will make it to the moon unless we launch it) or that we don't know even AFTER we implement it.
And if we continue searching AFTER we deploy the solution and test, why do we keep searching?
Are we always looking for a better solution?
wicked-problem
add a comment |Â
up vote
4
down vote
favorite
I'm studying Design. One of the concepts is Wicked Problems.
I don't understand, re: Wicked Problems: No Stopping Rule
I looked up further and found:
" You can tell when you’ve reached a solution with an ordinary problem. With a wicked problem, the search for solutions never stops."
Does that mean you don't know before you actually IMPLEMENT the solution?
(I.e., we don't know if the rocket will make it to the moon unless we launch it) or that we don't know even AFTER we implement it.
And if we continue searching AFTER we deploy the solution and test, why do we keep searching?
Are we always looking for a better solution?
wicked-problem
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I'm studying Design. One of the concepts is Wicked Problems.
I don't understand, re: Wicked Problems: No Stopping Rule
I looked up further and found:
" You can tell when you’ve reached a solution with an ordinary problem. With a wicked problem, the search for solutions never stops."
Does that mean you don't know before you actually IMPLEMENT the solution?
(I.e., we don't know if the rocket will make it to the moon unless we launch it) or that we don't know even AFTER we implement it.
And if we continue searching AFTER we deploy the solution and test, why do we keep searching?
Are we always looking for a better solution?
wicked-problem
I'm studying Design. One of the concepts is Wicked Problems.
I don't understand, re: Wicked Problems: No Stopping Rule
I looked up further and found:
" You can tell when you’ve reached a solution with an ordinary problem. With a wicked problem, the search for solutions never stops."
Does that mean you don't know before you actually IMPLEMENT the solution?
(I.e., we don't know if the rocket will make it to the moon unless we launch it) or that we don't know even AFTER we implement it.
And if we continue searching AFTER we deploy the solution and test, why do we keep searching?
Are we always looking for a better solution?
wicked-problem
wicked-problem
asked 9 hours ago
Clay Nichols
670718
670718
add a comment |Â
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
1
down vote
10 Characteristics of Wicked Problems
A wicked problem is a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize.
So what defines a wicked problem? Horst Rittel (1930-1990), a design
theorist and university professor, first coined the term “wicked
problem†in ‘Dilemmas in a General Theory of Planning’ (1973). In the
paper, Rittel details ten characteristics that describe a wicked
problem:
- There is no definitive formula for a wicked problem.
- Wicked problems have no stopping rule, as in there’s no way to know your solution is final.
- Solutions to wicked problems are not true-or-false, they can only be good-or-bad.
- There is no immediate test of a solution to a wicked problem.
- Every solution to a wicked problem is a "one-shot operation"; because there is no opportunity to learn by trial-and-error, every attempt counts significantly.
- Wicked problems do not have a set number of potential solutions.
- Every wicked problem is essentially unique.
- Every wicked problem can be considered to be a symptom of another problem.
- There is always more than one explanation for a wicked problem because the explanations vary greatly depending on the individual perspective.
- The planner/designer has no right to be wrong and must be fully responsible for their actions.
add a comment |Â
up vote
1
down vote
A "Stopping Rule" is a mechanism for deciding whether to continue or stop a process on the basis of the present position and past events, and which will almost always lead to a decision to stop at some finite time.
The most obvious example I can think of would be the winning condition for a card game. In the game "snap", the game continues until only one player has cards left in their hand.
In design, you may encounter a problem that no one really understands all the requirements for. In attempting to create a solution you will continue to encounter more problems to solve, and uncover things that others did not yet think about, or have conflicting requirements for. This is a common problem in software engineering, and is why many large IT projects overrun on time and budget (and are often considered to have failed).
add a comment |Â
up vote
0
down vote
Based on the definitions provided, the reason why a wicked problem has no stopping rule is because typically you can apply a stopping rule to a problem because there an acceptable or optimal solution exists which allows you to come to a point where there is no need to continue searching or iterating on a better solution.
I guess it means that you don't really know whether you are dealing with a wicked problem, but you will know if you are not dealing with a wicked problem because you will have found a solution for it. The problem is that sometimes it is difficult to tell if the lack of a clear solution is because you haven't solved for the problem correctly or if it is just a wicked problem that you are dealing with.
If you feel like the problem that you are solving seems to be a symptom of another problem, and that there might be a catch-22 or some circular relationship it might give you a hint that you are dealing with a wicked problem. Other times you might be just lacking an important piece of information and therefore was not able to factor it into your solution.
A typical wicked problem involves behavioural design involving people where there is resistance or adaptation to change. For example, if you created a solution to a behavioural problem and find that the user group simply evolves their behaviour to create another problem, and you find that each new solution gives rise to a new problem then you are potentially dealing with a wicked problem. However, it could also be that you haven't necessarily addressed the root cause of the behavioural problem, or that it is subject to random or unpredictable forces which means you are unable to work out how to factor it into the solution.
Nevertheless, it doesn't stop people from trying to solve such problems because as I mentioned before, you don't always know when you are dealing with a wicked problem, and it is human nature to keep trying while they think it is worth the time and effort (or sometimes because they have already invested so much time and effort).
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
10 Characteristics of Wicked Problems
A wicked problem is a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize.
So what defines a wicked problem? Horst Rittel (1930-1990), a design
theorist and university professor, first coined the term “wicked
problem†in ‘Dilemmas in a General Theory of Planning’ (1973). In the
paper, Rittel details ten characteristics that describe a wicked
problem:
- There is no definitive formula for a wicked problem.
- Wicked problems have no stopping rule, as in there’s no way to know your solution is final.
- Solutions to wicked problems are not true-or-false, they can only be good-or-bad.
- There is no immediate test of a solution to a wicked problem.
- Every solution to a wicked problem is a "one-shot operation"; because there is no opportunity to learn by trial-and-error, every attempt counts significantly.
- Wicked problems do not have a set number of potential solutions.
- Every wicked problem is essentially unique.
- Every wicked problem can be considered to be a symptom of another problem.
- There is always more than one explanation for a wicked problem because the explanations vary greatly depending on the individual perspective.
- The planner/designer has no right to be wrong and must be fully responsible for their actions.
add a comment |Â
up vote
1
down vote
10 Characteristics of Wicked Problems
A wicked problem is a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize.
So what defines a wicked problem? Horst Rittel (1930-1990), a design
theorist and university professor, first coined the term “wicked
problem†in ‘Dilemmas in a General Theory of Planning’ (1973). In the
paper, Rittel details ten characteristics that describe a wicked
problem:
- There is no definitive formula for a wicked problem.
- Wicked problems have no stopping rule, as in there’s no way to know your solution is final.
- Solutions to wicked problems are not true-or-false, they can only be good-or-bad.
- There is no immediate test of a solution to a wicked problem.
- Every solution to a wicked problem is a "one-shot operation"; because there is no opportunity to learn by trial-and-error, every attempt counts significantly.
- Wicked problems do not have a set number of potential solutions.
- Every wicked problem is essentially unique.
- Every wicked problem can be considered to be a symptom of another problem.
- There is always more than one explanation for a wicked problem because the explanations vary greatly depending on the individual perspective.
- The planner/designer has no right to be wrong and must be fully responsible for their actions.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
10 Characteristics of Wicked Problems
A wicked problem is a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize.
So what defines a wicked problem? Horst Rittel (1930-1990), a design
theorist and university professor, first coined the term “wicked
problem†in ‘Dilemmas in a General Theory of Planning’ (1973). In the
paper, Rittel details ten characteristics that describe a wicked
problem:
- There is no definitive formula for a wicked problem.
- Wicked problems have no stopping rule, as in there’s no way to know your solution is final.
- Solutions to wicked problems are not true-or-false, they can only be good-or-bad.
- There is no immediate test of a solution to a wicked problem.
- Every solution to a wicked problem is a "one-shot operation"; because there is no opportunity to learn by trial-and-error, every attempt counts significantly.
- Wicked problems do not have a set number of potential solutions.
- Every wicked problem is essentially unique.
- Every wicked problem can be considered to be a symptom of another problem.
- There is always more than one explanation for a wicked problem because the explanations vary greatly depending on the individual perspective.
- The planner/designer has no right to be wrong and must be fully responsible for their actions.
10 Characteristics of Wicked Problems
A wicked problem is a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize.
So what defines a wicked problem? Horst Rittel (1930-1990), a design
theorist and university professor, first coined the term “wicked
problem†in ‘Dilemmas in a General Theory of Planning’ (1973). In the
paper, Rittel details ten characteristics that describe a wicked
problem:
- There is no definitive formula for a wicked problem.
- Wicked problems have no stopping rule, as in there’s no way to know your solution is final.
- Solutions to wicked problems are not true-or-false, they can only be good-or-bad.
- There is no immediate test of a solution to a wicked problem.
- Every solution to a wicked problem is a "one-shot operation"; because there is no opportunity to learn by trial-and-error, every attempt counts significantly.
- Wicked problems do not have a set number of potential solutions.
- Every wicked problem is essentially unique.
- Every wicked problem can be considered to be a symptom of another problem.
- There is always more than one explanation for a wicked problem because the explanations vary greatly depending on the individual perspective.
- The planner/designer has no right to be wrong and must be fully responsible for their actions.
answered 3 hours ago


Invariant Change
12410
12410
add a comment |Â
add a comment |Â
up vote
1
down vote
A "Stopping Rule" is a mechanism for deciding whether to continue or stop a process on the basis of the present position and past events, and which will almost always lead to a decision to stop at some finite time.
The most obvious example I can think of would be the winning condition for a card game. In the game "snap", the game continues until only one player has cards left in their hand.
In design, you may encounter a problem that no one really understands all the requirements for. In attempting to create a solution you will continue to encounter more problems to solve, and uncover things that others did not yet think about, or have conflicting requirements for. This is a common problem in software engineering, and is why many large IT projects overrun on time and budget (and are often considered to have failed).
add a comment |Â
up vote
1
down vote
A "Stopping Rule" is a mechanism for deciding whether to continue or stop a process on the basis of the present position and past events, and which will almost always lead to a decision to stop at some finite time.
The most obvious example I can think of would be the winning condition for a card game. In the game "snap", the game continues until only one player has cards left in their hand.
In design, you may encounter a problem that no one really understands all the requirements for. In attempting to create a solution you will continue to encounter more problems to solve, and uncover things that others did not yet think about, or have conflicting requirements for. This is a common problem in software engineering, and is why many large IT projects overrun on time and budget (and are often considered to have failed).
add a comment |Â
up vote
1
down vote
up vote
1
down vote
A "Stopping Rule" is a mechanism for deciding whether to continue or stop a process on the basis of the present position and past events, and which will almost always lead to a decision to stop at some finite time.
The most obvious example I can think of would be the winning condition for a card game. In the game "snap", the game continues until only one player has cards left in their hand.
In design, you may encounter a problem that no one really understands all the requirements for. In attempting to create a solution you will continue to encounter more problems to solve, and uncover things that others did not yet think about, or have conflicting requirements for. This is a common problem in software engineering, and is why many large IT projects overrun on time and budget (and are often considered to have failed).
A "Stopping Rule" is a mechanism for deciding whether to continue or stop a process on the basis of the present position and past events, and which will almost always lead to a decision to stop at some finite time.
The most obvious example I can think of would be the winning condition for a card game. In the game "snap", the game continues until only one player has cards left in their hand.
In design, you may encounter a problem that no one really understands all the requirements for. In attempting to create a solution you will continue to encounter more problems to solve, and uncover things that others did not yet think about, or have conflicting requirements for. This is a common problem in software engineering, and is why many large IT projects overrun on time and budget (and are often considered to have failed).
edited 1 hour ago
answered 1 hour ago
Franchesca
10.8k21632
10.8k21632
add a comment |Â
add a comment |Â
up vote
0
down vote
Based on the definitions provided, the reason why a wicked problem has no stopping rule is because typically you can apply a stopping rule to a problem because there an acceptable or optimal solution exists which allows you to come to a point where there is no need to continue searching or iterating on a better solution.
I guess it means that you don't really know whether you are dealing with a wicked problem, but you will know if you are not dealing with a wicked problem because you will have found a solution for it. The problem is that sometimes it is difficult to tell if the lack of a clear solution is because you haven't solved for the problem correctly or if it is just a wicked problem that you are dealing with.
If you feel like the problem that you are solving seems to be a symptom of another problem, and that there might be a catch-22 or some circular relationship it might give you a hint that you are dealing with a wicked problem. Other times you might be just lacking an important piece of information and therefore was not able to factor it into your solution.
A typical wicked problem involves behavioural design involving people where there is resistance or adaptation to change. For example, if you created a solution to a behavioural problem and find that the user group simply evolves their behaviour to create another problem, and you find that each new solution gives rise to a new problem then you are potentially dealing with a wicked problem. However, it could also be that you haven't necessarily addressed the root cause of the behavioural problem, or that it is subject to random or unpredictable forces which means you are unable to work out how to factor it into the solution.
Nevertheless, it doesn't stop people from trying to solve such problems because as I mentioned before, you don't always know when you are dealing with a wicked problem, and it is human nature to keep trying while they think it is worth the time and effort (or sometimes because they have already invested so much time and effort).
add a comment |Â
up vote
0
down vote
Based on the definitions provided, the reason why a wicked problem has no stopping rule is because typically you can apply a stopping rule to a problem because there an acceptable or optimal solution exists which allows you to come to a point where there is no need to continue searching or iterating on a better solution.
I guess it means that you don't really know whether you are dealing with a wicked problem, but you will know if you are not dealing with a wicked problem because you will have found a solution for it. The problem is that sometimes it is difficult to tell if the lack of a clear solution is because you haven't solved for the problem correctly or if it is just a wicked problem that you are dealing with.
If you feel like the problem that you are solving seems to be a symptom of another problem, and that there might be a catch-22 or some circular relationship it might give you a hint that you are dealing with a wicked problem. Other times you might be just lacking an important piece of information and therefore was not able to factor it into your solution.
A typical wicked problem involves behavioural design involving people where there is resistance or adaptation to change. For example, if you created a solution to a behavioural problem and find that the user group simply evolves their behaviour to create another problem, and you find that each new solution gives rise to a new problem then you are potentially dealing with a wicked problem. However, it could also be that you haven't necessarily addressed the root cause of the behavioural problem, or that it is subject to random or unpredictable forces which means you are unable to work out how to factor it into the solution.
Nevertheless, it doesn't stop people from trying to solve such problems because as I mentioned before, you don't always know when you are dealing with a wicked problem, and it is human nature to keep trying while they think it is worth the time and effort (or sometimes because they have already invested so much time and effort).
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Based on the definitions provided, the reason why a wicked problem has no stopping rule is because typically you can apply a stopping rule to a problem because there an acceptable or optimal solution exists which allows you to come to a point where there is no need to continue searching or iterating on a better solution.
I guess it means that you don't really know whether you are dealing with a wicked problem, but you will know if you are not dealing with a wicked problem because you will have found a solution for it. The problem is that sometimes it is difficult to tell if the lack of a clear solution is because you haven't solved for the problem correctly or if it is just a wicked problem that you are dealing with.
If you feel like the problem that you are solving seems to be a symptom of another problem, and that there might be a catch-22 or some circular relationship it might give you a hint that you are dealing with a wicked problem. Other times you might be just lacking an important piece of information and therefore was not able to factor it into your solution.
A typical wicked problem involves behavioural design involving people where there is resistance or adaptation to change. For example, if you created a solution to a behavioural problem and find that the user group simply evolves their behaviour to create another problem, and you find that each new solution gives rise to a new problem then you are potentially dealing with a wicked problem. However, it could also be that you haven't necessarily addressed the root cause of the behavioural problem, or that it is subject to random or unpredictable forces which means you are unable to work out how to factor it into the solution.
Nevertheless, it doesn't stop people from trying to solve such problems because as I mentioned before, you don't always know when you are dealing with a wicked problem, and it is human nature to keep trying while they think it is worth the time and effort (or sometimes because they have already invested so much time and effort).
Based on the definitions provided, the reason why a wicked problem has no stopping rule is because typically you can apply a stopping rule to a problem because there an acceptable or optimal solution exists which allows you to come to a point where there is no need to continue searching or iterating on a better solution.
I guess it means that you don't really know whether you are dealing with a wicked problem, but you will know if you are not dealing with a wicked problem because you will have found a solution for it. The problem is that sometimes it is difficult to tell if the lack of a clear solution is because you haven't solved for the problem correctly or if it is just a wicked problem that you are dealing with.
If you feel like the problem that you are solving seems to be a symptom of another problem, and that there might be a catch-22 or some circular relationship it might give you a hint that you are dealing with a wicked problem. Other times you might be just lacking an important piece of information and therefore was not able to factor it into your solution.
A typical wicked problem involves behavioural design involving people where there is resistance or adaptation to change. For example, if you created a solution to a behavioural problem and find that the user group simply evolves their behaviour to create another problem, and you find that each new solution gives rise to a new problem then you are potentially dealing with a wicked problem. However, it could also be that you haven't necessarily addressed the root cause of the behavioural problem, or that it is subject to random or unpredictable forces which means you are unable to work out how to factor it into the solution.
Nevertheless, it doesn't stop people from trying to solve such problems because as I mentioned before, you don't always know when you are dealing with a wicked problem, and it is human nature to keep trying while they think it is worth the time and effort (or sometimes because they have already invested so much time and effort).
answered 3 mins ago
Michael Lai♦
13.7k1058134
13.7k1058134
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f121247%2fwhat-does-it-mean-that-wicked-problems-have-no-stopping-rule%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password