30-Day Gratitude Challenge to Foster Team Spirit this Holiday Season

Gratitude at work does not mean pretending every day is wonderful.

Teams can have deadlines, disagreements, frustrating processes, difficult clients, and genuine problems that need attention—and still make room to notice what is working and acknowledge the people who make work easier.

That is the idea behind this 30-Day Workplace Gratitude Challenge.

Whether you use it during the holiday season, at the beginning of a new year, during employee-appreciation activities, or simply when your team needs a reset, the goal is simple:

Spend a few intentional minutes noticing specific people, actions, opportunities, and everyday moments that might otherwise go unrecognized.

What Gratitude at Work Can—and Cannot—Do

Gratitude practices are simple positive-psychology interventions that have been studied in both general and working populations.

A systematic review of randomized studies involving workers found that gratitude interventions showed promising results for outcomes including perceived stress and depressive symptoms, although results for overall well-being were inconsistent and the studies varied considerably in design.

You can review the research in this systematic review of gratitude interventions among workers.

That makes gratitude worth exploring as a small workplace practice.

But gratitude is not a substitute for:

• Fair compensation.
• Manageable workloads.
• Clear expectations.
• Healthy boundaries.
• Useful feedback.
• Psychological and physical safety.
• Addressing conflict.
• Fixing broken processes.

A team should be able to appreciate what is good and still speak honestly about what needs to improve.

Gratitude Is More Powerful When It Is Specific

Compare these two messages:

“Thanks for everything!”

and:

“Thank you for catching the error in the report before it went to the client. You saved us from having to correct it later.”

The second message tells the employee exactly what they did and why it mattered.

That makes appreciation more informative as well as more personal.

The same principle applies to effective workplace communication: clarity makes a message more useful.

How to Run the 30-Day Gratitude Challenge

Keep the challenge light.

No employee should need to write an essay every morning or publicly reveal personal information.

A few minutes is enough.

• Make participation inviting rather than forced.
• Keep prompts short.
• Allow private reflection as well as public appreciation.
• Be specific when recognizing another person.
• Do not use gratitude to shut down legitimate concerns.

You can complete the prompts individually, post responses on a team board, use a shared digital channel, or choose one prompt for the beginning of a meeting.

30 Days of Workplace Gratitude

Day 1: Notice Someone Who Made Your Work Easier

Think of one person whose action saved you time, reduced confusion, solved a problem, or helped you move forward.

If appropriate, tell them specifically what they did.

Day 2: Appreciate Something You Usually Take for Granted

Maybe it is reliable technology, clean facilities, good coffee, working air conditioning, a quiet room, or easy access to information.

Day 3: Recognize Good Follow-Through

Who completed something when they said they would without needing repeated reminders?

Reliable work often becomes invisible precisely because it creates so little drama.

Day 4: Thank Someone Behind the Scenes

Consider someone whose contribution is important but not highly visible.

Recognition should not depend entirely on who speaks the most in meetings.

Day 5: Appreciate Something You Learned

What do you know today that you did not know six months ago?

Who or what helped you learn it?

Day 6: Recognize a Helpful Question

Think about a question someone asked that prevented a mistake, clarified a decision, or made the team think differently.

Day 7: Appreciate Progress

Choose something that is not finished yet but is better than it was before.

Progress deserves to be noticed even before the final result arrives.

Day 8: Thank Someone Who Shared Useful Feedback

Useful feedback is not always comfortable.

Think of feedback that improved your work, changed your approach, or helped you see something you had missed.

Day 9: Appreciate a Routine That Works

Which recurring process makes your work more predictable?

It might be a weekly meeting, project template, checklist, shared calendar, or communication routine.

Day 10: Recognize a Problem Solver

Who recently moved beyond identifying a problem and helped find a workable solution?

Day 11: Appreciate a Skill Someone Else Has

Maybe someone explains difficult information clearly, catches details, organizes chaos, calms difficult customers, or creates beautiful work.

Name the skill rather than simply saying the person is “great.”

Day 12: Notice Something That Has Improved

What is easier, clearer, faster, or better than it was a year ago?

Day 13: Thank Someone Who Helped Without Being Asked

Notice an act of appropriate initiative.

Day 14: Appreciate a Mistake You Learned From

You do not have to be grateful that the mistake happened.

Instead, ask whether anything useful changed because of what you learned afterward.

Day 15: Halfway Reflection

What have you noticed during the first half of the challenge that you normally overlook?

Day 16: Recognize Someone Who Communicates Clearly

Think of someone whose updates make it easier to understand what is happening without chasing them for information.

Day 17: Appreciate a Moment of Flexibility

Who adapted when plans changed instead of making a difficult situation even harder?

Day 18: Notice a Small Win

Not every accomplishment needs to be a major launch, promotion, or record-breaking result.

Identify one ordinary thing that went well today.

Day 19: Appreciate Someone Who Taught You Something

It could be a manager, coworker, employee, customer, mentor, or even someone much newer to the organization.

Day 20: Recognize Good Teamwork

Think about a recent moment when two or more people worked together especially well.

What made the collaboration work?

That question connects gratitude with the practical behaviors behind stronger team performance.

Day 21: Appreciate Something Outside Work

Your entire identity does not need to revolve around your job.

Privately notice something outside work that matters to you—a relationship, hobby, place, experience, routine, or ordinary comfort.

Day 22: Thank Someone Who Was Patient

Who gave you time to learn, explain, correct something, or work through a difficult situation?

Day 23: Appreciate a Resource You Have Access To

Consider training, software, equipment, expertise, documentation, flexible working arrangements, or another resource that supports your work.

Day 24: Recognize a Good Decision

Think of a recent decision—large or small—that improved an outcome.

What made it a good decision?

Day 25: Appreciate Someone's Reliability

Who makes your work easier simply because you know you can depend on them?

Day 26: Thank Someone for Something Specific

Send one short message using this structure:

“Thank you for [specific action]. It helped because [specific impact].”

For example:

“Thank you for organizing the client notes before yesterday’s call. I was able to prepare much faster because everything was in one place.”

Day 27: Recognize Something Difficult That the Team Handled Well

This is not about pretending the difficult situation was good.

Focus instead on how people responded.

Day 28: Appreciate a Boundary

Think of a boundary, expectation, policy, or routine that protects people's time or makes work more sustainable.

A healthy workplace does not require employees to be grateful for burnout.

Day 29: Notice What You Want More Of

Review the things you appreciated during the month.

Do you see a pattern?

Maybe you repeatedly appreciated:

• Clear communication.
• Quiet focus.
• Reliable coworkers.
• More autonomy.
• Helpful feedback.
• Collaboration.

Gratitude can sometimes reveal what you value—and therefore what you may want to protect or build more intentionally.

Day 30: Recognize the Team

Finish by identifying something the group accomplished or navigated together.

Ask:

• What are we proud of?
• What helped us succeed?
• Who contributed in ways we may have overlooked?
• What behavior should we carry forward?

Create a Gratitude Board

If your team enjoys visible participation, set up a physical or digital gratitude board.

Team members can add short notes such as:

• “Thank you to Diana for helping with the client handoff.”
• “Grateful that Operations fixed the reporting issue.”
• “Appreciated having an uninterrupted afternoon to finish the proposal.”
• “Thank you to Marcus for explaining the new system.”

Keep it optional and genuine.

A gratitude board filled with obligatory compliments defeats the purpose.

Try a Private Gratitude Journal

Not everyone enjoys sharing reflections publicly.

A private version can be as simple as writing:

• One thing that went well today.
• One person whose action you appreciated.
• One thing you learned.
• One ordinary thing that made the day easier.

This keeps the challenge accessible to people with different personalities and communication styles.

Do Not Turn Gratitude Into Toxic Positivity

A gratitude challenge becomes counterproductive if people start hearing:

• “Stop complaining and be grateful you have a job.”
• “Look on the bright side instead of raising the problem.”
• “We should focus on positivity, not what went wrong.”

A person can be grateful for their coworkers and still believe the workload is unreasonable.

An employee can appreciate their manager and still disagree with a decision.

A team can celebrate progress and still identify a failing process.

If chronic complaining is affecting the workplace, the solution is also not to demand artificial positivity. When the Job Was Good and How to Protect It When Others Aren’t explores the difference between constructive concerns and patterns of negativity that stop being useful.

Use Gratitude to Identify What Is Working

At the end of the 30 days, do not simply ask whether everyone “felt more positive.”

Look at the patterns.

What did people repeatedly appreciate?

• Clearer expectations?
• Helpful teammates?
• Autonomy?
• Recognition?
• Quiet work time?
• Reliable systems?
• Flexibility?
• Access to leadership?

Those answers can provide useful clues about what employees value and which practices are worth protecting.

A Simple Recognition Formula for Managers

If you are a manager, use this three-part formula:

1. Name the action: What exactly did the person do?
2. Name the impact: Why did it matter?
3. Connect it to the team: What did that behavior make easier, better, or more effective?

For example:

“Thank you for alerting us as soon as you realized the deadline was at risk. That gave us enough time to adjust the workload and still deliver to the client on schedule.”

That is more useful than simply:

“Great job!”

Optional Tools for the Challenge

You do not need to purchase anything to practice gratitude.

A sticky note, notebook, shared document, or team chat works perfectly well.

If your team enjoys physical office and organization tools, the original version of this article included a collection of recommended office products on Amazon.

Printable Tools for Team Challenges

If you prefer printable trackers, gratitude pages, planners, checklists, and other visual tools for workplace or personal challenges, explore the Efficiency Plan Etsy Shop.

Want Help Strengthening Your Team Culture?

If your team needs more than a challenge—such as clearer expectations, stronger accountability, better communication, or more effective workplace systems—explore Efficiency Plan consulting options.

The Takeaway

A gratitude challenge does not need to convince everyone that work is wonderful.

Its value is much simpler.

Notice what normally becomes invisible.

Recognize useful contributions.

Say thank you specifically.

Reflect on what is working.

And continue speaking honestly about what is not.

A healthy workplace can hold appreciation and improvement at the same time.

— Ashley Everhart
Founder, Efficiency Plan