Portals and Collaboration https://chamonix.com.au/blog/category-portalsandcollaboration en Emerging technologies sparking innovation at DPTI https://chamonix.com.au/blog/article-emergingtechnologiessparkinginnovation <span>Emerging technologies sparking innovation at DPTI</span> <span><span>Sophia Siegele</span></span> <span>Tue, 06/26/2018 - 01:34</span> <div><p>The Department for Planning, Transport and Infrastructure (DPTI) Library recently hosted their first ‘Lunch and Learn’ session for 2017 with a deep-dive into emerging technologies at the&nbsp;<a href="http://odasa.sa.gov.au/">Office for Design + Architecture</a>&nbsp;on Leigh St. Chamonix, in partnership with&nbsp;<a href="http://www.cortexinteractive.com.au/">Cortex Interactive</a>, were invited to present on, and demonstrate the application of, Virtual and Augmented Reality solutions to guests from across Government and industry.</p> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-06/ph4.jpg?itok=kXJMh9Dd" width="1140" height="642" alt="Emerging technologies sparking innovation at DPTI" /> </li></ul> <div><div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'><p>Over 50+ attendees from DPTI, Renewal SA, Department of Environment, Water and Natural Resources, Adelaide City Council,&nbsp;<a href="https://www.adelaidesmartcitystudio.com/">Adelaide Smart City Studio</a>&nbsp;and Department of State Development were able to experience emerging technologies in action, and hear from a number of guest speakers and subject matter experts including Tim Angel, Managing Director of Cortex Interactive.</p><p>Virtual and mixed reality technologies were a focus, with potential applications for DPTI including:</p></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'padding-top: 10px;'>Safety & Training </h4> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'><ul class = "list"> <li>Virtual fire training e.g. operating a fire extinguisher to put out a fire</li> <li>National rail level crossing inspection training</li> <li>Driverless care use e.g. how a passenger might react to driverless modes of operation</li></ul></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'padding-top: 10px;'>Urban Planning & Planning Decisions </h4> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'><ul class = "list"> <li>Ability to visualise and model planning scenarios for various developments, which could provide further value for planning authorities and developers to demonstrate and assess likely impact of proposals.</li></ul><p>It was a pleasure participating in the interactive session, and we look forward to working with clients to uncover and develop commercial applications for VR technologies.</p></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> Mon, 25 Jun 2018 16:04:00 +0000 Sophia Siegele 120 at https://chamonix.com.au Challenges of Introducing DevOps https://chamonix.com.au/blog/article-challengesofintroducingdevops <span>Challenges of Introducing DevOps</span> <span><span>Dave Sampson</span></span> <span>Tue, 06/26/2018 - 01:33</span> <div><div class = ' ui-sortable-handle'><p>Recently I’ve worked with a number of clients who are enthusiastic to start introducing DevOps practices into their organisations. DevOps has definitely gained a lot of momentum and buzz in recent times, and it’s been interesting to assist as organisations approach its introduction in different ways.</p></div> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/challengesofintroducingdevops.jpg?itok=HIMr-7Nv" width="1140" height="642" alt="Challenges of Introducing DevOps" /> </li></ul> <div><div class = ' ui-sortable-handle ui-sortable-handle'><p>Over the course of these engagements I’ve observed a few key themes and considerations that can really influence the success or otherwise of&nbsp;starting on the DevOps journey.</p></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black ui-sortable-handle ui-sortable-handle'>DevOps permeates the organisation </h4> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle'><p>Thinking of DevOps as simply a bunch of clever automation put in place by geeky infrastructure guys is risky at best. As you’ll observe from a number of the other considerations I’ve listed, introducing DevOps can necessitate a shift in thinking from across the organisation, not just from traditional development and IT ops. I’m not suggesting your whole organisation needs to go on a “5-day DevOps fundamentals” course, but it’s equally important to appreciate that introducing DevOps can challenge traditional thinking and practices across the organisation. The more you can communicate and include other areas in the journey the better your outcomes are likely to be.</p></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black ui-sortable-handle ui-sortable-handle'>Process doesn't go away </h4> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle'><p>DevOps still relies on solid service management &amp; operational principles. Processes such as IT change management, configuration management and release management are still as important as ever, and while you might be able to automate some aspects of them, unless you have a good starting point you may be automating less than ideal practices. You should also consider how any automation that you do put in place will interact with non-automated parts of any process, particularly where you’re integrating with traditional governance and authorisation entities like Change Advisory Boards.</p></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black ui-sortable-handle ui-sortable-handle'>Solid requirements are just as important as ever </h4> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle'><p>Because DevOps spans development&nbsp;<em>and</em>&nbsp;operations for a product, there’s even more emphasis placed on having solid requirements not just for product features, but also on how the product’s expected to be operated. Even if you’re working in a more agile manner without heavy-weight up-front requirements, your backlog still needs to cater for non-functional and operational backlog items. In effect, your DevOps automation suite (whether it’s automating builds or tests or deployment or infrastructure or whatever) becomes another feature that you’re building and that needs solid requirements, or else you risk building the most amazingly automated wrong thing!</p></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black ui-sortable-handle ui-sortable-handle'>Packaging & deployment automation needs to be driven by requirements (just like product features) </h4> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle'><p>The design of your packaging and deployment mechanism (ideally automated via the DevOps tool chain) needs to be&nbsp;informed by requirements. It’s important to consider things like the anticipated types and frequency of change that will be made to the product being operated, and dependencies between products in an operational product set (if your service consists of more than one product). As a couple of examples of the impact this can have:</p><ul class = "list"> <li> <p>Types of change. If you have a monthly operational process for releasing change to&nbsp;<em>information</em>&nbsp;provided by your product, but the only way to deploy that change is by re-deploying the whole product, it can potentially create a larger operational process &amp; testing overhead.</p> </li> <li> <p>Granularity of deployment. Similarly, if you only design your deployment process so you can click a button to deploy the entire product set, what happens if you only want to (or need to) deploy a change to a single component?</p> </li></ul></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black ui-sortable-handle ui-sortable-handle'>Consider the additional testing implications of more frequent deployment </h4> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle'><p>DevOps can automate your deployment process to the point of deploying a new product version in seconds, but if you’re still relying on manual testing you may just be moving the overhead to your testing team. And if you’re in the fortunate position to be able to create a test automation suite to bring into the DevOps chain, consider the ongoing requirements to develop, test and maintain this test suite itself&nbsp;– it’s generally not a write-once, never-touch-again exercise. Test automation is about finding an appropriate balance between coverage versus risk of&nbsp;regression versus ongoing maintenance effort.</p></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black ui-sortable-handle ui-sortable-handle'>Can you identify & prove what's changed? </h4> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle'><p>Traditional IT change management &amp; testing relies on the ability to be able to explicitly identify the components that have changed. If your DevOps deployment process relies on replacing running instances with new instances (even if the underlying component hasn’t changed), is this a change or isn’t it? Does it need to be tested or not? What’s required to prove that it hasn’t changed?</p><p>None of this is rocket science, but nonetheless it’s all important to take into consideration as you begin your DevOps journey. There are undoubtedly a raft of other considerations, and as with everything I expect for myself and Chamonix to continue to learn and grow as we assist our clients with their own journeys. Nothing in our industry ever stands still and every day is a fresh opportunity to re-evaluate what you knew yesterday!</p></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> Mon, 25 Jun 2018 16:03:00 +0000 Dave Sampson 121 at https://chamonix.com.au bypass the office365 login redirect page with ADFS https://chamonix.com.au/blog/article-office365redirect <span>bypass the office365 login redirect page with ADFS</span> <span><span>Chamonix Consulting</span></span> <span>Tue, 06/26/2018 - 01:32</span> <div><div class = ' ui-sortable-handle'><p>Office 365’s single sign-on capabilities with ADFS are a great improvement over dual-identities, and it takes online users a step closer to the seamless experience they have become accustomed to with an on premise web application. If you’re looking to set it up, Microsoft provide some great information and even some step-by-step videos:&nbsp;<a href="https://support.microsoft.com/en-us/kb/3061192">https://support.microsoft.com/en-us/kb/3061192</a>.</p></div> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/howtobypassoffice365.jpg?itok=q0uKXfKs" width="1140" height="642" alt="bypass the office365 login redirect page with ADFS" /> </li></ul> <div><div class = ' ui-sortable-handle ui-sortable-handle'><p>But, once you’ve got it all hooked up you quickly find a couple of unexpected “features” that can ruin your user experience.</p><p>If you are aware of these features and have tried everything, jump to the end of this post to see the magic! It’s not rocket science, but the workaround isn’t obvious and the technique isn’t overly well documented or communicated.</p><p>So, if you are still with me, the following process should sound familiar:</p><p>When you attempt to access https://portal.office.com you are prompted for credentials, email address and password. When you finish typing in your email address the page bounces you via your ADFS server, prompting you for credentials again if you are not on the domain.</p><p>If you are on the domain it signs you in and takes you to the Office 365 portal landing page – not a very exciting page. None of which requires you to use your password, so why show them that box on the first screen?</p><p>If you’re not on the domain you will need to enter your password, but on the second screen, not the first screen, so don’t start typing too quickly.</p><p>The next time your open your browser to go to Office 365 via https://portal.office.com, although it can remember who you are, it simply sits on the this login page until you click on your email address.</p><p>You receive a similar experience when you attempt to access your SharePoint Online site, none of which provides a very friendly user experience, particularly for those users that aren’t aware of any difference between their old Intranet and the SharePoint Online Intranet.</p><p>Now, I completely understand the technical barriers and implementations that Microsoft needs to support but we can’t realistically expect users to be happy with all of these steps. In addition, most users expect that the home page that IT pops into their browser is going to take them to the Intranet, not some strange portal landing page.</p><p>Now we’ve got all of the doom and gloom out of the way, let’s talk about how we fix this.</p><p>The first thing we need to do is to bypass the step before the ADFS redirect. The login page checks the domain of your email address to see if it can bounce you via ADFS, so if we could somehow include this in the URL we could skip the need for users to type in their email address. Fortunately there is such a URL!</p><p>In place of https://portal.office.com you can get users to use:</p><p>https://login.microsoftonline.com/login.srf?wa=wsignin1.0&amp;whr=%5Byour domain|RS|</p><p>So if your email address was bob@example.com you would use https://login.microsoftonline.com/login.srf?wa=wsignin1.0&amp;whr=example.com. Note, the same URL can be used for all users of the domain as it doesn’t care what the user’s username is, just their domain.</p><p>Now although this is a massive improvement, it isn’t really memorable. So it would be a good idea to set this as the user’s homepage. But, now, even though the user is logged straight it, it takes them to the Office 365 landing page. This shows you all of your “Apps” but it won’t be immediately obvious to users where they can find the Intranet. Click on Sites, click on the promoted link – not a great experience.</p><p>What would be really cool is if you could use this magic login technique alongside your SharePoint Online URL. Guess what, you can.</p><p>The %3A%2F%2F after https is :// URL encoded, as this is a querystring parameter it is a good idea to make sure it is encoded.</p><p>Following this URL will take you via example.com’s ADFS server, log you in if you are on the domain or prompt your for credentials on an example.com branded page, and then take you to example.com’s SharePoint Online team site – sorted!</p></div> </div> Mon, 25 Jun 2018 16:02:00 +0000 Chamonix Consulting 122 at https://chamonix.com.au Mobile BI for lawyers https://chamonix.com.au/blog/article-mobilebiforlawyers <span>Mobile BI for lawyers</span> <span><span>Chamonix Consulting</span></span> <span>Tue, 06/26/2018 - 01:23</span> <div><p>Several years ago I was working at a law firm managing the BI team. It was a law firm that was really trying to push the boundaries of technology and to leverage technology as a differentiator with their competitors.</p> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/mobilebiforlawyers.jpg?itok=uWIw_hCn" width="1140" height="642" alt="Mobile BI for lawyers" /> </li></ul> <div><p>We had established a solid and robust BI solution using Microsoft SQL Server Reporting Services (SSRS 2008r2) and Report Manager and had started down the path of using SharePoint 2010. Our lawyers, and in particular, our Partners spent a lot of time out of the office, travelling to meetings and events. We had an idea of a taxi report, a one pager that could provide them all the information they would need about a client which would include most recent interactions such as meetings and phone calls, current matters and timekeepers who were working on these matters, any outstanding bills for the client, and other relevant information. All this on one page so that they could be prepared when talking to the client.</p><p>The&nbsp;<strong>success of this taxi report was limited</strong>&nbsp;by the need for the Partners to run and print out the report before leaving the office. At the time, there was not much available in the Microsoft BI stack to securely bring this report to their mobile devices.</p><p>Since the acquisition of the mobile BI tool, Datazen, by Microsoft in April 2015, I have been playing around to see if this new tool can provide the taxi report that a law firm could truly benefit from.</p><p><em><a href="http://www.datazen.com/">Datazen</a>&nbsp;provides native apps for all mobile platforms (iOS 7, Android 4.1, Windows 8) and is easily customised to suit a phone, tablet or browser (HTML5).</em></p><p>First and foremost,&nbsp;<strong>Datazen is free if you have a SQL Server Enterprise license</strong>. This is a big tick for professional services organisations that may have invested in enterprise backend technology but do not want to spend extra on peripheral solutions. And remember, at a law firm, we are talking about the Partner’s hard earned profits.</p><p>Secondly,<strong>&nbsp;Datazen is secure</strong>, which is of utmost importance when storing client data on a mobile device. It is secure through the entire stack, from secure SSL connection between server and device, data encryption at rest on the server, and data encryption on the client device in case of device loss.</p><p><strong>What follows is my journey …</strong></p><p>I downloaded the Datazen Publisher client for Windows which is required for developing dashboards. I also went about installing Datazen Enterprise on a VM in Azure (more on this another time) to allow Datazen to be consumed by mobile devices and to provide access to enterprise and cloud data sources (SQL Server, SSAS, SharePoint, generic ODBC). Without Datazen Enterprise the Publisher only allows for dashboard design against an Excel spreadsheet.</p><p>Without focussing too much on all the wiz-bang functionality within the product suite itself, I developed a simple dashboard that presented the user with a summary of their clients, with a selector to choose the client, and then various gauges and charts to provide an overview of the client and their performance. The clients presented in the selector can be filtered based on the user logged into datazen. I also used the drill- through capability within Datazen to allow the user to open an associated dashboard linked to a KPI on a gauge. And yes, it supports the passing of parameters to the drill-through dashboard.</p><p><strong>Datazen requires the data it consumes to be prepared up front</strong>. There is no way to model data within Datazen and it is limited to basic aggregation. In most cases I would expect that the data would need to be manipulated in the SQL before consumption by Datazen.</p><p>In my example I have created the dashboard off of Excel sheets. The&nbsp;<strong>information that I included in the dashboard was designed to provide an overview of client performance</strong>. When the partner (user) opens the dashboard, a list of their current clients is shown. Once they select a client, the dashboard updates to display the metrics for the selected client. I included metrics around:</p><ul class = "list"> <li>Billings and performance against budget for the client</li> <li>Number of interactions with the client (Email, Meetings, Phone) and performance against budget</li> <li>Number of current matters</li> <li>Number of outstanding bills and a comparison to the previous month</li> <li>Client sentiment towards the firm and a comparison to the previous year</li> <li>Chart of the timekeepers working on matters for the client ordered by the most hours billed</li> <li>Pie chart of the breakdown of the client bills for the partner to show how much the client contributes to the partners overall client base.</li></ul><p>As mentioned above, the work required here is really in the preparation of the data and providing the datasets for the gauges and charts with the right structure. Once this is done, the dashboard can be published to the Datazen Enterprise server.</p><p>Basically once a chart or gauge is created,<strong>&nbsp;it can be reused between the master, tablet and phone views meaning the chart or gauge is only created once</strong>, but then can be used (or not) in different views, and can be resized etc. This is quite handy when negotiating between displaying important and relevant information on the phone, and displaying more detail on a tablet.</p><p>In the phone view Datazen will also automatically hide certain details on charts to save on real estate. Notice the Hours by Timekeeper chart does not have the timekeeper names on the Phone view, but pressing on a column will bring up the details.</p><p>I also created a dashboard that presented&nbsp;<strong>more detailed information about the interactions</strong>&nbsp;the firm was having with the&nbsp;client. This dashboard is viewed by clicking on the Interactions gauge which has a drill- through link passing the client as a parameter.</p><p>There are&nbsp;<strong>many other features which I have not covered</strong>&nbsp;in this blog which include KPIs, collaboration, caching of data, security and filtering on demand and custom maps. I feel that there are many use cases for Datazen particularly with the integration of custom maps (think live alerts to maintenance crew on a gas pipeline or a heat map of patronage at train stations).&nbsp;<strong>Hopefully there will be more news from Microsoft as to the future of this product</strong>&nbsp;and any potential integration into its existing BI stack.</p> </div> Mon, 25 Jun 2018 15:53:00 +0000 Chamonix Consulting 131 at https://chamonix.com.au Life before, during and after Sharepoint https://chamonix.com.au/blog/article-lifebeforeduringandaftersharepoint <span>Life before, during and after Sharepoint</span> <span><span>Chamonix Consulting</span></span> <span>Tue, 06/26/2018 - 01:15</span> <div><p>Think First: Strategic Planning Having done a great deal of SharePoint implementation work in recent times, it’s been a welcome change to spend the last couple of months working on strategic plans, roadmaps and reviews. Developing or refreshing any strategy is always interesting and intellectually challenging, and the diversity of requirements, expectations and issues that manifest from one company to the next is endlessly fascinating.</p> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/lifebeforeandduringandaftersharepoint.jpg?itok=LRnfoe5b" width="1140" height="642" alt="Life before, during and after Sharepoint" /> </li></ul> <div><p>Given I’m a consultant, you’ll probably expect me to declare my fondness for a good strategic model. &nbsp;Well sure, but it’s not a lazy preference for diverting diagrams – I expect a framework or model to work hard, providing much needed structure and clarity in assessing current and target states for complex, interconnected domains of people, process, content and technology. In previous strategy work I’ve used maturity modelling but, for a recent IT strategy engagement, an IT maturity model was judged too esoteric. I considered several alternatives in my search for another framework, but ultimately I found Gartner’s Demand – Control – Supply structure offered the best means of evaluating the client’s IT environment.</p><p>I’ll leave it to Dave Aron to explain why: structure is absolutely critical in large scale strategy exercises. (And medium and small ones too!) Being able to separate and link demand, control and supply-side issues, and further into subcategories (for example on the demand side: business context, business success, business capabilities and IT’s contribution) that are consistently used is a valuable exercise in itself – and helps to bring some clarity to the wicked problem that strategy setting is. http://blogs.gartner.com/dave-aron/2011/02/17/structure-is-content/ Dave delves further into consultant-speak in his post to describe the framework as follows: A MECE structure/framework covers the whole problem space (the CE part) and has pieces that do not overlap (the ME part), similar to the pieces of a jigsaw. The ME part helps you divide and conquer the issue at hand, and the CE part gives you confidence you aren’t missing anything Put rather more simply, the thing I liked best about the Gartner framework over others I considered is that it facilitated a full assessment of IT in the context of the overall business. Those of us who spend our working lives with a foot in both camps frequently get to experience the entrenched divide between “IT and the business” – the Mars and Venus of organisational practice it would seem (notwithstanding the few stellar exceptions that prove the rule.) At its worst this divide can lead to significantly increased costs and overheads that can stymie business profit, growth or agility; and so eliminating the silo approach as far as possible when developing an IT strategy seems to me an important objective. &nbsp;The buzzword is achieving strategic ‘alignment’ though there are some provocative souls out there who claim that the best IT strategy is no IT strategy. &nbsp;It’s a thought, though if you ask me it sounds like a technique with a high degree-of-difficulty score, best performed at Maturity Level 5.</p><p>Just by the by, I discovered Richard Rumelt’s http://www.strategyland.com/ recently and actually read (or, if I’m being honest and oxymoronic, thoroughly skimmed) his book Good Strategy Bad Strategy: The Difference and Why It Matters recently. &nbsp;Particularly liked the examples that distinguished the good from the bad. Of Rubber and Road If the Strategy is the why and what, then the Roadmap of recommended projects, initiatives or tasks arising out of the strategic rationale is the when and how. Unsurprisingly, this is what most clients focus on, and fair enough too since “plans are only good intentions unless they immediately degenerate into hard work” as Peter Drucker has said. &nbsp;And that ‘degeneration’ from plan to activity seems to be problematic much more often than it should be. One of the reasons I like to work across the spectrum from strategy through to implementation is that ultimately I prefer to produce something tangible out of all that hard brain yakka. And surely a strategy is only as good as its realisation? &nbsp;That said, I believe the strategic rationale for implementation – the context – is equally important and maybe that witticism “we have a strategy: it’s called doing things” isn’t quite as smart as it sounds. &nbsp;We all want to avoid analysis paralysis, but charging ahead into activity without due consideration of the why and what is reckless. On a recent IT strategy job, we developed the usual IT roadmap-on-a-page, mapping out phased initiatives over three years. &nbsp;But for the highest priority / highest impact initiatives – particularly those with a remediation component – the client required an even greater level of detail than that provided in the table accompanying the roadmap. &nbsp;So we agreed to produce a series of Action Plans. Details included: objectives, risks and issues, dependencies and assumptions specific to the proposed initiative the principal / recommended tasks comprising the initiative indicative timeframes and resource requirements the anticipated degree of difficulty and ROI impact Overall, the concept worked very well and gave the client greater confidence in their ability to implement after their strategy consultants had left the building. I’ll reuse the idea and the template wherever appropriate to assist clients move from strategic plan to execution. Think Again: Strategic Review I’m now on a strategic review engagement, doing a sort of ‘health check’ of a client’s online collaboration environment on its first birthday (or near enough) and making recommendations for improvements. They’ve done a particularly great job thus far, but they’re to be congratulated for not resting on their laurels. They’re wide open to assessing what’s worked and what hasn’t, thus far, and are still looking for ways to build further upon their success. They want some Action Plans too. If, as Rumelt claims, “organizations experience significant entropy—the continual drift towards disorganization”, then online collaboration environments may well be the most entropic of all business information management tools. There’s always room to improve.</p><p>Rather importantly, that necessitates checking back with the business to establish what improvement should constitute – there’s that ‘strategic alignment’ again. (I’ve been doing staff interviews for this job, as I did for the previous, and probably the five before that, and I’m reminded yet again just how much of my working life involves questioning people.) *What’s This Got To Do With SharePoint? Absolutely nothing. With that title I was just trying to indicate there’s more to me and the work I do than SharePoint expertise ;-) But also that there’s more to SharePoint than just deploying SharePoint, if you get my meaning. &nbsp;I suppose this post could be a sort of Tip #0 in my series Top Ten Tips for Success With SharePoint. &nbsp;Don’t go rolling out SharePoint to your enterprise unless you’ve assessed the platform to be a good fit with your business / IT Strategy and Roadmap that will meet your business requirements. And having done SharePoint, appreciate that it’s never finished, and plan accordingly. How about a roadmap! &nbsp;Whatever you’re using SharePoint for, make sure you deliberately review the platform, and explicitly plan to refresh and enhance it in line with your business / IT strategy.</p> </div> Mon, 25 Jun 2018 15:45:00 +0000 Chamonix Consulting 139 at https://chamonix.com.au Top 10 tips for success with Sharepoint #10 https://chamonix.com.au/blog/article-top10sharepoint10 <span>Top 10 tips for success with Sharepoint #10</span> <span><span>Chamonix Consulting</span></span> <span>Tue, 06/26/2018 - 01:13</span> <div><p>The best advice I can give anyone for success with SharePoint over the long term is to embrace it and enjoy the journey. Journey?&nbsp;That’s right, just like business itself, SharePoint isn’t something you every really finish, but is always a work in progress. &nbsp;Sometimes a journey can be a drag, it’s true&nbsp;(uncomfortable beds/bedfellows, dubious food, forever packing up and moving on to the next location and usually just when you feel most settled, communication issues, etc.). But being open to exploration and discovery can bring substantial rewards.</p> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/sp10.jpg?itok=FX5qLeNp" width="1140" height="642" alt="Sharepoint" /> </li></ul> <div><p>I suppose this post is a variation on&nbsp;<em>Love The One You’re Wi</em>th (see&nbsp;<a href="http://chamonix.com.au/success-with-sharepoint-3">tip #3</a>), but in finishing this lengthy series I really do want to accentuate the positive, eliminate the negative, latch on to the affirmative and not end on Mister In-Between.</p> <h4 class = ' align-left font-alt uppercase black'>Get into the groove </h4> <p>With a product like SharePoint there’s always a great deal to learn, but don’t be intimidated, plunge in and before you know it you’ll be a&nbsp;<a href="http://veroniquepalmer.wordpress.com/2011/07/31/the-first-sharemaster-ever-july-2011-michelle-barker/">SharePoint Master</a>.&nbsp;There are plenty of online training and user adoption resources I’ve referenced in other posts in this series, both formal and informal.&nbsp; Plus, everyone needs a bit of serendipity in their lives, so to really get into the SharePoint groove why not…</p><ul class = "list"> <li><strong>Connect with the SharePoint community</strong>&nbsp;– I don’t mean partners and consultants, though we all have lots of expertise and most of us have a willingness to share.&nbsp; Connect with your peers.&nbsp; There are lots of them out there. &nbsp;If you can’t find a local group, perhaps you should start your own?&nbsp;&nbsp;Listen to what’s working for your peers in other organisations, and why, and assess how these successes might translate to your own environment. (Similarly, keep an ear open to failures and try to avoid the same.)</li> <li><strong>Attend a conference</strong>&nbsp;– In my part of the world I’ve been fortunate to be involved in the&nbsp;<a href="http://www.shareconference.com/share">Eventful Management ‘Share’ conference</a>, and can highly recommend this for business people and non-technical managers with responsibility for SharePoint.</li> <li><strong>Follow a few gurus, and subscribe to discussion groups</strong><br> Lurk or participate, either way you’ll absorb knowledge and ideas without even trying.&nbsp; For example, I’ve captured&nbsp;<a href="https://chamonixvue.wordpress.com/2011/08/04/hitch-hikers-guide-to-the-sharepoint-blog-galaxy/">my favourite bloggers in this post</a>, and some active groups on LinkedIn are:<br> <em>SharePoint Experts</em>&nbsp;on LinkedIn:&nbsp;<a href="http://www.linkedin.com/groups?home=&amp;gid=42512">http://www.linkedin.com/groups?home=&amp;gid=42512</a><br> <em>SharePoint 2007 &amp; 2010</em>&nbsp;on LinkedIn:&nbsp;<a href="http://www.linkedin.com/groups/SharePoint-2007-2010-43166">http://www.linkedin.com/groups/SharePoint-2007-2010-43166</a><br> <em>SharePoint Users Group</em>&nbsp;on LinkedIn:&nbsp;<a href="http://www.linkedin.com/groups?gid=58750">http://www.linkedin.com/groups?gid=58750</a><br> <em>SharePoint Intranets</em>&nbsp;(Sub-group of the Worldwide Intranet Challenge) on LinkedIn:&nbsp;<a href="http://www.linkedin.com/groups?gid=3293870">http://www.linkedin.com/groups?gid=3293870</a></li> <li><strong>Connect with other like-minded communities</strong><br> You don’t need to focus exclusively on SharePoint to succeed. I believe you can learn a lot from other applications and communities that will inform and enrich your thinking about SharePoint. &nbsp;Join a general community on Web Content Management, User Experience Design, Social Business, or Intranet Design, or whatever suits your role or tickles your fancy, and expand your horizons. Great ideas can usually be transposed to any platform.</li></ul> <h4 class = ' align-left font-alt uppercase black'>Map it </h4> <p>Serendipity can be great fun, and might even be the mother of innovation, but it’s a risky way to approach an entire journey. &nbsp;So I advocate some considered planning for the future. Once you’ve got a decent handle on SharePoint’s capabilities,&nbsp;<em>and you understand how to translate those into business value</em>, you’ll know what your destination options are.&nbsp; Evaluate where to take SharePoint in your organisation and plan out the hops or stages to ensure you get there.&nbsp;&nbsp; For example, assess how best – and how far – to progress your SharePoint deployment up the value chain.&nbsp; Sadalit van Buren’s SharePoint Maturity Model is a good way to approach this:&nbsp;<a href="http://sharepointmaturity.com/">http://sharepointmaturity.com/</a></p><p><em>|LS|Aside:&nbsp;I love a Maturity Model – use them all the time in my strategy work – but worth noting that moving up the maturity ladder shouldn’t be approached as a Given or a Good Thing in all circumstances. Progression through each maturity level usually requires significant investment of time and resources, and you should always assess that effort against benefit.&nbsp;Yes, the old ROI catch.&nbsp; So achievement of the state of nirvana promised by Level 5, or ‘fully optimized,’ or however your Maturity Model of choice describes its peak, shouldn’t necessarily be targeted uncritically as the ultimate goal of any growth strategy, including SharePoint enhancement. Hovering at stage 3, say, might be a perfectly acceptable goal for a given organisation. Just my 2 cents’ worth.|RS|</em></p><p>But I digress…&nbsp; Use a&nbsp;<a href="http://www.benqt.com/kb-category/e-business-maturity-model">Maturity Model</a>&nbsp;as a reference point for drawing up a roadmap for SharePoint that’s aligned with your business’s strategy and plans.&nbsp; Since no-one has a crystal ball, be sure to revise and refine this roadmap over time, as business circumstances and plans change and new requirements emerge. &nbsp;Alan Weintraub has a post on creating a SharePoint roadmap here&nbsp;<a href="http://www.aiim.org/community/blogs/expert/Creating-a-Roadmap-to-SharePoint-Success">http://www.aiim.org/community/blogs/expert/Creating-a-Roadmap-to-SharePoint-Success</a>&nbsp; And there are&nbsp;<a href="http://www.google.com.au/search?hl=en&amp;biw=1440&amp;bih=775&amp;gbv=2&amp;tbm=isch&amp;sa=1&amp;q=business+roadmap&amp;oq=business+roadmap&amp;aq=f&amp;aqi=&amp;aql=&amp;gs_sm=e&amp;gs_upl=3460l3460l0l3713l1l1l0l0l0l0l0l0ll0l0">myriad options for collating and publishing the information as a one page map</a>, so hunt around for inspiration and choose the approach and presentation mode that best suits your organisation.</p><p>If and when requirements demand it, and the business is ready, maybe you’ll want to extend and enhance your SharePoint platform.&nbsp; Perhaps you’ll investigate the&nbsp;<a href="http://sharepoint.microsoft.com/Blogs/GetThePoint/Lists/Posts/Post.aspx?ID=298">Business Connectivity Services</a>&nbsp;(BCS) as a means of integrating external data from back-end business systems with SharePoint.&nbsp; Or the&nbsp;<a href="http://sharepoint.microsoft.com/en-us/Product/Pages/Feature-Details.aspx?Capability=Insights&amp;FeatureID=10">Business Intelligence features of SharePoint 2010</a>&nbsp;(Enterprise edition).&nbsp; A colleague who’s implementing&nbsp;<a href="http://sharepointmagazine.net/articles/business-user/three-main-reasons-why-you-should-upgrade-to-fast-for-sharepoint">FAST search for SharePoint</a>&nbsp;for a client has reported extremely impressive results; I confess I’m a bit gob smacked at just how impressive, as I think the Standard edition out-of-the-box search is pretty good in its own right.</p><p>You might also want to evaluate offerings from the SharePoint partner ecosystem to extend your environment beyond out-of-the-box options.&nbsp;Approach with caution (see my&nbsp;<a href="https://chamonixvue.wordpress.com/2011/05/28/success-with-sharepoint-3/">churlish post against excessive customisation / add-ons</a>) but if needs must, then SharePoint Reviews is a useful albeit not totally comprehensive directory:&nbsp;<a href="http://www.sharepointreviews.com/">http://www.sharepointreviews.com/</a>.</p> <h4 class = ' align-left font-alt uppercase black'>Summing up </h4> <ul class = "list"> <li>The SharePoint journey is there to be enjoyed, and there’s plenty of support available to help you do so</li> <li>Top Ten Tips … phew, we got there in the end …. Best wishes for success with your own SharePoint adventure</li></ul> </div> Mon, 25 Jun 2018 15:43:00 +0000 Chamonix Consulting 141 at https://chamonix.com.au The hitch hiker's guide to the Sharepoint blog galaxy https://chamonix.com.au/blog/article-hitchhikersguidetosharepointblog <span>The hitch hiker&#039;s guide to the Sharepoint blog galaxy</span> <span><span>Chamonix Consulting</span></span> <span>Tue, 06/26/2018 - 01:12</span> <div><p>Hiking your way through the peaks and valleys of SharePoint?&nbsp; Need a guide or three?&nbsp;&nbsp;Here are some URLs where you’ll find great blogging minds applying fingers to keyboard on all things SharePoint. &nbsp;Only minimally grouped, and in no particular order …</p> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/hitchhikersguidetothesharepointbloggalaxy.jpg?itok=xyblnD-8" width="1140" height="642" alt="The hitch hiker&#039;s guide to the Sharepoint blog galaxy" /> </li></ul> <div><div class = ' ui-sortable-handle'><p>I tend to subscribe to the business oriented blogs and read their posts avidly, and dip into the technical blogs more as a knowledge base for&nbsp;<em>ad hoc</em>&nbsp;trouble-shooting – you’ll find your own favourites and approach.&nbsp; Thank goodness for them all.&nbsp; Grab a lift and shortcut your trip.</p></div> <div style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black'>Business-ish </h4> <div class = ' ui-sortable-handle'><ul class = "list"> <li>Views from Veronique: &nbsp;<a href="http://veroniquepalmer.wordpress.com/">http://veroniquepalmer.wordpress.com/</a></li> <li>Richard Harbridge:&nbsp;<a href="http://www.rharbridge.com/">http://www.rharbridge.com/</a></li> <li>End User SharePoint site:&nbsp;<a href="https://www.nothingbutsharepoint.com/sites/eusp/Pages/default.aspx">https://www.nothingbutsharepoint.com/sites/eusp/Pages/default.aspx</a><em>&nbsp;– Okay, &nbsp;not strictly a blog, but some great articles</em></li> <li>Get the Point blog:&nbsp;<a href="http://sharepoint.microsoft.com/Blogs/GetThePoint/default.aspx">http://sharepoint.microsoft.com/Blogs/GetThePoint/default.aspx</a></li> <li>Path to SharePoint:&nbsp;<a href="http://blog.pathtosharepoint.com/about/">http://blog.pathtosharepoint.com/about/</a></li> <li>The SharePoint Contender:&nbsp;<a href="http://sharepointcontender.wordpress.com/">http://sharepointcontender.wordpress.com/</a></li> <li>SharePoint Supported blog:&nbsp;<a href="http://sharepointsupported.com/blog/">http://sharepointsupported.com/blog/</a>&nbsp;&nbsp;<em>– masked men (women?) of mystery, but some good posts</em></li></ul></div> <div style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black'>In-betweeners or a foot in each camp </h4> <div class = ' ui-sortable-handle'><ul class = "list"> <li>Bamboo Nation:&nbsp;<a href="http://community.bamboosolutions.com/blogs/featured_sharepoint_blogs/default.aspx">http://community.bamboosolutions.com/blogs/featured_sharepoint_blogs/default.aspx</a></li> <li>Paul Culmsee’s blog:&nbsp;<a href="http://www.cleverworkarounds.com/">http://www.cleverworkarounds.com/</a></li> <li>Pentalogic blog:&nbsp;<a href="http://blog.pentalogic.net/">http://blog.pentalogic.net/</a></li> <li>SharePoint Blues:&nbsp;<a href="http://www.sharepointblues.com/">http://www.sharepointblues.com/</a></li> <li>SharePoint Magazine:&nbsp;<a href="http://sharepointmagazine.net/">http://sharepointmagazine.net/</a>&nbsp;&nbsp;<em>– Okay again, not strictly a blog, but some great articles</em></li></ul></div> <div style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black'>Technical-ish </h4> <div class = ' ui-sortable-handle'><ul class = "list"> <li>Microsoft SharePoint Team blog:&nbsp;<a href="http://sharepoint.microsoft.com/blog/Pages/default.aspx">http://sharepoint.microsoft.com/blog/Pages/default.aspx</a></li> <li>SharePoint Joel (Joel Olsen):&nbsp;<a href="http://www.sharepointjoel.com/default.aspx">http://www.sharepointjoel.com/default.aspx</a></li> <li>Andrew Connell’s blog:&nbsp;<a href="http://www.andrewconnell.com/blog/">http://www.andrewconnell.com/blog/</a></li> <li>Bill Baer’s blog:&nbsp;<a href="http://blogs.technet.com/b/wbaer/">http://blogs.technet.com/b/wbaer/</a></li> <li>SharePoint Nuts &amp; Bolts (Chris O’Brien):&nbsp;<a href="http://www.sharepointnutsandbolts.com/">http://www.sharepointnutsandbolts.com/</a></li> <li>Spencer Harbar’s blog:&nbsp;<a href="http://www.harbar.net/Default.aspx">http://www.harbar.net/Default.aspx</a></li> <li>SharePoint Cowboy blog:&nbsp;<a href="http://www.binarywave.com/blogs/eshupps/default.aspx">http://www.binarywave.com/blogs/eshupps/default.aspx</a></li> <li>Laura Rodgers @ Wonderlaura blog:&nbsp;<a href="http://www.sharepoint911.com/blogs/laura/default.aspx">http://www.sharepoint911.com/blogs/laura/default.aspx</a></li> <li>Bits of SharePoint blog:&nbsp;<a href="http://www.bitsofsharepoint.com/BlogPoint/default.aspx">http://www.bitsofsharepoint.com/BlogPoint/default.aspx</a></li> <li>IT Pro on Nothing But SharePoint:&nbsp;<a href="https://www.nothingbutsharepoint.com/sites/itpro/Pages/default.aspx">https://www.nothingbutsharepoint.com/sites/itpro/Pages/default.aspx</a></li> <li>Christian Glessner @ I Love SharePoint blog:&nbsp;<a href="http://www.ilovesharepoint.com/">http://www.ilovesharepoint.com/</a></li> <li>Faraz Khan’s blog:&nbsp;<a href="http://faraz-khan.blogspot.com/">http://faraz-khan.blogspot.com/</a></li> <li>John Ross’s blog:&nbsp;<a href="http://www.sharepoint911.com/blogs/john/default.aspx">http://www.sharepoint911.com/blogs/john/default.aspx</a></li> <li>Random Musings of Jeremy Jameson:&nbsp;<a href="http://blogs.msdn.com/b/jjameson/">http://blogs.msdn.com/b/jjameson/</a></li> <li>Thor Projects (Robert Bogue):&nbsp;<a href="http://thorprojects.com/blog/default.aspx">http://thorprojects.com/blog/default.aspx</a></li> <li>SharePoint Joint (Jerry Brace):&nbsp;<a href="http://sharepointjoint.net/">http://sharepointjoint.net/</a></li> <li>The SharePoint Swiss Army Knife:&nbsp;<a href="http://blog.henryong.com/">http://blog.henryong.com/</a></li> <li>SharePoint in Pictures:&nbsp;<a href="http://blogs.msdn.com/b/sharepointpictures/">http://blogs.msdn.com/b/sharepointpictures/</a>&nbsp;–&nbsp;<em>such a good idea! Wish there were more pictures, and not all so very technical</em></li> <li>To the Point:&nbsp;<a href="http://blogs.technet.com/b/tothesharepoint/">http://blogs.technet.com/b/tothesharepoint/</a></li> <li>Woody Windischman @ The Sanity Point:&nbsp;<a href="http://www.thesanitypoint.com/default.aspx">http://www.thesanitypoint.com/default.aspx</a></li> <li>The SharePoint Farmer’s Almanac:&nbsp;<a href="http://msmvps.com/blogs/shane/default.aspx">http://msmvps.com/blogs/shane/default.aspx</a></li> <li>Tod Klindt’s SharePoint Admin blog:&nbsp;<a href="http://www.toddklindt.com/blog/default.aspx">http://www.toddklindt.com/blog/default.aspx</a></li></ul></div> <div style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h4 class = ' ui-sortable-handle align-left font-alt uppercase black'>Design </h4> <div class = ' ui-sortable-handle'><ul class = "list"> <li>See my post on&nbsp;<a href="https://chamonixvue.wordpress.com/2011/06/13/sharepoint-branding-101/">SharePoint Branding 101&nbsp;</a>for links.</li></ul></div> <div style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> Mon, 25 Jun 2018 15:42:00 +0000 Chamonix Consulting 142 at https://chamonix.com.au TOP 10 TIPS FOR SUCCESS WITH SHAREPOINT #9 https://chamonix.com.au/blog/article-top10sharepoint9 <span>TOP 10 TIPS FOR SUCCESS WITH SHAREPOINT #9</span> <span><span>Chamonix Consulting</span></span> <span>Tue, 06/26/2018 - 01:11</span> <div><p>There’s also, still, a surprisingly enduring&nbsp;bias towards technically-focused&nbsp;resources where SharePoint is concerned, which underestimates and undervalues the critical importance of business-focused resourcing&nbsp;for success. (Just scan&nbsp;this list of posts on this topic that Jeremy Thake has been capturing and hopefully you’ll see what I mean<a href="http://www.diigo.com/user/jthake/roles">:&nbsp;</a><a href="http://www.diigo.com/user/jthake/roles">http://www.diigo.com/user/jthake/roles</a>)</p> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/sp9.jpg?itok=mtXNqPi5" width="1140" height="642" alt="sharepoint" /> </li></ul> <div><h3 class = ' align-left font-alt uppercase black ui-sortable-handle'>Resource it right </h3> <div class = ' ui-sortable-handle'><p>There are two key dimensions to resourcing&nbsp;of SharePoint implementations –&nbsp;<em>project</em>&nbsp;and&nbsp;<em>operational</em>&nbsp;– but the literature mostly seems to confuse or conflate the two.</p><p>There’s also, still, a surprisingly enduring&nbsp;bias towards technically-focused&nbsp;resources where SharePoint is concerned, which underestimates and undervalues the critical importance of business-focused resourcing&nbsp;for success. (Just scan&nbsp;this list of posts on this topic that Jeremy Thake has been capturing and hopefully you’ll see what I mean:&nbsp;<a href="http://www.diigo.com/user/jthake/roles">http://www.diigo.com/user/jthake/roles</a>)</p><p>Admittedly, roles and responsibilities can blur, and the plethora of job titles can make it hard to identify who does what in the SharePoint space, but I’m going to strive for some clarification with this post because getting the resources right is important both for successful delivery of SharePoint and for successful operations long after go-live.</p></div> <h4 class = ' align-left font-alt uppercase black ui-sortable-handle'>The right project resourcing </h4> <div class = ' ui-sortable-handle'><p>When you’re deploying, upgrading, or significantly extending or enhancing SharePoint, you will probably do so within the structure of a project.</p><p>From experience I’ve found a mix of internal staff and external resources with a range of capabilities usually makes for the best project team.&nbsp; Unless you have a very strong in-house skill set in SharePoint, partnering with a solid implementation provider is a project Key Success Factor. &nbsp;With a strong understanding of the platform, there’s much greater certainty of designing a SharePoint-based solution that meets your goals and fully leverages SharePoint’s&nbsp;benefits, while avoiding common traps for young players.</p><p>Strong, effective and skilled&nbsp;<strong>Project Managers</strong>&nbsp;are worth their weight in gold.&nbsp; Personally, I’ve found good people and communication skills, an eye for detail, and vendor management expertise are more important attributes for the PM than deep SharePoint skills.</p><p>In addition to a great PM, you should carefully consider the need for&nbsp;the following project roles; though what roles are mandatory, and how many incumbents you should aim for per role depends on what you’re deploying SharePoint for and the scale of the project.&nbsp; On smaller projects, two or maybe more roles may be undertaken by one person; and on large/complex projects, some incumbents may have delegates or each role could be further broken out into sub-roles. When building a SharePoint project team, the main thing is to carefully assess your requirements to identify the scope and diversity of skill sets needed for delivery.&nbsp; &nbsp;Also, unlike the PM, I do believe that&nbsp;<em>most of the following roles need excellent SharePoint skills and experience</em>&nbsp;to produce the best solution.</p><ul class = "list"> <li><strong>Solution Architect</strong>&nbsp;– interprets business requirements to design the logical and physical solution</li> <li><strong>Business Analyst / SharePoint SME</strong>&nbsp;– gathers and interprets requirements and aligns to SharePoint features and functions.<br> This role is particularly important when SharePoint is being deployed for business process improvement, which SharePoint’s collaboration features and workflows are expected to enable (enormously useful if you have a BA who bridges the business and technical domains well)</li> <li><strong>Information Architect &amp; Usability Specialist</strong>&nbsp;– designs the ‘information model’ for the SharePoint solution, including navigation, site structure, taxonomy (content types, metadata, etc.) and even page layouts</li> <li><strong>Change Manager</strong>&nbsp;– prepares the change strategy and user adoption plan, including communications and training (e.g. Training Needs Analysis and plan)</li> <li><strong>Infrastructure Manager</strong>&nbsp;– prepares the infrastructure in accordance with the solution design</li> <li><strong>System Administrator&nbsp;</strong>– installs and configures SharePoint and SQL, implements back-ups and system monitoring</li> <li><strong>Content / Migration Manager</strong>&nbsp;– prepares the plan for creation of new content or migration of existing content into the new SharePoint solution&nbsp; (Also: EDMS / Records Manager)</li> <li><strong>Developer&nbsp;</strong>– develops any customisations&nbsp;required, integrates third party&nbsp;products, etc. May also implement branding, script migration tools, build custom InfoPath forms and page layouts, etc.</li> <li><strong>Quality or Test Manager</strong>&nbsp;– quality controls and tests any custom developed components, integration, etc.</li> <li><strong>Branding Specialist</strong>&nbsp;– skilled user interface designer,&nbsp;who creates and ideally implements a custom brand for SharePoint. Sometimes a UI designer can do the former but not the latter, and a Developer is needed to implement custom CSS.</li></ul></div> <h4 class = ' align-left font-alt uppercase black ui-sortable-handle'>Internal resources </h4> <div class = ' ui-sortable-handle'><p>Even if there’s a low level or complete dearth of SharePoint expertise within your organisation, I don’t advocate outsourcing the entire project to external resources. It’s very important that the people who are expected to use and manage SharePoint after it’s deployed are involved in its design and deployment – and not at arm’s length by way of Steering Committee membership or participation in the odd business or technical requirements workshop session. &nbsp;And I mean&nbsp;<em>fully</em>&nbsp;involved, with specific project responsibilities (though they don’t have to be seconded full-time).&nbsp; With greater skin in the game comes greater buy-in and ownership of the solution. And the quality and ‘fit’ of the solution is usually greatly enhanced by the nuanced insights of permanent staff who know the organisation in ways few external providers are likely to achieve in a limited project timeframe.&nbsp; For example:</p><p>Include your Communications or Training or HR Manager(s) in the project team with accountability for Change Management.&nbsp; If you have an internal design or marketing team, they should have involvement or at least sign-off on the visual design – even if that means your SharePoint specialist has to devote time to advising them on what should and shouldn’t be attempted regarding SharePoint branding.</p><p>Try to ensure your IT staff are responsible for key aspects of the technical implementation: if necessary, partner them up with a counterpart in the vendor team who’s not just expected to build, develop and configure, but also advise, &nbsp;mentor and up-skill your staff too. &nbsp;For example, the experienced provider or contractor might deploy and configure Development or Test environments while shadowed by the in-house IT staff, and the latter could then build the production system to acquire valuable hands-on experience.</p><p>And so it goes; I’m sure you get my drift.&nbsp; Yes, you might need to fund a business-focused SharePoint SME to spend time not just building the solution but building internal staff knowledge and expertise too. &nbsp;But the ‘teach a man to fish’ rule of thumb can pay significant dividends post launch.</p><p>In determining which permanent staff to involve in a SharePoint project, try to think ahead to life post-project. &nbsp;Who will have ongoing responsibilities for aspects of the solution in the future?&nbsp; They’re probably the people to invite into the team up front.&nbsp; One role I can guarantee will be necessary is a SharePoint&nbsp;<em>Business</em>&nbsp;Manager or Administrator or Coach or Steward or whatever you want to call him or her.&nbsp; Wherever possible, I advise my clients to nominate or recruit this role at the outset, involving them in the design and delivery of the SharePoint solution that they will be helping to manage and grow subsequently (see the section below on Operational Resourcing).</p></div> <h4 class = ' align-left font-alt uppercase black ui-sortable-handle'>External resources </h4> <div class = ' ui-sortable-handle'><p>Most medium to large SharePoint implementations I’ve been involved with have included external providers – i.e. a vendor company (they like to be called ‘partners’) or perhaps a small army of contractors, or both, with specialist skills in SharePoint.&nbsp; External providers have the benefit of exposure to many different environments and should have created a wide range of SharePoint-based solutions for many different clients in their time. Additionally, they’re usually well-connected in the SharePoint community. These characteristics can and should be leveraged to ensure your SharePoint deployment is best-of-breed.</p><p>Apart from the extreme skill and knowledge factor, a further benefit of resourcing&nbsp;a project team with external staff is that you pay for what you need when you need it and not beyond.&nbsp; Not all roles in your project team are needed on a day to day&nbsp;basis once in operational mode. As always, it depends on the nature of your implementation, but I don’t believe a majority of SharePoint implementations require ongoing branding or need a permanent solution architect over time (though you will often find these listed as mandatory for any organisation with SharePoint).&nbsp; In my view, these skills may be better&nbsp;procured on an as-need basis.&nbsp;&nbsp;Even enhancements that necessitate custom development can be bundled into logical packets and outsourced to avoid maintaining an in-house dev team.</p><p>At a minimum I’d suggest you look for the following in an external SharePoint implementation provider:</p><ol class = "list"> <li><strong>Hands-on experience of&nbsp;<em>successful</em>&nbsp;deployments</strong>, ideally similar to your SharePoint vision and project scope<br> Talk to referees, and ask detailed questions about delivery</li> <li><strong>Solid, demonstrable analysis expertise&nbsp;</strong>– both business&nbsp;<em>and&nbsp;</em>technical<br> Many projects do not recognise the importance of an experienced SharePoint Business Analyst who focuses on the business objectives as opposed to technical issues, and this is a source of project failure or compromised results rather more often than you might think.</li> <li><strong>Willingness and ability to transfer knowledge&nbsp;</strong>over the course of the project, to mentor and help grow your in-house skills<br> You do not want a partner who is precious about their intellectual capital, builds your reliance on their ‘exclusive’ knowledge of your SharePoint solution over the course of the project until it’s set like concrete, and ties you into to a long-term relationship based on dependency.&nbsp; If the respect and admiration is mutual and remains so that’s great, but you should be able to fly ultimately without needing&nbsp;your vendor to be the wind beneath your wings.</li> <li><strong>Good ‘cultural fit’</strong>&nbsp;– this is vague, but nevertheless quite important:&nbsp; what I mean is you should match up the partner’s profile with your own as far as possible<br> You won’t necessarily stand to gain by engaging a high-end consultancy that specializes in enterprise-scale SharePoint services for the top end of town, no matter how glossy their brochures and how impressive their resume and client list, if you’re a relatively small business that needs to extract every iota of value from your limited budget.&nbsp; If you don’t have a lot of experience with vendor management, don’t engage an established and sophisticated provider who overwhelms you with legal contracts, account management and other ‘overheads’. If you have a tiny in-house IT team, ensure your vendor of choice doesn’t assume a large team will be at their disposal to direct on deployment activities. Don’t engage a random bunch of SharePoint contractors and developers if you have no-one capable of herding those cats.</li> <li><strong>Excellent design, support and maintenance documentation&nbsp;</strong>– comprehensive, clear and actionable<br> This is extremely important to&nbsp;<em>me</em>, but I’m willing to accept the opinion might be a bit niche. However, for what it’s worth … I was once burned by vendors who handed over system documentation of such extraordinarily poor quality that it was&nbsp;impossible for the in-house team to use it for effective management of our SharePoint environment, or meet minimum support and DR documentation requirements.&nbsp; We had to re-write most of it, which was no mean feat.&nbsp; On the bright side, we all learned a lot about SharePoint in the process. Conversely, it was a cost that hadn’t been anticipated and it left a bad taste. As a result, I have inordinate respect for partners who provide robust documentation (see also point 3).</li></ol></div> <h4 class = ' align-left font-alt uppercase black ui-sortable-handle'>The right operational resources </h4> <div class = ' ui-sortable-handle'><p>SharePoint, once in place, does not just look after itself. &nbsp;This is abundantly apparent from even a cursory glance at the myriad advisory books and blogs available. However many organisations still seem to believe the opposite, and accordingly they&nbsp;seriously under-resource operational management of their expensive SharePoint solutions post-launch. Then wonder why they start to take on water and sink before their eyes.</p><p>After deployment, the SharePoint infrastructure and application environment will need to be well maintained and managed. Presumably installing and documenting an effective monitoring and maintenance regime was established as part of the deployment project.&nbsp; (If not, here’s a Resource Center to help with that critical task:&nbsp;<a href="http://technet.microsoft.com/en-us/sharepoint/hh127032.aspx">http://technet.microsoft.com/en-us/sharepoint/hh127032.aspx</a>)</p><p>Many SharePoint environments can grow beyond the capacity or capability of the in-house IT support resources.&nbsp; Consider outsourcing SharePoint support and maintenance to an external provider who specialises in this&nbsp;(and if you do, put a robust SLA in place). &nbsp;&nbsp;That said, do try to build in-house Help Desk knowledge, even if you outsource formal Level 2 and/or 3 Support &amp; Maintenance, so that end users have a local, responsive first line of support.</p><p><strong>But success over time with SharePoint is not just, not even mostly, about technical operations.</strong>&nbsp; If you concentrate all your operational resourcing effort and budget on IT, you’re still cruising for a bruising.&nbsp; Well-rounded governance is another, very important factor (see&nbsp;<a href="https://chamonixvue.wordpress.com/2011/07/05/success-with-sharepoint-8/">tip #8</a>), but it’s not the full answer either.</p><p>From my experience many – dare I say most? – end user questions and operational concerns will be purely business related and have zero technical substance.&nbsp; In the absence of any alternative however, these are likely to hit the Help Desk and technical staff may find themselves acting, probably reluctantly and ineffectively, as&nbsp;<em>de facto</em>&nbsp;business analysts and advisors.</p></div> <h4 class = ' align-left font-alt uppercase black ui-sortable-handle'>When, how and what? </h4> <div class = ' ui-sortable-handle'><p>At the most basic level, questions (and, if you’re not careful, frustrations) will proliferate about how and when to use the new SharePoint functionality properly.&nbsp; For example, even ‘simple’ things like check in and check out on document libraries confuse&nbsp;<em>many</em>&nbsp;people. How will you ensure that people know what features are available in SharePoint, and when and how to use the right one to meet a specific business need – how, for instance, do you prevent end users from creating a wiki if their problem would be much better resolved by a custom list?</p></div> <h4 class = ' align-left font-alt uppercase black ui-sortable-handle'>Why? </h4> <div class = ' ui-sortable-handle'><p>Beyond – or perhaps it’s&nbsp;<em>before</em>&nbsp;– the when, what and how questions, it’s actually the&nbsp;<strong>why</strong>&nbsp;questions that require the most time and energy of operational resources, but are at the heart of SharePoint success.</p><p>Why should I use metadata instead of a folder hierarchy in my Site?&nbsp; Why should I bother tagging content? &nbsp;Why should I use a SharePoint document library instead of a file server?&nbsp; Why should I transfer data from Excel to a SharePoint list? Why should I use a Team Site when email appears much easier?&nbsp; Why should I upload a photo or write a profile statement about myself?</p></div> <h4 class = ' align-left font-alt uppercase black ui-sortable-handle'>Who? </h4> <div class = ' ui-sortable-handle'><p>So who do you think will answer these what, when, how and why SharePoint questions? &nbsp;&nbsp;Not IT, in all probability.&nbsp; Common, frequently recurring questions are relatively easy to deal with (FAQs, short videos, cheat sheet). &nbsp;&nbsp;But who will address the unique, often highly specific issues and needs that arise department by department, team by team, group by group. Who will analyse a given functional unit’s business processes and advise them on how to improve these with online SharePoint workflows or build a process wiki?</p><p>The Change Management plan might include something about identifying and building&nbsp;<strong>champions</strong>&nbsp;or&nbsp;<strong>power users</strong>, distributed&nbsp;<strong>content stewards and publishers</strong>, or&nbsp;<strong>departmental owners</strong>&nbsp;of SharePoint Team Sites.&nbsp; These are all valid and important operational roles. But who supports, trains, advises, encourages, guides and wrangles these disparate groups with their disparate needs and concerns?</p><p>Enter the SharePoint Business Manager / Evangelist / User Adoption Specialist / Translator / Steward / Coach.*</p><p>Appointing a dedicated,<strong>&nbsp;SharePoint-savvy Business Manager</strong>&nbsp;for your solution is therefore strongly recommended, as I believe this is an essential ingredient of any recipe for success with SharePoint. Whether your solution is an intranet, a collaboration environment, a website, DMS, BI platform or other, this is one piece of advice I can’t stress highly enough.</p><p>Depending on the size and scale of your implementation, you may need to consider more than one person, or more than one business-facing role. For example, a dedicated&nbsp;<strong>Collaboration Manager</strong>&nbsp;who exclusively encourages and supports Site Owners and users of Team Sites for collaboration. A SharePoint&nbsp;<strong>Training Manager</strong>&nbsp;may also be advisable. Many businesses make the mistake of thinking one individual will be able to cover off everything, but while there are a few SharePoint superhumans about, often a team is necessary. &nbsp;Not necessarily big on numbers, but big on talent, skills and enthusiasm.</p><p>I’ll just circle back to IT to complete the list. While business-focused SharePoint Managers will know a great deal about the platform, they’re not technical. Therefore a&nbsp;<strong>Solution Manager</strong>&nbsp;with deep SharePoint technical knowledge and experience is another vital role for the long term. These two key roles need to work in partnership to ensure SharePoint is well maintained and supported, but also optimised over time in line with IT and business needs.</p></div> <h4 class = ' align-left font-alt uppercase black ui-sortable-handle'>Other resources on resourcing Sharepoint </h4> <div class = ' ui-sortable-handle'><p><strong>Veronique Palmer</strong>’s JDs for various roles:&nbsp;<a href="http://www.letscollaborate.co.za/Resource-Centre/SitePages/JobDescriptionsIndex.aspx">http://www.letscollaborate.co.za/Resource-Centre/SitePages/JobDescriptionsIndex.aspx</a></p><p><strong>Veronique</strong>&nbsp;again, posing the question “Do you need a SharePoint Whisperer?”&nbsp;<a href="http://veroniquepalmer.wordpress.com/2011/05/24/do-you-need-a-sharepoint-whisperer/">http://veroniquepalmer.wordpress.com/2011/05/24/do-you-need-a-sharepoint-whisperer/</a></p><p>And again, on “How NOT to advertise your SharePoint position”:&nbsp;<a href="http://veroniquepalmer.wordpress.com/2011/04/27/how-not-to-advertise-your-sharepoint-position/">http://veroniquepalmer.wordpress.com/2011/04/27/how-not-to-advertise-your-sharepoint-position/</a></p><p>And the book&nbsp;<strong><a href="http://www.amazon.com/Essential-SharePoint-2010-Governance-Addison-Wesley/dp/0321700759/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1301855908&amp;sr=8-1">Essential SharePoint 2010: Overview, Governance and Planning</a></strong>&nbsp;by Scott Jamison, Susan Hanley and Mauro Cardarelli has a useful section on Roles and Responsibilities for SharePoint operations.</p></div> <h3 class = ' align-left font-alt uppercase black ui-sortable-handle'>Summing up </h3> <div class = ' ui-sortable-handle'><ul class = "list"> <li>SharePoint implementation/upgrade project teams require a different mix of roles and responsibilities than teams involved in the ongoing management of SharePoint</li> <li>Projects benefit from the complementary skill and experience of internal staff and external SharePoint implementation partners</li> <li>Business&nbsp;<em>and&nbsp;</em>technical roles should be dedicated to SharePoint’s ongoing management for greatest operational effectiveness</li></ul><p>* UPDATE</p><p>The SharePoint Contender has a fun, and insightful, three-part musing on this rare beast that is this SharePoint-savvy Business Manager here:&nbsp;<a href="http://sharepointcontender.wordpress.com/2009/12/30/sharepoint-identity-crisis/">http://sharepointcontender.wordpress.com/2009/12/30/sharepoint-identity-crisis/</a></p></div> </div> Mon, 25 Jun 2018 15:41:00 +0000 Chamonix Consulting 143 at https://chamonix.com.au TOP 10 TIPS FOR SUCCESS WITH SHAREPOINT #8 https://chamonix.com.au/blog/article-top10sharepoint8 <span>TOP 10 TIPS FOR SUCCESS WITH SHAREPOINT #8</span> <span><span>Chamonix Consulting</span></span> <span>Tue, 06/26/2018 - 01:10</span> <div><p>Goodness gracious, it's governance!</p> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/sp8.jpg?itok=TkAn7x_3" width="1140" height="642" alt="sharepoint" /> </li></ul> <div><div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'><p><em>“Enough already with governance!”</em>&nbsp; I hear you groan.</p><p>Yes, I do realise this has been one of the hot topics of 2010 (the year and the version of SharePoint).<br>Yes, I know it’s just about been done to death in the blogosphere and conferences, as well as books, whitepapers, resource centers, etc.<br>But no, a Top 10 series on success with SharePoint simply cannot omit it, so here we go…</p><p>Why is governing SharePoint still so difficult in practice? Why is good advice proliferating, but apparently without giving rise to equally abundant excellent&nbsp;<em>working</em>&nbsp;examples in the real world?</p><p>Why am I still hearing businesses regularly describe deep SharePoint pain that can be directly attributed to poor governance?</p></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle' style = 'margin-top: 20px; margin-bottom: 20px;'><hr class="mt-0 mb-0"></div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>Questionable Thinking 1: We’re too small / mature / |LS|choose your own adjective|RS| to need governance </h3> <p>It’s your choice. But even small organisations are quite capable of producing terabytes of data and hundreds, if not thousands, of SharePoint sites in an astonishingly short time. Large and mature companies still seem to end up with thousands of pages on their websites or intranets that haven’t been reviewed in years.&nbsp; In your business, is SharePoint trying to coexist with other enterprise systems that do some of the same things?&nbsp; Then there’s a very real risk of the promise that “everything will be so well structured and maintained, and so easy to find once we get SharePoint” being quickly eroded, no matter what your profile.&nbsp; Fights break out over matters big and small – such as who simply&nbsp;<em>must not&nbsp;</em>have access to SharePoint Designer, or who can have it but what they&nbsp;<em>must not do</em>&nbsp;once they get hold of it.&nbsp; Are you sure you don’t need governance?</p> <h4 class = ' align-left font-alt uppercase black'>Think again: </h4> <p>I came across the following on a blog the other day. I’ve augmented it only a little, and it’s as good a list as any to prompt thinking about if and when governance is needed for your SharePoint deployment:</p><blockquote><p>In my SharePoint governance classes I often say that you should not release a SharePoint feature until you have a plan for it…</p><ul class = "list"> <li>is governance required (is there risk through misuse and if so, what is the potential impact)?</li> <li>who will own, support and maintain it?</li> <li>how will you inform and train users?</li> <li>what’s the impact on performance (both business and systems)?</li></ul></blockquote><p>&nbsp;</p> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>Questionable Thinking 2: Our Project Governance was faultless so we’ll just carry on with that </h3> <p>Strong project governance is undeniably important while you’re deploying SharePoint (see Tip #2). But is the Steering Committee – being typically comprised of senior stakeholders and decision makers – the right group to take SharePoint forward into operational mode?</p> <h4 class = ' align-left font-alt uppercase black'>Think again: </h4> <p>After the champagne and launch celebrations, the long and sometimes hard slog of governing SharePoint becomes vitally important – keeping the environment’s use and development aligned to the original strategic need, ensuring the organisation continues to gain value from the investment, that SharePoint is maintained robustly and managed well for all constituents, and the platform is further enhanced over time in response to business needs.&nbsp; While senior management obviously has an important role to play in achieving these objectives, a collaborative governance group or forum should be formed, comprising representatives from across the business, ideally at all levels of the hierarchy, for ongoing governance to be effective.</p> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>Questionable Thinking 3: We have a comprehensive written Governance Plan, so we’re sorted </h3> <p>It’s easy enough to write a plan.&nbsp; There are lots of examples just a search away, and a couple of them are even quite good.&nbsp; Some consultants make a good living from SharePoint governance; write a plan, hand over a document, walk away and don’t look.&nbsp;Job done?</p> <h4 class = ' align-left font-alt uppercase black'>Think again: </h4> <p>I do believe a written Governance Plan is essential – as long as it’s not a templated exercise but is carefully developed to suit the organisation’s objectives, culture, resources, staff and customers.&nbsp; Joel&nbsp;<em>Mr</em>&nbsp;<em>SharePoint</em>&nbsp;Olsen has also rightly noted that a SharePoint governance plan should be a ‘living’ document and he should know, having developed the original sample SharePoint governance plan for Microsoft back in the days of 2007, and written extensively on the subject ever since.&nbsp; Like some of my peers, I advocate using a SharePoint wiki to capture the governance documentation.&nbsp; I’ve done this myself, and found it’s an easy and effective way of structuring and presenting the content, it’s reasonably straightforward for multiple stakeholders to maintain, and it’s very easy to link to specific sections of the plan from other sites or pages when it’s relevant to do so – for example, from a New Site Request form you might link to the Ts &amp; Cs that Site Owners are expected to adhere to.</p><p>But no matter how great your written plan is, it’s just the beginning and it’s not much more than that.&nbsp; How many people read plans?&nbsp; And how many of those actually adhere to them?&nbsp; The hard work is taking the plan and turning it into operational reality. And ensuring it keeps working over time.&nbsp; That needs clear ownership, accountability and commitment from senior management.&nbsp; It requires active cooperation between IT and business stakeholders.&nbsp;The right roles need to be accountable for appropriate facets of the governance framework.&nbsp;Understanding, agreement and compliance won’t happen because you’ve written something down.</p> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>Questionable Thinking 4: Isn’t governance IT’s concern? </h3> <p>Well, no.&nbsp; In the SharePoint 2007 days, there was a plethora of blog posts about governance that were almost exclusively technical.&nbsp; Paragraphs and paragraphs were written about quota management, and content database sizes, monitoring plans and SSP delegation rules, and blah blah blah.&nbsp; I don’t mean to be dismissive – it’s an important fact that there are many technical aspects to governing SharePoint well that demand careful attention.&nbsp; I’m just saying that a platform like SharePoint, which seeks to ‘empower’ the information worker – that is, give human beings tools to work in new and better ways – involves&nbsp;<em>much more</em>&nbsp;than technical assurance. If your governance plan focuses exclusively on managing the technology layer it won’t contribute greatly to success with SharePoint.</p> <h4 class = ' align-left font-alt uppercase black'>Think again: </h4> <p>These days, most of us have moved on from that somewhat limited view, and understand that SharePoint governance has a significant&nbsp;<em>business</em>&nbsp;dimension.&nbsp; When SharePoint governance focuses on the users and aligns with business value and services it is more likely to be effective. And even more so, I suspect, when integrated into a holistic business governance framework, rather than tackled as a standalone.&nbsp; Does anyone have governance plans for Microsoft Exchange or Office? &nbsp; So while just doing “SharePoint governance” is undoubtedly better than doing nothing, we should be thinking about why SharePoint has been deployed for the business and how it fits into that organisation’s collaboration, information management or web content management ecosystem. Then we should be framing and contextualizing its governance accordingly.</p> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>Questionable Thinking 5: Governance = rules </h3> <p>Here are a few typical rules that you’ll find in many a SharePoint governance plan:</p><blockquote><p>“We enforce formal requests for all new Sites, Wikis and Blogs. A manager’s authorisation is mandatory, as is a business justification.”<br>“Only IT personnel can have Site Collection Administration access.”<br>“No staff will be granted SharePoint Designer access unless they have been fully trained and certified.”<br>“Site Owners are granted full control permissions by exception only. They must sign an agreement acknowledging they take full responsibility and exercise the permission level at their own risk.”<br>“Site Owners are not permitted to apply themes to their sites.”<br>“Private My Sites will not made available to staff.”<br>“Employees may not edit their own profiles. Any request for changes to profile information must be sent&nbsp; to HR.”<br>“All comments on the CEO’s internal blog will be moderated, and commenters will be identified by name.”<br>“Requests to recover or restore deleted or corrupted sites will be charged back to the requestor’s cost centre.”</p></blockquote><br><p>Each and all of these may be entirely appropriate in a given organisation. Then again, they may not. In some business contexts or for some staff too many rules with an admonitory tone and restrictive intent may nip interest in SharePoint in the bud. Certainly there are enough dire warnings and real-world case studies of SharePoint environments that have devolved into a terrible mess to frighten any administrator into immediate lock-down mode. I’ve worked on some such environments myself and written my share of restrictive rules too. Even so, it’s very important to weigh up the costs and benefits of each rule before you rush to command and control at the outset. More sticks than carrots will engender certain behaviours, so be sure your legislation is producing the behaviours you really do want to manifest.</p> <h4 class = ' align-left font-alt uppercase black'>Think again: </h4> <p>Written and legislated well, rules do help all users in the same way effective government and social policies create agreeable societies in which citizens are able to pursue their own goals while contributing to the collective benefit of society. The police (dare I call them IT?) help ensure a lawful, ordered space for citizens (SharePoint users) to participate effectively.&nbsp; But law and order shouldn’t be allowed to tip over into a regime. Citizens need some rules sure, but balanced with freedom and power to own their workspace and contribute meaningfully, or they’ll find ways – legal and illegal, explicit and subversive – to rebel. &nbsp; Like sticking with C: drives and flash drives and email for instance.</p><p>I’ve probably stretched the societal metaphor about as far as it will go, but the point is that rules are important for SharePoint success when there are “just enough” and they’re somewhat in the background. Rules are never the heart and soul of an effective SharePoint community and they shouldn’t be too much in the foreground, too prescriptive or too numerous, or users will be frustrated, discouraged or alienated.</p> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>Questionable Thinking 6: Rules don’t work for us: our approach to governance is all about our vision </h3> <p>A governance framework that aligns to your vision for SharePoint is no bad thing.&nbsp; And ideally the flip side of the coin will involve measuring how you’re tracking in achieving this vision and making adjustments as necessary.&nbsp;&nbsp;<em>Steering&nbsp;</em>with governance, not&nbsp;<em>commanding</em>.&nbsp; But let’s acknowledge that vision statements and visionary governance are unlikely to direct individual behaviour, don’t clarify who does what, probably won’t encourage uptake, and almost never contribute to strong compliance in and of themselves.</p><p>&nbsp;</p> <h4 class = ' align-left font-alt uppercase black'>Think again: </h4> <p>When you set out to establish a governance framework for your SharePoint environment, be clear on its fundamental intent.&nbsp; Governance, like it or not, is more about rules and responsibilities to support the common good than it is about striving for a shared vision.&nbsp; Governance is not user adoption and it doesn’t explicitly support and assist individual staff in their use of SharePoint (even as it assists the organisation as a whole). &nbsp; That’s the job of Change Management (see Tip # 7).&nbsp; So align governance with the business vision certainly, but don’t try to make governance become the catch-all for anything and everything to do with making SharePoint work.</p> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>What makes good governance for Sharepoint? </h3> <p>A successful, functioning governance framework is likely to be:</p><ul class = "list"> <li>Actively and regularly ‘steered’ by a formal, collaborative group comprising broad stakeholder representation, inclusive of IT and the business</li> <li>Documented<br> <em>But not to the nth&nbsp;degree</em></li> <li>Simple, based around broad guiding principles suited to the organizational profile, clear on roles and accountability, and light on low-level prescriptive rules<br> <em>But ideally it will clarify the typically problematic ‘grey areas’ re IT and business ownership of SharePoint – e.g. who makes the call on SharePoint development and customisation requests?</em></li> <li>Inclusive and focused as much (if not more) on the business as on IT and the technology</li> <li>Flexible and responsive to changing business needs<br> <em>E.g. If a rigid new site request process with mandatory approvals and justifications is keeping users away in droves, rethink it</em></li> <li>Ideally, part of wider, holistic business governance and aligned with relevant functions and services</li></ul> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>Need help? </h3> <p>If you’re in Australia,&nbsp;<a href="http://chamonix.com.au/contact">contact Chamonix</a>&nbsp;&nbsp; Otherwise, there are some excellent blogs and articles on governance in SharePoint and in general, so as is my wont&nbsp; I’m going to list my favourites for the benefit of anyone who wants or needs to deep dive into this topic:</p><ul class = "list"> <li><strong>Jim Adcock</strong>&nbsp;has started what promises to be an in-depth series here:&nbsp;<a href="https://www.nothingbutsharepoint.com/sites/eusp/Pages/SharePoint-Governance-Why.aspx">https://www.nothingbutsharepoint.com/sites/eusp/Pages/SharePoint-Governance-Why.aspx</a></li> <li><strong>SharePoint Geoff</strong>&nbsp;has a good post here:&nbsp;<a href="http://www.sharepointgeoff.com/governance/">http://www.sharepointgeoff.com/governance/</a></li> <li><strong>Veronique Palmer</strong>&nbsp;generously makes some document templates available from this post with her usual welcome focus on business use of SharePoint:&nbsp;<a href="http://veroniquepalmer.wordpress.com/2010/09/26/Sharepoint-business-governance-plans/">http://veroniquepalmer.wordpress.com/2010/09/26/Sharepoint-business-governance-plans/</a><br> She even has a sample SharePoint Governance Plan as a Wiki:&nbsp;<a href="http://www.letscollaborate.co.za/Resource-Centre/SitePages/GovernancePlanWiki.aspx">http://www.letscollaborate.co.za/Resource-Centre/SitePages/GovernancePlanWiki.aspx</a></li> <li>Not sure how long this link will be available, but you can download an excellent free sample chapter&nbsp;<a href="http://cloud.snappages.com/b8898dc2c08e137d03449de65b9e82e108c15658/chapter04planningforgovernance.pdf">http://cloud.snappages.com/b8898dc2c08e137d03449de65b9e82e108c15658/chapter04planningforgovernance.pdf</a>&nbsp; from the book by Susan Hanley&nbsp;<em>et al,</em>&nbsp;<a href="http://www.amazon.com/Essential-SharePoint-2010-Governance-Addison-Wesley/dp/0321700759/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1301855908&amp;sr=8-1">Essential SharePoint 2010: Overview, Governance and Planning</a>&nbsp;&nbsp; Thanks to the authors for sharing this excellent starter –&nbsp;if you like it, why not support them and buy the book (I did recently, and I recommend it)</li> <li><strong>Michael Sampson</strong>&nbsp;maintains a Resource Centre specifically on governing collaboration here:&nbsp;<a href="http://www.michaelsampson.net/governingcollaborationcenter.html">http://www.michaelsampson.net/governingcollaborationcenter.html</a></li> <li>A great blog post on SharePoint Governance 3.0 from&nbsp;<strong>Ant Clay</strong>:&nbsp;<a href="http://www.21apps.com/governance/sharepoint-governance-3-0/">http://www.21apps.com/governance/sharepoint-governance-3-0/</a>&nbsp;and the secret to understanding governance brought to you by, you guessed it,&nbsp;<strong>Paul Culmsee</strong>:&nbsp;<a href="http://www.cleverworkarounds.com/2009/07/03/the-secret-to-understanding-governance/">http://www.cleverworkarounds.com/2009/07/03/the-secret-to-understanding-governance/</a></li> <li><strong>Step Two Designs</strong>&nbsp;have some great posts on governance, in particular&nbsp;<em>Creating an Intranet Governance Guide</em>&nbsp;which shares some sample table of contents – always useful to get you started on a plan of your own:&nbsp;<a href="http://www.steptwo.com.au/papers/kmc_intranetgovernance/index.html">http://www.steptwo.com.au/papers/kmc_intranetgovernance/index.html</a></li> <li>The&nbsp;<em>Governance and Strategy</em>&nbsp;section of the&nbsp;<strong>Intranet Management Handbook</strong>&nbsp;by Martin White:&nbsp;<a href="http://www.intranetfocus.com/imhandbook">http://www.intranetfocus.com/imhandbook</a>&nbsp; (see Michael Sampson’s detailed review here:&nbsp;<a href="http://currents.michaelsampson.net/2011/02/white-intranets-part4.html">http://currents.michaelsampson.net/2011/02/white-intranets-part4.html</a>)</li> <li>And specifically for governance of websites, try Shane Diffily’s&nbsp;<strong>Website Management Handbook</strong>. From this page&nbsp;<a href="http://www.diffily.com/book/index.htm">http://www.diffily.com/book/index.htm</a>&nbsp;you can download a free website governance diagram</li></ul> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> <div class = ' ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle ui-sortable-handle'> <h3 class = ' align-left font-alt uppercase black'>Summing Up </h3> <ul class = "list"> <li>Governance is about as exciting as housework, but just as necessary for an enjoyable, orderly environment where everyone can work optimally</li> <li>Don’t govern SharePoint and you can probably expect content anarchy or what some call the ‘wild west’.&nbsp; But govern it too restrictively and you can expect user frustration, disenchantment or even complete avoidance</li> <li>Ensure your governance framework is actively steered, documented, simple, inclusive and collaborative, flexible and aligned to the business</li></ul> <div style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> </div> Mon, 25 Jun 2018 15:40:00 +0000 Chamonix Consulting 145 at https://chamonix.com.au TOP 10 TIPS FOR SUCCESS WITH SHAREPOINT #7 https://chamonix.com.au/blog/article-top10sharepoint7 <span>TOP 10 TIPS FOR SUCCESS WITH SHAREPOINT #7</span> <span><span>Chamonix Consulting</span></span> <span>Tue, 06/26/2018 - 01:09</span> <div><p>The Soft Stuff is the Hard Stuff (But it’s the Good Stuff) -&nbsp;Of this series of 10 posts I’ve planned,&nbsp;<em>this</em>&nbsp;is the one tip I’ve been waiting to write up (along with tip # 6, another fixation of mine). I’m incredibly passionate about this topic, so hang on for the diatribe, I mean ride.</p> </div> <ul class="clearlist content-slider mb-40"><li> <img src="/sites/default/files/styles/blog_1140x642_/public/2018-08/sp7.jpg?itok=oW3oB3_s" width="1140" height="642" alt="sharepoint" /> </li></ul> <div><div class = ' ui-sortable-handle'><p><strong>Underestimate &nbsp;or under-resource Change Management at your peril</strong>.&nbsp; If that&nbsp;sounds hysterical or intimidating I apologise,&nbsp;but in my view and my experience this is essential for SharePoint success, and &nbsp;this tip is probably “the one ring to rule them all.”</p><p>Now I&nbsp;<em>don’t</em>&nbsp;mean the ITSM&nbsp;or ITIL world of Change &nbsp;Management – standardization, infrastructure and configuration control, incident management and Change Advisory Boards and all that.&nbsp; I mean the messy and ‘soft’ human stuff that’s about working with people to get them to stop doing things the “way we’ve always done it” and start doing things differently on SharePoint, adopting new processes, interacting with one another online via other means than email, creating and sharing content in new formats, etc.</p><p>Important though the infrastructure and solution architecture are, success (or failure) in enterprise SharePoint deployments&nbsp;<strong><em>always</em></strong>&nbsp;comes down to&nbsp;<strong>user adoption&nbsp;</strong>(or lack thereof).<strong>&nbsp;&nbsp;&nbsp;</strong>Anything’s possible I guess, so perhaps I shouldn’t be so free with the italics and bold face … but I’ve never heard of or read a case study or encountered a real world environment where SharePoint failed literally&nbsp;<em>because</em>&nbsp;of technical issues –backups weren’t enabled, patches and Service Packs weren’t up to date, IT ran out of storage space, there was no Staging server, solutions were deployed into Production without proper testing, etc.&nbsp; Conversely, I’ve heard many stories and&nbsp;conference presentations first-hand and read many more case studies of implementations that failed&nbsp;<em>because</em>&nbsp;employees simply didn’t understand or could not use SharePoint; or they used it badly on their own, made a mess of it, learned to loathe it and then stopped using it.&nbsp; I’ve even been on a couple of ‘recovery’ missions in such circumstances.&nbsp; Heard &nbsp;any recent anecdotes about the SharePoint deployment that’s an expensive file &nbsp;server?&nbsp; Yes, me too…</p><p>So I advise<strong>&nbsp;never</strong>&nbsp;over-emphasize or resource the technology component or IT requirements at the expense of:</p><blockquote><ul class = "list"></ul></blockquote><ul class = "list"> <li>Business engagement and stakeholder management – before, during and after the project</li> <li>User adoption strategy and tactics – immediately post-launch and ongoing</li> <li>Communications</li> <li>End user training – formal and informal</li> <li>End user support</li></ul></div> <div class = ' ui-sortable-handle' style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h3 class = ' ui-sortable-handle align-left font-alt uppercase black'>Build Your Own SharePoint Field of Dreams and They Will Come… </h3> <div class = ' ui-sortable-handle'><p>This kind of thinking still occurs, and organisations still deploy SharePoint accordingly and are surprised when they don’t come and the field remains empty.&nbsp; Or sometime&nbsp;‘they’ do wander out of the corn rows and stumble into SharePoint, it’s true. But left to their own devices, with no real idea of the game they’re supposed to play, too many still end up ultimately “hating” SharePoint.&nbsp; Them’s strong words and also a real shame because it doesn’t have to be that way.</p><p>Despite the square miles of stuff written on the importance of user adoption and change management strategies and tactics, insufficiency or lack thereof remains a common root cause of failure with SharePoint. &nbsp;(Welcome to my own square metre contribution.)&nbsp;<strong>&nbsp;&nbsp;</strong>So why does this happen?</p><ul class = "list"> <li>Perhaps because SharePoint is usually owned or delivered by IT and managed by techies, and SharePoint Architects can be a little bit self-important about technical minutiae and indifferent to actual users&nbsp;&nbsp; Sorry, that’s a bit below the belt; it’s not fair to keep blaming the techies when many business administrators are equally guilty of “build it and they’ll come” magical thinking.</li> <li>Maybe it’s because Change Management programs demand not insignificant resources and effort, for outcomes aren’t usually particularly immediate or tangible (I didn’t say they’re not achievable and measurable though). &nbsp;&nbsp;Even if&nbsp;<em>you</em>&nbsp;know it’s important, you might find it hard to get appropriate buy-in or budget from management.</li> <li>Sometimes a great Change Management effort&nbsp;<em>during</em>&nbsp;a SharePoint project doesn’t continue and develop far beyond the launch, so it withers on the vine.</li></ul><p>Furthermore, despite the marketing hype you may have encountered, SharePoint is&nbsp;<em>not</em>&nbsp;easy for the average user (particularly if you haven’t paid due attention to any of the&nbsp;<a href="http://chamonix.com.au/success-with-sharepoint-1">success factors described in previous tips in this series</a>). &nbsp;Nope, not even with the new ribbon.&nbsp; Without explicit and deliberate Change Management support, SharePoint:</p><ul class = "list"> <li>Doesn’t make Business Analysts of your information workers overnight, and have them transforming their Excel files into lists and deploying Content Query Web Parts on their Enterprise Wikis for richly informative and interactive content.</li> <li>Won’t turn Project Office staff into black-belt information managers – consider yourself&nbsp;<em>very&nbsp;</em>lucky if they willingly transfer their Risk Registers and Issue Logs into online lists without you asking them, showing them, reminding them of the benefits, and showing them all over again, before doing it for them.</li> <li>Is unlikely to encourage HR or IT or Finance to convert their 50 page procedure documents into FAQ lists, web pages or wiki sites.</li></ul></div> <div class = ' ui-sortable-handle' style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h3 class = ' ui-sortable-handle align-left font-alt uppercase black'>Hard stuff </h3> <div class = ' ui-sortable-handle'><p>Does any of the following sound familiar?</p><ul class = "list"> <li>People complaining loudly about Inbox-induced madness, who simultaneously seem willfully addicted to email and insist “if it’s not emailed to me, forget it!”</li> <li>Frequent complaints that no-one can find anything</li> <li>Employees who don’t really understand the difference between ‘draft’ and ‘published’ content, and are never sure if something’s final and authorized for use or still a work in progress</li> <li>Staff who have little notion of&nbsp;how to manage document versioning and all just seem to do their own thing with naming and numbering conventions</li> <li>Rampant folder and file construction, duplicated content, and hoarding of files in personal C: drives and mailboxes</li> <li>Managers or content administrators who never seem to action their ‘awaiting your approval’ notifications</li></ul><p><em>Are you about to deploy SharePoint?</em></p><p><em>Or do you already have SharePoint in place?</em></p><p>Either way, I wouldn’t be surprised if you’re struggling with the same issues list!</p><p>These problems are the norm, not the exception, everywhere I’ve worked because people are by and large deeply change-averse creatures – whether lazy, fearful or selfish, or just content with the status quo, unimaginative, sceptical, busy, distracted or prioritizing something else. Persuading us to modify well-entrenched habits no matter how bad is really hard, no matter how good how the technology is and how great the outcome might be.</p><p>Way back in 2008 I won a Step Two Designs Intranet Innovation Award for Team Sites in a Box (see:&nbsp;<a href="http://www.steptwo.com.au/columntwo/best-practice-approach-to-sharepoint-team-spaces/">http://www.steptwo.com.au/columntwo/best-practice-approach-to-sharepoint-team-spaces/</a>&nbsp;for details.) &nbsp; Sure it’s no longer innovative, but nearly 3 years later it’s still a highly relevant design for enterprise online collaboration because it’s largely about the human element, not the application. The fact we now have a completely new and quite different version of SharePoint is largely irrelevant.</p></div> <div class = ' ui-sortable-handle' style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h3 class = ' ui-sortable-handle align-left font-alt uppercase black'>Soft stuff </h3> <div class = ' ui-sortable-handle'><p>‘Doing SharePoint’ ain’t over when the Project Manager sings and the project team packs up and moves on. In fact, this is the time for concentrated user adoption effort – all those ‘soft’ human things like engagement, communicating the WIIFM (What’s In It For Me?) and for all of us, and training, support and more training are vital.</p><p>You wouldn’t expect a team to hit the major league without a coach, would you?</p></div> <div class = ' ui-sortable-handle' style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h3 class = ' ui-sortable-handle align-left font-alt uppercase black'>So how do you do it? </h3> <div class = ' ui-sortable-handle'><p>Like almost everything I do with SharePoint, I target my change and user adoption&nbsp;strategies and plans to the needs and culture of the organization I’m working with.</p><p>If you’ve largely adhered to the&nbsp;<a href="https://chamonixvue.wordpress.com/success-with-sharepoint/">preceding tips for success with SharePoint</a>, you should find it easier to deliver an effective Change Management strategy and plan. You will know the vision, purpose and scope for SharePoint in your organization, and can readily align your Change strategy with those. You will understand your users&nbsp;and their requirements, and how SharePoint best addresses them. &nbsp;&nbsp;Your structural and visual design will have been developed with the input of your users, and will help them understand, navigate and enjoy SharePoint.</p><p>If not, don’t despair.&nbsp; You’re spoiled for choice with many great resources and impressive bloggers in this field. Here are a few of my favourites:</p><ul class = "list"> <li><strong>Veronique Palmer</strong>, newly minted MVP, of Let’s Collaborate fame – a very accessible writer and strongly user-focused:&nbsp;<a href="http://www.letscollaborate.co.za/SitePages/Home.aspx">http://www.letscollaborate.co.za/SitePages/Home.aspx</a></li> <li><strong>Michael Sampson</strong>&nbsp;– a thought leader on making collaboration work. I recommend his stuff generally, but particularly his books, his User Adoption Resource Center:&nbsp;<a href="http://www.michaelsampson.net/useradoptioncenter.html">http://www.michaelsampson.net/useradoptioncenter.html</a>&nbsp;&nbsp;and his blog:&nbsp;<a href="http://currents.michaelsampson.net/">http://currents.michaelsampson.net/</a></li> <li><strong>Dux Raymond Sy</strong>:&nbsp;<a href="http://sp.meetdux.com/default.aspx">http://sp.meetdux.com/default.aspx</a></li> <li><strong>Richard Harbridge</strong>:&nbsp;<a href="http://www.rharbridge.com/">http://www.rharbridge.com/</a></li> <li><strong>End User SharePoint&nbsp;</strong>on Nothing But SharePoint:&nbsp;<a href="https://www.nothingbutsharepoint.com/sites/eusp/Pages/default.aspx">https://www.nothingbutsharepoint.com/sites/eusp/Pages/default.aspx</a></li> <li>Microsoft’s&nbsp;<strong><em>I Use SharePoint</em></strong>&nbsp;site is a recent entry to the field:&nbsp;<a href="http://sharepoint.microsoft.com/iusesharepoint/landing.aspx">http://sharepoint.microsoft.com/iusesharepoint/landing.aspx</a>&nbsp;&nbsp;It’s fantastic to see MS making a laudable attempt to address the soft stuff – for example, the adoption best practices guide:&nbsp;&nbsp;<a href="http://download.microsoft.com/download/D/C/7/DC7AC167-03BE-4CF7-9F2F-2B9E50167DCE/SharePoint%202010%20Adoption%20Best%20Practices%20WhitePaper.pdf">http://download.microsoft.com/download/D/C/7/DC7AC167-03BE-4CF7-9F2F-2B9E50167DCE/SharePoint%202010%20Adoption%20Best%20Practices%20WhitePaper.pdf</a></li> <li><strong><em>Get the Point Blog</em></strong>&nbsp;from the Microsoft SharePoint End User Content Team:&nbsp;<a href="http://sharepoint.microsoft.com/Blogs/GetThePoint/default.aspx">http://sharepoint.microsoft.com/Blogs/GetThePoint/default.aspx</a></li> <li><strong>Change Management Toolbook</strong>:&nbsp;<a href="http://www.change-management-toolbook.com/course/category.php?id=9">http://www.change-management-toolbook.com/course/category.php?id=9</a></li> <li>See also a range of excellent blog posts and articles&nbsp;by&nbsp;<strong>Kerri Abraham</strong>, in various locations including&nbsp;<em><a href="https://www.nothingbutsharepoint.com/sites/eusp/Pages/Empower-the-Power-User.aspx">End User SharePoint</a></em>, and&nbsp;this one on&nbsp;<em>SharePoint Magazine</em>:&nbsp;<a href="http://www.linkedin.com/nus-trk?trkact=viewShareLink&amp;pk=nprofile-view-success&amp;pp=&amp;poster=60171731&amp;uid=5494708417501081600&amp;ut=NUS_UNIU_SHARE&amp;r=&amp;url=http%3A%2F%2Fwww%2Elinkedin%2Ecom%2Fshare%3FviewLink%3D%26sid%3Ds461175029%26url%3Dhttp%253A%252F%252Flnkd%252Ein%252FWdazdb%26urlhash%3DpMQk%26uid%3D5494708417501081600%26trk%3DNUS_UNIU_SHARE-lnk&amp;urlhash=UvVI&amp;goback=%2Eanb_3981544_*2">http://lnkd.in/Wdazdb</a></li></ul><p>To finish with some new age speak:&nbsp;&nbsp;<em>change is a journey, not a destination</em>.&nbsp;Businesses are always mutable, responsive to external and internal forces, and staff are always moving around, in and out of roles and organisations. &nbsp;Therefore it’s never too late to start your Change Management program and set yourself on the path to success with SharePoint.</p></div> <div class = ' ui-sortable-handle' style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> <h3 class = ' ui-sortable-handle align-left font-alt uppercase black'>Summing up </h3> <div class = ' ui-sortable-handle'><ul class = "list"> <li>Change Management is vital not just during a SharePoint project, but ideally before and definitely after</li> <li>Anyone with responsibility for SharePoint – either an implementation or upgrade project or in an ongoing management role – should focus on the people not the technology</li> <li>Think through the approach that will work best in your environment given your opportunities and constraints, document it and then just do it!</li></ul></div> <div class = ' ui-sortable-handle' style = 'padding-top: 20px; padding-bottom: 20px;'><hr class="mt-0 mb-0"></div> </div> Mon, 25 Jun 2018 15:39:00 +0000 Chamonix Consulting 146 at https://chamonix.com.au