Have you ever wondered how to find the “one metric that matters” (for your team)? Or how to magically communicate why your team is doing what you’re doing so everyone can understand? Or moving back several steps -- how should you decide which work to focus on? This tutorial isn’t the magic pill, but it’s the closest thing to get you to be able to answer all of those questions. And once you learn it, you’ll be able to sketch it out on the back of a napkin.
I’ve used this simple framework with:
- Fortune 500 executives decide on the right metrics to use for their latest initiatives and communicate it throughout the organization
- Sysadmins to communicate their latest improvement work across their own teams and to “the business”
- My own research ranging from complex hardware studies to the State of DevOps Reports
The framework works for all types of measures: system, survey, technical, financial, etc.
Engineers, managers, anyone needing to plan or understand a system.
When you leave this tutorial, you’ll be able to:
- Communicate your measurement framework in a straightforward manner
- Identify key measures for your own improvement work, and share this easily with the data team (whether that’s you or another team)
- Chain your measurement frameworks, allowing you to link executive-level initiatives to middle management goals to practitioner workstreams