Building a flexible model for sharing Office 365 changes with your end-users

Darrell as a Service published a great article recently about upcoming changes to the Office 365 ‘save’ dialog box. Starting in February 2019, Microsoft will roll out updates to the default save function for all Windows and Mac Office 365 users. When users press CTRL+S or click Save, the simplified ‘save’ dialog box will display. Files will be saved to OneDrive by default, but users will be able to change the save location via the More save options link. While we still have many questions about how this new ‘save’ dialog box will work, we know that this functionality change will impact our end-users significantly.

How many of our end-users will adapt quickly and easily to this ‘save’ dialog box change? And how can we ease this transition? Without an effective strategy for communicating changes like this one, we could be facing significant user confusion and a tidal wave of calls to the internal help desk.

save dialog box-01
Image source: support.office.com 

Building a flexible communications model
Most organizations can’t afford to create a formal communications plan for individual Office 365 feature changes (particularly given the volume of changes rolling out monthly). So how do we efficiently and effectively share Office 365 changes with our users?

We build a flexible communications model that guides us through the process of sharing Office 365 product updates. This model should provide a variety of conduits for communication, along with guidelines on when/why each should be used.

Your communications model should reflect the culture of your organization and the learning style(s) of your end-users. As I discussed in my post Change by color: The secret of green dots, yellow dots and red dots, some end-users will easily adapt to change. They’ll either roll with the changes when they come across them or be content with a quick explanation posted on a SharePoint Communications site or Yammer post. Other users require formal change communications. These are the users we need to build a flexible communications model for.

So how do you build this flexible model for sharing Office 365 updates? To start, I recommend building a list of the communication mediums you have at your disposal. Examples include:

  • Internal user group meeting announcements/demos
  • Yammer announcements
  • Microsoft Stream videos
  • News articles on a SharePoint Communications site
  • Tips & tricks rotator/carousel on your internal Office 365 learning center
  • Subscription-based email distribution groups (e.g. have end-users subscribe to an email distribution list to receive feature change communications)
  • Department or company-wide email broadcasts
  • News bulletins/announcements on your company intranet or help desk site

Once you know how you can communicate changes, you can build criteria for when to use each. You may decide, for example, to use an internal Office 365 Yammer group to share quick product updates. To help users differentiate these Yammer posts, you’ll use a consistent set of hashtags for product announcements:

  • #WhatsNew – denotes a new feature or capability
  • #mobile – denotes when an announcement is mobile-related
  • #OneDrive – denotes a OneDrive Yammer post
  • #Flow – denotes a Microsoft Flow Yammer post

The key is predictability. Users that want to learn about Office 365 changes on a proactive basis should have an easy time figuring out where to go to learn more. And your help desk agents should know where to go to review recent Office 365 changes so they can validate if a recent change is causing user confusion.

Your communications model must also flex and change over time. Be open to suggestions for improvement. And keep an eye out for trending information from your help desk. If you’re seeing large spikes in Office 365 user issues after changes are released, it could mean your communications model isn’t marketed well enough or isn’t hitting the right target audience. Focusing on a continuous improvement model will enable you to hone your approach and find the right strategy for communicating changes to your users.

SharePoint Saturday Twin Cities call for speakers (April 2019 edition)

SPSTC_logo_smallWe’re thrilled to welcome everyone back for another SharePoint Saturday Twin Cities! Our Spring event is scheduled for Saturday, April 6, 2019 at Normandale Community College in Bloomington, Minnesota.

Our call for speakers is now open. If you’d like to be considered, please submit your session ideas and speaker bio. Submissions will be accepted through February 12th.

More information about the Spring 2019 event (including registration and session schedule) will be posted over the next few weeks. Please monitor our Facebook page and www.spstc.com for updates.

The Coffee Chat on 365 Adoption (episode 2)

img_4406

Daniel Glenn and I just released episode 2 in our podcast miniseries The Coffee Chat on 365 Adoption. The miniseries explores the challenge of driving Office 365 adoption at the organizational level. In episode 1, we dispelled the idea that adoption is an urban myth. We explained why the traditional “build it and they will come” IT model doesn’t work and outlined why organizations must invest in user adoption as an ongoing service.

Episode 2 focuses on organizing and facilitating user adoption events. We discuss creative ideas for internal user groups, including virtual or in-person office hours, “lightning round” demos, and hack-a-thons (aka innovation day events). We also discuss the importance of making these events your own by ensuring they reflect your company culture. We hope you enjoy episode 2! And keep an eye out for episode 3 in the coming weeks!

Have a user adoption question you’d like us to answer in a future episode? Tell us about it: https://go.re365.show/CoffeeChatQ

Previous posts in this series:

Using Microsoft Flow & Azure Cognitive Services to automate sentiment analysis of Yammer posts

yammer sentiment flow-14

As an Office 365 product manager and corporate evangelist, I’m responsible for engaging users and driving adoption of Microsoft Collaboration tools. Measuring the saturation and use of Office 365 is a key part of my role. Yes, I regularly review Office 365 usage metrics for high-level trending. But metrics alone don’t tell the story of user satisfaction and adoption. In order to build better training and adoption programs, I need to understand why my dedicated users love the tools and why others remain resistant.

Many companies rely on surveys to gather end-user feedback. While surveys are useful for gathering specific types of quantitative data, surveys are one-dimensional. You can’t dynamically ask follow-up questions to learn more about specific survey responses, and you can only capture a limited set of data points. Innovation games enable you to gather a much broader set of quantitative and qualitative user data, but require an investment of time to facilitate games and distill the results. For best results, I recommend a multidisciplinary approach that leverages Office 365 usage statistics, user survey responses, innovation games data, user testimonials, etc. to measure user satisfaction. 

With the release of artificial intelligence (AI) and machine-learning algorithms, we also have the ability to gather user sentiments automatically. If your organization uses Yammer to drive employee engagement and empower open dialogue, you have a wealth of user data that can be analyzed. With Azure Cognitive Services and Microsoft Flow, you can perform automated sentiment analysis of your Yammer group posts. Sentiment scores for each Yammer message can be stored in SharePoint and visualized for trending analysis via Power BI. You can even send push email notifications to your Office 365 administrators or Corporate Communications team when strong positive or negative messages are posted in Yammer.

Chris Bortlik, Principal Technical Architect for Microsoft, recently shared a blog post on Yammer sentiment analysis. I used Chris’ model, with a few modifications, to gather and report on Office 365 user sentiment.

The scenario:
My organization leverages a Microsoft Flow Yammer group to foster employee conversations and questions/answers about flow. We want to monitor the Microsoft Flow Yammer group using sentiment analysis so we can:

  • Identify negative flow Yammer posts that require follow-up
  • Identify positive Yammer posts that can serve as user testimonials or references
  • Define trends in our Microsoft Flow Yammer posts (e.g. daily/weekly/monthly positive and negative trends, overall positive or negative sentiments for flow, etc.)
  • Validate the success of our Microsoft Flow education and adoption program (e.g. confirm we’re seeing growth in the volume of positive flow Yammer posts over time)

The setup:
Follow the steps outlined below to set up automated Yammer sentiment analysis.

Step 1: Confirm you have a Cognitive Services Text Analytics Account. In order to set up this solution, you will need a Cognitive Services account key and a root site URL.

Step 2: Create a SharePoint list to store your Yammer sentiment analysis scores. Flow will create a new item in your list for each Yammer message it analyzes. Here’s a list of the custom columns I added to my list:

  • Score – Number column; stores the sentiment rating for each Yammer message
  • Message link – Hyperlink column; stores a link to the rated Yammer message
  • Posted by – Person/Group column; stores the name of the person that posted the Yammer message
  • Thread ID – Single line of text column; stores the Yammer thread ID for the message. Enables you to sort, filter, and group sentiment scores for a given Yammer thread (including original message and replies).

Azure Cognitive Services will provide a numeric sentiment score between 0 and 1 for each Yammer message it analyzes. The more negative a Yammer message is, the closer to 0 its score will be. More positive messages will receive a rating closer to 1.

Here’s a screen shot of my SharePoint list. Each list item represents a rated Yammer message:
Yammer sentiment flow-11.png

Step 3: Identify the Yammer group you want to perform sentiment analysis on. You can set up sentiment analysis for multiple Yammer groups, but each will require a separate flow process. I also recommend setting up a different SharePoint list to hold sentiment scores for each of your Yammer groups. (Having different SharePoint lists enables you to set up different trending reports on Yammer group sentiment.)

Step 4: Create your Microsoft Flow. I created my flow from scratch (not using a template). Here’s a quick breakdown of the flow conditions and actions:

  • When there is a new message in a group – Detects when a new Yammer message is posted in my Yammer group
  • Get user details – Pulls Yammer user profile details. (Enables us to capture the full name and email address for the person posting the Yammer message.)
  • Detect Sentiment – Calls the Azure Cognitive Services API so it can calculate a sentiment score for the Yammer message
  • Create item – Creates a SharePoint list item for the Yammer message being analyzed
  • If the comment is negative – Sends an email to my Office 365 admin team if the sentiment score for a Yammer message is ≤0.3.
  • If the comment is positive – Sends an email to my Office 365 admin team if the sentiment score for a Yammer message is ≥0.7.

Step 5: Create Power BI report(s) to visualize your Yammer sentiment scores. Published reports can be rendered in your SharePoint Online Communications or Team sites using the Power BI web part. For help in setting up sentiment analysis slicers, check out this DataChant blog post.

Here’s a sample dashboard that shows Yammer sentiment data for my Microsoft Flow Yammer group:

yammer sentiment flow-14

Step 6: Distill the results. Once you start calculating Yammer sentiment and have reports to visualize the data, you can analyze the results and follow up where needed. Here are a few ideas to get you started:

  • Break down negative Yammer posts (e.g. posts with a score ≤0.3) by user. Schedule follow-up meetings with Office 365 end-users that consistently post negative messages. The goal is to ask questions and understand the pain points the users are facing. Perhaps they have hardware or network issues that impact their productivity. Or maybe they’re having issues with Microsoft Flow and need a coach/mentor to spur their learning. Having one-on-one dialogues provides the opportunity for candid feedback and enables you to make a difference in the user’s productivity and technology experience.
  • Identify Office 365 enthusiasts. Break down Yammer posts by volume or by high sentiment average in order to find power users across your organization. Set up meetings with these enthusiasts to understand how they leverage Office 365. Incorporate them into your user group or internal community and support them in their growth. These enthusiasts can become your Office 365 evangelists!
  • Monitor the volume of Yammer posts in your group. Build a gauge that shows your number of Yammer messages month-to-date and identifies progress towards your monthly Yammer message goal. Keeping an eye on your total posts month-to-date and year-to-date will help you monitor use over time and highlight areas you may need to invest additional time and adoption efforts in.

yammer sentiment flow-15

  • Optimize your communications. If one of your Office 365 admin resources has consistent negative Yammer sentiment scores, have them evaluate the verbiage they’re using. Slight wording changes can change the tone of their messages, increasing Yammer sentiment scores and better engaging with end-users.
  • Take a health pulse. Build trending visuals that show average post volumes and sentiment averages by week or month. If you start seeing spikes on volume of posts and/or significant changes in your sentiment averages, it’s time to dig deeper. Perhaps you’re seeing a spike in interest in PowerApps after a compelling user group presentation or have network bandwidth issues that are causing issues. Either way, Yammer sentiment analysis can be your early warning indicator that something has changed.

2018: A blogging year in review

2018-abstract-art-285173

Late last year, I was challenged to write and blog more frequently on SharePoint/Office 365. It started as a five-week effort: write five new blog posts in five weeks. The writing didn’t concern me (I was an English & Journalism major; writing comes naturally). I was worried about coming up with meaningful topics to write on. I dove in and managed to get five posts written by the five-week deadline. I congratulated myself for the effort, relieved to be done. But after taking a couple of weeks off, I realized I missed it.

This year, I extended the model. I wasn’t sure I could manage a blog post per week, so I set a goal of publishing three blog posts per month. The results exceeded my own expectations! Here’s my 2018 blogging year-in-review:

Total # of blog posts in 2018: 43
Total # of words: 20,629
Average words per post: 480

Just like my five-week challenge, I was certain the biggest obstacle was going to be coming up with topic ideas. But here’s the thing–the more I blogged, the more topic ideas I came up with. There were only a couple of times this year when I was stumped for a new topic to blog about.

One of the biggest surprises this year was popularity of individual blog posts. Turns out I’m often a bad predictor of which posts will resonate with readers. I had to learn to write and publish without pre-judging whether a given post would be deep enough, technical enough, useful enough, etc.. At the end of the day, readers will determine the relative merit of each post. There’s no point in me trying to predict the outcome.

Some blog posts took on a life of their own, generating a great deal of interest. A prime example was my Ignite 2018 post on The importance of Community Managers. I wrote the post in less than 30 minutes (a very quick turnaround by my standards) and wasn’t sure it was deep enough to generate much attention. But the content resonated with the Office 365 community, and it was one of my most-tweeted blog posts of 2018.

I also had to learn to be ready when imagination struck. New blog post ideas can spring up anytime–while driving to work, grocery shopping, talking with other Office 365 practitioners, etc.. I learned to take a few seconds when imagination struck to jot down blog ideas when I had them. I’ve sent myself emails, left myself voice memos, created draft blog posts with a brain dump of ideas, etc. The methodology doesn’t matter–I just need to capture the ideas when I have them.

I’ve also been amazed how quickly (and how slowly) some blog posts come together. My post It’s not about the technology. It’s about the use case was written in 10 minutes after recording REgarding 365 debate #4: Org-wide Microsoft teams. Other posts take an inordinate amount of time and effort. I wrestled with Disruption vs. Value: Keeping your Office 365 Initiative Afloat for 10+ hours before I was happy with the results. While I hate the wrestling process, the outcome is always worth it.

So what am I planning for 2019? I haven’t set a formal goal yet, but want to maintain a frequent pattern of publishing new posts. I love the interaction with readers via Twitter, and have learned to love the writing and review process. Blogging frequently keeps me engaged in learning about Office 365, user adoption, and enterprise governance. It makes me a better employee, a better community contributor, and a better Microsoft MVP.

I’m signing off for 2018 with a summary of my top blog posts (by user views) and my favorite posts of the year. I hope you enjoy them!

Top posts (based on user views):

My favorite posts of 2018:

Participating on episode 21 of Microsoft’s The Intrazone podcast!

I was recently asked to serve on a panel for episode 21 of The Intrazone, Microsoft’s bi-weekly conversation and interview podcast about SharePoint usage and adoption. Hosts Chris McNulty and Mark Kashman recorded the show live at SharePoint Fest Chicago.

The topic for our panel discussion was 2019 predictions for SharePoint. I was asked to represent the user adoption and enterprise governance point of view. Wes Preston outlined his predictions about PowerApps growth, Drew Madelung shared thoughts on OneDrive, and Treb Gatte discussed data visualizations and Power BI.

So what are my top predictions for SharePoint in 2019? Check them out:

  1. User adoption challenges will grow. As organizations realize their users are not homogenous and the traditional methods (e.g. company-wide rollout email communications, “train the trainer” education strategies, instructor-led training classes that focuses on features and not business outcomes) are ineffective, there will be a stronger focus on effective adoption models.
  2. SharePoint hub sites will require enterprise-level governance. Hub sites enable us to bring families of SharePoint sites together with common branding, search, news, and navigation. But hub sites are limited (only 100 hubs allowed per tenant) and site owners may be unsure when and where to use hub sites effectively. I predict many companies will dive headlong into hub sites and later realize that more effective governance of hubs is critical. I recommend creating a hub site governance policy and seeding your organization with strong hub site success stories/examples.

For more on our SharePoint 2019 predictions, check out episode 21 of The Intrazone. And for more on the episode, read Mark Kashman’s blog post.

Thanks to Mark Kashman, Chris McNulty, and their Intrazone team for inviting me to participate. It was a pleasure!

The SharePoint Conference is back in 2019!

SPCNA_2019The SharePoint Conference is coming back to the MGM Grand in Las Vegas May 21-23, 2019! This is THE conference event of the year for SharePoint. I’m honored to be asked back to present, and will have 4 new sessions at the conference:

  • Determining when to use SharePoint hub sites
  • Next-gen user adoption: Leveraging hack-a-thons to drive creative Office 365 business solutions
  • Building a diverse tech community (co-presenting with Wes Preston, MVP)
  • Executive presence and personal branding for women in technology

Why you need to attend:
SharePoint Conference is THE place to learn more about SharePoint and related Microsoft 365 technologies like OneDrive, Microsoft Teams, Yammer, Microsoft Stream, Outlook, Office applications, PowerApps, Microsoft Flow, etc. You don’t want to miss your opportunity to:

  • Connect with industry gurus, meet with members of the Microsoft product teams, and connect with Microsoft 365 customers from around the world
  • Learn more by attending one of 200+ educational sessions and workshops
  • Engage with Microsoft partners in the conference exhibit hall
  • Learn about Microsoft’s latest innovations and strategic product investments
  • Get answers to your burning Microsoft 365 questions!

Save money on your registration:
The SharePoint Conference will likely sell out, so don’t miss your chance to register. Use discount code HAASE and you’ll save $50 on registration!

Sarah Haase-Haase Social Banner-204.jpg

Want more information on my sessions? Abstracts and video introductions for each session are provided below. I can’t tell you how excited I am about the conference. Hope to see you there!

Determining when to use SharePoint hub sites
Hub sites are fundamentally shifting the information architecture for our intranets. And while site owners are excited about the functionality hubs offer, they’re still unsure when and where to use hubs. This session provides practical guidance on use of SharePoint hub sites, including:
– Determining when hubs are needed
– Building organizational strategies for governing hub sites
– Educating your site owners about hub sites

Next-gen user adoption: Leveraging hack-a-thons to drive creative Office 365 business solutions
This session explores the use of hack-a-thons to drive Office 365 user interest, enthusiasm, and innovation. Hack-a-thons are an immersive and inexpensive learning opportunity. Hack-a-thon participants take part in the entire solution design and build process, from envisioning new business solutions to learning how to build capabilities in Office 365. Come learn how to design and facilitate a hack-a-thon event for your organization or user group.

Building a diverse tech community (co-presenting with Wes Preston, MVP)
User communities play a vital role in the success of SharePoint and Office 365. This session explores methods for welcoming diverse community members. Whether you’re building a SharePoint Saturday event or an organizational or regional user group, you need to attract:
– Citizen developers
– Business users
– Traditional IT staff
– Users of different race, gender, age, and technical proficiency

Executive presence and personal branding for women in technology
This fast-paced diversity session focuses on the unique challenges facing female technology leaders. Personal stories and practical tips for building your personal brand and executive presence communication skills will be shared via a series of short TED-style talks and a Q&A panel. Topics covered include:
– Building a strong leadership personal brand
– Scales of dissimilarity: Why women are often judged differently than men
– Leadership presence, mindfulness, and inclusion

 

The Coffee Chat on 365 Adoption (episode 1)

I have exciting news to share! Daniel Glenn and I are ready to unveil the first episode in our new podcast miniseries “The coffee chat on 365 adoption!” The podcast enables us to drink coffee and talk about the challenge of driving Office 365 adoption at the organizational level. We recorded the first podcast episode several weeks ago at SharePoint Fest Chicago.

Topics discussed in this episode:

  • Why organizations have difficulty achieving strong adoption
  • Common adoption pitfalls and roadblocks
  • The challenge of scaling adoption initiatives (moving beyond one-on-one initiatives to impact a broader group of users in your organization)
  • Why adoption should be treated as an ongoing service instead of a one-time project

Daniel and I will keep the user adoption conversation going as we record several additional coffee chats in the coming months. Each episode will focus on a different Office 365 adoption topic. We’ll share successful strategies we’ve seen for hosting adoption events and provide practical tips for supporting the rollout and adoption of key Office 365 applications.

We hope you enjoy this episode. And don’t miss the outtake photos from the podcast recording!

20181213_121432958_iOS
20181211_025749395_iOS

 

Organizational Culture: Take it or leave it, but it’s yours

Close up of men's rowing teamCan organizational culture predict the success or failure of your Office 365 rollout? Absolutely. The positive (or negative) impact of your organization’s culture has a direct influence on the success of your technology initiatives. After all, your culture defines how easy or difficult it is to do almost everything, from onboarding new employees to openly sharing ideas and driving adoption of new technologies.

Your IT department’s reputation and history of engagement with business teams is a key indicator of its cultural tie-in to your organization. An IT department that fosters open dialogue and has high-trust relationships with business teams has a tremendous advantage in deploying Office 365. Conversely, a tarnished set of relationships with IT can make it virtually impossible to drive successful change management efforts. Users that distrust or have an adversarial relationship with IT may be predisposed to view all IT initiatives in a negative light.

Your organizational culture is a living, breathing organism. It is built over time and is reinforced by operating norms, employee interactions, and executive modeling. Every communication decision your executives make and every unwritten social norm your departments have put in place has driven the design, shape, and usability of your culture. Changing (or rewriting) your organizational culture is a monumental effort that requires diligence, time, and a huge influx of positive energy. And ultimately, your employees will decide if the culture shift has a hope of succeeding.

Many factors can negatively impact your company’s culture: well-regarded executives leaving for new opportunities, founders selling the company or retiring, erosion of employee trust, etc.. Ironically, difficult economic times and business turbulence isn’t always a harbinger of negative culture shifts. Positive cultures can exist and thrive in negative business climates if there is trust, transparency, and a sense of company unity.

So what steps can you take to improve your company culture and support your Office 365 rollout? First, evaluate the current state of your organization’s culture. If you’re concerned your employees can’t evaluate your culture objectively, bring in outside consultants to perform a culture assessment. Next, build a vision for where you want to go. Interview employees, executives, and board members to gather their wish list for culture improvements. If you haven’t done so already, try leveraging innovation games to gather creative ideas for cultural improvements.

Once you’ve documented your current and desired future state, it’s time to build your transition plan. The specifics of your plan will be driven by your specific context, but common themes for cultural improvements include:

  • Aligning strategy & communications. Ensure your organizational goals are clearly defined and openly discussed at all levels. Having everyone on the same page and moving towards the same goal brings a sense of unity and common purpose.
  • Tear down the silos. Ensure your business teams are working together effectively and not competing for attention, funding, or recognition. Actively use the word “we” when referring to company initiatives, tasks, and efforts. Inclusive language fosters a collaborative, engaging atmosphere.
  • Be transparent. Employees can sense inauthenticity. Consistent, strong leadership is critical, and transparency and trust will build bridges and inspire cooperative behaviors.
  • Communicate early and often. Talk about what’s going well and what still needs work. Engage in departmental, cross-departmental, and all-employee meetings and engage everyone in the mission to improve your company culture. A unified strategy will help achieve buy-in and drive adoption.

There’s no wrong time to start your cultural transformation. Yes, it would be ideal if all our organizations had a winning culture before we began rolling out Office 365. This is rarely the case, so don’t sweat it if you’re not in a perfect position. Where you’ve been is less important than where you’re going.

SharePoint Fest Chicago 2018

Sarah Haase.png

It’s almost time for SharePoint Fest Chicago 2018! I’m excited to head back to Chicago next week for this year’s conference, where I’ll be presenting a half-day user adoption workshop along with sessions on designing next-gen user adoption events, reeling in overgrown SharePoint implementations, and governing usage of SharePoint hub sites.

SharePoint Fest Chicago is always a great event. There’s a mix of technical how-to sessions on SharePoint and Office 365 along with conceptual sessions on user adoption, governance, business valuation, search, content management, etc. For more information on the great content being offered, check out the conference agendaStill want to register? Use discount code Haase100 and save $100 on your registration.

Abstracts for my conference workshop and sessions are included below. I’m looking forward to seeing everyone at the event!

business-commerce-container-379964SharePoint/Office 365 User Adoption Master Class

A smooth deployment isn’t enough. Driving effective utilization of SharePoint and Office 365 is more than building effective migration strategies, training users on key features or sending out marketing emails. This master class provides a deep-dive on the components of user adoption. You’ll learn why user adoption programs succeed and fail, gain practical experience designing adoption strategies and learn how to leverage innovation games to build consensus.

During this workshop, you will:

  • Learn the basic foundations of user adoption, including key intrinsic and extrinsic motivators
  • Understand how different types of users in your organization can make (or break) your chances of user adoption success
  • Understand how innovation games can help drive shared understanding, uncover user requirements and drive engagement/enthusiasm
  • Examine real-world user adoption programs and determine how and why they were successful

brandon-green-321795-unsplashThe Peter Pan complex: Determining when a SharePoint site should grow into a hub site

We’ve been waiting for it….and now SharePoint hub sites are here! Hubs enable us to create a shared experience for a group of related SharePoint sites, including: common navigation, unified branding, aggregated news displays, and multi-site search. But how do you determine which sites should be hubs? And how do you manage the fulfillment of hub site requests?

As SharePoint site owners are educated about the capabilities of hub sites, demand for new hubs will increase. This session outlines key business criteria you’ll want to consider as you start leveraging hub sites. You’ll learn:

  • What hub sites are and how hubs can be leveraged
  • How to determine when a hub site is needed (e.g. should every department have a hub site? What are the criteria for leveraging a hub site?)
  • How to build an organizational strategy for usage and governance of hub sites
  • Practical ideas for managing the provisioning of hub sites

rawpixel-315193-unsplashNext-gen user adoption: Leveraging hack-a-thons to drive creative Office 365 engagement

We want our users to leverage Office 365 to drive productivity and collaboration. But how do we engage our users, spark their creativity, and inspire them to build Office 365 solutions that re-imagine work? Hack-a-thons are an immersive and inexpensive way to build enthusiasm and foster learning. Hack-a-thon participants take part in the entire design and build process, from envisioning new business solutions to learning how to build capabilities in Office 365.

This session explores the use of hack-a-thons to drive user interest, enthusiasm, and innovation. You’ll leave with practical tips on how to design and facilitate a hack-a-thon event for your organization or user group.

An old abandoned house overgrown withReclaiming SharePoint: How to reel in an overgrown implementation

SharePoint is organic. File-based SharePoint sites grow exponentially, consuming more and more storage space and making it difficult for users to find what they need. Governance plans designed to steer SharePoint’s utilization tarnish over time, discouraging users from adopting the platform.

This session outlines the reasons why SharePoint environments become overgrown and under-utilized and provides practical guidance on how you can assess your implementation and create a revitalization plan. We’ll also review several real-world SharePoint turnaround stories, highlighting the challenges faced and the methods taken to revive user adoption. Whether you have a “green-field” implementation with no formal governance in place or have a faded governance model that is no longer working, you’ll leave this session with proven techniques for engaging your key constituents and driving change.