There once was a bearded, ungainly man, that the Oracle of Delphi called the wisest man in Athens. His name was Socrates, and he wasn’t happy with this accolade. ‘I know that I know nothing’ he declared, and he set about proving the Oracle wrong. While this did not make him popular – it led to his death – it did mark the birth of Socratic questioning. This approach focuses on asking critical, systematic questions to achieve a goal by way of a dialogue – in Socrates’ case, that he was aware of his own ignorance. We can learn from this approach in project management, too, in my opinion.
*What?*, I hear you say. Pull up a chair while I explain.
This approach dictates that we should not assume that we understand what our clients need – or that the client knows either. That understanding is achieved by asking questions, not answering them, through an ongoing dialogue. That we examine and challenge all assumptions, always asking why. That we dive beneath the surface, cultivate deeper understanding, assess the plausibility of things, and force all concerned to think. But I digress…
How does this work in practice?
In the example below, I’ve adapted this approach to project start up, when we ask what problem we are trying to solve for the client. Remember, you’re challenging the thoroughness and accuracy of the client’s thinking, so put your hard balls away and be patient.
1) Clarify the problem
Start nice and gently. Tone here is critical. Think Martin Bashir interviewing the People’s Princess.
Typical questions: What is the problem you are facing? Why do you think this is happening? What needs to be fixed? Why do you say that? Could you explain further?
Here are a few real world questions and answers to give a bit of context:
What is the problem you are facing? *Our online sales are very low*.
Why do you think your online sales are low? *Our website is not great and we think it puts people off*.
Could you explain further? *The Shopping Cart is very clunky. It takes several clicks to buy a product*.
And so on.
2) Challenging the assumptions
Now we probe the client’s assumptions by gently digging into the reasons behind their thinking, by not accepting it as a given, and by considering exceptions. Tone: think Pamela Stephenson, not Frazer Crane.
Typical questions: Why do you think these assumptions hold here? How do you know this to be true? Can you verify or validate your assumption? Are these the only explanations?
Real world examples: Why do you assume the shopping cart is the main barrier to online sales? Can you verify this? Is there any other explanation for low online sales?
3) Probing the evidence
Now we help the client set out their supporting evidence for the cause of the problem. This is cross-examined in a nice and friendly way. Tone: think Oprah, not Jeremy Kyle.
Typical questions: What tells you your assumption here is true? What evidence is there? Is there reason to doubt this evidence? What do you think caused this to happen? Has anyone else expressed a different opinion? Why do you think that is?
Real life examples: What tells you the Shopping Cart is the main problem? Does your customer feedback and data to support this? What caused the website to end up this way?
4) Establishing alternative viewpoints and perspectives
It’s time to look at other perspectives to show the client that there are equally valid viewpoints. Tone: think exploring the benefits of tidiness with your *creative* other half.
Typical questions: What is another way to look at it? What would be an alternative? Does this seem reasonable? What are the strengths and weaknesses of the perspective? How does *x* compare with *y*?
Real life examples: Could it be that your site is hard to find? Is your site as user-friendly as it ought to be? Is it mobile friendly? Did you have a marketing plan? Could that have contributed to low sales? Do any of these seem reasonable alternatives?
5) Implications and consequences
Now we probe the implications and consequences of the client’s assumption that we can forecast. Tone: think Kirsty Walk, not Paxman.
Typical questions: What generalisations can you make? What are the consequences of that assumption? Do these make sense? Are they desirable?
Real life example: If we fix the shopping cart what then? What are the implications of focussing on the shopping cart? How will this affect the rest of the site/sales? How does that fit with the alternatives we discussed?
6) Question the business problem
The home straight. Now you can also get a bit deep and turn the problem on its head.
Typical questions: Is this the real problem? Could there be other elements to the problem we need to consider? Does the problem go deeper than this? What should we do with the new information (the alternatives)?
Real life examples: Is the Shopping Cart the real problem here? Could there be other elements, such as a lack of web presence and poor user experience, which are contributing to the real problem? Could there be a deeper problem, such as the product strategy? What does this tell us about the approach to online sales?
And now the real dialogue can begin about the true nature of the problem based on a mutual understanding.
So, embrace your inner Socrates* and use this client-centred and inquiry-led approach to explore problems or issues, and to make decisions. It promotes collaboration, helps move clients toward their goals, and makes for a great customer experience.
The Humble PM
*The toga and beard are optional