Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

To handle leaders who demand results but offer no support, teams should create "forcing factors." By consistently documenting and reporting progress, impediments, and value alignment, you build a historical record. When leaders eventually ask "Why didn't this get done?", the data forces their engagement.

Related Insights

To move beyond platitudes about collaboration, one 5x CEO had his executive team stack-rank one another on their effectiveness as team players. This process created a measurable, accountable system that surfaced hidden friction and spotlighted true team-first leaders.

To get an unfiltered view of progress and maintain urgency, Musk runs highly detailed, weekly engineering reviews. He bypasses direct reports and has their team members provide updates directly, with no advance preparation allowed. This allows him to mentally plot progress and intervene only when success seems impossible.

To drive data discipline, a RevOps leader should consistently review a core set of metrics with the executive team. This forces their own team to come prepared with answers. This scrutiny trickles down, as sales leaders learn which metrics matter and begin proactively reviewing them with their own business partners.

Projects fail not from lack of tools, but from a lack of executive sponsorship. Success hinges on leaders dedicating significant weekly time (e.g., half a day) to a few key projects, rather than passively sponsoring many with monthly check-ins. This deep engagement is a primary driver of success.

The report shows that while 76% of leaders are increasing pressure to prove Agile's ROI, only 15% actively shape its practices. This creates a dysfunctional dynamic where leaders demand results from a system they don't understand, guide, or help prioritize work for.

Go beyond visual roadmaps. Create a monthly written document for executives that explains *why* the roadmap changed, details priorities, and includes data from recent launches. This forces intentionality, builds trust, and fosters deeper, more accountable conversations with leadership.

When a manager assigns a task and never follows up, employees perceive it as unimportant. Consistent inspection—whether through formal reviews or informal check-ins—communicates that the work is a priority, which keeps the team honest and motivated.

To create a high-velocity culture, managers must actively pull deadlines forward. Don't just accept a proposed timeline. Ask what's blocking it, question the actual work hours required, and repeatedly challenge why it can't be done sooner.

Instead of telling a leader what they're doing wrong, ask what impact they want to have. By comparing their desired outcome (e.g., 'I want my team to bring me new ideas') with the actual result (e.g., 'no one speaks up'), the leader is intrinsically motivated to identify and correct the behaviors causing the gap.

Executives crave predictability, which feels at odds with agile discovery. Bridge this gap by making your learning visible. A simple weekly update on tested assumptions, evidence found, and resulting decisions provides a rhythm of progress that satisfies their need for oversight without resorting to rigid plans.