Translation Is Crucial

In conversations about nonprofits, tension is often framed as disagreement about priorities, strategy, or resources. In my experience, many of the deepest challenges are not about disagreement at all. They are about language. More specifically, they arise when people inside the same organization assume they are speaking the same language when they are not.

Boards and funders often come from backgrounds in business, finance, law, or real estate. Staff members are more likely to come from education, the arts, human services, or community-based work. Each group brings essential expertise. Each group also brings its own vocabulary, assumptions, and ways of defining success. Problems emerge when one language is treated as inherently more credible than the others.

When business language dominates by default, mission-driven work can be flattened. Conversations drift toward efficiency, scale, or return without fully accounting for trust, care, or long-term impact. At the same time, when program language is left untranslated, boards can feel disconnected from the realities they are responsible for governing. Neither side is wrong. They are simply speaking past one another.

This is where leadership matters most. Translation is not an administrative task. It is a core leadership responsibility.

I remember a board meeting early in my career where program staff shared a deeply moving account of a program’s impact. The board’s response was not dismissive, but it was distant. The conversation stalled because no one helped translate that story into terms the board could hold. Later, a finance committee reduced the same program to a line item that looked inefficient on paper. It took intentional leadership to bring those perspectives back together and show that they were, in fact, talking about the same thing.

I often think about this when I facilitate a LEGO Serious Play exercise with leaders. I give fifty people six identical bricks and one simple instruction: build a duck. What happens next is always the same and always surprising. Fifty leaders, the same materials, the same directive, and we end up with fifty completely different ducks. Some are abstract. Some are literal. Some barely resemble ducks at all. And yet every one of them is a valid response to the prompt. The exercise is a reminder that there is rarely a single right way to get where we are going. Leadership is not about forcing uniformity. It is about recognizing patterns, honoring difference, and helping people see how many paths can lead to shared purpose.

At its best, translation honors complexity rather than erasing it. Program staff tell stories and share outcomes rooted in lived experience. Who showed up. What changed. What did not. Why it mattered. Finance teams translate those stories into numbers that help an organization understand cost per participant, sustainability over time, and tradeoffs between programs. Leadership’s role is not to choose one language over the other, but to hold both at once and bring them into conversation.

When this works well, boards are not asked to abandon their skills. They are asked to use them differently. Instead of pushing for simpler answers, they learn to ask better questions. Questions that recognize uncertainty. Questions that acknowledge risk without demanding false certainty. Questions that connect mission to money without reducing either to a slogan.

I have seen how powerful this can be. In healthier organizations, leaders slow conversations down instead of rushing toward conclusions. They take time to explain why a program that looks inefficient on paper may be deeply effective in practice. They also name when a beloved program is no longer serving the mission as well as it once did. Translation works in both directions. It protects what matters and challenges what no longer does.

Translation is not dumbing things down. It is building shared understanding. It is the difference between reporting and meaning-making. It requires patience, humility, and a willingness to admit that no single perspective holds the full picture.

Organizations that do this well tend to share a few traits. They do not privilege one language over another. Financial literacy is valued, but so is program expertise and cultural knowledge. They invest in mutual learning, creating opportunities for board members to better understand the work on the ground and for staff to better understand governance and finance. They reward curiosity rather than compliance.

These organizations also resist the urge to oversimplify. They understand that complex social problems rarely have clean solutions and that clarity does not always arrive quickly. Instead of forcing alignment through pressure, they build it through conversation. Over time, this creates trust, which is far more durable than consensus achieved through speed or authority.

In a sector built on relationships, translation is how those relationships are sustained. It is how mission survives complexity. When translation is treated as leadership rather than an afterthought, organizations are better equipped to do the long work they exist to do.