A Question Worth Considering…

If the most meaningful parts of your work can’t be shared publicly, how do you help someone understand the value you bring?

If you do evaluation or consulting work with sensitive data, you’ve probably said this to yourself at some point:

“I know I should show proof on my website…but everything I do is confidential.”

The concern is real:

• You’re dealing with sensitive data and internal dynamics.
• You don’t want to put organizations on display.
• Some of your best work sits behind NDAs.

At the same time, a website with no proof leaves visitors with unanswered questions, even when they already trust the person who referred you.

Let’s explore some practical ways to show impact and credibility on your site without naming clients, sharing sensitive details, or compromising trust.

What happens when there’s no visible proof

Let’s imagine someone has just heard about you→through a referral, a conference, a colleague, a publication, or a professional network.

They’ve heard:

• “Tricia is great at untangling website messaging.”
• or “This evaluator really helped us make sense of our data.”

They land on your site and see a description of what you do, some values and methods, but no example of what it looks like in practice.

They’re left wondering “Has this person actually done projects like mine before?” Or maybe, “Do they understand organizations like ours?” or even, “Will this be worth the time and money?”

We all know referrals (or introductions) give you a head start, but proof helps people feel safe moving forward.

You don’t need pages of case studies. You just need a few thoughtfully chosen signals that say “I’ve done this before. I understand the kinds of challenges organizations like yours are facing.”

Five ways to show proof without breaking confidentiality

You do not need named case studies with logos to be credible.

Here are five types of “safe” proof you can use.

1. Short, anonymized case snapshots

These are 3–5 sentence stories that protect identities but share the arc of the work.

Structure:

1. Context – What kind of organization or client was this?
2. Challenge – What wasn’t working before you worked together?
3. Approach – What did you do together?
4. Change – What’s different now?

Example (adapt to your own world):

A mid-sized community foundation wanted to better understand the impact of its youth grants across several partner organizations.

They had years of data but no clear picture of what was working or how to share that story.

We worked with staff and grantees to clarify a small set of shared outcomes, streamline what was being collected, and design simple visual summaries.

Now they create an annual learning brief for their board and partners and use it as a basis for funding decisions.

No names. No identifying details. Very clear story.

Drop 2 to 4 of these on a “Proof” or “Selected Work” section and your site already feels more grounded, painting a picture of the experience you can offer.

2. Patterns and themes across projects

Sometimes the most honest proof is at the pattern level:

• “Across 10+ community-based evaluation projects, we’ve helped organizations move from ‘drowning in data’ to using a focused set of measures they revisit regularly with staff and community members.”
• “In our work with independent consultants, a common shift is moving from ‘I’m embarrassed to share my website’ to ‘I send it ahead of conversations because it helps people understand my work before we meet.’”

Patterns reassure people that:

• You’re not new to their kind of problem.
• Their messy situation is actually quite normal.
• There’s a recognizable “before and after” you’re familiar with.

These can live as 2–3 short bullets or paragraphs under a heading like “What tends to change when we work together.”

3. Process evidence: showing how you think and work

Proof isn’t only outcomes. It’s also:

• The questions you ask
• The phases you move through
• The principles that guide your decisions

Describing your process helps visitors think:

• “Oh, this is how they’d approach our situation.”
• “This doesn’t seem cookie-cutter. They’ve thought carefully about how they work.”

You might outline:

• A few key steps you almost always take
• The types of conversations you have with clients
• How you make sure your work is actually used (not just shelved in a report)

This is especially helpful when you truly can’t share many project details, but you can share how you think.

4. Values-aligned testimonials (even if anonymized)

Even if you can’t name organizations, short quotes from clients or partners can still go a long way.

Examples:

“Working with [First name] helped us finally translate our evaluation work into something our board and staff could understand and use.”
            — Program Director, youth-serving nonprofit

“We came in overwhelmed by years of data and left with a simple, sustainable way to keep learning.”
            — Executive Director, regional coalition

You can label these by role and type of organization instead of name and logo, if that’s more appropriate.

Short is fine. Real is what matters.

5. Expertise signals and professional context

Sometimes credibility comes from showing the depth of experience behind your work.

This might include:

• Years working in a field
• Types of organizations you’ve supported
• Methods or approaches you specialize in
• Publications, presentations, or professional contributions
• Specialized training or credentials

These signals don’t replace examples of your work, but they help visitors understand the depth of experience behind the work.

A 20-minute exercise to build your “Proof” section

1. List 3–5 projects you’re proud of.
   Don’t worry yet about confidentiality; just write working titles for yourself.
2. For each, write 2–4 sentences using the case snapshot structure:
   • What type of organization it was
   • What wasn’t working
   • What you did together
   • What changed
   • Why did they choose you?
   • What expertise, perspective, or experience made them trust you with this work?
3. Underline any patterns you notice across the stories:
   • Common starting points
   • Recurring types of shifts or outcomes
   • Shared constraints or challenges
4. Choose 2–3 of those stories to lightly polish for your website.
   The rest can live in a private document you draw from in conversations.

By the end of 20–30 minutes, you’ll have:

• The bones of a “Proof” section for your site
• A few stories you can reuse in proposals, talks, and 1:1 conversations
• A clearer sense of your own impact patterns

A note on ethics, NDAs, and comfort levels

Always consider:

• Getting explicit permission before sharing a story, even anonymized
• Letting clients review how you’re describing the work
• Softening or omitting details that feel too specific

Many organizations are happy for you to talk about:

• The type of work you did together
• The kinds of shifts or decisions it supported
• Their experience of working with you

Especially if you’re careful not to share sensitive data or internal politics.

If a situation is genuinely too delicate, don’t use it publicly at all. You almost always have other projects you can draw from, but may still be able to include those more delicate situations as stats and in other ways (like mining for commonly used phrases, or give you insight as to the kind of problems you like to help with, etc.)

How this supports a business where expertise comes first

Remember: your website’s job is to help people understand and trust your work when you’re not in the room.

A strong website should:

• Make your expertise easier to see and understand
• Show the patterns and types of work you’ve successfully supported
• Give potential clients confidence that you can handle work like theirs
• Make it easier for someone to advocate for you internally

Thoughtful proof points can:

• Reduce the “Can you send us an example?” questions that often come up during early conversations
• Help someone explain your experience and approach when they share your website with colleagues
• Give you clearer language to reuse in proposals, conversations, and presentations
• Reinforce the credibility you’ve built through years of experience, even when client details need to remain confidential

You do not need glossy case study PDFs for every project.

You do need some visible evidence that your work exists in the real world.

One More Thought…

People don’t always need to see everything you’ve done.

They need enough understanding to imagine what it would feel like to work with you.

There are many ways to build trust, even when the details of your work need to remain private.

If you’re struggling to translate years of experience into a website that clearly communicates your expertise, that’s the work we begin in The Focus.

Together, we identify the patterns, stories, and proof points that make your work easier to understand—so your website can reflect the depth of your experience without sharing what needs to stay private.

Learn more about The Focus