<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data on Radical Optimist</title><link>https://radicaloptimist.org/en/tags/data/</link><description>Recent content in Data on Radical Optimist</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://radicaloptimist.org/en/tags/data/index.xml" rel="self" type="application/rss+xml"/><item><title>Ticketing Systems Are an Antipattern for Team Collaboration</title><link>https://radicaloptimist.org/en/post/ticketing-systems-are-an-antipattern-for-team-collaboration/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://radicaloptimist.org/en/post/ticketing-systems-are-an-antipattern-for-team-collaboration/</guid><description>&lt;h1 id="the-ticketing-system-user-interface-is-an-antipattern-for-cross-team-collaboration">The ticketing system user interface is an antipattern for cross-team collaboration&lt;/h1>
&lt;p>If your team spends most of its time managing a ticketing system — filing requests, triaging queues, waiting for answers — you have already made your collaboration legible to a machine.&lt;/p>
&lt;p>That is not a metaphor. Ticketing systems only work for the kind of work AI handles well: routine, well-defined, known destination, repeatable process. If your collaboration looks like a queue, it can be automated. And it will be.&lt;/p></description></item></channel></rss>