Hard Call

What Is Hard Call?

Hard Call is a Claude Code skill designed to support leaders facing the most challenging decisions—those with no clear, painless options. Accessible via the /em:hard-call <decision> command, this framework addresses scenarios where every alternative involves significant trade-offs: layoffs, executive departures, product shutdowns, and strategic pivots. Such decisions are not hard because of ambiguity in the data, but because of their emotional, organizational, and often irreversible consequences. Hard Call guides users through a structured approach for making these choices, aiming to help find the "less wrong" answer when no good options exist.

Why Use Hard Call?

Difficult decisions are an inescapable part of leadership and product development, especially in high-growth and high-stakes environments. What makes these decisions uniquely hard is not a lack of information, but the human and strategic costs involved. For example, terminating a beloved product may be necessary for company survival, but it disappoints customers and demoralizes the team. Delaying such choices tends to worsen the situation—what could have been a minor course correction becomes a major crisis.

Hard Call provides a repeatable, systematic process to:

• Minimize regret and error through structured analysis
• Reduce emotional bias and indecision
• Act proactively, rather than reactively
• Protect organizational health by facing hard truths early

By embedding the Hard Call skill into your workflow, you ensure that even the most painful decisions are made thoughtfully, transparently, and with full awareness of their impact.

How to Get Started

To use Hard Call, integrate the skill from its GitHub repository into your Claude Code environment. Once installed, invoke the command as follows:

/em:hard-call <decision>

Example usage:

/em:hard-call Lay off 20% of the engineering team to extend runway by 12 months

The skill will guide you through its decision-making framework, prompting you to consider the key factors and consequences relevant to your scenario.

Key Features

• Reversibility Test: The framework begins by assessing whether the decision can be undone. If reversible, experimentation is encouraged. If not, the process emphasizes caution and thoroughness.
• Human Impact Analysis: Special attention is given to the effect on individuals and teams, acknowledging that real people bear the costs.
• Bias Reduction: By structuring the process, Hard Call helps users recognize and counteract personal biases, such as emotional attachment or avoidance.
• Timing Guidance: Encourages proactive action—most hard calls are made too late, increasing the eventual pain.
• Clear Prompts and Documentation: Each step in the process is clearly documented, allowing for transparent communication with stakeholders or board members.

Best Practices

• Be Honest About Irreversibility: Use the reversibility test rigorously. Avoid rationalizing a decision as reversible when it is not.
• Document Your Reasoning: Capture the rationale at each step. This not only aids clarity but also provides a record for future reference or post-mortems.
• Engage Key Stakeholders Early: Solicit input from those most affected or whose judgment you trust, but do not use this as an excuse to delay.
• Act Decisively Once Ready: Once the process points to a "less wrong" answer, execute swiftly. Prolonged indecision compounds harm.
• Follow Up: After making the call, monitor outcomes and communicate transparently about what was learned and why the decision was made.

Practical code usage with documentation:

## Example:

Using Hard Call in a decision support script

decision = "Shut down product X due to declining revenue"

response = em_hard_call(decision)
print(response)

## Output might prompt:
## Step 1:

Is this decision reversible? (yes/no)
## Step 2:

Who is affected and how?
## Step 3:

What are the long-term implications?
## ...and so on

Important Notes

• Hard Call is not a substitute for leadership judgment; it is a structured aid to support better decision-making under pressure.
• The skill is most effective when used early in the decision cycle. If you find yourself avoiding a hard call, leverage the framework immediately.
• Documentation and transparency are encouraged throughout the process, but sensitive decisions (such as personnel changes) must be handled with confidentiality and empathy.
• Integration into your development or leadership workflow can help inculcate a culture of timely, considered decision-making, reducing organizational drift and regret.
• Regular review of past decisions made using Hard Call is recommended to refine your judgment and improve future outcomes.

By systematically applying the Hard Call skill, leaders and developers can navigate the most challenging crossroads with greater clarity, accountability, and confidence, even when there are no good options on the table.