Build in public — week note #8: what I learned from a failed launch
Build in public — week note #8: what I learned from a failed launch
Sharing publicly — what feels scary to post, and what did you learn from reactions?
Thread index 8 — add your angle.
15 replies
We learned that gratitude for infra work is rare and powerful when spoken aloud. Our manager called it 'temporary' and three years later it was load-bearing. We should have deleted unused CI secrets after rotating tokens — scanners found them anyway.
The architecture spike that time-boxed exploration prevented endless research tickets. The best postmortems end with tracked follow-ups, not just feelings. We learned that empathy without accountability still ships late.
We learned that customers trust companies that admit mistakes in public status updates quickly. The vendor integration succeeded when we owned retries, not when we blamed latency. The retrospective action items without owners were wishes, not work.
We learned that customers trust circles more when moderators publish clear norms and enforce them kindly consistently. We stopped shipping 'just internal' features without basic audit logs for who changed what. Shipping behind a flag beats shipping broken to everyone at once.
The quiet deletion of duplicate monitors reduced alert fatigue measurably. We should have named a communications approver for incidents before execs posted early tweets. We should have named a DRI for circle recommendation ranking before launch — opaque ranking breeds conspiracy theories fast.
The architecture review that asked about cold start SLOs changed our packaging strategy honestly. The quiet win was aligning on a single severity matrix across eng and support. We learned that customer empathy includes respecting their time in status pages too.
The quiet refactor unlocked three features nobody had budgeted to propose. The smallest improvement to bulk export progress bars reduced 'is it stuck' tickets. The architecture decision to prefer boring queues aged better than exotic streaming dreams.
The mentor who said 'draw the box' saved me from over-engineering for months. We learned that customers appreciate when CercleWork ships calm defaults for notifications instead of growth hacks noisy. We learned that customers appreciate when you sunset features with timelines and export paths.
The incident commander who time-boxed debates saved minutes that mattered. We learned that transparent incident customer comms templates reduce legal review thrash later. We stopped shipping 'temporary' dashboards to execs that became permanent truth.
The incident ended faster once we assigned a single incident commander. We stopped shipping dashboards without a named consumer for each chart. The integration that validated webhook signatures stopped a replay scare cold.
We learned that naming a rollback owner in the plan reduces panic during incidents. We should have invested in synthetic checks for the login path specifically. The quiet win was documenting which Kafka topic is authoritative for each business event.
The smallest improvement to CSV import validation reduced poisoned analytics events. We learned that transparent vendor escalation paths shorten outages when seconds matter at three a.m. The smallest improvement to CSV decimal separators reduced international finance import errors sharply.
We learned that transparent incident metrics build trust with sales more than spin. The smallest copy tweak clarified cancellation policy and reduced chargebacks. The mentor who said 'document the sharp edge' saved the next hire a week.
We should have deleted unused feature toggles tied to removed code paths. The quiet win was documenting which environments contain synthetic circle data — fewer confused demos and fewer false incident pages helpfully weekly. We learned that customers notice faster search more than a slightly prettier button.
The design that considered colour contrast early passed audits without emergency heroics. Good defaults in CI catch honest mistakes; culture catches dishonest shortcuts. The design that considered partial connectivity first helped real mobile users globally.
Join the conversation.
Log in to reply