“We served 400 people last year.” Okay, but how?

Why Credibility is about more than your numbers — and what funders, partners, and customers are actually looking for.

The OPTIC² model categorizes organizational clarity into six interdependent layers: Operations, Public Presence, Trust, Identity, Credibility, and Communications. This post is part of a series examining each layer in depth. For an introduction to the full model, start with The Writer Isn’t the Problem.

The impact numbers are in the annual report. They are also in the grant application, the board presentation, and the senior executive’s talking points for the Chamber of Commerce breakfast.

They are not always the same numbers.

Sometimes it's timing. Sometimes it's definition. Sometimes, no one explains the difference.

Funders notice, not always out loud, but when the numbers on page three of the proposal do not match the numbers on the website, and neither matches the business profile, they have to ask: Do they actually know what they are doing?

That is a Credibility problem.

And unlike some gaps in organizational clarity, this one does not feel administrative. It feels existential. Identity asks an organization to explain who it is; Credibility asks it to demonstrate that it does what it says it does.

Here is what that looks like in practice.

A local funder recently reviewed an application from an organization they had supported for years. They knew the organization. They believed in the work. But the application was missing a key data point — one that demonstrated its work, and one the funder needed to justify the award. The information existed, but it was not in the application.

The funder's review process required evaluators to work from what is on the page. They can hunt for missing facts if the decision is close — but only if it is close. If a better-documented organization is sitting in the same stack, the documented organization gets the funding.

This is not a story about a weak applicant. It is a story about what happens when evidence that exists is not organized, documented, and reliably present in the places it needs to be. The writer did not fail. The Credibility infrastructure did.

That is why this layer matters so much.

What Credibility actually is

In the OPTIC² model, Credibility is the intellectual backbone of your programs: the architecture, evidence, and evaluation systems that show others your work does what you say it does and that you know why.

This is not just about having good outcomes. It is about being able to explain your programs clearly and consistently, ground your claims in documented evidence, and demonstrate that you are tracking results in a way that produces reliable information over time.

That means things like a logic model or theory of change — a clear articulation of how your activities lead to the outcomes you claim. It is an evidence base that connects your approach to research or practice, not just intuition. It defines outputs and outcomes with a measurement plan that specifies what you track, how you collect it, and who is responsible.

It also means past performance that holds up under scrutiny — specific numbers, year-over-year trends, and cost per outcome where relevant — not impressive-sounding approximations. You need actual data from a system that produces it reliably.

The difference between having numbers and having evidence

Most organizations have numbers. Fewer have evidence.

Numbers are what you counted. Evidence is what your counting means and why anyone should believe it.

A program that served 400 people last year has numbers. A program that served 400 people with a defined eligibility threshold, a documented service model, a measurement plan that distinguishes outputs from outcomes, and a multi-year trend showing improvement — that program has evidence.

The difference matters because funders, investors, and partners are not just asking, Did you serve people? They are asking, Do you know what you are doing, and do you have a system that will keep producing reliable results?

That question cannot be answered with a number alone. It requires structure. It requires documentation.

Why this is harder than it sounds

Many organizations know their programs work. Staff have watched participants change. Program directors can tell story after story. In one sense, the evidence is all around them.

The problem is that it is not documented in a way that travels.

The program logic lives in the program director’s head. The outcomes data sits in three different spreadsheets that are not quite reconciled. The measurement plan, if it exists at all, has not been updated since launch. The success stories are powerful but not connected to any systematic evidence about whether the results they describe are typical or exceptional.

None of that means the program does not work. It means the organization cannot yet prove it confidently, and confidence is what this layer is really about.

Funders, investors, and partners are not trying to catch you in an inconsistency. They are trying to reduce their own risk. They are trying to find organizations they can trust to be fiscally responsible, deliver what they promise, and report back honestly.

Credibility makes that case.

What happens when Credibility is weak

When this layer is underdeveloped, the writer feels it first.

They are trying to make the case for a program they know is effective, but they do not have the documentation to back it up. The logic model does not exist or has not been updated in years. The outcome numbers are approximate. The evidence base is thin. They are left trying to sound convincing when what they really need is something solid to point to.

That is a different kind of hard than assembling a proposal under deadline. It produces vague proposals that lean on passion and mission language when reviewers are looking for structure and results.

When Credibility is weak, the downstream layers suffer too. Communications has nothing solid to build on. The impact claims in the boilerplate are either inflated or thin because there is no documented evidence base behind them. Identity may say who you are, but Credibility solidifies those claims.

What changes when the evidence is in order

When Credibility is strong, the writer has something to work with.

The logic model is current and documented. The outcomes are defined, tracked, and reconcilable across documents because they come from a single measurement system. The evidence base is articulated — not just “research supports this approach,” but which research, applied how. The past performance is specific and consistent wherever it appears because it is drawn from the same source.

The proposal still takes work, but it is the right kind of work — making the case, telling the story, and demonstrating alignment with the reviewer’s priorities. It avoids reconstructing the intellectual architecture of the program from fragments at eleven o’clock the night before the deadline.

Where Credibility connects to everything else

Credibility is where Identity becomes supportable and Communications becomes believable.

Identity establishes what you say you are. Credibility is what makes those claims hold — the evidence that connects your stated mission to documented results. Communications draws from both. The copy blocks and narrative assets are only as strong as the identity canon and the evidence base they are built from.

When Credibility is weak, Communications drifts in a particular direction: toward language that is aspirational rather than grounded, that describes intent rather than results, that sounds like a mission statement rather than a track record.

Funders will recognize that drift.

It signals an organization that believes in its work but has not yet built the systems to prove it. Building those systems is not a writing project. It is a program architecture project, and it is a valuable investment in an organization’s ability to learn and improve over time.