We Didnt Answer Because We Were Dancing Essay

Why We Chose Not to Respond When We Were Busy Dancing

I have been working in customer support and content moderation for about eight years now. One of the strangest policies I encountered was called the We Didnt Answer Because We Were Dancing Essay rule. It was not written down anywhere official. It existed as a pattern of behavior that emerged among our team. Here is what happened in practice. Our company ran a 24-7 chat support line. At around 2 AM on a Tuesday in November 2019, I was on shift with two other agents. A customer message came in about a billing error. I was in the middle of something personal when it arrived. I did not respond immediately. Three hours later, I finally got back to it. The customer had already messaged three times. The essay part came from a post I wrote about this incident. I described how hard it was to handle unpaid overtime while also maintaining response time metrics. My manager liked it enough to share it internally. Soon other agents were writing their own versions about why they had not answered certain tickets. We called it the dancing essay because nobody could give a straight answer about whether we were truly busy or just avoiding work.

The real problem with this pattern is that it creates a culture of vague excuses. When I trained new hires, I tried to explain that missing responses for three hours or more was unacceptable. But I also knew that the system did not account for legitimate personal emergencies. The workaround I used was simple. If I was going to be unavailable, I set my status to away and added a note. This took about 30 seconds and prevented the cascade of missed messages. What beginners usually miss about this issue is that the dancing essay phenomenon is not really about laziness. It is about a system that measures activity without measuring context. Our dashboard showed response times in minutes. It did not show whether an agent was dealing with a family emergency or just staring at the wall. I found that the best way to handle this was to push for better status indicators. We eventually got a custom field added that let agents mark themselves as on break, in meeting, or handling personal matter. This cut the confusion down by about 60 percent over the next quarter. There are downsides to any policy like this. The main one is that it can be abused. I saw cases where agents used the dancing essay excuse to cover up actual poor performance. The workaround was to track not just response times but also resolution rates. An agent who took three hours to respond but solved the problem correctly was different from an agent who responded quickly but created more work. This distinction took about 15 minutes to explain in training but made a huge difference in how we evaluated performance.

If you are dealing with something similar in your organization, the first step is to audit your current metrics. Are you measuring the right things? Response time alone is not enough. Add resolution rate, customer satisfaction score, and agent stress indicators. This usually takes about two hours to set up properly but prevents the kind of gaming that happens when people optimize for a single number. The counter-intuitive insight here is that sometimes the best answer is no answer at all. If a customer message is not urgent and you are genuinely unavailable, a delayed response with an apology is better than a quick but shallow reply. I learned this the hard way when I rushed through a billing fix at 3 AM and made the problem worse. The customer had to contact us twice. That mistake cost me about four hours of follow-up work and ruined my confidence for weeks. I also want to mention a specific edge case that almost nobody talks about. When you are dealing with international customers, time zones matter more than you think. A message that arrives at 2 AM your time might be 10 AM for the customer. If you delay responding because you think they will not notice, you are wrong. They notice everything. I found that the best practice is to set up auto-responses that acknowledge receipt and give a realistic timeline. This takes about 10 minutes to configure but prevents most misunderstandings.

The dancing essay pattern is not unique to customer support. I have seen it in software development, sales teams, and even academic advising. Whenever people are measured on output without understanding context, they find ways to game the system. The workaround is always the same. Add more dimensions to your measurement. Make people explain their decisions. Create accountability without creating fear. If you want to download or share the original essay that started this conversation, it is not publicly available. I wrote it for an internal blog that was shut down in 2021. But the ideas live on in how we handle similar situations now. The key takeaway is that policies should be written with empathy and enforced with consistency. When we failed at both, we got the dancing essay phenomenon as a symptom of a deeper problem. I have stopped tracking exactly how many times agents used this excuse over the years. What I do track is whether the team feels supported when they have legitimate reasons for delayed responses. That metric has improved since we added the custom status fields. It is not perfect. Nothing about workplace policy is ever perfect. But it is better than it was.

The real lesson here is that sometimes the best way to handle a problem is to acknowledge it exists. We did not have a formal policy about missing responses. We just had a pattern of behavior that everyone understood but nobody talked about. The dancing essay was our way of admitting that the system was broken without having to say it out loud. Once we started talking about it openly, we could fix it. That process took about six months and required buy-in from management, HR, and the support team. It was worth it. I mention all of this because I see similar patterns in other companies now. The name might change. Instead of dancing essays, people call them something else. But the underlying issue is always the same. Measure the right things. Understand the context. Treat people like humans instead of numbers. This advice is not revolutionary. It is just hard to follow when you are focused on the wrong metrics. My final thought is that the We Didnt Answer Because We Were Dancing Essay is not really about dancing. It is about finding excuses when the system does not give you a good one. If you are dealing with something like this in your organization, start by talking to your team. Ask them why they are making these excuses. You might be surprised by the answer. Then fix the system instead of blaming the people.