# Asynchronous development for hybrid remote dev teams | LinearB Blog

> Dev teams went hybrid remote overnight. Asynchronous Development is the new methodology for remote team success.

_This is a markdown rendering of a live HTML page on linearb.io, generated for AI/LLM consumption — it is not a markdown-only site. To get the full HTML page instead, request this URL with an explicit `Accept: text/html` header (no wildcard, no markdown preference)._


```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://linearb.io/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Blog",
      "item": "https://linearb.io/blog"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Asynchronous development for hybrid remote dev teams",
      "item": "https://linearb.io/blog/asynchronous-development"
    }
  ]
}
```

[Home](https://linearb.io/)

/

[Blog](https://linearb.io/blog)

/

Asynchronous development for hybrid remote dev teams

# Asynchronous development for hybrid remote dev teams

![Photo of Dan Lines](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Dan_Lines_3fb5152de2?_a=BAVMn6ID0)

By [Dan Lines](https://linearb.io/blog/asynchronous-development#dan-lines)

|

October 1, 2020

![Screen_Shot_2020_10_01_at_2_32_12_PM_aff2b0768e](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Screen_Shot_2020_10_01_at_2_32_12_PM_aff2b0768e?_a=BAVMn6ID0)

Hope and optimism are default settings for my LinearB co-founder, Ori Keren. For Ori, one silver lining in this tumultuous year is that 2020 ushered in the age of the hybrid remote work model.

_Click here to hear Ori_

“Hybrid remote is how software development teams were always meant to work. It just took 20 years and a global pandemic for us to figure that out.”

Ori believes that, to be highly successful, developers need uninterrupted time to get into a deep state of focus on their task at hand. Getting in “the zone” is hard and when you get interrupted you can’t easily get your deep focus back.

Remote work has eliminated most dev interruptions, right? Not so fast.

Company culture is a powerful force. Like gravity, we don’t see or or think about most days but it effects everything we do.

According to Ori, culture is even more powerful than a global pandemic or a new trend like hybrid remote.   
  
“Working remote was great for our dev team at first. Once we got over the initial disruption of getting equipment and finding a quiet place to work at home, team productivity soared. But then we started noticing our efficiency going down.”

What happened? Our in-the-office culture grabbed hold and brought us right back to where we were in March.   
  
“All of the interruptions crept back in… scheduled meetings, impromptu Zoom status meetings…”   
  
In other words, we were a hybrid remote company with an in-the-office mindset and process.   
  
You can see the effects here in our Cycle Time trend chart.

“Being a remote employee used to be a semi-unique experience that came with a certain level of trust, preparation and experience. Then the entire global dev community went remote at the same time, without preparation or understanding of what needs to change.”  
  
Hybrid remote can be a business advantage for companies embracing it. But only if we adapt our culture and process to make it work.

This is how [Asynchronous Development](https://linearb.io/blog/asynchronous-communication-future) was born.

## What is Asynchronous Development?

Async Dev is an approach to development grounded in asynchronous communication. It works for hybrid remote, full remote and any dev teams that wants to unlock the full creative power of their developers.

Async Dev builds on the foundation Agile put in place. Since the Agile Manifesto was published 20 years ago, software development has gone through some drastic changes. Many of those changes like asynchronous communication tools (e.g. Slack & Teams) becoming the default form of communication and hiring remote developers were forced into the spotlight in 2020.

Ori started wrote the Async Dev manifesto to help engineering and product leaders see how they can change the way they work to turn this new situation into an opportunity.

_**Below Ori explains how Async Dev builds on the Agile and DevOps movements and talk through each of the five core tenets of Async Dev. Listen to the accompanying 60\~ second audio clip from Ori in each section or just read the blog**_.

## The Async Dev Movement

Hybrid remote development is not new, but 2020 accelerated the adoption of many of the practices already in place. As these hybrid remote methods are normalized globally, we also have to accept the way we work, the processes, and the ceremonies have changed as well.

_Click here to hear Ori_

Asynchronous Development acknowledges the importance of movements like Agile and DevOps and offers a new way of looking at development that is a better fit for 2020\. 

## The 5 Tenets of Asynchronous Development

There are 5 core tenets of Async Dev that we have adopted to transform the hybrid remote reality into an opportunity to strengthen the alignment between development and the business.

1. Asynchronous is the default form of communication
2. Git is the central element of your development process
3. Project Management tools are for planning, not status updates
4. Continuous improvement is a daily practice
5. Dev teams are the core of the business

> LinearB built a new kind of project board exclusively for hybrid remote dev teams.
> 
> [Get free DORA Metrics](https://app.linearb.io/sign-up)

## Tenet 1 – Asynchronous is the default form of communication

Click here to listen to ori

Asynchronous communication means using collaboration tools and mentions by default. It helps reduce context switching, avoid unnecessary interruptions, and increases productivity.

After LinearB went full remote back in April of 2020, we analyzed our development team’s metrics to understand exactly how this change effected the productivity and efficiency of the team.

In true Asynchronous fashion, 92% of developers at LinearB were writing more code, while PR sizes and Cycle Times increased. This clearly tells us that fewer interruptions means greater individual productivity. It also clearly shows what we needed to adapt the way worked to the new circumstances if we were going to continue delivering at the same level as pre-wfh.

At LinearB we have started taking a closer look at the function of the daily stand-up and how to use that time to best suit our team. Now that we are a hybrid remote development team with up to the minute updates on issue statuses using LinearB, we use our stand-up time to connect on a personal level, and then just talk about blockers. It’s not perfect, but it’s been a nice adaptation to our new reality.

## Tenet 2 – Git is the central element of your development process

Click here to hear ori

Whether you use GitHub, GitLab, Bitbucket, Azure DevOps or other git flavor, most of the stages of the development cycle either start or involve your git system. [How you choose to configure, deploy and utilize it has a great impact on your dev process](https://linearb.io/blog/git-analytics).

In addition the most up to date status of work progress resides in the git system. Fortunately git was built with open source in mind so most of the phases (coding, review, merge) do not require mandatory synchronous communication and can be executed in different places and different times.

## Tenet 3 – Project Management tools are for planning, not status updates

_Click here to hear Ori_

Whether your team uses Jira, Trello or something else, project management tools are great for planning an iteration or the next week, but trying to use them to enrich dozens of micro decisions that dev teams are taking every day will slow down productivity.

Every update to the work status while in ‘building mode’ should be with dev first in mind, meaning it should automatically reflect the status based on actual git activity and it should mainly serve the people that build and ship the software.

> Does your current project board
> 
> give you more questions than answers?

## Tenet 4 – Continuous improvement is a daily practice

_Click here to hear Ori_

Data should always be accessible to everyone – no gate keepers, not just data engineers, and not just reviewed in meetings by management.

Your KPIs and how you decide to utilized them will define your culture.

Key Principles for Data Usage:

* Team-based data over developer stack ranking
* Measure process over output
* Measure empiric over subjective
* Focus on leading indicators vs. lagging indicators
* Establish baseline data points and trends
* Make sure it’s actionable

Data should be used in an ethical way and cannot replace good managers with good soft skills and human interaction.

> High-risk code & stuck PR Slack Alerts are pretty amazing.
> 
> [Get them Free with LinearB](https://app.linearb.io/sign-up)

## Tenet 5 – Dev teams are the core of the business

_Click here to hear Ori_

The best companies in the world evolved from developers that were highly aligned with business and market needs. Dev-led companies empower developers to make decisions on behalf of customers and the business by giving them context instead of instructions. 

We believe that ‘developers’ and ‘business’ are not disjoint sets and sometimes the most important business decisions are hiding in code lines. That is why the best businesses should focus on pushing context to dev teams, and dev teams should provide transparency into their decision making so both can enjoy a refinement cycle.

This is probably the hardest part of making Async Dev a reality because, as dev leaders, it is the element we have least control over. We need buy-in from throughout the business.

### **Here are 5 practical steps you can take today to start practicing Async Dev:**

#### 1) Cut status updates from your daily stand-up

Instead focus on what matters – who needs help and whether you’re going to ship on time. Async Dev means never spending valuable meeting time on status updates when everyone could take 5 minutes on their own before the meeting to see what happened yesterday and what’s happening today. [Click here to get 16 tips](https://linearb.io/blog/make-daily-better) for how to run a better daily stand-up.

#### 2) Decouple learning and improvement from your retro.

We’re not saying to cancel your retro. Getting together every few weeks to discuss learnings is great. But if you un-gate your team metrics so everyone can see bottlenecks and suggestions for how to improve each day, then improvement can be led everyone on your team (not just managers) and become part of the fabric of your team culture. [Click here to see how to use data in your day-to-day](https://linearb.io/blog/data-driven-dev-team) practices without damaging culture.

#### 3) Combine quantitative signals & qualitative assessments for team health

Use multiple data points to identify signs of overload and burnout. Face to face conversation is not the only way to see if a teammate is struggling. Looking at your WIP balance across the team and consecutive days worked, in combination with 1:1 conversation, can tell you a lot about a person’s work health. [Click here to see which data points can help you measure team health.](https://linearb.io/blog/dev-team-health)

#### 4) Reassess the need of each synchronous meetings.

Can the goals of one or more meetings be met through asynchronous communication? Sometimes your team is in too many meetings. Other times, you just need to tweak your meeting to give developers more blocked off time to work. Sometimes you need to reexamine the need for daily or weekly meetings instead of just attending out of habit. [Click here to read our suggestions for optimizing meetings your meetings for Async Dev.](https://linearb.io/blog/too-many-meetings-a-devs-cry-for-help-5-things-team-leads-can-do)

#### 5) Sign up for your free LinearB account.

We analyze code, Git logs, project issues and team interactions in real-time to give everyone the visibility they need without interrupting developers. Devs get more focus time, dev leads know which people and projects needs their attention and product managers plan and communicate more accurately. [Click here to try LinearB with a free account.](https://app.linearb.io/sign-up)

## Improve developer productivity with LinearB

Find us on

[](https://www.linkedin.com/company/linearb)
[](https://devinterrupted.substack.com/)

## Your next read

[![Cover image for AI as a value multiplier: a human-centric approach to engineering leadership](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Servant_Leadership_2400x1256_0cfd4e2a0c?_a=BAVMn6ID0)](https://linearb.io/blog/ai-as-value-multiplier-human-centric-leadership)

Leadership

[AI as a value multiplier: a human-centric approach to engineering leadership](https://linearb.io/blog/ai-as-value-multiplier-human-centric-leadership)

Super.com's Matt Culver explains why AI should be used as a value multiplier, not a cost-cutter, advocating for a human-centric approach to engineering...

[![Cover image for The Moneyball approach to engineering leadership](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Balancing_Technical_Depth_2400x1256_b56d93a733?_a=BAVMn6ID0)](https://linearb.io/blog/moneyball-approach-engineering-leadership)

Leadership

[The Moneyball approach to engineering leadership](https://linearb.io/blog/moneyball-approach-engineering-leadership)

Rethink engineering leadership with Transcend's Minh Nguyen and learn how to balance hands-on technical work with strategic leadership, communicate with a...

[![Cover image for Strategic lessons from Google on improving engineering teams](https://assets.linearb.io/image/upload/c_limit,w_2560/f_auto/q_auto/v1/Blog_Strategic_Lessons_From_Google_2400x1256_1_cd28b7242d?_a=BAVMn6ID0)](https://linearb.io/blog/strategic-lessons-google-engineering-teams)

Leadership

[Strategic lessons from Google on improving engineering teams](https://linearb.io/blog/strategic-lessons-google-engineering-teams)

Learn key lessons from Google on aligning engineering with business goals, boosting developer productivity, and building sustainable team culture.

## Structured data

_Machine-readable metadata (JSON-LD) embedded in the page for search/AI context — not content rendered on the page itself._

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "LinearB",
  "url": "https://linearb.io/",
  "logo": "https://assets.linearb.io/image/upload/v1715628027/logo-mark-lg.svg",
  "description": "LinearB is the engineering productivity platform that helps engineering leaders prove AI is improving throughput without sacrificing delivery confidence, flow efficiency, or developer experience.",
  "sameAs": [
    "https://www.linkedin.com/company/linearb"
  ],
  "award": [
    {
      "@type": "Award",
      "name": "LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms",
      "dateAwarded": "2026",
      "awardedBy": {
        "@type": "Organization",
        "name": "Gartner®"
      }
    },
    {
      "@type": "Award",
      "name": "Great Place to Work Certification",
      "dateAwarded": "2025-2027",
      "awardedBy": {
        "@type": "Organization",
        "name": "Great Place to Work"
      }
    },
    {
      "@type": "Award",
      "name": "America's Best Startup Employers 2025",
      "dateAwarded": "2025",
      "awardedBy": {
        "@type": "Organization",
        "name": "Forbes Magazine"
      }
    }
  ],
  "hasCertification": [
    {
      "@type": "Certification",
      "name": "SOC 1 Type 2"
    },
    {
      "@type": "Certification",
      "name": "SOC 2 Type 2"
    },
    {
      "@type": "Certification",
      "name": "GDPR Compliance certification"
    },
    {
      "@type": "Certification",
      "name": "ISO 27001"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Asynchronous development for hybrid remote dev teams",
  "url": "https://linearb.io/blog/asynchronous-development",
  "author": {
    "@type": "Person",
    "name": "Dan Lines"
  },
  "datePublished": "2020-10-01T11:05:00.000Z",
  "dateModified": "2020-10-01T11:05:00.000Z",
  "image": "https://assets.linearb.io/image/upload/v1720000000/Screen_Shot_2020_10_01_at_2_32_12_PM_aff2b0768e.png",
  "publisher": {
    "@type": "Organization",
    "name": "LinearB",
    "logo": "https://assets.linearb.io/image/upload/v1777485755/linearb-logo-2026.png"
  },
  "description": "Dev teams went hybrid remote overnight. Asynchronous Development is the new methodology for remote team success.\n"
}
```

## More on linearb.io

### Top navigation

- [Book a Demo](https://linearb.io/book-a-demo)
- [AI Code Reviews — Catch security risks, bugs, and spec mismatches](https://linearb.io/platform/ai-code-reviews)
- [AI & Productivity Insights — See how AI tools affect cycle time and delivery speed](https://linearb.io/platform/ai-developer-productivity-insights)
- [Measure AI Impact — Track AI adoption and tie it to delivery outcomes](https://linearb.io/use-case/measure-ai-impact)
- [MCP Server — Chat with your data to spot patterns and boost output](https://linearb.io/platform/mcp-server)
- [Resource Allocation — Cost initiatives and shape your investment strategy](https://linearb.io/platform/resource-allocation)
- [Cost Capitalization — Capitalize engineering costs with audit-ready reports](https://linearb.io/platform/cost-capitalization)
- [Dev Team Management — Set targets and tie throughput to business outcomes](https://linearb.io/platform/goals-and-reporting)
- [DevOps Workflow Automation — Policy-based PR routing, approvals, and tests](https://linearb.io/platform/ai-workflow-governance)
- [AI Powered Support — Unify AI and human code delivery in one clear view](https://linearb.io/use-case/ai-powered-support)
- [Optimization — Surface friction with feedback and MCP insights](https://linearb.io/platform/developer-experience)
- [Reporting — Spot what's working and what needs attention](https://linearb.io/use-case/measuring-developer-experience)
- [Surveys — Turn developer feedback into actionable signals](https://linearb.io/platform/developer-surveys)
- [Platform overview](https://linearb.io/platform/overview)
- [Register now](https://linearb.io/event/engineering-productivity-gap)
- [Customers](https://linearb.io/customers)
- [Pricing](https://linearb.io/pricing)
- [Why choose LinearB — Explore your data. Measure performance. Act to improve it.](https://linearb.io/why-linearb)
- [APEX framework — The operating model for AI-era engineering teams](https://linearb.io/resources/apex-framework)
- [Anti-FAQ — The questions other vendors won't answer](https://linearb.io/why-linearb/anti-faq)
- [Security — Enterprise-grade compliance and zero code access](https://linearb.io/security)
- [Build vs. buy — The hidden cost of building it yourself](https://linearb.io/resources/build-vs-buy)
- [Dev Interrupted Podcast — Conversations with engineering leaders](https://linearb.io/dev-interrupted/podcasts)
- [Reports & Guides — Deep dives on productivity and delivery](https://linearb.io/resources)
- [Webinars — Expert sessions on productivity and AI](https://linearb.io/resources?category=workshops)
- [Metrics Benchmarks — See how your engineering org stacks up](https://linearb.io/resources/software-engineering-benchmarks-report)
- [Blog — Product updates and practical insights](https://linearb.io/blog)
- [Help Center — Documentation, setup, and support](https://linearb.helpdocs.io)
- [API Docs](https://docs.linearb.io/api-overview)
- [Status](https://www.linearbstatus.com/)
- [Integrations](https://linearb.io/integrations)
- [LinearB Library](https://linearb.io/library)
- [Engineering metrics](https://linearb.io/library/engineering-metrics)
- [Platform engineering](https://linearb.io/library/platform-engineering)
- [Engineering glossary](https://linearb.io/library/engineering-glossary)
- [Developer productivity](https://linearb.io/library/developer-productivity)
- [AI in software development](https://linearb.io/library/ai-in-software-development)
- [Engineering management](https://linearb.io/library/engineering-management)
- [Developer experience](https://linearb.io/library/developer-experience)
- [DevOps](https://linearb.io/library/devops)
- [Engineering operations and the context layer](https://linearb.io/library/engineering-operations)
- [Engineering efficiency](https://linearb.io/library/engineering-efficiency)
- [Software delivery](https://linearb.io/library/software-delivery)
- [Research and data](https://linearb.io/library/engineering-benchmarks-and-research)
- [LinearB is a Leader in the 2026 Gartner® Magic Quadrant™ for Developer Productivity Insight Platforms](https://linearb.io/resources/gartner-magic-quadrant-dpi-platforms-2026)
- [Sign in](https://app.linearb.io/login)
- [Enterprise](https://linearb.io/solutions/enterprise)
- [Contact](https://linearb.io/contact-us)
- [About us](https://linearb.io/about-us)
- [Careers](https://linearb.io/careers)
- [Service agreement](https://linearb.io/services-agreement)
- [Privacy policy](https://linearb.io/privacy-policy)
- [DPA](https://linearb.io/data-processing-agreement)
- [Security FAQ](https://linearb.io/security-faq)
- [Substack](https://devinterrupted.substack.com/)

### Footer

_Additional links from the site footer, not repeated from the top navigation above._

- [GitHub](https://github.com/linear-b)
- [LinkedIn](https://www.linkedin.com/company/linearb)
- [Twitter](https://twitter.com/LinearB_Inc)