Organizational Development Consultant Interview Questions and Answers

Preparing for an organizational development consultant interview can feel daunting, but you’re already on the right track. This comprehensive guide walks you through the types of organizational development consultant interview questions you’ll likely encounter, provides realistic sample answers you can adapt, and equips you with the frameworks you need to tackle any curveball question. Whether you’re fielding behavioral questions about past experiences or diving into technical OD methodology, we’ll help you showcase the strategic thinking, change management expertise, and emotional intelligence that hiring managers are looking for.

Common Organizational Development Consultant Interview Questions

These are the bread-and-butter questions you’ll encounter in most OD consultant interviews. They give interviewers a chance to understand your experience, your approach to common challenges, and how you think about organizational problems.

”Tell me about your experience with organizational development initiatives.”

Why they ask: Interviewers want to understand the breadth and depth of your OD background. This question sets the stage for your overall expertise and gives them a sense of the types of projects and organizations you’ve worked with.

Sample answer:

“Over the past five years, I’ve led organizational development work across manufacturing, tech, and healthcare sectors. My experience spans the full lifecycle—from conducting needs assessments to designing and implementing interventions. One project I’m particularly proud of involved leading a cultural transformation at a mid-sized manufacturing company. We started with a comprehensive survey and focus groups, identified silos between departments, and implemented cross-functional collaboration initiatives. I also facilitate leadership development programs and have experience with succession planning and talent management strategies. Each engagement has deepened my understanding of how organizational context really shapes what interventions will stick.”

Personalization tip: Name specific industries or organization sizes you’ve worked with. Mention 2-3 different types of initiatives (culture change, talent development, process improvement, etc.) to show versatility. If you’re earlier in your career, focus on specific projects and measurable outcomes rather than years of experience.

”Describe your approach to conducting an organizational assessment.”

Why they ask: This is a core competency. Interviewers need to know your process is rigorous, data-driven, and grounded in sound OD methodology. They’re assessing your diagnostic thinking.

Sample answer:

“I always start by clarifying the presenting problem with leadership—what they think is wrong might not be what’s actually happening. From there, I develop a customized assessment strategy. I typically combine multiple data sources: employee surveys to understand perception and engagement, interviews with key stakeholders at different levels to get context and nuance, and review of operational data like turnover rates, performance metrics, and absenteeism. For example, when a client complained about poor collaboration, my initial survey showed that wasn’t the real issue—the problem was unclear roles and decision-making authority. If I’d stopped at surface-level diagnosis, the intervention would’ve missed the mark. I’m also careful to involve people in the process. When employees see that you’re genuinely trying to understand their experience, you build buy-in for whatever comes next.”

Personalization tip: Walk through a specific example if you can. Mention 2-3 assessment tools you actually use (employee surveys, interviews, focus groups, data analysis, etc.). Highlight how you challenge the initial problem statement rather than just accepting it at face value.

”How do you measure the success of an organizational development initiative?”

Why they ask: OD work is often seen as soft or unmeasurable. They want to know you can connect initiatives to business impact and aren’t just running feel-good programs.

Sample answer:

“I always establish metrics before implementing anything. The key is mixing quantitative and qualitative measures. For instance, in a leadership development program, I tracked hard metrics like promotion rates from within the program, retention of program graduates compared to non-participants, and time-to-fill for leadership positions. But I also measured softer outcomes—360-degree feedback from direct reports, pulse surveys on leadership effectiveness, and qualitative feedback from participants about application of skills. I present a baseline at the start and then check progress at 30, 90, and 180 days. Honestly, the real test is whether the business problem you were solving actually improves. If you implemented a collaboration initiative because project cycles were too long, you should see project timelines shrink. If you did culture work because of turnover, you should see retention move.”

Personalization tip: Use specific metrics from a real project you’ve worked on. Show that you think about both leading indicators (engagement scores, training completion) and lagging indicators (turnover, productivity). Mention your measurement timeline—how soon do you expect to see results?

”Walk me through how you would handle resistance to change in an organization.”

Why they asks: Change resistance is inevitable, and handling it poorly derails initiatives. They want to see that you understand the roots of resistance and have concrete strategies to address it.

Sample answer:

“First, I think resistance is almost always a sign that something hasn’t been communicated clearly or people don’t feel heard. I rarely see resistance to change itself—I see resistance to change imposed on them. So my approach starts with understanding what’s driving it. I’ll do listening sessions, ask people what concerns them about the change, and find out what they’re worried about losing. Often it’s about loss of control, unclear expectations, or fear that their skills won’t be relevant anymore. Once I understand it, I address it directly. In a digital transformation project I led, frontline staff were worried that new software would make their expertise obsolete. We addressed it by involving them in system selection, providing hands-on training well before go-live, and positioning them as ‘superusers’ to help peers. By the time we launched, they were advocates instead of resisters. I’ve also found that giving people choices within the change—like how they transition, not whether they transition—reduces friction significantly.”

Personalization tip: Describe a specific example where you faced meaningful resistance and explain both what you did and what you learned. Show that you view resistance as data, not defiance.

”What organizational development models or frameworks do you typically use?”

Why they ask: This gauges your theoretical foundation and whether you’re applying evidence-based practices rather than just improvising.

Sample answer:

“I draw on several frameworks depending on what the organization needs. For change management, I often use Kotter’s 8-step model because it emphasizes both the emotional and structural sides of change. For diagnosing organizational issues, the McKinsey 7-S framework helps me examine alignment across strategy, structure, systems, skills, style, staff, and shared values. For cultural assessment, I use Cameron and Quinn’s organizational culture framework to help leaders understand their current culture and identify what needs to shift. That said, I don’t blindly apply frameworks—I use them as thinking tools. An organization in crisis needs a different approach than one doing incremental improvement. I’ve also used ADKAR for projects where we needed to track individual readiness for change, and I’m increasingly incorporating systems thinking because most organizational problems involve interdependencies that linear models miss.”

Personalization tip: Name 2-3 frameworks you’ve actually used, not just ones you learned in grad school. Briefly explain why you choose different frameworks for different situations—this shows you’re thinking contextually, not just following a recipe.

”Tell me about a time you had to deliver difficult feedback to a leader or stakeholder.”

Why they ask: OD consultants need to influence without authority. They want to know you can be honest and constructive with powerful people, not just tell them what they want to hear.

Sample answer:

“In a recent engagement, the VP of Operations was implementing a restructuring that he was convinced would improve efficiency. During my assessment, it became clear the real problem wasn’t structure—it was unclear decision-making authority and poor cross-functional communication. I had to tell him that the restructuring wouldn’t solve the underlying issue and might actually waste the effort and goodwill he was spending on it. I framed it as ‘here’s what we learned’ rather than ‘you’re wrong,’ and I had data to back it up. I also came with alternatives. It was a tense conversation because he was already committed to the restructuring, but I positioned it as helping him avoid a costly mistake. He didn’t take my advice initially, and we did restructure. Three months in, the problems he was hoping to solve weren’t fixed, and he came back asking for help with the communication and decision-making issues. It would’ve been easier to just redesign with him, but that wouldn’t have been my job as an OD consultant.”

Personalization tip: Show that you can balance honesty with respect. Highlight that you brought data, offered alternatives, and didn’t pull punches just to be liked.

”How do you stay current with organizational development trends and research?”

Why they ask: OD is an evolving field. They want to know you’re not stuck in 2005 OD practices and that you actively build your knowledge.

Sample answer:

“I’m a member of the OD Network and attend their annual conference—it’s where I see cutting-edge thinking on topics like agile organizational design and remote-first cultures. I subscribe to the Journal of Applied Behavioral Science and the OD Practitioner magazine. I also follow researchers and practitioners on LinkedIn who are doing interesting work—people like Brené Brown on vulnerability in organizations and Amy Edmondson on psychological safety. I’ve recently been diving into neuroscience and organizational behavior because I think understanding how people actually process change—not how we assume they do—makes our interventions more effective. Last year I took a certification in Team Coaching because I was seeing organizations invest in individual coaching but miss the team dynamics piece. It’s about staying curious and recognizing that what worked for one organization won’t automatically work for the next.”

Personalization tip: Name specific sources, conferences, or practitioners you actually follow. Mention a recent insight you’ve gained and how you’ve applied it. Show intellectual curiosity, not just credential collecting.

”Describe a time when an organizational development initiative didn’t go as planned.”

Why they ask: Everyone who works in change management has failures. They want to see that you can learn from setbacks and aren’t either defensive or reckless.

Sample answer:

“I led a values clarification initiative at a nonprofit where we facilitated sessions to define and embed organizational values. We did great work clarifying what mattered, created beautiful materials, and launched with energy. But six months in, values were already fading into the background and behavior wasn’t shifting. Looking back, we underestimated the gap between knowing what you value and actually changing how you work. We had the messaging right but not the systems. We didn’t tie values to hiring criteria, performance management, or decision-making frameworks. We also didn’t give managers tools to reference values in real time. The lesson was that cultural change needs reinforcement through multiple channels—symbols and language matter, but systems matter more. I brought this back to the client, and we implemented a second phase that was much more embedded in how work actually happens. The organization did shift, but it took longer than the initial timeline I’d promised.”

Personalization tip: Pick a real setback, explain what went wrong, what you learned, and how you adjusted. This shows self-awareness and a learning orientation, which is gold in OD.

”How do you build trust with an organization’s employees and leadership?”

Why they ask: Trust is foundational to OD work. If people don’t trust you, they won’t be honest in assessments and won’t buy into your recommendations. They want to see your interpersonal strategy.

Sample answer:

“I think it starts with clarity and consistency. In my first week with an organization, I’m transparent about my role, what I’m here to find out, and how I’ll use the information. I’m explicit about confidentiality—people will tell you things, but only if they believe you won’t carry tales back to leadership. I also show up as a learner, not an expert. I ask questions like ‘help me understand’ rather than ‘here’s the problem.’ Early wins matter too. I try to identify one thing I can help with quickly that demonstrates that I listen and deliver. With leadership, trust comes from bringing them data they need to hear even if it’s uncomfortable, and following through on commitments. I’m also careful about my positioning—am I here as an advocate for a particular outcome, or am I genuinely trying to help them see what’s true? If they sense I have a hidden agenda, that trust evaporates fast.”

Personalization tip: Describe a specific behavior or practice you use (like confidentiality agreements you discuss upfront, or how you share preliminary findings). Show that trust is something you actively build and protect, not something you assume.

”What would you do if leadership wanted you to implement an intervention you didn’t believe would work?”

Why they ask: This tests your integrity and your ability to navigate pressure. Can you push back respectfully without being a contrarian rebel?

Sample answer:

“I would ask to understand their thinking first. Sometimes I’m missing context or assumptions they have that change my assessment. But if I genuinely believed the intervention wouldn’t address the root problem, I’d be direct about it. I’d say something like, ‘Based on what we learned in the assessment, here’s why I’m concerned this won’t get us the outcome we want, and here’s what I recommend instead.’ I’d present data and offer alternatives. That said, leadership has information I don’t have—about budget, timeline, politics, or strategic priorities. Sometimes the best intervention isn’t possible, and I need to figure out what is possible and how to maximize impact within those constraints. The line I won’t cross is implementing something I genuinely believe will make things worse or violate organizational ethics. In that case, I’d have a candid conversation about whether I’m the right fit for this engagement.”

Personalization tip: Show that you can be diplomatic while maintaining professional standards. Illustrate that you understand the complexity of organizational constraints without using that as an excuse to abandon your expertise.

”Tell me about your experience with different organization sizes or industries.”

Why they ask: They want to know if you can adapt your approach and whether you understand the context specifics of their organization.

Sample answer:

“I’ve worked across a range. At a Fortune 500 company, I was managing a global culture initiative with complex stakeholder dynamics and strict governance. At a 50-person tech startup, I was helping them build HR and people processes from scratch because they were hitting growing pains. At a mid-sized healthcare system, I was facilitating difficult conversations about role clarity across clinical and administrative staff. Each had very different challenges. In large organizations, you’re managing political complexity and building change through networks and influence. In startups, the challenge is often that things change so fast that processes become outdated quickly. In healthcare, clinical expertise and hierarchies add layers that other industries don’t have. I’ve learned to ask early: ‘What’s the DNA of this organization? What’s worked here in the past? What are we up against?’ Understanding that context shapes everything about how you structure an engagement.”

Personalization tip: Name 2-3 different organization sizes or industries you’ve worked in. Mention a specific challenge that was unique to each context. Show that you don’t have one cookie-cutter approach.

”How would you approach working with a resistant or skeptical leadership team?”

Why they asks: Not everyone believes in OD. They want to see that you can influence people who are doubtful or cynical about organizational development work.

Sample answer:

“I respect skepticism, honestly. A lot of OD work is fluffy, so their skepticism might be warranted. I start by speaking their language. If they care about revenue, I frame OD in terms of what drives revenue—people retention, customer satisfaction, innovation capability. I also deliver data early and make the business case transparent. I might say, ‘The issue you’re calling a performance problem looks like a communication structure problem. Here’s what I learned. Here’s what happens if we don’t fix it. Here’s what’s possible if we do.’ I’m also very clear about what I’m recommending and why, and I’m specific about metrics—we’ll know if this is working by X date if Y thing improves. I don’t ask them to believe in my methodology; I ask them to try an approach and judge it by results. That removes a lot of the ideological resistance. And I’m careful not to be preachy. If someone doesn’t believe in engagement surveys, I don’t try to convince them surveys are the way. I find another way to gather the data they’ll trust.”

Personalization tip: Show respect for healthy skepticism and focus on business outcomes rather than OD philosophy. Demonstrate that you speak multiple languages—both OD and business.

Behavioral Interview Questions for Organizational Development Consultants

Behavioral questions ask about your past experiences to predict how you’ll behave in the future. Use the STAR method (Situation, Task, Action, Result) to structure your answers. These questions reveal how you actually handle the challenges OD consultants face.

”Tell me about a time you led a significant change initiative. What was your role, and what was the outcome?”

Why they ask: This is the centerpiece question for OD consultant interviews. They want concrete evidence that you can design, implement, and see through organizational change.

STAR framework:

• Situation: Set the scene. What organization, what was the business situation, and what change was needed?
• Task: What was your specific responsibility? Were you leading it solo or on a team?
• Action: Walk through your process step-by-step. How did you diagnose? How did you plan? What specific things did you do?
• Result: What measurable outcomes happened? What did you learn?

Sample answer using STAR:

“At a manufacturing company with 300 employees, leadership wanted to shift from a command-and-control structure to a more collaborative, empowered model. The company was losing talented mid-level managers to competitors, and innovation was stagnant. I was brought in to lead this culture transformation. My process started with a two-month assessment—employee surveys, interviews with 25 people across all levels, and focus groups. The data showed that people felt unheard and didn’t trust leadership’s commitment to change. Knowing this, I helped leadership team get very specific about what the new culture actually looked like and what would have to change in their own behavior. Then we rolled out a phased approach: we trained all managers in collaborative leadership and coaching skills, redesigned the annual meeting to be more of a dialogue than a broadcast, and established employee councils with real decision-making power. I facilitated the first three council meetings and then gradually handed off facilitation to the leadership team. The results: after one year, our internal promotion rate increased by 12%, employee engagement on questions about voice and influence went up 23 points, and innovation submissions increased by 40%. The thing I learned was that people will tolerate leadership asking them to change faster than they’ll tolerate leaders not changing along with them.”

Personalization tip: Be specific about your role versus team roles. Include the human element—not just metrics, but what you learned about people. Mention 2-3 concrete actions, not just a high-level summary.

”Describe a situation where you had to influence someone who had more authority than you.”

Why they ask: OD consultants influence without direct authority. They need to know you can persuade, navigate politics, and get things done without commanding.

STAR framework:

• Situation: Who did you need to influence and what was the ask?
• Task: What was at stake? Why was this important?
• Action: What specific techniques did you use to build your case?
• Result: Did you get the influence you needed? What happened?

Sample answer using STAR:

“I was working with a manufacturing plant manager who was convinced the solution to low productivity was working longer hours and tighter deadlines. I’d done an assessment that clearly showed the problem was actually disorganized work processes and unclear priorities—people were working hard but on the wrong things. He had no interest in my assessment. Instead of arguing about my data, I asked him if we could run a small test. We picked one department, implemented process improvements for 30 days while keeping the same hours, and measured output. Productivity increased 18% without anyone working more. That gave me his ear. I’d also learned that this manager cared deeply about cost reduction, so I framed further process improvements in terms of waste elimination, not culture change. He went from skeptical to my biggest advocate. What I learned is that you can have the best data in the world, but people move on their own internal logic. My job was to find where his logic and my recommendations intersected.”

Personalization tip: Show that you did your homework on what mattered to the other person. Describe a specific technique you used—data, a small test, reframing, building allies. Highlight that influence is a skill, not luck.

”Tell me about a time you had a conflict with someone you were working with. How did you handle it?”

Why they ask: OD work involves people, and people conflict. They want to see your conflict resolution skills and emotional intelligence.

STAR framework:

• Situation: Who was the conflict with and what was it about?
• Task: What was your role in addressing it?
• Action: What did you actually do or say?
• Result: How was it resolved? What did you learn?

Sample answer using STAR:

“I was co-facilitating a strategic planning session with an internal HR director. We had very different views on how much time to spend on diagnosis versus jumping to solutions. She wanted to move fast—we had a board deadline. I wanted to make sure we understood the real problems before designing solutions. During a break, she pulled me aside and was frustrated that I was ‘slowing things down.’ Instead of defending my approach, I asked her what I was missing about the business situation. Turned out, the board was expecting recommendations at this meeting, so her urgency made sense. We talked through a hybrid approach—we’d do a rapid assessment focused on the highest-priority questions, present preliminary findings with clear caveats about what we still didn’t know, and build a more detailed plan with the findings. What could’ve been a standoff became a better plan because I understood her constraints. We actually got more credibility with the board by being honest about our methodology than we would’ve if we’d just thrown recommendations at them.”

Personalization tip: Show genuine curiosity about the other person’s perspective, not just your own rightness. Describe how you actually shifted—not just the outcome, but what you learned about working differently.

”Share an example of when you had to deliver bad news or difficult feedback to a group or an individual.”

Why they ask: Change often involves bad news—restructurings, role changes, difficult truths about culture or performance. They need to know you can communicate hard things with honesty and compassion.

STAR framework:

• Situation: What was the bad news? To whom were you delivering it?
• Task: Why did you have the responsibility to communicate it?
• Action: How did you prepare? What did you actually say? How did you handle reactions?
• Result: How did the person/group respond? Did they accept the feedback?

Sample answer using STAR:

“During a merger integration, I had to tell a group of 40 people that their department structure was changing and some roles would be eliminated. This was information coming from the merged company’s leadership, but HR asked me to help with the communication. I could’ve just read the announcement and answered questions, but I knew people would feel blindsided and anxious. I prepared the leadership team to be candid about what was changing and what wasn’t, and I prepared talking points that were honest without being gratuitously harsh. I said things like ‘these roles are changing because they’re redundant now, not because you haven’t done good work.’ During the meeting, I acknowledged that this was scary and uncertain, and I was clear about what we knew and what we didn’t. We had individual follow-up conversations scheduled the next day so people could process. Later, people told me they appreciated the honesty and the pace of communication, even though they didn’t like the outcome. It taught me that people can handle bad news—what they can’t handle is feeling like you’re hiding information or that you don’t care how it affects them.”

Personalization tip: Show that you prepare and that you care about the human impact, not just the message. Describe the specific language you used or structure you created to help people process the news.

”Tell me about a project where you had to learn something new quickly.”

Why they ask: Organizations and industries change. OD consultants need to be learning agile and able to get up to speed in unfamiliar contexts.

STAR framework:

• Situation: What was the project and what didn’t you know?
• Task: How much time did you have to learn it?
• Action: What did you do to fill the knowledge gap?
• Result: Were you successful? How did you apply what you learned?

Sample answer using STAR:

“I was hired to lead a culture and change initiative at a pharmaceutical company, and I’d never worked in regulated industries before. I knew nothing about FDA requirements, clinical trial timelines, or how regulation shaped company culture. I did three things: I read relevant regulations and case studies about pharma culture, I shadowed people in different roles to understand where regulation actually created friction, and I asked a lot of questions during my assessment interviews, framing my lack of knowledge as a strength—‘help me understand how this works here.’ Once I got it, I realized that a lot of the siloed culture wasn’t personality conflicts; it was by design because of regulatory requirements. That meant my recommendations had to account for regulatory realities, not just try to break down the silos. The assessment and recommendations were stronger because I took time to understand the industry context instead of assuming my standard culture playbook would work.”

Personalization tip: Show that you take responsibility for learning, not that you pretend to know things. Describe how you’ve filled knowledge gaps in real situations. Highlight that context-specific knowledge made you more effective.

”Describe a time when you had to adapt your plan based on new information or changing circumstances.”

Why they ask: Plans change. Situations evolve. They want to see you’re flexible and can pivot without falling apart.

STAR framework:

• Situation: What was the plan and what changed?
• Task: How did you decide to adapt?
• Action: What specifically did you change and how did you communicate it?
• Result: Did the adaptation improve outcomes?

Sample answer using STAR:

“I was leading a leadership development program designed as in-person cohort-based sessions over six months. We were three months in when the pandemic hit. I could’ve tried to transition it to Zoom and hoped for the best, but the program relied on relationship building and vulnerability among the cohort. Instead, I paused, consulted with the cohort members about what mattered most, and redesigned on the fly. We kept small Zoom calls for reflection and peer coaching, but we moved the skill-building content to asynchronous learning so people weren’t zoomed out. We created a Slack community and shifted some of the cohort bonding there. Here’s the thing—the outcomes were actually better. The asynchronous format meant people could engage when they had energy instead of back-to-back meetings. The Slack community became a ongoing peer coaching network. So when things reopened, we kept the hybrid model. Forced adaptation created something better than the original plan.”

Personalization tip: Show that you’re not rigidly attached to your original design. Describe how you gathered input and involved stakeholders in the adaptation decision.

Technical Interview Questions for Organizational Development Consultants

These questions assess your knowledge of OD methodology, frameworks, and your ability to think through complex organizational scenarios. Rather than memorized answers, think through the framework and reasoning process.

”Walk me through how you would assess an organization experiencing high turnover.”

Why they ask: Turnover is a common presenting problem. Your diagnosis will determine your intervention. They want to see your diagnostic thinking, not just fix-it impulses.

How to think through your answer:

1. Clarify the turnover. Is it everyone or specific groups? Is it involuntary or voluntary? When in tenure do people leave? This matters because the root causes are different.

2. Gather multiple data sources. Exit interviews reveal why people leave (might be incomplete or sugarcoated). Stay interviews show what makes people stay. Engagement surveys reveal perceptions about culture, leadership, and opportunity. Demographic data reveals patterns—are high performers leaving? Are minorities leaving at higher rates?

3. Dig into the context. What’s happening in the industry? Is this competitive turnover or are people leaving work entirely? Are managers leaving people or is it individual contributors?

4. Identify root causes. High turnover might be about compensation, but it might be about management quality, lack of growth opportunities, misalignment with culture, or work-life balance. Different causes require different interventions.

5. Recommend specific interventions. Don’t just say “improve retention.” If the problem is management quality, you need manager training. If it’s compensation, you need market analysis. If it’s career development, you need succession planning.

Sample answer:

“I’d start by looking at the turnover data to understand patterns. Who’s leaving? When? For what reasons? I’d contrast that with industry benchmarks—is 20% annually high for this industry and company size? I’d also do exit interviews and honestly, I’d do stay interviews too because people who leave won’t tell you the whole truth, but people who stay will tell you what keeps them. I’d do an engagement survey focused on specific areas—management quality, growth opportunities, culture fit, compensation expectations. From there, the root causes usually become clear. I worked with a nonprofit with 35% annual turnover. The data showed that people left in their second year, which is classic ‘honeymoon wore off’ timing. Exit interviews blamed low salary, but stay interviews revealed that people who stayed felt like they were doing meaningful work and had a manager who invested in their development. It wasn’t actually about money. They needed management training and more intentional onboarding and mentoring. Once we invested there, turnover dropped 12 percentage points without changing compensation."

"How would you approach a situation where two departments have poor collaboration?”

Why they ask: Cross-functional silos are common organizational problems. Your approach to diagnosing and solving this reveals your systems thinking and ability to manage complex stakeholder situations.

How to think through your answer:

1. Look beyond personality. It’s rarely just that people don’t get along. Dig into structure, incentives, and clarity.

2. Understand each department’s perspective. Both departments believe they’re right. What does each one care about? What pressures are they under?

3. Identify structural barriers. Are there conflicting metrics? Do they report to different leaders who don’t align? Are their physical locations separate? Are there information barriers?

4. Assess relationships and trust. Even with good structure, poor relationships kill collaboration. Where’s the trust broken?

5. Co-design solutions with both departments. If you design the solution alone, the department you didn’t consult will sabotage it.

Sample answer:

“I’d start by interviewing key people in both departments—not together, separately. I want to understand how each one perceives the collaboration problem and what they think is causing it. Usually, they blame each other. Then I’d look at structure: Do they have shared goals or competing goals? Are they measured on things that create conflict? Do they actually need to work together or was someone assuming they should? In one case I worked on, Sales and Implementation had terrible collaboration. Sales was pushing implementation dates that weren’t realistic. Implementation felt blamed for client dissatisfaction. Turned out there was no shared success metric. Sales was measured on new deals, Implementation was measured on customer satisfaction. They had no reason to talk until someone created a shared metric. Then I facilitated a working session where both departments created a joint process for scoping engagements and setting realistic timelines. Once they had joint skin in the game, the collaboration improved significantly."

"An organization wants to implement a major technology change, but there’s significant resistance. How would you approach this?”

Why they ask: Technology implementations fail for people reasons, not technology reasons. They want to see your change management thinking.

How to think through your answer:

1. Understand the resistance. Is it fear of job loss? Lack of clarity about why the change is happening? Lack of involvement in planning? Skepticism about whether the technology will actually work? Different resistance requires different approaches.

2. Address readiness. Are people trained before go-live? Is leadership modeling the change? Are there quick wins to build confidence?

3. Think about adoption reinforcement. The launch day is not when adoption happens. What keeps people using the new system after launch?

4. Build champions. Who are the informal leaders who can influence peers? Can you turn resisters into advocates by involving them?

5. Communicate the why. People accept change they understand better than change imposed on them.

Sample answer:

“Technology resistance is usually about change management, not the technology. I’d first understand the resistance through listening sessions—what are people worried about? Then I’d focus on a few key things. First, crystal clear communication about why we’re doing this. Not ‘we bought this software’ but ‘here’s the business problem we’re solving.’ Second, involve people in planning if possible—having a say in how we implement changes perception significantly. Third, I’d build a champion network from every group who use the system and train them early so they can help peers. Fourth, I’d plan for significant upfront training and support—the error rate is highest in week one, so you need real support, not just a manual. Last, I’d build reinforcement into how people work. If the old system is still available as a workaround, people will use it. If performance is being measured, include how well the new system is being used. I was brought in mid-implementation of a new CRM when adoption was at 30%. We paused the system and spent three weeks retraining with a focus on ‘what’s in it for you’ instead of ‘here’s how to use it.’ Adoption jumped to 75% within a month because people understood the benefit."

"How would you help an organization define and embed its values?”

Why they ask: Values culture work is common in OD. They want to see that you understand the difference between values on a poster and values that actually shape behavior.

How to think through your answer:

1. Clarify what you’re actually trying to do. Is it articulating unarticulated values? Shifting the culture? Bringing new people into alignment? The process is different.

2. Involve people in defining values, not just announcing them. Values designed in an executive retreat don’t stick.

3. Make values tangible. “Integrity” means nothing. “Integrity” in this company means “we say what we think even if it’s uncomfortable” and “we admit mistakes immediately.” Behaviorally specific values actually guide decisions.

4. Embed values in systems. Put them in hiring criteria, performance evaluation, onboarding, and decision-making frameworks. Symbols matter (posters, language) but systems matter more.

5. Model the values at leadership. If leaders don’t live the values they’re asking employees to embrace, the whole thing is theater.

Sample answer:

“I’ve learned that values exercises fail when they’re top-down and vague. The ones that work start with listening. I’d facilitate sessions with diverse groups across the organization—not just leadership—and ask, ‘What do you believe makes this organization different? What do we do well? What do we stand for?’ From there, you identify the themes and get specific. A client said they valued ‘collaboration.’ When I asked what that meant, people said ‘we make decisions together’ and ‘we’re honest about disagreements.’ Those specifics became hiring questions and performance evaluation criteria. Then we built them into our meeting norms and our feedback culture. I also made sure leadership was visibly living the values. There’s nothing that kills values embedding faster than seeing leaders violate them. We revisited the values annually as a way to check if they still hel