How can I present GRIST in ten minutes to my colleagues so they understand the value of the application?

I have ten minutes to introduce GRIST during our team meeting.

I also ran a short survey, and the feedback is quite mixed : some colleagues don’t know the tool at all, while others do know it but feel it creates more problems than it solves.

How can I approach this topic, considering that everyone has different levels of digital skills and that I only have ten minutes ?

What made you start using GRIST in your work ? Have you ever done this kind of exercise before ?

We also just recently started to integrate GRIST for some of our processes. I envisioned a relatively grand solution for our event management needs. Even though it was more efficient and scalable, it was also a total departure of the way we used to organize stuff (Dozens of Excel-files). Basically a No-Go for my boss.

We also organize all signposts, guide posts and destination boards in the area. It just so happened that I was tasked to determine their individual wear and tear and need for replacement and document it with photos. Instead of creating yet another excel file with a separate folder for photos, I created a GRIST document. I put a lot of work in the actual data but the end result was quite simple.

I presented my boss with a simple map widget. He would click one of the pins on the map and was presented with the most recent photo and description of the object. Easier than Excel.
The presentation itself was completely non-technical and basically only showcased a big jump in usability. The bigger implications or potential of the tool didn´t matter at all. It just worked and he approved it.

After that, he knew the name of the tool and it was easier to implement it for other projects.

So, my advice would be to make it a battle of first associations. Show them a prototype and make it as easy, cool and non-scary as possible.

1 Like