Every GBS leader knows the situation. A country wants an exception to the global process; the process owner says no. Technology needs an answer before its next release; Finance wants to know who is paying. Two hours later, everyone has been heard, the deck has grown by six pages, and exception management has spawned a new working group. Nobody has made the call, but at least Copilot’s minutes are absolutely immaculate.
GBS has service in its name, which is amusing given how much of the model’s value—and the leader’s power– consists of deciding who gets to say no—and when. GBS’s value levers: standardization, service scope, platforms, locations, investment and exceptions all require decisions about money, timing, authority and priorities.
That is where a leader’s decision-making habits matter. One style can rescue a floundering model or conversely, predispose a team to constantly wait patiently for orders. Another can earn genuine team buy-in or hand the most negative person in the room an unearned veto. A data worshipper can expose an expensive operating fiction or demand yet one more analysis until the opposition lays down and play dead.
No style is inherently good or bad. But like most things in life, any action (or lack thereof) has implications for success. Let’s unpack the 10 decision-making styles GBS leaders most commonly demonstrate. Which one sounds like you?
1. The Autocrat
The autocratic GBS leader makes a big display of listening before ‘deciding’ but no one in the room is confused about who makes the call. They quickly cut through noise, making decisions visible and stopping endless debate, protecting the enterprise from stakeholder drift and endless second-guessing. In early-stage GBS build-outs or, major transformations, merger integrations or rescue missions, the autocrat can be exactly what the doctor ordered.
Plus? The style is directive, fast and clear and works when the GBS organization needs pace, discipline or critically, rescue. It can be particularly effective when the model is a mess and under fire: unclear accountability, weak service performance, no priorities excessive customization, local resistance, failed transitions, bloated governance, or a leadership team that has turned obtaining alignment into a lifestyle choice.
Downside? Dependence. If every critical decision sits only with one person, the GBS team never builds decision muscle. They cease critical thinking, knowing the leader will eventually impose a decision and silence useful dissent.
The GBS team quickly learns to present what the leader wants to hear, not what the leader actually needs to know. Over time, the organization looks beautifully aligned when it is actually compliant, cautious and under-empowered.
Best for: Autocracy works when the situation requires decisive intervention, the leader has sufficient facts, and decisions must be made quickly. It fails when it becomes the permanent GBS house style. GBS cannot scale if the leader is the only decision engine.
2. The Consultant
You know the consultative decision-making style—the leader seeks input before making the call. They ask for views, test assumptions, involving subject-matter experts and usually external voices, then land the answer. At times, this is most effective for a GBS model because it cuts across functions, geographies, technology, process, risk and people, requiring an ecumenical style. We all know that no single leader has sufficient command of the context to make the right decision on their own.
Plus? Usually a better-quality decision. Consultative leaders surface operational reality before decisions harden. They hear from the people who understand the work. They build enough involvement that implementation is less likely to be undermined by the classic ‘no one asked us’ refrain, which arrives immediately after 47 email invitations to provide input have been ignored.
Downside? Slippage. Consultation creates decision mush if the team cannot distinguish between input and authority. People start to believe that being ‘consulted’ means having a vote. When their views do not prevail, they feel ignored. The leader then spends more time explaining that consultation is not synonymous with the ability to consent than they would have spent making the original decision on their own, creating inclusive exhaustion.
Best for: Consultative decision-making works when the leader provides clarity upfront: “I want input, I will listen, and I will then decide.” But it fails when consultation is used as camouflage for indecision, or worse, when the leader asks everyone what they think because they are hoping the room will make a default decision.
3. The (kumbaya-singing) Camp Counselor
Camp counselor GBS leaders crave broad agreement before moving. Everyone is invited into the tent. Everyone is heard. The leader then tries to create a decision the whole group can support. When it works, this style builds ownership and reduces resistance. In its worst form, it becomes GBS group therapy with a steering committee calendar.
Plus? Buy-in. GBS consensual decision-making is useful in enterprises or cultures where trust is low, where the model is new, where functions are terrified of loss of control, or where the leader needs to build a team coalition before pushing harder and moving the next dial. It also works well when team members and stakeholders are mature, honest and capable of putting enterprise interest above functional preference.
Downside? Dilution. Consensus rewards those in the room who are most reluctant to change. The camp counselor softens the implication of a decision until no one objects, which usually means the outcomes don’t have a prayer of being delivered. In GBS, this is particularly dangerous because the model’s success requires stakeholders to surrender a degree of control. If everyone must be comfortable, standardization will become optional, scope will be negotiable, and every exception will be branded a ‘business imperative.’
Best for: Consensus works when the decision requires collective commitment from a group that shares a real enterprise agenda. It fails when alignment means no one is allowed to be unhappy. Sometimes the most grown-up sentence in the room is: “thank you, I understand your concern, and we are still moving forward.”
4. The Democrat
The GBS democrat allows the group to decide, often by majority view or collective preference. This usually works in situations where the decisions are bounded, where consequences are limited, and the team has the relevant expertise. For example, democracy is most useful when deciding internal working norms, prioritizing improvement ideas, choosing between comparable options, or giving teams ownership as to how they deliver an agreed outcome.
Plus? Engagement. People feel they are trusted. Teams develop ownership. The leader avoids micromanaging and signals that decision-making is not reserved for the most senior person in the room. Used appropriately, democratic decision-making helps develop future leaders because people learn to weigh options and live with the consequences, which is generally how we grow more proficient GBS professionals.
Downside? Not all GBS decisions can or should be democratized. The model is full of enterprise trade-offs that cannot be determined by group preference. The majority tends to choose what is comfortable, familiar or locally popular rather than what is right for the operating model and the enterprise it serves. Democratic decision-making can also frustrate high performers if the group repeatedly makes decisions that trickle down to the ‘safest’ path forward, calling it team ownership.
Best for: This style works when the decision is contained, the team has real expertise, and the leader is genuinely willing to accept the outcome. It fails when the leader pretends the decision is democratic but reserves the right to override anything they deem inconvenient or downright wrong.
5. The Data Worshipper
The GBS leader cum data worshipper pushes the organization to make decisions solely based on evidence: cost, volume, service levels, cycle time, risk, controls, adoption, demand, productivity, benchmarks and customer feedback. This style is especially critical because the model is bombarded with anecdotes and opinions masquerading as fact. One country is unhappy. One partner complained. One function says the process is unique. One executive says service levels have deteriorated, based largely on the memory of a single incident from 2019.
Plus? Discipline. Data-led leaders eliminate much of GBS mythology. They expose variation, cost, duplication and performance gaps. They show where the real problems are and where the noise is disproportionate. This is particularly useful when prioritizing automation, redesigning service models, challenging exceptions, defending investment or proving the value of outcomes. Data also has the rude habit of showing that some sacred cows are simply very expensive cows.
Downside? False certainty. Data is rarely complete, clean or neutral. It can be deployed ‘selectively.’ It can also become a way to delay making a decision; some leaders keep asking for more data because they do not want to annoy anyone. Others weaponize data to shut down debate, even when the human or political factors really matter.
Best for: A data-led decision-making works best when evidence is necessary to inform judgment. It fails when data is treated as a substitute for leadership.
6. The Principled Promulgator
The principled promulgator strives to make as many decisions as possible against a defined set of operating tenets. These might include standard before custom, global before local, digital before manual, self-service before assisted service, enterprise value before functional preference, and end-to-end ownership before handoff. This style is powerful because it gives the organization a repeatable way to decide without reopening the philosophy every time.
Plus? Consistency. The team always know what the leader values. Decisions become less personal and less negotiable; a principle-led leader can say no without sounding arbitrary (the answer is not ‘because I said so.’) They support their call ‘because we agreed this is the kind of organization we are building.’ This is useful because GBS leaders otherwise spend half their lives explaining why a global model design cannot be made up of everyone’s favorite local exception.
Downside? Rigidity. Principles can become dogma if the leader refuses to recognize legitimate exceptions. A local regulatory requirement is not the same as a local preference. A high-touch service may be justified for a genuinely high-value business need. The danger is that principle-led leaders can become so attached to the model that they stop seeing reality.
Best for: Principled decision-making is effective when GBS organizations needs coherence and repeatability. It fails when principles become slogans or when the leader applies them without judgment. The test of a good principle is whether it helps the organization choose wisely.
7. The Empowerer
The empowering GBS leader pushes decisions down. They define the outcome, set boundaries, and let their teams decide how to get there. This is particularly important in mature GBS organizations where the leader cannot and should not be involved in every operational decision. Service owners, process owners, platform leaders and regional leaders must have authority if they are going to be held accountable.
Plus? Scalability and speed. Empowered teams move faster. They develop confidence. They solve problems closer to the work. The leader is then freed to focus on strategy, stakeholders, investment and talent rather than adjudicating every service issue. This style is also essential for leadership development; people do not become good decision-makers by watching someone else decide while they take notes.
Downside? Inconsistency. If the leader empowers without clear guardrails, the GBS organization fragments. Different teams make different calls. Standards drift. Exceptions multiply. Stakeholders shop around for the answer they prefer. Empowerment without a framework becomes decentralization with nicer language and, usually, better PowerPoint.
Best for: When decision rights are clear, leaders are capable, and boundaries are explicit, the style works well. It fails when empowerment is used as a polite synonym for abdication of responsibility. ‘You decide’ is only useful if people understand the framework within which they are deciding; otherwise the leader has not empowered the team
8. The Political Broker
The political broker primarily manages GBS decisions through influence, coalition-building and careful sequencing. They know who matters, who will resist, who needs to be brought in early, who can block the decision, and who must feel they were heard. In some enterprises, this decision-making style is not optional; it is survival.
Plus? Realism. GBS has to deal with power structures, egos and functional kingdoms. A leader who ignores the context in which they operate will always be trumped by someone who knows where all the skeletons are buried . Political decision-making can help move difficult decisions through skeptical environments. It can be especially useful when GBS lacks a strong formal mandate or when the business is highly federated and everyone agrees in principle while defending every inch of terrain.
Downside? Opacity. If every decision is brokered behind the scenes, the GBS organization and the enterprise it serves never learns how decisions are actually made. The team and stakeholders become cynical, assuming that decisions were made before the meeting. And they are often correct; brokered decision-making depends heavily on the leader’s personal relationships. When the leader leaves, the decision system leaves with them.
Best for: The political broker style works well when the GBS leader uses political influence to unlock progress, not to avoid transparency. Successful leaders avoid making side deals, private understandings and diplomatic fog.
9. The Avoider
Avoidance may not look a decision-making style, but it is one. The avoider delays, softens, delegates vaguely or send back analysis for yet more analysis. They ask good questions but does not land the answer. They encourage yet more discussion. They suggest another review. They obsess about getting the timing right. They want more stakeholder input. The decision remains technically alive but practically dead.
Plus? Limited. Avoidance can occasionally be useful when the timing is genuinely wrong, the analysis are not complete, or a premature decision would create unnecessary damage. Not every delay is cowardice; some delays are grounded in judgment. The trick is knowing which is which, preferably before the organization has spent six months admiring the problem.
Downside? Enormous. Avoidant decision-making drains everyone’s energy. It is usually the leader’s default conflict strategy. Teams keep working around unresolved issues. Stakeholders fill the vacuum with their own usually contrary decisions. ‘Informal’ decisions become permanent by default. The organization becomes confused, then frustrated, then cynical. In GBS, avoidant leadership is particularly damaging because the model already sits at the intersection of competing agendas. If the GBS leader will not decide, someone else will, usually the stakeholder with the most to lose from change. And GBS’s trust capital erodes. People can live with a decision they do not love. But they have a much harder time operating inside a permanent holding pattern
10. Adaptive Adult
The adaptive adult in the room does not have one style, choosing the right style based on the situation, the stakes, the maturity of the team, the urgency, and the degree of enterprise impact. They may be autocratic in a crisis, consultative on service design, data-led on investment, principle-led on exceptions, empowering with mature service owners, and political when navigating enterprise resistance.
Plus? Adaptability. Adaptive leaders do not overuse their favorite muscle; they understand that different decisions require varying levels of involvement and authority. They are clear with their teams about which mode they are in. People can tolerate a directive decision when they understand why it is directive, the need to consult when those affected have a stronger voice. What is frustrating is pretending a decision is open when it has already been decided.
Downside? Adaptive leadership can look inconsistent if the leader does not explain the mode they are in. One week the leader asks for input, the next week they make the solo call. The team sees mood swings rather than judgment. Adaptive leaders therefore need to be explicit: this one is consultative; this one is mine to decide; this one sits with the service owner; this one goes to the executive sponsor because it crosses enterprise risk.
Best for: Adaptive decision-making works when the leader is transparent about decision rights. It fails when flexibility becomes unpredictability.
The practical test
A useful way to assess your decision style is to ask four questions.
First, where does the decision naturally sit? Some decisions belong with the enterprise, some with the GBS leader, some with process owners, some with service teams, and some with stakeholders. If everything comes to the leader, the model is too centralized. When nothing comes to the leader, the model may be too loose.
Second, how much input is useful before the decision starts to decay? GBS leaders need input, but input has a shelf life. At some point, additional consultation stops improving the answer and starts protecting people from the answer. This is usually the point where the meeting name changes, the deck gets longer, and no one gets braver.
Third, what is the cost of being wrong? High-risk decisions require more evidence and senior stakeholder ownership while low-risk decisions should not be treated like constitutional amendments. GBS organizations tend to over-govern small decisions and under-decide big ones, which is an impressive way to be both slow and risky at the same time.
Fourth, who has to live with the decision? The team implementing the decision needs enough involvement to make it real. But living with a decision does not always mean owning the decision.
The real leadership issue
The best GBS leaders are not simply decisive. Plenty of decisive people make terrible decisions quickly and then call the wreckage momentum. The best leaders are clear about how a decision will be made, who has authority, what input is needed, when debate ends, and how the decision will be enforced.
The weakest leaders are not always the ones who make bad calls. Sometimes they are the ones who never quite make calls at all. They allow decisions to remain permanently open because open decisions feel inclusive, flexible and safe. They are not–they are expensive. They create shadow authority, rework, stakeholder fatigue and leadership theatre.
GBS needs decision-making honesty. Sometimes the leader should decide. Sometimes the team should decide. Sometimes the enterprise should decide. Sometimes the data should settle the argument. Sometimes the principle should. Sometimes the group should be heard and then told, politely, that the answer is still no.
This is the essence of GBS leadership.