As a new leader, how do I create a good vision?
The last part of the Your Plan of Action series talked about informing and infusing your vision into the organization so that you can help your staff learn to make good decisions on their own.
Which was all good stuff, but we didn’t actually talk about vision. What is it, and how do you get some?
A vision: how things ought to be
Vision is another $50 cottage-industry-spawning buzzword. But really a vision is simply your mental image of how things could or ought to be. In general this should be fairly high level, so that you don’t have lots of visions. If you do, it’s fairly likely that what you really have are goals related to a single overarching vision.
For example, my vision for high performance computing is to remove the barriers to access in order to encourage scientific discovery. In plain English, this means that I want to make high performance computers so easy to use that the scientists and engineers using them can focus only on what they want to do, not how to get it done.
My vision involves changing the way things have been done for the past thirty-five years. In general, visions are like this; they are stretch goals, not the next logical step in the chain, but a big leap over to a new chain of logical things entirely.
Forming a vision takes time: don’t rush it
If you’re still in school or recently graduated, the odds are fairly good you don’t have a vision. If you’ve just recently started to lead as a part of the executing team in your organization, the odds are still good you don’t have a vision, even if you and others think you do, or at least they think you should.
This is fine.
One of the necessary conditions for creating a vision of your own is being able—either by virtue of training, natural ability, or time in a position of sufficient seniority—to see the big picture and then to see what’s wrong with that picture and imagine how it could be better.
When you are just starting out, you don’t see the big picture. You may not even know there is a picture. You’ve got your head down, getting the job done.
Training yourself to create a vision
But eventually someone will ask you to pick your head up a little. They’ll ask, “You know, our code-revision system is really pretty old and seems kind of clumsy to use. Could we manage the code base more effectively? What do you think?” And you’ll look around at the landscape of one particular problem, and see part of the picture. As time goes on and your experience and level in the organization grow, you’ll naturally see more and more of the picture. Then, if you are paying attention to what you see and trying to stay out front then eventually you’ll start to see the flaws in the image. Once you see these flaws, and come up with a new picture, then you’ve got a vision.
Focus on the value of the contribution
Incidentally, not all visions are unique. Probably very few are. I certainly am not the first person to have my particular vision for high-performance computing, and I’m not even the only one who cares about it right now. Lots and lots of people all over the world share this vision. The important point is to contribute something unique, not that the vision itself be unique.
