“take a step back” is also the right thing to say in a lot of situations; it's very easy for people to get lost in the details of one proposed solution instead of deciding which solution is best or even what the exact goal is.
Half of those tips occur in most hour long meetings I already attend. When a participant in the meeting uses one of those techniques all I think is: wow, in no way did you just contribute to this discussion.
> When a participant in the meeting uses one of those techniques all I think is: wow, in no way did you just contribute to this discussion.
The problem with this statement is that you're assuming everybody's as smart at spotting bullshitters and manipulators as you. What if only 20% of people in the room noticed what they were doing and the other 80% thought they were a genius?
This is often the case and it's why strictly rational people are playing an irrationally weak hand.
Thing is, some of these are genuinely useful and smart things, in very specific contexts :P
To paraphrase a recent experience of my own, a manager calling a meeting with the dev team "we need to re-arrange the javascript in our headers" "step back a bit, what problem are we trying to solve?" "pages need to load faster, rearranging headers makes pages load faster" "step back a bit, why do they need to load faster? Why is javascript the problem?" "Clients have complained about graphs not loading" checks the server logs, sees internal server errors causing pages to crash (those which don't crash on the server side are loading instantly), goes to fix the actual problem
>3. Encourage everyone to “take a step back”
This one is the best cause it is so damn effective at getting everyone to pay attention to you without you having to say anything of substance.
>8. Ask the presenter to go back a slide
Because clearly the presenter doesn't know enough to give you the most pertinent information on their own slides.