— A Human-Centered Look at Evidence and Numbers for People Feeling Crushed by Metrics


—

Meta Description

Why do EBPM (Evidence-Based Policy Making) and data-driven management so often end up exhausting people on the frontlines? From the perspective of a mid-career, severely disabled blogger, this article unpacks surface-level issues, deeper root causes, and structural problems, and offers practical, human-centered tips for management and team building.


—

Table of Contents

1. Why Do EBPM and Data-Driven Practices Create “Exhaustion”?【Intro】


2. What Is EBPM Really? Its Original Meaning and Common Misunderstandings
2-1. Definition of EBPM (Evidence-Based Policy Making)
2-2. EBPM Is an “OS (Mindset)” Rather Than a “Technique”


3. What Is Data-Driven Management? The Trap of “Metrics as the Goal”
3-1. The Usual Image of Data-Driven Management
3-2. The Typical “KPI for the Sake of KPI” Problem


4. EBPM and Data-Driven: How Their Relationship Gets Inverted
4-1. Originally: “EBPM = OS” and “Data-Driven = App”
4-2. When This Reverses, the Organization Becomes Used By Data


5. Surface-Level Problems: “We Have Data, but the Frontline Isn’t Improving”
5-1. Too Much Data, and No One Truly Looks at It
5-2. Even When KPIs Are Hit, All That Remains Is “So What?”
5-3. When Data Turns into a Stick to Beat People With


6. Deeper Root Causes: “Evidence” and “Hypotheses” Are Missing
6-1. No Shared Understanding of What “Evidence” Actually Is
6-2. Data Collection Without Hypotheses Becomes Just Post-Hoc Justification
6-3. The Structure Where Only “People Who Can Read Data” Hold Power


7. Structural Problems: The Organizational OS Is “Responsibility Avoidance” and “Short-Termism”
7-1. “The Data Made Me Do It” as a Responsibility-Evasion Device
7-2. EBPM Optimized for Short-Term Gains Eventually Breaks Organizations
7-3. No Clear Answer to “Whose Happiness Are We Maximizing?”


8. What a Severely Disabled Person Sees “Outside the Data”
8-1. The Light and Shadow of “Point-Based” Healthcare & Long-Term Care Systems
8-2. Invisible Costs Hidden in Night Shift Allowances and Staff Shortages


9. Using EBPM in Team Building: Turning Data into a “Mirror That Deepens Questions”
9-1. Data as Material for Deeper Questions, Not as the “Correct Answer”
9-2. Twisting Quantitative and Qualitative Data into a “Double Helix”
9-3. First Define: “What Does This Team Consider Good?”


10. Using EBPM in Management: From “Evaluation Tool” to “Learning System”
10-1. Don’t Use EBPM as a Whip for Judgment
10-2. How to Run EBPM as “Test Small, Learn Fast”
10-3. Organizations That Celebrate Failure Data Are Strong


11. Three Practical Steps You Can Start Tomorrow
11-1. Add Just One Phrase Before Showing Data
11-2. Add Stories to Numbers to Raise the Resolution of Data
11-3. Hold One Non-Negotiable “OS Line” Inside Yourself


12. Conclusion: Don’t Give Up on a Society Where Data Doesn’t Crush People


13. FAQ for People Struggling with EBPM and Data-Driven Management




—

1. Why Do EBPM and Data-Driven Practices Create “Exhaustion”?【Intro】

In recent years, terms like EBPM (Evidence-Based Policy Making) and
“data-driven management” have spread rapidly.

We hear:

“Let’s talk based on data, not gut feeling.”

“Let’s decide with evidence, not assumptions.”

“Let’s move from spirit and grit to scientific decision-making.”


On the surface, this sounds completely reasonable.

As someone who had a stroke (brain hemorrhage) in midlife and now lives with a severe disability,
I’ve personally experienced how important it is to face “data” head-on:

How much can I move today without wrecking tomorrow?

What kind of work rhythm allows me to stay healthy?

How effective is my rehab, really?


Trying to live only by “vibes” doesn’t work anymore. I know that all too well.

And yet, as a worker, as a family member, and as someone watching headlines about EBPM and data-driven reforms, I can’t shake this question:

> “If decisions are being made based on data,
why does life on the frontline feel so exhausting?”



We see things like:

The numbers are improving, but people keep quitting.

KPIs are being met, but the team atmosphere is deteriorating.

Everyone says “based on evidence,” yet somehow no one takes responsibility when it goes wrong.


In this article, I want to unpack this discomfort:

surface-level problems,

deeper root causes, and

the structural issues beneath them.


I’ll do it from the perspective of:

a mid-career, severely disabled person,

living in rural Japan,

working and watching the world as a blogger.


I’m not a researcher or a consultant.
I’m just one person trying to live and work with limited energy.

Precisely because of that, I want to talk about:

> “What does truly helpful EBPM for real workplaces look like?”



Not in abstract jargon,
but in language that feels close to real experience.


—

2. What Is EBPM Really? Its Original Meaning and Common Misunderstandings

2-1. Definition of EBPM (Evidence-Based Policy Making)

EBPM started as a term in government and public policy.
Literally, it means “evidence-based policy making.”

Put simply, the idea is:

> “Instead of relying on a leader’s gut feeling, ideology, or slogans,
let’s base policies on solid evidence and data.”



In its original form, EBPM involves steps like:

1. Clarify the objective

What exactly are we trying to improve?
(e.g., public health, educational outcomes, quality of welfare)



2. Form a hypothesis

Why do we think this policy or measure will help achieve that objective?



3. Gather evidence

Past data, surveys, academic research, field knowledge, etc.



4. Implement and measure

Carry out the policy and track what actually happens.



5. Reflect and revise

What worked well? What didn’t? Which assumptions were wrong?




The key here is that EBPM is basically:

> “A way of treating every decision as a testable hypothesis.”



It’s less about “finding the one correct answer”
and more about “learning continuously from what actually happens.”

2-2. EBPM Is an “OS (Mindset)” Rather Than a “Technique”

A common misunderstanding is treating EBPM as:

a set of statistical methods,

a data analysis toolkit, or

a way to design evaluation indicators.


But in reality, EBPM is closer to:

> “The operating system (OS) of how we make decisions.”



For example:

We keep questioning the objective.

We always articulate our hypotheses.

We commit to learning from the results.


If you introduce EBPM as a bunch of tools and templates without this OS, you’re almost guaranteed to create distortions on the frontline:

endless surveys with no clear purpose,

dashboards nobody really uses,

reports written just to “tick the EBPM box.”


The problem here is not EBPM itself,
but EBPM introduced as mere technique, without mindset.


—

3. What Is Data-Driven Management? The Trap of “Metrics as the Goal”

3-1. The Usual Image of Data-Driven Management

In companies and organizations, “data-driven management” usually means something like:

quantifying sales, profit, churn, overtime hours, NPS, etc.

using BI tools and dashboards to monitor those metrics in real time

quickly detecting anomalies and trends, then adjusting tactics


That sounds reasonable.
There are many companies that succeed with this approach.

But at the same time, another pattern emerges.

3-2. The Typical “KPI for the Sake of KPI” Problem

On the ground, you’ll often see:

Headquarters pushes down KPIs, and frontline teams just have to chase them.

No one explains clearly what ultimate purpose those KPIs serve.

Even when KPIs are met, no one can say,
“So, exactly whose life got better because of this?”


As a result, people start feeling:

> “We exist for the sake of the numbers.”
“It feels like I’m living for KPIs, not for real people.”



KPI stands for Key Performance Indicator:
it’s supposed to be a means to an end.

But slowly, quietly, it mutates into:

> “KPI achievement itself is the objective.”



There lies the biggest trap in data-driven management.


—

4. EBPM and Data-Driven: How Their Relationship Gets Inverted

4-1. Originally: “EBPM = OS” and “Data-Driven = App”

From what we’ve seen so far, the ideal relationship looks like this:

EBPM

The OS: the mindset and framework for making decisions

A cycle of:
Objective → Hypothesis → Evidence → Action → Learning


Data-Driven

The app: concrete tools and methods that support that cycle

Techniques for collecting, visualizing, and analyzing data



In other words:

> You install the data-driven “app”
on top of the EBPM “OS.”



That’s the healthy order.

4-2. When This Reverses, the Organization Becomes Used By Data

But in reality, the order often gets flipped:

> Data-driven practices (the app)
start acting like the OS that defines the organization’s values.



And then you see:

Anything that can’t be measured is treated as if it has no value.

Short-term metrics dominate over long-term health.

People worry more about “how to make the numbers look good”
than “how to genuinely improve things.”


At that point, the relationship between humans and data flips:

> It’s no longer “people using data,”
but “data using people.”



That’s when the exhaustion of the frontline deepens dramatically.


—

5. Surface-Level Problems: “We Have Data, but the Frontline Isn’t Improving”

Let’s first整理 (sort out) the visible symptoms.

5-1. Too Much Data, and No One Truly Looks at It

You see:

dashboards, weekly reports, monthly PDFs, endless spreadsheets

meetings where most of the time is spent “reporting the numbers”

very little time spent on “so what do we change based on this?”


So we end up with:

> “Data for the sake of data.”
“Reports for the sake of reports.”



There’s a flood of numbers,
but almost no upgrade in decision quality.

5-2. Even When KPIs Are Hit, All That Remains Is “So What?”

Common patterns:

The team hits the KPI, but the day-to-day reality feels worse.

No one can clearly say,
“This KPI being green means these people’s lives got better, in this way.”


So what remains is not satisfaction, but emptiness:

> “We hit the target, but… what was the point?”
“We did all that for the spreadsheet?”



When that feeling sticks,
no amount of “data is important” speeches will move people anymore.

5-3. When Data Turns into a Stick to Beat People With

You might hear phrases like:

“These numbers are terrible. What were you doing?”

“The data says this, so you have no argument, right?”


Data, meant to be a neutral mirror,
turns into a weapon.

People who are not comfortable with numbers think:

> “No matter what I say, I’ll just get hit with the data.”



So they shut down, stop speaking up in meetings,
and leave the conversation to the “data people.”


—

6. Deeper Root Causes: “Evidence” and “Hypotheses” Are Missing

Behind these apparent symptoms,
there are deeper issues.

6-1. No Shared Understanding of What “Evidence” Actually Is

Even in organizations that loudly promote EBPM,
“evidence” often means very different things to different actors:

Management:
“If sales and profit go up, that’s evidence enough.”

Frontline staff:
“Short-term numbers alone don’t prove this is sustainable; the burden is on us.”

Customers / users:
“Your survey scores don’t capture what matters most in our experience.”


If this gap remains,
the phrase “based on evidence” often ends up meaning:

> “We chose the numbers that suited people in power.”



6-2. Data Collection Without Hypotheses Becomes Just Post-Hoc Justification

In theory, EBPM should follow this chain:

> Hypothesis → Data collection → Testing → Revision



But in practice, we often see the reverse:

1. Collect any data that’s easy to measure.


2. From that pile, pick numbers that look “usable.”


3. Build a nice-sounding story around them for the report.



That’s no longer EBPM.
It’s basically:

> “Using numbers to justify decisions after the fact.”



6-3. The Structure Where Only “People Who Can Read Data” Hold Power

In organizations that champion EBPM and data-driven approaches,
the people who tend to gain power are:

those who are strong with stats and graphs, and

those who can present data compellingly.


Then:

The same data can be framed to support different conclusions.

The person with better framing and presentation skills “wins.”


So instead of “democratizing data,”
we get:

> “More power concentrated in the hands of those who can manipulate data well.”



People who are not good with numbers
start swallowing their doubts, thinking:

> “Well, if the data says so…”



And in that silence,
real issues remain buried.


—

7. Structural Problems: The Organizational OS Is “Responsibility Avoidance” and “Short-Termism”

If we go even deeper,
we reach the level of the organization’s OS—its built-in assumptions.

7-1. “The Data Made Me Do It” as a Responsibility-Evasion Device

EBPM should support responsible decision-making.

But it can easily be misused this way:

When things go well → “It was my bold decision.”

When things go badly → “Given the data at the time, it was the best choice.”


In that case, data becomes:

> “A system that lets everyone avoid responsibility.”



If we don’t clearly record:

who formed which hypothesis,

and how they interpreted which data,


then it becomes easy to say:

> “The system said so.”
“We just followed the data.”



And if no one owns the learning,
flaws are repeated.

7-2. EBPM Optimized for Short-Term Gains Eventually Breaks Organizations

Another structural issue is time horizon.

Under:

quarterly earnings pressure,

short-term KPIs,

“show results by next term” culture,


EBPM and data-driven practices often get steered toward:

short-term wins over long-term health,

instant visible metrics over slow, deep trust-building,

quick cost-cutting over sustainable workload and wellbeing.


On paper, the graphs look great.
But over years, the organization and its people wear out.

It’s not because EBPM is wrong.
It’s because the OS is:

> “Prioritize short-term visible success at all costs.”



7-3. No Clear Answer to “Whose Happiness Are We Maximizing?”

At the deepest level lies this question:

> “Whose, and what kind of happiness is this organization trying to maximize?”



Is it:

short-term returns for shareholders?

the career and reputation of top management?

the quality of life of employees and their families?

the experience and dignity of customers / patients / users?

the sustainability of local communities and the environment?


If this “objective function” is fuzzy,
then EBPM and data-driven management become tools for:

> “Maximizing the convenience and benefit of whoever holds power.”



That’s where the biggest distortion comes from.


—

8. What a Severely Disabled Person Sees “Outside the Data”

Let me shift the camera angle a little.

I had a brain hemorrhage in midlife,
and live with right-side paralysis and chronic fatigue.

As a patient, as a person with a disability, and as a family member,
I’ve watched healthcare, welfare, and workplaces
from a slightly “outside” position.

What I’ve felt strongly is this:

> EBPM-like thinking and data-driven systems
can be powerful tools for helping people—
but also sharp blades that cut them.



8-1. The Light and Shadow of “Point-Based” Healthcare & Long-Term Care Systems

In healthcare and long-term care,
many actions are converted into “points” (fees):

This treatment = X points

This working condition at this time = Y points

Under these conditions, this “add-on” is granted


It’s very EBPM-ish in one sense:
it tries to design a database of “what is worth how much.”

But from the frontline worker’s point of view, it can look like this:

Deep, non-billable human care gets deprioritized.

Staff feel pulled toward “what earns points,”
not necessarily “what the person in front of me needs most right now.”

Documentation and billing work for those points consumes time and energy.


A system designed with evidence and rationality
can end up producing:

> “Care for the sake of the billing system.”



Again, we see the flip:

> “Data created to protect people”
→ “A system that consumes people to protect the data.”



8-2. Invisible Costs Hidden in Night Shift Allowances and Staff Shortages

Reductions in night shift allowances
and changes in staffing levels
are often justified with “data-based rationalization”:

Labor costs higher than peer institutions

Statistical models say this staffing level is safe enough

Simulations show “no major risk”


But in the actual bodies and lives of the people doing night shifts,
there are “invisible data points”:

chronic sleep deprivation and fatigue,

physical symptoms that never fully recover,

frustration over losing time with family,

a deep sense of “I’m being taken for granted.”


As a person with a disability trying to protect my limited health,
watching family members do demanding shift work,
I can’t help but think:

> “We’re not counting the right things.”



EBPM and data-driven arguments have a constant risk:

> “Optimizing what’s easy to measure,
while ignoring what really matters but is hard to quantify.”



That risk increases exactly where the human cost is highest.


—

9. Using EBPM in Team Building: Turning Data into a “Mirror That Deepens Questions”

So how can we make EBPM and data-driven practices
an ally rather than an enemy for our teams?

9-1. Data as Material for Deeper Questions, Not as the “Correct Answer”

We need to change how we position data:

> ❌ Data = the correct answer
✅ Data = a mirror that deepens our questions



For example, when you see rising attrition:

You can say, “Clearly you’re not trying hard enough.”

Or you can say, “What stories might be hiding behind this number?”


Before showing numbers in a meeting,
a leader or facilitator can add just one sentence:

> “I don’t want to use these numbers to blame anyone.
I’d like us to use them to better understand what’s happening together.”



That alone changes the atmosphere.

People who were braced for another beating
may relax just enough to offer real insight.

9-2. Twisting Quantitative and Qualitative Data into a “Double Helix”

For team building, it’s crucial to twist:

quantitative data (numbers) and

qualitative data (words, stories)


into a double helix.

Quantitative examples:

attrition rate, overtime hours, survey scores, sales, error counts…


Qualitative examples:

things people say in 1-on-1s,

tone and content of casual conversations,

changes in expressions and silences,

the “feel” of the office after certain meetings.


You cannot truly grasp human realities from numbers alone.

The loop we want is:

1. Use numbers as a starting point for conversation.


2. From that conversation, discover new questions and patterns.


3. Turn those into the next metrics to track.



That back-and-forth is what gradually transforms a team.

9-3. First Define: “What Does This Team Consider Good?”

Before “E” in EBPM,
we actually need a “V”:

> V = Values: What does this team consider good?



Questions like:

If profit and human dignity collide, which do we prioritize?

If short-term results and long-term health/family time collide, what do we protect?

How do we recognize “invisible contributions” that don’t show up in metrics
(emotional labor, invisible support, knowledge sharing, etc.)?


If these values remain vague,
then no matter how sophisticated your EBPM process is,
the default will be:

> “Whoever is most powerful or loudest wins.”



On the other hand, a team that can say:

> “In these situations, we will prioritize X over the numbers.”



even if it’s just one sentence,
can maintain a healthy distance from data.


—

10. Using EBPM in Management: From “Evaluation Tool” to “Learning System”

At the management level,
we need to redesign what EBPM and data-driven management are for.

10-1. Don’t Use EBPM as a Whip for Judgment

In many organizations,
EBPM and numbers get tied tightly to “evaluation”:

If a measure succeeds → praise