Learning a Language No One Teaches

This essay is part of a continuing series on power and ambiguity in philanthropic practice. It builds on ideas introduced in Guessing What the Funder Wants, though it can be read on its own.

When I worked at an organization dependent on philanthropic and government funding, we were selective about which competitive opportunities we pursued. We won some and lost many. Looking back at the wins, one pattern stood out: we had either worked with the funder before, or we were a sub-partner on a larger bid - contributing technical ideas while a bigger organization, with existing contracts and years of relationship history, led the proposal.

At the time, I read this as a question of organizational capacity. We were smaller, newer to certain spaces, still building our track record. But over time I came to see it differently. The larger organizations weren’t just better resourced. They knew how to read the system. They understood which parts of a requirement were fixed and which were negotiable, which risks a particular agency would tolerate, and how to frame ideas in language that felt native to that funder’s way of thinking. We contributed the substance. They supplied the fluency.

That asymmetry has a name, though the sector rarely uses it. I now think of it as philanthropic literacy.

Not literacy in the conventional sense, but the ability to interpret how funders think and decide. It includes recognizing which questions matter most, how risk is interpreted, and how particular phrases signal alignment even when they appear neutral on the page. A line like “strong leadership” or “a clear theory of change” can carry very different expectations depending on how a funder has used those terms before and whether an organization has learned, through experience, how they tend to be read.

Like many forms of literacy, it is rarely taught directly. It tends to accumulate slowly through repeated interaction. Organizations develop it after years of engaging with the same institutions, observing which proposals advance, how feedback is framed, and which trade-offs are rewarded. What once felt ambiguous becomes easier to interpret. Silences and omissions begin to speak.

Unfortunately, this kind of literacy does not accumulate evenly. Organizations that have worked with a funder before often develop an intuitive sense of how that institution thinks. Signals that might appear vague to others become legible through familiarity. For organizations encountering the same funder for the first time, the experience can be very different. Ambiguity may feel like openness. Silence may appear neutral. Decisions that seem predictable to some appear opaque to others.

What looks like experience, however, is often proximity. What looks like intuition is often repetition.

None of this is usually intentional. The conditions that produce philanthropic literacy - risk aversion, the myth of flexibility as openness, the simple fact that grantmakers can afford to be misunderstood - are worth examining on their own. What matters here is what they produce.

Funding processes are often designed to be fair by treating all applicants the same. But when interpretive knowledge is unevenly distributed, equal procedures do not necessarily create equal footing. What appears neutral on paper can quietly reward familiarity. Organizations with prior exposure are better positioned to read between the lines - not because they are more capable, but because they have learned how this particular system speaks.

And so something subtle begins to happen. Organizations become skilled not only at understanding the systems they are trying to change, but also at understanding the institutions that fund the work. Success begins to depend partly on interpretive skills - knowing how to respond to what is said, and just as importantly, to what is not.

Quietly, the field becomes fluent in philanthropy's silences. Once that language exists, it begins to shape behavior. Organizations learn which signals matter and how to respond to them. Certain risks are avoided. Some questions remain unasked. Proposals grow more careful, sometimes more cautious.

The danger is not simply that some organizations learn this language better than others. It is that the field gradually begins to reward fluency in it. A sector organized around solving complex problems can end up directing a surprising amount of collective intelligence toward interpreting funders rather than understanding the systems those funds are meant to change.