<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Teams on BunnyCal Blog</title><link>https://bunnycal.io/blog/tags/teams/</link><description>Recent content in Teams on BunnyCal Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2026 16:03:00 +0530</lastBuildDate><atom:link href="https://bunnycal.io/blog/tags/teams/index.xml" rel="self" type="application/rss+xml"/><item><title>Round-robin that actually balances</title><link>https://bunnycal.io/blog/round-robin-that-actually-balances/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://bunnycal.io/blog/round-robin-that-actually-balances/</guid><description>&lt;p&gt;Every scheduling tool with a team plan claims to do round-robin. Most of them
implement the same thing: keep a pointer, hand the next booking to whoever is
next in the list, advance the pointer. It demos beautifully. It falls apart in
the second week.&lt;/p&gt;
&lt;h2 id="why-a-rotating-pointer-drifts"&gt;Why a rotating pointer drifts&lt;/h2&gt;
&lt;p&gt;A pointer only counts &lt;em&gt;offers&lt;/em&gt;, not outcomes. Consider a three-person team where
everyone is nominally equal:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Priya works Tuesdays through Fridays.&lt;/li&gt;
&lt;li&gt;Marco is on Pacific time; the team&amp;rsquo;s booking page is mostly booked by European
prospects in the morning.&lt;/li&gt;
&lt;li&gt;Dana has back-to-back internal meetings every Monday.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The pointer doesn&amp;rsquo;t know any of that. It offers Marco the 9am CET slot, finds he
has no availability, and skips to the next person. Skipping &lt;em&gt;doesn&amp;rsquo;t cost Marco
his turn&lt;/em&gt; — so he stays at the head of the queue and gets skipped again. By
Friday, Priya has taken sixteen calls and Marco has taken three, and nobody
touched a setting.&lt;/p&gt;</description></item></channel></rss>