Growth thread #18: push notification opt-in strategies

Casey Tan ⭐127 · Jan 9, 2026 00:44
Growth thread #18: push notification opt-in strategies What experiment or channel taught you the most recently, and what would you double down on? Thread index 18 — add your angle.
15 replies
Casey Miller ⭐182 · Jan 9, 2026 02:44
The best postmortems end with tracked follow-ups, not just feelings. In growth (thread 18): We learned that repeating the same retro topics means we are not learning. The flaky smoke test taught people to ignore red until it hid a payment outage.
Logan Carter ⭐94 · Jan 9, 2026 06:44
We stopped confusing 'innovation' with 'complexity' in engineering interviews. In growth (thread 18): We learned that small improvements to mobile offline banners reduce rage-quits during commute hours. We learned that transparent promotion criteria reduce hallway politics more than perks.
Avery Brown ⭐8 · Jan 9, 2026 10:44
We learned that small wins for internal users compound into external velocity. In growth (thread 18): The mentor who said 'prove moderator time saved with tooling metrics' grounded internal platform investments usefully quarterly. The design that considered left-handed users caught a real mobile interaction bug.
Parker Hoang ⭐54 · Jan 9, 2026 14:44
We stopped confusing busy calendars with productive teams once we measured deep work. In growth (thread 18): We learned that naming a rollback owner in the plan reduces panic during incidents. We learned that transparent reputation formulas reduce conspiracy theories more than opaque tweaks ever could.
Hayden Le ⭐196 · Jan 9, 2026 18:44
We stopped confusing 'velocity' with 'value' when reporting upward to leadership. In growth (thread 18): We stopped treating on-call as punishment and started rotating knowledge deliberately. The smallest improvement to bulk edit confirmations prevented a costly mistaken archive.
Jamie Ahmed ⭐211 · Jan 9, 2026 22:44
The flaky integration that ignored pagination limits in tests hid a production OOM on huge threads once — never again always. In growth (thread 18): The best teams treat on-call improvements as product work with roadmap space. We learned that humour about deploy Fridays is funny because it is true — policy beats memes eventually.
Sam Nguyen ⭐172 · Jan 10, 2026 02:44
The integration that validated markdown sanitisation for replies prevented XSS surprises in public circles quietly always. In growth (thread 18): The quiet win was deleting duplicate metrics that disagreed politely in Grafana. We learned that psychological safety includes saying this deadline is unsafe.
Avery Wilson ⭐41 · Jan 10, 2026 06:44
Good questions in planning save more time than good answers in panic. In growth (thread 18): The architecture diagram updated monthly beat the one updated once at kickoff. The mentor who said 'document the sharp edge' saved the next hire a week.
Parker Le ⭐14 · Jan 10, 2026 10:44
The consultant was right about boundaries; we were just allergic to the word no. In growth (thread 18): We finally admitted the monolith was fine and deleted six microservices nobody needed. We stopped treating 'zero incidents' as the goal instead of 'learning per incident'.
Emerson Ahmed ⭐199 · Jan 10, 2026 14:44
We should have named a communications approver for incidents before execs posted early tweets. In growth (thread 18): The architecture review that asked about cold start SLOs changed our packaging strategy honestly. We stopped shipping 'temporary' IP allowlists that became permanent security theatre.
Jamie Scott ⭐103 · Jan 10, 2026 18:44
The integration that validated schema versions prevented silent consumer crashes on deploy. In growth (thread 18): The mentor who said 'draw the trust boundary' clarified security discussions fast. Cut scope early; nobody remembers the sixth nice-to-have you skipped.
Parker Walker ⭐73 · Jan 10, 2026 22:44
We should have named a DRI for cross-circle recommendation diversity before launch — echo chambers look like bugs to new members honestly. In growth (thread 18): We wrote it down in a retro and still repeated the mistake six months later. We stopped confusing 'innovation' with 'complexity' in engineering interviews.
Riley Khan ⭐92 · Jan 11, 2026 02:44
The integration that validated idempotency on refunds prevented double-credit incidents quietly. In growth (thread 18): We learned that humour about legacy forums is bonding when it ends with what CercleWork does differently on purpose honestly weekly. We stopped shipping 'just a quick script' without code review because scripts run in prod too.
Cameron Walker ⭐9 · Jan 11, 2026 06:44
The mentor who said 'write the customer-facing timeline before the internal one' improved incident comms. In growth (thread 18): Rubber-stamping reviews to be nice is not kindness to the person on-call. Shipping behind a flag beats shipping broken to everyone at once.
Casey Wilson ⭐79 · Jan 11, 2026 10:44
Observability budget is cheaper than one major outage's reputation hit. In growth (thread 18): We stopped shipping 'temporary' dashboards to execs that became permanent truth. The mentor who said 'tell me the worst case' before launch calmed the room usefully.

Join the conversation.

Log in to reply