Skip to content

borghei/Claude-Skills / tools/linkedin/linkedin-content-repurposer

linkedin-content-repurposer

Verified

Turns something made for another channel (a thread, a video or talk transcript, a blog post, a newsletter) into a post that reads as native to LinkedIn, without changing what the source says. Use when existing material should become a LinkedIn post rather than writing one from a blank page.

assets/sample_article.md

View on GitHub
# What four years of customer support rotas taught me

In this article I want to walk through the changes we made to the support rota at Brackenhall, a 40-person company that makes booking software for dental practices. Dear reader, it is longer than I intended.

## Table of contents

1. The weekend problem
2. The handover note
3. The on-call swap market
4. What I would do differently

## The weekend problem

When I joined in 2022 the weekend rota was filled by whoever replied last in the group chat. Over the first year we logged 212 weekend tickets and 58 of them waited more than twelve hours for a first reply. Nobody had decided that was acceptable. It had just become normal.

I assumed the fix was headcount. We hired a fifth support person in early 2023 and the twelve-hour figure barely moved, because the new hire ended up in the same last-to-reply lottery as everyone else. The problem was not the number of people. It was that nobody owned Saturday morning.

So we stopped asking for volunteers. Each person now owns one weekend in five, published a quarter ahead. In the following year we logged 240 weekend tickets and 9 waited more than twelve hours.

## The handover note

As mentioned above, ownership fixed the weekend. It did not fix Monday. Tickets opened on Sunday night were being picked up on Monday by someone with no context, and customers were asked the same questions twice.[1]

We introduced a handover note with exactly three lines: what is still open, what I promised and to whom, and what I would do next. I wanted a longer template. The team argued me down, and they were right: a three-line note gets written, and a twelve-field form does not. Within two months repeat-question complaints dropped from 17 a month to 4.

| Month | Repeat-question complaints |
|-------|----------------------------|
| March | 17 |
| May | 4 |

## The on-call swap market

In the next section of our internal write-up we describe the swap board in detail; here is the short version. People were swapping weekends privately and the rota on the wall was wrong about a third of the time. Instead of banning swaps I made them public: a single pinned message where any swap has to be posted before it counts.

I used to think flexibility and predictability pulled against each other. What the swap board showed is that people will accept a fixed rota if they can see a legitimate way out of it. In the six months after the board went up there were 31 swaps and no missed weekend.

## What I would do differently

I would have fixed ownership before hiring. The fifth hire was the right decision eventually, but in 2023 it cost us a salary to learn that our problem was a calendar. I would also have asked the team to design the handover note from the start, since my version was three times too long.

If you run a small support team, read on to the checklist below, or see ![rota screenshot](rota.png) for the layout we use. The first thing to check is simple: for any given Saturday, can you name the person who owns it?

[1] Based on our complaint tags for January to March 2023.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall