Do you feel pressure or do you apply pressure — screenshot of a16z.com

Do you feel pressure or do you apply pressure

This a16z post argues that CEOs must proactively apply pressure by delegating issues with clarity and accountability, rather than passively feeling overwhelmed by internal complaints. It's about taking ownership of solutions and pushing them down the chain.

Visit a16z.com →

Questions & Answers

What is the core message of "Do You Feel Pressure or Do You Apply Pressure"?
This article discusses a fundamental principle for CEOs: they must actively apply pressure by delegating problems and setting clear expectations, rather than allowing themselves to be overwhelmed by internal complaints and criticisms. It posits that a leader's role is to drive solutions down the organizational chain.
Who is the target audience for this Ben Horowitz article?
This article is primarily aimed at CEOs, founders, and senior executives in growing companies, particularly those struggling with increasing internal complaints and challenges. It provides guidance on effective leadership and delegation strategies.
How does this approach to leadership pressure differ from typical management styles?
This approach emphasizes a proactive delegation of problem-solving with specific, actionable directives and accountability, contrasting with more passive management styles that might absorb internal pressure or delegate vaguely. It advocates for the CEO to define the problem parameters rather than just handing off an abstract issue.
When should a CEO apply the "apply pressure" strategy described in the article?
A CEO should apply this strategy when facing escalating internal complaints, feeling overwhelmed by company issues, or noticing a loss of confidence within the leadership. It's particularly useful when problems are complex, cross-functional, or lack clear ownership.
What practical advice does the article give for delegating abstract problems like "product quality" or "customer churn"?
For abstract problems, the article advises framing them with specific examples, quantifying issues where possible, and requiring detailed proposals for solutions from the responsible teams. For cross-functional issues, it suggests bringing relevant executives together to agree on common definitions and objectives with firm deadlines.