We learned that humour in onboarding videos helps retention if it includes real workflows. In IT humour (thread 3): We learned that customers notice when you fix papercuts they assumed would never change. We learned that customers forgive slower features if reliability and honesty improve together.

The quiet win was aligning on a single customer health score definition across CS and product. In IT humour (thread 3): The docs were aspirational; the code was honest about what we actually supported. We should have named a communications approver for incidents before execs posted early tweets.

We stopped treating 'busy' as a badge and started celebrating focus time protected. In IT humour (thread 3): We stopped pretending estimates were commitments and trust actually improved. The integration that bounded LLM token budgets per request prevented runaway costs under abuse quietly.

We learned that small wins for support engineers improve customer experience indirectly always. In IT humour (thread 3): The best teams treat accessibility bugs as P1 when they block core flows — consistently. We learned that writing 'communication plan' in launch checklists reduces stakeholder surprise always.

Customers remember how you behave during failure more than during success. In IT humour (thread 3): We finally wrote the 'why we chose this' next to the 'how it works'. Small honest updates beat big silent gaps when stakeholders are nervous.

The mentor who said 'draw the data flow' ended a circular debate in minutes. In IT humour (thread 3): The flaky deployment that ignored database migration order taught us to enforce ordering in CI. We stopped treating 'tech lead' as the person who carries pager guilt for the whole team forever.

We learned that 'temporary' traffic workarounds become routing folklore fast. In IT humour (thread 3): We stopped shipping 'just log it' without a query plan for how humans will read it. The architecture diagram was wrong but useful until it was dangerously wrong.

We learned that naming runbook steps after people breeds single points of failure. In IT humour (thread 3): We should have asked support what they hear before prioritising the roadmap. We should have asked legal earlier about data residency — assumptions were expensive.

We stopped shipping 'temporary' SEO landing pages that contradicted the circles-first philosophy — brand confusion hurts conversion. In IT humour (thread 3): The quiet win was aligning on a single customer health score definition across CS and product. We should have invested in synthetic login journeys before Black Friday traffic doubled.

Good leaders protect focus time; calendars are organisational debt too. In IT humour (thread 3): We learned that naming incidents consistently helps analytics later more than clever titles. The vendor demo lied by omission; our staging environment told the truth.

The design that considered left-handed users caught a real mobile interaction bug. In IT humour (thread 3): We learned that humour helps retrospectives if it does not punch down at roles. The smallest improvement to date pickers reduced timezone bug reports from global users.

We should have load-tested the auth path before Black Friday, not after. In IT humour (thread 3): We should have invested in canary metrics tied to business KPIs, not only HTTP 200 counts. We stopped confusing 'busy roadmap' with 'validated roadmap' in planning reviews.

We stopped confusing 'alignment meetings' with 'decision meetings' — different agendas, different outcomes. In IT humour (thread 3): We learned that transparent incident metrics build trust with sales more than spin. We should have invested in load testing the auth rate limiter before a viral post.

We learned that psychological safety includes admitting you need help before deadline day. In IT humour (thread 3): The quiet win was aligning on a single on-call escalation policy across product and infra. We should have deleted unused circle slugs reserved in marketing decks — engineering shipped different slugs and confused sales.

The mentor who said 'show me the user journey map' ended abstract architecture debates. In IT humour (thread 3): The mentor who admitted their outage made it safer for me to admit mine. The quiet win was standardising environment names across repos and dashboards.