top of page

Organizational Preparation for Difficult Conversations: Conversation Flow and Record Structure

Sep 28
7 min read

Updated: Sep 30

Organizational Preparation for Difficult Conversations
Organizational Preparation for Difficult Conversations

A period in which performance expectations are not met, a role change, a disagreement within the team, a response to a pay request — but equally, turning down a customer’s request, renegotiating contract terms with a supplier or delivering unwelcome news to a business partner are all difficult conversations. What they have in common is that, whoever the other party is, they need to be approached with preparation.


Difficult conversations are usually discussed through the manager–employee relationship, yet the scope is broader. Every employee working in functions such as sales, customer service, field operations and supply chain will at some point in their career need to hold a conversation of this kind. The preparation framework and record structure should therefore be designed not only for the management team but for every employee who may have to hold a difficult conversation.


The organization’s role is shaped accordingly. Human Resources designs the framework, provides the tools and offers support when needed; preparing for and conducting the conversation, however, is the responsibility of the person who will hold it. Making this distinction clear ensures the process is adopted not merely as an HR practice but as an organizational competency.


The value of this approach shows up on more than one side. The person conducting the conversation knows in advance which information they will bring and which decision they will communicate; on the organization’s side, because the outcome is recorded, subsequent decisions rest on a documented basis.


When Do Difficult Conversations Arise?


The first step is to define the situations in which difficult conversations arise. These can be grouped into two categories.


Internal conversations include periods in which performance expectations are not met, warnings about conduct and working principles, a negative response to a promotion or pay request, role and job changes, disagreements within the team and the end of the employment relationship.


External conversations are handled less systematically, yet they are just as critical for the organization’s reputation and customer relationships. Being unable to fulfill a service request, notifying a customer or supplier of a price increase or contract terms, responding to a complaint and ending a business partnership all fall into this group. The person conducting these conversations is often not a manager but a sales representative, a customer relations specialist or an employee in a field team.


Compiling this list gives the organization two advantages. First, it becomes possible to define which data needs to be ready for each situation. Second, it becomes clear which unit the person conducting the conversation will turn to for support on which topic. For internal matters, this support may come from HR; for matters involving customers or suppliers, from the relevant business unit or the legal function. This narrows the area in which the person is expected to decide alone before the conversation.


For senior leadership, this definition is a matter of risk management. Unrecorded, unprepared conversations weaken the information the organization holds — internally in employment law proceedings and externally in commercial disputes. A defined preparation and record structure makes it possible to demonstrate the rationale behind a decision after the fact.


For each topic, the organization also documents which decisions are made by the person conducting the conversation and which by the relevant manager, HR or senior leadership. On topics such as pay, title, contract terms and ending an employment or business relationship, decision authority is usually not something the person conducting the conversation carries alone. Clarifying this before the conversation prevents them from making a commitment they cannot deliver on.


Pre-Conversation Preparation Framework


Preparation starts with writing down the purpose of the conversation in a single sentence. The person conducting it separates, at the outset, the decision that will be communicated to the other party by the end of the conversation from the topics that are open to mutual discussion. Without this distinction, the conversation shifts back and forth between communicating a decision and gathering input, and can leave the other party unsure of what to expect.


The second step is data preparation. For internal conversations, performance records, target achievement rates, notes from previous conversations, training and development history and any earlier warnings are gathered together. For conversations with a customer or supplier, contract terms, previous correspondence, service records and any complaint history are compiled in the same way. The relevant unit provides this information to the person conducting the conversation in advance and specifies which information may be shared.


The third step is deciding on time, place and participants. The length of the conversation, the setting, whether a second representative will attend and keeping the parties’ schedules suitably clear afterwards are all planned. Conversations squeezed into the end of the working day or into a busy day reduce how well the decision is understood.


The fourth step is preparing for possible reactions. The person conducting the conversation works through, in advance, the points the other party may object to and how they will respond. The aim is not to memorize lines but to set the limits of how much information will be shared on each topic. The organization can support this with a short rehearsal; for people holding this kind of conversation for the first time in particular, rehearsal is one of the most effective parts of preparation.


Designing the Conversation Flow


The organization gives the person conducting the conversation a single flow template. The template follows the same sequence in every situation, while the content changes according to the situation and the counterpart. The components of the flow are defined as follows:


Purpose statement: The subject and scope of the conversation are stated first.


Concrete data: The assessment is communicated with information that includes examples and dates.


The other party’s perspective: The counterpart’s explanation is heard without interruption.


Decision and rationale: The decision and the criterion it is based on are stated clearly.


Expectation and timeline: The behavior, output or step expected, and by which date, is defined.


Support: The support on offer is specified — internally this may be training, coaching or a job adjustment; externally, an alternative solution, compensation or revised terms.


Closing summary: What was discussed and the next step are restated in two sentences.

The part of this flow most often skipped is the closing summary. When the conversation ends right after the decision is communicated, each party may leave with a different understanding. Restating the summary aloud during the conversation also leaves a shared text for the recording stage.


Keeping a single template also makes training easier for the organization. When employees in different functions apply the same sequence in different situations, the examples discussed in development sessions settle into a common language, and newly assigned staff pick up the flow quickly. Adding a two-page practice note to the template leaves a resource that can be used outside the sessions as well.


The length of the flow is planned in advance too. For conversations that involve communicating a decision, a forty-five-minute slot is sufficient in practice, with half of that time set aside for the other party’s perspective. A shorter conversation limits the other party’s account, while a longer one can cause the discussion to drift.


Record Structure and Follow-Up


The organization defines a single form for recording. It covers the date of the conversation, participants, subject, the decision communicated, the other party’s perspective, the agreed expectation and timeline, the support offered and, where applicable, the date of the next conversation. The form is completed shortly after the conversation, as details can be lost when time passes.


Where the record is stored and who can access it are documented as well. For internal conversations, records entered into the employee file are kept separate from the conducting person’s own follow-up notes, and the employee’s right to access their own record is defined in line with personal data protection obligations. For conversations with a customer or supplier, the record is usually entered into the relevant CRM system and is subject to commercial confidentiality rules. This clarity helps record-keeping become a habit.


Alongside the form, the person conducting the conversation fills in a short preparation note beforehand. The note covers the purpose of the conversation, the decision to be communicated and the data to be shared. Reading the preparation note together with the conversation record shows the gap between what was planned and what was communicated — and that gap is the most concrete input for development sessions.


On the follow-up side, the organization tracks three indicators: whether the expectation has been met by the end of the agreed timeline, the number of repeat conversations on the same topic and the uptake of the support offered after the conversation. We cover the calendar and record structure of performance reviews in our article performance reviews: how HR builds the calendar and record structure.


The approach developed in these conversations is also a frequent focus in individual coaching. You can read how the organizational impact of coaching is measured in our article how to measure the impact of coaching within the organization.


Read together, these three indicators show the organization whether the preparation framework is working. Repeat conversations on the same topic point to a gap in preparation or support; unused support shows that it does not match the need. For senior leadership, this reading provides concrete input on which topics and which employee groups the development budget should be directed to.


Once difficult conversations are no longer left to the personal style of a particular group of staff and are defined through a preparation framework, a flow template and a record form, they become an organizational practice regardless of who the counterpart is. To structure your employees’ preparation in this area, explore our 'Managing Difficult Conversations' training program and our executive coaching services.


As Kaan Böke Management Consulting, we offer strategic and actionable solutions drawing on 35+ years of corporate experience and a 25+ year C-level leadership perspective. To build an organizational preparation framework for difficult conversations and define its record structure, get in touch.

Comments


bottom of page