Project Management

Project Site Design For Stakeholders (Part 1)

From the Eye on the Workforce Blog
Workforce management is a key part of project success, but project managers often find it difficult to get trustworthy information on what really works. From interpersonal interactions to big workforce issues we'll look the latest research and proven techniques to find the most effective solutions for your projects.

About this Blog


Recent Posts

Leading by Listening (Part 2)

Leading by Listening (Part 1)

Lockdown! Just Like That Everything Changes (Now You Lead)

Project Site Design for Stakeholders (Part 2)

Project Site Design For Stakeholders (Part 1)

Categories: Manage People

I pay attention to your comments, believe me. This post, in fact, was driven by comments to an article of mine on Daniel Moskowitz and Luis Branco requested more information on techniques I wrote about in Improve Stakeholder Relations by Adding a Social Component related to building a project web share site that will be effective for stakeholders. I got started on my response to the comments and it turned into almost two full posts.

The goal, according to the original article, is to have a project share site that not only works for your project team, but also attracts stakeholders and has useful and timely information they need to keep them doing their job in the project, however that is defined. 

These design ideas and communication enhancers are based on sites I have created and also from what I have seen done by others. Always keep your audience in mind. Stakeholders do a lot and your project is just a small part of their work life. They may have just minutes to understand what is happening in your project and be able to respond/participate properly.

What to Place Front & Center

Provide stakeholders with what they need immediately or with just a click. Give them basic context.

  • Put a title and summary at the top to clearly explain that the purpose of the site is more than to house project documents but is in part to meet stakeholder needs.
  • Next, place a brief "What's Happening Now" with text and links to related status files and deliverables. For example, if you are gathering requirements, state that and describe the work sessions and review meetings that are happening (with dates if a calendar is not part of the site) and link to the latest draft requirements document. Put a link to the email of someone who can answer questions and add people to meetings.
  • This is the spot to place the link to the discussion area and specifically the discussion connected to what is happening now. Some applications may allow you to display the last items in the discussion in kind of a snapshot on your project Home page.
  • Be diligent about keeping this section updated. It will be a key landing point for your "push" emails that send stakeholders to the site. More on these later.

To summarize, then, your "front and center" content should include

  • Current activity summary description
  • Link to files that are related to those current activities
  • Link to meetings, activities and team members that are related to those current activities
  • Links to discussions, showing recent posts if possible

Other Content & Where to Place It

The application you use to build your project site typically allows you to format your page with one or two "rails" on the sides for additional content, links, announcements, etc. that are not important or urgent enough to put "front and center". They can contain links to other areas of the site. You can also use the area below the "front and center" section for additional detail that is more static.

  • Links to document repositories for use by project team members who know the organization of the folders
  • Announcement bullets and link to archive of communications from the project.
  • Upcoming events and link to project calendar
  • It may also be useful to include an embedded presentation that summarizes project foundational information, especially when you have new stakeholders added later during the project. This will allow new people to catch up on the basics without involving you or your team in excessive rework.

Avoid These Design Mistakes

It's easy to become excited about what you can do, but a common problem is putting in too much content on the Home page that must be updated. Soon, for various reasons, you will have less time and desire to manage this page. If someone else is updating the page, perhaps there is less of a problem.

Look critically at what you create to see that you have not simply left the design to "default" or "common" without thinking about stakeholders.

  • Unnecessary navigation - Stakeholders do not want to navigate through folder layers that make sense only to the person who organized them. Keep direct links to the latest summary updates, statuses, files, etc. front and center.
  • Lack of background - Stakeholders, especially those who get involved later in the project, need a quick briefing on your project. Make this easily available, but don't let it take up the whole Home page which is commonly seen. Make it available by a link, even if it is a presentation.

In my next post, I will describe more about applications that are used and using "push" and "pull" emails.

Posted on: January 12, 2020 06:18 PM | Permalink

Comments (6)

Please login or join to subscribe to this item
Dear Joe
Interesting perspective on the theme: "Project Site Design For Stakeholders (Part 1)"
Thanks for sharing

It sounds like a great idea for me to create one site per project.

When the company has multiple projects does the idea prevail?

The project site is itself a project.

You need people with web design skills, copywriters for the home site, and people who update information on a permanent basis.

In addition, there are other extra costs: web hosting

Thanks, Joe. Important topic. Often overlooked.

Good idea to also elicit from the stakeholders what it is they want to see. Even worth having the conversation on how they would like to see it. Information should be displayed in a format that provides a quick at-a-glance summation, with an ability to drill in for additional context. Show me what I need and want to see in a way that I can understand it.

Centralized information with the tools available at our disposal should be a basic component; SharePoint, Confluence, Jira, etc.

Probably the most difficult is to get stakeholders to start using it, trust it, rely on it. So definitely an aspect of educating stakeholders as well.

Organizational culture dependency as well.

Hi Mr.Joe

Microsoft Teams provides/creates a wiki sharepoint per team, i.e project. It keeps updating the home page "automatically".

Good feedback, Joe. I'm also curious about some of the practices used. For example, our web site team chooses to stage each version of the status update as a different file. That means they have to touch the main screen, so the link will pick up the correct version.

Please Login/Register to leave a comment.


"Man, if you gotta ask, you'll never know."

- Louis Armstrong...when asked what Jazz is.