November 8, 2024

November 8, 2024

November 8, 2024

Is remote work the silent killer of tech productivity?

Is remote work the silent killer of tech productivity?

Is remote work the silent killer of tech productivity?

A remote team in retail tech operated at 79% of their in-office productivity, highlighting how remote work affects performance differently across teams. Factors like team size and structure significantly influence outcomes, underscoring the need for data-driven insights. Using a Stanford-developed algorithm, we objectively measured productivity by analyzing the functional impact of source code changes.

A remote team in retail tech operated at 79% of their in-office productivity, highlighting how remote work affects performance differently across teams. Factors like team size and structure significantly influence outcomes, underscoring the need for data-driven insights. Using a Stanford-developed algorithm, we objectively measured productivity by analyzing the functional impact of source code changes.

A remote team in retail tech operated at 79% of their in-office productivity, highlighting how remote work affects performance differently across teams. Factors like team size and structure significantly influence outcomes, underscoring the need for data-driven insights. Using a Stanford-developed algorithm, we objectively measured productivity by analyzing the functional impact of source code changes.

Yegor Denisov-Blanch

Yegor Denisov-Blanch

Yegor Denisov-Blanch

Content

Content

Content

2 mins

2 mins

2 mins

After going remote, this team operated at just 79% of their in-office productivity levels – contrasting sharply with our case study published two weeks ago.

This calls into question the effectiveness of remote work for some teams' performance.

Our ongoing research indicates that several factors can affect a team's remote work productivity. Team size appears to be key.


Given the variability we see among even similar teams, the best approach is to examine your own productivity data.

Snapshot of Our Study:
- Period Analyzed: Feb 2019 – Mar 2022
- Industry: Retail Tech
- Service: Shopping Rewards Platform
- Team Size: 18 Developers
- Languages: PHP, JS
- Location Pre-COVID: Silicon Valley, USA
- Location Post-COVID: Dispersed, USA

Methodology:
Leveraging a cutting-edge algorithm developed at Stanford, we can objectively measure a developer's productivity based on the functionality of their source code. This algorithm scans through Git & code repositories, quantifies the functionality of the code, and generates an impartial metric for both individual developers and teams, irrespective of programming language or coding style.

Dive Deeper:
For a comprehensive breakdown of our case study, click the link in the comments.

About Our Mission:
This is part of a Stanford research initiative aimed at quantifying software engineering output.

The goal? To enable data-driven decisions in engineering organizations.

Our research participants harness our groundbreaking algorithm's insights for pivotal decisions - be it work models, team structure, outsourcing, or tool adoption.

Similar Insights

Similar Insights

Similar Insights

Logo

Objective Productivity Data for Smarter Engineering Team Decisions

Let's talk

Logo

Objective Productivity Data for Smarter Engineering Team Decisions

Let's talk

Logo

Objective Productivity Data for Smarter Engineering Team Decisions

Let's talk

Logo

Objective Productivity Data for Smarter Engineering Team Decisions

Let's talk

Logo

Objective Productivity Data for Smarter Engineering Team Decisions

Let's talk