Software Engineering, Project Management, and Effectiveness
I showed a colleague of mine one of my tricks for building slide decks faster. It's a divide and conquer approach I've been using a few years. I do what I call "one-sliders."
Whenever I build a deck, such as for milestone meetings, I create a set of single-slide decks. I name each slide appropriately (vision, scope, budget, ... etc.) I then compose the master deck from the slides.
Here's the benefits that might not be obvious:
The biggest impact though is that now I find myself frequently sharing concise one-sliders, and getting points across faster and simpler than blobby mails.
I may try this approach - I usually end up with 'repository' decks around key topics with many slides I've found re-usable and 'fish and stitch' the right slides for te right audience. It's worked out well.
I think the key, just in source code reuse, is to add slides to the 'reusable' collection once you've actually reused them in a couple of occasions.
Otherwise you may end up creating many YAGNI slides.
I think presentation decks are over- & mis-used a lot in large organizations but they don't seem like they 'll go away anytime soon... so we might as well get effective about managing them.