We stopped shipping 'temporary' admin impersonation without audit logs — compliance nightmare. In IT humour (thread 11): The smallest improvement to bulk edit confirmations prevented a costly mistaken archive. The design that considered assistive tech early avoided costly retrofitting later.

We learned that customers trust changelog honesty more than marketing superlatives. In IT humour (thread 11): We should have named a DRI for circle recommendation ranking before launch — opaque ranking breeds conspiracy theories fast. We learned that naming a single decision maker in incidents ends thrash faster.

We learned that writing 'what belongs in this circle' examples in the composer reduces moderator workload measurably without nagging always. In IT humour (thread 11): We replaced heroics with runbooks and sleep schedules improved measurably. We stopped shipping 'just internal' admin pages without basic CSRF protections — lesson learned.

We learned that transparent promotion feedback reduces anxiety more than surprise 'you are promoted' chats. In IT humour (thread 11): The design review that asked 'what if they are offline' prevented real pain. Half the team knew the risk; nobody felt authorised to say stop on the call.

The mentor who said 'document the workaround' saved the next on-call from inventing a worse one. In IT humour (thread 11): We stopped confusing 'busy' engineers with 'fully utilised' capacity for planning. We stopped treating 'innovation time' as a guilt trip when product pressure spikes.

Small honest updates beat big silent gaps when stakeholders are nervous. In IT humour (thread 11): The flaky deployment that ignored read replica lag taught us to surface replication delay in UI for sensitive actions quietly. We should have deleted unused feature branches — stale PRs confused everyone.

The best teams debrief decisions after outcomes, not only after failures. In IT humour (thread 11): We stopped confusing 'more threads' with 'healthier threads' when evaluating circle success honestly weekly always finally helpfully measurably. Two strong opinions without data turned into a week nobody wants back.

The spreadsheet everyone hated was also the source of truth — respect the ugly tools. In IT humour (thread 11): The quiet refactor unlocked three features nobody had budgeted to propose. The design that considered screen reader labels for charts made data accessible to more roles.

The best teams treat documentation updates as part of definition of done for features. In IT humour (thread 11): We learned that empathy for users and empathy for teammates are the same skill. We underestimated how much naming environments consistently reduces human error.

The smallest type annotation prevented a class of null surprises — types as docs. In IT humour (thread 11): The architecture principle 'optimize for debuggability' aged better than micro-optimisation pride. The mentor who said 'what would you ship if you had half the time' clarified scope brutally.

The bug bash found issues our automated suite could not imagine — humans still matter. In IT humour (thread 11): The architecture spike that time-boxed exploration prevented endless research tickets. The smallest improvement to empty states reduced bounce on onboarding screens.

The integration that bounded attachment sizes per circle tier prevented storage surprises for hosts quietly. In IT humour (thread 11): The architecture principle 'encrypt by default' aged better than 'encrypt later when auditors come'. Kindness in Slack threads is a retention strategy nobody puts on a slide.

We learned that customer empathy includes respecting their time in status pages too. In IT humour (thread 11): The clever abstraction blocked new hires for weeks; boring code shipped. The mentor who said 'draw the trust boundary for data' clarified GDPR discussions quickly.

We should have deleted unused IAM policies quarterly — stale permissions accumulate quietly. In IT humour (thread 11): We stopped shipping 'temporary' public circles without moderators — empty moderation queues become emergencies fast. The build pipeline that emails on success trains people to ignore email.

We learned that small accessibility wins in admin tools help internal teams ship faster too. In IT humour (thread 11): The integration that validated idempotency keys on payouts prevented duplicate payouts quietly forever. The mentor who said 'prove retention with cohorts not totals' ended vanity metric debates again.