Touchpoints Service Design Blueprint
The short answer is that every time I started a new project I found myself creating similar user journey maps from scratch on platforms like Miro and Mural. Then the 30-day trials would run out and I was loath to pay a monthly fee for an entire platform that I would only use for one thing. The long answer is probably a bit more interesting though.
A while back I started studying Service Design principles. Once I started digging into Service Design Blueprinting it made a ton of sense to me but communicating the value behind Service Design to anyone who was not actively practicing it was really hard. Then one day while I was studying a blueprint from IDEO it hit me, I should just call this a user journey map. Everyone I was working with knew what that artifact was and why it was important, so why bog them down with terms they didn't understand? It worked immediately. I started creating more and more complex maps that more and more people were weighing in on! I found that I could schedule a call with Figma or Sketch open and walk the Directors and Product Owners through super-specific flows while extracting valuable insights into the existing state of a product or service. If they were not available I would make some guesses on specific information related to a touchpoint and in our next call, they would jump on it if/when it was wrong! This was really exciting. On one project we even made a massive printout and put it up on the wall to discuss together with the team.
If you'd like to try Touchpoints, just grab the files. All I ask is that you fill out the Typeform survey below if you use them.
https://www.figma.com/embed?embed_host=notion&url=https%3A%2F%2Fwww.figma.com%2Ffile%2FXkjVrwswi3utokRTiG9TY4%2Ftouchpoints_template_alpha%3Fnode-id%3D0%253A1
touchpoints_template_alpha.sketch
https://lanceweisser.typeform.com/to/djgxuEnP