"When you're right, you're right, Jerry"

In the previous post I wrote that accurate wording and the facts, on their own, do not guarantee a move forward. Today, the practices that actually help teams keep a working pace, solve problems faster, and stay constructive. All of it from research by Google (Project Aristotle), McKinsey, and Harvard Business Review.

This matters: it is not about “being positive all the time”. A supportive environment raises performance. It does not mean pretending everything is fine.

💡 1. A sync before the discussion

A short alignment of expectations before the conversation reduces misunderstanding and saves time.

Why it works: HBR notes that the opening frame of a meeting affects the quality of decisions and reduces cognitive bias.

How to use it:

• Yourself: before the discussion, ask, lightly: “So we stay on the point — what result do we need from this meeting?”

• The team: agree that every meeting starts with the goal and the result you expect.

• The company: make it a norm: meetings happen only with an agenda and a desired outcome.

🤝 2. The principle “one team, one vector”

Putting the shared goal in view lowers “local thinking” and helps people look for solutions more widely.

Why it works: McKinsey points out that teams with a single focus reach their goals 20–30% faster, because the effort is synchronized.

How to use it:

• Yourself: bring into the conversation not only the problem but the link to the shared goal: “I am raising this so we get to result X faster.”

• The team: once a week, briefly check the shared priority: what is the main thing right now.

• The company: write down, and regularly update, “the single priority of the period”, a quarter or a month.

🐣 3. Psychological safety in a working form

An environment where you can talk calmly about difficulties, mistakes, and ideas raises the quality of decisions.

Why it works: Google (Project Aristotle) showed that psychological safety is the main factor in a team’s effectiveness, ahead of the experience and competence of the people in it.

How to use it:

• Yourself: offer ideas in an open form: “This is a sketch. Let’s see what can be improved.”

• The team: add a short feedback ritual with no search for the guilty: “what worked / what we will try differently”.

• The company: build a culture of discussing mistakes as material for improvement, not as a source of accusations.

🆘➡️✅4. State a difficulty as a path to a solution

The focus is not on “why this is bad”, but on what will move the situation.

Why it works: HBR research shows that a problem-solving approach lowers emotional tension and raises involvement in the solution.

How to use it:

• Yourself: when you describe a problem, add: “What I think could help is …” (even if it is one step).

• The team: agree that every question is raised together with a version of the first step.

• The company: teach people the basic tools for structuring a solution (for example, 5 Whys, a problem tree, hypotheses).

✍️5. Write the agreements down

Transparency lowers the risk that important decisions “dissolve” or get read in different ways.

Why it works: McKinsey notes that writing things down clearly speeds up execution and reduces repeat discussions.

How to use it:

• Yourself: after a meeting, briefly write the shared outcome and the steps: 3 to 5 points.

• The team: agree on one format for the outcome: who does it, what they do, and by when.

• The company: make a simple standard for recording decisions, so the information is available and easy to find.

We cannot always change the whole system. We can start at the level we actually have. Sometimes a small change in wording, habit, or ritual already has an effect, for us and for the people next to us.