We scan new podcasts and send you the top 5 insights daily.
Mike Dalton describes a CEO's casual idea that became a project; when the team showed it would not make money, the CEO said it was just an idea and accepted the finding. He says the best CEOs are careful about sharing ideas because people overinterpret them. Without a feedback mechanism, one sentence can redirect everyone.
Product leaders often feel they must present a perfect, unassailable plan to executives. However, the goal should be to start a discussion. Presenting an idea as an educated guess allows for a collaborative debate where you can gather more information and adjust the strategy based on leadership's feedback.
Senior leaders should directly engage with "boots on the ground" employees to get unfiltered information. This bypasses the "game of telephone" where middle management can dilute or distort the reality of what's working and what isn't, especially during high-intensity periods like M&A integration.
As seniority grows, a leader's casual thought can be misinterpreted as a direct order, derailing a team. To counter this "executive megaphone" effect, leaders must be explicit about their intent by labeling all feedback as either an "idea," a "suggestion," or a required "action item."
An Amazon executive told Jeff Bezos he had "enough ideas to destroy Amazon." An endless flow of ideas from leadership, even good ones, can overwhelm a team, create backlogs, and cause constant distraction, ultimately hindering progress and adding no value.
Leaders can reduce team anxiety and prevent misinterpretation by explicitly categorizing input. 'Do' is a direct order (used rarely), 'Try' is an experiment, and 'Consider' is a low-stakes suggestion (used 80-85% of the time). This ensures a leader's random thoughts aren't treated as gospel.
Don't pitch big ideas by going straight to the CEO for a mandate; this alienates the teams who must execute. Instead, introduce ideas casually to find a small group of collaborative "yes, and" thinkers. Build momentum with this core coalition before presenting the developed concept more broadly.
Feedback often gets 'massaged' and politicized as it travels up the chain of command. Effective leaders must create direct, unfiltered channels to hear from customers and front-line employees, ensuring raw data isn't sanitized before it reaches them.
When executives push broad, substance-less ideas like "add AI" or "users want personalization," it's often a setup. If the project fails, the idea is deemed great while the team's execution is blamed, despite the original directive being meaningless or misguided.
Frontline builders almost always recognize a failing project before managers do because they feel their passion waning after trying multiple angles. Leaders should focus on cultivating a safe environment where team members can openly admit early on that an idea is falling flat and suggest stopping it.
To ensure a culture of honest feedback, a CEO should pitch a convincingly presented but terrible idea. Firing team members who agree with it serves as a "simple test" to eliminate sycophants and identify those who will challenge leadership, which is critical for innovation and avoiding groupthink.