How to Make a Shared Website Work for Different Departments

November 17, 2026

How to Make a Shared Website Work for Different Departments
Summer Swigart

Posted by

Summer Swigart

Executive Brief

Summary

You invest in a shared website so your departments can benefit from the same technology, reduce duplicated work, and give your audience a dependable experience. But sharing a platform doesn’t mean every department needs identical pages or approval processes. You need to decide which requirements protect the whole organization, which choices departments can make themselves, and when a specialized need deserves additional support. Making those boundaries clear helps you get more value from your platform while giving the people closest to each audience room to do their work well.

Questions Answered in This Article

How do I manage a website with multiple departments?
Give each department clear responsibility for its content and define which decisions it can make independently. Keep shared requirements for things such as accessibility, security, and authoritative information, and establish a review process for changes that affect other departments or the platform itself.
What should be standardized across multiple websites?
Start with the requirements that help you protect your audience and maintain the platform reliably. These may include access controls, reusable components, common data definitions, and the way you maintain important information. Allow variation where different audiences need different content or ways to complete a task.
How can I let departments update content without approving every change?
Set permissions and review requirements according to the consequences of a change. You can let a trained editor update routine departmental information while requiring the appropriate owner to approve changes to organization-wide policies or eligibility requirements. Make those boundaries visible so your editors know when they can proceed.
When should I customize a shared website platform?
Consider customization when you have evidence that an important audience need cannot be met through your existing capabilities or configuration. Before approving it, compare the benefit with the ongoing support it will require and check whether other departments share the same need.

Start With the Request That Doesn’t Fit

You’ve brought several departments onto a shared website. You have common templates, reusable components, and a publishing process that should make the site easier to manage. Then a department asks for something different.

Imagine you’re managing a university website, and one school wants a different way to present its programs. Your first concern may be what happens if every school asks for its own approach. You’ve invested in a shared platform partly to avoid maintaining a collection of unrelated sites.

But the school may have a good reason. Someone comparing short professional courses needs to understand scheduling, employer sponsorship, and how the course fits around work. Someone considering a research degree needs information about supervisors, funding, and research opportunities. The same page structure may serve one person well and leave the other searching.

You have a decision to make about what the website should accommodate. Before approving a separate solution or directing the school back to the existing template, look at the need behind the request. You may be able to support it within the platform, or you may discover a limitation worth addressing.

That conversation is where a shared website starts becoming useful across departments. You can preserve the benefits of working together while recognizing that your audience doesn’t always need the same experience.

Know What Each Standard Is Doing for You

When you require a common approach, be able to explain what it accomplishes. You might be protecting the accuracy of important information, helping someone move between departments, or keeping your team from maintaining several versions of the same feature.

Consider application deadlines. If each school presents them differently or copies them into several places, a prospective student may find conflicting information. A common structure and a clearly maintained source can help you give that person a dependable answer.

Now consider a requirement that every program page have the same number of sections. That may make the pages look orderly during a presentation, but it could force an editor to combine unrelated information or fill a section that has little purpose. You need a stronger reason to preserve that requirement than the fact that it already exists.

Ask what would become harder, less reliable, or more expensive if a department handled something differently. Also ask who would experience the consequence. A local choice may affect a visitor comparing programs across schools, or it may create maintenance work for the team supporting the whole website.

Those answers give you a basis for deciding which standards deserve to stay firm. They can also reveal where you have been enforcing a preference that no longer earns the effort it requires.

Share the Capability and Allow Useful Choices

You can often support different needs without building separate systems. A shared set of components might let one department emphasize course schedules while another highlights faculty research, with both using the same underlying publishing tools.

Think about your decisions in three groups. First, you have requirements that apply across the website, such as access controls and accessibility expectations. You then have supported choices, including approved page components or different ways to organize a program’s information. Finally, you have decisions a department can make within those boundaries, such as which examples to feature or when to publish a story.

The point of making those distinctions is to give an editor a usable amount of freedom. If every choice requires a request to the central team, your platform may offer flexibility that nobody can actually use.

Return to the professional courses example. You might already have components for schedules, costs, and application steps. Giving the school a suitable combination of those components could resolve its need without creating a custom template. If the information requires a capability you don’t have, you can evaluate that gap specifically.

Be careful about offering so many options that publishing becomes a design exercise every time. A few well-supported patterns can give a department meaningful choices while keeping the experience understandable for the person building the page and the person reading it.


edestrian crossing warning sign against a clear blue sky, illustrating how website design and content should be guided by the audience’s specific tasks, needs, and navigation goals.

Let the Audience’s Task Guide the Difference

A department’s request deserves attention, but its preferred solution is only a starting point. Ask what someone needs to understand or accomplish and where the existing experience gets in the way.

Suppose a school asks for a separate microsite because its programs feel buried. You may discover that prospective students can’t filter programs by schedule, or that the main navigation assumes they already know which school offers a course. A separate site might address part of that difficulty while making comparison across the university harder.

Follow the task before choosing the solution. Ask the department to show you how someone currently finds a relevant program, checks whether it fits, and takes the next step. Look for the specific moment when the shared experience stops helping.

This also gives you a fair way to assess requests from different departments. You can compare the importance of the problem and the evidence behind it, rather than giving the most flexibility to whoever makes the strongest internal case. When a proposed difference helps someone complete a meaningful task, you have a reason to investigate it further.

Give Departments Authority They Can Use

Your website can support departmental needs technically and still make ordinary work unnecessarily difficult. If an editor must wait for central approval to correct a biography or update an event location, you may have made responsibility easier to assign than to fulfill.

Match the review to the consequence of the change. A trained editor could update routine departmental information, while a change to an application requirement goes to the person authorized to confirm it. Editing a shared component would need a different conversation because it could affect pages across the website.

Be explicit about where one kind of decision becomes another. An editor should know whether changing a date is a routine correction or an update to an official deadline maintained elsewhere. That distinction is easier to follow when you identify the authoritative source and name the person responsible for it.

Permissions can support these decisions, but permissions alone won’t explain them. Give your editors practical examples of what they can publish, what needs review, and where to take an unfamiliar situation. You can then reserve central attention for changes that carry wider consequences while allowing departments to keep their content current.

Use Exceptions to Learn What Your Platform Is Missing

When the same request keeps returning, take a closer look at why it doesn’t fit. You may have a specialized need, but you may also have several departments struggling with the same limitation in different ways.

One school might request a spreadsheet download for comparing programs. Another might create a separate page listing schedules. Both could be trying to help a prospective student compare options the shared website presents individually. Seeing that connection gives you a different investment to consider.

In The Workarounds Your Team Invents Can Show You What to Improve Next, I explored how an unofficial process can reveal something your system doesn’t support. You can bring that same curiosity to a department’s request for an exception. Ask what it has already tried and what becomes difficult if the alternative is taken away.

You don’t need to turn every exception into a shared feature. Some requests can be handled through configuration or clearer guidance, while others may serve a genuinely narrow need. The useful question is how widely the underlying problem occurs, not how many departments have requested the same feature by name.

If you find a common need, involve more than the original requester in evaluating a response. You’ll have a better chance of building something broadly useful without losing the insight that brought the problem to your attention.

Make the Ongoing Responsibility Part of the Decision

A specialized capability can be a sensible investment. Before you approve it, make sure you understand what will be required after it launches.

Someone will need to maintain the content, test the capability when the platform changes, and respond if it stops working. A department may be prepared to fund the initial build without realizing that the central team will carry those responsibilities for years. Put that work into the conversation while you still have choices.

Compare the available approaches. You might improve a shared capability, support a departmental configuration, or build a specialized solution with a named owner and an agreed support arrangement. Look at the value each approach creates alongside the effort needed to keep it useful.

Consider what happens if the original sponsor leaves or the department’s priorities change. The capability should have enough documentation and organizational ownership to remain manageable. Otherwise, a reasonable exception can become something nobody feels able to change or retire.

In How a Focused Product Roadmap Accelerates Delivery for Every Department, I discussed how to decide which improvements deserve your team’s attention first. Knowing whether a request belongs in the shared platform or serves a specialized need helps you make that comparison. You can describe who benefits, what support it requires, and how it fits with work already underway.

Make It Easier to Work Within the Shared Approach

If you want departments to use the shared platform, the supported route needs to work well enough for them to rely on it. A standard becomes harder to sustain when following it means waiting weeks for a routine page or struggling with a component that doesn’t support the content.

Pay attention to what you ask an editor to do. Can they find an appropriate page pattern, understand how to use it, and publish within their authority? When they need help, do they know where to go and what response to expect?

Those practical conditions affect whether your governance decisions hold up. A department that can accomplish its work within the shared approach has less reason to commission a separate tool or maintain a parallel process.

You can learn a great deal by watching someone publish a real piece of content. Notice where they need another person’s intervention, where they copy information from elsewhere, and where they make a choice the available guidance doesn’t explain. That gives you specific ways to improve the platform without assuming the department needs more training or more restrictions.

The central team has a responsibility here too. If you reserve a decision for central review, make sure you can provide that review within a workable time. Otherwise, you have created a dependency without providing the capacity to support it.

Revisit the Boundaries as You Learn

The right arrangement today may need adjustment as your website and organization change. A feature built for one school may become useful to several others. A review requirement introduced during launch may no longer be necessary once experienced editors have reliable tools and clear guidance.

Revisit the decision when you see evidence that its purpose or consequences have changed. Repeated exceptions, duplicate capabilities, and routine requests waiting for approval can all give you a reason to investigate. You don’t have to reopen the entire governance model to improve one boundary.

Look at outcomes when you evaluate a change. You might examine whether routine updates happen sooner, whether important information remains accurate, and whether your central team spends less time resolving the same questions. Include the departmental editor’s experience as well as the work required to support the platform.

When you change the arrangement, explain what has changed and why. If a department can now publish independently within a defined area, make that authority clear. If a local capability becomes shared, agree on who will maintain it and how future requests will be considered.

You can begin with one recurring request that keeps returning for discussion. Work through the audience need, the purpose of the existing standard, and the responsibilities each possible response would create. Then make a decision you can apply consistently to similar situations.

Your shared website should become more useful as you learn how different departments serve their audiences. Clear boundaries let you preserve the capabilities everyone depends on while making room for differences that earn their place. That gives you a platform you can improve together without making every new need a negotiation about how the whole organization should work.