Your Wedding, Your Rules: The "Do Not Play" List

Every song tells a story. The trick is making sure your wedding soundtrack tells the right ones

January 8, 2026

About fifteen years ago, I accidentally played the wrong song at a wedding.

At the time, I had no reason to think twice about the choice. The dance floor had been busy. The energy in the room was excellent. We were approaching the end of the first hour of open dancing, and as I often do, I was looking to bring the tempo down for a few minutes before beginning the climb back upward. Over the years, I have learned that dance floors breathe. Guests can only maintain maximum energy for so long before they need a chance to catch their breath. The best receptions rise and fall in waves. They build. They release. They build again. On this particular evening, I reached for a slow song that had worked beautifully countless times before. It was "All My Life" by K-Ci & JoJo, a massive hit from 1997 and one of the most requested slow dances of its era. The song is romantic, soulful, and universally recognizable. In hundreds of situations, it would have been a safe choice. In this situation, it absolutely was not.

I knew something was wrong almost immediately.

The reaction wasn't dramatic. Nobody stormed off the dance floor. Nobody grabbed a microphone and demanded an explanation. There was no confrontation and no anger. But after nearly three decades of weddings, I have learned to pay attention to faces. A wedding reception is a room full of conversations that occur without words. A smile can tell you everything. So can a look of confusion. So can a glance exchanged between a bride and groom. As the opening lyrics began to play, I noticed the groom's expression change. The bride looked uncomfortable. Not mildly uncomfortable. Deeply uncomfortable. The sort of expression people wear when an unexpected memory has just entered the room uninvited. It didn't take long for me to learn what had happened. The groom had been married before, and "All My Life" had been the first dance at his previous wedding. Suddenly, what I thought was a beautiful slow dance carried an entirely different meaning. The song wasn't taking him back to high school dances or romantic evenings. It was taking him back to another marriage.

I have thought about that moment many times over the years because it taught me something important about music. Most people think of songs as entertainment. They are certainly that. They fill dance floors. They energize crowds. They provide a soundtrack for celebrations. But music is also something else entirely. Music is memory. More than photographs. More than videos. More than old letters tucked away in drawers. A song can transport a person across decades in the span of a few notes. It can take you back to your first kiss, your first heartbreak, your senior prom, your college dorm room, your first apartment, your wedding day, or the day you lost someone you loved. The strange thing about music is that it doesn't merely remind us of those moments. It allows us to feel them again. A photograph shows us what happened. A song allows us to revisit it.

I suspect everyone reading this has experienced something similar. Perhaps you hear a particular song on the radio and instantly find yourself transported back to a high school parking lot. Maybe a song comes on in a grocery store and suddenly you're remembering a relationship that ended twenty years ago. Sometimes the memories are wonderful. Sometimes they are painful. Often they are both. Certain songs become inseparable from certain chapters of our lives. They become attached to people, places, emotions, victories, failures, and moments we thought we had forgotten. Then one day, completely without warning, the song returns and opens a door we weren't expecting to walk through.

That reality is one of the reasons I find wedding music so fascinating.

Most people assume that a DJ's job is simply to find songs that people like. On the surface, that's true. But there is far more happening beneath the surface than many guests realize. Every song carries emotional baggage. Sometimes that baggage is positive. A particular track reminds someone of summer vacations, road trips, first dates, or college friends. Other songs carry different associations. They remind us of breakups. Funerals. Failed relationships. Difficult years. Family members who are no longer with us. The exact same song can make one person smile while making another person desperately wish they were somewhere else. Music is deeply personal in that way. It means different things to different people, and there is no way for a DJ to know every story attached to every song.

That is why I place so much importance on a couple's "Do Not Play" list.

Most couples spend a great deal of time thinking about the songs they want to hear. Those songs matter. They help define the personality of the reception. They tell me which decades, genres, artists, and styles are important to you. They help establish the atmosphere you want your guests to experience. But over the years, I have become convinced that the songs you don't want to hear are often just as important. In some cases, they may be even more important. Your "Must Play" list tells me what should be included in the soundtrack of your wedding day. Your "Do Not Play" list tells me what should not.

The reasons vary tremendously from couple to couple. Sometimes a song reminds someone of an old relationship. Sometimes it reminds them of a difficult period in their life. Sometimes it was played at a funeral. Sometimes it belonged to a parent, grandparent, or loved one whose memory is still painful. Occasionally there is no profound reason at all. Sometimes people simply hate a song. If Ed Sheeran's voice sounds like nails on a chalkboard to you, that is reason enough. You do not need to justify it. You do not need to explain it. You do not need to defend it. If hearing a particular song would make your wedding less enjoyable, then that song has no place at your wedding.

This is one of the reasons I have never understood DJs who insist on controlling all of the music themselves. I have heard stories over the years from couples who were told they would have little or no input regarding the playlist. That approach has never made sense to me. While I certainly bring experience, musical knowledge, and the ability to read a room, I am not the one getting married. I am not the one creating memories that will last a lifetime. I am not the one who has spent months—or years—imagining what this day will feel like. The wedding belongs to the couple. The music belongs to the couple. My role is not to impose my preferences. My role is to help bring theirs to life.

No two wedding receptions are ever the same, nor should they be. Some couples love country music. Others want none of it. Some want line dances. Others would rather remove every trace of "The Chicken Dance" from human history. Some couples want a dance floor built around classic rock. Others want pop, hip-hop, disco, Motown, or a little bit of everything. There is no universally correct playlist because there is no universally correct couple. The goal has never been to create the perfect wedding reception. The goal is to create your wedding reception. Those are not the same thing.

And that brings me back to "All My Life."

I still think it's a beautiful song. My wife still insists that women melt when K-Ci starts singing, and after all these years, I suspect she is probably right. But every time I hear it, I think about that wedding. I think about that groom. I think about how quickly music can unlock memories we forgot were waiting. Most importantly, I think about the lesson that couple unknowingly taught me. A wedding playlist is not simply a collection of songs. It is a collection of memories, emotions, and experiences. Some belong on the dance floor. Some do not. And that is precisely why your "Do Not Play" list matters. Because on your wedding day, the music should tell your story—not somebody else's.

Previous Post Return to Blog Next Post