How to Gather Feedback on Your Company’s Approach to Celebrating Milestones

My process is unglamorous: I ask, in writing, shortly after the moment has passed. Celebration is one of those areas where founders grade themselves on intention and teams grade them on experience, and the gap between the two stays invisible unless you go looking. So after any milestone we mark, a launch, a funding close, a big customer, I send a short anonymous pulse of 3 questions: did the way we marked this feel proportionate, did it feel personal, and what would you change next time. Anonymous matters, because nobody tells the founder to his face that his celebration missed.

The example that changed my approach came from an early venture. Our habit was to mark launches with a team dinner booked weeks later, once the dust settled. The pulse feedback was consistent and slightly painful: by the time the dinner happened it felt like admin, because the emotional peak was launch day itself and we had let it pass with a message in the group chat. So we flipped it. Recognition now happens the day the thing ships, small, immediate and specific about who did what, and the bigger gathering later is a bonus rather than the main event.

The pulse itself tells me the loop is working, because people keep answering it. Feedback only stays alive when the team can watch their answers change what you do.

My process is unglamorous: a short anonymous pulse form each quarter with one standing question, how should we mark wins and milestones, plus the same question asked live in stay interviews, because some people will never type what they will say out loud. The anonymous channel matters in a small team, where declining the office party can feel like a personal rejection of whoever planned it. What the feedback taught me was humbling. I had assumed our front desk birthday spotlight, balloons and an announcement in the waiting area, was a highlight of working here. In one pulse round, 6 of the nine responses said some version of please stop, that being sung to in front of patients was mortifying. So we rebuilt the whole thing around consent. Celebrations are now opt in, with a menu: a public shoutout, a handwritten note from me, a covered shift so they leave early, or nothing at all, and nobody has to explain their pick. The covered shift turned out to be the runaway favorite, which no owner would have guessed from the inside. The story I share with other founders is the medical assistant who chose the quiet note, then kept it pinned inside her locker for a year. The feedback did not just improve the celebration, it stopped us from spending money on a ritual our own team was politely enduring.

We’re a fully distributed team, so celebrating wins is genuinely hard — there’s no office where a cake shows up. For a while I gathered feedback the obvious way: after a milestone, I’d ask people what they thought of how we marked it. And the feedback was always polite and useless. “That was nice, thanks Derek.” Nobody critiques a celebration to your face. It feels ungrateful.

So I changed what I was actually listening for. Instead of asking about the celebration, I started watching how people talked about the milestone weeks later, unprompted. Did anyone bring it up again? Did it show up in how they described their own work? That’s the real signal — a celebration that gets referenced later actually landed. One that vanishes by Friday didn’t, no matter how many thumbs-up emojis it got in the moment.

The example that changed things for us: we used to celebrate big aggregate numbers — “one million articles converted!” Crickets, every time. Then we shifted to spotlighting a single specific user story behind the number — one person, one reason listening mattered to them. People kept quoting those in Slack for weeks. Turns out nobody feels personally connected to a million of anything, but everybody remembers one human.

So the lesson: don’t ask if the party was good. Watch what people still carry a month later. That’s your feedback, and it doesn’t lie the way politeness does.

Bootstrapping two companies since 2018 means milestone celebrations can quietly become meaningless if you stop checking whether they actually land. We learned this the hard way.

For a while, Pageloot’s team would get a Slack message when we hit a user milestone. Growth to 10,000 brands, 15,000, 20,000. We thought it was enough. Then during a quarterly retrospective, someone on the team mentioned they didn’t even remember the 15,000 announcement. It had scrolled by in a channel full of noise and felt like a stat, not a moment.

The feedback came through a simple async retro we run every quarter. We ask three questions: what felt good, what felt hollow, what would you actually remember in a year. That last question is where the honest answers live. No one says “the Slack message” when you ask what they’d remember.

We rebuilt the approach around one rule: the person closest to the win tells the story, not the founder. When we crossed 20,000 brands across 110 countries, our customer success lead wrote up three specific customer stories behind that number. That post went into our internal wiki and our external newsletter. The team referenced it for months. The Slack message never got referenced once.

Process-wise, the retro questions run async on Notion, responses are anonymous, and I read every one. If the same word appears twice across responses, it gets discussed the following week. “Hollow” appeared twice in one quarter. That was enough.

We have no process for this in any formal sense, which is the honest answer for a business our size. What we have is asking, then doing something visible with the answer.

We ask twice a year in a one to one, with a specific question rather than a general one: what did we do this year that you thought was a waste of time? General questions get polite answers. That one gets the truth, because it gives permission to be critical about a thing rather than about a person.

The answer that changed us was about how we marked hitting a big sales month. I had been announcing the number in the group chat with a lot of exclamation marks. 7 people, in different words, told me the same thing. The number means nothing to them, and the announcement felt like it was for me. Fair enough.

So we changed it. Now we mark what the team can see themselves in, the busiest dispatch day, the week with no mispicks, and we mark it with something ordinary and shared, usually food, in the warehouse where the work happens.

The lesson was that recognition has to be recognisable. If people cannot see their own hands in what you are celebrating, you are celebrating at them.

An anonymous feedback box revealed how hollow our celebrations had become

Our process for gathering feedback on how we celebrate milestones has always leaned heavily on an anonymous feedback box, kept genuinely anonymous rather than just labelled that way, because I’d noticed people rarely say what they actually think when feedback is tied to their name, especially about something as seemingly minor as how achievements get recognised.

For years, our approach to celebrating wins followed the usual pattern, a message in the team channel, occasional mentions in an all-hands meeting, maybe drinks after a particularly big client win. It felt sufficient from where I sat. Then a handful of anonymous notes started appearing over a few months, all circling the same frustration, that recognition almost always went to whoever was client-facing or presented in meetings, while people doing equally important work behind the scenes, data analysts, technical specialists, junior team members supporting a campaign quietly, rarely got mentioned at all.

That pattern was uncomfortable to read, but it was honest in a way direct conversations hadn’t been. We changed our approach entirely, introducing a monthly recognition round where anyone could nominate a colleague for a specific contribution, however small, with a short explanation of what they’d actually done, not just their job title or visibility.

Within a few months, submissions to the anonymous box shifted noticeably, fewer complaints about recognition, more general suggestions about other processes entirely, which told us the original issue had genuinely been addressed rather than just quietened.

What that taught me is that people will tell you the truth about culture long before they’ll say it to your face, if you give them a way to do it safely. That anonymous box has quietly shaped more meaningful change in how we operate than most formal reviews ever have.

Celebrate the team, then review the format

Our main milestone celebration is a company-sponsored holiday once a year. I treat the trip as both recognition and a format the team should help improve, rather than a fixed tradition leadership repeats without checking whether it still works for everyone.

Before planning, I ask for input on timing, travel comfort, accessibility, preferred balance between group activities and personal time, and anything that would make participation difficult. People can respond privately because preferences around travel, family commitments, health, or social time should not require a public explanation.

At VoiceAIWrapper, the purpose is to thank the team and give people space to connect outside normal delivery work.

After the holiday, I use a short feedback review focused on the format rather than asking whether people had fun. What helped people connect? What felt over-scheduled? Which parts should remain optional? What planning information arrived too late? What would make the next holiday easier to participate in?

One improvement from that feedback was separating shared moments from free time more clearly. We kept a small number of activities where the whole team could be together, then protected unstructured time rather than filling every hour. The change recognized that celebration does not require everyone to enjoy the same pace or activity.

I summarize what we heard and state what will change next time. Private details remain private, but the team should see that feedback affected the plan. If a suggestion cannot be adopted because of cost, timing, or logistics, I explain the constraint instead of letting the request disappear.

The trade-off is that more choice can make planning harder and reduce the feeling of one shared event. I protect a few common moments while keeping the rest flexible. Another failure mode is allowing the annual holiday to become the only form of recognition. Everyday contributions still need timely acknowledgement during normal work.

A sponsored holiday is valuable when it reflects the people being celebrated. The feedback process keeps the tradition from becoming an obligation designed around leadership preferences. Ask early, review afterward, and change the next plan in ways the team can see.

I look for feedback in behavior before opinion. After any celebration, metrics from the following two weeks get reviewed, including customer response quality, refund language, staff tempo, and whether the moment created urgency or fatigue. Then a few trusted people answer one question: did this reinforce the standards behind the milestone, or just the milestone itself?

That process changed how achievements are shared after a revenue jump produced strong social engagement but a spike in confused customer expectations. The language had celebrated momentum, not the disciplined constraints behind it. The next update emphasized what was intentionally not pursued, and trust improved because the company sounded more selective than self-congratulatory.

We don’t have a process for gathering feedback on milestone celebrations. We have a direct line to the people using what we built.

Three-person team. No separate function for HR, no culture lead, no one whose job it is to design celebrations. When something ships or hits a marker, the three of us decide if it’s worth pausing for. Most of the time, it isn’t. We’re building a non-custodial DeFi application that routes perpetuals through Hyperliquid and prediction markets through Polymarket, all unified in a single mobile interface with an AI layer. The milestones that matter are product milestones, and the people who care most are the users depending on what we ship.

Here’s the specific example. We hit a transaction volume threshold in our web app that felt meaningful internally. We posted about it in our user channels. The response wasn’t celebration. It was feature requests. Users wanted the mobile app live, they wanted faster onboarding, they wanted the NikaAI layer to handle more complex queries. That feedback reframed how we think about milestones entirely.

Now we only celebrate milestones that users can feel. Mobile app going into beta. That’s a milestone. A new routing integration that gives users access to better liquidity. That’s a milestone. Internal metrics that don’t change the user experience? We track them, but we don’t celebrate them.

The feedback mechanism is structural. We’re close enough to users that we hear what matters to them in real time. When the decision-making layer and the execution layer are the same layer, you don’t need surveys or retrospectives. You just listen and ship.

Most teams over-index on celebrating things that make the team feel good but don’t move the product forward. We celebrate the things that make users come back.

The process starts with one principle, celebrations should teach the organization what success actually looks like. Feedback is collected through brief anonymous prompts, leadership listening sessions, and manager level pattern reporting. I pay close attention to whether people describe recognition as motivating, accurate, and fair. In operationally complex environments, milestone celebrations can unintentionally favor front end wins while overlooking the systems and discipline that make those wins repeatable.

That issue surfaced after internal feedback showed project management and quality teams felt disconnected from recognition moments. We redesigned milestone communication to explain the operational chain behind each achievement, including turnaround control, escalation handling, and collaboration strength. The result was more than higher engagement. It created better alignment on what excellence means, which improved handoffs and made future recognition easier to trust.

At Tibicle, the honest answer is that our early milestone celebrations were decided by leadership and announced to the team. We assumed we knew what felt meaningful. The feedback we eventually gathered showed we were often wrong about which moments mattered most to the people actually doing the work.

The shift came when we started asking the team directly after significant project deliveries what they felt deserved recognition and how. Not a formal survey. A genuine conversation in the retrospective about what the team was proud of from that sprint or that project. The answers consistently surprised us.

Leadership tends to celebrate outcomes. Clients signed, revenue milestones, product launches. The team cares more about the internal moments. The sprint where everything was broken on Monday and working by Friday. The developer who stayed sharp under a difficult client. The collaboration that solved something nobody had figured out for weeks.

When we started acknowledging those internal milestones publicly on LinkedIn and in team channels alongside the business outcomes, engagement with the content changed noticeably. The team shared those posts themselves rather than just seeing them.

The improvement was simple. We stopped deciding what was worth celebrating and started asking. The team knows better than leadership which moments actually meant something.

As a CEO, I have found the best way to collect feedback on how we are celebrating milestones is to conduct short pulse surveys with employees immediately after significant project completions, and then have small groups of employees discuss the feedback they received in greater depth to understand which types of recognition were meaningful and which were routine. I don’t just focus on participation, I’m also keen to see the comments that give reasons why a particular approach was valued by employees.

An example of this was when a team was acknowledged for successfully implementing a new feature that was customer-facing. The feedback showed that the peer nominated recognition was more appreciated than the recognition from the manager, as this highlighted the contributions that are made behind the scenes. We incorporated peer recognition into all milestone celebrations and short stories about the impact of each person from those learnings. Members of a team were more engaged in celebrating other team members’ successes, and feedback demonstrated a greater sense of ownership of projects across team members.

As owner of Big River Roofing, I look at milestones through three lenses: homeowners, crew, and whether the achievement reflects the standards we actually want repeated. A “Best of the Best” vote or manufacturer certification only matters if the team can connect it to better installs, cleaner communication, and safer jobsites.

My process is simple: after a milestone, I ask what felt real, what felt like marketing, and what behavior we should reinforce. I get that feedback from closeout conversations, project photos, warranty documentation, and direct crew input.

One change came from our project gallery. Homeowners told us they cared less about polished bragging and more about seeing real before-and-after work, so we started using actual job photos to show problems like rotted decking, bad flashing, or valley issues instead of just posting “finished roof” pictures.

Another example is safety. After Lancaster Safety Consulting training, we made safety itself something worth recognizing, because a crew that uses harnesses, anchors, PPE, and proper jobsite procedures is usually the same crew that pays attention to flashing, ventilation, and cleanup.

We treat recognition like any other program: measure it, then fix what the data shows. Our feedback loop has three parts. First, a two-question pulse after every milestone moment, asking the person if the recognition felt personal and if the timing was right. Second, a quarterly review of which award types and messages people actually kept or displayed, since a gift that ends up in a drawer is a signal. Third, direct manager debriefs, because managers hear the honest reaction first.

One example: our pulse data showed people valued the moment more than the object, but our first-year anniversaries were the weakest scored because they often slipped past the actual date. We changed two things. We moved to automated date reminders so no anniversary is late, and we required a short, specific note from a direct manager, not a generic “thanks for your service” from HR. First-year scores rose the next two quarters, and managers told us the notes were the part employees mentioned back to them.

The lesson we keep relearning: timing and specificity move the numbers more than spend does.

At O Spa, I gather feedback in two places: right after treatments, when guests are most honest in their body language, and in reviews where they describe what stayed with them. I also ask my team what recognition felt genuine versus what felt performative.

One thing we heard often was that guests valued feeling unrushed, soothed, and personally cared for more than big gestures. So when we celebrate a team achievement, I stopped making it about a generic “great job” and started sharing the exact guest outcome, like cleaner scalp, less tension, or a calmer experience.

A practical example: reviews mentioned easy booking, same-day availability, quiet rooms, and gentle service as part of the win. That feedback made us treat convenience and calm as achievements too, not just the treatment result.

Now our milestone process is simple: collect the guest’s words, connect them to the team behavior that created it, and improve the service around that pattern. In wellness, the best celebration is often quieter, more specific, and tied to real care.

I’m the CEO and co-founder of Netsurit, and keeping recognition meaningful matters when you have 300+ people across multiple regions and cultures.

Our process is simple: after milestones, we ask through Dreams Program conversations, manager check-ins, and culture forums: what felt genuine, who was missed, and what behavior should we reinforce?

One improvement came from feedback that awards and acquisitions could feel too company-centric. So we shifted more recognition toward client-impact stories, like Machen McChesney moving from fear of ransomware to confidently exploring AI and better workflows.

Now we don’t just celebrate “we made the MSP 501” or “we completed an acquisition.” We celebrate the people, the client outcome, and the dream it helped unlock.

I try to gather feedback in the least corporate way possible: ask people directly what felt meaningful, what felt forced, and what they’d actually want repeated. One thing we learned is that not everyone wants a giant public victory lap; some people love the shoutout, others would rather get a thoughtful note, extra flexibility, or a small team celebration. So we moved away from one-size-fits-all recognition and started matching the celebration to the person and the win. That made milestones feel less like mandatory confetti and more like actual appreciation. My rule is simple: if the celebration is more fun for leadership than for the person being celebrated, you’re doing it wrong.

I doubt anyone tells you honestly what they thought of their work anniversary gift while you are watching them open it. So we stopped asking in the moment and started asking 2 months later, inside the conversation where managers ask what people want from the company rather than what they are giving to it. At 60 people, nothing reaches leadership by accident. It arrives through a manager or it does not arrive.

What came back was that only the 5 year milestone felt real, so everything before it read as filler. We moved the budget around and let people choose a day off instead of a gift. Uptake on the day off was far higher than anyone guessed. Whether that means people wanted rest or just wanted to skip being celebrated on a video call, I cannot tell. Does anyone actually enjoy that part?

As Head of School at Wilkes-Barre Academy, I rely on our active PTO and our interactive Parent Portal to maintain a continuous, open feedback loop with our families. This direct communication helps us constantly evaluate how we celebrate academic and community milestones to ensure they remain meaningful.

For instance, after receiving feedback that parents wanted more hands-on leadership opportunities for older kids during school-wide events, we transformed our “Read Across America” celebration. We handed the reins to our middle schoolers, tasking them with designing and delivering the interactive literacy activities for the younger students.

This change turned a standard reading milestone into a powerful confidence-builder that united the entire school. To make your organization’s celebrations successful, create clear channels for feedback and be willing to let your stakeholders take the driver’s seat.

I get my feedback straight from members during flight debriefs and through our annual surveys. We monitor Net Promoter Score, sure, but the most useful feedback happens right after flights when people’s reactions are still raw. Last year members told us flat-out that our 25th anniversary celebration felt too corporate, too distant. They wanted something that felt more personal. So we changed course. Instead of throwing a big gala, we organized small dinners in different cities where I could sit down and thank longtime clients face-to-face. The response was overwhelmingly positive. The takeaway? Your customers already know how they want to be treated. You just have to ask them, and then actually do something with what they tell you.

Our process for gathering feedback on how we celebrate milestones at distribute.you happens during routine one-on-ones, rather than through formal internal surveys. Because we are an acquisition agency built around highly quantitative metrics, we naturally tend to track everything. Early on, our internal celebrations were mostly tied to standard top-line growth, like signing a new batch of clients. But during one-on-ones, when I started asking our team what actually felt like a real win to them, the feedback was remarkably consistent. They felt a bit disconnected from those broader revenue milestones. Instead, they were deeply invested in the operational metrics we actually engineer for our clients.

Based on that direct feedback, we completely shifted what we celebrate as a company. Now, our biggest internal shout-outs happen when a team member successfully runs an outreach experiment that pushes a client’s cost per interested reply down to our target of around $65, beating the standard $500 to $700 market rate.

One of the most useful improvements came from feedback after we celebrated a major publishing milestone. While the event was well received, we learned that the recognition felt focused only on the final result. We wanted the full journey to matter as much as the achievement itself. That feedback matched our culture because we value steady effort, curiosity, and long-term learning every day.

In response, we changed how we celebrate progress across each project. We now recognize small wins instead of waiting for major announcements. Managers gather quick team reflections, and we review shared themes that deserve more attention. This change helped people feel valued earlier and kept motivation strong throughout the work.

At Connext, we allow participation upfront to include surveys of themes and locations. We also have a volunteer committee to work with the people and culture team on planning and execution. I personally participate in most events, talk to as many participants as possible and gather on the spot feedback coupled with my own observations.

We conduct surveys after the event. We regularly make changes based on this feedback including changing locations, theme, and program. One specific example was adding more buffet stations after an event with only two lines created a significant backlog for participants.

As the founder of Your Dog’s Best Days, I stay close to client and team input through daily conversations during drop-offs and pickups, along with notes shared in our review channels. This keeps feedback practical and tied to how we support each dog’s routines.

We adjust recognition by focusing on clear communication that matches what owners and staff value most. Feedback showed that generic praise felt disconnected, so we shifted toward brief, personalized updates highlighting specific wins like improved playgroup comfort.

One example came when owners mentioned wanting more details on structured activities during extended stays. We began noting small daily achievements in updates, which strengthened trust and helped owners feel more connected to their dog’s progress.

Our process starts after every major win with a simple review. We ask a small group from different teams what felt genuine and what felt forced. We also review anonymous feedback that focuses on fairness, visibility, and whether the success reflected the work of the whole team. We then look at how people engage after the celebration and whether trust and teamwork continue to grow.

One lesson changed the way we celebrate success. We found that public praise often focused on the final result and missed the people who solved important problems along the way. We now share stories that show the full journey and recognize resilience, teamwork, and steady progress. This makes every celebration feel more meaningful, more inclusive, and more genuine.

Our process is not formal, and I think that is actually why it works. With a small team, I hear directly whether something landed or fell flat, whether that is a shoutout at a team meeting or how we mark a big order milestone. I would rather get honest reactions in the moment than run a survey that people fill out just to be polite.

One example is that we used to keep recognition pretty low key, and a few people on the team told me it felt like wins came and went without much notice. We started making a bigger point of calling out specific contributions tied to actual results, like a big account win or a smooth production run, instead of generic praise. That small shift made recognition feel earned instead of routine, and people have responded to that.

My process is simple: I collect feedback closest to the moment a milestone is celebrated, then I compare what people said they valued with what they actually engaged with. In a small startup, milestone celebrations can easily become founder-driven instead of team-meaningful, so I try to keep the loop practical. After a launch, product milestone, or meaningful internal win, I ask a few short questions in our normal communication flow: what felt motivating, what felt performative, and what kind of recognition made the work feel visible. I also look at behavioral signals like participation, response quality, and whether the celebration created momentum or just interrupted work.

What has worked best for me is using lightweight feedback instead of formal HR-style surveys. People are much more honest when the questions are short, specific, and tied to a real event. I want to know whether the celebration matched the effort behind the milestone. For example, some wins deserve a public team-wide note, while others are better recognized by highlighting the specific people who solved the hardest part of the problem.

One improvement came after a product progress milestone where I realized the way I framed the celebration was too focused on the visible outcome and not enough on the behind-the-scenes work. The feedback was essentially that shipping is exciting, but what really motivated the team was having the problem-solving, iteration, and persistence acknowledged too. After that, I changed the structure of milestone recognition. Instead of only celebrating the result, I started breaking recognition into three parts: what we achieved, what obstacles were overcome, and who made the difference. That led to better participation, more thoughtful internal responses, and stronger morale because people felt the work itself was being seen, not just the headline.

The biggest lesson is that celebrations work best when they reinforce culture, not just success. Feedback helps you see whether your recognition is actually motivating people or just checking a box.

Feedback on milestone celebrations is most valuable when it goes beyond measuring participation and instead evaluates whether recognition reinforces learning, collaboration, and long-term motivation. Short pulse surveys, manager conversations, and post-project retrospectives provide meaningful insights into how recognition is experienced across teams. Gallup research consistently shows that employees who receive meaningful recognition are more engaged and significantly less likely to leave, highlighting the connection between thoughtful recognition and organizational performance. One recurring insight revealed that employees placed greater value on celebrating skill development, certification achievements, and knowledge sharing than on traditional milestone announcements alone. Recognition practices were refined to highlight professional growth, business impact, and collaborative success, creating celebrations that felt more personal, purposeful, and aligned with a culture of continuous learning.

We don’t run formal surveys. We run a 15-minute Slack session 72 hours after any milestone we celebrate publicly. That’s it.

Here’s how it works. When we hit something worth marking, a project launch, a retention milestone, a major client renewal, we celebrate on Slack. Usually it’s me posting in the general channel with context on what the team accomplished. Sometimes there’s a small bonus if the milestone directly tied to revenue. Then 72 hours later, I drop a single question in the same thread: “If we hit another one like this, what should we do differently about how we celebrated?”

The timing matters. If you ask immediately after, people say nice things. If you wait a week, they’ve moved on. Three days in is when people actually remember what felt off.

The example that changed how we operate came after we closed a six-figure annual contract with a crypto client. I posted in Slack thanking the team. Sent out a flat bonus split across everyone. Thought it landed well. Then I ran the 72-hour check-in.

Three people said the same thing in different ways: they didn’t know how their specific work tied to that contract. Our content writer said she’d been writing thought leadership posts for that client’s founder for two months but had no idea it was part of a renewal negotiation. Our ops lead said he’d been handling their coverage reports but didn’t realize we were in risk-of-churn mode when he started.

That feedback was a systems problem, not a celebration problem. We were celebrating the win but the team didn’t understand the chain of events that produced it. So I changed two things.

First, I started running a five-minute walkback in the same Slack post where I announce the milestone. I write out the timeline, what each person did, when it mattered, and how it connected to the result. It takes me ten minutes to write and it makes the celebration mean something.

Second, I stopped doing flat bonuses for client renewals. Now the bonus goes only to the people whose work directly prevented churn or closed the upsell. It sounds harsher but it’s clearer. People know what moved the result.

The 72-hour rule caught something I wouldn’t have seen in a quarterly retrospective. You don’t need a process. You need a question, a timeline, and the willingness to act on what you hear.

Running a family HVAC business since 1980 means milestones stack up fast — technician anniversaries, loyal customers, generational ownership transitions. My feedback process lives in the reviews customers leave and the conversations we have in the field, not in formal internal surveys.

One of the clearest examples: a customer mentioned in a review that our technician David had been serving her for decades. When I responded, I shared publicly that David was actually celebrating 31 years with Southern Air that very day. That one exchange told me customers *want* to know the human story behind the service — not just that we show up, but that the same trusted people keep showing up.

That feedback shifted how we recognize tenure internally. Long-term employees aren’t just assets to us — they’re proof points we now actively surface in customer-facing moments, because that’s what builds trust with new customers faster than any ad ever could.

The practical takeaway: don’t wait for an internal review cycle to figure out what resonates. Your customers will tell you what matters through the feedback they already leave — you just have to read it carefully and act on it publicly.

I believe that an organization’s recognition programs must exemplify what the organization values. People leave feedback informally. I see this as an opportunity to frame how employees get recognized to better align it with employee drivers. People value timely and specific recognition over infrequent, large celebrations. We focused on smaller milestones and activities, recognizing victories where we were able to hit major milestones on large and complex initiatives, take on challenging assignments, and efforts to remove roadblocks. This recognition approach not only felt more authentic, but reinforced recognition of people behaviors we wanted to advocate for the organization.

We maintain a two-tier feedback loop, combining anonymized quarterly sentiment surveys with open-forum retrospectives, to ensure our recognition programs reflect the actual technical complexity of our delivery operations. We specifically ask teams whether rewards reflect the effort invested in the most difficult parts of the project lifecycle rather than just the final delivery date.

This feedback previously revealed a significant gap: engineers and architects felt invisible during year-long projects until the final launch, despite the grueling nature of middleware integration or database migration. To fix this, we moved away from a binary celebration model in favor of a peer-nominated system that identifies micro-milestones. We now celebrate technical wins like the successful refactoring of a critical module or the hardening of a security protocol before a major audit. This shift ensures recognition is tied to technical excellence and problem-solving rather than just a calendar date. It also provides junior architects with a clear understanding of the specific behaviors the organization values. Ultimately, feedback loops shouldn’t just measure happiness; they should confirm that the team feels seen throughout the marathon, not just at the finish line. Celebrating the finish line is standard practice, but recognizing technical hurdles cleared along the way is what sustains engineering integrity.

Rather than assuming people value the same recognition, we regularly ask our team what feels meaningful. One consistent piece of feedback was that celebrating team achievements mattered more than recognising individual results alone. We shifted towards acknowledging project completions, successful store fit-outs and customer feedback as team wins, which has created a stronger sense of shared ownership across the business.

As President guiding Kelbe Brothers through industry shifts and a challenging economy, I track operational patterns from our store updates and service practices to see what resonates in how we mark progress.

After opening the De Pere location to replace the prior facility and remodeling the Madison store for better efficiency, we noticed staff input on daily routines pointed to stronger focus on preventive steps.

This shifted our approach to spotlighting achievements around fleet strategies like the 80-20 rule for targeting repeat issues and routine fluid analysis, keeping machines productive longer without added downtime.

We now tie milestone reflections directly to records of working hours and maintenance expenses so decisions stay grounded in what actually extends equipment life.

Tracking attendance patterns and engagement metrics revealed which celebration formats actually landed with team. We noticed certain announcement types consistently generated positive Slack reactions, comments, and follow-up conversations while others generated silence. Analyzing response data to different celebration approaches showed us that peer-win announcements generated 8X more engagement than company-milestone announcements. Specifically, celebrations highlighting “here’s what we learned” received sustained discussion while pure achievement announcements disappeared from conversation within hours. We doubled down on learning-focused celebrations and reduced corporate-announcement style celebrations. One unexpected pattern emerged: celebrations including specific person stories generated longer conversation threads than generic team accomplishments. We shifted toward celebrating individuals and specific situations over abstract achievements. The data-driven approach removed guesswork about what mattered.

We have over 200 people working at Digital Silk, so we don’t run formal surveys for this. Instead, I keep in touch with the managers to stay informed about each person on the teams. One piece of feedback we received became one of our best company culture processes: we have a company meeting every 15 days to showcase our projects, share feedback, and talk about our business. It’s a moment to get together and strengthen our sense of leadership and community.

We collect these insights through our regular team check-ins and by having the owners of celebrations we held provide information in the form of notes in our operational updates. During check-ins, team members share how the celebration affected their motivation and how they’ve experienced it in their day-to-day working lives. From this information, we get a good insight into what’s working well and what needs to change. We use these insights to focus our celebrations on the operational wins people like. This helps to sustain motivation during times of change.

I think that employee recognition should be directly tied to the values that a company holds dear.

After observing my own employees for a while, I realized that recognition was something that was informally discussed every day and was an area where we could truly improve. We began to focus on creating a system that would enable them to understand what it is we value here and how they could achieve similar results in their day to day efforts.

We stopped focusing on the end of the year “big” recognition events and instead focused on more smaller scale victories. We began to specifically recognize employees when they were able to get through certain hurdles in our projects, take on more challenging initiatives and even when they eliminated obstacles in our daily work. It made everyone feel good and it drove the type of behaviors that we wanted to see throughout the whole company.