Your engineering organization invests heavily in technology.Who invests in the people who build it?

An organization-wide push aimed to make AI fundamental to how Engineering, QA, Product, Design, and Project Management worked. The technical challenge was only part of it — for many experienced professionals, the change challenged established habits and, in some cases, professional identity. An engineer who took pride in writing high-quality code manually might not immediately see AI-assisted development as an improvement. Declaring the organization "AI-first" wasn't going to create that behavior change on its own.

Because I was already coaching individually across the organization, I could see where each person actually was — and that resistance wasn't always resistance to AI itself. Sometimes it was uncertainty, a confidence gap, quality concerns, or simply not knowing how AI could help that person's particular work.

I helped people work through those barriers, understand what the change meant for their role, experiment with new approaches, and progressively incorporate AI into everyday work — making the role complementary to leadership's: executives set direction, technical leaders introduced the tools, and I helped the strategy work at the individual level.

Executives can declare a transformation. The harder challenge is getting hundreds of individual behaviors to change. Coaching can become the human implementation layer between strategic intent and actual adoption.

The organization was making a major shift from manual QA toward shared quality ownership across QA, backend, and frontend engineering. This wasn't automation for its own sake, but a real shift in process and mindset.

For QA professionals, that raised fundamental questions: what happens to the work I've done, which skills still matter, what does my role become? Engineering teams needed to adjust to owning more quality responsibility themselves rather than relying on QA at the end of the process.

I worked individually with affected people to understand how they viewed the transformation, where they felt resistant or uncertain, and what they needed to move from the current model toward the new one. Those conversations helped people make sense of the change personally rather than just hearing a directive — surfacing specific needs around training, skill development, expectations, and collaboration.

The transition was also supported by closer collaboration across the team's different locations, since a shared-quality model required substantially more cross-discipline coordination.

Technical transformations are also people transformations. Changing tools and processes isn't enough when the change affects people's skills, responsibilities, identity, and understanding of good performance.

I worked with a technical team that needed to shift its working day three hours later to create meaningfully more overlap with colleagues in other time zones — increasingly important as technical initiatives became more collaborative across regions.

For affected employees, moving an entire workday raised legitimate concerns about family responsibilities, routines, and life outside work.

I worked with managers and leadership on how to approach the transition, then met individually with affected employees to understand what the change actually meant for them. I surfaced relevant concerns to leadership and coached people through the practical and personal adjustments, including strategies for restructuring their days.

The team transitioned with zero attrition attributable to the change. Several employees who'd been genuinely concerned beforehand later told me they preferred their new schedules. The added overlap also helped teams in different regions collaborate more effectively on other cross-functional initiatives that required closer coordination across engineering disciplines.

Successful organizational change isn't simply getting people to comply with a decision. It's understanding the human consequences, helping people navigate them, and creating the conditions for the business benefits to materialize.