<?xml version="1.0" encoding="UTF-8"?>
<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-10-05T21:32:42Z</responseDate>
  <request identifier="27975" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:27975</identifier>
        <datestamp>2026-10-05T06:44:02Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Characterising Meeting Practices in Software Engineering Teams: A Mixed-Methods Study of Perceptions, Objective Patterns, and Impacts</dc:title>
          <dc:creator>Patkar, Nitish</dc:creator>
          <dc:creator>Isenegger, Xeno</dc:creator>
          <dc:creator>Monterosa, Gideon</dc:creator>
          <dc:creator>Panichella, Sebastiano</dc:creator>
          <dc:creator>Seyff, Norbert</dc:creator>
          <dc:subject>Software engineering</dc:subject>
          <dc:subject>Meeting practices</dc:subject>
          <dc:subject>Productivity</dc:subject>
          <dc:subject>Flow (deep work)</dc:subject>
          <dc:subject>Well-being</dc:subject>
          <dc:subject>Experience sampling method (ESM)</dc:subject>
          <dc:description>Background. Meetings are an integral part of software practitioners' workday, but many practitioners see them as disruptive to focused work and productivity. Prior research has mainly focused on overall meeting load and broad perceptions; however, teams cannot effectively improve meeting practices without knowing which specific meeting patterns cause disruption. &#13;
&#13;
Aims. Our core aim is to move from general perceptions to an empirical investigation of meeting characteristics that are strongly linked to productivity, flow, and well-being. &#13;
&#13;
Method. We conducted a two-phase mixed-method study. In Phase 1, we surveyed 55 software practitioners to establish a baseline of meeting practices and perceived impact on productivity, flow, and well-being. In Phase 2, a two-week field study with experience sampling collected real-time post-meeting ratings (usefulness, energy, focus disruption) and daily end-of-day reports, complemented by objective meeting characteristics extracted automatically from calendar metadata (135 post-meeting and 40 end-of-day records). &#13;
&#13;
Results. In the baseline survey, 61.8% reported at least moderate flow disruption and 76.4% lower productivity on high-meeting days, with unclear purpose and excessive duration as the top frustrations. The field study revealed a more nuanced pattern: overall usefulness was moderately positive, but varied by type - ad-hoc meetings were among the most useful (Mdn = 4), planning meetings were most disruptive (Mdn = 4), and one-on-ones were least disruptive (Mdn = 1). Type contrasts are exploratory and based on small sample. At the daily level, higher meeting counts coincided with lower productivity and deep-work ratings; energy was lowest on high-meeting days. This daily pattern reflected between-participant differences rather than within-person day-to-day effects. The directional alignment between survey complaints and real-time observations strengthens confidence in these emerging patterns. &#13;
&#13;
Conclusions. This study shifts the conversation from broad dissatisfaction with meetings toward identifiable and actionable meeting patterns that organizations can actively redesign. The findings suggest that not all meetings are equally harmful-or beneficial-and that factors such as meeting purpose clarity, duration, and scheduling context may play a critical role in shaping employees’ productivity, ability to sustain flow, and daily energy levels. We treat these patterns as design hypotheses pending larger confirmation. They also provide an empirical starting point for longitudinal research on meeting design.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Nitish Patkar and Xeno Isenegger and Gideon Monterosa and Sebastiano Panichella and Norbert Seyff</dc:contributor>
          <dc:date>2026</dc:date>
          <dc:relation>Is Part Of LIPIcs, Volume 394, 20th International Symposium on Empirical Software Engineering and Measurement (ESEM 2026)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/LIPIcs.ESEM.2026.7</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-279754</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/LIPIcs.ESEM.2026.7</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by/4.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
