Being the Pulse of the Team

Being the Pulse of the Team#

You're the CMO's early warning system for team issues. By the time they hear about it from you, you've already thought about what to do.

Why the VA Sees Things the CMO Doesn't#

Your CMO talks to clients, leads strategy sessions, and runs meetings. They see people in "performance mode" - presenting, reporting, pitching. You see the in-between moments. The Slack messages at 11pm. The delay before someone responds. The sigh before they say "yeah, it's fine."

People tell the VA things they won't tell the boss. Not because they're hiding anything - because the VA feels safer. Less judgment, less career risk, less formality. That makes you a bridge between the team and the CMO. The skill is being that bridge without breaking anyone's trust.

Signals to Watch For#

Team health rarely announces itself with a crisis. It shows up in small shifts over days and weeks. Here's what to watch:

None of these signals alone means something is wrong. Two or three together over a couple of weeks? That's worth flagging.

Checking In Without Being Intrusive#

You don't need formal 1:1s or survey forms. The best check-ins happen naturally:

• "Hey, just wanted to make sure you have what you need for the Brightline deck. Anything I can take off your plate?"
• "I noticed you've been burning the midnight oil on the Acme campaign. Everything going okay, or is the scope bigger than expected?"
• "Quick heads up - the CMO moved the deadline for the quarterly report to Friday instead of next Wednesday. Does that work for your schedule?"

The pattern: be helpful first, observant second. People open up when they feel supported, not when they feel watched.

The Bridge Without Breaking Trust#

This is the hardest part of the job. Someone tells you they're struggling, overwhelmed, or frustrated with a decision the CMO made. What do you do?

Rules for being the bridge:

1. Never quote someone without their permission. "Alex told me he hates the new process" is a trust violation. "I'm picking up some friction around the new reporting process - might be worth checking in with the team" is a bridge.

1. Translate feelings into actionable observations. The CMO doesn't need to know someone is "stressed." They need to know "the Acme deliverables are taking twice as long as estimated and the team might need more capacity."

1. Ask before escalating. If someone shares something personal, ask: "Would it be helpful if I gave the CMO a heads up, or would you rather handle that yourself?" Respect their answer.

1. Separate venting from problems. Sometimes people just need to complain. That's not a flag. It's a Tuesday. The flag is when the complaining doesn't stop, or when it turns into disengagement.

Coordinating Across the Team#

When multiple people work on the same client, things get messy fast. Two people update the same document. Someone makes a promise to the client that contradicts what another team member said. A task falls through the cracks because everyone assumed someone else was handling it.

You're the connective tissue. Keep a simple tracking habit:

"Switch to Acme Corp"

"Search memories for recent action items and who owns them"

When you spot overlap or gaps, flag it immediately. A quick Slack message saves hours of rework: "Hey Alex and Jamie - you're both working on the Acme social calendar. Want to sync before EOD so you're not duplicating effort?"

Running Small Moments of Recognition#

The CMO celebrates the big wins in team meetings. You celebrate the ones that happen between meetings:

• "Hey team, just wanted to flag that the Brightline blog post Alex wrote got picked up by their industry newsletter. Nice work."
• "Shoutout to Jamie for turning around the Acme emergency request in 2 hours yesterday. The client was thrilled."
• "Quiet win today: we hit 90 days with zero missed deadlines across all clients."

These don't need to be formal. A Slack message, a quick note in the team channel. The point is that people feel seen for the work they're doing, not just the work that makes it into the quarterly review.

Store wins so they're available for reviews and recognition later:

"Store a memory: Alex's Brightline blog post got picked up by MarketingWeek newsletter on March 15. Client mentioned it in their weekly call."

Flagging for the CMO#

When you do bring something to the CMO, be specific and include your read on the situation:

Weak: "I think Alex might be unhappy."

Strong: "Alex has been working late every night this week on the Acme campaign and missed the team lunch yesterday. I think the scope expanded beyond what was planned. It might be worth checking if we need to adjust the timeline or bring in support."

You're not just reporting a problem - you're giving the CMO enough context to act. Include what you've observed, how long it's been going on, and what you think the next step should be. That's the difference between being an early warning system and being an alarm with no context.

Related Guides#

• Morning Routine: Pull Your CMO's Daily Briefing - where team check-ins fit into your daily rhythm
• The Personal Touch List - tracking personal milestones that affect team morale
• Tracking Action Items Across All Clients - catching coordination gaps before they become problems