
Retention Theatre: Why Companies Lose Good Engineers Whilst Pretending to Listen
Retention theatre explained through surveys, recognition schemes, pay, autonomy, trust, workload, management quality, and why strong engineers still leave.
Articles
Engineering practices are the repeatable habits that protect quality when delivery gets busy. The writing here looks at how review, documentation, and testing support sound technical judgement, clearer ownership, and work that other engineers can inherit without guesswork.

Retention theatre explained through surveys, recognition schemes, pay, autonomy, trust, workload, management quality, and why strong engineers still leave.

Why transformation programmes fail after the slide deck, covering ownership, governance, operating‑model change, vendor fragmentation, and delivery reality.

My view on product engineers and software engineers: how the remit differs, why organisational support matters, and what we need to learn after release.

Consultancies can unblock stalled programmes, but without ownership transfer and internal capability growth, rescue work becomes recurring dependency.

Deadline debt explained as hidden rework, incidents, technical debt, quality loss, and recovery cost when teams compress quality without recording trade‑offs.

Outsourcing can accelerate delivery, but if it replaces internal ownership, companies lose platform knowledge, leverage, and the ability to change safely.

The seniority trap happens when organisations hire experienced engineers for judgement, then deny authority, access, decision rights, and influence.

Companies talk about a high hiring bar, but weak offers, slow interviews, and vague criteria drive strong engineering candidates out long before a decision.

Cheap engineering can shrink payroll, but it often increases rework, instability, contractor spend, supplier dependence, and total delivery cost later.

Approach production observability in Next.js with contextual logs, traces, release markers, client errors, cache signals, build visibility, and business data.

AI‑assisted delivery can increase throughput, but cutting QA, accessibility, SEO, security, and exploratory testing in response is a costly mistake.

Underpaying senior engineers can look efficient on payroll, but often costs more through weaker hiring, slower delivery, contractor spend, and retention risk.

AI slop is a symptom of weak incentives, not just weak tools. This article links generic output to shallow briefs, poor review, and volume‑led metrics.

AI programmes are often adopted tactically, without enough governance for supplier risk, data exposure, quality, workforce impact, or board accountability.

As AI reduces friction in implementation, the value of architecture, review, domain judgement, mentoring, and failure analysis rises rather than falls.

Automation can save labour, but it also creates monitoring, exception handling, vendor, governance, and security costs that many business cases ignore.

AI knowledge retrieval can weaken organisational memory when summaries hide context, dissent, incident history, product reasoning, and uncertainty.
