Pros
Talented peers in Tech Support. There are quality employees across the customer-facing teams, just severely lacking the backing to succeed.
Cons
Decision-making prioritized preference over evidence, and the people closest to customers were routinely sidelined. Cross-team communication broke down, and leadership often defaulted to interdepartmental blame instead of owning outcomes. Leadership and decision-making Senior leadership operated in silos. Feedback from frontline teams was dismissed or reframed as a “lack of effort,” masking real staffing and prioritization gaps. Strategy was presented as certainty even when data and on-the-ground signals said otherwise. Execution and product quality Releases repeatedly went out with systemic QA gaps that produced major regressions. These were predictable results of weak release gates, unclear ownership, and shipping to a calendar rather than to readiness. When failures reached production, Tech Support absorbed the fallout while still managing a heavy backlog of unresolved defects. Support and escalation Ticket escalations frequently aged without meaningful updates within the technology organization. Operations did not consistently back Tech Support when cross-team help was required, leaving support accountable for issues it had no authority to prevent. Culture and accountability Stated values around collaboration and customer focus were largely aspirational. Raising risks early was treated as negativity. The environment rewarded keeping heads down over surfacing problems, so the same fires returned sprint after sprint. Impact Customers experienced avoidable breakage, morale declined, and turnover increased. Those doing the heaviest lifting had the least influence on the inputs that drive outcomes.