The Vanity Metrics of Innovation: When Being Busy Starts Looking Like Impact

100 participants.
20 startups.
10 workshops.
15 partnerships.
5 programs completed.

We see numbers like these everywhere in startups, TBIs, innovation programs, government, and ecosystem building.

And I’ll admit it: I’ve done it too.

I’ve celebrated the number of people reached, events conducted, startups supported, and activities completed.

For a long time, I thought these numbers were enough to show progress.

But eventually, I started asking a different question:

What actually changed because we did all of this?

That question changed how I think about metrics.

We’re Good at Counting What We Can See

Activities are easy to count.

An event happened.
We take photos.
We count participants.
We post the highlights.
We write the report.
Then we move on to the next activity.

There’s nothing wrong with documenting these things.

The problem starts when activity becomes the definition of success.

A workshop can have 100 participants.

But did they learn something?

Did they apply it?

Did their business improve?

Did they actually change something because of the workshop?

The 100 participants are real.

But the number alone doesn’t tell us what happened after.

Startups Do This Too

Startups have their own version of vanity metrics.

“We have 10,000 users.”

Sounds impressive.

But then the questions start:

How many are actually using the product?

How many come back?

How often do they use it?

Are they solving the problem we built the product for?

Are they willing to pay?

Are users recommending it to others?

Having 10,000 users is an important number.

But users acquired is not the same as users who actually get value from the product.

The same thing happens with startups saying:

“We launched.”

“We have an app.”

“We have 5,000 downloads.”

“We gained 20,000 followers.”

These numbers can tell us something.

But they don’t tell the whole story.

The better question is:

What changed for the user because this product exists?

TBIs Can Fall Into the Same Trap

Technology Business Incubators can also become very good at measuring activity.

Number of startups incubated.

Number of trainings conducted.

Number of mentors engaged.

Number of events organized.

Number of participants.

Number of startups graduated.

All of these are useful to track.

But imagine two incubators.

One incubator supported 100 startups through 30 activities.

Another supported 30 startups but helped several of them validate their products, find customers, secure funding, commercialize technologies, or build sustainable businesses.

The activity numbers tell only one part of the story.

For an incubator, we should also ask:

What happened to the startups after we supported them?

Did they progress?

Did they validate their ideas?

Did they gain customers?

Did they generate revenue?

Did they raise funding?

Did they create jobs?

Did they survive?

Those are harder questions.

But they tell us much more about whether incubation is actually working.

Government and Innovation Programs Face the Same Challenge

This is especially visible in government programs.

We conduct a training.

We conduct a workshop.

We organize a summit.

We support entrepreneurs.

We create partnerships.

We launch a program.

Then we report the numbers.

500 participants reached.

20 activities conducted.

10 partner organizations.

100 entrepreneurs trained.

These numbers are important for documenting what was done.

But government programs exist for a reason.

The bigger question should be:

What changed because the program existed?

Did businesses adopt something new?

Did entrepreneurs start or improve their businesses?

Did a government process become better?

Did a community gain access to something they didn’t have before?

Did organizations collaborate in ways they weren’t able to before?

Did the program solve the problem it was created to solve?

That’s where the conversation needs to move.

Activity → Output → Outcome → Impact

One simple way I’ve started thinking about this is:

Activity → Output → Outcome → Impact

For example:

Activity:
Conduct 10 entrepreneurship workshops.

Output:
300 people participated.

Outcome:
100 participants applied what they learned to their businesses.

Impact:
Those businesses improved their operations, increased revenue, created jobs, or achieved another meaningful result.

The first two are relatively easy to measure.

The last two require us to follow up.

And that’s exactly why they’re harder.

But difficulty shouldn’t be the reason we stop measuring them.

So What Needs to Change?

I don’t think the answer is to stop counting activities.

We still need to know how many people attended, how many programs we delivered, how many startups we supported, and how many partnerships we created.

But we need to connect those numbers to what happened next.

Instead of only asking:

How many attended?

Ask:

What did they do after?

Instead of:

How many startups did we incubate?

Ask:

How did those startups progress?

Instead of:

How many users do we have?

Ask:

Are those users getting value from the product?

Instead of:

How many events did we organize?

Ask:

What became possible because we brought these people together?

Instead of:

How many partnerships did we create?

Ask:

What did those partnerships actually produce?

The shift isn’t from metrics to no metrics.

It’s from counting activity to understanding progress.

The Photo Is Not the Impact

I still take photos.

I still celebrate events.

I still share milestones.

I’ve been on both sides of the camera—facilitating workshops, speaking, mentoring, judging, supporting startups, and working on ecosystem programs.

Photos are useful.

They document that something happened.

But a photo of 100 people in a room doesn’t tell us whether those 100 people moved forward.

Documentation proves that something happened.

Impact tells us whether it mattered.

What I’m Trying to Ask More Often

This doesn’t mean every activity needs an immediate measurable impact.

Change takes time.

But it does mean we should start designing our programs, startups, and initiatives with the next question in mind:

What happens after this?

Because a full calendar doesn’t necessarily mean a strong ecosystem.

A large user base doesn’t necessarily mean a successful product.

A completed program doesn’t necessarily mean a successful intervention.

And a room full of people doesn’t necessarily mean meaningful change.

The numbers are not the problem.

The problem is when we stop at the numbers.

Maybe instead of only asking:

“How much did we do?”

We should also ask:

“What is different now because we did it?”