Recognition in Rhythm: How symplr Wove Rewards into Their Intranet Experience with MangoApps

For teams managing rewards and recognition across a distributed workforce, the default outcome is inconsistency. Managers do their best — a gift card here, a public thank-you there — but without a shared system, appreciation stays invisible to the people who need to see it most. symplr, a healthcare governance, risk, and compliance company, solved this not by purchasing a standalone recognition platform, but by activating the recognition module already inside the intranet their employees used every day. In 2024 alone, that decision produced over 1,500 recognitions, more than 2 million points distributed, and nearly 900 employees receiving public shoutouts on their company feed.

That outcome doesn't happen by accident. It happens when a team designs for culture first, deploys with discipline, and keeps working at it after launch.

The problem with ad hoc recognition in distributed companies

Only 23% of employees strongly agree they receive the right amount of recognition for the work they do, according to Gallup. That leaves the large majority of most workforces feeling underappreciated — not because managers don't care, but because informal recognition doesn't scale.

symplr had exactly this dynamic before formalizing their program. Managers were expressing genuine appreciation through disconnected gestures: gift cards, surprise treats, one-off thank-you emails. The appreciation was real. But it wasn't visible beyond the immediate exchange, and it wasn't consistent across teams, locations, or job levels. Gratitude happened — it just didn't build culture.

For a global workforce spread across the U.S., India, and beyond, this gap had consequences. Remote and distributed employees are disproportionately at risk of feeling invisible, and structured, visible recognition is consistently cited as one of the top three retention levers for fully remote teams, according to the Gallup 2026 State of the Global Workplace report. The stakes show up in turnover data too: companies with highly effective recognition programs see 31% lower voluntary turnover than those with ineffective ones, per Bersin by Deloitte research.

symplr's team recognized the gap. The question was what kind of solution was actually worth building.

Why symplr chose to build inside an existing platform

The conventional answer to a broken recognition process is a new tool. symplr made a different call.

Since 2021, symplr had been using MangoApps as the backbone of their intranet, symplr IQ — a central hub for internal communications, collaboration, and company culture. When the need for a more structured recognition approach surfaced, the team didn't go looking for a standalone recognition vendor. They activated the recognition module already available within MangoApps.

The logic was about adoption, not just cost. According to SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — and according to Social Edge Consulting, only 13% of employees use their intranet daily. A standalone recognition platform requiring a separate login would have encountered the same adoption friction as any other tool employees don't naturally reach for. By embedding recognition inside symplr IQ, the team removed that friction before the program launched. Employees didn't have to form a new habit; recognition became part of the digital rhythm they already had.

Organizations that integrate recognition into a single digital workplace platform consistently report higher program participation rates than those running standalone tools, because employees don't have to context-switch to give or receive acknowledgment. symplr already had near-universal adoption of symplr IQ. That existing adoption was itself a strategic asset.

As Melissa Hoyos, symplr's VP of Internal Communications, put it: "We wanted something very consistent across the board, and [MangoApps] was going to provide it to us."

Designing the program before touching the software

symplr spent several months on program design before any configuration started. The internal comms, talent management, and HR operations teams sat together and worked through hard questions: What behaviors should earn points? How do we prevent recognition from feeling performative? Who should have the authority to give points — and what happens if that authority creates a bottleneck at the wrong layer?

They built awards that reflected symplr's own voice, not vendor-template language. Every award name connected to a stated company value. Kevin Williams, Director of HR Operations, worked through the complexity of a global point structure — ensuring that reward values felt equitable across countries with different purchasing power, without creating imbalances that would undercut the program's credibility across a workforce spread across the U.S., India, and beyond.

"We wanted to make sure when we launched our R&R program that we launched it right," Williams explained. "We did not want to do several iterations of this, so we spent… several months internally making sure that we considered everything."

Recognition programs tied to company values — rather than generic praise — are significantly more likely to drive the specific behaviors leadership wants to reinforce, according to SHRM and WorldatWork benchmarking research. symplr's investment in design reflected that principle. The awards weren't decoration; they were the mechanism for encoding culture.

The launch: communication, training, and no surprises

Before the program went live to the full organization, Emily Biery, Senior Internal Communications Specialist, led a three-part rollout strategy.

The first track was a personalized email from the CHRO, repurposed as a company-wide intranet post explaining what the program was, why it existed, and how it worked. The second was live training sessions with senior leaders walking through their specific role in awarding points. The third was tailored sessions for HR business partners on reporting tools and how to coach their leaders on participation.

Olivia Aguilar, symplr's Intranet Engagement Specialist, coordinated the entire launch — keeping timelines, communications, and training sessions aligned so nothing caught employees off guard. "Her coordination helped to ensure that there were no surprises for anyone," Biery noted, "and everyone knew what and when to expect updates and how to access support."

The team also built a private resource space for point awarders — a place to find FAQs, look up which awards applied in which country, and stay current on any program updates. The goal was to give every person with recognition authority the ongoing support to use it well, not just on launch day.

By treating the launch as a cultural milestone rather than a system deployment, they set the tone for long-term participation.

What year one produced

The program started with controlled access: senior and executive leaders received point-awarding authority first. The design logic was to establish norms before scale. In practice, recognition bottlenecked at the leadership layer. As Jami Mims, Director of Talent Management, described it: "It kind of got bottlenecked… just because they're, as we all are, moving fast and incredibly busy."

The team's response was deliberate expansion. Rather than opening access broadly, they moved down one layer at a time. By year two, the program had grown from 30 point awarders to 70 managers — roughly 2.3 times the original coverage.

The results in 2024 were concrete: over 1,500 recognitions issued, more than 2 million points distributed, and nearly 900 employees receiving acknowledgment visible on the company feed. Employees could log into symplr IQ and see recognition happening in real time — not in a spreadsheet, not in an email chain, but in the same feed they used for company news and team updates.

The employee engagement signal in symplr's eNPS survey shifted alongside program adoption. "We're not seeing as many in our eNPS survey people saying things such as, 'Oh, we want to find a way to be recognized,'" Mims noted. "People see that they are being recognized. And so I know that that's positive."

What teams building recognition programs can take from this

symplr's experience maps to five principles that apply beyond their specific context.

Embed recognition into the system employees already use. A standalone recognition tool will be adopted primarily by the employees who are already motivated to give recognition. Embedding it inside an existing intranet removes that selection effect — recognition becomes the obvious path, not an extra step.

Design for culture before configuring software. The several months symplr spent on program design wasn't overhead. It was the reason the launch landed as a cultural signal rather than a routine HR rollout. Awards that sound like the company's own values do more work than generic ones.

Launch with controlled access, then expand deliberately. Starting with senior leaders allowed for learning and course correction before scale. Expanding to 70 managers in year two created sustainable coverage without diffusing accountability.

Give awarders ongoing support. Inactive awarders mean employees who aren't being recognized. HR business partners playing a coaching role — nudging leaders who haven't awarded recently, reminding them that points exist and should be used — sustained participation without requiring a separate management layer.

Measure leading indicators, not just outcomes. Active awarder counts, participation rates, and eNPS comments about recognition tell you whether the program is working before the signal shows up in turnover or engagement scores. Waiting for lagging indicators means losing the window for early correction.

For teams that want to understand how recognition fits into a broader employee engagement strategy, the full webinar with the symplr team is available at From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program.

Recognition that sticks isn't built by selecting the right software. It's built by the decisions made before the software is configured, maintained by the decisions made after launch, and sustained by the people with enough authority and enough support to make it a daily practice.