Improving Retrospective Demo Engagement #5956
Replies: 3 comments
-
|
In our demo the bot groups across columns – this might be confusing for people encountering the tool for the first time. One person commented:
|
Beta Was this translation helpful? Give feedback.
-
|
This is an underrated discussion! It's going to be difficult for us to resolve this discussion async in GH I feel. If our priorities for the next couple of quarters carry you to action on this one, I think it'd be a good idea to see if there are some folks who'd want to jam on ways if improving the demo experience. We've done very little revision here since we launched it |
Beta Was this translation helpful? Give feedback.
-
|
Stale issue |
Beta Was this translation helpful? Give feedback.
-
Data from Amplitude shows that only c.3% of folks starting our Retrospective demo get to the group stage, which means the vast majority of people are clicking onto the demo and then almost immediately clicking away.
There's an opportunity to improve demo completion.
Hypotheses why people abandon the demo:
1. People want to see how it works before trying it themselves
2. People are impatient and don't want to wait for the bots to write up their reflections
Some thoughts on each of these points:
When I go to a new site to evaluate a technology offering my usual flow is as follows:
We might improve demo engagement if we do more to ease people in with a product video that shows quickly what it does instead of requiring browsers to make the effort of actively engaging with a demo.
Personal reflection: I remember the first time I came across Parabol's demo, I didn't feel comfortable yet writing in the reflection boxes because even though it was a demo, I didn't want to do it wrong. Doing the demo is a bit like coming into a new team and not really having the psychological safety associated with knowing what's expected.
It takes roughly 35 seconds for all the bots to write up their reflections and we know from user research and observing new folks on our team that the 'Next' button isn't always obvious to people the first time around.
We might improve this by creating a stronger CTA within the demo nudging people to move on to grouping. It might be that people don't know what to do next or don't realise there is another stage and therefore exit the demo.
My hunch is that people want to passively see how something works first. If we are engaging people in the demo after they have seen how it works passively, they will have gone to the demo because they are interested (i.e. want to actively participate in the demo) and will feel more confident actively participating because they've seen how it works.
Beta Was this translation helpful? Give feedback.
All reactions