liveBook · Manning

Unused skill

As explained in Build High Value Software Systems

Lean waste caused by failing to use people's knowledge, abilities, or judgment to improve outcomes.

Unused skill is Lean waste that occurs when skilled people spend their judgment compensating for system problems instead of solving meaningful problems. The work may matter, but it often needs automation or tooling rather than the expertise being spent on it. This is a system problem, not a judgment about an individual’s effort or competence. section 2.4.8 section 2.4

Amara’s Tuesday

Amara designed a complex logistics platform, but spends her day triaging flaky tests, reconciling configuration drift, manually checking a migration, answering questions already covered by a runbook, and commenting on formatting. She is busy and helpful, yet her architectural judgment goes unused. Applied to higher-value design decisions, that judgment could build on itself over time. section 14.1

Use questions like these to spot where expertise is being consumed by avoidable friction:

  • Where are skilled people acting mainly as glue or safety nets? section 2.4.8
  • Which tasks genuinely require human judgment, and which could be automated or handled with better tooling? section 2.4.8
  • What system change would help people focus on outcomes instead of compensation? section 2.4.8
Listing 14.1 Cognitive value log
# End-of-session capture
 
1. Commit WIP to a branch. Push. # Save state
2. Write: "Tomorrow, start with ___." # ← Capture 1: restart point
3. Tag today's work: # ← Capture 2: cognitive value
   - What required my judgment? ___
   - What just consumed my time? ___
4. Update ticket status. Add to friction log.

A cognitive value log helps distinguish work that required your judgment from work that merely consumed time, while recording a restart point and friction. section 14.1

How Build High Value Software Systems covers it

How deep it goes
Traces causes and software-team manifestations, from manual checks and firefighting to expertise concentrated on system quirks.
Examples
Contrasts Amara’s routine Tuesday tasks with the architectural judgment she could apply to system design.
What you can do after
Practice/perform a cognitive value log to distinguish judgment-requiring work from time-consuming work and record friction.
How it connects
Connects unused skill to Lean waste, TIMWOODS, waiting, defects, overprocessing, and inventory.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.