Skip to content
azimut

Domain Lab · Coordination

Dialogue LabA program for listening, disagreement and feedback

Dialogue Lab is our program on listening, disagreement and feedback for managers and team leads. Over 6–8 weeks, a cohort of 8–12 people works through three two-and-a-half-hour labs, applying each one with their own team between sessions.

Duration
6–8 weeks
Rhythm
one 2.5-hour lab every 1–2 weeks
Cohort
8–12 participants (15 at most)
Format
on-site or online

Who it’s for

When does a team need Dialogue Lab?

The problem usually arrives as one sentence: “everyone agreed in the meeting, and three of them were against it in the corridor.” Day to day, it shows up like this:

  • Meetings are polite, and the same problems come back next month, still undiscussed.
  • Anyone who brings a problem gets a solution before they have finished explaining it.
  • “Any thoughts?” at the end of a meeting is met with silence, and the objections surface later, in execution.
  • A disagreement between two colleagues turns personal, and the rest of the team checks out.
  • Feedback arrives once a year at the review, or sounds like “you should communicate better.”
  • People have stopped suggesting ideas because they feel shut down too quickly.

Is the problem more about execution, commitments that aren’t kept? Accountability Lab →

Want to work with a whole team, together with its leader? Team Performance Architecture →

The journey

What do participants work on in the three labs?

Dialogue is not politeness. Very polite teams and very harsh teams fail the same way: one doesn’t say things, the other says them badly. Dialogue is a team’s ability to think together, with candor and with respect. The three labs work in order: listening, then disagreement, then feedback. Each one starts from participants’ real situations and ends with something to apply with their team the following week.

  1. Lab 1

    Listen before you answer

    Active Listening & Understanding

    Understand, acknowledge, and only then respond: a summary before your reply, even when the other person is frustrated. Facts separated from interpretations and emotions, a complex problem led through questions alone, and the hardest one: an uncomfortable message about your own behavior, received without defending yourself.

  2. Lab 2

    Disagreement that builds

    Constructive Dissent & Conflict Navigation

    Inviting objections so that they actually come: a specific question, followed by silence, and the first objection summarized rather than defended. Disagreement voiced in four parts (what I see differently, why it matters, the risk I see, the alternative I propose), and tension named early. Each participant leaves with a real disagreement, prepared.

  3. Lab 3

    Feedback that changes something

    Feedback Exchange

    Feedback on behavior, impact and a genuine question, with the test that matters: does the person know what to do differently tomorrow? Feedback to a valued person who gets defensive, and receiving difficult feedback in five steps, including from your own team. Each participant leaves with the feedback they keep putting off, prepared and scheduled.

The order is deliberate: a disagreement can only be worked through if someone is listening, and feedback is the same move as disagreement, applied to behavior. The first lab lays the ground for the other two.

Between sessions

What happens between the labs?

The lab is the smaller part. The change happens in the weeks between sessions, in the real work.

Before each lab
a short microlearning: one video and a one-page job aid.
AI practice, twice a week
10–15 minute sessions with an AI coach on real situations: a frustrated colleague who needs to be understood before being answered, a silent meeting where the objections need to come out, feedback for someone who gets defensive. The feedback is built on the models from the lab.
A field assignment
every lab ends with actions for the following week: a conversation where you summarize before you reply, a decision preceded by an explicit call for objections, the feedback you have been putting off. The next lab starts from what happened.
Real cases
before each lab, the sponsor sends us a live situation from the organization: an issue people keep raising that never gets heard, a forum where “everything is fine,” missing feedback that is costing the team. We work through it together in the lab.
The participants’ own managers
get a briefing at the start and, every week, one question to use in conversations they are already having, such as “What’s the main concern here?” before offering any suggestion. Their job is to reinforce, not to assess.

How it runs

The same spine, adapted to the program.

DiagnosticLive LabsAI PracticeWorkplace ApplicationManager ReinforcementReview

The program spine: from diagnostic to review

Measurement

How is progress measured?

Baseline
a questionnaire on the three capabilities and on how hard conversations happen in the organization, completed before the first lab.
Along the way
after each field action, a two-minute reflection log shows what is being applied and where it gets stuck.
At the end
the same questionnaire, two weeks after the last lab, in which participants also rate how much they feel they have changed on each capability. The line manager observes the same behaviors twice: before the first lab and at the end.
For the sponsor
a cohort report showing each capability before and after and the patterns that keep recurring, discussed in an executive review. How much participants feel they have changed is reported next to the measured change and the managers’ view, and never goes into the score.

The questions are the same before and after, so progress can be compared rather than described. The report also counts what can be counted: how many decisions were preceded by an explicit call for objections, and how much feedback passed the specificity test.

Frequently asked questions

Three 2.5-hour labs, one or two weeks apart, plus two weeks of application after the last one: 6–8 weeks in all. Between labs: a short microlearning before each session, AI practice twice a week for 10–15 minutes, and field assignments with their own team.

Managers, team leads and functional leaders, in a cohort of 8–12 people (15 at most). It fits when the same symptoms show up across several teams: polite meetings where what matters goes unsaid, conflicts that turn personal, feedback that is rare or vague. If you want all four domains for managers, Manager Operating System is the right format.

A course delivers content over a day. Dialogue Lab builds behavior over time: every lab is followed by application with the team, practice, and questions from the line manager, and progress is measured before and after with the same questionnaire. And the focus is not pleasant communication but the hard conversations that decide the quality of decisions: the objection that would otherwise stay in the corridor, the postponed feedback, the tension nobody names.

Yes. One lab, with practice and a guide for managers, is the simplest way to test the approach; two labs cover the most pressing capabilities. Measurement grows with the format: for a single lab, a short pulse before it and again two weeks after, with the same questions; for two labs, a short before-and-after test on the capabilities covered; for the whole domain, the full questionnaire. From two labs up, the line manager also observes the same behaviors at the start and at the end.

A small, precise role of about 15 minutes a week. They get a briefing at the start and one question a week to use in conversations they are already having with their people. They reinforce rather than assess. At the start of the domain and again at the end, they observe the same behaviors, and their concrete examples go into the sponsor report without names.

AI is the practice partner between labs; it does not replace facilitation. Each participant rehearses their own real situations with a coach set up on the program’s models. The conversations stay private: we only see the reflection log, and the sponsor gets cohort-level results, not individual assessments. We agree the tools and the rules of use with you before the start.

Yes. Labs run at your offices or online, in Romanian or English. Online, the drills happen in small groups and the live case is worked through together on a shared whiteboard.

Pricing depends on the format (one lab, two, or the whole domain), the number of participants, the language, and how much we tailor the cases. We give you a concrete price after the first conversation, once we know what you want to change.

Further reading

Start with a conversation

Tell us the behavior you need to change. We’ll show you the system that changes it.

A 30–45 minute diagnostic conversation, no pitch deck. You’ll leave with a sharper read on the capability gap, whether or not you work with us.