Host Q&A sessions to address potential problems early #11
Labels
developers
Involves interaction with your developers in some shape or form
optional
Would certainly help, but isn't essential
Milestone
Yes, I always include time for Q&A in my workshops. And that's great for any questions that people have immediately. But that's not enough. Because when people start putting your change into action themselves, that's when a lot of questions come up. And if you want to keep that early adopter momentum going, offering Q&A sessions to address those questions can be beneficial.
I like to schedule them slightly after the first round of workshops but not too far into the future.1 To avoid awkward silence in these sessions, I prepare a couple of questions.2 These might be questions people dm'ed you about, or if there aren't any, bring some yourself. This isn't really about the quality of the question3. It's more about getting things going - they work like an icebreaker, if you will.
If you can, take notes on the questions and answers and provide a summary later for everyone to refer back to.
Footnotes
You'll want to try and hit a sweet spot between nobody-had-time-to-try-yet and I'm-not-waiting-that-long-to-get-an-answer. ↩
This was actually a suggestion from the field services team members who worked with us on the rollout! ↩
People get stumped by really obvious seeming things, but then hesitate to ask about them. Be helpful and ask for them! ↩
The text was updated successfully, but these errors were encountered: