Engineering manager inherits an unsolicited CX dashboard team, bypasses their greenfield React build, and hits the OKR faster with Spring Boot templates and CX training.
Key Takeaways
The new CX team was structured on an old stack-based operating model (mobile/backend/web/CX) while the tribe had already shifted to full-experience team ownership.
The team reported outside the tribe, to a business vertical product leader, creating a communication gap that persisted even with shared ceremonies.
The proposed microfrontend React architecture misaligned with leadership expectations and was blocked internally by backend engineers unwilling to write HTML.
The EM shipped per-team Spring Boot template dashboards instead, trained CX staff directly, and adapted Jira to match their existing reporting habits, driving adoption.
Ticket resolution time dropped from days to hours within one month; the CX team was disbanded after five months once product teams were resolving CX metrics autonomously.
Hacker News Comment Review
The sole commenter reads the EM’s framing charitably but flags a darker interpretation: deliberately blocking a team that does not report to you, then declaring their work unadoptable, is a recognizable org-politics pattern dressed in Team Topologies language.
