To empower your team, enforce the '1-3-1 rule' for problem-solving. Before anyone can escalate an issue to you, they must define the one problem, research three potential solutions, and present their single best recommendation. This forces critical thinking and shifts the team from problem-spotters to problem-solvers.

Instead of optimizing a hundred small tasks, focus on the single action that creates the most leverage. Citing Tim Ferriss, Dave Gerhardt uses this question to identify the core task that, if completed, would simplify or eliminate many other items on the to-do list.

Not all tasks are equal. Focus on "compounding" activities—small, high-leverage actions like creating templates or establishing processes. These tasks, like compounding interest, deliver growing returns over time and create a bigger impact than completing numerous low-value items, fundamentally shifting how teams approach their work.

Prioritize projects that promise significant impact but face minimal resistance. High-friction projects, even if impactful, drain energy on battles rather than building. The sweet spot is in areas most people don't see yet, thus avoiding pre-emptive opposition.

Focus on the root cause (the "first-order issue") rather than symptoms or a long to-do list. Solving this core problem, like fixing website technology instead of cutting content, often resolves multiple downstream issues simultaneously.

Avoid the trap of building features for a single customer, which grinds products to a halt. When a high-stakes customer makes a specific request, the goal is to reframe and build it in a way that benefits the entire customer base, turning a one-off demand into a strategic win-win.

Not all business problems are created equal. Time savings often translate to five-figure cost savings, which may not be compelling. The most powerful executive problems are "six-figure problems"—major risk mitigation (avoiding lawsuits), significant revenue generation, or replacing other large costs.

In environments with highly interconnected and fragile systems, simple prioritization frameworks like RICE are inadequate. A feature's priority must be assessed by its ripple effect across the entire value chain, where a seemingly minor internal fix can be the highest leverage point for the end user.

A superior prioritization framework calculates your marginal contribution: (Importance * [Success Probability with you - Success Probability without you]) / Time. This means working on a lower-priority project where you can be a hero is often more valuable than being a cog in a well-staffed, top-priority machine.