Contact us

How to Deliver Bad News Without Panic

by Eric Hanson, Backend Developer at Clean Systems Consulting

Breaking bad news is never fun.
Here’s a calm, practical way to handle it without losing your cool.

Pause and Prepare

Before you send that email or hop on a call, take a moment to think.

  • Understand the full scope of the issue
  • Know the impact on timelines, budget, or deliverables
  • Prepare a clear explanation of what happened and why

Key Tip: A little prep goes a long way in keeping your delivery calm and confident.

Be Honest, Clear, and Concise

Clients appreciate transparency. Avoid over-explaining or making excuses.

  • State the problem clearly in simple language
  • Avoid technical jargon that could confuse
  • Stick to the facts and avoid blame

Key Tip: Clear communication reduces panic on both sides.

Offer Solutions, Not Just Problems

Delivering bad news is easier when paired with actionable steps. Show you’re in control.

  • Suggest immediate fixes or workarounds
  • Offer alternatives to mitigate the impact
  • Outline next steps and timelines

Key Tip: Framing the issue with solutions shows professionalism and reassurance.

Stay Calm and Empathetic

Your tone matters. A composed delivery eases tension.

  • Speak slowly and avoid sounding defensive
  • Acknowledge the inconvenience to the client
  • Use “we” instead of “I” to emphasize collaboration

Key Tip: Empathy and calmness build trust even in difficult situations.

Follow Up and Keep Communication Open

After the initial news, maintain regular updates.

  • Confirm progress on solutions
  • Check in to answer questions or concerns
  • Reflect on lessons learned for future projects

Key Tip: Follow-up shows reliability and commitment, turning a negative into an opportunity for trust.

Final Thought: Delivering bad news isn’t fun, but preparation, honesty, empathy, and actionable solutions help you handle it gracefully—keeping both your client and your sanity intact.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Say Hej

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

API Documentation Is Not an Afterthought. It Is Part of the Design.

Documentation written after the API is already built reflects the API that exists. Documentation written during design shapes the API that should exist.

Read more

The Best Ways to Organize Your Freelance Workflow

Freelancing can feel like juggling a dozen balls while riding a unicycle. With the right workflow, you can keep everything moving smoothly—and stay sane.

Read more

Building a Webhook System in Spring Boot — Delivery, Retries, and Signature Verification

Webhooks are HTTP callbacks from your system to your customers' systems. Delivering them reliably — with retries, signature verification, and delivery tracking — requires more infrastructure than a simple HTTP call. Here is the complete pattern.

Read more

The Difference Between an API That Works and an API Developers Enjoy Using

Functional correctness is the floor, not the ceiling. The APIs developers choose to build on have properties that go beyond working — they are predictable, honest, and low-friction.

Read more