deaconsune t1_j50opw9 wrote
I find that when I run events I end up creating notes for "next time" to iteratively improve. Events I run tend to be cyclical.
Do you organize information after an event from what you've learned, and if so, how do you incorporate what you learned from "last time"?
Have you experienced other stakeholders pushing back on changes that you are implementing because of your notes, but they think everything went fine?
kvlnkyl OP t1_j50ud57 wrote
If there are difficulties with implementing such things or ideas, you need to explain to the right people why they should listen to you. To do this, you need to demonstrate the value of your idea. Here are some steps to consider:
- Confirm your opinion with a post survey of participants - Ask people who have already experienced your idea or have used it in a similar way what they think. This will give you an indication of whether your idea is viable and worth pursuing.
- Validate your opinion on a subreddit or in a slack - Posting on subreddits and slacks can give you an additional perspective from people who may not be familiar with your idea or the industry it applies to. Their feedback can help you understand if any changes or modifications need to be made before implementation.
- If possible, calculate your idea and the profit from its implementation - Crunch the numbers and determine how much money implementing your idea could make and how it could benefit the company financially. This will make it easier to show the value of your idea and convince others that it's worth pursuing.
If necessary, I can share the event planning checklist I use for process. This will help ensure that all aspects are taken into consideration before making a final decision about implementation.
deaconsune t1_j51pmw8 wrote
Good points all around.
I'm sure that not only myself would be interested in your planning checklist if you're willing to post it.
Thanks for the ideas.
Viewing a single comment thread. View all comments