Partnership meetings

Key takeaways

  • Define the partnership question.
  • Verify relationship context.
  • Bound every next step.
Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

Operating data

Primary workflowPartnership meetings
Reading time2 minutes
Internal next steps2 links
External citation1 source

Playbook

A strategic partnership meeting deserves more than profiles and biographies. The executive needs to know why the relationship matters now, what each side may decide, which assumptions remain unverified, and what a useful next step looks like. Write a one-sentence purpose and separate decision question; explore partnership is too broad to guide preparation.

Confirm who requested the meeting, how the introduction occurred, relationship stage, and executive owner. The executive relationship map guide connects history to purposeful contact. Build attendee cards from approved and public sources: role, remit, interactions, interests, pronunciation, and open commitments. Mark inference clearly and never copy sensitive notes across relationships.

Organize evidence into confirmed common ground, questions to test, boundaries requiring specialist review, and decisions available in the room. Validate dates, program names, public statements, and relationship claims. Harvard Program on Negotiation guidance explains why alternatives and boundaries matter; authorized leaders still define organizational positions.

Prepare a run of show: opening context, priorities, discovery questions, areas of fit, risks, dependencies, and requested close. Add time for disagreement. For virtual meetings, verify host rights, permissions, time zones, accessibility, and backup channel. If an identity cannot be verified, show the gap rather than inventing context. Keep confidential positions out of unrestricted invites.

Capture statements as proposals, questions, decisions, or commitments; enthusiasm is not agreement. Read back each next step with owner, scope, dependencies, review authority, and target date. If either side needs approval, record it before follow-up implies commitment. Draft an owner-approved recap and route actions through operations follow-through.

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

FAQ

When should a leader delegate this workflow?

Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.

What should the assistant own first?

Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.