Language:  English  Français  Español 

Outcome Mapping Practitioner Guide

Tips for doing vision statements

Some tips and tricks to have on hand when doing a Vision statement

Author: Terry Smutylo

Published: Sunday 14 September 2014

Tips for doing Vision statements:

  • To break out of a narrow project approval document mindset, it is often helpful to try to write the vision statement in the language of the people whose concerns it talks about.  Participants may be able to precipitate new thinking by shifting away from coded institutional language and using explicit every day language.
  • Prior to starting the Intentional Design steps, it is a good idea to assess whether calling it a 'vision' statement is appropriate.  There may already have been a large investment in developing an existing organizational vision statement.  It maybe not be helpful or welcomed to open up a process that reists their struggle or tha questions hard-won territory.  Also, it may not fit organizational culture for an individual project or program to have its own 'vision' statement.  Yet creating a vision statement has important functions.  In the early statges it can enable team building and develop mutual understanding and trust among partners.  And it can serve as a test of readiness to proceed. 
  • During implementation the vision statement (or whatever a program, project, organization needs to call it), is a motivator and a guide.  Changing the label will not change its value - it may make sense to call it something other than a vision: a goal statement, an ideal future, a desired state - use a term that speaks to participants.

This nugget was applied in: N/A

Related Practitioner Guide sections:

Latin America & Carribean Sub-Saharan Africa North Africa & Middle East South Asia South East Asia & Pacific Far-East Asia Eastern Europe & CIS (ex USSR) Western Europe North America & Canada Australasia