We recognized that our long-standing tradition of having in-person events in the office was driving a wedge between team members instead of pulling them together. As we continued to grow into a global, remote organization, having events that were only office-centric left remote engineers feeling like they were just on the sidelines. Instead of abandoning our tradition of in-person meet-ups altogether, we have reinvented this tradition into a decentralized funding model where teams create their own geographic events/meet-ups. What I learned from this experience is that traditions are only a framework for cultures, and do not define cultures themselves. When the structure of your company changes, holding onto old traditions causes resentment instead of building community. The goal isn't to hold onto what was done in the past but to carry on the spirit of the tradition (community and recognition) despite the operational realities of being a larger organization. Final Thought: Culture changes, and so do the ways we build culture. If you use intention and transparency while creating new methods to connect, you will continue to strengthen the relationships between distributed teams.
In a family business, traditions carry more weight than they do in a regular company. They're tied to identity, to the people who started the business, to a whole history. So when a tradition stops making sense, you can't just cut it. You have to handle it with some care. We had a tradition of doing a big year-end dinner for the whole team at a restaurant. For years it worked fine. But as the team grew and changed, the format stopped fitting. Some crew members didn't drink. Some had young kids and couldn't stay late on a weeknight. The attendance was dropping and it was starting to feel more like an obligation than a celebration. Instead of cancelling it or defending it, I brought it to the team directly. I said: this was meant to be a way to thank you, and if it's not landing that way anymore, I want to know. The feedback was clear. People wanted something more flexible and more daytime-friendly. We switched to a late-afternoon summer BBQ at the shop. Families were welcome. It was over by early evening. Within a year it became one of the things people actually looked forward to. The lesson for me was that the purpose of a tradition matters more than the tradition itself. If people feel recognized and appreciated, you've done your job. The format is just a vehicle. Don't protect the vehicle at the expense of the purpose.
We had a Friday drinks tradition from the company's earliest days casual all-hands where eight people shared wins and socialised. It was genuinely the highlight of the week and shaped the culture everyone loved. As we grew past thirty people and went partially remote it quietly became a problem nobody wanted to name. Remote employees dialled into a noisy room full of inside jokes they couldn't follow. Newer hires felt like outsiders watching a friend group. Parents couldn't stay late and felt guilty. Some people were uncomfortable with the drinks focus for personal reasons they didn't want to broadcast. The hardest part was that the tradition's biggest fans were the most influential people long-tenured staff who saw it as sacred. When I first raised concerns a cofounder reacted as though I was proposing to dismantle the entire culture. Instead of killing it or forcing change I shared anonymous feedback from people the tradition was excluding. Not my interpretation their actual words. Reading that a remote team member felt like a second-class citizen during the one event meant to unify everyone was harder to dismiss than abstract arguments about inclusivity. We redesigned it collaboratively. Friday afternoons stayed but became a 30-minute structured session at a time-zone-friendly hour. Each week a different person shared something they'd learnedVa project insight, a mistake, a discovery. No drinks requirement, no pressure to linger. Informal socialising still happened naturally but was no longer the official event. Some long-timers mourned the old format. But within two months engagement across the whole team was higher than the previous tradition had seen in over a year. Remote employees participated actively. Newer hires said it was where they first felt belonging. Traditions serve culture but they aren't culture itself. When a ritual starts excluding the people it's meant to connect, loyalty to the format over the purpose actually damages what you're trying to protect. Redesigning with input from those affected preserved the spirit while making it genuinely inclusive.
Mandatory weekend retreats used to be a big part of who we were as an organization. But by adding these days to already over-busy schedules of many working parents, this was creating burnout. I heard from employees through regular employee survey feedback. So, I pushed to convert those mandatory weekends into optional Monday Impact Day events. That way families could have some normalcy back in their week and also create better bonding experiences among employees.
I worked on this shift when our team's long-standing, rigid seating and top-down speeches were no longer fitting. To an environment of a more inclusive, agile, and employee-centric culture. From a research perspective, only 32% of employees globally feel fully engaged, instead of highly satisfied. Also, 88% of employees now prioritise culture. So, staying stuck to outdated traditions directly undermines attraction and retention. We first diagnosed the misalignment using internal pulse surveys and focus groups, which found that over-formatted events triggered 47% of disengaged staff to report they felt tokenized or excluded, consistent with broader findings that toxic or rigid traditions erode engagement and drive turnover. Then, we co-designed a replacement with cross-functional reps, aligning the new model to three research-backed pillars. Psychological safety, flexible participation, and recognition. Elements linked to 18% higher productivity and 85% higher revenue growth in strong-culture organisations. We piloted a monthly, theme-based "Culture Lab" where teams rotated facilitation, swapped large gatherings for smaller, mixed-tenure circles, and embedded short recognition rituals. Which shown to increase engagement by up to 69% when done consistently. In six months, engagement increased, absenteeism dropped, and retention increased. This growth reinforced that modernising traditions, not abandoning them, preserves cultural continuity while driving performance.
I am serving as a CuStrategy Advisor, and I recently handled a situation where our traditional "Friday beers" no longer fit our team. As our software team grew to include more remote developers and parents, the weekly drinking sessions started to feel forced. I also noticed that the hangovers were negatively affecting our work on Monday mornings. I took a very direct approach to fix this. I sent out an anonymous survey and discovered that 62% of the staff preferred doing something "useful" rather than just "fun." We phased out the old drinking tradition slowly and without any drama. The results of this change were excellent. The team engagement became 49%. we saw a huge increase in people learning skills from other departments. Our remote developers felt like they could contribute. As we recorded the sessions, nobody felt like they were missing out if they couldn't attend live. I have learned that company traditions usually die out naturally when you provide a better option.
We had a long standing habit of celebrating the loudest wins in all hands meetings. This worked well in the early stage when visibility helped build energy across the team. Over time it began to favor a few voices and many steady efforts went unnoticed. As we grew we realized inclusion mattered more than a few big spotlight moments. We changed the way we recognized people by focusing on team effort learning and steady progress. We invited peer nominations so more voices could be heard across the company. Leaders also shared the story behind the work so people understood the impact. We learned that people do not resist change they resist losing their sense of identity so we respect the past while building something better.
We had this Friday tradition at my fulfillment company where the whole team would gather for beer and pizza at 4pm. Started when we were 15 people crammed into that converted morgue. It was sacred. Everyone loved it. Then we scaled to 140 employees across multiple shifts. Our warehouse ran 24/7. Night shift felt excluded. Our best picker was a single mom who had to leave at 4:30 to get her kids. Two of our top performers didn't drink. The tradition that once brought us together was now creating an in-group and out-group. I ignored it for months because I loved those Fridays. That was my mistake. One of my warehouse managers finally pulled me aside and said half the team felt like second-class citizens. That hit hard. The tradition had become about preserving what made ME feel good, not what actually built culture. Here's what I did wrong first: I tried to fix it by adding a second pizza party for night shift. Terrible idea. Now we had two mediocre events instead of one good one. You can't just duplicate your way out of an outdated tradition. What actually worked was killing it completely and replacing it with something better. We started monthly team celebrations where we'd close the warehouse for two hours, bring in catering that accommodated everyone's dietary needs, and recognize specific wins from that month. We rotated the timing so different shifts got priority. Some were breakfast celebrations, some were afternoon, some were evening. The first time I announced we were ending Friday beer and pizza, you'd think I canceled Christmas. Three people told me it was a mistake. But six months later, our employee retention improved and our engagement scores went up 31 percent. The lesson isn't that traditions are bad. It's that the moment you're preserving a tradition because "we've always done it this way" instead of asking "does this still serve our team," you've already lost the plot. Culture isn't what you did when you were small. It's what evolves to include everyone as you grow.
My "popular tradition" was product pages. WhatAreTheBest.com originally launched with 15,000+ scored product pages spanning everything from kitchen appliances to power tools. They were generating real traffic from Bing and DuckDuckGo, and building them felt like progress. But maintaining that breadth was diluting what actually differentiated the platform — deep, evidence-based SaaS evaluation with a six-category weighted scoring system across 900+ software categories. Killing the product pages meant 410-ing thousands of URLs that were actively receiving visitors. It felt wrong. But the focus shift let me build the matching wizard, the scored comparison framework, and the editorial depth that no general product review site could match. Sometimes the tradition that built you is the thing preventing you from becoming what you're supposed to be. Albert Richer, Founder, WhatAreTheBest.com
So we had this Friday demo tradition where every team would showcase their weekly work to the whole company. It started when we were 15 people and felt electric. By the time we hit 50, it had become a 2 hour endurance test nobody wanted to sit through. People started finding excuses to skip. The energy was gone but the founders treated it as sacred. We tried shortening it, rotating presenters, making it biweekly. Nothing helped because the format assumed a size we no longer were. We eventually killed it and replaced it with async video updates, 3 minutes max, posted to a shared channel. The people who actually wanted to watch did. Attendance pressure disappeared and weirdly more people engaged with the async version than had been showing up live.
We faced this when a long-standing company tradition of late-night "crunch culture" during major projects was still being celebrated internally, even as we were trying to shift toward a more sustainable, performance-focused culture. The challenge was that people had an emotional attachment to it. It was seen as a badge of commitment and team spirit, even though it was increasingly leading to burnout and inconsistent output. Instead of removing it outright, we reframed the conversation around what we actually wanted to reward. We started highlighting teams that delivered strong results without last-minute overwork, emphasizing planning, collaboration, and efficiency. At the same time, leadership modeled the change by avoiding after-hours communication during critical periods unless absolutely necessary. We also made the shift explicit. We acknowledged the role the tradition had played in the past, but clarified why it no longer aligned with where the company was going. What we learned is that changing culture isn't about eliminating traditions, it's about redefining what gets recognized and reinforced. If you don't replace the old signal with a new one, the old behavior tends to persist. The key takeaway is to respect the history, but be deliberate about what you choose to celebrate going forward. That's what ultimately shapes culture.
When a long-standing company tradition no longer aligns with an evolving culture, the most effective approach is to treat the change as a cultural recalibration rather than a removal. One successful method involves openly acknowledging the tradition's past value while reframing it against current organizational goals and employee expectations. Research shows that nearly 70% of transformation initiatives fail due to lack of cultural alignment, highlighting the importance of deliberate change management. A key action is replacing the outdated tradition with a more inclusive or purpose-driven alternative, supported by clear communication and leadership endorsement. This ensures continuity of cultural identity while adapting to new realities, minimizing resistance and preserving engagement.
When a long-standing company tradition begins to conflict with an evolving culture, the most effective approach is to reposition the change as an evolution rather than an elimination. One practical action is to assess the original purpose of the tradition and evaluate its relevance against current organizational values and workforce expectations. Research shows that nearly 70% of organizational change initiatives fail due to cultural misalignment, making it critical to address such shifts deliberately. A strong decision framework involves replacing the outdated practice with a more inclusive, value-driven alternative while clearly communicating the rationale behind the change. This preserves cultural continuity while ensuring alignment with future goals.
As our company grew, informal communication habits became inefficient. We transitioned to more structured processes to support scale. We explained the reasons clearly to the team to maintain trust. The change improved efficiency without losing team cohesion.
CEO at Digital Web Solutions
Answered 24 days ago
A tradition we outgrew was treating constant availability as commitment at work today. In the early days we often took pride in answering messages late at night together. This built hustle but also rewarded presence over judgment in teams. It created pressure for people to prove dedication in unhealthy ways ourselves. I changed this by making it clear that responsiveness and responsibility are not the same clearly. We introduced simple communication rules around urgency planning and offline time also. I also made sure to model this change because leaders shape culture first now ourselves. We learned that some old habits feel strong because they are tied to our origin story but we must let them evolve when they cause strain today.
We once only celebrated big milestone wins in our team culture together. This created excitement but also made people hide messy progress over time. We later realized this led to less openness and slower learning gradually. When recognition only came at the finish line teams became cautious overall. We shifted the tradition to also recognize honest effort reflection and small improvements in how we work in practice. We avoided making it feel like participation praise and focused on work that improved thinking and operations as well. Over time we became more open about risks and asked for help earlier for support together. We learned that recognition shapes culture and shows what feels safe for us in culture system.
A favorite tradition involved celebrating volume above everything during major campaigns. It had symbolic value, but it slowly rewarded speed over judgment. As the business expanded, culture increasingly centered on trust, education, and dependable support. We introduced listening sessions across teams, then mapped which behaviors the tradition truly reinforced. That exercise exposed an uncomfortable gap between stated values and actual incentives. The change worked because replacement came before removal, not after confusion. New rituals highlighted solved customer problems, strong cross-team handoffs, and smarter recommendations. Communication stayed simple, frequent, and rooted in real operational examples. People accepted the shift once they saw culture becoming more useful, not more abstract. The clearest lesson was that traditions survive longer when they evolve with purpose.
We had a habit of making major decisions in fast group discussions because it felt collaborative and fast. Over time we noticed that louder voices were influencing outcomes more than careful thinking. This did not match the culture we wanted to build as a team. We wanted a culture that values preparation accountability and input from everyone. So we changed our approach in a simple and clear way. We moved key decisions into a process with written context and clear ownership. We also gave people time to think and respond at their own pace. This helped quieter team members share ideas and improved the quality of decisions we made.
I faced a similar situation where a beloved company tradition clashed with our evolving culture at InCorp Vietnam. Instead of abruptly ending the tradition, I initiated open discussions with the team to understand their attachment to it. I emphasized the importance of aligning our practices with our values and goals. Together, we brainstormed alternative activities that better resonated with our current culture and objectives. Through transparent communication and involving the team in decision-making, we successfully transitioned away from the outdated tradition. This experience taught me the significance of adaptability and inclusivity in fostering a positive work environment. As a result, our team morale and productivity improved, showcasing the power of embracing change for organizational growth.
A long standing tradition celebrated late night wins with after hours gatherings, but over time it started signaling that visibility mattered more than sustainable performance. As the culture matured around clarity, inclusion, and better decision making, that ritual no longer matched the standard being built. Rather than cancel it abruptly, we reviewed participation patterns, asked quieter team members for honest feedback, and mapped what the tradition was really rewarding. The change focused on replacing symbolic recognition with something healthier and more durable. Wins began being recognized during working hours, tied to learning, collaboration, and measurable impact. That shift improved morale, reduced pressure, and made success feel more accessible across different personalities and life stages. The biggest lesson was that culture is shaped less by slogans and more by repeated signals about what truly earns respect.