You know the main point of this blog is really so I don’t forget things I come across or ideas I have. I am sure, that if I didn’t right this one down, I’d forget about it and then “rediscover” it about a year from now.
I did some reading on Professor Von Hippel’s site (and of course Wikipedia).
The ‘lead user’ is the person who is using your product/service in a way that the majority of people are not yet. They are trying to solve a problem that the rest of the world doesn’t know it has, yet.
The idea is that you can get innovation breakthrough’s by working with ‘lead users’ of your products/services and see what problems they are facing and how they are working on solving them. You can then perhaps also work with related (but different) area’s to see how they are working to solve similar problems.
If all goes well, you will be ahead of the competition and just as importantly have a better product/service.
Lead Users and ITSM
Are there ‘lead users’ of ITSM? Are there people in your organization that are trying to use your processes (or technologies built to support those processes) to solve problems that you (and the rest of the organization) are not really aware of or paying attention to…yet?
I know, in my last place, I heard of a Project Manager wanting to link a Change Request to a Project. I didn’t hear this from 10 or 20 PM’s or really from anyone working on projects or anyone in leadership – just the one PM.
But what I did was take that idea to the development team and asked them to include in the Change Request a place where you can put in the Project ID Number.
Boom! Now, you can track changes associated to projects. A few weeks after that, at lunch with the CIO, I bring it up to her that she can now have a report that would link Projects to Change Requests. Instantly she saw value in that and instantly it became a need for the majority.
Lesson: Find “lead users” in your organization. Listen to them. Bring their ideas forward. See how you can test them or, put them in practice quickly without spending too much time trying to make it ‘perfect’.
I’m not going to spend anytime explaining this concept. I’m not a SCRUM Master (what a title…) but I do believe Agile is better than classic/traditional/waterfall.
Now, previously, I described the simple way in which you can track projects to change requests. Is this the ‘best’ way to do it?
No. Clearly not. Anyone can forget to associate the two. They can “fat finger” the number. It isn’t the best method. Is it better than nothing. Yes.
And with an Agile approach to process you can start and in the next ‘release’ (maybe 30, 45 days, whatever) you update it. Maybe it wasn’t a mandatory field at first now it is. Maybe even better, there is a question “Is this Change Request related to a Project?” – if they say “Yes” then you make it mandatory. Oh, even better, why not ask the question, make it mandatory, but it is a drop down pulled from the Project Management technology?