An EM inherited a surprise CX team that reported outside his tribe, ignored its greenfield dashboard, built messy internal tooling instead, and hit the OKR faster.
Key Takeaways
A CX tribe team was created without input from the engineering manager whose tribe owned the affected products, reporting to a separate product vertical leader instead.
The new team pursued a microfrontend React dashboard architecture while the actual blocker was CX agents lacking read/write tooling to resolve tickets without developer intervention.
Product teams built per-team Spring Boot HTML dashboards rather than waiting for the greenfield system; CX tickets went from days to hours within one month.
Metric success masked process failure: the PM absorbed all CX ticket work herself, hitting OKR numbers while burning out and cementing the wrong workflow.
The manager explicitly applied Team Topologies’ platform principle: do not force adoption of a platform that is not yet good enough; the CX team was disbanded after five months.
Hacker News Comment Review
Commenters broadly read the post as an account of organizational politics dressed up in sociotechnical framing: the EM sidelined a team outside his reporting chain, ensured its work was never adopted, and framed that outcome as principled engineering judgment.
Skepticism focused on missing context: the decision to build separate per-team dashboards instead of collaborating with the CX team is presented as self-evident, but the justification for that pivot is thin given the EM also had no frontend skills available in his own teams.
One sharp counterpoint noted the post buried the key structural fact – the CX team reported to a different leader – which reframes the whole narrative from “mysterious orphan team” to a deliberate org decision the author had reason to resist.
Notable Comments
@Aurornis: argues the intro obscures that the team reported to a different product leader, making the “appeared out of nowhere” framing misleading.
@layer8: flags that hiring three FTEs to build an internal dashboard the author himself describes as “not that complex” is the real buried cost story.
@cbbb: notes the justification for redirecting the project is underexplained given the EM’s own teams also lacked the frontend skills to execute his alternative plan.
