Everyone's CV says "delivered transformation." Nobody's says "deleted a live server on Black Friday."
That's the gap Tech Confessions was built to close. Last week in Manchester, four speakers stood up and did something most people spend their careers avoiding: talked publicly, in detail, about the moments that didn't go to plan.
Here's what came out of it.
1. The email you send in anger can outlive the mistake that caused it
Mark's confession wasn't really about the technical mistake, it was about what happened after.
Early in his career, he ended up with access to a button he was never supposed to have. When it caused a problem during peak trade time, serious enough that the CEO got personally involved, he had to retrace his steps, quietly go back in, and unpick what he'd done. Everything came back, but the moment stuck with him for a different reason.
Frustrated at feeling undervalued and overlooked as a junior developer, he sent an email to the whole company about it. Years later, when he applied for a CTO role, that email came back to bite him, a curt, unhelpful response from someone who clearly remembered it.
The lesson: don't cut corners, and don't take a shortcut on something you're not the subject matter expert on. But just as importantly, don't burn a bridge in a moment of frustration. You don't know who's still standing on the other side of it years later. When Mark did own up and admit he was wrong, he found the support around him was more forgiving than he expected.
2. Culture decides whether people tell you the truth
One speaker's confession started as a student, working near a row of server trolleys. He hit the emergency stop button. Every server went down.
He panicked, and told security there'd been a power cut. His boss found out later he was actually the one who'd sorted it, and thanked him for "saving the day."
Years later, in a different job, a live server went down entirely, the whole website, offline for three hours. This time, he did something different: he owned up immediately.
The lesson: he wouldn't change a thing about owning up the second time, it turned out fine, and it always does better than the alternative. But the real point he made was about culture. People only admit mistakes quickly if they trust the environment will let them. If the culture punishes honesty, people will hide problems for as long as they can, and that costs far more in the long run than the mistake itself.
3. The mistake matters less than who's around you when it happens
Brett's story is the one everyone in the room still talks about: cancelling 37,000 warranties instead of one. He selected all instead of a single row, ran the action, and watched the counter climb far longer than it should have. "Why is it taking so long" is, in hindsight, one of the worst thoughts you can have mid-mistake.
He was candid about it: he wasn't great at his job at the time, and looking back, he was genuinely underprepared for how to handle the situation once it happened.
The lesson: what actually saved him wasn't skill in the moment, it was being fortunate enough to know the right person at the right time. His biggest takeaway wasn't about the technical fix. It was that surrounding yourself with the right people matters more than most people think, especially when things go wrong.
4. The best technical solution isn't always the best business decision
The last story was the highest-stakes: a product built from the ground up after regular outages made a rebuild unavoidable. The team spent months, and millions, building a technically strong solution, while a competitor built something cheaper, faster, and less "perfect," and scaled with it.
By the time the rebuild was finished, it was too late. The company got overtaken, then bought out. Job losses followed.
The lesson: technical quality isn't the same as business timing. Being laser-focused now, later in his career, this speaker was clear about what he'd taken from it, the best engineering answer can still be the wrong business answer if it takes too long to ship. It was a painful growth opportunity, but one he says he learned more from than almost anything else in his career.
The theme underneath all four
None of these stories were really about the technical failure. They were about what happened next, whether people owned it, who was around them, and whether the culture they worked in made honesty easy or expensive.
That's exactly why Tech Confessions exists: the moments that never make it past the group chat, let alone a LinkedIn post, are usually where the real lessons live.
Thank you to our speakers for putting it all on the table, and to AND Digital for hosting and sponsoring the evening.
More confessions to come.