01
TestOpsy
Identify the failure modes, their causes, and the signals that will show whether quality is improving.
Software so bad, it's good.
Start with a TestOpsy.
When releases slow down, defects escape, or confidence drops, a TestOpsy examines the technical and organizational system behind the symptoms.
From findings to working changes
Each service stands on its own. When a problem crosses boundaries, TestOpsy, Advisory, and Implementation can connect the investigation to the decisions and working changes that follow.
02
Advisory
Decide what to change, what to defer, how to sequence the response, and what evidence should guide the work.
03
Implementation
Turn the selected recommendations into working changes across code, tests, documentation, tooling, and delivery systems.
Proof in practice
Mailinator: from an outdated document to an aligned developer experience
An outdated-documentation project exposed a missing API source of truth, broken endpoints, and four outdated SDKs. The work continued through specification, documentation, SDK repair, testing, publication, and measurement.
Founder-led by Chris Kenst
The Bad Software Company is founded by Chris Kenst, a software quality leader, writer, open-source contributor, and former President of the Association for Software Testing. Chris writes about software engineering, AI, systems thinking, and quality at Kenst.com, and created TestingConferences.org to help the software community discover conferences and learning opportunities.