Kanso Framework - Liesware

Kanso is an open operational simplicity framework.

Friction in. Recovered capacity out.

Kanso makes operational friction visible, converts it into a monetary figure, and reduces what does not need to exist. It targets the hidden cost created by tools, handoffs, approvals, integrations, and processes that accumulate over time — the part of OPEX that traditional TCO models never break out.

Kanso does one narrow job. It works alongside Scrum, DevOps, ITIL, Lean, and Six Sigma, and does not replace them. The framework is published under the CC BY-SA 4.0 license.

Kanso (簡素) is one of the seven principles of Zen aesthetics: simplicity, the absence of ornament. Clarity and efficiency emerge once the unnecessary is removed and only the essential remains.

What Kanso Does↗

Friction is the natural resistance of an ecosystem to a new element. Kanso splits it in two because each kind requires a different response. Avoidable friction should be eliminated or redesigned. Unavoidable friction should be accepted, documented, contained, or optimized.

Friction	Definition	Criteria	Response
Unavoidable	Natural OPEX. The solution cannot work in your context without it	Essential nature, external mandate, universal technical limit, or a fix that costs more than the problem	Accept, contain, partially automate
Avoidable	Overhead. Exists only because the design, process, or integration is not right	Redundancy, missing standards, repetitive manual work, recurring errors, excess bureaucracy, poor integration	Eliminate, standardize, automate, redesign

Maintaining valid TLS certificates is unavoidable. The renewal work can still be automated. A DevOps engineer spending four hours a week fixing scripts because the ticket system does not integrate with CI/CD is avoidable.

Avoidable friction can emerge from accidental complexity, but the terms are not interchangeable. Complexity describes the system. Friction describes the operational resistance experienced while working with it.

Complexity is inevitable. Simplicity is intentional.

The Kanso Index↗

The Kanso Index (KI) is the framework’s central metric. It measures the share of scoped human operational cost consumed by avoidable friction. The Spanish edition calls the same metric the Índice Kanso (IK).

KI = ( Avoidable Friction Cost / Scoped Operational OPEX ) x 100

Avoidable Friction Cost = avoidable friction hours x hourly cost

The numerator and denominator must cover the same team, system, and period. Scoped Operational OPEX is the human operational cost being measured, not every accounting category included in corporate OPEX.

KI	Zone	Reading
<15%	Fluid	Most operational effort creates value. Unavoidable friction is under control
15–25%	Controlled	The system works, but efficiency leaks: duplication, manual work, poor integrations
>25%	Chaotic	A quarter or more of spend is overhead. The organization works harder to keep the system running than to move the business

TCO measures the total cost of owning a solution. KI measures avoidable human operational overhead within a defined scope. A system with low TCO can still have a high KI when its operation depends on manual work. KI is a directional instrument, not an accounting standard or an exact measure of productivity.

Artifacts↗

Artifact	Question it answers	Output
Kanso Index	How much are we losing?	One percentage, tracked over time
Friction Ledger	What happens and what does it cost?	A living inventory: hours, hourly cost, monthly cost, evidence, action
Friction RCA	Why does it happen?	Root cause at technical, organizational, and process level, with countermeasures
Harmony Board	Is it improving?	Monthly executive view: KI, hours recovered, value recovered, frictions closed

The Friction Ledger is a backlog for overhead instead of features. Each entry carries a cost, so complexity stops being a feeling and becomes a line item.

F-001 | CI/CD breaks credentials weekly | Avoidable | 40h/mo | $50/h | $2,000/mo
F-002 | Quarterly PCI audit             | Unavoidable | 20h/mo | $70/h | $1,400/mo
F-003 | Minor changes need 3 signatures | Avoidable | 15h/mo | $60/h |   $900/mo

Where Kanso Fits↗

Framework	Primary responsibility
Scrum	Delivery cadence and team practice
DevOps	Build, release, and operational feedback
ITIL	Service management and change control
Lean / Six Sigma	Process waste and variation
Kanso	Cost of operational friction, measured as OPEX overhead

Kanso replaces no methodology. It can attach to existing retrospectives, operational reviews, and planning cycles. It also defines a minimum review cadence through Kanso Sessions, Friction Reviews, Efficiency Syncs, and Strategic Reviews. Their frequency depends on whether the implementation is Lite, Core, or Full.

Kanso does one narrow job. It composes with the rest.

How It Works↗

detect -> classify -> quantify -> analyze -> act -> measure again
  |          |            |          |        |
tickets   avoidable /   hours x   Friction  eliminate
pipelines unavoidable   cost/h      RCA     standardize
logs                      |           |      automate
interviews                v           v      redesign
                    Friction Ledger  causes      |
                         |                       v
                         +--------------> Harmony Board

Detection comes from evidence, not opinion: ticket wait times and rework, pipeline durations and retries, incident frequency, and fifteen-minute interviews asking which steps are unnecessary.

Operating Principles↗

Four heuristics, applied in context rather than as absolute rules.

Principle	Rule
Simplicity over complexity	Given two paths, take the simpler one
Automation over manual work	Given a repetitive task, automate it
Standardization over redundancy	Given many ways to do one thing, standardize
Flow over friction	Given a blocked process, redesign for flow

Every non-essential variation is debt that accumulates.

Processes should adapt to the work, not the work to the processes. And not all friction can or should be removed — when three or more unavoidability criteria apply, the correct move is to contain it, not fight it.

Roles↗

Role	Owns	Does not own
Kanso Lead	Detection, documentation, facilitating RCA sessions, keeping the Ledger current	Which frictions to resolve, how to implement, prioritization, resources
Friction Resolvers	Executing countermeasures, documenting reapplication steps	Prioritization, deadlines, artifact format
Business Link	Executive sponsorship, priorities, resources	Implementation, facilitation

Friction Resolvers is a collective function of the operating team, not a hierarchy. In Lite, responsibility can rotate with capacity and context. Core and Full formalize the Kanso Lead role while countermeasure ownership remains with the relevant operating teams.

Maturity Levels↗

Start where your organization actually is.

	Lite	Core	Full
Team size	3–10	10–50	50+, multiple teams
Dedicated resources	0.05–0.1 FTE, rotating	0.1–0.6 FTE Kanso Lead	2–4 FTE Kanso Office + 0.15–0.2 FTE per team
Annual investment	$5K–10K	$15K–80K	$425K–1.3M
Setup time	1–2 weeks	1–2 months	3–6 months
Measurement	Manual, monthly, ±50%	Semi-automated, biweekly or weekly, ±30%	Telemetry, continuous, ±15%
Expected improvement	5–10%	15–30%	30–50%
Payback	Immediate	3–6 months	12–18 months

Lite runs on a shared spreadsheet and a one-hour monthly meeting. Core adds tagged ticket time and CI/CD log analysis. Full instruments systems with OpenTelemetry and distributed tracing to find handoffs.

Always start with Lite to validate cultural fit before committing budget.

What Friction Costs↗

Illustrative scenario.

A services company with 50 technical and administrative staff finds each person loses 15 hours a month to redundant tasks and interdepartmental waits. At an average $40 per hour:

50 people x 15 h/month x $40 = $30,000/month
                             = $360,000/year of unproductive OPEX

Reducing that friction by 40% would correspond to $144,000 a year in potentially recoverable capacity. Recovering time does not automatically reduce accounting spend. It may instead increase the capacity available for other work.

These figures illustrate magnitude, not accounting precision or guaranteed savings.

Why Kanso Exists↗

Operational knowledge should be accessible. Too many proprietary methodologies are common sense wrapped in jargon and expensive certification.

Kanso builds on Lean, Theory of Constraints, Agile, DevOps, and Systems Thinking. Its specific contribution is the systematization of operational friction as a measurable metric, and a method to reduce it: the Kanso Index, the Friction Ledger, and the Friction RCA.

The framework is at v0.9.6 and open for inspection, use, and modification. If you find value in these concepts, use them. If you improve them, share them.

Start Small↗

Pick one recurring friction the team already complains about.
Classify it: avoidable or unavoidable.
Multiply hours lost per month by the hourly cost of the affected role.
Run a Friction RCA on the avoidable one and ship a countermeasure.
Recalculate the Kanso Index next month.

Nothing here requires a reorganization or a new tool. It requires writing down what the friction costs.

Clear complexity is not good, but hidden complexity is dangerous.

View the Kanso Framework repository.