# chrizbo comments on Double Crux — A Strategy for Resolving Disagreement - Less Wrong

61 29 November 2016 09:23PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Sort By: Best

You are viewing a single comment's thread.

Comment author: 30 November 2016 02:15:48AM *  7 points [-]

I'm excited to try this out in both strong and weak forms.

There are parallels of getting to the crux of something in design and product discovery research. It is called Why Laddering. I have used it when trying to understand the reasons behind a particular person's problem or need. If someone starts too specific it is a great way to step back from solutions they have preconceived before knowing the real problem (or if there is even one).

It also attempts to get to a higher level in a system of needs.

Are there ever times that the double crux have resulted in narrowing with each crux? Or do they generally become more general?

There is the reverse as well called How Laddering which tries to find solutions for more general problems.

It sounds like the 'reverse double crux' would be to find a new, common solution after a common crux has been found.

Comment author: 05 December 2016 07:12:22PM 2 points [-]

There are parallels of getting to the crux of something in design and product discovery research. It is called Why Laddering. I have used it when trying to understand the reasons behind a particular person's problem or need. If someone starts too specific it is a great way to step back from solutions they have preconceived before knowing the real problem (or if there is even one).

In programming, we call that The XY Problem.

Comment author: 06 December 2016 02:08:03PM 2 points [-]

I hadn't heard of that before. Thanks!

Comment author: 11 December 2016 07:20:25PM 0 points [-]

Nice association.

I see this model as building on Laddering or the XY problem, because it also looks for a method of falsifiability.

It's closer to a two-sided use of Eric Ries' Lean Startup (the more scientific version), where a crux = leap of faith assumption. I've called the LoFA a "leap of faith hypothesis", and your goal is to find the data that would tell you the assumption is wrong.

The other product design thinker with a similar approach is Tom Chi who uses a conjecture -> experiment -> actuals -> decision framework.

In all of these methods, the hard work/thinking is actually finding a crux and how to falsify it. Having an "opponent" to collaborate with may make us better at this.