General Motors

Team A brought me in from day one. I conducted 6–10 user interviews that surfaced a finding nobody had measured before — users were spending half their working time verifying data instead of doing their actual job. That single stat changed the project's priority overnight. I synthesized the interviews into empathy maps, personas, and journey maps that became the team's shared reference point. When disagreements came up, people pointed to the research instead of their opinions. When we hit a design crossroads with two competing architecture approaches and strong advocates on both sides, a SWOT analysis resolved it in one meeting. Sprints moved smoothly. Ideation sessions were focused. Requirements were simple to write because everyone already understood the problem they were solving. Team B never included UX in scope. Without interviews or shared artifacts, every meeting became a negotiation between assumptions. There was no framework for saying "not now" to a feature request, so scope expanded unchecked. Features were designed, built, and presented to stakeholders — only to be rejected because the assumptions behind them were never validated. This happened repeatedly. The application grew more chaotic with each cycle as layers of unvalidated decisions stacked on top of each other. The team wasn't less talented or less experienced. They just never had a shared understanding of who they were building for or why.