Working in partnership: The foundation of effective facilitation

Early in my facilitation career I was commissioned to design and deliver a two-day strategy event for a regional public sector organisation. The brief came through a single email. It described the desired outputs, the number of participants and the date. I prepared a thorough design, confirmed the logistics and arrived on the day ready to work.

The session began well enough, but within the first hour something started to feel wrong. The senior leader in the room kept interrupting the process to reframe what was being discussed. Several participants seemed uncertain about why they were there and what authority they had. By mid-morning a significant tension had emerged between two teams whose interests were in direct conflict on the core question, and no one had told me this in advance. The design I had prepared was not equipped for what the room actually contained.

At the lunch break I spoke privately with the sponsor. It turned out that the organisation was in the middle of a restructure that had been announced three weeks before the session. Several of the participants were uncertain about their own futures. The senior leader had not been part of the original brief and had very different expectations from the person who had commissioned the work. The email I had received eight weeks earlier described a world that no longer existed.

The afternoon recovered, partly because I was able to adjust the design and partly because I had enough experience to hold the room through the discomfort. But the session never reached what it could have reached, and the outputs reflected that. When I reviewed it honestly afterwards, the problem was not the design. It was the absence of a genuine partnership before the design began. I had agreed to deliver an event. I had not built the relationship that would have given me the information I needed to design it well, or the standing to adapt it honestly when circumstances changed.

That experience is the most instructive failure I can point to for why IAF Core Competency A1, Develop Working Partnerships, comes first in the framework. It is not procedural housekeeping before the real work begins. It is the ground on which everything else rests. Without trust, clarity and shared ownership between facilitator and client, even the most carefully designed session is working from an incomplete picture of the situation it is meant to serve.

The three strands of developing working partnerships

In practice, this competency rests on three reinforcing strands:

  • Clarifying mutual commitment
  • Developing consensus on tasks, deliverables, roles and responsibilities
  • Demonstrating collaborative values and processes

These are not steps to be completed in sequence and set aside. They are threads woven through the whole arc of the engagement, from the first conversation with the client through to the final debrief. When all three are tended well, the facilitator and client are genuinely working together rather than operating in adjacent lanes. When any one is neglected, the gaps tend to appear at the worst possible moment: when the stakes are highest and the margin for misunderstanding is smallest.

Clarifying mutual commitment

This strand is about uncovering not only what the client wants but what both parties need in order to do the work well. Wants are outcomes: a strategy, a decision, a shared vision, a set of priorities. Needs are the conditions that make those outcomes possible: access to the right people, enough time to prepare properly, the willingness to have honest conversations, the authority to adapt the design when the situation requires it.

Naming both at the beginning creates a shared frame that both parties can return to when circumstances change, as they almost always do. When this conversation happens well, trust is established early enough to be resilient when it is tested. When it is missed, assumptions take the place of agreements, and those assumptions typically surface at the moment when they are most costly to discover.

Developing consensus on tasks, deliverables, roles and responsibilities

Once the direction is agreed and the conditions named, attention turns to the specifics of how the work will be done and who will carry which part of it. This is more than a project plan. It is a shared understanding of what a successful outcome looks like, who holds responsibility for each element, and how decisions will be made along the way.

Without this clarity, facilitators and clients can leave the same event with genuinely different accounts of what was achieved. A colleague once delivered a national consultation that produced detailed and well-evidenced insights. When she presented the outputs, the sponsor was disappointed: they had expected a prioritised, costed action plan. Because there had been no shared definition of deliverable, the work was undervalued regardless of its quality. The difficulty was not the facilitation. It was the absence of the conversation that should have preceded it.

Demonstrating collaborative values and processes

The third strand is lived day to day across the whole engagement. Partnership is not built once in a contracting conversation and then stored. It is sustained in the quality of the behaviours both parties bring into every interaction. If a facilitator speaks of collaboration but makes significant design decisions behind closed doors, the message is communicated clearly even if unintentionally. If a client sponsors a participatory process but has already decided the outcome, participants will feel it, and trust in the process will erode.

Demonstrating collaborative values means being transparent about why and how decisions are made, inviting the client into shaping the process rather than presenting finished plans for approval, and sharing credit with generosity when things go well. These are not soft gestures. They are the material from which engagement is built.

Reflections on clarifying mutual commitment

The conversation about mutual commitment is the one most frequently abbreviated or skipped altogether. There are understandable reasons for this. Clients are often time-pressured. Facilitators can feel that asking for what they need risks appearing difficult or insufficiently client-focused. The email arrives with a brief, a date and a number of participants, and the temptation is to begin designing rather than to pause and establish the relational foundation the design will depend upon.

Research on consulting relationships consistently shows that this abbreviation is among the most expensive mistakes a practitioner can make. Edgar Schein’s foundational work on the helping relationship, developed across several decades of research and practice in organisational consulting, describes what he calls the problem of premature advice: the tendency of consultants and facilitators to move toward solutions before they have adequately understood the situation. Schein argues that this tendency is driven partly by the cultural expectation that experts should quickly demonstrate competence, and partly by the anxiety of not yet knowing enough to feel useful. The effect is that the practitioner designs for the problem as it was initially presented rather than for the problem as it actually exists, and these are rarely the same thing.

Peter Block’s framework for contracting, developed in Flawless Consulting and directly relevant to facilitation practice, offers a more precise account of what the mutual commitment conversation needs to achieve. Block distinguishes between wants, the visible outcomes a client is asking for, and needs, the underlying conditions and concerns that will determine whether those outcomes are achievable. He argues that both parties have wants and needs, and that a genuine contracting conversation surfaces both rather than focusing only on the client’s stated request. This is the conversation in which the facilitator says what they require in order to do the work well: access, candour, the willingness to have difficult conversations, the authority to adapt the design. When this is named honestly, it shifts the relationship from service provider and purchaser to genuine partnership.

The distinction between organics and mechanics is a useful frame for structuring this conversation. The organics are the relational and behavioural questions: how will we communicate, how will we give each other feedback, what does each of us need to do our best work, how will we handle the moments when things go differently from plan? The mechanics are the practical questions: what is the purpose, who are the stakeholders, what are the deliverables, what authority does the facilitator hold over the design? Both matter, and both need to be addressed. But the organics deserve to come first, because they create the quality of relationship within which the mechanical questions can be answered honestly rather than formally.

In my own practice, the most reliable indicator of whether a partnership has been well established is what happens the first time something goes wrong. If the facilitator and client can have an honest conversation about an unexpected development, adapt together and renew their shared commitment to the purpose, the partnership is real. If the first difficulty produces defensiveness, blame or a retreat into the letter of the original brief, the partnership was never fully established. The contracting conversation is not the partnership itself. It is the foundation on which the partnership is built.

Seven practices that help me clarify mutual commitment

  1. I begin with the relationship before the task. Before discussing design, timelines or logistics, I ask the client what prompted the work and what will make the engagement feel worthwhile for them. This signals that the partnership matters as much as the output, and it gives me information I cannot get from a brief.
  2. I make my own needs visible. I name what I require in order to do the work well: access to relevant context, the willingness to have honest conversations, the authority to adapt the design. Naming these is not a demand. It is an act of professional honesty that the client deserves.
  3. I turn assumptions into agreements. Every engagement begins with unspoken expectations on both sides. I surface these explicitly: what is the client counting on me for, and what can I count on them for? The conversation itself builds trust and creates a reference point for later decisions.
  4. I address the organics before the mechanics. I give time to the relational questions, how we will communicate, how we will give each other feedback, how we will handle difficulty, before moving into the practical scope and logistics. The quality of the mechanics conversation depends on the organics having been addressed first.
  5. I distinguish wants from needs in the contracting conversation. I help the client articulate not only the outcome they want but the conditions they believe are necessary for that outcome to be achievable. I do the same for my own side of the partnership.
  6. I write up what we have agreed and send it back. A brief summary of the mutual commitments, sent to the client after the contracting conversation, serves three purposes: it confirms shared understanding, it creates a reference document for when things shift, and it signals that I take the agreements seriously enough to record them.
  7. I revisit the commitments at key transition points. When circumstances change, when the scope shifts, when new stakeholders appear, I return to the original agreements and ask together whether they still hold. This prevents drift and turns change into an opportunity to renew commitment rather than work around it.

Reflections on developing consensus on tasks, deliverables, roles and responsibilities

One of the most consistent sources of disappointment in facilitation engagements is the gap between what the facilitator understood they were delivering and what the client understood they were receiving. This gap almost always traces back to a conversation that was too brief, too formal or too focused on logistics to establish genuine shared understanding of what the work was actually for.

Research on client-professional relationships in service contexts, including studies of consulting, coaching and facilitation engagements, consistently identifies expectation misalignment as the primary driver of client dissatisfaction regardless of the objective quality of the work delivered. The phenomenon was described precisely by Zeithaml, Parasuraman and Berry in their foundational service quality research, which identified the gap between client expectations and perceived service delivery as the central determinant of whether a service engagement is experienced as successful. The implications for facilitation are direct: a session that objectively produces high-quality outputs can still be experienced as a failure if it does not match the client’s expectations of what success would look like, and those expectations can only be understood through genuine dialogue before the work begins.

The practical challenge is that clients often find it difficult to articulate their expectations precisely, particularly for facilitation work where the process itself is less familiar than the outcomes. They may describe what they want in terms of a format, “we need a workshop”, rather than in terms of an outcome, “we need a decision that the whole team genuinely supports.” They may conflate the immediate output with the underlying purpose, asking for a report when what they actually need is a shift in organisational conversation. Part of the facilitator’s task in the contracting conversation is to help the client surface the real deliverable beneath the stated request, and to test that understanding explicitly so that both parties can describe it in the same terms.

Clarifying roles and responsibilities requires equal care. In facilitation engagements, the boundary between the facilitator’s role and the client’s role is not always obvious to clients, particularly those who have not worked with a professional facilitator before. Making this explicit matters not only for practical reasons but for relational ones: when the client understands that the facilitator holds the process and the client holds the content and the authority, the division of labour becomes a source of confidence rather than confusion. And when it is not established, the facilitator risks being drawn into content decisions that are not theirs to make, or the client risks stepping into the facilitation in ways that undermine the process.

Seven practices that help me develop consensus on tasks, deliverables, roles and responsibilities

  1. I help the client name the real deliverable beneath the stated request. I explore what the client needs people to understand, decide or commit to by the end of the work, and test whether the stated format will actually produce that. A workshop is not a deliverable. The shift it creates is.
  2. I ask the client to describe what success looks like in their own words. If two people in the room describe success differently, I know the conversation needs to continue. Success is only genuinely shared when both sides can tell the same story about it without prompting.
  3. I clarify what is in scope and what is not. Naming explicitly what the engagement does not include is as important as naming what it does. This prevents the scope from expanding in ways that neither party intended and that neither has resources to support.
  4. I make the process-content-authority boundary explicit. I explain clearly that my role is to hold the process through which the group reaches its own outcomes, not to provide content expertise or advocate for particular conclusions. This is best established early, before any design work begins.
  5. I confirm decision rights at every level of the work. Who can approve changes to the design? Who decides what goes into the final output? Who holds authority to act on the outcomes after the session? These questions, answered in advance, prevent the friction that arises when they are left implicit.
  6. I build checkpoints into the engagement design. Regular brief conversations between design and delivery give both parties a chance to confirm that the work is still headed toward the right destination and to adjust before the investment of delivery makes adjustment costly.
  7. I document the agreed scope and revisit it when things shift. The scope document is not a contract in a legalistic sense. It is a shared map that both parties have agreed to navigate by, and that provides a reference point when the territory turns out to be more complex than the map anticipated.

Reflections on demonstrating collaborative values and processes

The third strand of this competency is the one most vulnerable to remaining at the level of aspiration rather than practice. It is easy to describe collaboration as a value. It is considerably harder to demonstrate it consistently across all the small decisions and interactions that make up the reality of a facilitation engagement. And it is in those small decisions, not in the formal contracting conversation, that the actual character of the partnership is revealed.

Research on trust in professional relationships offers a useful framework here. David Maister, Charles Green and Robert Galford’s work on the trust equation, developed through research with professional service firms, identifies four components of trustworthiness: credibility (the belief that the professional knows their field), reliability (the belief that they will do what they say), intimacy (the belief that they will handle sensitive information with care) and self-orientation (the degree to which the professional appears to be working in their own interests rather than the client’s). Their research found that self-orientation has a disproportionate negative effect on trust, more than any deficiency in the other three components. A professional who is technically credible and behaviourally reliable but who consistently appears to prioritise their own interests, their preferred methods, their reputation, their ease, over the client’s needs, will consistently underperform the trust potential of the relationship.

For facilitation, this has direct implications. The facilitator who insists on a particular method because it is in their comfort zone, rather than because it serves the group, is demonstrating self-orientation even if the choice is unconscious. The facilitator who presents a finished design for approval rather than inviting the client into the design process is claiming credit and control that belong to the partnership. The facilitator who avoids raising a concern because the conversation feels risky is prioritising their own comfort over the client’s need for honest counsel. Each of these choices is individually minor. Cumulatively they define the character of the partnership.

Demonstrating collaborative values means making the invisible visible: being transparent about why design choices are made, inviting the client into decisions where their input would improve the outcome, acknowledging uncertainty when it exists rather than performing confidence, and sharing credit with generosity when things go well. It also means modelling the behaviours the facilitation process is designed to create. A facilitator who advocates for participatory dialogue in sessions but does not practise it in their client relationship is sending a message about what they actually believe.

The most durable partnerships I have built have been shaped by a small number of consistent behaviours: explaining my thinking before asking for a response, treating the client’s knowledge of their context as superior to my own, acknowledging when I have made an error in judgement, and asking regularly whether the way we are working together is serving the client as well as it could. None of these are techniques. They are expressions of a genuine belief that the partnership is more important than the performance of expertise.

Seven practices that help me demonstrate collaborative values and processes

  1. I share my reasoning, not only my conclusions. When I make a design recommendation, I explain why: what I understand about the group’s situation, what the method is designed to produce, and what I am uncertain about. This treats the client as a thinking partner rather than a decision point.
  2. I invite the client into the design rather than presenting finished plans. I share early thinking and ask what the client notices, what they would add or change, and where they sense the design does not yet fit their reality. Co-created designs are owned more fully.
  3. I acknowledge uncertainty rather than performing confidence. When I do not know how a group will respond to a particular design choice, or when the situation contains unknowns I cannot resolve in advance, I say so. This builds more durable trust than a confident account that later proves incomplete.
  4. I raise concerns early rather than managing around them. If I notice something in the client relationship or the commission that concerns me, I name it in the partnership conversation rather than accommodating it silently. An honest early concern is almost always less costly than a late discovery.
  5. I model in the partnership what I am trying to create in the facilitation. If the session is designed to create honest dialogue, I practise honest dialogue in my client conversations. If it is designed to surface different perspectives, I invite the client’s perspective genuinely rather than formally. The relationship is a rehearsal for the work.
  6. I share credit when things go well. When a session produces something valuable, I acknowledge the client’s contribution: their willingness to engage honestly, their courage in commissioning a process that required vulnerability, their skill in holding the outcomes in the organisation after the event. Partnership means shared ownership of success as well as of difficulty.
  7. I check in on the quality of the partnership itself. At natural transition points in the engagement, I ask directly: is the way we are working together serving you well? Is there anything about how I am showing up that you would want to change? This keeps the partnership a living thing rather than a settled fact.

The organics and mechanics of the partnership

A useful way of structuring the contracting conversation is through the distinction between organics and mechanics. The organics are the relational dimensions of the partnership: how we will communicate, how we will give each other feedback, what each of us needs in order to do our best work, how we will handle the moments when things do not go to plan. The mechanics are the practical dimensions: the purpose of the session, the scope of the work, the stakeholders involved, the deliverables, the timeline, the budget and the terms.

Both are necessary. But they need different kinds of attention and a different sequence. The organics deserve to come first, because they create the quality of relationship within which the mechanical questions can be answered honestly. A client who does not yet feel safe in the partnership will answer the mechanical questions formally rather than frankly. They will describe the situation as they want it to appear rather than as it actually is. And the design that results will be built on a partial and managed picture of the reality it needs to serve.

The organic questions worth exploring include: what does each party need in order to do their best work, what communication rhythm will serve the engagement, how will feedback be given and received, what behaviours or dynamics tend to get in the way and how will we address them when they appear, and how will we handle difficulty when it arises. The mechanical questions worth exploring include: what is the working purpose of the session, who are the key stakeholders and what are their interests, what specific outputs are required, who holds decision-making authority at each stage, what are the logistical requirements, what are the assumptions and risks, and what does a successful outcome look like in concrete terms.

Neither list needs to be worked through exhaustively in a single meeting. What matters is that both dimensions are addressed before the design work begins in earnest, and that the organic questions are not crowded out by the pressure to move quickly to practical planning.

The payoff

When working partnerships are genuinely developed, the facilitation that follows has access to something that no amount of design skill can substitute for: an honest picture of the situation the work is meant to serve. The facilitator knows what the real stakes are, who the key tensions are between, what the client needs from the outcome and what constraints will shape how the outputs can be used. The design can be built on that reality rather than on the version of it that would have appeared in an initial email brief.

Strong partnerships also create resilience. When the unexpected happens, as it almost always does in facilitation work of any complexity, a well-established partnership provides the foundation from which facilitator and client can adapt together rather than retreating into their separate interpretations of what the agreement requires. The willingness to have an honest conversation mid-stream depends entirely on the quality of the relationship that preceded it.

The lasting payoff is that a well-partnered facilitation builds something beyond the immediate outcome. The client learns what genuine collaborative process feels like from the inside, and that learning travels into how they work with their own teams and communities. The relationship itself becomes a model for the kind of working that the facilitation is designed to create. When this happens, the competency is not simply a precondition for effective facilitation. It is part of the facilitation itself.

Frequently asked questions about IAF Core Competency A1: Develop working partnerships

What does IAF Core Competency A1 actually involve?
A1 is about building a genuine working relationship with the client before, during and after a facilitation engagement. It involves clarifying what both parties want and need from the work, developing shared understanding of the tasks, deliverables, roles and responsibilities, and demonstrating collaborative values through the behaviours of the partnership itself. It is the first competency in the IAF framework because everything that follows depends on it.

Why does this competency come first in the IAF framework?
Because the quality of the facilitation is determined before the session begins. A facilitator who does not understand the real stakes, the key tensions, the constraints on how outputs will be used, or what the client genuinely needs from the process is designing from an incomplete picture. The working partnership is how that picture becomes complete and honest enough to design from.

What is the difference between the organics and the mechanics of a partnership?
The organics are the relational dimensions: how we communicate, how we give each other feedback, what each party needs to do their best work, how we will handle difficulty. The mechanics are the practical dimensions: purpose, scope, deliverables, stakeholders, logistics, budget and terms. Both are necessary. The organics deserve to come first because they create the quality of relationship within which the mechanical questions can be answered honestly rather than formally.

What happens if this stage is skipped or abbreviated?
The risks accumulate quietly. Misaligned expectations lead to frustration on both sides. Deliverables miss the mark because the real need was never fully articulated. Facilitators design for the situation as presented rather than as it actually is. When something goes wrong mid-engagement, there is no relational foundation from which to adapt. In the worst cases, participants experience the session as disconnected from what actually matters to the organisation, and trust in the process erodes before it can do its work.

How do I raise what I need from the client without seeming difficult?
Frame it as professional responsibility rather than personal preference. Naming what you need in order to do the work well is an act of honesty that the client deserves. A facilitator who accepts a commission without the access or conditions required to execute it well is not being helpful: they are setting the engagement up for a difficulty that will be more costly to address later. Most clients, when the need is named clearly and connected to the quality of the outcome, respond to it as a sign of professional seriousness rather than as a demand.

How do I distinguish the client’s real need from their stated request?
By asking what they need people to understand, decide or commit to by the end of the work, and testing whether the stated format will actually produce that. A request for a workshop is rarely the real deliverable: it is a proposed means to an end that may or may not be the right means. The conversation about the real need beneath the stated request is often the most valuable part of the contracting conversation, and it almost always produces a better design.

What does it mean to demonstrate collaborative values in practice?
It means making the invisible visible: being transparent about why design choices are made, sharing the reasoning behind recommendations, inviting the client into decisions where their input would improve the outcome, acknowledging uncertainty honestly and sharing credit generously when things go well. It also means modelling in the partnership the behaviours the facilitation is designed to create. A facilitator who advocates for honest dialogue in sessions but does not practise it in client conversations is not demonstrating what they believe.

How do I handle it when the client’s expectations shift significantly during the engagement?
Return to the original agreements. Acknowledge the shift, explore what has changed, and ask together whether the existing scope and design still serve the client’s actual needs. This treats the change as information rather than as a problem, and it gives both parties the opportunity to renew their commitment to a shared direction rather than each managing the change separately. Well-established partnerships can hold significant changes without fracturing because the trust was built before the difficulty arrived.

Does this competency apply when working with community or voluntary groups rather than corporate clients?
Yes, and often with greater importance. In community and voluntary settings, the people commissioning the work may have less experience with professional facilitation and more uncertainty about what to expect from the process. The power dynamics may also be more complex, with multiple stakeholders having different and sometimes conflicting relationships to the commissioning body. The trust and clarity that A1 builds matters at least as much in these contexts as in corporate ones, and the consequences of skipping it are often more visible.

What is the best resource for deepening understanding of this competency?
Peter Block’s Flawless Consulting is the most directly relevant text. Block’s framework for contracting, which distinguishes between wants and needs, and his account of the three stances available in a consulting relationship, are directly applicable to facilitation partnerships. His work on what he calls the politics of the client relationship, the dynamics of power, dependency and honesty that shape every professional engagement, provides the theoretical grounding that makes the practical tools of contracting feel purposeful rather than procedural.

What has helped you build working partnerships that hold when the unexpected happens?

How do you create enough space in the contracting conversation for the organics, when the pressure to move to logistics is often immediate?

What has a strong working partnership made possible that a weaker one would not have?

Thanks for reading!

Explore IAF Core Competency A: Create collaborative client relationships

This article is part of a three-part series on building strong client foundations.