Changing the way we refer to things says a lot about our changing mindsets. For example, our organizations used to “train” people, now we “develop talent” through “blended learning experiences.” Companies that once employed “salespeople” responsible for closing deals, now have “business development teams” that form relationships with customers and clients.
Our changing descriptions of organizational roles and functions signify more than a gentrification of the way we talk about business. In the case of the interactions formerly known as “sales” and “training,” the change in language represents a shift from thinking in terms of transactions to thinking in terms of connections.
Once, we asked for coffee, received it and paid for it. Now we interact with a skilled and knowledgeable barista who assesses how much conversation will be required to meet our coffee needs, including the needs we didn’t realize we had: We can make your cappuccino frothier. Next time order it “dry.”
We no longer transact business. We connect services and solutions to wants and needs.
Our internal and external clients and customers no longer want our prefabricated widgets, our generic training programs, or our one-size-fits-all professional service methodologies. Even health care systems have started personalizing treatment plans to meet individual patient needs.
Sometimes, I have a very specific coffee order and I’m not interested in exploring my options. Similarly, sometimes, a client or customer simply wants to transact business with you. They know what they want and they’re looking for the best value. Before your scoping conversation, ask yourself (or even better, ask the client) about the importance of what Unstuck Minds calls, “The Four Imperatives.”
Find out the extent to which your client needs to…
Reduce the risk of missing something important
Avoid solving the wrong problem
Make it easier for people to take concerted action
Increase the novelty of their options
If the imperatives matter, you’ll want to walk into the scoping conversation with better questions. There are four primary questions that will change any scoping conversation from a business transaction into a conversation that connects services and solutions to needs:
What is changing? Start your scoping conversation with a question that demonstrates the importance of context. By the time you have been invited into a scoping conversation, your client has already decided that something needs to change or improve. To avoid being trapped by a discussion of the features and functions of your solutions, find out what has changed in the internal and external environment that triggered the scoping conversation. By asking. “What is changing?” you reduce the risk of missing something important.
What does it mean? After hearing about what is changing, find out how your client has interpreted the changes. Consider other explanations for the identified changes. Why has the client’s current interpretation of the changes become a priority? By finding out what the change means to your client you avoid solving the wrong problem.
How do others see it? You have heard one perspective on the context and rationale for the client’s stated need, now it’s time to find out about the thoughts and feelings of others in the organization. Be suspicious of a client who describes strong alignment on a consistent set of needs. The scoping conversation should include a discussion of what people may end up losing when the client’s needs are met, not just what people stand to gain. Finding out how others think and feel helps make it easier for people to take concerted action to meet the client’s requirements.
How else might we define the challenge? The client engaged you in a scoping conversation by framing a request. If you’ve had a productive dialogue prompted by the first three questions, it’s likely that new information and perhaps some new insights have emerged. In asking the fourth question, you are adding value to the conversation by broadening the solution set. You may even uncover needs that set the stage for future scoping conversations.