The integration contract tests caught a breaking change the vendor did not announce. In growth (thread 2): The roadmap slide was fiction; the issue tracker was closer to reality. Sometimes the right answer is fewer features and clearer defaults.

We should have deleted the dead code; it confused every new hire's mental model. In growth (thread 2): The mentor who pair-reviewed my first PR set the tone for years after. We stopped confusing 'MVP' with 'prototype we will rewrite' without telling stakeholders.

We should have deleted unused circle invite tokens after events ended — stale links confuse newcomers measurably. In growth (thread 2): The integration that bounded queue depth prevented memory cliffs under spikes. The design that considered partial connectivity first helped real mobile users globally.

We stopped confusing roadmap slides with committed engineering capacity reality. In growth (thread 2): We learned that naming circle owners in the database export reduces support tickets about 'who can delete this' always. Rubber duck debugging worked because explaining forced us to notice gaps.

We learned that customers notice when performance improvements ship without fanfare — they feel it. In growth (thread 2): Good telemetry feels like magic once you stop flying blind during incidents. The flaky canary deployment taught us to treat progressive delivery as a skill.

We stopped shipping 'temporary' dashboards to execs that became permanent truth. In growth (thread 2): The architecture review that asked about cold start SLOs changed our packaging strategy honestly. The mentor who said 'show member overlap across circles without exposing PII' sharpened discovery privacy debates helpfully.

We learned that customers trust roadmaps that include maintenance and reliability work visibly. In growth (thread 2): The integration that bounded concurrency with semaphores prevented thread pool exhaustion quietly. Staging parity with prod sounds expensive until you price one bad release.

The architecture review that asked about cold starts changed our hosting choice honestly. In growth (thread 2): The mentor who said 'prove discovery helped joins, not just clicks' sharpened UX success metrics for CercleWork measurably weekly honestly always. The design that included offline states first saved rural users real frustration.

The quiet win was deleting an alert nobody had acted on in a year. In growth (thread 2): We stopped shipping 'temporary' admin impersonation without audit logs — compliance nightmare. We learned that small accessibility wins in admin tools help internal teams ship faster too.

We should have instrumented business metrics, not only technical ones. In growth (thread 2): We stopped treating 'tech debt paydown' as a bucket without measurable outcomes quarterly. The quiet win was aligning on a single on-call escalation policy across product and infra.

We learned that humour in demos is memorable when it illustrates a real constraint, not fluff. In growth (thread 2): The best teams celebrate deleting code as loudly as adding features sometimes. We stopped treating 'MVP' as an excuse to skip basic security hygiene on internal tools.

We should have named an owner for the cron job everyone assumed was automatic. In growth (thread 2): We learned that humour in retrospectives helps if it focuses on systems, not individuals' quirks cruelly. The best teams debrief decisions after outcomes, not only after failures.

We learned that writing 'why we are not doing X' prevents recurring debates monthly. In growth (thread 2): The migration that chunked batches avoided locking tables longer than maintenance windows. Small honest updates beat big silent gaps when stakeholders are nervous.

The integration that surfaced partial batch failures prevented silent under-billing in invoicing quietly. In growth (thread 2): The best postmortems include customer communication review, not only root cause. We learned that kindness in ticket triage reduces duplicate escalations surprisingly well.

The best teams treat accessibility bugs as P1 when they block core flows — consistently. In growth (thread 2): The mentor who said 'write the customer comms before you merge' improved launch discipline. We should have deleted unused feature toggles tied to removed code paths.