Articles

Even Overs: A Discussion Guide for Leadership Teams

Written by Moira Kelly | July 03, 2026

The problem this solves

Every leadership team eventually hits the same wall: two good things, not enough time, money, or people to do both well. The instinct is to avoid saying so. You add the new initiative without retiring the old one. You promise the board both stability and innovation. You tell faculty that retention and new hiring are both top priorities this year, without ever naming which one wins when they collide.

The avoidance feels kind. It isn't free. Left unresolved, it shows up as slower decisions, because nobody has permission to choose. It shows up as credibility loss, when a head says everything matters and the team quietly concludes nothing does. It shows up as drift in culture and identity, as the school tries to be all things and becomes recognizable as none. It shows up as fatigue in your best people, who are asked to hold two competing standards at once. And it shows up in the board room, when the head and the board have never actually agreed on what the institution is optimizing for.

The tradeoff itself isn't the problem. The silence around it is.

What an Even Over is

The practice comes from Karina Mangu-Ward's work at August, developed in her book Teams That Meet the Moment. The structure is simple: name two things you genuinely value, and state which one wins when they conflict.

Faculty compensation growth, even over expanding new academic programs. Retaining institutional memory, even over hiring for fresh perspective. Protecting instructional time, even over adding new all-school programming.

Notice what an Even Over is not. It is not "A over B" as in B doesn't matter — that's just a priority list, and priority lists are how schools end up with eleven priorities. An Even Over insists both things are real values, worth real investment, held by reasonable people on your team. It only resolves the question of what happens when they collide. At times they won't collide, and you'll get to do both. The Even Over exists for the times they do.

That distinction is what removes the stigma. Choosing B doesn't mean you devalued A. It means you did the thing your team already agreed to do, in a moment your team already anticipated.

An example

Imagine a school leadership team spending a fall weighing, budget cycle after budget cycle, whether to fund a new STEM lab, raise faculty salaries, or hold tuition flat for affordability. Every conversation returned to the same three options, because no one had ever said out loud which of these the institution was actually built to protect first. The team finally sat down and wrote: Faculty compensation, even over new capital projects, even over affordability initiatives. It took one afternoon and the team was very clear on their thinking of why they arrived at this place. It saved months of revisiting the same question and gave the head language to use with the board that made the team’s thinking transparent.

How a team uses this

Even Overs work best as a small, durable set — two to three statements a leadership team can actually hold in their heads, not a policy document. They're built from real recent decisions, not abstract values exercises. And they're revisited on a cadence — annually, or when circumstances genuinely shift — because an Even Over that was right two years ago (protect the endowment, even over facilities investment) may be exactly wrong today. The point isn't to get it permanently right. It's to have something explicit enough to return to, so the next hard call doesn't start from zero.

Discussion guide

Use this with your leadership team in a single 60–90 minute session. Come with real recent decisions in hand, not hypotheticals.

1. Surface the pattern.

  • Where have we recently made a decision that pitted two genuinely good things against each other and never said so out loud?
  • Where are we currently telling different audiences (board, faculty, families) that we're prioritizing two things that will eventually conflict?

2. Draft candidates individually.

  • Before discussing as a group, each person writes one or two Even Over statements based on real tensions they've personally navigated in the last year. What did you actually choose, even if no one named it at the time?

3. Compare and stress-test.

  • Where do our individual drafts agree? Where do they reveal that we've been operating from different unspoken priorities?
  • For each proposed Even Over: can you name a real, recent decision where the "losing" side genuinely lost? If you can't, it's not a real tradeoff yet — it's aspirational language.

4. Check for false comfort.

  • Does this statement still feel true if the other side of it is what gets sacrificed next month? If it only feels safe in the abstract, keep working on it.

5. Commit and communicate.

  • Which two to three Even Overs will we actually carry forward this year?
  • Who else needs to hear these — board, department chairs, faculty? An Even Over that lives only in the leadership team's heads doesn't do its job.

6. Set a revisit date.

  • When will we come back to these? What would have to change about our circumstances for one of these to flip?

A closing note for facilitators: the goal of the session isn't consensus on every word. It's getting the team comfortable saying, out loud, that something they value will sometimes lose and that this is a decision, not a failure.