Problem Solving – A Framework

In my first post on principles, I had an entry regarding problem solving – specifically, guidance on defining problems.  That entry is actually a condensed version of something I have hanging in my cubicle at work:

20181018_154129~2

I printed the post from a Lifehacker article, and have since annotated it with a few extra ideas.  On the left, I stole a line from Tim Ferriss’s Tribe of Mentors to supplement the step for generating possible solutions to your problem.  The simplicity of the question, “what would this look like if it were easy?” allows me to limit the choice pool by excluding unlikely scenarios while thinking about the positive outcomes.

When it comes to evaluation consequences and narrowing down the options, I have added three additional tools.  First, I borrow again from Tim Ferriss where he uses “Fear Setting” to determine the worst case scenarios possible, and then he goes through each outcome and asks himself whether the cost is something that he could live with.  By doing so, he reframes his concerns away from merely worrying about negative outcomes to only focus on the things that matter to him.

I also added a note to myself to ensure I’m capturing my assumptions.  A lot of the time I start with my conclusions and assume they are transparent in their reasoning.  However, if I ask a series of clarifying questions (usually the 5-why technique), I often end up drilling down to hidden assumptions or emotions that motivate the conclusion (rather than pure reason).

The final note I scribbled is in reference to Enrico Fermi who had an uncanny knack making stunningly accurate “guesses” off the top of his head.  Fermi used probabilities and statistics to make educated guesses to solve problems, which could then be further refined.  It’s a tool for quick and dirty estimates, and it helps to narrow down the choice pool.

My annotations aim at four tools I can use to supplement Kranz’s method: what is the best/easiest solution, what’s the absolute worst case, how easily can we figure this out, and what motivations are driving my decisions.  I try to keep those considerations in mind, though I’m not nearly as rational as I pretend to be.

Stay Awesome,

Ryan

Advertisements

Principled Thinking (part two)

Since my last post on principles, I’ve jotted down a few more ideas in my notebook.  I’ve transcribed my thoughts under the photo below.

20181118_131600~2

6. Where appropriate, seek to reduce or limit choice pools.
a.) Too many choices is paralyzing.
b.) Extraneous choices impacts rank(ing) orders.
c.) Choice + paralysis  will cause decision friction –> procrastination, and inertia will  grind things to a halt.
d.) Time and resources get wasted in the decision process –> you trade off value.
e.) Most decisions can be whittled down by routine and quick preference (gut reaction) –> use 80/20.
f.) Invest time in deliberation for high stakes outcomes or decisions that interest you.
i.) Also invest when decision process is educative for you.

This entry largely captures what my behaviours are like when it comes to making decisions versus where I want them to be.  By nature, I’m a risk averse and indecisive person.  I tend to sit on decisions far too long, to the point where they can cause anxiety when it’s finally time for me to make the call.

I also tend to lack preferences in a lot of things.  For instance, I usually don’t have a strong preference when it comes to picking a place to eat, so I’m terrible at deciding where to go but I’m perfectly happy to go along with choices made by others.  There are many things I’m starkly black-and-white about (which is really annoying to my wife), but most of the time I sit in a middle state like Buridan’s ass.

Therefore, this set of principled notes captures where I want to be – to quickly narrow down extraneous choices (because too many options usually leads to diminished outcomes), and to automate where I can.  Then, I can focus on the really important decisions or use the deliberation process as a teaching tool for myself.

Stay Awesome,

Ryan