Flow Efficiency

Apply Niklas Modig & Pär Åhlström's flow-efficiency framework from "This is Lean — Resolving the Efficiency Paradox" (2012). Covers the central paradox (resource efficiency vs flow efficiency), the efficiency matrix, Kingman's formula and why high utilization destroys flow, the three laws of process dynamics (Little's Law, the law of bottlenecks, the law of variation), the "variation × utilization" killer combination, lean as an operational strategy not a tool, and the diagnostic vocabulary for explaining why "keeping everyone busy" actively harms delivery. Use when a team is busy but not ship

5 stars 2 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill flow-efficiency
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/flow-efficiency ~/.claude/skills/flow-efficiency

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Flow Efficiency (Modig & Åhlström)

Apply this skill when a team is working hard but delivering slowly, when management asks "why don't we just keep everyone busy?", when justifying WIP limits or visible slack, when explaining why throwing people at a project doesn't help, or when teaching the difference between *being efficient* and *delivering efficiently*.

## Core Philosophy

**The efficiency paradox:** organizations that obsess over keeping resources busy (resource efficiency) actually deliver more slowly than organizations that optimize for moving work through the system (flow efficiency). The harder you push utilization up, the longer flow times become.

**Two ways to be efficient.** Resource efficiency measures how much you use the resources. Flow efficiency measures how much of a flow unit's time is spent receiving value. These are different things, and they conflict.

**The fundamental insight:** processes are *systems*, and pushing utilization to 100% in a system with variation produces exponentially worse waiting times. This is not a management choice; it is a mathematical property.

**Lean is an operational strategy, not a toolbox.** The choice to optimize for flow efficiency over resource efficiency is the lean strategy. Kanban boards, value-stream maps, and 5S are *tools* in service of that strategy. Adopting tools without choosing the strategy is cargo-cult lean.
Read the full skill on GitHub

Details

Skill name
flow-efficiency
Path
plugins/engineering-practices/skills/flow-efficiency/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Flow Efficiency skill do?

Apply Niklas Modig & Pär Åhlström's flow-efficiency framework from "This is Lean — Resolving the Efficiency Paradox" (2012). Covers the central paradox (resource efficiency vs flow efficiency), the efficiency matrix, Kingman's formula and why high utilization destroys flow, the three laws of process dynamics (Little's Law, the law of bottlenecks, the law of variation), the "variation × utilization" killer combination, lean as an operational strategy not a tool, and the diagnostic vocabulary for explaining why "keeping everyone busy" actively harms delivery. Use when a team is busy but not ship

How do I install the Flow Efficiency skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Flow Efficiency popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Fractal Architecture

5

vnovakovits/claude-skills

Apply heuristics from Mark Seemann's "Code That Fits in Your Head" (2021) — fractal architecture, working-memory limits, cyclomatic complexity ceilings, vertical slices, encapsulation through invariants, functional core / imperative shell, checklists, and sustainable software engineering. Use when designing, decomposing, sizing methods/classes, deciding what fits in working memory, or evaluating whether code is sustainable over the long term.

Software Development

Event Storming

5

vnovakovits/claude-skills

Apply Alberto Brandolini's Event Storming — a collaborative modeling technique using domain events on sticky notes to discover business processes, identify bounded contexts, and design software collaboratively. Covers Big Picture, Process Modeling, and Software Design levels, the color-coded sticky-note grammar, the workshop flow, and how Event Storming pairs with DDD. Use when starting a new project, exploring a complex domain, finding bounded-context seams, designing aggregates, or surfacing hidden assumptions across business and tech.

Software Development

Grok

5

bolasblack/claude-skills

xAI Grok second opinion via the grok CLI — three modes. Review: independent diff review with a pass/fail gate. Challenge: adversarial pass that tries to break the code. Consult: ask Grok anything, with session continuity for follow-ups. Use when the user says "grok review", "grok challenge", "ask grok", or wants a second opinion from Grok.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.