Eliminating terminology conflicts: building a shared conceptual framework

In the process of strategy development, it is critically important that all team members share the same understanding of the terms being used. A lack of clarity around key concepts can lead to misunderstandings, hinder communication, and reduce the effectiveness of the work. That is why building a shared conceptual framework and eliminating terminology conflicts are an integral part of successful strategy development.

1. Why an introductory session for methodology alignment is needed?

An introductory session before strategy work begins helps synchronise team members, reduce misunderstandings, and speed up the process. Here is why it matters:

Synchronisation of participants. All team members start working within the same context, which reduces misunderstandings.
Time saving. If disagreements over terminology are resolved at the outset, the team moves more quickly to the substance of the strategic work.
Shared understanding of goals. Every participant understands what is actually required from the team throughout the strategy development process.

2. Key concepts: what to include in a mini-glossary?

A mini-glossary is a tool that captures key concepts and their definitions. It helps eliminate terminology conflicts and keeps the focus on the core tasks. The glossary should include all terms that have generated disagreement. For example, at one company’s strategic session, the word «client» was interpreted differently: for the sales team it meant the end consumer, while for logistics it meant the distributor. The introductory session made it possible to align the term and prevent further disputes.

Tip: Keep the glossary updated as you go and make sure it is accessible to all team members.

3. How to avoid terminology conflicts within the team?

Terminology conflicts frequently arise from differences in participants’ backgrounds, their areas of specialisation, or the fact that they work in different departments. To avoid these situations, follow these recommendations:

Aligning terms at the outset. The entire team must understand exactly what is meant by each term.
Discussing disagreements. When disagreements arise, it is important to discuss them and reach a shared position.
Using examples. Practical cases help bring abstract concepts to life.

A practical example: at one session, company managers disagreed on what counted as a «strength» of the business. For the sales team it was market reputation; for production, it was low cost of goods. After discussion, they agreed that in the context of the strategy, both aspects should be considered — but with different levels of priority.

4. Tips for successfully building a shared conceptual framework:

Run introductory sessions. The time spent on them will pay off through more productive work downstream.
Create mini-glossaries. Documented terms help avoid disputes and misunderstandings.
Update definitions regularly. As strategy work progresses, new terms may emerge that also need to be aligned.

Eliminating terminology conflicts is a key step that lays the foundation for productive strategy work. Clear definitions and a shared understanding of goals help the team stay focused on what matters and move toward success faster.

You might also be interested in

Case study: Building a transformation strategy for an IT integrator

We wanted a strategy to build on — not to be left behind.

Review of the strategy development project with ALSI Group

One of Alexander's most important and valuable qualities is his ability to ask the team very precise and uncomfortable questions — questions that led to unexpected solutions the team had never thought of before...