How to read direct criticism and detailed planning when working with a German team

A short, firm email: criticism of the project or of the person?

A message arrives for the Polish team: “This is not acceptable. Please revise the timeline.” There is no lengthy introduction and no praise for earlier work. The manager takes it as a sign of clear hostility, and his colleague says: “That’s just how they are.” Both interpretations are premature. All the email tells us is that the partner does not accept the schedule and is asking for it to be revised. We don’t know whether it is about a lack of time, quality requirements or genuine dissatisfaction with the relationship. The best reply starts with the facts: “Which part of the schedule doesn’t meet the agreed requirements, and what deadline do you need?” A question like this does not require you to accept the tone of the message. It lets you work out what it means for the business. If the collaboration is long-term, it is also worth discussing how feedback is given – but only once both sides understand which substantive problem they are talking about.

What the research on German communication style actually tells us

Cross-cultural research and models of organisational practice describe differences between particular groups and contexts. They are not, however, an instruction manual for every employee from a given country. Eva Ogiermann’s 2009 study analysed how requests are phrased in English, German, Polish and Russian in a specific scenario. It did not examine every situation in which work is criticised, nor any “national character”. So it cannot be used to claim that German partners always speak directly and Polish ones always more gently. Within the same organisation, styles differ between the legal department, sales and engineering. Professional experience, position in the project, time pressure and language proficiency can all matter. A meta-analysis by Stahl and colleagues shows that cultural diversity can affect collaboration processes, but it does not determine the outcome of any single working relationship. The safe practice is to check the habits of the specific team: “How do you usually give comments on a draft, and when do you consider it accepted?”

Acceptance criteria help more than guessing the tone

When a German colleague says “This plan is unrealistic”, it is easy to start defending your own competence. It is worth first establishing what “unrealistic” means. Are two days missing for testing? Was the wrong sequence of work agreed? Does the risk depend on an external supplier? You might reply: “I understand we can’t sign off the current date. Is the problem the testing stage, resources or the client’s requirements?” Then write down four things: the requirement, the gap observed, the person responsible and the deadline for clarification. If the criticism is justified, making the correction does not mean admitting that the whole team did a bad job. If it is not justified, you can calmly present the data: “With the current scope of testing, we have confirmation that we can deliver. If you expect an additional scenario, let’s agree the cost and the deadline.” A conversation conducted like this turns an emotionally loaded assessment into verifiable decisions and agreements.

Why a detailed plan can help build trust

A detailed schedule is sometimes seen as excessive rigidity, but in projects that depend on many teams it may simply expose risks earlier. The partner wants to know what their stage depends on, who confirms acceptance and what will happen if there is a delay. Rather than talking about a “German need for control”, it is worth asking what the plan will be used for. It helps to separate the fixed elements, such as an audit date or a safety requirement, from assumptions that may need updating. For example: “We will deliver a test version by 15 December, assuming we receive the input data by the end of November. If that doesn’t happen, we’ll revisit the schedule within two days.” An entry like this does not pretend to be certain. It shows the dependencies and how you will respond to change. Flexibility does not require giving up the plan, and a detailed plan does not rule out changes. Together, you can design the level of detail that genuinely helps the work.

How to agree rules for giving comments without guessing intentions

It is worth agreeing three rules for giving comments separately. First: where do we give critical comments – publicly, or directly to the person responsible for the task? Second: which word or label means acceptance, and which means only a request for changes? Third: how do we signal that the way a comment is phrased is making collaboration harder? An example sentence: “I appreciate clear comments on the project. When an assessment comes without a criterion, the team doesn’t know what to fix. Could we always include the relevant point of the specification?” If you need people to speak differently in meetings, name it just as clearly: “I’d prefer us to discuss critical issues concerning individuals one-to-one.” There is no reason to demand that your partner change their personality. It is enough to agree rules that help both sides. Remember that the Polish team, too, may send messages that are too ambiguous, put off replying or fail to confirm decisions. The rules work both ways.

When criticism crosses the line of professional conversation

There is a difference between saying “This report doesn’t meet three of the requirements” and “You have no idea what you’re doing.” The first is about the work and can be checked. The second is an attack on the person. Likewise, public ridicule, threats or persistent humiliation do not become acceptable just because someone explains them away as national style. If you receive a message like that, name the behaviour: “I want to discuss the errors in the report, but I don’t accept my competence being judged in this way. Let’s go back to the requirements and the proposed corrections.” If breaches keep recurring, it is worth documenting the incidents and using the company’s established procedures. You should not, however, treat every short email as evidence of hostility. In everyday collaboration, what helps most is distinguishing between the content and form of what is said, and recurring patterns of behaviour. This makes it possible both to respond matter-of-factly to a demanding assessment and to set a firm boundary when that becomes genuinely necessary.

Direct criticism does not have to be an attack, and a detailed plan does not have to mean rigidity. Instead of interpreting what someone says through a national stereotype, it is worth establishing the facts, the acceptance criteria and how concerns should be raised. Clear expectations help both when the differences lie in conversational style and when the problem stems from an imprecisely defined project.

How Em helps you respond to criticism and agree a plan with a German team

Michał receives a short, critical email from a German partner. His first reaction is to defend his team, even though he doesn’t yet know which stage of the project is causing concern. He pastes the text of the message, without any confidential data, into his conversation with Em, along with his own proposed schedule. He asks Em to separate the facts from his reading of the tone and to help him prepare a calm reply. Em points out which information is unclear and helps him frame questions about the acceptance criterion and the corrections needed. Michał also rehearses a live conversation in case the partner says again that the plan is “unrealistic”. Instead of replying “You always exaggerate”, he proposes a shared table of dependencies and deadlines. If Empatyzer gives him context on how this person prefers to collaborate, he can use that information when choosing how to respond. After the meeting, they agree on labels for decisions, rules for updating the schedule and where critical comments should be raised. In this way, Em helps him move from the tension caused by an email to concrete rules for working together.