Who’s up for a scary story? This one isn’t going to start with “It was a dark and stormy night…,” but if your IT department is reporting metrics that nobody’s listening to, that can be equally freaky. Dan Kane, writer for the ITSM Review, argues that your metrics should always tell a story. It doesn’t have to be a scary one, but it should be always be compelling. Here’s how metrics are like good storytelling:
- Every element must lead to a singular goal.
- It should create a shared experience.
- It should make the stakeholders care.
- You should always know your ending before figuring out the middle of the story (keep your end goals in mind throughout the project).
- Always provide a practical example (something that makes your story real).
Maybe every story doesn’t end in happily ever after, but it also doesn’t have to end in carnage. Either way, your metrics will attract a rapt audience of stakeholders if you keep all the storytelling elements in mind.