Every June, the same question arrives on someone's desk: “What are we doing for Pride?”
The pressure is real. You want to do something meaningful that doesn’t feel like a corporate checkbox. There’s probably not a big activation budget, and you're aware that doing it badly might be worse than doing nothing at all.
The way your office shows up during Pride and how it carries those same instincts into every other month has a lot to do with decisions that may look small.
Why some Pride events feel hollow and others don't
You’ve probably seen the version that doesn’t quite land: rainbow cupcakes in the break room, a company-wide email with a stock photo, maybe a Pride emoji added to the #general Slack channel. The intention is good, but when these moments aren’t shaped with meaningful input or consideration, employees can usually tell the difference between something performative and something thoughtful.
When the only signal a company sends during Pride is decorative, employees can usually tell what’s missing: any real sense of thoughtfulness, intention, or lasting commitment beyond the month itself.
A Pride moment that works is usually connected to something the company already does (a team meal, a Friday gathering, a recurring lunch), planned with input from LGBTQ+ employees who wanted to be involved. And it doesn't position itself as a one-time event. It feels like part of how the office runs.
The HRC Foundation's 2026 Corporate Equality Index found that Fortune 500 participation in public inclusion reporting dropped 65% year over year, reflecting a climate where many companies are pulling back on visible commitments even as their employees continue to expect them. You can't fix what the CEO says or doesn't say in a press release, but you can shape how your team feels when they sit down to eat together.
Planning a Pride event your LGBTQ+ coworkers didn't have to ask for
If someone realized it was June and fired off a message asking for “Pride celebration ideas,” the effect is that your LGBTQ+ coworkers just became the unofficial planning committee for their own recognition.
The intention is good, but now the people you're trying to recognize end up doing the work of teaching everyone else how to recognize them. And that gets tiring.
Your first move should be figuring out what your team actually wants before you announce anything. That doesn't mean sending an all-company survey that says, “How should we celebrate Pride?” because now you've made it everyone's business to weigh in on something that's deeply personal for some people in the room.
A better approach: talk to your affinity group leads or LGBTQ+ employee group privately, early. Ask what they'd find meaningful, and give them the option to be involved in planning or to just show up and enjoy whatever happens. Some people will want to help shape the day. Others will want to eat lunch with their coworkers and that's it.
If you want to bring in an external speaker or host a conversation with LGBTQ+ voices, that can be valuable, but only if those speakers were invited with lead time, compensated for their time, and given full control of what they wish to discuss. Pulling a coworker aside on June 3 to ask if they'd “share their story” at a lunch-and-learn misses that point.
Not everyone wants to be the center of the celebration
Some of your LGBTQ+ coworkers are out and vocal. They'll appreciate the visibility. Others are out at work but private about it. And some aren't out at all.
A well-planned Pride moment makes room for all of those experiences without requiring anyone to identify themselves.
Frame it as a team value. “We're ordering from a queer-owned restaurant this week because it's a great spot and we want to support the community” lands differently than “We're celebrating our LGBTQ+ colleagues today!” The first one creates space. The second one creates a spotlight, and not everyone wants to stand in it.
Keep participation voluntary and low-pressure. A shared meal where people sit with whoever they want, no icebreakers, no mandatory attendance, no going around the table. If the food is good and the vibe is relaxed, people will stay.
What your menu says about who you thought of
Food is one of the most visible decisions in an office. Everyone sees what showed up, who it was ordered for, and what options exist. That makes it a signal, whether you intend it to be or not.
During Pride, ordering from a queer-owned restaurant is a concrete way to direct company dollars toward the community you're recognizing. Many cities have LGBTQ+ owned restaurants that do catering or group orders. Including a note that explains why you chose the restaurant does the work.
But the menu signal goes beyond June.
Think about the person on your team who's vegan and has to ask about ingredients every time you order food for a group. Or the employee who keeps halal and quietly skips the team lunch when there's nothing they can eat. These aren't Pride-specific issues, but they're inclusion issues, and they're visible in the same way. When someone shows up to a team meal and realizes nobody considered their dietary needs, the message is clear regardless of what month it is.
Group orders are a practical fix. People pick individual meals, nobody has to flag a restriction, request a special plate, or eat before the meeting. When you do go with catering platters, choosing restaurants that naturally cover the most common diet restrictions, plant-based options, gluten-free sides, allergen-separated sauces, means the default spread works for most people in the room.
Your team notices who you think about when it's not a designated month
Pride is in June. But the principles that make a Pride event feel real, like asking before assuming, offering individual choice, and designing for people who don't want to flag their needs, apply to every team meal and gathering you run all year.
The same attention you'd give to ordering food during a team member's religious observance or planning a meal around cultural heritage months applies here. Inclusive food decisions shouldn’t just be seasonal.
Accommodation is reactive: someone asks, and you respond. Consideration is proactive: you designed the system so they didn't have to ask.
A few structural choices that carry this all year:
Set up a recurring meal program for team lunches, so inclusive food ordering becomes automatic instead of something you have to think about each time.
Rotate restaurants to reflect the diversity of your team, not just during designated months. A Korean restaurant one week, a Nigerian spot the next, a Mediterranean place after that.
Include remote employees in food-related moments with meal credits so they're not watching a Slack photo of a lunch they weren't part of.
Build a calendar of cultural and identity-based moments at the start of the year, not a week before each one arrives.
Create inclusive team moments with DoorDash for Business
DoorDash brings group orders, catering, and meal credits into one platform. If you're planning a Pride lunch, a recurring team meal, or a one-off celebration, you can find restaurants that fit, set dietary filters, and include remote employees without managing it all separately. See how it works.
