Office 365 is changing the rules for Intranets

-
Before Office 365 (O365), when we were asked to build an intranet, we built a SharePoint solution with an inviting home page and some sub sites that promotes team collaboration. Maybe we added in a few interactive features and "Ta-daaa", your intranet was done.

Now, its the game is different, and many of the players don't even realise this. 

An intranet that is using Office 365 is more than just a pre-defined set of pages that has a starting point and set navigation plan that should be used by all. Its use is now dictated by the users, and if done right, no 2 users will experience their Intranet in the same way. 

We all know that O365 has this new, beautiful SharePoint Communications sites, for example, this site can help promote Corporate-Level communication and is typically seen as an ideal Home Page to an intranet, but why force that as the Home Page to everyone? Everyone is different, with different objectives when using the Intranet, why not make the users chose a homepage that best suite their interest?

If they plan to use the intranet to access there web tools quickly, then they could use the O365 Home Page which provides quick access to all their Office tools.  Alternatively, they could use Delve, a O365 tool that provides great insight on what relevant people are doing. Maybe the SharePoint Site Selection page should is a preferred starting point, so they can easily view the sites of the projects that they are currently working on. The rule of having a central home page is gone, and we need to focus on an approach that is more user-centric.

This change in the Intranet rules does not apply to the home page alone. Why force everyone to use Team Sites to collaborate? The end users now have a great selection of tools available to them. Tools like Groups, Teams and Yammer are all available via O365 to promote collaboration through discussions but each tool appeals to different audiences (i.e. some users prefer to engage via email, others via chat) so the one size fits all approach is now the wrong way to handle this.  
Also, previously, if we wanted our Intranet to stream video content from a secure environment, we needed to invest in a dedicated Video Streaming Server, NOW with O365's video service, its easier that ever to load video content. meaning that users are now using their cell phone, record a quick video that promotes some news or corporate interest and quickly sharing it to all via the Intranet. 
Now, thanks to O365 and other cloud services, an intranet is more than just a website, just like a car is more than just an engine, the rules of this game is changing, its less rigid and more user-focused. People are only figuring this out now (if at all), so stop building intranets the way you did 5 years ago, and figure out how the new playing field is removing the restrictions we had before and change your approach before its too late. 

Comments

Post a Comment

Popular posts from this blog

Why there is a shortage of SharePoint experts

-
Image
Microsoft has been very successful to promoting their SharePoint product, even though SharePoint has been around for a while, there 2007 and now 2010 version is something every organisation wants. With Microsoft practically giving away SharePoint licenses to organisations via EA agreements – we are reaching a very unique and rather unexpected situation where the demand for SharePoint developers is surpassing the demand for Web developers. This shift in demand are forcing IT departments and Web Development companies to reduce the size of the web development teams and increase the size of their SharePoint team, in other words, take staff originally hired for web development and get them into SharePoint development. This is currently the "normal" approach in getting SharePoint experts, many IT Recruitment companies still don’t understand this shift in demand, and are not yet focusing in the SharePoint space, some recruiting companies haven’t even heard of SharePoint and...
Read more

The move from Technical Expert to Manager

-
Image
Let me start of by explaining how things were before I became a Manager. I worked my way to a Senior ASP.NET developer with a decent amount of SharePoint exposure; it only took me 7 years. And in those 7 years I was usually poorly managed; • scope was poorly defined and not managed • no clear plan was in place or plan omitted crucial steps • timeframes were unrealistic • no quality checks were in place (faults were discovered during client demo's) • clients expectations were not managed • communications were poor • processes were not followed • resource allocation was poor (I once requested a .NET developer and my Manager believed he solved the problem when he got me a junior network administrator who knew a little HTML) • poor risk management In many cases I had reached a point where I had very little faith (or respect) for my manager that I insist that they present me with the requirements and leave me alone so I can “do my magic”, this involv...
Read more

Please don’t pimp your SharePoint site

-
Image
Look at this picture, someone spent allot of money on a Benz, but decided that they wanted to make the car look like a sports car instead, so with a little extra time and money, they added design elements that made the car look different, the new look gets a great deal of attention and everyone wants to drive it, but later people notice that the car cannot drive faster than 30km/h or drive up an incline without breaking something, the lights didn’t work as well as they use to, you can only enter the car a certain way, sharp turns has not been tested but is not recommended and only people with special training or knowledge on how this new look was implemented will be able to wash, repair, drive or fuel up the car. Sounds crazy doesn’t it, well, that’s what you are asking us to do when you ask for a SharePoint site that does not look like a SharePoint site. Sticking with my Benz example, the Benz comes from the factory in silver, black, white and red, and a special colour can even ...
Read more