X4 | Badge of the Month | March 2026

Best Practice Tip - I still stand behind taking as many surveys as you can to get a feel for what works and what doesn’t as a respondent.  It’s helped me a lot when working to build my own or for other departments.

X4 Tip - Pace yourself, there’s a lot going on so you might not be able to get to everything.  Wear comfortable shoes😁

We refer to Qualtrics' employee experience trend report every year.

The method of using or designing questionnaires to hypothesize and separate groups on interesting insights written by experts is classic, but it is always very helpful in checking the immersion of the ever-changing organization and its members.

Completely agree that it’s helpful to use a product from the pov of a customer/respondent. I do it as well and always discover something new!

We’re glad you find the trend report helpful!

Best Practice Tip: as a customer experience practitioner, you will need to create interest and support for the value of developing customer insight for several reasons including lack of familiarity with CX, concerns about access to customers and contacts, and hard-to-define ROI. This is a long process but can be done. Key elements can include:

• Avoiding technical or statistical terms and instead focusing on terms that your internal customers will understand. (For example, say “typical” instead of “mean” or “median” to describe scores.
• Trying to make insights as actionable as possible; design questions based on what value they will add to the product owner, rather than an academic or other interest.
• Communication -- a lot of it. Be prepared to discuss why CX is valuable and why it’s safe to track and ask customers about. “This will help you do your job better and be a better product owner or manager -- you will not lose your job, funding, etc. because of it.”

Absolutely! As a respondent and as a custom survey solutions builder. I complete surveys coming from several panels and platforms. I even probably have a (very small) impact on the average LOI, considering the time I spend inspecting the underlaying html, css and js code of the surveys I fill out!

​@vgayraud Agree!  I’m looking at question types, survey design, length, etc.  I just took a survey yesterday from my son’s book order club because I know they specifically use Qualtrics.

Best Practice Tip: Always check the XM Community when you’re having some issues. I cant remember how many times i have found solutions to my problems on the community. I find this communty such a usefull place to find help when im struggling on some configurations. Please use the community to learn and share what you know! 

​@Juan Zapata Yesss!  That is a good one!

I may be slightly biased 😏 but 100% agree with this!

Share What You're Experimenting With

We have a pretty strong focus on compliance and legal requirements when it comes to collecting feedback; but at the same time, Qualtrics users here have a lot of freedom to design their surveys.

To keep things in check without being too restrictive, I’ve been playing around with improving our existing “sensitive question” check. Until now, it was based purely on keywords (e.g. age, gender, political affiliation). I’ve replaced that with an AI-based approach.

Now, whenever a survey is published:

• All questions are pulled via Qualtrics API
• Sent to the AI with a detailed prompt
• The response is an email‑ready summary that highlights:
  • Potentially sensitive questions with highlighted topics/keywords
  • Why they are considered sensitive
  • A confidence score for each record
• If there is anything to report, the summary is mailed to the respective people

It’s a small change, but early testing already shows a noticeable drop in false positives. It works across any survey language, and covers far more edge cases than a keyword-based check ever could. I’m quite happy with it :)

​@Romanoman This is a really interesting approach to survey design and promotes self service in a way that must ease the workload for your compliance team. What kind of scripting to you use to make this workflow… work?

Nothing too fancy 🙂 It’s mostly lightweight automation around Qualtrics rather than in‑survey scripting. We use workflows to trigger the process, pull the relevant survey questions via APIs, run them through an AI prompt, and then format the result into an email‑ready summary.
So it’s more orchestration and glue code than anything deeply custom. Happy to share more details offline if you’re curious.

Sure-that would be much appreciated! How would you like to connect?

I agree.  Very helpful information and tips especially when new to the platform

1. I would love to hear recommendations on basecamp courses for Dashboards, Text IQ Analytics and anything more that would be helpful now that we have 3 live surveys and data responses.
    
2. Tip: Sitting with your leaders and front line teams to help them set up and filter their own personal dashboards as been a real win in getting ‘buy in’ on the new survey platform. After introduction training with all teams - being available has been most helpful. It has also allowed us Admins to compare the similiar FAQ’s that we are getting at the start of the roll out which helps all in the long run.

Excited for X4!

Hi ​@NewHomeCXManager , my name is Dana and I am a Learning Designer on the Basecamp team! There are a few workshops that may be great for you to check out. The “Workshop: Turn open-text feedback into actionable insights” is a TextiQ focused workshop.

The other CX workshops that may be interesting to you are the Mastering workflows and automated ticketing and  Mastering digital feedback from web to app. You can read more about them on the X4 Sessions page and choose which time is best for you - each session is repeated. 

A fellow Dana - how cool is that!  Thank you for your quick response. I will for sure check out these sessions.

Experimenting with Dashboard Field Mapping

I’ve been testing a way to make Qualtrics CX Dashboard auditing much easier. Usually, when you have a dashboard with lots of sources, checking each field manually is slow and tedious.

What I’m trying: I use the browser’s developer console to capture the dashboard’s metadata JSON as it loads. This lets me see all field mappings in one place without clicking through each source.

Benefits I’ve noticed so far:

• Saves hours of manual work

• Quickly shows if any field is mapped incorrectly

• Lets me create a full Data Dictionary to share with stakeholders

I also wrote a simple guide on this here: Extract Qualtrics Dashboard Mappings

Curious to hear how others are handling field mapping: still using spreadsheets, or have you found a faster way?