Week 19 Day 2: The Leader Who Over-Specifies Kills Innovation

Over-specification is the quiet killer of innovation. It does not look like micromanagement because the instructions are reasonable and well-intentioned. But each additional instruction narrows the solution space. Use this technology. Follow this process. Structure it this way. Coordinate through this channel. By the time the team starts working, the solution space has been compressed to a single point -- and that point is the leader's predetermined answer, which may or may not be the best one.

Here is a practical test for over-specification. Take the last significant task you assigned and count the instructions. Then separate them into two categories: constraints (things that must be true about the outcome) and prescriptions (things that dictate the approach). Constraints sound like: 'Must handle 10,000 concurrent users.' 'Must deploy without downtime.' 'Must meet WCAG 2.1 accessibility standards.' Prescriptions sound like: 'Use React for the frontend.' 'Deploy using Kubernetes.' 'Follow the repository pattern for data access.' Constraints define the box. Prescriptions fill the box for the team before they start. If your prescriptions outnumber your constraints, you are over-specifying. In my experience, most leaders prescribe three to four times more than they constrain. The fix is to delete every prescription and ask: 'If the team chose a different approach that met all the constraints, would I accept it?' If the answer is yes, the prescription was unnecessary. If the answer is no, it was actually a constraint and should be reframed as one. This exercise alone -- recategorizing prescriptions as constraints where appropriate and deleting the rest -- will transform how your team approaches work.

The degrees-of-freedom metaphor maps precisely to what Ashby (1956) formalized as the 'Law of Requisite Variety' in cybernetics: a system can only effectively respond to environmental complexity if it has at least as much internal variety as the environment demands. Each prescription reduces the team's variety (available responses), which reduces its ability to match the variety of the problem space. This creates what Ashby called a 'variety deficit' -- the team has fewer options than the problem requires. Research by Csikszentmihalyi (1996) on creative flow demonstrates that optimal creative performance occurs when the challenge matches the skill level and the constraints are enabling rather than restrictive -- what he calls the 'flow channel.' Over-specification pushes teams below the flow channel into boredom (the task becomes mechanical) or out of the channel entirely into anxiety (the prescriptions conflict with the person's expertise). The constraint-versus-prescription distinction maps to what software engineers call the 'open-closed principle' (Meyer, 1988) -- systems should be open for extension but closed for modification. Constraints close specific dimensions (non-negotiable requirements) while leaving the system open for extension (method, approach, technology). Prescriptions close the system for both, eliminating the possibility of innovation.