Most institutions have a purpose statement. Most of the leaders I work with can recite it from memory, or at least summarize it fairly. Very few of them can use it to resolve an actual trade-off when one arrives. That gap, between a purpose statement that exists and a purpose statement that works, is the subject of this essay.
The gap becomes most visible during difficult stretches, when an institution is being pulled in several directions at once and the pulls do not all fit inside the week. Those moments are, at some level, values conflicts. In the absence of a purpose statement that can actually function as decision criteria, the conversation that follows will not produce a decision. It will produce a values argument, which is the worst form of leadership meeting in higher education, because nothing closes and everyone leaves with their original position more firmly held than when they arrived.
The shape of a values argument is recognizable enough to describe. The pattern usually runs this way. Someone in the room advocates for a particular choice because it protects something real and worth protecting. An objection arrives from someone else, on the grounds that the same choice compromises a different commitment that is also real. A third commitment enters the conversation through yet another voice, who would prefer a different choice because of what that one preserves. Everyone is defending something worth defending, and no one is wrong about what they are defending. Because the shared criteria for weighing the competing goods has not been established, the conversation becomes an implicit contest over whose concern has more moral weight. Those contests do not produce decisions. They produce either a compromise nobody believes in, or a unilateral call by the leader, because the team could not arrive at agreement on its own.
What purpose is supposed to do, in a moment like that, is tell the team in advance of the argument how competing goods will be reconciled when they conflict. Not by ranking values philosophically, which is a separate and mostly unproductive exercise, but by specifying, for the situation at hand, which commitments the institution will prioritize, and why. The specification is what allows the conversation to shift from “whose concern matters most” to “how do we protect as many of the specified commitments as possible given the real constraints.” The second conversation is a design problem, which can be solved. The first is not a design problem. It is a contest.
The specification has two properties that are easy to describe and surprisingly hard to produce in practice. It has to be specific enough to actually discriminate between options the team is facing, which means not “we value excellence” but something closer to “in this particular decision cycle, we are protecting the advising office’s same-day response on student-care issues, and we are willing to accept reductions elsewhere to preserve that capacity.” The other property is portability. The director who leaves the meeting has to be able to repeat it to her team in language that matches what she heard in the room. If purpose requires translation every time it is invoked, it is not doing the work criteria do. It is doing the work of a password.
Most mission statements fail the portability test. They are written for external audiences, in a kind of language designed to sound appropriate to those audiences, and the language of appropriateness is not the same as the language of decision. A mission statement that reads well on a website is not necessarily useless, but it is usually insufficient for the work a team has to do together during a hard stretch. What the team needs, in that stretch, is a short articulation of what this particular institution is protecting during this particular period, at a level of specificity the mission statement deliberately avoided.
There is a failure mode that is recognizable once you know to look for it. An institution has a mission statement, has values on a website, has strategic priorities in a planning document, and still cannot use any of that language to resolve the tensions a hard week produces. When teams in that condition make decisions, the formal values language rarely shows up until someone invokes it rhetorically to defend a position they were already holding. The values language is serving as ammunition rather than as criteria. The mission statement is present, the decision-making is still a values argument, and nobody can quite explain why.
What has usually happened, in that condition, is that the institution has confused aspirational language with operational language. Mission statements are aspirational. They describe what the institution hopes to be. Operational purpose is different. It describes what the institution is protecting right now, given the constraints that exist right now. A leader who wants purpose to function during a difficult week has to translate the aspirational language into operational language for the particular week in question. That translation is the move.
The translation is not dramatic. It takes about ten minutes at the start of a leadership meeting, and it consists of answering one question out loud in front of the team. What, specifically, are we protecting in this stretch? Not what do we aspire to. Not what does the mission statement say. Not what would we protect in the abstract. What, right now, are we committed to defending when the trade-offs arrive? Answering that question in concrete language shifts everything downstream. The team has a filter for incoming requests. Decisions have criteria. The values argument that was about to happen does not have to happen, because the values have already been weighed and named.
The resistance most leaders feel to doing this is worth taking seriously. The real resistance is usually not time, which is minimal, nor skill, which is not required. The real resistance is that operational purpose makes trade-offs visible, and visible trade-offs are politically uncomfortable. An implicit trade-off can be managed through vague language about difficult decisions, because no one can name precisely what was sacrificed for the outcome that was produced. An explicit trade-off means the leader has to stand behind a specific ranking of values she made, rather than hiding the ranking inside a more general invocation of the mission.
The answer to that discomfort, for what it is worth, is that the trade-offs exist whether or not they are named. Leaving them implicit does not make them disappear. It means the team is making them without shared agreement on what they should be, which is a worse situation than the one explicit trade-offs produce. Making them explicit costs something in political comfort. What it produces in exchange, over time, is a team that can actually coordinate under pressure without fragmenting, which is a better trade than most leaders realize at the time they make it.
There is one last thing worth saying about purpose as criteria, because I see leaders get it wrong often enough to flag it. The articulation has to be revisited. Operational purpose is not a set of permanent commitments. It is a statement about what this institution is protecting in this stretch, which is a different question in the fall than it is in the spring, and a different question in a budget year than in a strategic-planning year. Leaders who name operational purpose once and then treat it as settled are missing the point of the exercise. What makes the practice useful is that it produces a fresh answer when the situation has changed, which means the articulation is a living thing the team returns to, not an artifact the team produced and then stored.
That is almost all of what I wanted to say on this. Purpose that actually works is specific, portable, and revisited. The test for whether yours is working is whether, during the last tense meeting your team had, anyone invoked it in a way that actually settled the argument. If yes, it is doing its work. If not, what you have is probably an aspiration, which is a different thing from criteria, even when the two pieces of text use the same words.
DEB