Saying the Obvious Thing
Stating the obvious thing in technical discussions is often more effective than being clever. Obvious solutions are frequently overlooked because they seem too simple, but they prevent miscommunication and save time. Engineers should overcome the fear of stating the obvious in meetings and code reviews.
Background
- The essay argues that in tech workplaces, the most valuable contribution is often stating something that everyone knows but nobody says aloud — the "obvious thing." The author, Sean Goedecke, is a staff engineer who writes about engineering management and organizational dynamics.
- Many tech meetings suffer from polite silence: engineers avoid stating uncomfortable truths (e.g., "this project will fail," "our architecture is fragile," "this deadline is unrealistic") because they fear looking naive, negative, or overstepping.
- The core insight: saying the obvious thing breaks groupthink and unblocks decisions. What feels risky to say is usually exactly what everyone needs to hear.
- The piece assumes familiarity with common workplace dysfunctions: too-long meetings, vague requirements, misaligned incentives between teams, and the social cost of candor in hierarchical or consensus-driven organizations.
- Practical takeaway: junior and senior engineers alike can add disproportionate value by developing the courage to name the elephant in the room, rather than waiting for someone more "senior" to do it.