Back to the episode map

Evergreen

How to Confront the Hard Problem First at Work

Confront a worsening problem by establishing facts, containing harm, choosing the right channel, assigning authority, communicating honestly, and measuring recovery.

Aug 4, 20265 min readBy Dalton Anderson

How to Confront the Hard Problem First

Confronting the hard problem first means making the facts visible, limiting further harm, choosing the right channel, assigning a decision owner, communicating honestly, and measuring recovery. It does not mean acting recklessly, humiliating people, or announcing a conclusion before the evidence is secure.

The practical goal is to shorten the time between the first credible warning and responsible action.

Name the problem without performing certainty

Write a one-page problem record. State what happened, what evidence exists, what remains unknown, who or what may be affected, which deadline matters, what is getting worse, and who currently owns the decision.

Separate observation from inference. "The release missed three agreed checks" is an observation. "The team does not care about quality" is an interpretation.

Give the record a date and update it. A hard problem often changes while people debate the original version.

Decide whether immediate containment is needed

Some problems allow analysis before action. Others require a temporary stop, access restriction, customer notice, safety step, financial hold, legal preservation, or incident process.

flowchart TD
    A["Credible warning"] --> B["Establish facts and uncertainty"]
    B --> C{"Immediate harm continuing?"}
    C -->|Yes| D["Contain through authorized channel"]
    C -->|No| E["Investigate with bounded deadline"]
    D --> F["Assign decision owner"]
    E --> F
    F --> G["Communicate decision and rationale"]
    G --> H["Recover, monitor, and learn"]

Containment should be proportionate and authorized. Stopping a production system, freezing money, suspending a person, or making a public statement can create new harm.

Cybersecurity incident practice offers a useful general structure. NIST's incident response recommendations organize preparation, detection, response, recovery, and improvement. The guide is for cybersecurity, not every management problem, but the disciplines of containment, communication, evidence preservation, recovery, and lessons learned transfer well.

Use the right channel

A routine project miss can be raised with the project owner. Fraud, harassment, discrimination, safety, privacy, legal, financial reporting, or regulated conduct may require a protected compliance, human resources, legal, audit, security, board, union, or government channel.

Do not conduct an amateur investigation that alerts a subject, destroys evidence, breaches confidentiality, or exposes a reporter. The one-page record should preserve what is known and route it to the authorized process.

Retaliation risk is part of the operating design. A company that says "speak up" but punishes the messenger will receive problems late.

Assign one decision owner

A problem can have many contributors and still need one person with authority to choose the response. The owner should know which decisions can be made, which require escalation, which resources are available, and when the next update is due.

Responsibility without authority creates delay. Authority without evidence creates arbitrary action.

The owner may delegate investigation and execution. The decision and accountability should remain visible.

Communicate bad news without false reassurance

State the fact, impact, action, owner, uncertainty, and next update. Do not fill an information gap with optimism or blame.

Different audiences need different detail. The delivery team may need the technical failure. A customer may need service impact and remediation. The board may need exposure, options, cash, and governance. A regulator may require a prescribed notice.

Legal review can shape language without turning the message into an evasion. If the facts are uncertain, say what is being investigated and when another update will follow.

Protect the ability to learn

Amy Edmondson's research on psychological safety and team learning found an association between a team's shared safety for interpersonal risk and learning behavior in a study of 51 work teams.

Psychological safety does not mean comfort, agreement, low standards, or freedom from consequences. It means a person can ask a question, admit an error, or raise a concern without expecting interpersonal punishment merely for speaking.

Accountability and psychological safety support each other when standards are clear and the response focuses on facts, decisions, and correction. Humiliation encourages concealment.

Choose a response that matches the problem

Possible responses include repair, rollback, customer remediation, staffing change, scope reduction, write-down, timeline reset, contract change, control redesign, product retirement, investigation, or closure.

Compare the options against safety, legality, customer harm, evidence, reversibility, cost, time, and the risk of waiting.

The fastest visible action is not always the fastest recovery. A rushed reorganization can hide the underlying failure. A temporary containment step can create time for a better permanent decision.

Measure recovery

Recovery needs a target, owner, date, leading indicators, stop conditions, and a way to confirm that the original harm is no longer continuing.

Track the corrected output, customer remediation, backlog, error recurrence, cash, control completion, staffing load, and any indicator that fits the case. Continue monitoring after the visible crisis passes.

Hold a review that asks when the first warning appeared, why it was not acted on sooner, which control failed, which incentive encouraged delay, what containment helped, what created new harm, and which change has an owner.

The book lesson and its boundary

Episode 102 draws its memorable language from Ben Horowitz's The Hard Thing About Hard Things. The publisher's book page establishes the work and author.

The public guide does not reproduce the book's language at length. It applies the underlying operating lesson: do not spread a known correction across months merely to avoid one painful decision.

That lesson is not universal permission to reveal confidential information, bypass process, or act before facts. The hard first action may be preserving evidence, contacting counsel, protecting a reporter, stopping work, or admitting that the team does not yet know.

The one-page standard

If the problem cannot be described plainly, it is hard to own. Write the record, contain authorized harm, assign the decision, communicate the truth that is known, and make recovery measurable.

Toughness is optional. Responsibility is not.

AI assisted with research organization, structure, drafting, and validation. Dalton Anderson remains the attributed author and final editorial authority. The transcript and linked public sources control factual claims. Publication remains unauthorized.

Sources

Follow the evidence.

  1. epa.gov: stationary enginesepa.gov
  2. gao.gov: gao 25 107172gao.gov
  3. spec.c2pa.org: Explainerspec.c2pa.org
  4. cdc.gov: fatigue workcdc.gov
  5. Current Google Search AI feature documentationdevelopers.google.com
  6. pubmed.ncbi.nlm.nih.gov: 22708885pubmed.ncbi.nlm.nih.gov
  7. fema.gov: lifelinesfema.gov
  8. pubmed.ncbi.nlm.nih.gov: 31864153pubmed.ncbi.nlm.nih.gov
  9. Google's guide to optimizing for generative AI featuresdevelopers.google.com
  10. energy.gov: powering americas ai future data center resource hubenergy.gov
  11. energy.gov: doe releases new report evaluating increase electricity demand data centersenergy.gov
  12. deepmind.google: synthiddeepmind.google
  13. content.naic.org: naic adopts first national climate resilience strategy insurance close coverage gaps and improvecontent.naic.org
  14. steveblank.com: whats a startup first principlessteveblank.com
  15. content.naic.org: resilience data visualization mapcontent.naic.org
  16. developers.google.com: google search and ai contentdevelopers.google.com
  17. ycombinator.com: jared friedmanycombinator.com
  18. Introducing Search Generative AI performance reportsdevelopers.google.com
  19. nist.gov: reducing risks posed synthetic content overview technical approaches digital contentnist.gov
  20. ycombinator.com: startup school videosycombinator.com
  21. spec.c2pa.org: charterspec.c2pa.org
  22. swissre.com: Natcat protection gapswissre.com
  23. fema.gov: requirementsfema.gov
  24. harpercollins.com: the hard thing about hard things ben horowitzharpercollins.com
  25. ibhs.org: wildland fire embers and flames home mitigations that matteribhs.org
  26. dash.harvard.edu: 13a7b031 0fdd 45ec a7e0 2b80e2bc679fdash.harvard.edu
  27. ycombinator.com: 8g how to get startup ideasycombinator.com
  28. deepmind.google: identifying ai generated images with synthiddeepmind.google
  29. pubmed.ncbi.nlm.nih.gov: 33749936pubmed.ncbi.nlm.nih.gov
  30. csrc.nist.gov: finalcsrc.nist.gov
  31. nibs.org: NIBS MMC MitigationSaves 2019nibs.org
How to Confront the Hard Problem First at Work