Design Terminology

From Critical Practice Chelsea
Jump to: navigation, search
A:
B:
C:
D:
E:
F:
G:
H:
I:
J:
K:
L:
M:
N:
O:
P:
Q:
R:
S:
T:

*Tame Problems: In the past, financial institutions have tended to solve problems through analytical methods, breaking things down into parts, fixing components, and assessing the probability of known sequences of failures leading to an accident or loss. In the new world, this type of problem is labelled as a tame problem, and tame problems tend to enjoy consensus. Everybody pretty much agrees to why something needs to be done and the right way to go about doing it. To solve a tame problem, we develop systems that gather all the data, then we analyze that data, formulate a solution, and finally implement the solution. Do not mistake tame for simple--some of these problems are extremely difficult to solve. Over the years IT systems have carried out the processes faster and faster, until today's systems achieve results in real time. However, there are still times when we fail and pretty dramatically at that. source (Also, see my notes on Chris Rust's talk on wicked problems here and the entry for "Wicked Problems" included below.)

U:
V:
W:

*Wicked Problem: "Wicked problem" is a phrase used in social planning to describe a problem that is difficult or impossible to solve because of incomplete, contradictory, and changing requirements that are often difficult to recognize. Moreover, because of complex interdependencies, the effort to solve one aspect of a wicked problem may reveal or create other problems. source
(Also, see my notes on Chris Rust's talk on wicked problems here and the entry for "Tame Problems" included above.)

X:
Y:
Z:

Return to Marsha's Resaerch Hub * Practice Literature * Threads and Quotes



Return to lexicons

comments:
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox