Skip to main content

Health & Wellness Initiatives

Make wellness benefits feel real by showing the people who use them. One program becomes ten reusable internal and recruiting assets.

Why this works

Wellness programs printed in benefits PDFs feel theoretical. The same program shown through one employee who used it during a hard quarter feels real. That's the difference between a candidate skimming the benefits page and a candidate emailing the recruiter back the same day.


Who you'll feature

  • An employee who used the benefit. Honest, specific, comfortable on camera.

  • A program lead. Names what's available and how to access it.

  • An optional partner, like a coach, therapist, or fitness lead.


How to capture it

  • Open MarketScale → Requests → New Request. Three prompts to the employee:

    1. What was going on for you when you reached for this benefit?

    2. How did you actually use it?

    3. What changed because of it?

  • Use AI Writer to draft the participant brief in a tone that respects the topic.

  • Run the recording in Remote recording for a comfortable, conversational setting.

  • Always offer the employee anonymous voice-only or B-roll options if they prefer.


Reuse it (the 1:10 framing)

One wellness story becomes:

  1. A 2-minute employee story.

  2. A 30-second LinkedIn cut from the program lead.

  3. A benefits-page hero on the careers site.

  4. An open-enrollment intro video.

  5. A new-hire onboarding clip on "benefits that actually work."

  6. A manager-toolkit asset.

  7. A people-ops blog post.

  8. A clip your benefits partner can repost.

  9. A pulse-survey discussion-starter.

  10. A pinned post on your Channel feed under Wellness.

Group wellness stories into a Collection in Ready to Share for recruiters and people-ops.


Common mistake

Filming a list of benefits read off a slide. The benefits aren't the story; the moment someone needed one is. Anchor every piece to a person and a real situation, and the program enrollment numbers will shift on their own.

Did this answer your question?