<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-18T21:57:54Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/146706" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/146706</identifier><datestamp>2022-12-01T03:01:17Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor">Welsch, Roy E.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="advisor">Boning, Duane S.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author">Tindall, Andrew J.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Electrical Engineering and Computer Science</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Sloan School of Management</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2022-11-30T19:42:37Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2022-11-30T19:42:37Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued">2022-05</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="submitted">2022-08-25T19:15:50.678Z</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://hdl.handle.net/1721.1/146706</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="orcid">0000-0002-9206-783X</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract">Hybrid work is a coordination problem at heart—how frequently and on which days of the week should hybrid employees come into the office? The COVID-19 pandemic accelerated a remote work revolution and caused the hybrid model—where employees split time between in-office and remote work—to become the norm as employees return to the office in 2022 and beyond. The shift to fully remote work during the pandemic highlighted numerous remote work benefits. To name a few, zero commute cost, more focus time and more flexibility. The challenge is that remote collaboration is more difficult and time consuming to orchestrate—potentially decreasing innovation. &#xd;
&#xd;
Acknowledging that remote and in-person work have different, and at many times complementary goals, our study tests whether employee collaboration data can help organizations solve the coordination problem inherent in hybrid work. We find that collaboration data can align work groups to maximize in-person collaboration gains while minimizing the number of days in office per week. We use data to recommend the optimal in-office frequency and find that offices will be 60% under capacity when employees return. Most importantly, we think about offices as networks—the value of being in the office scales non-linearly as users increase. We find that organizations can use collaboration data to model employee networks and appropriately align work communities. Ultimately, we develop a scheduling system that will help stabilize office space demand in 2022 and beyond.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree">M.B.A.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree">S.M.</dim:field>
   <dim:field mdschema="dc" element="publisher">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights">In Copyright - Educational Use Permitted</dim:field>
   <dim:field mdschema="dc" element="rights">Copyright retained by author(s)</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri">https://rightsstatements.org/page/InC-EDU/1.0/</dim:field>
   <dim:field mdschema="dc" element="title">Analytics to Make Hybrid Work, Work</dim:field>
   <dim:field mdschema="dc" element="type">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="mit" element="thesis" qualifier="degree">Master</dim:field>
   <dim:field mdschema="thesis" element="degree" qualifier="name">Master of Business Administration</dim:field>
   <dim:field mdschema="thesis" element="degree" qualifier="name">Master of Science in Electrical Engineering and Computer Science</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="f0ef74ea-14ac-456c-be8d-b6f0cd78107b">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
   	&lt;Title>Analytics to Make Hybrid Work, Work&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2022-05&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Tindall, Andrew J.&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>https://rightsstatements.org/page/InC-EDU/1.0/&lt;/License>
   	&lt;Abstract>Hybrid work is a coordination problem at heart—how frequently and on which days of the week should hybrid employees come into the office? The COVID-19 pandemic accelerated a remote work revolution and caused the hybrid model—where employees split time between in-office and remote work—to become the norm as employees return to the office in 2022 and beyond. The shift to fully remote work during the pandemic highlighted numerous remote work benefits. To name a few, zero commute cost, more focus time and more flexibility. The challenge is that remote collaboration is more difficult and time consuming to orchestrate—potentially decreasing innovation. &#xd;
&#xd;
Acknowledging that remote and in-person work have different, and at many times complementary goals, our study tests whether employee collaboration data can help organizations solve the coordination problem inherent in hybrid work. We find that collaboration data can align work groups to maximize in-person collaboration gains while minimizing the number of days in office per week. We use data to recommend the optimal in-office frequency and find that offices will be 60% under capacity when employees return. Most importantly, we think about offices as networks—the value of being in the office scales non-linearly as users increase. We find that organizations can use collaboration data to model employee networks and appropriately align work communities. Ultimately, we develop a scheduling system that will help stabilize office space demand in 2022 and beyond.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>