Data reports · Edition 01 · June 2024 — August 2026

How teams build

Tens of thousands of teams run product development inside Linear. Two years of that telemetry — from the first issue to the pull request that closes it — trace how AI actually changed software work. This is that story in nine charts, reinterpreted for everyone, not just engineers.

Based on Linear’s data report Analysis: Tim Qi, Head of Data 9 datasets · Paid workspaces only
  • AI adoption doubled in every function in six months → chart 01
  • 9% → 36%AI-active CEOs at 201+-person companies, Jan → Jun 2026 → chart 02
  • ≈ ½of all issues created in Linear are now written by AI → the crossover
  • +111%pull requests per workspace versus June 2024 → chart 08

Read it in three acts

Linear sees the whole workflow behind building a product — the issue, the plan, the pull request — which makes this a rare window into the work itself rather than just token counts and code volume. The report answers three questions across that window: who is using AI, how it reshapes where teams spend their time, and whether it changes how much they ship.

One honest caveat, up front: everything here is measured inside Linear’s own paid customer base, not the market at large, and AI use outside the product is invisible to it. Read this as a fixed point to measure the next edition against — not a census.

  1. Act I — Adoption · who’s using AI
  2. 01Adoption by functionslope
  3. 02By executive teamslope
  4. 03By company sizeslope
  5. Act II — Application · how work moves
  6. 04Creating & organizingbars
  7. The crossover: AI-written issues2 yrs weekly
  8. 05Planningbars
  9. 06The new AI layerbars
  10. Act III — Output · what teams ship
  11. 07Non-engineer PRsslope
  12. 08Total pull requests2 yrs weekly
  13. 09Coding-agent cohorts2 yrs weekly

Act I · Adoption

AI adoption didn’t trickle. It landed everywhere at once.

The first question is simple: who’s actually using this stuff? Between January and June 2026, the honest answer became — everyone, in every role, at every level, at every company size.

Chart 01 · Adoption

Adoption doubled in every function — in one half-year

Between January and June 2026 the share of users active on Linear’s AI features more than doubled everywhere. Product climbed fastest, 12% to 34%. Even go-to-market — the function furthest from the codebase — went from 5% to 18%. Roles are classified by normalizing job titles, which adds noise at the edges, but the pattern is far too broad to be a labeling artifact.

How to read slope charts: each row is one group. The hollow dot is January 2026, the filled dot June 2026, and the pill at right nets the change in percentage points. Hover, tap, or use arrow keys for exact numbers; a full table sits under every chart.

Percentage of users active on Linear AI features (last 30 days), by function

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 127,000 paid users, active in both January and June 2026 Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — AI-adoption share by function, January vs June 20265 rows
AI-adoption share by function, January vs June 2026
Segment Jan 2026 Jun 2026 Change
Founder14%30%+16pp
Engineering12%30%+18pp
Product12%34%+22pp
Design6%22%+16pp
GTM5%18%+13pp

The read: no laggards. The slowest function (GTM +13pp) still nearly quadrupled. When the floor moves this fast, adoption is a property of the tooling, not the team.

Chart 02 · Adoption

The corner office went hands-on

Executives are personally active on AI at rates that match or beat their teams. CEOs at companies of 201+ people posted the largest jump of any cut in this report — 9% to 36% in six months — suggesting the most senior leaders are learning the technology by using it rather than reading about it. Company size comes from third-party enrichment, so this cut covers a smaller cohort than the rest of the report.

Percentage of users active on Linear AI features (last 30 days), by executive team and company size

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 13,300 executives, active in both January and June 2026 Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — AI-adoption share by executive role and company size, January vs June 202612 rows
AI-adoption share by executive role and company size, January vs June 2026
Segment Jan 2026 Jun 2026 Change
Founder, 201+10%26%+16pp
Founder, 51-20015%27%+12pp
Founder, 1-5015%31%+16pp
CEO, 201+9%36%+27pp
CEO, 51-20015%25%+11pp
CEO, 1-507%21%+14pp
CPO, 201+3%24%+21pp
CPO, 51-20010%26%+15pp
CPO, 1-5011%36%+25pp
CTO, 201+11%35%+24pp
CTO, 51-20012%28%+16pp
CTO, 1-5016%33%+17pp

The read: leadership isn’t delegating their AI curiosity. Every single executive row grew by double-digit points — CEOs of large companies 4×-ed their usage in half a year.

Chart 03 · Adoption

Company size barely matters

Normally, size is one of the best predictors of how fast an organization adopts new technology. Not here: adoption roughly tripled at enterprises and scrappy startups alike. Whatever is pulling people to AI, it isn’t filtered by org chart depth.

Percentage of users active on Linear AI features (last 30 days), by company size

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 199,000 paid users with a known company size, active in both January and June 2026 Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — AI-adoption share by company size (full-time employees), January vs June 20264 rows
AI-adoption share by company size (full-time employees), January vs June 2026
Segment Jan 2026 Jun 2026 Change
1001+ FTE8%25%+17pp
201-1000 FTE9%27%+19pp
51-200 FTE9%25%+16pp
1-50 FTE8%23%+14pp

The read: the four rows are nearly on top of each other — 23–27% by June. AI adoption in 2026 behaves like infrastructure, not innovation.

Act II · Application

The shape of the work is bending around AI.

Adoption is the who. The how is more specific: teams pour more coordination into the system, AI starts writing half of what gets tracked, planning time stubbornly holds still — and a brand-new layer of work appears on top of everything.

Chart 04 · Application

Teams are putting more into the system

Time spent creating, triaging, assigning, updating and commenting rose in nearly every function between June 2025 and June 2026 — engineering alone is up roughly 17% on creation and triage. Founders swing hardest (+17 min creating, +26 min commenting a month), though theirs is a smaller, noisier cohort. More work needs more coordination — and that coordination increasingly becomes the context agents act on.

How to read these bars: hatched bars are June 2025, violet June 2026, grouped by activity. The number above each pair is the change in minutes. Legend chips can hide a series — and if you hide both, an empty state tells you how to bring the chart back.

Average minutes per user per month — June 2025 vs June 2026, by function

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 54,300 paid users (Jun 2025) → 89,000 (Jun 2026) Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — Minutes per user per month on creating and organizing work, by function15 rows
Minutes per user per month on creating and organizing work, by function
Segment Jun 2025 Jun 2026 Change
Create & triage, Eng24 min28 min+5m
Create & triage, Product38 min37 min-1m
Create & triage, Design22 min25 min+3m
Create & triage, GTM27 min31 min+4m
Create & triage, Founder40 min57 min+17m
Assign & update, Eng16 min19 min+3m
Assign & update, Product26 min26 min0m
Assign & update, Design12 min15 min+3m
Assign & update, GTM12 min15 min+3m
Assign & update, Founder22 min29 min+7m
Comment, Eng35 min40 min+5m
Comment, Product48 min49 min+1m
Comment, Design32 min34 min+2m
Comment, GTM49 min55 min+6m
Comment, Founder39 min64 min+26m

The read: only one bar in the whole chart sank (product create & triage, −1m). Everything else moved up — the system of record is being fed, not bypassed.

Exhibit · Two years, weekly

The crossover: AI now writes nearly half of all issues

Two years ago, fewer than one issue in a thousand came from AI. This week in August 2026, agents and MCP clients authored 2,435 issues against 2,481 from people and integrations combined. At the current pace, AI will soon write the majority of everything tracked in Linear.

How to read the time charts: solid violet is the AI series, dashed amber the human one — styles never rely on color alone. Hover or use arrow keys to walk week by week; the legend toggles each series; end labels carry the final values so screenshots still read clearly.

Issues created per week by source — June 2024 to August 2026 (excludes imported issues)

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 114 weekly observations · excludes imported issues Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — Issues created per week by source, June 2024 – August 2026114 rows
Issues created per week by source, June 2024 – August 2026
Week of Agents & MCP People & integrations
2024-06-030605
2024-06-100599
2024-06-170582
2024-06-240689
2024-07-010602
2024-07-080628
2024-07-151621
2024-07-220627
2024-07-291650
2024-08-050654
2024-08-121624
2024-08-190660
2024-08-261650
2024-09-021670
2024-09-091690
2024-09-161692
2024-09-231725
2024-09-300696
2024-10-071726
2024-10-141724
2024-10-211741
2024-10-281721
2024-11-041760
2024-11-110760
2024-11-181795
2024-11-251677
2024-12-021765
2024-12-091800
2024-12-161770
2024-12-230373
2024-12-300460
2025-01-061825
2025-01-131878
2025-01-201869
2025-01-271920
2025-02-031930
2025-02-101924
2025-02-171890
2025-02-241934
2025-03-031942
2025-03-101974
2025-03-173971
2025-03-243984
2025-03-311985
2025-04-071999
2025-04-141974
2025-04-211994
2025-04-2831,029
2025-05-0551,037
2025-05-1271,063
2025-05-1991,042
2025-05-2611992
2025-06-02181,095
2025-06-09181,074
2025-06-16281,064
2025-06-23341,148
2025-06-30351,092
2025-07-07441,166
2025-07-14401,137
2025-07-21411,164
2025-07-28451,177
2025-08-04521,171
2025-08-11501,206
2025-08-18551,177
2025-08-25471,225
2025-09-01481,200
2025-09-08461,299
2025-09-15451,272
2025-09-22451,294
2025-09-29581,338
2025-10-06621,352
2025-10-13681,350
2025-10-20651,382
2025-10-27741,414
2025-11-03851,461
2025-11-10851,457
2025-11-17911,436
2025-11-24931,299
2025-12-011221,473
2025-12-081421,487
2025-12-151471,526
2025-12-22110795
2025-12-29139808
2026-01-052061,601
2026-01-122731,725
2026-01-192911,721
2026-01-263231,806
2026-02-024011,897
2026-02-094511,901
2026-02-165161,875
2026-02-235992,048
2026-03-027072,123
2026-03-097942,170
2026-03-168372,106
2026-03-239162,297
2026-03-309352,104
2026-04-061,0382,063
2026-04-131,1282,297
2026-04-201,2092,173
2026-04-271,2752,185
2026-05-041,3822,238
2026-05-111,5062,278
2026-05-181,5972,271
2026-05-251,4722,132
2026-06-011,5422,270
2026-06-081,7662,371
2026-06-151,6522,256
2026-06-221,7282,372
2026-06-291,7992,265
2026-07-062,0782,532
2026-07-132,1432,465
2026-07-202,1952,396
2026-07-272,3482,357
2026-08-032,4352,481

The read: watch the violet line cross the dashed amber one. Around July 2026 they meet — from ~0 to half of all intake in 26 months.

Chart 05 · Application

Planning time didn’t move — and that’s the data

In a year when nearly everything else in this report moved, time on customer requests, docs and projects held steady. Planning practice varies wildly between teams and much of it happens in conversation before it lands anywhere, so the average blends heavy planners with light ones. What the flatness suggests: AI has so far changed how teams execute far more than how they decide what to build.

Average minutes per user per month — June 2025 vs June 2026, by function

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 54,300 paid users (Jun 2025) → 89,000 (Jun 2026) Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — Minutes per user per month on planning surfaces, by function10 rows
Minutes per user per month on planning surfaces, by function
Segment Jun 2025 Jun 2026 Change
Customer requests, Eng1 min1 min0m
Customer requests, Product3 min4 min0m
Customer requests, Design1 min1 min0m
Customer requests, GTM4 min4 min+1m
Customer requests, Founder2 min3 min+1m
Docs & projects, Eng3 min3 min+1m
Docs & projects, Product13 min14 min+1m
Docs & projects, Design4 min5 min+1m
Docs & projects, GTM3 min3 min+1m
Docs & projects, Founder7 min8 min0m

The read: every change rounds to 0–1 minutes. Whatever AI is doing to software work, it hasn’t (yet) touched how long teams spend deciding what the work even is.

Chart 06 · Application

A new layer of work appeared out of nowhere

Chatting with AI and delegating issues to agents are categories of work that didn’t measurably exist a year ago. Both now show up in every function’s month, with product leaning in hardest (5 min chatting). And critically — nothing else shrank to make room. AI landed on top of the job, not instead of it.

Average minutes per user per month on AI-layer activities — June 2025 vs June 2026, by function

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 54,300 paid users (Jun 2025) → 89,000 (Jun 2026) Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — Minutes per user per month on AI chat and agent issues, by function10 rows
Minutes per user per month on AI chat and agent issues, by function
Segment Jun 2025 Jun 2026 Change
Agent issues, Eng0 min1 min+1m
Agent issues, Product0 min1 min+1m
Agent issues, Design0 min0 min0m
Agent issues, GTM0 min0 min0m
Agent issues, Founder0 min2 min+2m
Chat with AI, Eng0 min2 min+2m
Chat with AI, Product0 min5 min+5m
Chat with AI, Design0 min3 min+3m
Chat with AI, GTM0 min3 min+3m
Chat with AI, Founder0 min4 min+4m

The read: zero to 1–5 minutes per person per month, everywhere, in twelve months. Small numbers — but they measure a category that was exactly 0 before, growing on top of an unchanged workload.

Act III · Output

More builders. More builds. One cohort pulling away.

The last question: does any of this change what ships? Three views — who’s attaching pull requests, how many pull requests exist at all, and which teams are doing the accelerating.

Chart 07 · Output

Non-engineers are shipping code now

The share of product managers attaching pull requests rose from 3% to 10% in two years; designers went 1% to 8%. Only PRs in repositories connected to Linear count, so these numbers are floors, not ceilings. The people who used to describe a change increasingly ship it themselves.

Percentage of users who attached a pull request (last 30 days), by function

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 166,000 paid users (June 2026) Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — Share of users attaching a pull request, by function, June 2024 / 2025 / 20265 rows
Share of users attaching a pull request, by function, June 2024 / 2025 / 2026
Segment Jun 2024 Jun 2025 Jun 2026 Change (2 yrs)
Founder11%12%23%+12pp
Engineering20%22%34%+14pp
Product3%3%10%+7pp
Design1%2%8%+7pp
GTM1%1%3%+2pp

The read: every function’s line rises — but note the slopes steepen after 2025. Designers 8×-ed their shipping share as coding agents went mainstream.

Chart 08 · Output

Pull requests are up 111% in two years

Pull requests opened per paid workspace held roughly level for the first twelve months — then bent upward through 2026 as model quality and adoption climbed together. The count is PRs opened, not merged, and an opened PR says nothing about the change’s value. But the inflection is hard to miss.

Weekly change in pull requests per workspace versus the June 2024 baseline

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 47,900 paid workspaces (June 2026) Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — Weekly PR volume change versus June 2024 baseline, all paid workspaces108 rows
Weekly PR volume change versus June 2024 baseline, all paid workspaces
Week of Change vs Jun 2024
2024-06-020%
2024-06-09+9%
2024-06-16+10%
2024-06-23+3%
2024-06-30+8%
2024-07-07-4%
2024-07-14+8%
2024-07-21+7%
2024-07-28+8%
2024-08-04+7%
2024-08-11+6%
2024-08-18+3%
2024-08-25+10%
2024-09-01+10%
2024-09-08+5%
2024-09-15+12%
2024-09-22+10%
2024-09-29+14%
2024-10-06+8%
2024-10-13+11%
2024-10-20+9%
2024-10-27+18%
2024-11-03+8%
2024-11-10+15%
2024-11-17+11%
2024-11-24+17%
2024-12-010%
2024-12-08+16%
2024-12-15+17%
2024-12-22+10%
2024-12-29-58%
2025-01-05-50%
2025-01-12+6%
2025-01-19+15%
2025-01-26+13%
2025-02-02+15%
2025-02-09+19%
2025-02-16+21%
2025-02-23+17%
2025-03-02+21%
2025-03-09+19%
2025-03-16+26%
2025-03-23+26%
2025-03-30+23%
2025-04-06+17%
2025-04-13+24%
2025-04-20+11%
2025-04-27+10%
2025-05-04+7%
2025-05-11+14%
2025-05-18+21%
2025-05-25+22%
2025-06-01+9%
2025-06-08+22%
2025-06-15+16%
2025-06-22+12%
2025-06-29+22%
2025-07-06+8%
2025-07-13+16%
2025-07-20+16%
2025-07-27+16%
2025-08-03+13%
2025-08-10+9%
2025-08-17+5%
2025-08-24+10%
2025-08-31+8%
2025-09-07+4%
2025-09-14+11%
2025-09-21+10%
2025-09-28+8%
2025-10-05+9%
2025-10-12+9%
2025-10-19+9%
2025-10-26+9%
2025-11-02+14%
2025-11-09+15%
2025-11-16+13%
2025-11-23+16%
2025-11-30+1%
2025-12-07+17%
2025-12-14+17%
2025-12-21+14%
2025-12-28-48%
2026-01-04-54%
2026-01-11+10%
2026-01-18+22%
2026-01-25+22%
2026-02-01+27%
2026-02-08+32%
2026-02-15+36%
2026-02-22+33%
2026-03-01+50%
2026-03-08+49%
2026-03-15+54%
2026-03-22+55%
2026-03-29+58%
2026-04-05+41%
2026-04-12+46%
2026-04-19+60%
2026-04-26+66%
2026-05-03+67%
2026-05-10+80%
2026-05-17+91%
2026-05-24+95%
2026-05-31+85%
2026-06-07+106%
2026-06-14+113%
2026-06-21+111%

The read: a year of noise around the baseline, then a staircase: +50% by March 2026, +111% by June. Something structurally changed in early 2026.

Chart 09 · Output

Coding agents account for most of the acceleration

A fixed cohort of teams with a coding agent connected went from 21 to 65 pull requests a week — nearly a tripling. Teams without one went from 8 to 10. The levels aren’t directly comparable — agent-linked teams were higher-output before agents existed — but each cohort against its own baseline tells a clean story: nearly all the growth sits on the agent side.

Pull requests per team per week — fixed cohorts, June 2024 to June 2026

Rendering chart… the data table below shows the same numbers.

All series are hidden. Select a series in the legend to bring the chart back.
N = 6,887 paid teams (4,280 with coding agents, 2,607 without) Data: Linear — How Teams Build, Edition 01 (Tim Qi, 2026)
Data table — Average PRs per workspace per week, coding-agent cohort versus traditional cohort108 rows
Average PRs per workspace per week, coding-agent cohort versus traditional cohort
Week of Coding-agent teams Traditional teams
2024-06-02218
2024-06-09248
2024-06-16249
2024-06-23228
2024-06-30249
2024-07-07218
2024-07-14248
2024-07-21248
2024-07-28249
2024-08-04248
2024-08-11248
2024-08-18238
2024-08-25258
2024-09-01248
2024-09-08248
2024-09-15259
2024-09-22258
2024-09-29269
2024-10-06259
2024-10-13268
2024-10-20258
2024-10-27269
2024-11-03258
2024-11-10279
2024-11-17268
2024-11-24289
2024-12-01238
2024-12-08279
2024-12-15289
2024-12-22268
2024-12-29103
2025-01-05114
2025-01-12258
2025-01-19279
2025-01-26278
2025-02-02288
2025-02-09299
2025-02-16309
2025-02-23299
2025-03-02309
2025-03-09309
2025-03-16309
2025-03-23319
2025-03-30319
2025-04-06308
2025-04-13329
2025-04-20288
2025-04-27288
2025-05-04288
2025-05-11298
2025-05-18329
2025-05-25319
2025-06-01288
2025-06-08318
2025-06-15318
2025-06-22308
2025-06-29328
2025-07-06298
2025-07-13328
2025-07-20318
2025-07-27328
2025-08-03328
2025-08-10328
2025-08-17317
2025-08-24338
2025-08-31328
2025-09-07318
2025-09-14348
2025-09-21348
2025-09-28348
2025-10-05358
2025-10-12348
2025-10-19348
2025-10-26348
2025-11-02368
2025-11-09368
2025-11-16358
2025-11-23378
2025-11-30317
2025-12-07378
2025-12-14388
2025-12-21378
2025-12-28163
2026-01-04133
2026-01-11357
2026-01-18408
2026-01-25398
2026-02-01428
2026-02-08448
2026-02-15469
2026-02-22448
2026-03-01499
2026-03-08509
2026-03-15519
2026-03-22509
2026-03-29529
2026-04-05489
2026-04-12499
2026-04-19549
2026-04-26559
2026-05-03558
2026-05-10579
2026-05-176010
2026-05-246210
2026-05-31579
2026-06-076510
2026-06-14639
2026-06-216510

The read: same two years: agent teams +210%, traditional teams +25%. The weekly gap between the two cohorts is now 55 PRs — and still widening.

A closing note

What two years of telemetry can — and can’t — say

Correlation, loudly

The clearest signal in the whole dataset: AI adoption and shipping acceleration move together. Whether that output converts to business outcomes, no dashboard can yet say — but the coincidence of the two curves is difficult to argue with.

Everyone becomes a “builder”

Adoption is blurring roles: senior leaders doing hands-on IC work and adopting AI aggressively to do it, non-engineers committing code. Directionally, the suggestion that everyone in an organization is becoming a builder now has numbers behind it.

A Jevons-paradox quality

The gains didn’t show up as time saved. Time on existing tasks held while AI work appeared as a new layer, so total effort is going up, not down. Teams are working more, not less — efficiency became capacity, not leisure.

Motion isn’t value — yet

Pull requests measure motion, not worth. It beats measuring tokens — a mechanical refactor burns mountains of them while a one-line fix burns none — but the next edition’s job is the full lifecycle: from token spend to outcomes.

Appendix

Methodologywindows · aggregation · noise handling

The source report uses aggregated product telemetry from Linear: AI conversations, agent sessions, issue activity, comments and pull requests, covering paid workspaces and their users only. All metrics are reported in aggregate — broad patterns, never individual behavior.

  • Each metric is measured in a fixed window: a calendar month or trailing 30 days.
  • Year-over-year charts compare June 2025 with June 2026; adoption charts use January vs June 2026 with a trailing 30-day window.
  • Time series aggregate to weekly points; several cuts keep only users active in both windows. Both steps damp short-term noise.
  • Pull requests count opened PRs (not merged) in repositories connected to Linear.
DefinitionsAI-active · agent team · PR · paid workspace
AI-active
A user with at least one AI interaction — an in-app or Slack conversation, or an agent session — in a 28-day window.
Agent team
A workspace with a coding agent connected.
Pull request
A code change opened against a repository connected to Linear. Opened, not merged.
Paid workspace
A workspace on a paid plan, active during the relevant period.
Agent issue
Delegating an issue to an agent or starting an agent session.
Company size
Full-time employees at the company, from third-party enrichment.
Cohort sizesthe N behind every chart
  • Adoption by function: 127,000 paid users, active in both January and June 2026.
  • Executive team: 13,300 executives, active in both windows; company size from third-party enrichment.
  • Company size: 199,000 paid users with a known company size.
  • Application charts (04–06): 54,300 paid users in June 2025 → 89,000 in June 2026.
  • Non-engineer PRs: 166,000 paid users (June 2026).
  • PR volume: 47,900 paid workspaces (June 2026).
  • Coding-agent cohorts: 6,887 paid teams — 4,280 with, 2,607 without a coding agent.
  • Issue crossover series: 114 weekly observations, June 2024 – August 2026; imported issues excluded.
About this pagesources · licensing · accessibility

This is an independent visual reinterpretation of How Teams Build: AI usage patterns in software teams (Edition 01), by Tim Qi, Head of Data at Linear (2026). Every number was extracted verbatim from the public data tables published at linear.app/data on August 20, 2026; the charts, copy, and design are new. This page is not affiliated with or endorsed by Linear.

  • Self-contained: fonts (Newsreader, Inter, JetBrains Mono — SIL Open Font License), styles, scripts and images are bundled locally. No trackers, no third-party requests, works offline.
  • Accessible by design: every chart has a plain-language summary, a native HTML data table, keyboard navigation with arrow keys, and non-color encodings. Reduced-motion preferences are honored throughout.
  • Quotation policy: short phrases from the source report appear in quotation marks (e.g. “builder”, “Jevons paradox”); all other copy is original.
↑ top
View more demos Get $10 off Kimi K3