Intranet governance

Organisations are depending on their intranets to deliver information and services which directly impact on performance.  For successful organisations intranets are more than ‘nice to have’ extras with a few bits of news and some policies which might be out of date.

Intranets are becoming critical to employees needing to complete tasks using tools and apps on the intranet.  They need to be easy to find and easy to use.  Employees also want to feel confident the information they use is relevant, up to date, reliable and clearly owned should they need more information.

Employees share information and contact friends and followers using tools on the internet that are very easy and very rich in features and functions.  They expect their organisation’s intranet to offer the same experience.  It will become a factor in new recruit’s deciding whether to join an organisation or whether to stay and become an engaged employee.

How will you be able to to achieve this?
Your intranet doesn’t just need different technology to solve these problems – not even SharePoint 2010.  It is how you implement technology, what your business priorities and strategy are and how you manage the information and tools on your intranet that really make the difference and will bring success.

Intranet should be organised based on some key factors governance, strategy, communications, engagement, collaboration, usability and measuring value.Contact me to find out how I can help you:

• develop a strategy aligned with your organisation’s and align with business head or leader
• find the right approach to successful technology and change projects 
• understand what publishing standards you need and how best to implement them
• advise on compliance with standards and risk management
• measure the full value of an intranet
• design roles and responsibilities within a governance framework

My tailored service to business:

• a few hours help and guidance
• a day’s training/workshop
• a few days advice and detailed guidance
• a few weeks strategic guidance, project planning and if needed, implementation

Find out more about my experience, read the information below and get in touch.

Moss Site usages report

Moss Site usages report explained

This paper gives detailed descriptions of parameters displayed in MOSS 2007’s usage reports.
Since very similar reports exist at both the Site and Site Collection level, descriptions will be combined when applicable.  The phrase “site/collection” will be used to indicate either site or site collection, depending on which level the report was requested at.
Performance tip: the default page for usage reporting demands the most of SQL Server because it has the most reporting parts; each part executes at least one stored procedure to retrieve its data.  Each part is also found on other reporting pages.  It may be desirable to bookmark specific pages for detailed reports, it the summary report is not desired.  This will prevent the intensive processing required to summarize all reports if all that is wanted are details.
Note, when a description says “over the past 30 days” or “divided by 30” the underlying calculations always account for the possibility that usage reporting may have been turned on less than 30 days ago, and fewer than 30 days worth of records exist.  In these cases, the appropriate number less than 30 is used.
In all calculations, “Requests” means a request for a single page, and does not include any of the items that appear on the page that may require additional HTTP requests to the server.  In other words, a Request is equivalent to what is commonly called a Page View.  Statistics for intra-page requests such as graphics, scripts and style sheets are not collected for SharePoint usage reporting.
“Distinct” users are the same as “Unique” users.  Each is computed via the SQL operator DISTINCT when selecting over all users.
Show hidden text for underlying technical specifications.

Average requests per day over past 30 days: average = total number of requests over past 30 days, divided by 30 to give daily average.

Distinct users over past 30 days: total number of users accessing this site/collection over the past 30 days, not including repeat visits from the same user.

Distinct users yesterday: total number of users accessing this site/collection on yesterday’s date, not including repeat visits from the same user.

Requests yesterday: total number of requests to this site/collection on yesterday’s date.

Queries Yesterday: total number of search queries submitted by all users from this site/collection on yesterday’s date.

Queries Over Past 30 Days: total number of search queries submitted by all users from this site/collection over the past 30 days.

Top Pages (Average requests per day over past 30 days)

Table

• Page: URL of requested page

• Value (decimal): average = total number of requests for this page over the past 30 days, divided by 30 to give daily average.

Top Users (Average requests per day over past 30 days)

Table

• User: ID of user accessing this site/collection.

• Value (integer): average = total number of requests from the user to this site/collection over the past 30 days, divided by 30 to give daily average.

Top referring pages (past 30 days)

Pie Chart

• URL: page that any user visited just prior to browsing to a page in the current site collection.  The top 5 URLs are shown.

• Slice-value (integer): total number of times this URL was a referring page over the past 30 days.