Build in public — week note #6: a mistake I owned in front of the team
Build in public — week note #6: a mistake I owned in front of the team
Sharing publicly — what feels scary to post, and what did you learn from reactions?
Thread index 6 — add your angle.
15 replies
We learned that small improvements to internal wikis reduce repeated onboarding questions weekly. Design said edge case; support said thirty percent of tickets — words matter. We stopped treating 'busy' as a badge and started celebrating focus time protected.
We learned that transparent promotion criteria reduce hallway politics more than perks. We learned that transparent incident metrics build trust with sales more than spin. Kindness in Slack threads is a retention strategy nobody puts on a slide.
The mentor who said 'tell me the worst case' before launch calmed the room usefully. The mentor who said 'prove funnel conversion with experiments' sharpened growth marketing debates usefully. We learned that customers trust companies that publish post-incident learnings without corporate jargon.
We learned that naming on-call secondary is as important as naming primary. The flaky deployment that ignored canary latency regressions taught us to watch p99 not only errors. The integration that validated webhook signatures stopped a replay scare cold.
We stopped measuring lines of code and started measuring customer outcomes. The smallest improvement to date formatting reduced international support confusion. We should have named owners for cron jobs in the same place we name service owners.
We should have invested in staging data refresh before the compliance audit panic. The smallest copy tweak clarified cancellation policy and reduced chargebacks. We should have invested in synthetic login journeys before Black Friday traffic doubled.
We should have named a DRI for dependency upgrades across the org chart seam. The migration plan assumed humans read email; they did not — multi-channel comms won. We learned that naming a risk does not summon it — silence does not protect you.
We stopped shipping 'just internal' admin pages without basic CSRF protections — lesson learned. We should have load-tested the auth path before Black Friday, not after. The mentor who said 'document the workaround' saved the next on-call from inventing a worse one.
The architecture principle 'encrypt by default' aged better than 'encrypt later when auditors come'. We learned that transparent engineering ladders with examples reduce interpretation arguments quarterly. We learned that customers forgive slower shipping if quality and communication improve together visibly.
We should have deleted unused OAuth scopes granted during early experiments — least privilege matters. We should have asked support what they hear before prioritising the roadmap. The mentor who said 'document the workaround owner' prevented orphan hacks from rotting silently.
We stopped confusing 'busy' engineers with 'fully utilised' capacity for planning. We learned that writing postmortems for near misses prevents the big miss later. The flaky test that depended on wall clock time taught us to inject clocks in tests.
Politeness in code review sometimes hides problems until they hit production. We learned that trust is the compound interest of kept small promises. We learned that writing 'communication plan' in launch checklists reduces stakeholder surprise always.
The mentor who pair-reviewed my first PR set the tone for years after. We learned that customers trust companies that publish post-incident learnings without corporate jargon. The best teams treat deleting unused endpoints as security work with visible credit in reviews.
We learned that transparent engineering ladders reduce attrition from perceived favouritism. The mentor who said 'draw the data flow' ended a circular debate in minutes. The quiet win was aligning on a single on-call escalation policy across product and infra.
We stopped debating tools and started measuring lead time to first fix. We learned that humour about standups lands when it proposes a concrete experiment to shorten them next week. We learned that humour in retrospectives helps if it focuses on systems, not individuals' quirks cruelly.
Join the conversation.
Log in to reply