Getting Stakeholders on Board

Every web project today is a team effort. The days when one person could quietly build an entire site from content to code are long gone. Modern websites demand specialists working together, and they require approval from more people than ever before because the web has become central to how organizations operate. That means succeeding as a web professional now depends as much on working well with others as it does on design or engineering skill.

The frustration this causes is real, but it helps to recognize what stakeholders actually contribute. A website's success depends on far more than design, code, or copy. It has to fit into broader business operations — from the sales funnel to market positioning — areas where most web professionals have limited knowledge and skill. Stakeholders bring that perspective, and without their buy-in and approval, no amount of technical excellence will save a project.

Dismissing stakeholders as ignorant or mocking their requests only makes approval harder to obtain. Building an acrimonious relationship with the people whose support you need is a losing strategy. What is needed instead is genuine appreciation for what they bring to the table.

Why Arguments Don't Work

Here is an uncomfortable reality: you will never win an argument with a stakeholder in a way that benefits the project. This has nothing to do with whether you are right. Facts rarely settle these disputes because they are not really about facts — they are about people and feelings.

If you argue with a stakeholder, the best outcome is that they grudgingly back down and then look for chances to undermine you later. The worst outcome is that they pull rank and refuse to compromise. Few managers enjoy having their authority challenged, and being seen as "difficult" will follow you even if you win the occasional battle.

Confrontation also has a public shaming problem. Nobody likes being proved wrong, especially in a group setting. Shoving facts in someone's face to demonstrate you were right and they were wrong only deepens the wound. And confrontation is binary — it forces a winner and a loser, leaving no room for compromise or for everyone to walk away satisfied.

A Softer Approach

A more effective tactic is to respond to disagreement by acknowledging the stakeholder may be right. Then ask questions about any concerns you have, but with genuine curiosity about their position rather than a hidden agenda.

Instead of saying "that won't work because it will be inaccessible," try "that could work, but what do you think we should do about the accessibility issues?" Often, stakeholders talk themselves out of their own idea while answering such questions. If they do not, suggest testing the position they proposed — framed not as an attempt to prove them wrong, but as a sanity check to ensure nothing is being missed.

If the test does prove them wrong, express surprise. Making someone feel stupid will only lead them to argue with the test results and dig their heels in. The key is to help people save face when their opinion turns out to be incorrect.

The best way to help someone save face is to preempt issues before they raise them. If you can convincingly address a concern before a stakeholder voices it, they can stay quiet and never attach themselves to the position. For example, if you know a client will want their logo bigger, explain at the start of your presentation why you chose not to make it bigger. If your reasoning is sound, the client will not raise the issue at all and will never have to back down.

Empathy as a Persuasion Tool

Another hard truth: nobody cares about your work as much as you do. Developers care about code; UX designers care about users. But a marketing manager cares about their campaigns and a finance director cares about budgets. That does not make them bad people — they have their own areas of responsibility. How much do you care about legal or accounting?

This means phrasing requests in terms of your own discipline will likely fall on deaf ears. You have to frame what you want so it resonates with the specific stakeholder you are addressing. Want to run more usability testing? Do not talk about improving user experience. Instead, explain to a marketing manager how better usability encourages word-of-mouth recommendations. Tell a finance director that testing avoids waste and prevents building the wrong thing. Explain to legal that it helps meet accessibility obligations.

Personal style matters too. Analytical thinkers are swayed by numbers and facts, so make use of the unprecedented amounts of data digital provides. Emotional thinkers respond to stories and visuals, so show them a small prototype or footage of users struggling with the current experience.

Meeting People One at a Time

This tailored approach only works when you can speak to people individually. In a group meeting, you cannot customize your message for each attendee, and discussions quickly slip out of your control. Meet with each participant beforehand and present your case. By the time the group meeting happens, they are already on board and the session becomes a formality.

Not all stakeholders carry equal weight, however. Winning over one key decision-maker can sometimes be enough. But ignore the others at your peril — those you overlook can come back to cause problems later.

Stakeholder Management: A Communication Playbook

Projects fail not because of technical complexity but because of human dynamics. When many stakeholders are involved, ignoring those with less authority is tempting — especially if executive support is already secured. That approach backfires. Ignored stakeholders grow resentful and ultimately create more friction than engaging with them from the start would have caused.

The goal, then, is not merely to build a service but to sell it internally. A one-to-one persuasion strategy is insufficient when a broader audience requires buy-in. Four techniques form the backbone of a successful multi-stakeholder communication strategy:

Keep Stakeholders Regularly Informed

Silence breeds suspicion. People who feel left in the dark become anxious about the project's status and often interfere out of a desire to regain control. Conversely, being kept in the loop makes stakeholders feel valued and reduces the urge to meddle.

Regular updates also signal progress. Reassure stakeholders with consistent email communication, occasional video walkthroughs, and scheduled calls to address questions. If leadership hears from you on a cadence, they won’t assume the worst when things get difficult.

Excite Stakeholders By Inspiring Them

Momentum is the antidote to political gridlock. To generate it, you must make stakeholders want what you’re building.

Show them the end state: create a prototype or map the future customer experience. If IT claims a key interface is impossible on the current tech stack, don't capitulate. Build the prototype, record users reacting positively to it, and present the clip to senior management. Once leadership asks why they can’t have the thing they just saw, the pressure shifts from you to IT to deliver.

Take The Time To Educate

Most stakeholders don’t understand your field — and it’s not their job to. If they fail to grasp your vision, that is your failure to communicate, not theirs.

Take responsibility for their education. Circulate best-practice articles that shape your approach, explain the rationale behind key decisions, and offer sessions where colleagues can learn hands-on. Ideas include:

  • Lunchtime presentations
  • Drop-in clinics
  • Email newsletters
  • An internal conference session

People learn best by doing. The more you let stakeholders experience the work, the more they will understand what makes it effective.

Always Involve Stakeholders

The most reliable way to win allies is to let them help create. Involvement educates them on what works and what doesn’t while granting them a sense of ownership. People who contribute are more likely to defend the outcome to others.

Invite them into activities like design sprints or prototyping workshops. Even a survey or stakeholder interview is sufficient to open the door.

Inclusion makes sign-off less painful and yields valuable context about the broader business. You cannot change your stakeholders, but you can adjust your communication patterns and your definition of the role you play.

The lone-genius narrative is destructive. A "rockstar" is too arrogant, a "ninja" too isolated. Delivering successful digital services is a team sport — one your stakeholders are on.