I agree that spending the time teaching products (for me, this is stuff like showing my business stakeholders how to use a new dashboard, or providing demos of Looker) is really useful. What I struggle with sometimes is getting the buy-in from the powers that be to spend the time on it. Generally I have no problem getting buy-in for one-time demos or Lunch & Learns, but am typically shot down for things like being involved with our onboarding education series for new employees, or giving thought to regular teaching time on our most used tools.
One-off isn't enough, I agree. What advice do ya'll have for framing the need for ongoing education in a way that makes it seem as important as me churning out new data products? I get that both are important, it's not a one or the other thing. I just have a hard time getting approval for the former.
Something I do to create documentation and resources but not pre optimize for scale is when someone asks a question I record a Loom showing how to do it or I record a training session of me teaching. I've even just recorded looms of me doing tasks and talking through them and then I throw the link into Notion/confluence/guru. It takes very little additional time for me and at least creates some type of reference for others.
Superhuman's white-glove approach to the "prosumer" market has always been very interesting to me. Not a common business model, but one that I think could be effective.
On a different note, I think it's interesting that most people will have no problem sitting through a synchronous 30-minute meeting with a live person on the other end, but asking them to watch a 10 minute Loom video with the exact same content is out of the question.
I agree that spending the time teaching products (for me, this is stuff like showing my business stakeholders how to use a new dashboard, or providing demos of Looker) is really useful. What I struggle with sometimes is getting the buy-in from the powers that be to spend the time on it. Generally I have no problem getting buy-in for one-time demos or Lunch & Learns, but am typically shot down for things like being involved with our onboarding education series for new employees, or giving thought to regular teaching time on our most used tools.
One-off isn't enough, I agree. What advice do ya'll have for framing the need for ongoing education in a way that makes it seem as important as me churning out new data products? I get that both are important, it's not a one or the other thing. I just have a hard time getting approval for the former.
Something I do to create documentation and resources but not pre optimize for scale is when someone asks a question I record a Loom showing how to do it or I record a training session of me teaching. I've even just recorded looms of me doing tasks and talking through them and then I throw the link into Notion/confluence/guru. It takes very little additional time for me and at least creates some type of reference for others.
Superhuman's white-glove approach to the "prosumer" market has always been very interesting to me. Not a common business model, but one that I think could be effective.
On a different note, I think it's interesting that most people will have no problem sitting through a synchronous 30-minute meeting with a live person on the other end, but asking them to watch a 10 minute Loom video with the exact same content is out of the question.