Vision statements are usually terrible. Here is a better test and a shorter format.
Consulting is often accused of being long on frameworks and short on judgement. This piece is an attempt at the opposite: a working operator's view of how to write a company vision statement that sticks, with the frameworks kept in the background where they belong.
Every good piece of business writing starts with the question the reader is actually trying to answer. In this case it is a variation of: what should I do differently on Monday? If a piece of writing does not answer that, it is decoration.
The best way to get to the underlying question is to ask it directly of the people you are trying to help. In consulting terms, that means starting an engagement with a discovery conversation whose only purpose is to surface the real question โ not the one the client wrote in the brief, and not the one you thought you were being hired to solve.
Three failure modes show up over and over. The first is premature answers โ jumping to a solution before the question is properly framed. The second is false precision โ spreadsheets and models that look confident but rest on unexamined assumptions. The third is ownership drift โ decisions that quietly become no one's job between the last session and the first Monday afterwards.
Force the question into a single sentence. Assign a named owner to every decision. Agree what will be true in ninety days if the work has gone well. Then, and only then, get into the analysis.
When ClarityBridge is engaged on this kind of problem, we normally spend the first week on framing and ownership before touching the substantive work. It feels slow. It is the fastest path to a decision that actually holds.
If any of those steps feels hard, that is diagnostic โ and worth a Business Review.