April 27, 2026
New team, who dis?
Adding a team was the wrong strategic decision
Surprise team sparks turf war; commenters cry sabotage and roast the 'tribe' talk
TLDR: A surprise customer-experience team was created outside the usual reporting lines to speed up support, clashing with the company’s end‑to‑end team model. Comments explode over turf wars, alleged sabotage, and cringey “tribe” jargon—raising bigger questions about who should own customer problems and how leaders make these calls.
An engineering manager says a new customer experience (CX) team dropped into his org like a UFO—no warning, no input, and reporting to someone outside his “tribe.” The goal: fix support speed and build a shiny dashboard. The conflict: their company had just moved to end‑to‑end (E2E) teams that own the whole product, and this new team cut across that. Cue the internet grabbing popcorn. The top comment basically screamed: if a team doesn’t report to you, some managers will quietly nuke it from orbit. Others chimed in with “been there,” while one reader had the opposite story—leadership shot down a similar plan at their company and now they want to know why.
The community tore into the narrative itself. Several readers argued the post reads like a humble‑brag cover story for a messy power play, pointing out contradictions and calling the author an unreliable narrator. Another thread blew up over the word “tribe,” with people mocking corporate cosplay and asking why we’re still saying that in 2026. The tension boiled down to turf, trust, and tools: a lonely CX team promised a dashboard of dreams while everyone else asked who’s actually fixing tickets today. The vibe? Org‑chart Hunger Games with a side of jargon roast and a dash of “new team, who dis?”
Key Points
- •A new CX team was introduced without prior consultation to improve customer experience and build a support dashboard.
- •The company transitioned from component-based teams to end-to-end product ownership, reducing bugs and incidents.
- •Leadership created the CX team despite the new operating model; stated reasons included slow information flow, 2020 budget context, and centralized CX metrics ownership.
- •The CX team reported outside tribe leadership, causing communication issues, and lacked necessary tooling to resolve tickets autonomously.
- •The CX plan involved a React microfrontends dashboard, but it did not align with leadership expectations; ticket volume decreased, but resolution time remained high.