Skip to main content

5 Google IT tips for driving and sustaining Chromebook adoption


Like any other enterprise, we look to technology investments to improve operational efficiency, reduce costs, and increase productivity. At Google, we love Chromebooks for the same reasons as many of our customers—they’re secure by design, they minimize distractions to help users stay focused, and they’re a smart IT investment.
Like any enterprise investing in technology, user adoption is a priority for us. From 2017 to 2018, we nearly tripled the number of Chromebooks used by Alphabet employees—and we learned a lot in the process. If your organization is switching to Chromebooks, here are five tips we recommend as you build out your plan.
1. Ask your employees what they want and need from their devices
You have many choices when selecting devices. Naturally, things like performance, specifications and the kind of work your users do on their devices will top your list of considerations. But it’s essential to keep in mind the priorities your users have as well. One of the best ways to learn them is to ask.
At Google, we did just that. Our thousands of users told us they wanted lightweight devices to fit workdays where they’re frequently mobile, with long battery life, a touch screen, and a high-quality hardware look and feel.
They also wanted to feel connected to their team members in their device choice—IT managers noticed that when most members of a team adopted a particular device together, other team members were more likely to switch. By asking employees what they need, IT managers can ensure that employees are comfortable and supported with their new device at the outset.
2. Decide whether Chromebooks should be mandatory or a choice
After deciding which devices to introduce into your organization, you should determine whether you want Chromebook adoption to be a business mandate or an employee choice. A business mandate can make adoption faster and easier, but can sometimes be challenging for users getting up to speed with new devices. Giving users flexibility in device choice gives them room to make the switch on their own terms, but can add complexity for IT teams.
If you opt for a business mandate, consider the change management process, starting with your best candidates for adoption, and use team feedback to refine your strategy—you can read more on how we did it at Google in this blog post. I also recommend providing plenty of training and transition resources.
If you decide to let people choose their devices, there are lots of ways you can influence employee adoption. For example, you can debunk Chromebook myths and expand the device footprint through flexible trade-in policies or a Grab and Go with Chrome Enterprise program that let them experience the high-end build quality and power for themselves.
3. Train first-time users to be Chromebook pros
After onboarding thousands of Googlers on Chromebooks, we’ve learned a thing or two about quickly getting users up and running. Here’s a quick overview of the timeframe we’ve found works best for gradually introducing users to information:
  • Week 1: Focus on onboarding users with their most critical applications—email, calendar, internal apps, and access to internal systems.
  • Week 2: Help users personalize their Chromebooks by showing them how to customize workflows and add their favorite apps and personal accounts.
  • Week 3 (and beyond): Share lots of resources to help users be productive—hot keys, pro tips, FAQ, and advanced training are all great options.
Proper onboarding for first-time users will go a long way toward making sure your employees are productive and successful on their new devices.
4. Monitor user adoption going forward
We recommend developing a dashboard that can answer some of the biggest user adoption questions about new users. We suggest tracking things like:
  • How many users have a Chromebook and how many use it as their primary device.
  • Why users leave Chrome OS.
  • How many users choose Chromebook at device refresh.
  • The Chromebook assignment rate for new employees.
  • How Chrome OS stacks up against other platforms in your organization.
When developing a tracking tool, remember to include platform attrition. Insights from people who’ve left the platform can help you refine your overall targets and strategy.
5. Share your feedback with us
Improving user adoption also involves welcoming employee feedback and showing them that their insights matter. We encourage all of our customers to collect and escalate feedback from their users to Google.
Our goal is for people to be able to use the platform as much as possible. We want to help you figure out why people can’t use Chrome OS or don’t want to, and make Chrome OS the best possible platform for all users. If you run into recurring issues, file a Chrome bug with Google. You also can stack-rank and prioritize your requests.
Check out our Chromebook adoption kit
Planning to introduce Chromebooks to your organization? Our adoption kit is regularly updated and provides resources and a timeline with the steps we took to evaluate and deploy Chromebooks inside Google. Find it here.





Comments

Popular Posts

Life at Finetech - Episode 2 - Support Engineering

Transform item advancements into key customer arrangements. The foundation of Finetech prosperity, the record directors, specialists, administrators, and experts in these parts are altogether devoted to first rate customer support. 

In the case of consulting with 300 organizations around Sri Lanka and abroad, explaining specialized difficulties for independent companies, or surfacing item advertisements in simply the correct place, we grow new business openings while expanding the utilization of our item offerings.

Finetech Support Team , is playing an important role in the field of business.Lets hear about the experience of the Support Engineering team.

This is Chamathka Fernando , Renewal & Customer Support specialist at Finetech.

7 years of previous experience while achieving a Degree in Business management , HND in Human Resource Management  ( University of Dublin)  and HND in Marketing. She is also an Old Bridgateen with passion and well known for undertaking and consulting the e…

Life at Finetech - Episode 4 - Software Engineering 1

In the case of consulting with 400+ organizations around Sri Lanka and abroad, explaining specialized difficulties for independent companies, and providing with significant solutions, we grow new business openings while expanding the utilization of our item offerings.
Finetech Software Team, is playing an important role in the field of business. Lets hear about the experience of the Software Engineering Team.
The team is crushing it — the road-map is clear, features are taking shape. The product manager is happy with the progress. Engineers are excited about their tasks upto now. Maintaining that rhythm is the first pillar of the tech lead’s job. Lets hear the story of Tech Lead @ Finetech.
Raminda Dayananda- Tech Lead



5 years of experience while achieving a Bsc Degree in Management and IT from University of Kelaniya, He is also an old Maliyadevian with passion and well known for undertaking and leading the software engineering team at Finetech.

Let's hear what Raminda says,

" It …

Life at Finetech - Episode 5 - Software Engineering 2

In the earlier article it was only about one fourth of our software team, today’s interview is about few more people .The team of Jagath, Chamini, Kalana, Chamath & Ajantha, is playing an essential role to make sure the software team is going. Also the contribution they make cannot be measured.

Jagath Priyashantha - Software Engineer

Jagath has completed his BSc in (Software Engineering) at Java Institute while achieving Diploma in BIT, Graphic Designing (IBTS), Professional Certification in Java Technology at Java Institute. Jagath is a product  of St. Peter’s College, Negombo.

Let’s see what software engineer "Jaga" has to say,

As a software engineer, I work in a constantly evolving environment, due to technological advances and the strategic direction of the organisation. We create, maintain, audit and improve systems to meet particular needs, often as advised by a systems analyst or architect, testing software systems to diagnose and resolve system faults.

To do all this…