How to Lead Your Audience to the Result You Want?

As product managers, we can’t succeed without others agreeing with our direction and doing their part. Meetings are an important tool in that mission. First, you need to prepare and understand what is the desired outcome of that meeting. But then comes the hard part - how to get everyone onboard? Here are some guidelines for how to run the meeting itself and get to the outcome you want.

In my last article I wrote about how to prepare for your meetings so that you make the most out of them. Even if you stop there, your meetings will be much more effective and it will be easier for you to get the outcome you are looking for.

However, there is another important part in unlocking the full potential of your meetings to work for you – and that’s, of course, what happens in the meeting itself. 

To get the results you want, you will need to lead your audience through three distinct phases. Each of them is important and relies on the previous ones (and the prep work you have done before the meeting) to be successful.

I want to make it super clear that although you have a specific outcome in mind, in most cases the best strategy is to start with listening, and not with stating your desired outcome right at the beginning of the meeting. You can start by stating the objective of the meeting, as in “today we are here to make the following decision”, but it’s usually not recommended to start with the outcome itself: “the right decision is X and I will show you why”.

Phase 1: Listen

If you have done your preparation right, you now know exactly what you are hoping to achieve from the meeting. It is usually about a decision to be made. In some cases, you will have a strict opinion about the right choice for this specific decision, and in others you just want the team to decide (on a certain strategy for example) so that people can move on (to implementing it in this case). As part of the preparation, ideally you would also have an idea of what others are hoping to achieve, the direction they want to drive the decision, and what they need to hear in order to get to the outcome you want. But you don’t know for sure, so now is the time to listen. 

Take for example a meeting with a large potential customer who is asking for a feature request as part of the deal. You talked to the relevant salesperson and understood the feature more or less. It makes sense, but you have more urgent things on your backlog. So in your prep for the meeting, you realized that you want to do this, but only in the next quarter. 

Now is the time to listen. There are two things you need to listen to: first, did you really understand the feature they need? Never assume you got it right until you talked directly to the customer. What you hear in these conversations makes a huge difference. And second, how urgent is it for them? You don’t need to ask it bluntly from the get go, but instead read between the lines of what they say and then find a hook that would allow you to ask if you got it right.

To be able to fully listen, you need to focus just on that, not on responding. For this part, it will serve you best to almost forget the outcome you wanted to get to, and truly listen in order to fully understand the other side. Ask clarifying questions and share with the room what you understood to make sure you got it right.

Phase 2: Look for a Win-Win Solution

Before responding, now is the time to reconsider your outcome and see if it still makes sense, given everything else you have heard so far. Note that we are not in the business of convincing people to do things that are not good for them, we are in the business of finding win-win solutions. So you want to make sure you are moving forward with a win-win approach in mind.

Ask yourself as objectively as you can, as if you were in the other person’s shoes, is this a good solution? If you think it is, move on to phase 3 below. But if you are not sure, you have some more work to do.

First, understand where the mismatch is. To continue the example from above, let’s say the customer explained that this feature plays a key role in their ability to get the value they want out of your product. If you simply go now to say “great, so you will have it in 6 months” it just doesn’t seem appropriate. You see the gap immediately.

But just seeing the gap won’t help you. To be able to move forward, you need to frame it for everyone to see it too. 

First, acknowledge what you have learned: “great, so I understand that you need this as part of the core process of your work with the product, right?”. This goes a long way for people to be able to accept any follow-up suggestions from you. If they feel you understand them fully, it’s easier for them to trust you that you are doing your best to help them get what they want, not just what you want.

Next, frame the gap – first to yourself and then to the other side. In our example, you no longer debate whether or not this feature is important. The only question is when can you deliver it. So say it out loud. There are nuances, but you can say something like “I believe I understand what you need and I agree that it is important. Let me ask a few more questions to better understand where I can fit it in”.

Assuming you still think, considering everything that you have learned during the meeting, that your predefined outcome is the right one, now you need to lead the other people to think so too. If you have come to realize that your predefined outcome is no longer the right one (it happens, we learn new things and want to be flexible and brave enough to be convinced otherwise with any decision we make), you now need to think what IS the right outcome, and still lead the other people to think so too. So anyway that’s what you need to do. That’s the trickiest part in the analysis, but here is what you should do: ask yourself what can potentially lead to the conclusion that your predefined outcome is the right one. For example, if you know the customer needs this feature on the first day they start using the system, you want to assess together with them when is that expected.

In our simple example, the crux of the matter is that they only need it when they will actually start using the product, and not when they sign the deal. In large enterprises that can be a very different timeline, and since you have gained their trust up until now by fully listening to them and showing them that you understand and respect their needs, there is a higher likelihood that they will be more flexible and willing to help uncover a win-win solution.

With that understanding in mind, you can say something like: “so ideally (without committing to anything, just thinking out loud) you want to have this feature ready as soon as you start using the product, right?”, and assuming they agree, you can go on and say “let’s try to understand when is that expected”.

If your case is more complex, and the first attempted solution doesn’t yield the desired results, you need to repeat this step again and again until you find something that is good enough for everyone. It’s not easy to do it in real-time in the meeting itself, but the more prepared you are the easier it is. 

To make it easier, you might want to add to your preparation a deeper understanding of your real boundaries. In our example, you can come prepared in advance with what is the nearest time you can deliver this feature if it comes to that. It doesn’t mean you are aiming for it, but this is the farthest you can go, so if they need it sooner you simply cannot do it.

Don’t be afraid to take a moment to think this through if you need to. You can say “let me organize my thoughts for a minute” and only then continue. Of course, you can’t take forever, but sometimes even a few seconds can make a difference. If you feel you have learned things that have completely changed how you see things, it is also fine to ask to stop the meeting, think it through, and come up with a suggestion separately.

Phase 3: Make a Suggestion

The last phase is where you are leading the discussion towards a decision or an agreement. In phase 2 you were able to close the gap (even if you had to repeat it over and over, agreeing on more and more things in the process, and making the gap smaller with each iteration). In this final phase, you need to summarize everything and make the final suggestion for everyone to agree on.

The last step of the preparation phase was to “pave the way” for your audience. This is the time to summarize it and update it based on what you have learned and agreed upon in the discussion so far. If you had the story already built before the meeting, it should be relatively easy to update in real-time and lead everyone to say yes.

This is an important step because it creates clarity. Even if everyone already feels what the right decision is (which is usually what happens if you worked properly in phase two), stating it clearly and getting everyone to say “I do” makes a huge difference. It allows people to hear it out loud (other than just in their own thoughts) and re-assess if they still think it’s a good idea, or if it’s a decision they can live with. It also helps in making sure (or increasing the chances) everyone understood it the same way, and creates clarity around the fact that an actual decision was made and it wasn’t just a brainstorming session.

That’s how the magic works. There’s a lot of work and thought behind it, but you can make it happen.


Our free e-book “Speed-Up the Journey to Product-Market Fit” — an executive’s guide to strategic product management is waiting for you

Share this post

Subscribe now with your preferred language​

Registration for the 11th

CPO Bootcamp

in now open!

Registration for the 11th

CPO Bootcamp

is now open!

A special earlybirds discount:

10% off

the early registration price,

until April 13th.