Category: Frequently Asked Questions

I focus on systems and processes rather than individuals. I document practices, create self-service resources, and use buddy systems for onboarding. Change must be embedded in the structure, not dependent on individuals.

Yes, but it requires change portfolio management. I map interdependencies between initiatives and establish coordination mechanisms. Communication planning is key – ensuring people see the big picture, not just individual changes.

I start with alignment sessions with key stakeholders – clarifying priorities and trade-offs. Often, the real issue is not conflicting priorities but lack of explicit priority setting. Transparency about constraints supports better decisions.

Celebration is not just recognition but reinforcement of new behaviors. I highlight milestones and actions I want to see more of. It acts as a social signal – “this is what success looks like” – and motivation to continue.

It’s important to acknowledge past failures and learn from them. I don’t ignore history but show why this time will be different – better planning, new approaches, and lessons learned. Trust builds through transparency.

Timing is crucial – I initiate changes during natural transitions (new quarter, reorganization, onboarding). I avoid periods of high organizational stress, when focus shifts to survival rather than learning.

I don’t fight culture, but work with its elements. I identify cultural assets supporting change and build on them. Cultural transformation is evolutionary, not revolutionary.

Yes, but it requires influencing without formal authority. I build coalitions, demonstrate quick wins, and use social proof – “team X is already testing this with good results.” Credibility is essential.

Yes – by leveraging social proof and showcasing early adopters. I support opinion leaders in successful implementation and use their successes as examples. Momentum grows through success stories.

You can start with small-scale experiments, but scaling always requires top sponsorship. I usually begin with a proof of concept within a single team to demonstrate value before escalating to executives.