Gratitude in Leadership: Combat Lessons on Building High-Performing Teams
Thanksgiving week seems like the obvious time to talk about gratitude, but this isn't a feel-good holiday piece about counting blessings. This is about a hard-learned leadership lesson from combat and nuclear operations: gratitude is a tactical weapon for building high-performing teams.
When I commanded 140 personnel as CFO of the 341st Comptroller Squadron at Malmstrom Air Force Base, we managed financial operations for the nation's nuclear ICBM deterrence mission. High stakes. High stress. High operational tempo. No room for error.
In that environment, I learned that gratitude wasn't soft leadership—it was force multiplication. Teams that felt genuinely appreciated consistently outperformed teams that didn't, even when talent and resources were equal.
Later, managing $33 billion in funding in Iraq, I saw the same dynamic. In combat finance, where people were working 80-hour weeks in dangerous conditions far from home, gratitude wasn't a nicety—it was oxygen. The leaders who showed genuine appreciation retained their best people and got discretionary effort when it mattered most. The leaders who didn't bled talent and got compliance but not commitment.
Now, working with business leaders as a fractional CFO, I see gratitude grossly underutilized as a leadership tool. Most leaders think they're expressing appreciation when they're really just going through motions. And most teams are performing below their potential because they're starving for something that costs nothing to provide.
Gratitude vs. Generic Appreciation
Let's start by distinguishing between real gratitude and the corporate-speak version that means nothing.
Generic appreciation: "Great job, team!" or "Thanks for your hard work" or "We appreciate everything you do."
Real gratitude: "Sarah, the way you restructured that reconciliation process last week caught a $15,000 error before it hit the financial statements. That saved us from a messy audit conversation and showed real systems thinking. Thank you."
The difference? Specificity, impact recognition, and genuine acknowledgment of the individual's contribution.
Generic appreciation is background noise. Everyone says it, nobody feels it. Real gratitude requires you to notice what people actually did, understand why it mattered, and communicate both clearly.
In military leadership training, we learn to be specific in both praise and correction. Vague praise is worthless because people don't know what to repeat. Specific gratitude reinforces the exact behaviors and thinking you want to see more of.
The Three Types of Gratitude That Build Teams
Different situations call for different expressions of gratitude. High-performing leaders deploy all three types systematically:
Recognition Gratitude: Acknowledging Achievement
This is gratitude for results delivered—the project completed, the problem solved, the goal exceeded. It's the most common type and the easiest to give.
But here's where most leaders fail: they express recognition gratitude only for the big wins. Major deal closed? Celebration. Quarter exceeded? Praise all around. Daily excellence? Silence.
In the nuclear mission, we couldn't wait for major achievements to recognize people—daily mission success was the expectation, but that didn't mean it was invisible. The NCO who executed a flawless budget closeout? Recognized. The analyst who identified a variance early enough to correct it? Acknowledged. The admin specialist who kept complex scheduling running smoothly? Appreciated.
Recognition gratitude should follow a simple rule: notice what you want repeated. If you want month-end closes to run smoothly, express gratitude when they do. If you want people to catch problems early, acknowledge when they do. If you want collaboration across teams, recognize when it happens.
Effort Gratitude: Valuing the Process
This is gratitude for how people approach their work, regardless of outcome. The late nights, the creative thinking, the persistence through difficulty, the care taken even when no one's watching.
Effort gratitude is harder because results are visible and effort is often not. But it's crucial for sustaining morale through difficult periods.
In Iraq, we managed massive financial complexity with imperfect systems and constant disruptions. Success wasn't always visible—sometimes success was just preventing catastrophe. The people working those problems needed to know their effort mattered even when results weren't spectacular.
"I know this reconciliation has been brutal, and we're still not where we need to be. But the way you've stayed on it, the creative approaches you've tried, the fact that you're still pushing—I see it and I appreciate it. We're going to figure this out because you're not quitting on it."
That's effort gratitude. It sustains people through the grind.
In business, effort gratitude is what keeps your best people engaged during tough quarters, difficult implementations, or strategic pivots that take longer than expected. Results will come, but effort comes first—and acknowledging that effort sustains the behaviors that eventually produce results.
Character Gratitude: Appreciating Who They Are
This is gratitude for the qualities people bring beyond just task execution—their integrity, their attitude, their impact on team culture, their mentorship of others.
Character gratitude is the rarest and most powerful because it recognizes people as humans, not just productivity units.
"I appreciate that when things got tense in that client meeting, you stayed professional and solution-focused. That's who you are, and it sets the standard for this team."
"The way you've helped onboard the new analysts without being asked—that's leadership, and it makes this whole team stronger. Thank you."
In the military, we talked about "wingman culture"—the idea that you take care of the people around you, not because it's in your job description, but because that's what keeps the mission and the team intact. Character gratitude reinforces that culture.
I've seen character gratitude transform team dynamics in finance functions. When you acknowledge the person who stays calm under pressure, others aspire to that standard. When you appreciate the team member who helps others succeed, you signal that collaboration matters as much as individual performance.
The Gratitude Delivery System
Knowing what to appreciate is half the battle. Delivering it effectively is the other half. Here's the tactical framework:
Public vs. Private
Some gratitude should be public (team meetings, all-hands, written communication that others see). This amplifies the recognition and signals to the broader team what behaviors and results you value.
Some gratitude should be private (one-on-one, direct message, personal conversation). This creates intimacy and ensures the person knows you personally noticed, not just that you're performing for an audience.
Use both. Public recognition without private follow-up feels performative. Private recognition without any public acknowledgment leaves others unaware of what excellence looks like.
Immediate vs. Reflective
Immediate gratitude is expressed right after the action or achievement. It's spontaneous, authentic, and directly linked to what just happened.
"That was exactly the right call in that meeting. Well done."
Reflective gratitude comes later, often when you've had time to see the full impact of someone's contribution.
"I've been thinking about how you handled that crisis three weeks ago. The way you kept the team focused and worked the problem systematically—that's what got us through it. I wanted you to know I see that."
Both matter. Immediate gratitude shows you're paying attention. Reflective gratitude shows you're still thinking about their contribution, which signals it genuinely mattered.
Verbal vs. Written
Verbal gratitude is powerful for immediacy and personal connection. The tone, the eye contact, the authenticity in your voice—it all reinforces the message.
Written gratitude has different strengths: it's permanent, can be revisited, and often feels more considered and therefore more meaningful.
In the Air Force, we had formal awards and decorations, but we also had handwritten notes from commanders. Both mattered, but the handwritten note often meant more because it was personal and unexpected.
I encourage my fractional CFO clients to keep a simple practice: once a week, write a brief email or note to someone on the team expressing specific gratitude for something they did well. Two paragraphs max. Specific. Genuine. No ask attached.
The impact is disproportionate to the effort.
Gratitude as Performance Feedback
Here's where gratitude becomes tactical: when you express specific appreciation for the right things, you're actually providing performance feedback disguised as thanks.
"I noticed how you explained that budget variance to the department head yesterday—you didn't just show the numbers, you helped them understand the story behind the numbers. That's what transforms data into decision-making insight. More of that, please."
You've just:
Acknowledged their effort
Identified specific high-value behavior
Explained why it matters
Encouraged repetition
That's more effective than formal performance review feedback because it's immediate, specific, and positive-framed.
In combat finance, we used gratitude systematically to shape team behavior. Junior analysts who caught errors early got acknowledged publicly. Team members who collaborated across silos got recognized. People who kept calm under pressure got appreciated. Over time, the culture shifted toward those behaviors because people knew they were valued.
This isn't manipulation—it's leadership. You're reinforcing the behaviors that drive team success while making people feel genuinely valued. Everyone wins.
The Gratitude Discipline
The problem with gratitude as a leadership practice is that it's never urgent. You're always too busy. There's always another fire to fight, another meeting to attend, another deadline to hit.
So gratitude becomes something you'll do "when things calm down"—which means never.
High-performing leaders treat gratitude as discipline, not discretionary activity:
Weekly gratitude quota: Identify three specific things team members did well this week and acknowledge them. Put it on your calendar as a recurring task. Make it non-negotiable.
Start-of-meeting appreciation: Before diving into agenda items in team meetings, take 60 seconds to acknowledge one or two recent wins or efforts. It sets a positive tone and takes almost no time.
End-of-project gratitude: When any project or major task completes, immediately send thank-you messages to key contributors. Don't wait. Don't batch it. Strike while the achievement is fresh.
Gratitude rounds: Once a quarter, block 30 minutes and go through your team roster. For each person, ask yourself: what have they done recently that I haven't acknowledged? Then send messages or schedule brief conversations to fix that gap.
These aren't time-consuming practices. They're discipline practices. And like all disciplines, they compound over time.
When Gratitude Rings Hollow
Gratitude without integrity is manipulation. People can smell fake appreciation from a mile away. Here's what makes gratitude ring hollow:
Gratitude without action: You thank people for working late nights but never address the systemic reasons they're working late nights. You appreciate their effort but don't fix the broken processes that make effort heroic. That's not gratitude—that's exploitation dressed up with nice words.
Gratitude without fairness: You praise one person publicly while ignoring equivalent contributions from others. Or you thank people effusively while underpaying them. Gratitude can't substitute for fair treatment.
Gratitude without follow-through: You express appreciation for someone's initiative and then shoot down every idea they bring forward. You say you value their input and then never implement it or explain why not. People learn quickly that your gratitude is performative.
Real gratitude exists within a leadership framework that includes fair compensation, reasonable expectations, systematic problem-solving, and genuine respect. It's not a substitute for those things—it's a complement to them.
The Compound Effect
A single expression of gratitude might seem trivial. And in isolation, maybe it is. But gratitude is a compound practice—the impact builds over time.
Teams that receive consistent, genuine appreciation develop different characteristics:
Higher discretionary effort: When people feel valued, they give more. Not because they have to, but because they want to. That's the difference between compliance and commitment.
Lower attrition: People leave jobs for many reasons, but one of the most common is feeling unappreciated. "Nobody noticed what I did" is a resignation letter waiting to happen.
Stronger collaboration: When leaders model appreciation, team members start appreciating each other. The culture shifts from individual competition to collective success.
Faster development: Gratitude that highlights specific high-value behaviors accelerates learning. People know exactly what excellence looks like because you've shown them through acknowledgment.
I've watched this transformation in military units and business teams. The culture shift isn't dramatic or sudden—it's gradual and cumulative. But six months of consistent gratitude produces teams that operate fundamentally differently than they did before.
Beyond Thanksgiving
Thanksgiving is a good reminder to express gratitude, but the real question is: what happens the other 364 days of the year?
The leaders I most respected in the Air Force—the commanders who built high-performing squadrons, who retained top talent, who got extraordinary results from ordinary resources—weren't the ones who gave great Thanksgiving speeches.
They were the ones who said thank you on Tuesday morning after a rough Monday. Who acknowledged the midnight effort that nobody else saw. Who noticed the quiet excellence that doesn't generate headlines but keeps the mission running.
That's the gratitude that builds teams. Not the annual performance review praise or the holiday platitudes, but the consistent, specific, genuine appreciation woven into daily leadership.
Your finance team is grinding through month-end close, managing cash flow, fielding vendor issues, supporting business decisions with analysis, and keeping the financial infrastructure running. Most of that work is invisible until it breaks.
Don't wait until it breaks to notice. Don't wait until they quit to appreciate them. Don't wait until Thanksgiving to say thank you.
Build gratitude into your leadership operating system. It costs nothing. It takes minutes. And it transforms teams.
That's not soft leadership. That's force multiplication.
Gabriel Denny Financial Services, LLC