Lior Barak

The Method · Impact Operations

Run your data portfolio the way you already run every other corporate investment.

Impact Operations is a management method, not a software tool. It provides your leadership team with three financial metrics, a clear decision sequence, and an executive review rhythm, ensuring data investments receive the exact same capital scrutiny as any other line item on your balance sheet. Your team learns to run it. Then I leave.

I. Flipping the Pyramid

Value first. Then capability. Technology last.

Most organizations spend quarters debating warehouse vendors, storage architectures, and migration timelines while the core value question waits. The method permanently flips this sequence.

First, the business names the exact decision a data product serves and what that decision is worth. Second, the organization verifies that the team possesses the skills, ownership, and capacity to capture that value. Only then does anyone discuss the technology required to build it. The engineering conversation still happens; it just happens last, and it is brief, because everyone already understands what the work is for.

II. Three Hidden Bills

Three costs you are paying right now. You have felt all of them. The method prices them.

01

The Friday morning workaround

It is Friday morning at 9:40. Your finance lead is not analyzing strategic results. She is reconstructing them inside a custom spreadsheet she built herself, cross-checking data that a central system product was supposed to deliver. Ask her why, and you get a shrug: 'It's faster if I just do it manually.'

That shrug is the sound of an invisible cost being absorbed by your operating margin. Multiply those hours across every analyst, marketing lead, and operations manager running the same quiet workarounds, price them at loaded payroll rates, and you get a monthly bill that appears on no technology invoice. You are paying twice: once for the data team to build the asset, and again for your business teams to work around it.

The MetricHours lost to manual workarounds × loaded hourly payroll rate = a monthly euro figure, broken down by team and product, that your CFO can audit directly against payroll.

02

The budget that only moves forward

Every budget review, the data infrastructure line is slightly higher. Every line item has an articulate defender and a plausible engineering reason. Nothing is ever removed. You sign the approval with a feeling you cannot act on: somewhere in that stack, capital is funding capabilities nobody would choose to build today.

That feeling is correct. Every data product continues to drain capital long after the launch party ends: server compute, storage space, support tickets, and the engineering hours required to fix pipelines when they break. Products get added constantly. Products almost never get retired.

The MetricOne verified monthly carrying cost per data product, everything included, mapped directly against its business yield. Keep-or-kill choices become a clear financial comparison instead of a political argument.

03

The busy team that ships nothing new

You request a new strategic data asset. The answer from engineering is consistent: 'The team is completely at capacity.' You look over and they clearly are; nobody is idle, everyone is working hard, and the sprint tickets are full. Yet, nothing new has shipped to production in two quarters.

What is happening is that the size of the portfolio has consumed the team. Background maintenance, minor pipelines breaking, and custom hand-holding requests eat up the engineering hours quietly. The team ends up defending what already exists instead of building what is coming next, and no one explicitly chose that trade-off. It happened one unvalidated request at a time.

The MetricA single operational capacity score tracking where engineering hours actually go versus where strategy requires them to go, making team availability a clear number with a trend instead of an emotional debate.

III. The Decision Rhythm

A decision rhythm, not a slide deck.

Data points alone change nothing; your company already has dashboards. The method installs the concrete decisions around the numbers.

New data requests must pass a clear business value test before they consume engineering hours. Existing data products are evaluated, carrying cost against operational yield, on a strict interval. Products that stop earning their position are retired deliberately, with an owner and an off-ramp date, rather than lingering on the payroll. The entire review runs in the same financial language your board already uses, keeping the conversation tied to capital allocation.

I watched this rhythm work perfectly once, in a place that had nothing to do with data. A Michelin-starred kitchen, thirteen complex dishes leaving the pass at once: no chaos, no backlog, no shouting. The secret was not harder work or more expensive stoves. It was the Head Chef's daily discipline of removing dishes that took too long and dropping ingredients that no longer earned their place on the menu.

Most corporate data functions have no Head Chef. They have a line of very busy, very skilled technicians trying to satisfy an endless queue of incoming tickets. The method installs the missing role: not a person, a rhythm. A menu that gets curated, on a schedule, by the people who own the budget.

IV. Structured Retirement

Data products age. The method notices.

Three specific operational signals flag a data asset for executive review: user usage dropping below the threshold it was built to serve, support incident volumes rising, and monthly carrying costs exceeding the value of the decisions it informs.

When an asset crosses these boundaries, it triggers a documented review with a named business owner. What survives, earns its place on the balance sheet. What does not, exits through a structured off-ramp: dependencies mapped, downstream users notified, and engineering capacity fully recovered. No product dies politically, and none survives politically either.

V. Designed to Leave

An education-led integration built so you don't need an advisor long-term.

Phase 1

Surface the Numbers

We calculate the three costs together: the workaround bill, the per-product carrying weight, and the team's true capacity split.

Phase 2

Run the Rhythm

Your data and finance leaders run the strategic review cadence with me in the room, embedding the habits until the allocation choices come naturally.

Phase 3

Independent Operations

Your team operates the full method completely independently. If leadership shifts, the successor inherits an audited portfolio, clear performance signals, and a boardroom that already reads the numbers.

VI. Where Technical Frameworks Stop

Why traditional tools miss this gap.

Framework
What it measures
What it cannot see
Cloud Cost Management (FinOps)
Monitors server invoices and query optimization.
It cannot see the payroll hours your business teams burn on manual workarounds.
Engineering Metrics (DORA, Tech Debt)
Track deployment speed, repository health, and pipeline uptime.
They cannot see the shadow processes frontline teams build around the data platform.
Data Maturity Models
Measure the volume of data tooling you have installed.
They ignore whether keeping that massive footprint alive is the exact thing paralyzing your team's innovation.

Each tool is useful inside its specific lane. None of them prices your data portfolio as corporate capital. That is the operational gap this method fills.

Three ways in

Where is your data portfolio today?

Building or Migrating

The Prevention Blueprint

You are about to commit capital to an infrastructure migration, a stack overhaul, or an AI-agent rollout. Before your engineers write a single line of code, we install the financial rules that govern what earns a place in the new architecture.

1-Month Rule Foundation + Ongoing Strategic Steering Cycles · CEO + CFO

What stays when we are done:
  • →A clear financial bar every data product must pass before it enters the new stack.
  • →Keep-or-kill decisions governed by structural rules, not political capital.
  • →An honest assessment of what your team can carry before you add technical weight.
Set the bar before you build →

Running and Tracking

The Hidden Cost Recovery

Your data budget grows every quarter, yet frontline teams are still fixing numbers by hand in spreadsheets. Those manual hours run on your payroll. I locate them, calculate them, and isolate the exact leakage.

4-Week Capital Diagnostic + Multi-Month Capacity Verification · CEO + CFO

What stays when we are done:
  • →A precise euro figure for the hours your business teams spend compensating for data gaps.
  • →A monthly operational review your own people keep running after the engagement ends.
  • →An actionable roadmap with the first three months fully mapped for your team to execute.
Find the leak →

Institutional Transformation

The Data Capital Program

Your data lead reports in sprint velocity and engineering metrics. Your CFO tracks margin contribution and capital efficiency. Neither can make an allocation decision together. This program installs a single, unified financial language.

6 to 8-Month Embedded Integration · Executive Board

What stays when we are done:
  • →One set of numbers connecting boardroom strategy directly to weekly engineering tasks.
  • →A live view of what every data asset costs to carry against its explicit business return.
  • →Structured validation cycles that test value before major engineering capital is deployed.
Run data like the rest of your P&L →

The Next Step

Book a 30-minute alignment call.

No pitch decks. No marketing slides. Bring the portion of your data spend you can't quite defend, and we'll locate the leak together.

Book Your 30-Minute Alignment Call →