3 ms·
For me, the more prepared I am, the more comfortable I am. Going over what I’m going to say, out loud, so I can fix any wording I might get tripped up on, as we
by al_borland 2y ago
For me, the more prepared I am, the more comfortable I am. Going over what I’m going to say, out loud, so I can fix any wording I might get tripped up on, as well as thinking about questions that might come up. I’ll either proactively answer them as part of the talk or at least have an idea of how I will answer them.
If you have someone you can present to that can give honest feedback, that is also helpful. We used to do this internally on my team before our sprint reviews/demos and it helped a lot. Half the time someone would finish up and we had no idea what they were talking about, so we would talk about ways to adjust the message to make it more meaningful.
To go right along with that, I’d say to keep your audience in mind. Who are you talking to? What do they care about? I might write some code that I think is really cool, but no one cares, and I need to accept that. The person I’m presenting to is going to know how what I did can help them and how to use it. They don’t usually care how the sausage is made. In some cases I’ve prepared for a few options, and if the audience is small enough, I ask them how deep they want to dive and adjust accordingly. Finding that sweet spot, where it seems like people will actually care about what is being said helps to put me at ease, as I’m less worried about boring them (if it’s too high level), or seeing their eyes glaze over (if it’s too technical).