CSR practitioners are used to building programs under two kinds of scrutiny. The work has to be credible to communities, partners, investors, and reporting audiences, but it also has to feel real to employees whose trust in corporate commitments may already be uneven. A volunteer campaign, giving strategy, sustainability goal, or community partnership can be well-run and still feel distant from the daily life of the company.
That distance matters because employees do not experience CSR only as a policy portfolio. They read it as evidence. They notice what the company chooses to fund, what leaders make time for, which communities are treated as partners, and whether responsibility shows up in operating choices or only in communications. Over time, those signals become part of how employees decide what kind of organization they work for.
What the CSR Research Shows
Ante Glavas and Ken Kelley’s study, The Effects of Perceived Corporate Social Responsibility on Employee Attitudes, gives this intuition some empirical grounding. In a study of 827 employees across 18 organizations, they found that employee perceptions of CSR were positively related to job satisfaction and organizational commitment, with work meaningfulness partly explaining those relationships. Their contribution was not simply that CSR may support employee attitudes; it was that employees appear to be affected by how they believe the organization treats people beyond themselves.
That changes the practical question for CSR managers. Awareness still matters, but awareness is not the same as meaning. Employees may know the company has a foundation, a volunteer platform, a giving campaign, or a sustainability strategy, yet still have no lived connection to the human stakes of that work. The design challenge is not only whether employees can find the program. It is whether the program gives them enough proximity, context, and reflection to understand why it should matter.
Glavas and Kelley are careful about what they mean by CSR. They are not describing a loose collection of good deeds, nor are they treating responsibility as a reputation asset managed from the edge of the business. Their definition centers on care for the well-being of others and the environment, connected to business value and embedded in strategy, structures, and daily practice. That matters because employees are more likely to perceive CSR when it is woven into how the organization behaves, not only when it is reported after the fact (Glavas and Kelley, 2014).
The study also helps explain why some CSR work feels more immediate to employees than other work. In their model, social responsibility had an additional effect beyond the general CSR factor; environmental responsibility did not show the same additional effect. The authors suggest that the difference may be relational. Social responsibility makes people more visible: employees, customers, suppliers, communities, and others affected by the organization’s choices.
That finding should not be used to rank social issues above environmental ones. It points instead to a design problem many CSR teams already recognize. Environmental commitments often have profound human consequences, but the human relationships can be harder for employees to see. A climate target, waste-reduction strategy, or procurement standard may be consequential and still feel abstract unless the program helps employees connect the work to people, places, and choices they can understand.
Designing for Connection, Not Just Awareness
RW’s Transformative Approach sits in that gap. It asks practitioners to look beyond the activity itself and examine the conditions around it. Does the experience invite employees into relationship, or does it keep them at the level of task completion? Does it prepare people to encounter difference with humility, or does it assume good intent will be enough? Does it give participants a way to interpret discomfort, surprise, resistance, or connection after the activity ends?
The practical spine of the approach is Brief-Guide-Debrief. The Brief happens before the activity and frames purpose, context, and posture. The Guide function happens during the experience, when participants may need help staying present to complexity rather than retreating into task mode. The Debrief happens afterward, giving people room to interpret what happened and connect it to identity, behavior, and future choices. Without that arc, even a well-run volunteer event can remain a transaction: employees show up, complete the activity, feel something briefly, and return to work mostly unchanged.
A program can serve people and still leave the volunteer standing outside the relationship as a helper, benefactor, or observer. That posture may generate participation, and sometimes it may meet a real need, but it does not reliably change how employees understand proximity, power, or mutual responsibility. In Realized Worth’s language, the more transformative move is toward “with”: partnership, mutual change, and the slow dissolution of the fixed roles of helper and helped. From Helping to Belonging makes that argument directly, tying well-designed volunteering to proximity, structured reflection, and the practice of keeping another person’s full humanity in view.
The research supporting employee volunteering is important because empathy work is easy to overstate. A participant may leave a conversation moved, unsettled, or more curious than they were before, but none of those responses automatically proves durable change. Stories can point to something real, but they cannot carry the evidence burden alone. Participation data has the same limit; it tells us who showed up, not whether the experience altered how people relate, decide, or work with difference. A stronger design has to ask what would need to be true for the experience to matter beyond the hour itself, then build the operational conditions to test that honestly: facilitation capacity, privacy protections, manager support, partner readiness, cohort size, data quality, and enough humility to learn from mixed results.
From Communications Problem to Design Problem
For CSR managers, the practical shift is not to abandon participation metrics or reporting requirements. Those are part of the job. The shift is to treat employee engagement less like a communications problem and more like a design problem. Employees may know the company has a volunteer platform, a giving campaign, or a community strategy, but the deeper question is whether those structures help them encounter the human stakes of the work with enough support to make meaning from it. Without that, CSR stays visible but thin.
That means looking closely at the moments before, during, and after participation. Before the experience, are employees being prepared for relationship, or only briefed on logistics? During the experience, is anyone helping them navigate discomfort, curiosity, confusion, or the temptation to stay at the surface? Afterward, is there a real debrief, or only a thank-you message and a photo recap? These are not cosmetic choices. They shape whether the experience remains an activity or becomes part of how people understand their role in the organization and in the wider community.
Translating CSR Research Into Volunteering Program Design
Glavas and Kelley give the field a helpful empirical foundation: perceived CSR can be connected to meaningfulness, job satisfaction, and commitment. RW’s Transformative Approach turns that insight into process: Brief the meaning, Guide the encounter, Debrief the learning, and design for the different ways people enter the experience.
The Empathy Project (see below: “Want help building the champion side of this?”) gives practitioners a practical test case for doing that work at scale without pretending that scale itself is the point.
Employees are already reading CSR. The question is whether the program gives them something true enough, close enough, and well-designed enough to read differently.
Further Reading
The article draws on the Glavas and Kelley study together with Realized Worth’s Transformative Approach. The list below points to the underlying research and to the RW framework pages that explain how to put it into practice.
Empirical research cited in the article
Glavas, A. and Kelley, K. (2014). The Effects of Perceived Corporate Social Responsibility on Employee Attitudes. Business Ethics Quarterly, 24(2), 165–202. A study of 827 employees across 18 organizations linking perceived CSR to job satisfaction and organizational commitment, with work meaningfulness as a partial mediator. Full PDF available via the authors’ page.
Glavas and Kelley, 2014 full text PDF: University of Notre Dame mirror.
Realized Worth frameworks referenced in the article
Transformative Volunteering: the framework overview. The conceptual home for RW’s Transformative Approach, including the three Keystone Behaviors and the rationale for moving from participation to identity change.
From Volume to Value: the framework for Transformative Volunteering. Explains the Brief-Guide-Debrief cycle in operating detail and why it is the design spine of the approach.
The Journey of the Volunteer: Tourist, Traveler, Guide. The framework for the different ways people enter and inhabit volunteer experiences. Important context for the article’s claim that programs should design for the range of postures people bring, not for a single average participant.
From Helping to Belonging: Rethinking Corporate Volunteering. The argument that the volunteer’s posture matters. Moves the design goal from helping to belonging, and from a charity orientation to a solidarity orientation.
The Empathy Project: a structured volunteer experience designed to build global empathy at scale. RW Institute’s coalition initiative referenced at the end of the article. Practical test case for putting the Transformative Approach into operating practice across many companies.
Supporting RW writing on the design points in the article
Fostering Growth Through Critical Reflection. Reflection as the operating mechanism of the Debrief. Connects the article’s argument that the work after the activity is what allows the experience to land.
Why Most Volunteer Programs Don’t Change Anyone. A direct treatment of the gap between participation and change, and the design conditions required for the gap to close.
From Burnout to Breakthrough: the neuroscience of empathy and compassion in corporate volunteering. The neuroscience supporting the article’s distinction between participation that moves people briefly and experiences designed to alter how people relate to difference over time.
Volunteer Leader Networks: a tipping point strategy for transformative employee engagement. The organizational system that turns isolated transformative experiences into a durable culture, addressing the article’s call to treat engagement as a design problem.
Creating Conditions for Transformation, Not Controlling Experience. On the design posture the article points toward: build the conditions, do not over-script the outcome.
Where Does the Value of Employee Volunteering Come From? Useful complement to the article’s argument that participation metrics alone do not tell the meaning story.
Want help building the champion side of this?
The harder problem for most CSR managers is not running one well-designed event. It is building a network of champions who can run Briefs and Debriefs consistently across teams and time zones, without the program lead having to be in the room each time.
The Empathy Project was built with that problem in mind. It is a six-week structured volunteer experience that puts the Brief and the Debrief in champions’ hands from day one: a one-hour champion-led Brief that establishes context, purpose, and norms; four hours of one-on-one conversations between employees and partners from different parts of the world, designed around the conditions Pettigrew and Tropp (2006) identified as predictive of prejudice reduction; one to two hours of structured reflection; and a one-hour team Debrief, led by the same champion, connecting what surfaced back to the work.
Six hours of engagement per participant, spaced across six weeks, with champions practicing the three keystone behaviors throughout. We built it this way because most attempts at Brief-Guide-Debrief collapse when champions have to invent the structure from scratch under deadline. The Empathy Project supplies the structure, the training, and a real cohort of employees to practice with. The practitioner behaviors tend to stay in the organization after the program ends.
If your team is working on internal champion capability and looking for a program to anchor that work, we invite you to take a look at the Empathy Project.
A smaller starting point is available to anyone reading: write a five-minute Brief for your next event, protect fifteen minutes at the end for the three questions, and listen to what comes back when you ask, “what surprised you?” Those answers are often a more useful read on whether the day produced any movement than any of the standard dashboard numbers.






