"not exactly" as in "not quite but close to being"
Equivalent to "no, but"?
Take the question, "I jump over the cliff. Do I make it to the other side safely?"
How would you interpret these answers:
"no, but":
"yes, but":
"not exactly (i.e. not quite, but close)":
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
My answers (curious about yours):
"no, but" : "no, but you land on a rock outcropping six meters down the edge at the other side. "
Oracle: "not exactly"
Interpretation: "not quite but close. you only missed by an inch." (seems like a 'no' with some window dressing)
Now take the question: "Was he a professional boxer?
"no, but": "no, but he was a professional arm wrestler. "
"not exactly": "not quite but close. he won the amateur gold medal in the olympics. "
Is "no, but" more open ended than "not exactly"?
Couple of thoughts. First, maybe changing the angle/requirements of the question would help? Maybe, "don't ask if you make the jump, because you roll mechanics for that. Ask if you get across the chasm in one piece". (Inspired by a post on Task vs. Conflict resolution I read on lumpley's forum the other day).
ReplyDeleteThen you can say "yes", "no", or "not quite" and have a pretty good idea of where those go. Yes, you make it across the chasm. No, you fall in. Not quite, you're hanging from your fingertips. What are you going to do now?
The trick would be determining when to roll mechanics vs. when to ask the oracle, but that could be pretty simple -- roll mechanics when you have a mechanic to roll, roll oracle when you have a question not covered by the mechanics.
OK, here's another iteration, refining the idea further: "yes, but then it is negated.", "no, but then something makes it happen".
ReplyDeleteOr, "no, barely" and "yes, barely"
It's basically still no and yes but with some additional color.
no but you manage to survive clutching at the last moment to a providential shrub
ReplyDelete