Satisfaction is a relationship, not a score
A shared services team can meet every target and still have unhappy customers. Business units may feel unheard, distant from decisions, or unsure who to turn to. The reverse also happens: a team that is slightly slower than planned can keep goodwill because customers feel informed and involved. Satisfaction depends on performance, but also on how the relationship is managed.
The three main mechanisms are feedback loops, governance forums and escalation paths. Each has typical benefits and typical ways of going wrong.
Feedback loops
A feedback loop means asking customers what they think, doing something with the answers, and telling them what was done. The last two steps are the ones that often get skipped. Customers who give feedback and see nothing happen soon stop giving it.
Common sources of feedback
- Short surveys after a request is completed. A couple of questions asked at the moment of service are more likely to be answered than a long annual survey. They capture the experience while it is fresh.
- Periodic relationship surveys. Broader questions, asked occasionally, about whether the service is understood, valued and improving.
- Conversations. Regular, informal check-ins between the service team and key contacts often reveal things no survey would. Account-style contacts for each business unit can make this routine.
- Complaints and compliments. Both are data. Recording them in one place helps show patterns.
- Operational signals. Repeat requests, reopened tickets and workarounds suggest problems that customers may not mention.
Cautions
- Too many surveys cause fatigue and falling response rates.
- Small response samples can mislead. A handful of angry replies is not necessarily representative, nor is a handful of positive ones.
- Satisfaction scores alone say little about causes. Comments and follow-up conversations explain the number.
- Asking for feedback you cannot act on creates frustration. Be clear about what can and cannot change.
Closing the loop. A brief regular note, such as “you said X, we did Y,” goes a long way. If something cannot be changed, say why. Customers usually respond better to an honest explanation than to silence.
Governance forums
A governance forum is a recurring meeting where representatives of the business units and the service team review performance, discuss priorities and settle disagreements. It gives customers a formal voice and gives the service team a way to explain constraints.
Related ideas about how such bodies work, including steering committee purpose, membership and agendas, apply here. A few points are specific to shared services:
- Membership. Include people with enough authority to decide, and representatives of the main customer groups. A forum made up only of junior contacts cannot settle priorities, and one made up only of senior people may lose touch with day-to-day problems.
- Agenda. A simple standing agenda works well: performance against agreed targets, upcoming changes, open issues, customer requests for new or altered services, and decisions needed.
- Frequency. Often quarterly for strategic matters and more often for operational ones, though the right rhythm depends on the organization.
- Decisions and actions. Record them and follow up. A forum without visible outcomes becomes a talking shop.
- Fairness among customers. Larger units may dominate. A chair who deliberately invites quieter members to speak can help.
Cautions. Meetings multiply easily. If a forum has no clear purpose it should be merged or dropped. Also watch for forums that only receive reports and never make choices, as these tend to lose attendance.
Escalation paths
An escalation path tells customers what to do when normal routes fail. Without one, frustrated people go around the team, complain to senior managers, or give up and arrange their own solution.
A workable path usually has
- A first point of contact for everyday requests.
- A named role to raise concerns if the first contact does not resolve the issue within an agreed time.
- A senior contact for matters that remain unresolved or affect multiple units.
- A route to the governance forum for repeated or systemic problems.
Refer to roles rather than individual names so the path survives staff changes, and publish it where customers will find it, for example in the service agreement or the internal service catalog.
Cautions. If escalation is too easy, urgent matters get lost among minor ones. If it is too hard, problems fester. Escalations should also be tracked, because a rise in escalations on one topic points to a weakness upstream. Treat escalation as information for improvement, not as an attack on the team.
Habits that support the mechanisms
Beyond the structures, everyday behavior matters:
- Explain, do not just refuse. When a request cannot be met, say why and offer alternatives.
- Communicate changes early. Planned outages, process changes and staffing shifts are better announced in advance.
- Keep customers informed on progress, especially for longer requests.
- Share results openly, including shortfalls. Customers tend to be more forgiving of problems that are acknowledged.
- Involve customers in design. Inviting them to test changes before launch builds ownership and often catches issues early.
Balancing customer wishes with the whole organization
Listening does not mean agreeing with every request. A shared team serves several units with competing needs, and some wishes conflict with each other or with the standards that make the model efficient. When local requests clash with central standards, a defined route for exceptions and ways to balance central control with local input help. The aim is that customers feel heard and understand the reasoning, even when the answer is no.
Reviewing whether it is working
Signs that the approach is working include rising response to feedback requests, fewer surprise escalations, fewer workarounds, and forums that make decisions. Signs of trouble include falling attendance, repeated complaints about the same issue, and business units quietly building their own capability. Where the signs are poor, the sensible response is usually to ask customers directly what is missing, rather than to assume the process just needs more reporting. Outcomes will vary, and satisfaction is best treated as something to keep working on rather than a state that is reached once.