SYSTEM NOTICE

Auto translation by AI. Be sure, accuracy, nuances and authorial intent may not be fully reflected.
見出し画像

[Exploring Effective Presentations] Why Your Presentation Fails Despite Being Logically Sound | The Concept of Inception-Style Presentations

What you will learn in this article

  • Why even logically sound presentations sometimes fail

  • What you should really be designing in a presentation

  • What is 'terrain design' that allows the answer to naturally emerge within the audience

| A presentation is not an explanation, but terrain design

You are giving a presentation, and you are sure you are making a logical argument, yet it doesn't get through.
You have the evidence. You have the numbers. The logic is sound.
Even so, the audience doesn't move, and sometimes they even respond with doubt or resistance.

Situations like this are surprisingly common.
And in many cases, the speaker thinks, 'I didn't explain enough,' and tries to add even more information.

However, the problem occurring there is not necessarily a lack of explanation.
Rather,
the more you pile up correctness, the more doubt or resistance can be born within the audience instead of conviction.

Presentations are often thought of as a technique for explaining things clearly.
That is why many people add information, line up evidence, and try to speak carefully to avoid any misunderstandings.

But in reality, just because you have explained everything does not mean the audience will move.
What is important is not just what you say, but the order in which the audience sees things, and where they can think, 'That makes sense.'
It is about arranging the path to that conclusion.

| Why doesn't it get through even when you explain it properly?

The reason it doesn't get through even when you explain it is not necessarily because the explanation is insufficient.
In many cases, what is lacking is not information, but the order in which the audience can make a judgment.

People do not just receive information as it is and act on it.
They view the content through their own position, experience, interests, and existing criteria for judgment.
Therefore, no matter how correct the content is, if it does not align with the perspective the audience is looking from, it will not reach them with the meaning you intended.

That is where the spinning wheels of explanation occur.
The speaker feels, 'They haven't understood yet,' and adds more explanation.
But the more information there is, the more the audience senses the number of points and the pressure, making them more likely to harbor doubt or resistance before conviction.

In other words,
the cause of it not getting through is not so much the correctness of the content itself, but the failure to design the position from which the audience receives it.

What is needed in a presentation is not to say everything that is correct.
It is to arrange a path that allows the audience to move forward without strain.

The ideal is not to convince the audience after you have finished explaining.
It is for the answer to emerge in the audience's eyes before you explain it.
When you can create that state, a presentation becomes something that supports the audience's decision-making, rather than just an explanation.

People want to be 'convinced,' but they do not want to be 'persuaded.'
That is precisely why pushing correctness can sometimes create resistance instead.

| What you should design in a presentation is the 'path to the conclusion' rather than the 'content'

When people think of presentations, they tend to think it is about organizing 'what to say.'
Of course, the content is important.
However, even with the same content, the way it is received and the decision-making process change significantly just by changing the order in which it is presented.

This is because the audience is not receiving the information all at once.
The audience understands in the order in which things appear before them, gets stuck along the way, and stops to judge if necessary.
In other words, rather than the content itself, the order in which you show things is actually more effective.

For example, when you want to get a new proposal approved, a common approach is to lead with the conclusion.

"We should implement this measure. The market size is this, our company's strengths are that, and therefore it is worth doing."

At first glance, this seems rational.
However, the moment the other party is confronted with a conclusion, they are prone to adopting a "for or against" stance.
In that state, subsequent information is easily perceived not as something to be shared, but as material to solidify their agreement or disagreement.

Conversely, there is also a way to align the landscape that should be shared first.

“Right now, this kind of inconvenience is happening on the front lines, isn't it?
If this could be resolved, the way we make decisions and act would change significantly.
As a measure that can satisfy that condition, we have this.”

With this order, the conclusion is not something forced upon them, but something that naturally appears as an extension of the landscape.

What you really need to design in a presentation is not the strength of your argument.
Where the other party does not get stuck, where they can think "that makes sense," and at what point the conclusion emerges.

It is about how they arrive there.

| What to change first in practice is not "what to add," but "what to show first"

When a presentation doesn't go well, many people think, "I didn't explain enough."
However, what should be reviewed first in practice is the order, not the amount of information.
Rather than what to add, what you show first has a stronger effect on the other party's judgment.

There are three major things that should be changed first.

The first is not to push the conclusion too abruptly.
The conclusion itself is not bad.
However, if you strongly present a conclusion before the other party's premises are set, they are prone to adopting a stance of agreement or disagreement before understanding.
Then, the subsequent explanation becomes a battle rather than a sharing of information.

The second is to align the "landscape that should be shared" first.
Facts, background, constraints, and axes of comparison.
Just by creating a state where the other party can see the same landscape, subsequent judgments become much less likely to waver.
Instead of making them swallow the conclusion first, prepare the landscape where the conclusion becomes visible first.
That order is more reasonable.

The third is to be conscious of "where the other party is judging from" for every slide and every paragraph.
The speaker knows the big picture, but the other party can only judge based on the material they see right now.
That is why you need to structure the path while imagining whether the other party will be confused, convinced, or wary at this very moment.

Improving a presentation is not about making the materials thicker.
It is about organizing the order in which the answer can be seen reasonably in the other party's mind.

| A presentation is about organizing the path to seeing the answer

What you really need to design in a presentation is not the content of the talk itself.
The order in which the other party encounters information, where they do not get stuck, and the moment they can think "that's how it is."
That flow is what is important.

What is needed in a presentation is not to increase the number of points.
It is to reduce the places where the other party stumbles, clear away the fog of mismatched premises, and organize the path to seeing the answer.

Instead of forcing a conclusion, create a state where the answer emerges in the other party's eyes before you finish explaining.
What is necessary for that is to organize the path of judgment.

I think of this way of presenting as "terrain design" here.
And I would like to call a presentation where the answer naturally emerges within the other party through terrain design,
"Inception-style presentation."

It is not a technique to defeat the other party.
It is a design that supports decision-making toward the goal in a form where the other party can be convinced on their own and feel they have arrived there themselves.

A presentation is not an explanation, but a design of the terrain that allows the audience to reach the goal on their own.

When you try to refine a presentation as a technique for explanation, your focus inevitably turns to 'what to add'.
However, what truly works may not be increasing information, but organizing the path so that the answer becomes visible to the audience.

Instead of convincing them after you have finished explaining, the answer should begin to emerge in their minds before you even explain it.

When you can create such a state, a presentation becomes not just a transmission of information, but a design that supports decision-making.

Summary of this article

  • What you really need to design in a presentation is not the content itself.

  • It is important to consider the order in which the audience encounters information, where they won't get stuck, and at what moment they will think, 'That makes sense.'

  • Reducing the places where they might stumble is more important than increasing the number of points.

  • A presentation is not an act of forcing an answer upon someone, but an act of organizing a path where the answer naturally comes into view.

  • Here, we call this kind of design 'terrain design'.

  • And we define a presentation where the answer naturally arises within the audience as an 'Inception Presentation'.

いいなと思ったら応援しよう!