Peer One-to-One Meetings

What success looks like

Use lightweight peer conversations to improve coordination and working relationships. The practical test is whether the people involved can point to fewer cross-team surprises and stronger mutual context without reconstructing the whole conversation.

If the same meeting also needs useful organizational insight and a safe route for themes, read How to Run a Skip-Level Meeting before finalizing the design.

A practical method

Set the boundary for the work

Write fewer cross-team surprises and stronger mutual context as the boundary. Keep only the evidence, authority, and participation needed to produce that specific result.

Work through the sequence

Share near-term changes, dependencies, friction, useful feedback, and one concrete offer or request; revisit only at a cadence that earns its time. Place that instruction in the shared workspace and use it to distinguish the real work from background discussion.

Create a usable record

A durable record should make sense beside this example: Two team leads compare upcoming decisions and resolve one ownership gap before it becomes an escalation. Name any owner, due point, decision rule, or review trigger needed for another person to act.

Worked example

Two team leads compare upcoming decisions and resolve one ownership gap before it becomes an escalation.

Copy this example

The example connects directly to fewer cross-team surprises and stronger mutual context. Put similarly concrete wording in the invitation, agenda, or record so the result can be checked later.

A failure to avoid

Watch for Creating another status meeting or using the conversation to route around accountable owners. If it appears, pause and compare the discussion with fewer cross-team surprises and stronger mutual context before more meeting time is used.

A useful recovery question

Ask: “What is the smallest responsible move that would still create fewer cross-team surprises and stronger mutual context?” If the answer depends on missing evidence, record that evidence, one owner, and the exact return condition.

Final checklist

• The stated goal is fewer cross-team surprises and stronger mutual context.
• The working method is visible to everyone involved.
• The record is specific enough to support an example such as: Two team leads compare upcoming decisions and resolve one ownership gap before it becomes an escalation.
• The design actively guards against Creating another status meeting or using the conversation to route around accountable owners.

Next, use the one-to-one planner to turn the method into a working artifact.