Since the start of the COVID-19 pandemic, there’s been a rapid acceleration of digital transformation across the entire healthcare industry. Telehealth has become a more mainstream and safe way for patients and caregivers to connect. Machine learning modeling has helped speed up innovation and drug discovery. And new levels of integration and data portability have helped enable greater vaccine availability and equitable access to those who need it.

Data has been at the crux of this digital transformation — helping people stay healthy, accelerating life sciences research and delivering more personalized and equitable care. We recently unveiled partial results from our research with The Harris Poll, which revealed that nearly all physicians (95%) believe increased data interoperability will ultimately help improve patient outcomes. Today, we’re unveiling the second part of that research. 

In February 2020, we commissioned The Harris Poll to survey 300 physicians in the U.S. about their biggest pain points — this was just before the COVID-19 pandemic strained the entire healthcare system and made us all hyper-aware of the risks we take in going to the hospital. In June 2021, we followed-up with those same questions and more. What it unveiled was just how much COVID-19 reshaped technology’s role in the healthcare field and how it’s changing day-to-day operations for physicians. 

Here are some of the highlights: 

Healthcare organizations accelerated technological upgrades over the course of the pandemic. After a year shaped primarily by the COVID-19 pandemic, use of telehealth saw substantial YOY growth, jumping nearly threefold from 32% in February 2020 to 90% this year. Forty-five percent of physicians say the COVID-19 pandemic accelerated the pace of their organization’s adoption of technology. In fact, more than 3 in 5 physicians (62%) say the pandemic has forced their healthcare organization to make technology upgrades that normally would have taken years. For example, 48% of physicians would like to have access to telehealth capabilities in the next five years. Before the COVID-19 pandemic, about half of physicians (53%) say their healthcare organization’s approach to the adoption of technology would best be described as “neutral” (i.e., willing to try new technologies only if they have been in the market for awhile or others have tried and recommended them). 

Despite the technological leaps this year, most physicians still believe the industry lags behind in technology adoption but recognize the opportunity for technological support and advancement. The majority of physicians don’t view the healthcare industry as a leader when it comes to digital adoption. More than half of physicians describe the healthcare industry as lagging behind the gaming (64%), telecommunications (56%), and financial services industries (53%). However, the healthcare industry is not seen to be trailing as much as it was last year behind retail (54% in 2020; 44% in 2021); hospitality and travel (53% in 2020; 43% in 2021); and the public sector (39% in 2020; 26% in 2021). 

Better interoperability alleviates physician burnout, improves health outcomes and speeds up diagnoses. The majority of physicians say increased data interoperability will cut the time to diagnosis for patients significantly (86%) and will ultimately help improve patient outcomes (95%.) In addition to better patient experiences and outcomes, more than half of physicians (54%) believe increased access to data via technology has had a positive impact on their healthcare organization overall. A majority believe that technology can alleviate the likelihood of physician “burn-out” (57%) and that efficient tools help decrease friction and stress (84%). And, as a result, 6 in 10 physicians say access to better technology and clinical data systems would allow them to have better work/life balance (60%) and that better access to/more complete patient data would reduce administrative burdens (61%). It is therefore not surprising that nearly 9 in 10 physicians (89%) say they are increasingly looking for ways to bring together all patient data into a single place for a more complete view of health. 

Familiarity with new Department of Health and Human Services (DHHS) interoperability rules grows, and many physicians are in favor. Most physicians (74%) say they have at least heard of the new DHHS rules (launched in 2019) to improve the interoperability of electronic health information. This is a clear rise from 2020 (64%), but deeper knowledge is fairly low. Only 30% of physicians say they are somewhat or very familiar with the new rules (though, again, this is a rise from 2020, when only 18% said they were very/somewhat familiar). Similar to in 2020, among those who have heard of the new rules, nearly half are in favor (48% in 2021; 45% in 2020) but a similar proportion remain unsure (46% in 2021; 50% in 2020). And like in 2020, by far the top potential benefit of the rules is thought to be forcing EHRs to be more interoperable with other systems (70%).

Google was founded on the idea that bringing more information to more people improves lives on a vast scale. In healthcare, that means creating tools and solutions that make data available in real time to help streamline operations and improve quality of care and patient outcomes. For example, our recently announced Healthcare Data Engine makes it easier for healthcare and life sciences leaders to make smart real-time decisions through clinical, operational, & groundbreaking scientific insights. To find out more about the Healthcare Data Engine, click here.

^{Survey methodology: The 2021 survey was conducted online within the United States by The Harris Poll on behalf of Google Cloud from June 9 – 29, 2021 among 303 physicians who specialize in Family Practice, General Practice, or Internal Medicine, who treat patients, and are duly licensed in the state they practice. The 2020 survey was conducted from February 18 – 25, 2020 among 300 physicians who specialize in Family Practice, General Practice, or Internal Medicine, who treat patients, and are duly licensed in the state they practice. Physicians practicing in Vermont were excluded from the research. This online survey is not based on a probability sample and therefore no estimate of theoretical sampling error can be calculated. For complete survey methodology, including weighting variables and subgroup sample sizes, please contact press@google.com.}

Last June, in the early months of the pandemic, we expanded Business Messages to support all kinds of businesses, from pharmacies and grocery stores to airlines and luxury brands. Then, in December, we announced the ability for small businesses to use the Google Maps app to message with their customers. We knew people would find messaging directly with businesses from Google Search and Maps helpful, but we didn’t know just how valuable it would turn out to be. 

Consumers are increasingly eager to use messaging to connect with brands, and businesses across all industries are now building innovative messaging experiences to address that growing need. The demand from consumers is reflected in recent data:

• 45% of users have spent more time on messaging services because of the pandemic
• 85% of consumers would like to message brands directly, up from 65% in 2019

Being able to message a business directly has never been more important. For me personally, there’s nothing more fulfilling than using technology to help people in the moments that matter. After the release of initial COVID-19 vaccines in late 2020, online searches for vaccines reached an all-time high. To help people searching for vaccine eligibility, availability, and appointment booking, Albertsons Companies’ banner pharmacies—like Albertsons, Safeway, and Vons—made this information easily accessible through Google Search and Maps via the “chat” button. This  gave people the information they needed, when they needed it.

To be more helpful in moments like these, over the last year, we’ve made Business Messages available globally, in more than 70 languages, and we’ve seen more than 30,000 brands and 200 partners come on board. Major brands like Carrefour, Walmart, and Woolworths have invested in Business Messages to help serve their consumers in new and meaningful ways. 

Expanding the conversation between consumers and brands

The retail sector has undergone a transformation since the start of the pandemic. As a result, we know it is critical for digital services to integrate with physical stores. We were able to do just that with Google’s Business Messages, which has been instrumental in helping better serve our customers across 1200+ stores in Europe.Thomas Rudelle
Global Digital Marketing Director, Carrefour

There were major shifts in consumer behavior during the pandemic, from the way people found and purchased products to the ways they interacted with businesses. Not only did we see higher demand for direct contact with brands, but retail searches also surged. At the end of 2020, retail searches grew at a rate that was more than three times higher than the same period in 2019 (based on Google internal data).

As Business Messages has become more widespread, brands are able to boost both responsiveness and customer satisfaction using the service. Levi’s, for example, surpassed 85% customer satisfaction scores using Business Messages and they discovered that the service drove 30x more store-related questions than web chat.

Many brands have also digitized what were traditionally in-store experiences, especially in high-consideration categories like jewelry. For example, Signet brought its virtual jewelry consultant to Business Messages, offering customers advice and answering queries in a way that’s convenient but still feels personal.We started using Google’s Business Messages pretty early on, and continue to transform and improve our experience. The ability to let customers know whether a product is in stock, and its precise location, is critical to offering a connected and frictionless shopper experience. Of course it also helps reduce the workload on our store and customer hub teams.Nick Eshkenazi
Chief Digital Technology Officer, Woolworths

As a working mother, these sorts of innovations have made a direct impact in my own life. I find it very helpful to be able to ask—and get real-time answers to—everyday questions using Business Messages, ranging from store hours and product availability to order status and how to make returns. One of my favorite features is the ability to know, in real time, what store wait times are like, and the exact location of the product I’m looking for, saving me precious time when I visit the store. 

Business Messages helps people do more with their time in other ways as well. Earlier this year I’d been meaning to change my insurance plan, but kept pushing it off because I didn’t want to get on a phone call. I can now message Geico to update my policy through the agent pretty effortlessly. Similarly, in India, Vi customers can use 24×7 real-time customer service to chat with their AI powered virtual assistant VIC, integrated with Google’s Business Messages, to check billing information, activate packs, add recharges and payments, check balances, and much more—and it all happens seamlessly.

Building a full suite of messaging products

We’re investing in building a full suite of messaging products that enable seamless conversational commerce to drive business results. As Business Messages continues to support brands in establishing their messaging presence on Google, we’re also experimenting with other ways to help them increase their reach and engagement on Search and Display. To accelerate on the digital front, we recently integrated AdLingo, a project built within Area 120, Google’s in-house incubator. This will enable brands to easily transform ads into AI powered, personalized conversations at scale.

For more information on how you can activate Business Messages, please reach us via the contact form on the Business Messages website. Merchants can also read and respond to messages via Google My Business or on the Google Maps app.

Over the past year, Google Workspace rapidly evolved to meet the needs of users as we collectively grappled with remote and hybrid work. First, we launched Google Workspace to commercial customers, which brought together the powerful individual apps people know and love into a single, integrated solution. Then we made Google Workspace available to nonprofits, governments, and schools. And in June, we brought the power of Google Workspace to everyone, enabling more than 3 billion users to transform the way they connect, create, and collaborate. To extend these experiences further, we’ve seen a stunning 4.8 billion apps installed in Google Workspace to date. We’re excited to see so many users personalize their experience by adding third-party apps or by building their own to create a more powerful engine for productivity and collaboration. 

As we celebrate the more than 5,300 public apps in the Google Workspace Marketplace that provide users with the opportunity to extend their experience, we’re increasing our investment in the underlying platform. Developers have been able to build applications that integrate with Gmail, Drive, and Docs for years. And today, we’re announcing significant enhancements to the Google Workspace platform by making it just as easy for developers to build applications and integrate with Google Meet, Chat and Spaces.

We’re releasing a new Jira integration for Google Chat and Spaces. This integration enables users to create new tickets quickly, see actionable previews, and monitor issues as they come into the space they’re already using for collaboration. 

“Modern work requires people to switch contexts and tools faster than ever before. We believe an open ecosystem and tight integrations among the tools that users rely on every day is vital to their success. Since 2017, our Trello integration with Gmail has been installed by more than 7 million people. Today, we are excited to build on the partnership between Atlassian and Google to propel work collaboration further with the integration of Jira with Google Chat and Spaces,” said Joff Redfern, Chief Product Officer, Atlassian.

As work continues to evolve, we’re especially committed to the concept of collaboration equity: the ability for everyone to participate and drive impact no matter their location, technical ability, language preference, or device. Carrefour Property – Carmila is evolving how they innovate by connecting frontline workers to those in the office with our no-code development platform AppSheet. For example, after discovering a problem, onsite managers previously had to send an email, enter data into a spreadsheet, and sometimes attend a meeting to explain the issue. Now, with AppSheet, they can simply input the data on their phone in a single step, and the team back at headquarters can see and act on the issue while also tracking all the other issues being reported from other locations.

We continue to empower frontline workers and IT teams alike, bringing more flexibility into Google Workspace by integrating AppSheet into Gmail. This new integration allows anyone—regardless of their coding experience—to reclaim time with custom, no-code apps and automations. Budgets and vacation requests can be approved, inventories and asset management systems can be updated, and much more—all with AppSheet and directly from your inbox. 

New investments in security 

As we continue to deliver delightful new experiences for users, we are keeping security at the forefront; it’s infused in every layer of our product design so that customers have the flexibility and trust needed to operate in a secure environment. To build on this commitment, we’re announcing Google’s new Work Safer offering to help organizations, their employees, and partners collaborate and communicate securely and privately in today’s hybrid work environment. Work Safer will provide companies with access to best-in-class security for email, meetings, and messages, documents, and more. It uniquely brings together the cloud-native, zero-trust solutions of Google Workspace with industry-leading solutions from across Google and its cybersecurity partners, CrowdStrike and Palo Alto Networks. 

To further strengthen security and privacy across the Google Workspace platform, we’re also announcing four key new capabilities: 

1. In June, we announced that Client-side encryption (CSE) was available in beta for Drive, Docs, Sheets, and Slides. Now we’re bringing CSE to Google Meet, giving customers complete control over encryption keys while helping them meet data sovereignty and compliance requirements. We’re also pleased to announce the beta of our Key Access Service Public APIs, which enables customers to directly manage their encryption keys without the need for a third-party partner.
2. Data Loss Prevention (DLP) for Chat is now in beta. This is a continuation of our ongoing commitment to help organizations protect their sensitive data and information from getting into the wrong hands, without impacting the end-user experience. With DLP for Chat, you can enable the power of spontaneous conversation between individuals and teams, while preventing sensitive and confidential information from leaving your organization. Interested customers can sign up for the Client-side encryption and DLP for Chat betas today.
3. Drive labels are now generally available. Organizations are now able to classify files stored in Drive based on their sensitivity level. Labels integrate with Google Workspace Data Loss Prevention, making it easier to manage external sharing, downloading, and printing of sensitive files. 
4. We’re rolling out additional protections to safeguard against abusive content and behavior. If a user opens a file that we think is suspicious or dangerous, we’ll display a warning to the user to help protect them and their organization from malware, phishing, and ransomware. This functionality is now available in Google Docs and will be rolling out soon for Google Sheets and Slides. 

Fueling the future of work and collaboration   

Our mission is to empower everyone with an innovative and seamless experience that gives people—no matter their location or technical ability—the opportunity to drive real impact. At its core, the vision of the Google Workspace platform is to help you build your own innovation momentum, while providing a foundation of security and privacy. I hope you’ll join me at the Google Cloud Next ’21 event where you can learn more about the Google Workspace vision, and even better, see these new experiences in action.

Editor’s note: Today we hear from the Lowe’s SRE team. They share about how they have been able to increase the number of releases they can support by adopting Google’s Site Reliability Engineering (SRE) framework and leveraging their partnership with Google Cloud. 

At Lowe’s, we’ve made significant progress in our multiyear technology transformation. To modernize our systems and build new capabilities for our customers and associates, we leverage Google’s SRE framework and Google Cloud, which helps us meet their needs faster and more effectively. With these efforts, we’ve been able to go from one release every two weeks to 20+ releases daily—about 20X more releases per month. 

Our SRE transformation didn’t happen overnight, though. Every step along the way brought some challenges. But looking back, we are excited to see how much we have accomplished for our customers as a result. 

Back in 2018, before adopting SRE practices, we were more reactive than proactive, following an “eyes on glass” approach. On-call structures and incident management efficiency were not at optimal levels with too many repetitive and manual tasks, resulting in operational toil. Production concerns were not surfaced into the product roadmap, which resulted in delays in making fixes.

Bootstrapping SRE at Lowe’s

As we moved from on-prem to Google Cloud, we decided to move from a monolithic- to microservices-based architecture. And to better manage this new architecture, we embarked on an SRE journey. 

Then as COVID-19 hit, we really had to accelerate this journey as customers increasingly moved to online ordering and delivery to meet their Total Home Improvement needs. To do so, we followed four key principles that allowed us to meet changing customer needs quickly and release fast and reliably.

1. Automate away toil 
   As we moved from traditional Ops to an SRE ecosystem, our biggest opportunity was reducing toil, so that engineers can spend time on activities that drive business impact and customer outcomes. We think of toil as work that is manual, repetitive,  tactical, devoid of enduring value—but automatable. So, to tackle toil, we focused on automating away the need for manual intervention. As an example, we made sure engineers were not the first point of contact for any alert. Any triage or resolution that an engineer can perform, a machine can be trained to do the same. We used supervised and unsupervised learning techniques to automate our toil. With a long-term goal of “no toil,” our SREs work on identifying and reducing toil to a manageable level across the organization.
2. Engineer alignment through roadmaps
   Our goal is to maximize the engineering velocity of developer teams while keeping products reliable. We want an engagement model where product, SRE and development teams are closely aligned. A key way we’ve been able to create this alignment is by having our SREs embedded into domain and product teams. Each domain has an SRE, who is  involved at the beginning stages of product development to ensure that the domain stakeholders are in alignment with the SRE initiatives. As such, SREs are able to improve the reliability, performance, scalability and launch velocity of the services throughout all phases of the service lifecycle. 
3. Adopt one-touch releases
   Our path to production used to contain many manual steps and validations, slowing the rate at which we released features. Additionally, we used to bulk all our releases together to deploy at once, which increased the risk of failure and created a longer feedback loop from production. To tackle this with an SRE mindset, we created a one-touch release process in which SREs review the product team’s pull requests. When approved, this triggers a DevSecOps pipeline that deploys the approved changes to production securely. This process created a safe, reliable and sustainable continuous delivery pipeline with quick feedback loops. Striking the right balance between speed, innovation and stability, we were able to increase our releases exponentially for the year, taking less than 30 minutes per release to deliver quality code, including various automated quality checks and processes, all in just one click. 
4. Embrace capacity planning
   To ensure our services have enough spare capacity to handle any surge in traffic patterns, our SREs emphasize capacity planning, making recommended capacity changes in the continuous delivery (CD) pipeline. They constantly monitor performance to make sure the service is robust, stable and available. And when there’s a sudden surge beyond the forecasted volume, SREs change the capacity on demand and document changes for the performance and domain teams. 

Capacity planning is especially important for us during peak holiday times such as Black Friday and Cyber Monday (BFCM). We lay out our SRE stability plan three months in advance and surface into the domain team’s product roadmap. This way development teams are able to allocate sufficient engineering time to reliability. We do performance testing to ensure the environment is able to sustain increased load over long periods of time and also handle sudden surges in traffic. We also do region failover testing at a global scale to validate the automatic failover duration of service level agreements  (SLAs), SRE and domain readiness. Additionally, we conduct Black Friday and Cyber Monday-specific destructive testing to validate customer experience, reliability and more.

Google Cloud’s Black Friday and Cyber Monday white-glove service played a key role in ensuring our success in both BFCM 2019 and BFCM 2020. This service included on-site visits from Google’s Customer Reliability Engineering (CRE) team who reviewed Lowe’s web architecture, capacity planning, operations practices for event risks, and presented workshops on topics such as incident response best practices. 

Looking ahead

There is always room for improvement, and at Lowe’s we aim to continuously improve our SRE practices. One thing that has worked well for us, which we plan to continue, has been our road shows, where senior SRE leads present to other SREs and application domain teams on the latest SRE principles and best practices, and to get input in real-time from them. 

Google’s tools and methodology have played an instrumental role in helping reshape our SRE practices and better serve our customers. We look forward to building on the momentum and partnership as we continue our SRE journey at Lowe’s. 

If you want to learn more about how to adopt SRE best practices on Google Cloud, check out our documentation. If you want to learn more about Google SRE, visit our website. Stay tuned for the next blogs with Lowe’s discussing how they trained their engineering talent to adopt SRE practices and tooling, and how they improved MTTR using SRE principles.

This April, Gmail will be 18 years old. That’s a big milestone, given that email as a medium just turned 50.

Launched in 2004—with its 1 GB free storage, conversation based grouping, and enhanced search capabilities—Gmail quickly became one of the most popular email services in the world.

What started off as Paul Buchheit’s side project is now part of Google Workspace, a solution that’s used by over 3 billion users. 

Yet despite this growth and Gmail’s long history, the product continues to find new ways to delight its users with great experiences, new features, and constant innovation.  

How does the product team do it? 

To help us unpack this question, I interviewed Matthew Izatt, Product Lead for Gmail.

Matthew has been building and growing Gmail for the last 10+ years. He started off in mobile where he built the Android and iOS apps for Gmail, and eventually he became the lead product owner for all of Gmail’s front end. He also led the development of the new Gmail in 2018, which was a complex rebuild of the technical architecture and visual design, along with the addition of multiple enterprise focused features. Since then, he has been leading Google’s charge on redefining how we work as the product lead for the Workspace Platform and Partnerships efforts with a team of over 100.

What follows is an edited version of our interview. 

Mustafa Kapadia: Matt, thank you for joining us. Now, before we jump into how your team does its magic, can you please share with me some of the challenges you face when you build a new feature or experience on Gmail?

Matthew Izatt: Thanks Mustafa. And I think this is a great place to start.

One of the biggest challenges is that Google Workspace is used by over 3 billion users, and while that is great, there are many different ways of using our product. It’s not like a doorbell, where there is only one way of using it. With Gmail, it’s like an infinite Swiss army knife, where everyone has their own favorite way of using the product.

Second, Gmail is a critical product for many of our users. Yes, it’s fun to use, but people use it to get important work done—sending job proposals, emailing with their kids’ teachers, or booking medical appointments. This is why we have to be careful about what we experiment with and what we roll out. We can’t just throw things out there and see what works. We have to do our homework.

Third, we have to constantly innovate and think outside the box. Email is an old product, but it continues to evolve. Every day we have new startups reinventing email and challenging the big players. If we are to remain a market leader, we literally have to rethink the product every few years. Which is why creating the new Gmail was so much fun. 

Mustafa: I don’t envy you. This is not an easy product to build. Going back to something you touched on: Given these hurdles, how do you build these great experiences? Is there an example that you can share with us?

Matt: A specific example I always like to share is the story of how we came up with the right display density on our thread list. The thread list is your inbox; it’s the list of all the messages that you have. The display density is how that information is presented to you.

In Gmail you can choose to have fewer messages with a lot of information about each message. Or you can choose to see a larger number of messages with much less information about each message.

It really comes down to your preferences. And it’s one of the reasons why so many users like using Gmail. In fact, being able to set inbox display preferences is actually one of the top 10 most used settings within Gmail.

Mustafa: So you were really trying to give users choice on how they would like their information presented?

Matt: Exactly. Now, we could have added 100 different levers so that every user could customize their email feed to an infinite degree. While that is possible from a coding perspective, it’s not practical for three reasons.

First, infinite choice sounds good on paper, but in reality, too many options creates a confusing user experience. Second, development would take many months—maybe even a year. And third, it would be a long-term maintenance nightmare. 

Mustafa: So how did you go about doing it? Share with me the inner workings of Gmail in Google Workspace. How is the sausage made? 

Matt: Well, it came down to four key steps, working closely with our amazing UX Research team.

First came the primary research to find out if building this experience was worth doing. After all, what is the point of building it if no one wants it? For this we actually sat down with real users inside and outside of Google to understand their needs.

Second, we brainstormed 100 potential solutions and narrowed them down to 8 options. Then we mocked up each of the 8 options to see how they looked.

While it would have been easy to just pick the option we liked the most and build it, we wanted to create what our users want, not what we like the most. So we took those options and surveyed the users from step 1 again. We specifically asked them to rank their preferences across three dimensions: Love It, Hate It, or Meh!

Based on the user responses, we realized that 3 configurations would meet the needs of most users. These were the three options we developed and deployed to Google Workplace.

Mustafa: I love how you used data to guide your decision of what to build. This really is Google’s secret sauce—first-hand data collected from users.

Matt: Absolutely. Without their feedback, we would have never been able to narrow down to the 3 options that would satisfy most of our users.

Mustafa: Talking about risks: Getting user feedback and validating before you build is one way to de-risk your product, but you even de-risked your product launch strategy, correct?

Matt: Yes. Sometimes we launch features individually. Sometimes we launch them as a group. In this particular case, we had a lot of moving parts. We had a complete UI redesign, 10 or 12 new features, and architecture changes.

So to de-risk this, we put in place—I kid you not—a 26-stage launch process. We started off with the technical architecture changes—stuff that the user would not notice—to make sure that it was working. And we did it in small increments.

Then we rolled out a few features at a time, launching it first to our early access program—where users have opted in to receive updates. We measured their reaction and satisfaction first, and then moved on to the next group.

At every stage, we kept our blast radius small and put in these checks and balances where we could launch, measure reaction, and then reassess our strategy. And that worked out pretty well for us for this massive launch.

Mustafa: Agreed! Thank you for taking the time to talk to me. And good luck with building the next version of Gmail.

Matt: Thanks for having me.