The author reflects on the difference between being right and being effective within corporate environments, particularly regarding "bad projects." Drawing from personal experience as a senior engineer, he highlights that while it’s tempting to voice concerns about projects that seem flawed, doing so can come with significant costs. He describes various dimensions of a bad project, including user experience issues, technical shortcomings, and misaligned political motives. The subjective nature of these judgments often means that what appears to be a bad project might not be recognized until much later. The author emphasizes the importance of strategic influence management. He likens influence to a bank account, where each time you voice a concern, you make a withdrawal. Minor issues cost small amounts, while significant objections to a VP's project can deplete your influence significantly. If you spend too much on minor issues, you risk political bankruptcy, where your opinions are disregarded, and your ability to effect change diminishes. He advises being humble and evaluating whether you genuinely have the expertise to comment on a project before doing so. Recognizing your limits and focusing your influence where it truly matters is essential for maintaining credibility and effectiveness in a large organization.