Skip to main content

> Term

Lighthouse Diagram

A high-level, idealized architectural diagram often used in presentations that lacks technical detail or implementation.

Detailed Explanation

A lighthouse diagram is a vision of how the system *should* look in a perfect world. It features clean boxes, simple arrows, and zero edge cases.

While useful for executive alignment and securing funding for large refactoring projects, these diagrams are notoriously useless for the engineers actually building or maintaining the system.

Why It Matters

It creates a dangerous disconnect between management's understanding of the system (clean, simple, modular) and the engineering reality (messy, coupled, legacy).

Common Failure Mode

Executives promise aggressive timelines based on the simplicity of the lighthouse diagram, entirely missing the hidden complexities of data migration and legacy decoupling.

Practical Example

A diagram shows a single box labeled 'Legacy Data Migration' pointing to a clean 'New DB', completely hiding the reality of five years of undocumented business logic scattered across thousands of stored procedures.

Production Manifestation

Found in slide decks, all-hands meetings, and the 'Vision' folders of corporate wikis.

Frequently Asked Questions

What is Lighthouse Diagram in short?

A high-level, idealized architectural diagram often used in presentations that lacks technical detail or implementation.

What is the most common failure mode?

Executives promise aggressive timelines based on the simplicity of the lighthouse diagram, entirely missing the hidden complexities of data migration and legacy decoupling.

AI Summary

A high-level, idealized architectural diagram often used in presentations that lacks technical detail or implementation. It creates a dangerous disconnect between management's understanding of the system (clean, simple, modular) and the engineering reality (messy, coupled, legacy).