liveBook · Manning

Visibility

As explained in Think Like a Software Engineering Manager

Work visibility is the degree to which an organization's ongoing efforts, progress, priorities, and constraints are observable to stakeholders.

Visibility makes engineering work easier for stakeholders to see and understand, especially when effort, priorities, and constraints are otherwise misjudged. Improving visibility can rebuild trust between engineering and leadership. section 1.3.7

Effective visibility can:

  • Show the effort behind deadlines and ongoing work. section 1.3.7
  • Clarify priorities so conversations about constraints and challenges become more reasonable. section 1.3.7
  • Highlight effective work, innovative solutions, and opportunities for collaboration. section 6.2.4
  • Set expectations for others and encourage engagement and useful discussion. section 6.2.4

Making excellent work visible

A manager publicly praised a senior engineer by explaining the problem, the challenges, and the engineer’s efforts. The recognition showcased effective work and gave colleagues a practical benchmark for excellence. Public acknowledgment can be powerful, but private recognition may be preferable in some situations. section 6.2.4

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains workplace effects through recognition examples but does not specify a measurement method for visibility.
Examples
Uses public praise, company-wide announcements, and an engineer’s work as concrete visibility examples.
What you can do after
Apply it through public acknowledgment to showcase effective work and surface collaboration opportunities.
How it connects
Connects work visibility with leadership, prioritization, constraints, recognition, collaboration, and engagement.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.