Achieving better outcomes in IT: eliminate Blind Spots

Peter Samson
Nov 4 · 1 min read

Blind spots are biases and assumptions that can narrow your vision and potentially influence your behaviors.

Whereas a photographer may use aperture to control depth of field (ie., how much is in focus), many in IT still attempt to make decisions with limited depth of field.

For example, a blind spot of most Enterprise Architecture (EA) programs is failing to understand and consider the constraints of the as-is IT landscape. The Architects should be using maximum depth of field when creating enterprise road maps and making strategic recommendations.

In 8folios.com we call it Dependency Awareness (pages 6–7).

Additional examples:

  • Planning to upgrade a core application. What else is impacted?
  • Applying software patches to everywhere a technology is used in the IT landscape. What might get missed?

Challenge project plans, road maps, and recommendations that lack depth of field.

The goal should be to bring everything into view to contain the complexity, prevent foreseeable risks from becoming incidents that impact your customers, and achieve better outcomes.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade