A good website project team needs a sponsor, a day-to-day lead, a content owner and the right advisers. It also needs one named owner for each key decision. The same person can hold more than one role in a small team.
The goal is not to put every team member in every meeting. The goal is to bring the right people in at the right time.
Keep the core team small
A large group can give useful input. But it should not run the project as one big group.
When everyone can approve everything, simple choices can take weeks. Feedback may clash. No one knows whose view wins. The agency may spend time joining comments instead of solving the real problem.
A website project can have many voices, but each decision needs one owner.
Use a small core team for weekly work. Bring other people in for facts, checks and key reviews.
The six roles to cover
1. Project sponsor
The sponsor is a senior leader who owns the reason for the project. They protect the budget, remove roadblocks and make major calls about scope.
The sponsor does not need to join every task. They do need to be present when a choice affects cost, timing or the main goal. If approval is still being sought, our guide to building a business case for a website redesign can help the sponsor frame the decision.
2. Day-to-day project lead
This person is the main link between your team and the agency. They book reviews, gather input, track actions and make routine calls.
Choose someone with enough time and trust to lead. A job title matters less than access to the right people and the power to keep work moving.
3. Content owner
Content is often the largest task on a website project. The content owner plans what must be kept, changed, written or removed. They also find the people who can check each topic.
This role needs real time in the plan. It should not be added to someone's week with no space to do the work.
4. Technical owner
The technical owner checks needs such as forms, data, login tools, hosting, security and links to other systems. They may work in IT or with an outside provider.
Bring them in early. A late technical rule can change the design, platform, cost or launch plan.
5. Risk and access advisers
Some sites need advice on privacy, legal rules, brand, access, records or child safety. These people do not need to design the site. They need clear points where they can check the work that relates to their role.
Ask them what must be true, what proof they need and when they need to review it.
6. Subject experts
Subject experts know the facts about a service, program, campus, team or process. Use them to check facts and find missing needs.
Do not ask each expert to shape the whole site. Ask a clear question about the part they know best.
Name the decision owner
Roles alone are not enough. Write down who decides each part of the project.
- Goals and budget: project sponsor.
- Daily priorities: project lead.
- Content facts: content owner with subject experts.
- Brand and design: one named client approver, guided by user needs and the agreed brief.
- Technical rules: technical owner with the agency.
- Launch approval: sponsor and the named risk owners.
This is not about shutting people out. It is about showing how their input will be used.
Ask these questions before work starts
- What result must this website create?
- Who can make a final call when views differ?
- Who will supply and approve content?
- Which people must check privacy, access, legal or technical needs?
- How much time can each person give each week?
- Who will own the site after launch?
Put the answers in the project plan. Review them if a key person leaves or the scope changes.
Avoid the two common extremes
The first extreme is a project run by one busy person with no senior support. They may know what needs to happen but cannot approve the budget, get content or settle a hard choice.
The second is a project run by a large committee. It may include every view but have no clear owner.
The better model sits between them: a small core team, clear decision rights and planned input from others.
Plan for the team after launch
The launch team and the long-term website team may not be the same. Before launch, decide who will publish content, check forms, review results and keep old pages from building up.
Clear ownership is part of good website governance. It helps the site stay useful after the project ends.
What should the agency own?
A good agency should guide the process, test ideas, make the work clear and raise risks early. It should not ask the client to design the answer.
Your team brings the goals, facts, limits and final decisions. The agency turns that input into a sound plan, design and build. You can see how that comes together in our website case studies.
If you are planning a new site and need help setting the team, scope and decision path, talk to IGNITE. We can help you start with the right people and a clear plan.