# Work Visibility Makes Friction Discussable ## Summary Work visibility is not surveillance. It is a way to make queues, handoffs, uncertainty, blockers, invisible work, and decision delay discussable. When friction is visible, the team can improve the system instead of blaming people for absorbing it. ## Claim status Type: Owlery synthesis grounded in flow-of-work and coordination practice. Evidence base: Practice patterns where hidden work, waiting, unclear dependencies, and invisible handoffs create friction that cannot be improved until it is made visible. Confidence: High as a practical lens; medium for specific system diagnosis. Use as: A lens for making work, waiting, and coordination cost discussable without blaming people. Do not use as: A reason to create surveillance, micro-management, or reporting theatre. ## Source lineage Primary lineage: Flow, work-visualisation, constraints, and coordination-practice traditions. Related Owlery synthesis: Coordination cost, hidden work, late discovery, queues and waiting, and work intake readiness. What Owlery adds: Owlery frames visibility as a social and coordination condition, not merely a board or dashboard practice. What Owlery does not claim: Owlery does not claim all work must be made visible in the same way or at the same level of detail. ## Owlery synthesis When work is invisible, friction becomes personal. When work is visible enough, teams can discuss the system rather than guessing about effort, commitment, or competence. ## Use with care Do not use visibility practices to monitor individuals, expose people without safety, or add administrative load that does not improve decisions or learning. ## See Also - [[Work That Looks Busy Can Still Be Messy]] - [[Invisible Gaps Create Operational Drag]] - [[Messy Work Visibility Review]] - [[Flow]] ## Coordination burden extension Visibility should help answer: - what is active? - what is waiting? - what is blocked? - what is unclear? - what depends on whom? - what decision or knowledge is missing? - what is aging silently? Use [[When Work Is Scattered Everywhere]] and [[Team Cognitive Load Scan (20 min)]] when scattered work is making shared thinking expensive.