Noise Institute

Quantify the cost your dashboards miss.

For owners, CEOs and COOs in service firms, SMEs and SSC/GBS/BPO operations: ONI shows where decisions stall, work comes back, and leadership time turns into operating cost.

Book diagnostic call View ONI readout
01Decision delaysWho blocks the result and why.
02ReworkWhere work comes back after handoff.
03ROIWhat to reduce first.
Noise Institute logo

Cost readout

ONI shows which losses are worth reducing first.
Decisions stallCost rises when approval has no owner.
Work returnsHandoffs without criteria create rework.
Load growsMeetings replace decisions and reduce throughput.

Company

We build operating-cost diagnostics for executive teams.

Noise Institute helps owners, CEOs, COOs and CFOs see where the organisation loses time, margin and throughput through decisions, handoffs and unclear accountability. We do not sell opinions about workplace culture. We provide the basis for a decision: what to measure, what to reduce and where budget has the strongest return.

Measurewhere cost is created
Rankwhat has the strongest ROI
Reducefirst losses with measurable impact
For the board A business case instead of an opinion about chaos.

We show whether the issue is large enough to deserve budget.

For the COO A map of where work loses pace.

We separate activity from results: decisions, handoffs, process and coordination load.

For the CFO A reduction sequence with ROI logic.

Reduction starts where the impact on time, cost and risk is strongest.

The instrument

The number has to lead to a decision, not another deck.

You get a 0-100 score, cost sources and a reduction sequence. No soft diagnosis and no language that cannot stand up in front of a CFO.

0-100 ONI score ROI action order 4-6w diagnostic
ONI sample readout
Operational Noise Index diagnostic snapshot
62
High cost
6D friction map
selected 71
Communication load

Leadership time goes into coordination that does not end with a decision.

Select a cost driver
Communication load71
Decision delay68
Handoff cost59
Priority reduction path
  1. 1. Reduce meeting load around approval loops.
  2. 2. Move status traffic out of leadership forums.
  3. 3. Define one owner for weekly decision updates.
ONI means

Operational Noise Index

Measures

Decision delay, handoff cost, process complexity, communication load, political drag and cognitive safety.

Outputs

A 0-100 ONI score, cost drivers and a ranked action order by ROI.

Built for

Service firms, SMEs, SSC, GBS, BPO and operations where work crosses teams, tools and governance layers.

The Problem

The most expensive problems are the ones nobody is measuring.

Dashboards show activity, but they rarely show the cost of decisions waiting, handoffs without clear ownership and rework.

ONI locates those losses and ranks what to remove first by impact on cycle time, cost and margin.

Quick cost test

Price the meetings that do not end in decisions.

This is a fast scale check. It does not value the whole operation, but it shows whether management overhead is already a CEO, COO or CFO topic.

Estimated annual cost 152k EUR about 13k EUR per month, before delay and rework cost.
12.4h
in meetings, per employee, per week

Illustrative diagnostic figure for mid-sized operations. The practical working target sits below 8 hours.

4.1
approval layers per operational decision

A practical working target is around 2 layers. Each additional layer usually lengthens cycle time and flattens accountability.

2.8d
average handoff delay between teams

Most cross-team transitions lose 1–3 days waiting on someone to act. Multiply by handoff count to see real cycle cost.

Decisions take weeks, not hours

Escalation paths are unclear. Ownership is shared into ambiguity. The cost of delay is real — and nobody is measuring it.

Teams align more than they deliver

Coordination overhead grows silently with every new layer of management, tool, or process — until it outweighs the work itself.

Process complexity compounds invisibly

Every workaround becomes a permanent fixture. Every exception hardens into policy. The total cost is never calculated.

The Instrument

Operational Noise Index

ONI quantifies systemic friction across six structural dimensions. Each captures a distinct source of noise that erodes throughput, ownership and decision speed.

Score interpretation
0–35 Low — clear navigation, lean processes
36–55 Moderate — friction present but manageable
56–75 High — coordination dominates execution
76–100 Critical — system overload, lost decision capacity
Definition

Operational noise is the measurable friction that makes work slower, less clear and more expensive than the process design suggests.

Instrument

ONI converts that friction into a 0-100 score across six dimensions, so leaders can compare where noise concentrates and what to reduce first.

Output

The diagnostic produces a score, sub-scores, decision and handoff maps, and a prioritized reduction roadmap for operations leadership.

weight 20%

Decision Noise

Complexity of decision approvals, escalation chains, and reversals. How many layers and loops does one decision require?

weight 20%

Handoff Friction

Delays and friction at ownership transitions between departments or teams. How much cycle time is lost when work crosses boundaries?

weight 15%

Process Complexity

Redundant steps, rework loops, and unnecessary complexity in operational workflows. How much work is wasted on process friction?

weight 15%

Communication Load

Meeting density, channel fragmentation, and coordination overhead. How much time is spent coordinating instead of working?

weight 15%

Political Noise

Decisions distorted or delayed by internal politics, turf protection, or image-driven initiatives unrelated to outcomes.

weight 15%

Cognitive Safety

Ability of employees to surface problems, challenge decisions, and report systemic issues early — before they compound.

A composite score from 0 to 100

Each dimension is assessed through structured surveys, process mapping and leadership interviews. Interpretation thresholds are working ranges refined through diagnostic use. Once measured, noise becomes reducible.

Sample case

They thought meetings were the problem. ONI showed the issue started after sales handoff.

This is an example of the diagnostic format, not data from a specific client. It shows what the buyer pays for: knowing whether to fix the visible symptom or the place where cost is actually created.

Company
Business services
about 500 people · sales, service and delivery across several countries
What they came with
"Too many meetings, too few cases closed"
managers wanted fewer meetings and better communication
What we checked
3 cases from request to invoice
50+ responses · 8 interviews · handoff documents between teams
Key finding
Meetings were the symptom
cost appeared earlier: delivery received cases as "ready", while key decisions were still missing
How the company saw it
  • 1
    "People talk too long about simple issues"
    Pressure was building to shorten meetings and reduce the number of people involved in decisions.
  • 2
    "Delivery is not fast enough"
    At first glance, delay seemed to sit with the team responsible for delivering the service.
  • 3
    "Service keeps going back with questions"
    Returns to sales looked like a lack of independence, so the obvious fix was communication training.
What the diagnostic showed
  • 38%
    Cases started without complete inputs
    Price, scope, decision owner or customer confirmation were missing. Delivery could not start with delivery work. It started with chasing answers.
  • 12.4h
    Per person each week went into clarification, not service work
    Meetings were not the source of the problem. They were how the company repaired an incomplete case start.
  • 1
    One rule was missing: when is a case ready?
    Each team had a different definition of "we can start". That created rework, calls and customer waiting time.
Decisions after the audit
Do not start by cutting meetings

That would remove the visible symptom and leave people with the same missing information.

Create "ready for delivery" conditions

A case does not move forward without price, scope, decision owner and customer confirmation.

Assign an owner for exceptions

When something is missing, the team knows who decides: fix it, send it back to sales or approve an exception.

What the company receives in this audit
ONI scorea number showing the scale of the problem and where the company loses the most.
One-case mapfrom request to invoice: who waits, who asks, what comes back for correction.
First decisionswhat to change now, what not to touch yet and who owns exceptions.
Owner or board summarya plain explanation of why the problem sits somewhere else than it first appeared.

Numbers are examples of the method format, not data from a specific client. In a real audit, amounts, priorities and decisions are calculated on the company's own data.

Engagements

Budget should buy a decision, not a report.

Pricing is visible because this is an investment in recovered time, margin and leadership capacity. Diagnose first. Reduce only where cost and payback are clear enough to defend.

Why pay To identify cost that can actually be removed.

Not for slides. For a decision on whether the issue is material and where reduction has the strongest return.

What you get ONI score, decision maps and action sequence.

Material that lets the COO, CFO and board discuss numbers, not impressions.

How budget stands up Time, margin, risk and ROI in one view.

The reduction scope follows business impact, not a process wish list.

01 — Diagnose

Diagnostic Audit

Best when you need to know whether the issue deserves budget: what it may cost, where it is created and what decision the board should make.

Single-case check 7-10 days
PLN 6-9k
SMEs / teams 10-80 FTE
  • →1 real case that stalls, comes back or needs too many conversations
  • →Short pulse survey for people involved in the case
  • →2-3 interviews with people seeing the issue from different sides
  • →Decision: run full ONI, fix one thing or stop the topic
Light 4-5 weeks
PLN 12–18k
SMEs / operations 30-200 FTE
  • →Survey on calibrated 25 items
  • →1 critical sales, service or operational workflow mapped
  • →3 leadership interviews
  • →ONI score + 3 decisions with a business rationale
Most chosen
Standard 5-6 weeks
PLN 20–40k
Operations 200–1000 FTE
  • →Survey + 50+ respondents
  • →2–3 workflows mapped
  • →5–8 leadership interviews
  • →Decision Flow + Handoff Friction maps
  • →Reduction roadmap ranked by cost, risk and ROI
Enterprise 6-8 weeks
PLN 45–90k
Operations 1000+ FTE
  • →Multi-unit ONI assessment
  • →Cross-region comparison
  • →10+ leadership interviews
  • →Board briefing: cost, risk, decision
  • →Tailored governance recommendations
02 — Reduce

Reduction Programs

For organizations that already have the evidence and want the result back: shorter decisions, less rework and lower management load in the places with the highest cost.

Process Simplification Sprint
PLN 25–70k
4–6 weeks

Remove redundant steps, exceptions and rework loops that slow 1-2 critical workflows. Outcome: fewer returns and faster closure.

Decision Flow Fix
PLN 40–120k
8–12 weeks

Restructure approval layers, escalation paths and boundary ownership. Outcome: shorter decisions and less work returning for correction.

NoiseCut Program
PLN 60–150k
12–20 weeks

Reduction across 3+ dimensions. Diagnostic-led, implemented and measured. Target: identify and reduce the highest ONI drivers, with impact shown in numbers.

03 — Monitor

Index Monitoring

PLN 8–25k / year
Semi-annual or annual

Track ONI over 6 or 12 months. Detect friction drift before it compounds. Quarterly briefings, structural change alerts.

04 — Equip

Leadership Workshop

PLN 6–18k
1–2 days · in-person or remote

Translate ONI into a shared language of decisions, cost and accountability for operating leaders.

Start with a scoped diagnostic conversation

Bring one workflow where the result depends on decisions by many people.

In 30 minutes we check whether the issue has scale, whether it can be measured and whether ONI makes sense as an investment.

Request scoping call

All ranges in PLN, exclusive of VAT. Final scope and pricing depend on organization size, geographic complexity and access required. Quoted on a per-engagement basis after a 30-minute scoping call.

Method proof

Built in operations, not presentations.

ONI was shaped for environments where results depend on decisions, handoffs, ownership and control points at team boundaries. That is where time disappears before a dashboard can explain it.

Readsreal operating flow
Turns intocost, risk and decisions
Founder website
Selected requirement

Reduction

The diagnosis must point to reducible delay, rework, meeting load and escalation drift.

SignalDelay, rework, escalation drift
OutputRanked reduction path
Leadership useChoose what to remove first
Kamila Drygalska, founder of Noise Institute

Who stands behind it

ONI was built inside operations.

My name is Kamila Drygalska. For twenty years I led and improved operations in SSC, GBS and BPO environments across EMEA, including interim roles, where one case can pass through several teams, countries and systems before it reaches the customer. I kept seeing the same pattern: the report looked fine, while work was stuck, returning for correction or waiting for someone to decide.

ONI was built from that experience, not from theory. It is a method for measuring operational noise that I built, tested and improved in real organizations under performance pressure. Some company names are not public because of NDA boundaries. In one global financial group, I increased a key operating metric by 10 points in three months by changing how work moved, not by adding people. Today I do the same for other companies: with a number and a map instead of a feeling.

20 yearsEMEA operations: SSC, GBS, BPO
Practice-built methodtested in real organizations under pressure
Diagnostic, not a reportscore, map and first decision
Full professional profile: kamiladrygalska.com

Evidence from live operations

We do not show logos. We show mechanisms.

CEOs and COOs do not need another list of familiar brands. They need to know whether the method detects costs that can be reduced without guesswork or blame.

Dashboard reality vs. operational realityFlow test

Closure activity looks healthy while clients experience delay, rework or missing ownership. ONI tests whether metrics describe flow, not just activity.

Ownership across countries and teamsTransfer friction

Transfers expose dependencies in local knowledge, escalation paths and handoff quality. ONI separates transfer execution from the friction the transfer creates.

Commercial intent into executable workControl points

Customer promise, compliance logic, invoicing, tools and escalation do not land in one operating design. ONI makes missing control points visible before they become client issues.

External shock translated into executionRisk to workflow

Regulatory or geopolitical shifts create cost when teams lack a clear path from policy change to decision. ONI checks whether risk becomes workflow, not interpretation load.

Demand shock and prioritisationCapacity logic

Unclear systems hide trade-offs until teams absorb them through overtime, meetings and reactive escalation. ONI turns capacity pressure into prioritisation logic leaders can act on.

Our operating view

Four assumptions that keep ONI close to business results

01

Strategy is rarely the biggest problem.

Most leaders know what they want to do. The cost appears when decisions wait, ownership blurs, and teams spend management time keeping work moving.

02

The problem has to be quantified.

"Too many meetings" and "slow decisions" are not enough. Executives need cost: delay, rework, lost leadership time and ROI impact.

03

Fix the mechanism, not the atmosphere.

We look at decision rights, handoff rules and process logic because that is where lost time, rework and margin pressure are created.

04

Cost cuts without diagnosis can make performance worse.

If the operating system is unclear, a smaller team carries the same delay and rework with less buffer. Measure first. Remove the waste. Then decide.

FAQ

Questions a serious buyer would ask

How do I know this will not become another report?

The scope ends with a decision: where the cost sits, what should be reduced first and what business effect is realistic. The report carries the decision. It is not the product.

How do you calculate ROI if the problem is hidden?

We combine survey data, workflow mapping and leadership interviews. We estimate the cost of delay, rework and coordination time, then rank actions by impact on results.

What do I actually receive after the diagnostic?

A 0-100 ONI score, six sub-scores, a decision map, a handoff map, ranked reduction priorities and an executive briefing: cost, risk and the recommended decision.

How much time does this take from my team?

Usually 4-6 calendar weeks for a Light or Standard diagnostic, depending on response volume, interview scope and data access. Your team contributes a short survey, a few real workflow walk-throughs and leadership interviews. The work is designed to measure overhead, not create more of it.

Will people answer honestly if the topic touches leadership decisions?

Survey results are aggregated and comments are not reported in a way that identifies individuals. We ask about cost mechanisms, not blame. Without that, the data would be useless.

Does ONI make sense outside large SSC or GBS environments?

Yes, if the company has repeatable processes, several roles in one workflow and hidden cost in decisions, handoffs or rework. The scope is adjusted to the organization scale: from one critical SME workflow to a multi-unit comparison.

Does ONI work if we run several countries and systems?

Yes. That is one of the strongest use cases. ONI compares cost mechanisms across units instead of pretending every country and team works the same way.

How are you different from Big Four or continuous improvement teams?

We do not begin with a transformation agenda or a catalogue of improvements. We first test where the cost is created and whether reduction has a return. If the issue is not material, the recommendation can be no larger programme.

What happens after the diagnostic?

We either stop at the board decision or move into reduction: simplifying process, shortening decision paths, cutting rework or monitoring ONI after the change.

Ready to see where operational drag is costing you?

Start with a 30-minute scoping call. We will look at one real workflow, the decisions around it and whether ONI can produce a clear ROI case.

1 workflow to inspect 3 questions on cost and decisions 1 decision whether ONI fits
hello@noise-institute.com Visit Kamila's website

Response within 48 business hours · Engagements available across EMEA