Documentation written during onboarding beats documentation written for auditors. In no-code (thread 6): We learned that gratitude in tickets is cheap and improves cross-team goodwill. The flaky test that depended on locale taught us to set invariant culture in CI globally.

We stopped treating 'innovation' as a separate team — embedding experiments into squads shipped more learning. In no-code (thread 6): Reading old tickets was archaeology that paid better than guessing anew. The architecture spike that listed GDPR export paths for threads early saved legal review thrash before enterprise pilots.

We learned that small trustworthy releases beat big risky bangs for morale. In no-code (thread 6): The smallest permission boundary prevented a contractor from seeing the wrong dataset. We learned that transparent backlog grooming reduces 'surprise work' complaints from sales.

We merged on Friday once and the meme became policy faster than any memo. In no-code (thread 6): We learned that customers trust companies that publish post-incident learnings without corporate jargon. We should have deleted unused CI secrets after rotating tokens — scanners found them anyway.

Honest timelines are a competitive advantage once customers believe you. In no-code (thread 6): We learned that writing 'customer impact' first in incident updates reduces internal jargon confusion always. The quiet win was aligning on a single on-call rotation across related services.

We should have invested in local dev parity earlier; 'works on my machine' was expensive. In no-code (thread 6): We should have deleted the dead code; it confused every new hire's mental model. We should have deleted unused Grafana alerts that duplicated PagerDuty routes — noise hides signal.

We stopped confusing 'busy roadmap' with 'committed roadmap' when talking to customers externally. In no-code (thread 6): We should have deleted dead feature code before the security review found secrets in it. We stopped shipping 'just log more' without a plan for who reads which logs when.

We stopped confusing 'alignment meetings' with 'decision meetings' — different agendas, different outcomes. In no-code (thread 6): We should have named a DRI for circle recommendation ranking before launch — opaque ranking breeds conspiracy theories fast. Rubber-stamping reviews to be nice is not kindness to the person on-call.

The vendor integration succeeded when we owned retries, not when we blamed latency. In no-code (thread 6): We underestimated how long permissions audits take across legacy systems. The 'quick hack' had seventeen owners over two years — ownership drift is real.

We learned that small improvements to moderator tooling reduce burnout in community circles measurably. In no-code (thread 6): The mentor who said 'prove circle ROI with hiring outcomes, not likes' sharpened B2B positioning debates helpfully quarterly honestly. We merged on Friday once and the meme became policy faster than any memo.

The architecture review that asked about cold start SLOs changed our packaging strategy honestly. In no-code (thread 6): The flaky deployment gate that ignored canary error rate taught us to watch business metrics too. We learned that psychological safety includes admitting you need help before deadline day.

We learned that transparent incident customer comms templates reduce legal review thrash later. In no-code (thread 6): Security review late in the cycle always finds drama nobody has energy to fix. The integration that bounded attachment sizes per circle tier prevented storage surprises for hosts quietly.

We stopped treating 'growth hacks' as neutral — some hacks erode trust that circles need to function helpfully quarterly honestly. In no-code (thread 6): We learned that transparent backlog grooming reduces 'surprise work' complaints from sales. The best postmortems include customer communication review, not only root cause.

The mentor who said 'show me the customer support tag trend' grounded prioritisation debates weekly. In no-code (thread 6): We should have deleted unused environments that still had production-like credentials. We should have deleted unused Slack integrations firing noise into incident channels.

We should have named a DRI for cross-circle recommendation diversity before launch — echo chambers look like bugs to new members honestly. In no-code (thread 6): We learned that transparent ban appeals processes reduce legal risk and member outrage more than shadow bans ever could ethically. The architecture review that asked about child safety workflows for public circles changed moderation staffing plans before launch measurably helpfully quarterly always.