How do I plan my first conversations with people whose work I’ll now oversee or coordinate?

Treat the first conversation as a chance to understand the work, not evaluate the person or announce a plan. Before meeting, decide what you need to learn: what each person is responsible for, what matters now, and where work depends on others. Keep the meeting focused; arrange a follow-up for anything that needs more time.

You could open with: “I’d like to understand how your work currently fits together and what would make coordination useful. I’m here to listen first, not to assume anything needs changing. Is there something you’d especially like me to understand?”

If you already know about a constraint or change, state it plainly. Explain what you can decide, what you need to learn more about, and what is outside your control.

Ask for examples, not just a job-title summary. Useful prompts include:

1. “What are the main things you’re responsible for in a typical week?”
2. “Which responsibilities need the most attention right now?”
3. “What outcomes or deadlines matter over the next few weeks?”
4. “What work is less visible to others but still takes time or matters?”
5. “Where do you have discretion, and where do you need input or approval?”

Listen for the difference between ongoing responsibilities and temporary projects, then check your understanding. If priorities conflict, ask how the person handles that now and whether a joint decision is needed. Don’t promise to resolve competing demands before you know who can decide.

Ask about how work moves and what makes it easier or harder, rather than who is at fault. Try: “Where does your work usually come from, and who depends on what you produce?” “What information do you need at a handoff?” “Where do delays or unclear ownership tend to show up?” or “What would make one upcoming handoff go more smoothly?”

If someone describes a difficult interaction, ask what was needed and what happened next; don’t push them to label a colleague. If a concern needs a decision you cannot make alone, note it as an open question rather than presenting a quick fix as settled.

Before moving on, summarize one or two points: “I heard that you own X, Y is the near-term priority, and expectations for the handoff from Z can be unclear. Have I got that right?” Give them a chance to correct you.

Use a compact template that separates what the person told you from your interpretation and next steps:

“Conversation with: [name or role] | Date: [date] Responsibilities: [work they own] Current priorities: [near-term work or deadlines] Dependencies and handoffs: [input they need; who uses their output] What helps coordination: [information, timing, or decisions they said they need] Open questions: [what to confirm; who can clarify] Agreed next step: [action] | Owner: [person] | Check-in: [date or ‘to be agreed’] My understanding to confirm: [brief summary]”

For example, suppose a coordinator prepares a weekly schedule, needs team updates by Tuesday, and sends the schedule on Wednesday. Notes might say: “Responsibility: prepare and share weekly schedule. Dependency: team updates by Tuesday. Open question: what happens when an update arrives late? Next step: ask affected people how late changes should be handled.” This records a coordination question without assigning blame or deciding the answer in advance.

Close with: “What have I missed? Is there anything you’d like me to check before I follow up? I’ll [action] by [timeframe], and we can revisit [open question] then.” Record only information needed to coordinate the work, and treat your notes as a starting point, not a definitive account of someone’s role.