There Is a Difference Between Need and Demand

Mission-driven organizations are very good at identifying need.

We conduct needs assessments. We analyze disparities. We talk to communities. We study workforce gaps, educational inequities, healthcare challenges, and unmet social needs.

Then we build something to address them.

But there is a critical question that often gets skipped: Does anyone actually want what we're building?

Need and demand are not the same thing.

A community may clearly need greater access to workforce training. That doesn't mean people will enroll in the program you've designed.

Employers may desperately need workers with a particular skill set. That doesn't mean they'll pay for the training required to produce them.

Students may benefit enormously from a new educational offering. That doesn't mean they'll choose it over the dozens of alternatives competing for their time and money.

This distinction can feel uncomfortable in mission-driven work because "demand" sounds like the language of markets, while "need" sounds like the language of impact.

But ignoring demand doesn't make an organization more mission-driven. It can make the mission harder to achieve.

Need tells you where the problem is. Demand tells you whether your solution can reach it.

Startups learn this lesson quickly.

A founder can be absolutely correct that a problem exists and still build a product nobody buys. That's why successful entrepreneurs spend so much time on customer discovery, product-market fit, adoption, and willingness to pay.

Mission-driven organizations need the same discipline.

Before investing heavily in a new program, initiative, or service, leaders should be able to answer:

• Who specifically will use this?

• What are they doing instead today?

• Why would they change?

• What barriers could prevent adoption?

• Who benefits from the solution?

• Who pays for it?

• What evidence do we have that either group will participate?

These aren't questions that undermine the mission.

They protect it.

Demand is evidence.

One of the most dangerous assumptions an organization can make is that because something should be valuable, people will value it.

Instead of assuming, test.

Build the smallest version of the idea. Talk to prospective users. Ask employers to commit. Pre-sell seats. Run a pilot. Seek a corporate partner. Put a price on the offering and see what happens.

A hundred people saying, "That's a great idea," is interesting.

Ten people saying, "Where do I sign up?" is much more useful.

Impact requires adoption.

A beautifully designed program that nobody uses creates very little impact.

A groundbreaking idea that never reaches the market changes very little.

And an initiative that survives only because someone continues subsidizing it may eventually disappear when that funding does.

Mission-driven organizations don't have to choose between impact and market discipline.

In many cases, market discipline is what allows impact to endure.

Start with the need.

But before you scale the solution, prove the demand.