Make Work Visible
Apply Dominica DeGrandis's "Making Work Visible — Exposing Time Theft to Optimize Work & Flow" (IT Revolution, 2017; 2nd ed. 2022). Covers the five thieves of time (too much WIP, unknown dependencies, unplanned work, conflicting priorities, neglected work), how to expose and counter each, the book's own exercises (demand analysis, work item types, card design, workflow mapping, the five reasons we take on more WIP, the "Oh, By the Way" dependency matrix, the interruption reduction experiment, visualise priorities, the aging report), board design, line of commitment, flow metrics, the Time Thie
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill make-work-visiblegit 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/make-work-visible ~/.claude/skills/make-work-visiblePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Making Work Visible (Dominica DeGrandis) Use this skill when work is invisible, too much is in progress, or a team is busy but not finishing. The first move is always to show the work that exists, all of it, and the problems around it. Then manage what you can see. Source: **Dominica DeGrandis, *Making Work Visible: Exposing Time Theft to Optimize Work & Flow*** (IT Revolution, 2017; second edition 2022). Structure, exercise names and figure titles below are checked against IT Revolution's companion PDF for the first edition. Material from DeGrandis's later talks is marked as such. Exercise steps are paraphrased. ## Core ideas 1. **Five thieves steal time.** Too much WIP, unknown dependencies, unplanned work, conflicting priorities and neglected work. Naming the thief tells you which countermeasure to reach for. 2. **Too much WIP is the ringleader.** DeGrandis defines it as demand exceeding capacity and treats it as the thief that feeds the others. Conflicting priorities and unplanned work also push WIP up, so it is a hub, not the only root cause. 3. **Visibility comes before improvement.** A board shows the work, its state, and the problems delaying it. The team designs that board together through short exercises. 4. **Measure flow, not busyness.** Part 3 of the book is about metrics and feedback: flow time, lead and cycle time, WIP, aging, flow efficiency and batch size, reviewed in an operations review.
Details
- Skill name
make-work-visible- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/make-work-visible/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Make Work Visible skill do?
Apply Dominica DeGrandis's "Making Work Visible — Exposing Time Theft to Optimize Work & Flow" (IT Revolution, 2017; 2nd ed. 2022). Covers the five thieves of time (too much WIP, unknown dependencies, unplanned work, conflicting priorities, neglected work), how to expose and counter each, the book's own exercises (demand analysis, work item types, card design, workflow mapping, the five reasons we take on more WIP, the "Oh, By the Way" dependency matrix, the interruption reduction experiment, visualise priorities, the aging report), board design, line of commitment, flow metrics, the Time Thie
How do I install the Make Work Visible 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 Make Work Visible popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/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
Agent Retro
5vnovakovits/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
API Design
5vnovakovits/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.
Product Analytics
8Freddy-CHEN-ux/00_claude_skills
Framework for analyzing product usage data and identifying patterns. Use when performing deep analysis of user behavior and engagement metrics.
Kanban
5vnovakovits/claude-skills
Apply Kanban as a method for managing knowledge work, based on Marcus Hammarberg & Joakim Sundén's "Kanban in Action" (Manning, 2014) with David J. Anderson's foundational Kanban Method ("Kanban", 2010) and Klaus Leopold's "Practical Kanban" (2017). Covers the four foundational principles, six core practices (visualize, limit WIP, manage flow, make policies explicit, implement feedback loops, improve collaboratively), Kanban-board design, WIP limits and how to set them, flow metrics (lead time, cycle time, throughput, CFD), Little's Law, classes of service, cadences (daily standup, replenishme
Project Astrology Numerology
8Freddy-CHEN-ux/00_claude_skills
Expert astrological advisor (30+ years experience) for Cosmic Copilot - validates calculations, catches logic bugs, provides domain expertise for chart accuracy and interpretation. (project)
Browse the most popular Claude skills, all data & analytics skills, or write your own with the skills generator.