Loading video...

Video Failed to Load

Go Home

Every product change risks leaving your docs behind. Here’s how our CX team uses Loops to keep them up to date.

22,739 views • 3 months ago •via X (Twitter)

8 Comments

Linear's profile picture
Linear3 months ago

Learn more and create your own loop:

Manish Baghel's profile picture
Manish Baghel3 months ago

why do you need docs if LLMs can document on the spot?

Fiducial.ai's profile picture
Fiducial.ai3 months ago

the daily scan plus weekly review is a sensible split. the agent catches drift continuously without turning every small change into an immediate docs edit

JRod's profile picture
JRod3 months ago

Linear has public facing docs?

Erik Erelöf's profile picture
Erik Erelöf3 months ago

Docs go stale because they're a second artifact kept in sync by hand. Ship the system, then remember to touch the doc. If docs ARE the system map, updating the system updates the doc by definition. Different bet:

Maximiliano Moxarella's profile picture
Maximiliano Moxarella3 months ago

docs can never be out of date if you just don't write them in the first place

Jayadeep Reddy's profile picture
Jayadeep Reddy3 months ago

Shifting documentation updates to the CX team creates a delayed feedback cycle. Unless the Loops workflow triggers directly from merged engineering code, CX will only discover outdated documentation after users submit support tickets.

Neel Samadder's profile picture
Neel Samadder3 months ago

It’s time to discover and transform linear folks This ain’t gonna work for long

Related Videos