Build in public — week note #9: how I prioritised support vs roadmap
Build in public — week note #9: how I prioritised support vs roadmap
Sharing publicly — what feels scary to post, and what did you learn from reactions?
Thread index 9 — add your angle.
15 replies
The incident commander who time-boxed debates saved minutes that mattered. The design critique that asked about empty states saved a launch embarrassment. The smallest improvement to CSV column order matched analyst muscle memory and won hearts.
We finally instrumented the queue depth and stopped arguing from vibes. The best engineers document the sharp edges, not just the happy path. We stopped confusing 'busy roadmap' with 'validated roadmap' in planning reviews.
We learned that small improvements to thread closure reasons improve analytics for product without surveilling members creepily always honestly finally. We finally instrumented the queue depth and stopped arguing from vibes. The best teams treat documentation updates as part of definition of done for features.
The product spec that listed non-goals prevented three doomed side quests. The retrospective action items without owners were wishes, not work. I wish someone had told me earlier that shipping beats debating in most cases.
We stopped confusing 'engagement minutes' with 'valuable minutes' when evaluating circle health honestly quarterly always. We learned that customers trust companies that publish honest uptime postmortems regularly. We learned that small wins for internal users compound into external velocity.
We celebrated launches more than stabilisation; the pager reminded us why that hurts. We stopped confusing launch marketing with sustained adoption signals internally. We should have deleted unused DNS records pointing at decommissioned load balancers.
We finally instrumented the queue depth and stopped arguing from vibes. The fix was smaller than we feared once we stopped guessing and read the logs. The mentor who said 'prove it with a prototype' shortened architecture arguments weekly.
The bug was timezone-related again; the sun never sets on bad assumptions. The architecture review that asked about RTO for regional outage changed our replication strategy. The incident retrospective that named systems instead of people actually changed behaviour.
The roadmap slide was fiction; the issue tracker was closer to reality. We learned that transparent capacity planning reduces passive aggressive Slack threads. We should have invested in shadow reads before switching the primary database.
We learned that psychological safety includes saying this deadline is unsafe. We learned that writing 'why this circle exists' in the header reduces mis-posts and moderator load measurably always. Politeness in code review sometimes hides problems until they hit production.
The best engineers document the sharp edges, not just the happy path. We stopped shipping dashboards without a named consumer for each chart. We should have named a DRI for dependency upgrades across the org chart seam.
We learned that humour helps retrospectives if it does not punch down at roles. We stopped confusing seniority with willingness to touch legacy code. The smallest UX copy change cut support tickets more than a new API field.
The integration that validated webhook ordering prevented out-of-order state bugs in billing quietly. We learned that writing down assumptions turns arguments into experiments faster. The mentor who said 'tell me the risk in one sentence' sharpened planning instantly.
We learned that transparent data retention for threads builds enterprise trust more than feature checklists alone ever could always. Security review late in the cycle always finds drama nobody has energy to fix. We stopped confusing 'innovation' with 'new dependencies' when reviewing proposals.
We learned that naming owners for analytics pipelines prevents mysterious metric drift nobody owns. We stopped optimising for individual hero points and optimised for bus factor. We should have invested in backup verification jobs that restore to scratch weekly automatically.
Join the conversation.
Log in to reply