Thread by @sambhigham

As Product People we want to ALWAYS start with the problem.

In reality, sometimes, that's not possible.

Sometimes you have to find 'the why' on 'the way'.

How? 👇 (1/6)

It's obvious to most outside of the perfect product environment, that there is a need for compromise when it comes to how stuff gets done.

If you always push back with a 'why' or a 'what's the outcome' you can find yourself removed from the conversations entirely...(2/6)

So, what can you do about it?

Find 'the why' on 'the way'

Instead of immediately pushing back (and you'll know when this is or isn't the right thing to do) take the request/demand and run with it.

Then... it's time to try and circle back to 'the why'...(3/6)

The person has demanded we do 'X'.

Logically, we need to try and deconstruct what 'X' is trying to achieve, for who, and why.

Tip: I reverse engineer using Outcome Solution Trees (@ttorres) (4/6)

Once you can relate back to an outcome, you can start to figure out if what's the best way to provide it.

So when you are completing the Discovery for the 'X' they demanded, you can also highlight options 'Y' and 'Z' which be a better way to get there. (5/6)

You'll need to play this back in a way that makes them feel smart for making the right decision.

But ultimately you win because you've avoided diving straight into a solution...

And you've educated them (just a bit) on thinking more broadly about what they might want. (6/6)