Ah. Presentations can really be annoying in those ways. You're already looking at outcomes, so to add to your analysis I'd focus on something more like an expe

Ah. Presentations can really be annoying in those ways. You're already looking at outcomes, so to add to your analysis I'd focus on something more like an experimental framework for yourself. Needed outcome tightly defined, test group, stimulus, response. That's a pretty good model for this stuff. Then you can start to hypothesize and try specific new things. Things that commenters here would just have no idea about because we're not there. Those are big. I would expect yourself to come up with at least 3-4 ways to rescue yourself from outcome #4 if that's what you're looking to do. At the same time I would recommend doing your best to focus on the advantages of group work (light touch, easy outcome) vs. one-on-one work (deep work, quality outcome). If they overlap too much it can get awkward and difficult--you can get that one person who it's really easy to talk to the whole time, or you can get the speaker/presenter reputation for being way too intense, trying to do training rather than presenting. Or trying to fix problems in person rather than let the audience go off and try breaking stuff themselves. Over time I'd expect you to document your suite of tools for this stuff and then write a bestseller. ;-) Anyway hope that helps some, good luck. BTW for tech groups specifically: 1) Engage their competence when you can; tell them what stumps or troubles you (relevant to topic) for example 2) Find those in the group who are looking to (hidden agenda) perform, and those who are looking to socialize, and help them do that for your benefit and 3) Study their shared sense of humor and play to it so you can take some pressure off yourself with their implicit permission.