Forum Discussion

Mike Jansen's avatar
Mike Jansen
Iron Contributor
Nov 23, 2016

SharePoint Online Intranet - A new approach? What are your thoughts?

In the old days (=now) most intranets are hierarchy based. The question is, is this still the way to go?


Recently there have been a lot of changes is the O365/SharePoint (online) area:


- Modern teamsites (which are site-collections)


- Modern pages


- The "new" SharePoint landing page (tile) https://blabla.sharepoint.com/_layouts/15/sharepoint.aspx


- Groups


- Teams

 

 

Some thoughts:


- As an employee, why would I want to see all the intranet pages of the company? I know I only see the ones I am authorised for but most of the time it's a lot.


- I need an Intranet landingpage with company news and some other "need to know" information


- I need an overview of all the sites (or collections) I'm interested in.


- Some more thoughts.

 

 

Possible solution:


- https://blabla.sharepoint.com is the Intranet landing page


- The landing page wil be redirect to https://blabla.sharepoint.com/sites/intranet. This will be a modern site collection.

- ../sites/intranet will be a small intranet (just landing page and "need to know", like HR etc.)

- Departments get their own (Modern) site collections

- Everything comes together in the SharePoint landing page, https://blabla.sharepoint.com/_layouts/15/sharepoint.aspx.

- So my SharePoint landing page shows me everything I need in an attractive way.

 

 

Questions:


- What do you think of this approach?


- How can I customise the SharePoint landing page?


- Other thoughts


- Will this be a workable solution for a user or will it be confusing?

 

 

I've not figured it out for myself yet but I just want to share my thoughts.

 

 

 

 

 

 

21 Replies

  • You know where I stand on this (see the discussion I started about global navigation and lack thereof in Microsoft's roadmap).

     

    I think the reality is that you are going to get a lot of pushback.  People are used to having information fed to them and having specific ways of getting to things (global nav) and finding what's out there. 

     

    Here are the biggest challenges I see (and I've thought about this often) --

     

    • How do you tell people about new sites?  Will a news area suffice? 
    • What about sites that aren't new that people haven't look at?  Those won't be in the "news" area and might not show up on the SharePoint home page.
    • How do people look around and discover new sites and information?  With a global nav, you can build out a site structure which enables people to look at what else is out there (if you build it right).    How do you replicate this? 
    • Search is AWESOME when people NEED something and are actively looking.  But again, how do you enable people to look around, see what's new, what's cool, what might be useful that they don't know about?
    • Groups and Teamsites.......... be sure to think about how permissions play a role here.  Groups only give a member EDIT rights.  What about read only?  If every departments gets a teamsite, what do you with information shared between departments?  You can't just hand out edit permissions to everyone just because you want to show information.  I realize you can lock down files in Groups/Teamsites to some degree.  My point is, plan for sites that primarily team oriented and sites that are more built for showing files/folders for reference.

     

    I think with this type of structure (or lack thereof) the Intranet/portal team needs to have a plan in place to continual draw people to new and different "stuff" that's out there.  I don't see that as a negative but something to plan in.  With most "classic" intranets there is a news section but I think you need to do more for people to highlight what's happening and what is around the intranet.

     

    Some ideas --

    • Ads............. no joke.  Intranet "ads" or something similar that highlights different areas and places (since there's no global navigation
    • A plan to constantly update and highlight different areas and places, even if it's redundant from year to year (you're going to get new employees who didn't know about certain sections, or missed it the first time around).
    • A "did you know you could do this" type of section -- similar to ads or news... but possibly a different possible take on delivering the info above

     

    None of this is easy.......... the above are just things I have on my list and some challenges I see.  I've been mulling this all around for quite some time and my biggest concern is showing people what's out there if they don't know about it.

    • Antony Taylor's avatar
      Antony Taylor
      Iron Contributor

      as an MSP, internally we're always trying to push and use the latest thing because we need to understand how to then advise our clients.

       

      Whilst we're a relatively small Org internally We've developed a hybrid approach that so far is working well.

      • Central Promoted Team Site for surfacing News/Directions/Wiki. Great for a Central hub for directing people to the right resources
      • Larger Projects are handled by Team Sites / Project Online
      • Smaller Projects are handled by O365 Groups
      • Groups around other topics are O365 Groups
      • Obviously there are some historical team sites knocking about as well as we transition but they're easily surfaced with SharePoint.

      How do people navigate and access? (we'll focus on web based user rather than Outlook etc)

      • SharePoint Home to easily navigate to sites/groups they're part of
        • Eagerly awaiting the aggregated News web part here.
      • Our Promoted "Central Team Site" is also set as a Tile for the business Apps for central quick access to catch up on the latest that you're not already connected to.
        • I imagine we'll also add the Aggregated news Web part here if it's available so that we can have one Central place for News
      • Suggested Sites are great for highlighting sites/groups you may want to be part of based on colleague interactions.

      Once people are comfortable with this "one way to access things in Heirarchical way" I Introduce them to things like OneDrive where they can access the sites/groups they're part of but with a focus specifically on files.

       

      Because Teams are Private only at the moment we're yet to get any real traction with them currently.

    • Ivan54's avatar
      Ivan54
      Bronze Contributor

      Hi, 

       

      all valid bullet points. No real out of the box solution in sight at the moment.

      As for O365 Groups, I currently don't see a viable option to use O365 in a "one department to many sharing scenario" because of the lacking read only rights. Thats why I would use a subsite of the default root site collection for every department (easy for me with only a handful departments - quite hard for large corporations).

      • Clint Lechner's avatar
        Clint Lechner
        Iron Contributor

        Office 365 groups................... actually, you can have read only rights in the group now.

         

        -Create a modern team site but make it "public" (create it via the Sharepoint dashboard).... 

        -Go Into permissions for the teamsite (you need to wait a few minutes)

        -You will see "Owners" and 2 Groups for edit permissions.  One of those groups is "Everyone except External Users" which by default is set to edit.  You can change that to "Read"...

         

        This adds a couple new possibilities

        -Owners can do anything/edit/modify/delete and everyone else can ONLY read

        -Owners can do anything, public users can READ, and members can EDIT



  • Ivan54's avatar
    Ivan54
    Bronze Contributor

    I was debating all this myself internally and I assume Microsoft will make the following changes sometime next year:

    • Add a "news headlines" element to the SharePoint Waffle Landing Page that aggregates all news pages from all the sites that you have access to or are following
      • similiar to the News Tab in the iOS SharePoint App
    • Introduce the modern Publishing Pages features.
      • It'll be interesting to see how they enhance the current modern pages, since in theory (and pratically) you are already publishing (modern) pages and news

     

    We'll probably go this route:

    • reconfigure the current sharepoint root site collection to "modern", and find some appropriate name for it
      • add modern subsites for departments and branches that host content that was previously shared in a dedicated Intranet. Stuff that one departments offers to all users or specific locked down document library for a subset of users
        • separate subsites are needed in order for the SharePoint News features to show up as "from department XYZ". (Question: how do I prevent subsites from opening in another tab?)
      • push this default root site collection to all users somehow
      • Future Iteration: make the root site collection some how personalized instead of generic
    • O365 Groups (+Sites) for all other stuff (internal department stuff, projects, interest groups and so on ...)
    • Custom Site Collections for future larger projects/apps and publish those as Waffle Icons in the O365 Launcher.
  • MrCarrick's avatar
    MrCarrick
    Copper Contributor

    This is the direction I'm leaning toward too. I see this approach as the best way to leverage all the recent investments from MS.

     

    User lands on the designated Intranet Homepage (hopefully a Modern Publishing Site this time next year!) to get their quick glance at important and new organisational information. Where applicable, curated informational pages live here from the rest of the organisation.

     

    Once our user has decided "I need to get something done", they head for SharePoint Home from the app launcher. I really like the way this works out of the box, hopefully our user should see the site they need right there at the top of the page.

     

    My only customisation needs/wants for SharePoint Home, is to perhaps define which site sits at the top left, in position A1. Maybe have that first tile as the top promoted site, with frequent sitting to the right. I'd like to have that control as this space is a bit noisier than the feature sites list.

     

    Custom app tiles are great for the things traditionally added to a quick links or resources menu, we're adding to these all the time. Works especially well with the new personalisation options in the app launcher.

     

    The only thing i do beyond that, is to use the cutom clickable logo in the Office 365 suite bar as a link back to my designated intranet homepage. Gives users a nice anchor point to quickly dive back to the intranet from anywhere, when they need it.

  • Brent Ellis's avatar
    Brent Ellis
    Silver Contributor
    In general, I dont see any "flaws" in your approach if you have to build the solution right now. The only hangups I would have are (1) what is coming for modern publishing sites and (2) whats coming for converting existing site collections into modern

    I am not a fan of the "every site goes into one big bucket on the same level and users can fish out the sites they need". We've always relied on custom enterprise navigation to make the intranet make sense (which doesn't look to be an option anymore)

    I am generally planning to redo our intranet like this:

    Root Home Page (hopefully modernized publishing whatever that ends up looking like)
    - Each department/operating company has an informational site under the root where we will force layout and content
    - Key strategic informational sites will reside as subsites under the root level
    - Each department/operating company has a modern team site (collection) where they can build out what they want
    - Formal workgroups, organizational groups, and project teams will be O365 groups and have a dedicated SP Site (tied to the Group)
    - Document Management and Business App solutions will be dedicated SharePoint sites and site collections (kinda the 'old school' way of building SharePoint stuff)
    - We'll use SharePoint home for general search for Sites
    - We'll use custom webparts on the Intranet home page to focus on Site's I'm Following for quick access
    - We'll use a "Key Links Page" that is like a 1 page directory of corporate controlled/recommended content (we do this already but this might become our intranet home page since we are losing custom navigation...)
    - We'll use the "Custom App Icons" in the waffle menu for some key quick links to resources (no matter if you are in SP, Group, OWA, etc)
    • Charbel Matni's avatar
      Charbel Matni
      Copper Contributor
      Hi
      On the department/unit level, when you give the ability to create as many subsites as they need, wouldn't that impact the governance and site directory?
      Isn't better to implement a site provisioning form where they request a subsite and it gets routed to the department champion for example.
      The reason I'm asking is cz we are moving around 5000 sites to SP online and the challenging part is to build a site directory easy to navigate (logical or physical-haven't decided yet) and establish a governance with limited depth of 5 levels for example with metadata to display site info on the site level.

      Appreciate your thoughts!!
    • Mike Jansen's avatar
      Mike Jansen
      Iron Contributor

      Hi Brent Ellis,

      That "information" site might indeed be a good addition to my approach. I think I will make that a modern page, as I prefer that layout. But that might be a personal thing ;-)

Resources