Guidelines For Effective Surveys

My nonprofit friends, why are we so afraid of messy data? I hear it all the time: ● "We can't ask that question—it might confuse people." ● "This survey works fine; it's what we've always used." ● "If we dig too deep, we might find something we don't want to see." Here is the problem: when we stick to the same safe questions and the same tidy reports, we stop growing. We stop learning. Data collection isn't supposed to be neat and tidy. It's supposed to reveal the mess. To spark discomfort. To challenge assumptions. Think about it: ● If your donor survey shows no gaps between who gives and who benefits, are you really asking the right questions? ● If your program evaluation scores are always glowing, could you be missing feedback from the people too uncomfortable to speak up? ● If your board dashboards never include community input, whose voices are you really prioritizing? Messy data—data that is incomplete, complicated, or contradictory—isn't purely bad data. It is your directional support for work to be done. It's where the real insights live. Here are three steps you can take to embrace this mess and use it to drive meaningful change: ● Audit your data collection: Go back to your surveys, focus group guides and intake forms. Which questions are missing? Are you asking things that make people uncomfortable in productive ways, or just sticking to what's easy to measure? ● Welcome contradictions: Dig deeper if your data doesn't have conflicting opinions or surprising results. Discomfort in your findings often signals areas where change is needed. Instead of dismissing it, ask: What is this teaching us? ● Ask for feedback on your data practices: Go beyond asking your team. Bring in the voices of your community—your beneficiaries, donors, and stakeholders. Show them the data you are collecting and ask: Does this reflect your reality? What are we missing? As a sector, we often talk about "driving impact." Let's not forget that real impact comes from asking hard questions with the entire community, listening to the answers we would rather not hear, and using that data to build the needed change, not just justify it. #nonprofits #nonprofitleadership #community

A few years ago, I tried to convince a CEO we should run an employee survey. He looked at me and said, “Why? So we can create a colorful PowerPoint about feelings and then do absolutely nothing with it?” Honestly… fair. He’d seen the movie before: -100+ questions -Good participation -Beautiful charts -Zero change -Collective employee eye-roll At the time, I was determined to prove a survey could be more than a corporate ritual we perform between budgeting season and the holiday party. Here’s what I learned: An employee survey isn’t about asking questions. It’s about deciding what you’re actually willing to hear. And what you’re willing to do about it. Our first draft survey was… ambitious. We asked everything. Engagement. Benefits. Leadership trust. Office snacks. Probably the emotional impact of the expense policy. It was thoughtful. It was thorough. It was also completely unfocused. The CEO asked me one question that changed everything: “What decision will this data help us make?” Silence. We weren’t clear on what we really wanted to learn. We were going through the motions because “good companies run surveys.” So we scrapped it and started over. Instead of starting with questions, we started with intent: -Where are we guessing instead of knowing? -What’s getting in the way of great work? -What are we actually prepared to fix? -What might surprise us? We cut the survey nearly in half. We removed vague questions like, “Do you feel valued?” (valued… by whom? For what?) We replaced them with sharper ones: -What’s one process that makes your job harder than it needs to be? -What does leadership think is working well - but isn’t? -If you could change one thing in the next 90 days, what would it be? The difference was immediate. Participation went up. Comments got specific. Patterns were clear. Within 60 days, we eliminated a clunky approval process, clarified decision rights, and fixed a communication gap that had been frustrating half the company. Nothing revolutionary. Just listening - and acting. And that’s what changed the CEO’s mind. Employees don’t expect perfection. They expect evidence that their input matters. What I took away from that experience: -Don’t ask a question you’re not prepared to act on. -Fewer, sharper questions beat longer, safer surveys. -Specific beats sentimental. -The real work starts after the results come in. -Over-surveying is annoying. Under-listening is fatal. Now, whenever someone says, “We should run a survey,” my first question is: “To learn what?” Because the power isn’t in the form. It’s in the intention behind it. Sometimes tweaking just a few questions doesn’t just change the data. It changes the conversation.

User experience surveys are often underestimated. Too many teams reduce them to a checkbox exercise - a few questions thrown in post-launch, a quick look at average scores, and then back to development. But that approach leaves immense value on the table. A UX survey is not just a feedback form; it’s a structured method for learning what users think, feel, and need at scale- a design artifact in its own right. Designing an effective UX survey starts with a deeper commitment to methodology. Every question must serve a specific purpose aligned with research and product objectives. This means writing questions with cognitive clarity and neutrality, minimizing effort while maximizing insight. Whether you’re measuring satisfaction, engagement, feature prioritization, or behavioral intent, the wording, order, and format of your questions matter. Even small design choices, like using semantic differential scales instead of Likert items, can significantly reduce bias and enhance the authenticity of user responses. When we ask users, "How satisfied are you with this feature?" we might assume we're getting a clear answer. But subtle framing, mode of delivery, and even time of day can skew responses. Research shows that midweek deployment, especially on Wednesdays and Thursdays, significantly boosts both response rate and data quality. In-app micro-surveys work best for contextual feedback after specific actions, while email campaigns are better for longer, reflective questions-if properly timed and personalized. Sampling and segmentation are not just statistical details-they’re strategy. Voluntary surveys often over-represent highly engaged users, so proactively reaching less vocal segments is crucial. Carefully designed incentive structures (that don't distort motivation) and multi-modal distribution (like combining in-product, email, and social channels) offer more balanced and complete data. Survey analysis should also go beyond averages. Tracking distributions over time, comparing segments, and integrating open-ended insights lets you uncover both patterns and outliers that drive deeper understanding. One-off surveys are helpful, but longitudinal tracking and transactional pulse surveys provide trend data that allows teams to act on real user sentiment changes over time. The richest insights emerge when we synthesize qualitative and quantitative data. An open comment field that surfaces friction points, layered with behavioral analytics and sentiment analysis, can highlight not just what users feel, but why. Done well, UX surveys are not a support function - they are core to user-centered design. They can help prioritize features, flag usability breakdowns, and measure engagement in a way that's scalable and repeatable. But this only works when we elevate surveys from a technical task to a strategic discipline.

I've said it before, but it's worth repeating. "Survey fatigue" isn't what you think it is. It's not about too many surveys, it's about too little action. At YMCA WorkWell, I often hear: "Our employees have survey fatigue, I don't think this is the right time to collect their feedback". But here's the thing. Employees aren't tired of providing feedback and and they aren't tired of speaking up to try and make their work better. They're tired of nothing changing when they do. A survey isn't the problem, it's feeling like your voice isn't going to be heard. That's what makes another survey feel pointless and exhausting. So if you want to do a survey right, start by asking: ✅ Have we closed the loop on the last one? ✅ Did we communicate what we learned and how we would respond? ✅ Have we made tangible changes based on the feedback? ✅ Have we communicated those changes back and clearly tied them back to the feedback provided? ✅ Do we have a process in place to communicate back what we hear this time quickly and clearly? ✅ Are we really committed to acting decisively on what we hear? If you're viewing a survey as just a round of data collection or something to check off on a box, you're going to fall short. Instead, view it as an opportunity to signal to everyone in your organization that leadership is listening, learning and responding. Because if employees stop responding and start complaining about surveys, it's not because they are tired of a 5-minute survey twice a year, it's because they don't think their voice will matter. So if you really want to address survey fatigue, removing employees' opportunities to speak up is not the answer. It's acting on their feedback when they do. #SurveyFatigue #EmployeeExperience #EmployeeSurveys

If there is no clear outcome, it was a wasted project. This might feel harsh, but research for the sake of research is a luxury most companies can’t afford. We’ve all been there—months spent on a study that: - Gets a polite nod in a meeting - Has no impact on decisions - Collects dust in a Google Drive folder Your research isn’t valuable unless it drives real change. Here’s how to ensure every project delivers measurable impact (including generative research): 1. Anchor every project to a business goal Start with questions like: - What decision does this research need to inform? - What’s the business metric we’re trying to improve? - What’s the cost of NOT doing this research? For example: If product adoption is stagnant, your goal might be: “Identify usability blockers to reduce onboarding drop-off by 20%” For generative research, think beyond immediate impact: - Uncover unmet customer needs to shape the next 12-month product strategy - Identify emerging behaviors in [market] to drive innovation in [feature area] If you can’t connect your project to a clear business goal, rethink it. 2. Deliver outcomes, not just insights Stakeholders don’t need a data dump—they need decisions. Here’s how to frame your findings: - Instead of: “Users prefer Option A over B” - Say: “Option A is projected to improve conversion by X%, generating an additional $Y in revenue” For generative research, focus on potential and prioritization: - Our interviews uncovered three unmet needs. If addressed, these could expand our market share by targeting [new audience] or boosting retention - Prototyping [concept] revealed an opportunity to explore [new product direction] Concrete recommendations tied to impact turn research from “nice-to-have” to must-have. 3. Follow up to measure success Your work doesn’t end with the presentation. Follow through: - Did your insights lead to changes in the product? - Did those changes improve the target metric? For generative research, measure your influence on strategy: - Did your findings make it into the product roadmap? - Are stakeholders referencing your insights in key decisions? Example: If your generative study revealed unmet needs among power users, track whether the roadmap now includes solutions for that group. 4. Become a champion for action Research that isn’t acted upon is research wasted. To make sure your work drives decisions: - Hold insight-to-action workshops with stakeholders to co-create next steps - Check in regularly to ensure recommendations are being implemented - Advocate for alignment on priorities when teams get distracted Research isn’t about ticking boxes, but creating outcomes If your projects aren’t tied to measurable results, whether tactical or generative, they’re not reaching their full potential What’s one way you’ve ensured your research has a direct impact? Join 10,000+ others in reading about UXR strategy and impact: https://lnkd.in/egx5SaUJ Image via Midjourney

Annual surveys are dead and ABN AMRO realized it the hard way —by watching engagement data arrive months too late, after the damage was already done. ABN AMRO replaced their once-a-year surveys with a 𝐜𝐨𝐧𝐭𝐢𝐧𝐮𝐨𝐮𝐬 𝐥𝐢𝐬𝐭𝐞𝐧𝐢𝐧𝐠 𝐦𝐨𝐝𝐞𝐥.  Every month, they ask a representative group of employees one core question: Would you recommend this place to work? Plus—open-ended feedback on what’s working and what’s not. Over 𝟏,𝟎𝟎𝟎 𝐜𝐨𝐦𝐦𝐞𝐧𝐭𝐬 𝐩𝐞𝐫 𝐦𝐨𝐧𝐭𝐡 are analyzed using NLP models like TF-IDF, Word2Vec, and SVM. That means 150+ themes clustered and tracked—𝐢𝐧 𝐫𝐞𝐚𝐥 𝐭𝐢𝐦𝐞. And the impact: 1. Spot issues before they spiral 2. Build trust through transparency 3. Align HR insights with quarterly leadership decisions They didn’t just collect data. They turned feedback into fuel—for culture, strategy, and trust. 𝐓𝐡𝐢𝐬 𝐢𝐬 𝐰𝐡𝐚𝐭 𝐩𝐞𝐨𝐩𝐥𝐞 𝐚𝐧𝐚𝐥𝐲𝐭𝐢𝐜𝐬 𝐬𝐡𝐨𝐮𝐥𝐝 𝐥𝐨𝐨𝐤 𝐥𝐢𝐤𝐞. Fast, actionable, employee-led. Not a dashboard no one opens, 10 months too late. When employees feel heard and see change—HR becomes a driver of transformation, not just measurement. #PeopleAnalytics #EmployeeEngagement #HRTech #Leadership #ContinuousListening #FutureOfWork

Stop calling it Survey Fatigue. It’s probably “Nothing Changes Anyway” Fatigue. If you want people to keep sharing what they think and feel, you have to earn it. Show them you’re listening and that it matters. Here’s how to do it right… 1. “Where are the Receipts???” Before launching a new survey, show what you did with the last one. Remind employees what they shared and how it led to real change. Even small wins matter here. This is where trust begins. 2. Respect Their Time Run the survey with clear communication and thoughtful outreach. Give people a reason to care while acknowledging the time it takes. Celebrate your early responders and follow up with the rest respectfully, even those last-minute stragglers… 3. Don’t Sit on the Results Your people already know what’s working and what isn’t because they told you. Give a high-level overview of what came up. They don’t need every detail, but enough to know you’re paying attention. 4. Time for Action Pick a few key areas and plan what you’ll do… then actually do it. Planning is part of action, but it can’t be where it stops. Keep people updated on what’s happening and what’s next. Show progress, even if it’s just the first steps. “Nothing Changes Anyway” Fatigue is REAL If your survey process ends with “thanks for your feedback,” you’re doing it wrong. A good survey cycle proves you’re listening and acting. That’s how you earn trust, every time.

As Summer PD kicks off in many Northeast charters, I’ve been thinking about what it really takes to build a culture of feedback and learning—not just deliver professional development. One thing I learned based on my years as a principal and then supporting principals and leaders in designing professional development is this: A culture of feedback doesn’t start with a protocol. It starts with a habit. One of the most powerful: short, focused reflection surveys. And this isn’t just for summer onboarding. It works any time you're introducing a new initiative, tool, or workflow. But if the goal is learning—not just collecting data—how you use those surveys matters. Whether you're onboarding teachers or leading a change effort on your team, here are three lessons I’ve learned: ✅ Ask better questions. You get the data you ask for. Make sure you ask about both content and format. For content: • What’s one practice you’re excited to try? • What’s still unclear? • Where will you need more support? For format: a quick Keep–Start–Stop works wonders. ✅ Review the feedback as a team. Don’t just collect feedback—process it. Spot patterns, add context from your own observations, and adjust your plan. That might mean reshuffling sessions, re-grouping folks, or offering targeted support. ✅ Close the loop. If you want people to be honest, show them that their feedback matters. Share what you heard and how you’re responding—even if the answer is, “Not yet, and here’s why.” For individual concerns, follow up 1:1. This approach doesn’t just improve your rollout. It models the kind of learning culture we want in every classroom and team. And while I’ve seen this most in schools, these lessons apply anywhere—nonprofits, startups, corporate teams. If you’re leading any kind of team learning experience, these small moves build trust, responsiveness, and real feedback loops. You’ve heard me say it before: clarity is a process, and it’s bidirectional. This is one simple, powerful way to get there. What are your favorite moves or 1% solutions for building a culture of learning?

Your survey strategy isn’t broken. 𝗬𝗼𝘂𝗿 𝘀𝘂𝗿𝘃𝗲𝘆 𝗰𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻 𝗶𝘀. Surveys are flying in from every direction: → CS flags churn risk → Product wants roadmap input → Marketing needs messaging feedback → Community checks in after events Each survey alone? Useful - maybe. 𝗔𝗹𝗹 𝘁𝗼𝗴𝗲𝘁𝗵𝗲𝗿? 𝗖𝗵𝗮𝗼𝘀. No shared thread. No action plan. No response strategy. Here’s the truth: Surveys aren’t about ownership. 𝗧𝗵𝗲𝘆’𝗿𝗲 𝗮𝗯𝗼𝘂𝘁 𝗼𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻. When teams build surveys together, you create signals that are: ✓ Mapped to journey stages ✓ Routed to the right teams ✓ Activated in days—not quarters Most companies miss the highest-impact signals: • Who’s ready to be an advocate, but hasn’t been asked • Where content gaps are slowing key personas • Where “ease of doing business” is breaking down • Which stakeholders are unclear on onboarding value • Who wants to engage, but hasn’t been activated Now imagine this: → CS: Flags onboarding confidence drop → 1:1 support triggered → Product: Tags repeated friction → enablement updated → Marketing: Spots high engagement → story/promo activated → Community: Sees dormant power users → invites them back in 🧠 Insight → Alignment → Activation That’s the real customer lifecycle loop. You don’t need another tool. You need a shared survey strategy. This is the model I’ve used with CX, Product, Marketing, and Support teams. It works. It scales. Want a full playbook to better customer surveys? Drop “𝘀𝘂𝗿𝘃𝗲𝘆” below. 

There are some useful examples for effective post-survey actions in this article about Aflac. Yet there are some tweaks to their approach that would turn action planning into cultural transformation. 1. Don’t just create survey action teams, create peer-nominated action teams. This is a better way to involve employees and to identify emergent leaders. 2. Don’t just use survey scores as goals, use related business metrics that leaders always prioritize. Survey goals tend to take a backseat to “real” numbers, so find that number as a leading indicator to employee perceptions. 3. Don’t just use the same questions for a pulse survey, add questions to ask about progress at the current stage of action. Obviously the target outcome won’t happen overnight, but is it the focus of meetings, are there team goals that were created, is progress discussed weekly, etc.? Details matter. I’ve been creating survey-driven change for over 20 years. If you would like to learn more tweaks to improve your organization’s culture and performance, contact me. How Aflac uses data to engage and retain employees