All resources

Why every Proof of Change service starts with a diagnostic

Before Proof of Change, I spent years working in marketing, communication and advertising. One lesson from that work shapes how we run every project today: there is usually a difference between what a client says they want, what they actually want, and what they need.

That is why every service we provide starts with a diagnostic.

Three answers to one question

Ask a client what they want and you will usually get the first answer. Spend time with them and you find the other two.

  • What they say they want. “We need a new website.” “We need a B Corp certification.” “We need an impact report by the end of the month.”
  • What they actually want. More of the right clients. Credibility with a funder. A team that tells the same story. Peace of mind that the organisation is doing things properly.
  • What they need. Often something different again: clearer positioning before any website, a stronger set of policies before any certification, usable data before any report.

None of this is anyone’s fault. People describe the solution they can already picture, not the problem underneath it. A good consultant’s first job is to close that gap before spending anyone’s time and money.

The “telemóvel estragado” effect

In Portuguese, we have a name for the children’s game where a message is whispered from one person to the next until it reaches the end of the line, completely changed: telemóvel estragado, or “broken telephone.”

Projects work the same way. The longer a misunderstanding drags on, and the more stakeholders get involved, the more the original message changes. A request passes from the founder to the programme lead, then to the consultant, then to the designer, the writer or the analyst. Everyone does their part well. By the time the work is delivered, it answers a question nobody was really asking.

The fix is not more meetings or longer briefs. It is understanding what is actually being said, by whom and why, before the message travels any further.

What a diagnostic does

A diagnostic is a short, structured assessment of where you are now: what is working, what is missing, what is unclear, and what should be fixed first. Depending on the job, it can include:

  • A review of existing strategies, reports, data and policies
  • Conversations with key people across the organisation
  • A mapping of current activities, systems and evidence
  • An assessment of gaps against a relevant standard or goal
  • A short list of priorities, risks and opportunities

It is scaled to the size of the job. For a small piece of work, it may be a few focused conversations and a document review. For a larger one, it is more structured. Either way, it is not a 40-page report. It is a clear picture and a practical next step.

What it looks like in each service

The focus changes with your goal. The purpose does not: to understand what you need before we build it.

Service What the diagnostic looks at
Strategy and Business Planning Material issues, stakeholder expectations, existing commitments, data and capacity.
Capacity Building What your team already knows, what it needs, and the real projects it will apply the learning to.
AI Governance and Responsible Adoption The tools and AI your team uses today, what data goes into them, the risks, the skills and who is accountable.
MEAL Goals, activities, existing data, reporting needs and how your team makes decisions.
Certification Readiness Current policies, practices and evidence, and the gaps against the standard.
Impact Communication The evidence you have, your audiences, your current messages and the claims you make.
Report Writing The reader, the purpose, the deadline and the data and stories available.

Why it saves time and money

A diagnostic can feel like an extra step, especially when there is pressure to deliver. In practice, it usually reduces wasted effort. It helps you:

  • Avoid buying or building systems you do not need
  • Focus limited team time on the highest-value gaps
  • Create a baseline before you measure change
  • Make realistic decisions about scope, timeline and budget
  • Get internal buy-in before asking people to change how they work

Most importantly, it prevents the most expensive outcome: investing in a solution that does not address the real problem.

What you get

At the end of a diagnostic, you should be able to answer:

  • Where are we now?
  • What is working?
  • What is missing?
  • What is the biggest risk?
  • What should we do first?
  • Who needs to own each action?

That is more useful than a long strategy that nobody reads, and it is the foundation for everything that follows.

Not sure what your organisation needs first? Book a diagnostic conversation.

Ready to talk about where you're headed?