Re: your comment, I think we’re on the same page. I agree that the vision statement is brief – yes, probably too brief to stand alone in most cases. I would recommend accompanying the vision statement with a more detailed list/description of the business problem(s) to be solved and the objectives to be met – to include more emphasis on the economic impact of the problem, and how we’ll measure success (a.k.a the objectives or benefits as you mentioned).

As I mentioned in my post, I liken the vision statement as a strategy statement scaled down to the project level. It is easy to remember and can be a powerful “quick reference” when it comes to arbitration over whether something should be in scope or not. If it aligns with the vision, let’s talk about it. If it doesn’t get us closer to attaining the vision, we’ll probably drop it.

Anyway, again, thanks for the comment, and welcome to JB.com.

I use this format to structure my vision statements often and I’ve added it to every project proposal template I’ve had the authority to create and implement. When you are dealing with a relatively immature environment, this format really helps people clarify their thinking. However, I think it encourages thinking that is a little too brief at times. My best vision statements have fleshed out each item in at least a few bullets. So for example, “That integrate digital fantasies with actual film footage” would become a list of the new systems key features. And “SGI has made a no-compromise commitment to meeting film-makers’ post-production needs” would become an itemized list of benefits to be realized by the project. You lose the effect of the elevator speech but you gain a lot of clarity.

Cheers,
Laura

website: http://www.clearspringanalysis.com
blog: http://www.clearspringanalysis.wordpress.com