The Third Field™ · Team Map
For the launch team
This specimen imagines a Map the participants have reviewed and permitted to be shared. Their words and the Director’s interpretation are distinguished below. An absent perspective is not agreement.
At a glance
The shared aim: you wanted to put useful work into customers’ hands. Your accounts differ about what needed to be ready first, and what the launch vote settled.
What to protect: colleagues still help one another, care about the product and challenge ideas in design reviews. The capacity for useful disagreement is already here.
The Third Field signature: visible agreement, unaddressed reservations, and uneven confidence that speaking will matter. The recorded yes concealed different meanings of support.
The business cost: planned work has given way to fixes and customer workarounds. Time that could go into the product is also going into arguing about what was previously raised or agreed.
The question to work with: how can a concern become part of the decision while there is still time to use it?
1. The same vote, different meanings
Dana, the product lead, describes a meeting with a launch date already in view. A few voices pressed strongly for shipping. The final question was whether to proceed. Dana understood the result as a commitment to the plan.
I heard support for launching. I did not understand that some of those yeses still had conditions attached.
Dana · invented shared words
Mei, an engineer, supported getting the product into use but thought reliable bulk uploads and a way to recover a failed upload needed to be resolved first. Ravi, a designer, describes putting those concerns in a review document without seeing them discussed in the launch meeting. Sam, who works with customers, describes pressure to meet promises already made.
My yes meant yes once those gaps were covered. The decision log only kept the yes.
Mei · invented shared words
These accounts do not show that everyone opposed the launch or that delay was the only sound choice. They show that the recorded decision did not preserve a difference that mattered to the work.
2. Where disagreement still helps
Mei, Ravi and Olu describe design reviews where an unfinished idea can be challenged and improved. People ask for evidence, change their minds and stay involved. Olu, who coordinates operations, also describes colleagues stepping in when customer work becomes difficult.
This matters because the team is not uniformly silent or unwilling to help. Your accounts locate the difference in the conditions around the launch: time pressure, promises already made, a few voices setting the direction, and a question that allowed a yes or a no but left little room for a condition.
What makes a concern useful in design review, but difficult to bring into a launch decision?
3. What the customer request brings back
Customers now ask for the bulk-upload features that Mei and Ravi wanted addressed before launch. Sam describes trying to respond while hearing colleagues say they had warned about these gaps. Olu describes discussions moving quickly from what the customer needs to what people said in the earlier meeting.
We start with a customer problem and end up arguing about whether anyone listened the first time.
Olu · invented shared words
The Director’s reading is that the present request carries an earlier unresolved experience: some people believed support had been secured; others did not believe their reservations had been heard. “We agreed” and “we raised this” can both be accurate descriptions of different parts of that meeting.
The field becomes fragmented when a common decision no longer means a common understanding. A concern that once asked for attention can return as frustration; those trying to deliver the launch may hear that frustration as withdrawal of support. This is a possible connection for you to correct, not a judgment about anyone’s loyalty or temperament.
4. Where the business pays
Mei describes planned engineering work being interrupted for fixes. Olu describes manual workarounds for customers. Sam describes revisiting promises and explaining what the product can currently do. Dana describes spending meeting time reconstructing the launch discussion instead of settling the response.
The cost is therefore not only an uncomfortable room. In this fictional case it appears as rework, displaced priorities, extra customer support and time spent reopening the past. If the pattern continues, customer confidence and people’s willingness to raise the next concern may also be at risk; those are risks to examine, not measured outcomes here.
No financial loss or engagement score has been calculated for this team. To understand the scale, look at your own unplanned work, support effort and commitments displaced. Product readiness still requires technical evidence and action; a better conversation does not itself deliver a missing feature.
5. A concern needs somewhere to go
The next step is not simply to give everybody more speaking time. It is to make visible what happened to the concern: was it understood, answered, accepted as a risk, or left unresolved? A leader can make a decision that someone disagrees with and still show that their judgment was considered.
What did your support mean—and what would have needed to happen for you to stand behind the same plan?
When a reservation was raised, what response showed that it had entered the decision?
What needs attention now for customers, and what needs repair in the way you hear one another?
One trial to consider: keep the conditions with the decision
For the next significant release decision, try making the differences visible before asking for a final choice.
- Before the room
- Each person considers their position privately: support, support with conditions, not ready, or more information needed. They choose which concerns and reasons to bring into the decision.
- In the room
- Hear the positions before debating them. Check that the conditions have been understood. Record the response to each material concern alongside the decision, including an unresolved risk and the reason for proceeding if that is the choice.
- The choice
- Hearing every voice does not make every decision unanimous. Confirm together who has authority to decide and what support for the resulting plan means. An objection remains an objection unless its author changes it.
- The return
- Choose a first decision, a person to convene the review, and a date to look back. Were concerns visible while they could still affect the choice? Did people understand the response, even where they disagreed?
- The work
- Look at avoidable rework, customer workarounds and displaced commitments alongside the effort the trial added. Compare with your own earlier work in context; a different release may carry different risks.
This is a proposal to adapt or decline. It is not a signed Team Charter or evidence that alignment has already been reached.
About this reading
All people, circumstances and quoted words are invented. The example uses shared material only and illustrates how a Director can connect accounts, keep disagreement visible and offer a trial. A real shared Map follows each participant’s permissions and review; private Folios and Director-only answers do not supply its interpretation. Wider engagement research is context for the practice, not a finding about this fictional team.