We learned early on in technology school (well . . . if there was such training)! It is all about people, process, and technology. But we often skip past the people and the process and go straight to the technology.
We’re very guilty of that.
I want to share a simple model to use going forward to ensure we consider people and process too. Something that will help you define what Agile, for example, means . . . to you ! (or DevOps, or microservices, or . . .well, anything). Others, of course, will have other definitions and that’s ok: you can be the translator!
Be the person that can be the translator for your organization, and for your partners.
The model is simple. It’s the idea that in order to be able to do anything, before you get to tools or anything else — you have to understand how your organization works, what your processes are, and that you must categorize them. And if you categorize them — take the time to say “okay, this is where this goes, this is where this fits, this is what this does”, then you can start to classify them. Well, “if I’ve got that, then that means maybe I’m setting up this — and this could be a special use”.
This is the beginning of declaring and establishing standards!
And, if you do those two things, then you get clarity AND a greater capability to consider questions and factors such as:
- What was the missing or weak step in the process?
- What caused the missing or weak step in the process?
- What is currently done to prevent failure at this step?
Want to know more about being the translator for your organization and leveraging Categorizing, Classifying, and Clarifying?
Reach out to us and we’ll help you dig deeper, probe, and look beyond the obvious.