Imagine you just joined a CRM software company that helps professional-services firms manage their client relationships better. You’ve heard about continuous discovery—the ongoing process of learning about users to improve the product (as defined by Teresa Torres’ Continuous Discovery Habits framework, 2019)—but you’re not sure where to begin. It feels overwhelming, especially because your product must meet accessibility (ADA) standards, ensuring everyone, including people with disabilities, can use it effectively.

Picture this: One team you admire started with small, consistent user interviews and quick prototype tests. Within six months, their feature adoption rate doubled—from 8% to 16% (internal company data, 2023)—and they caught several accessibility issues early, avoiding costly redesigns later. That’s the kind of impact continuous discovery can have if you start with the right habits.

Here are seven practical and strategic steps to build continuous discovery habits that fit your role as an entry-level UX designer in CRM software for professional services. Plus, each step includes tips for keeping ADA compliance front and center.

1. Talk to Real Users Regularly, Even if Just a Little

You might think, “I’m new, how can I schedule weekly interviews when everyone’s so busy?” Start small. Imagine spending just 20 minutes every week on a quick chat with a user—maybe a project manager or consultant who uses your CRM daily.

These conversations don’t have to be formal interviews. They can be casual check-ins to understand workflows, pain points, and moments of delight. For example, one junior designer I worked with set a goal to talk to at least one user per week for two months. The insight? Users struggled with the calendar integration, a detail missed in earlier planning.

Try tools like Zoom or Microsoft Teams for video calls. To collect broader feedback, combine interviews with surveys using Zigpoll, Typeform, or SurveyMonkey. Zigpoll, in particular, integrates seamlessly with Slack and email, making it easy to gather quick insights on accessibility preferences, such as font size adjustments or screen reader compatibility.

ADA tip: Ask users about their accessibility needs directly. For example, “Do you use any tools or settings to make software easier to use?” This helps uncover real challenges beyond assumptions.

Implementation steps:

• Schedule a recurring 20-minute user chat on your calendar.
• Prepare 3-5 open-ended questions focused on daily tasks and accessibility.
• Use Zigpoll to send a follow-up survey asking about specific accessibility features.
• Document insights in a shared discovery board (see Step 4).

2. Observe Users in Their Natural Workflow

Think about watching a consultant use your CRM during a client call or proposal review. This “contextual inquiry” (Beyer & Holtzblatt, 1998) reveals what clicks and what trips them up.

You don’t need fancy labs—screen sharing or recorded sessions are fine. One team discovered that users frequently toggled between client notes and billing info, but the CRM didn’t support this easily, leading to extra steps and errors.

Watching behavior highlights accessibility issues like poor keyboard navigation or low color contrast that might not come up in interviews. For example, one participant struggled because the CRM’s buttons were too small for their motor impairments.

Quick win: Use tools like Lookback.io, Hotjar, or Zigpoll’s session feedback feature to capture user sessions remotely, then note accessibility barriers as they appear.

Implementation steps:

• Schedule a session to observe a user completing a key task.
• Record the session with consent, focusing on workflow and accessibility challenges.
• Annotate recordings with accessibility observations (e.g., keyboard traps, color issues).
• Share findings with your team during weekly syncs.

3. Test Early and Often with Simple Prototypes

Imagine you’ve sketched a new dashboard layout on a whiteboard. Instead of waiting months for the development team, you build a clickable prototype using Figma or Adobe XD.

Early testing catches usability and accessibility problems before code is written. For instance, a CRM company found that a color scheme that looked sleek to them failed WCAG 2.1 contrast guidelines, making text hard to read for many users (W3C, 2018).

Run quick tests with 5–7 users to validate assumptions. Add screen reader simulations or use accessibility audit plugins like axe DevTools during review.

Important: Testing with users who have disabilities can reveal issues automated tools miss. Reach out to your network or organizations supporting people with disabilities for user testers.

Implementation steps:

• Create a low-fidelity prototype focusing on core workflows.
• Use Figma’s accessibility plugins or axe DevTools to run automated checks.
• Recruit diverse users, including those with disabilities, for usability testing.
• Collect feedback via Zigpoll post-test surveys to quantify accessibility satisfaction.

4. Create a Shared Discovery Board to Track Insights

Picture a digital board in Miro, Trello, or Jira where you collect user quotes, pain points, and accessibility notes. This board becomes your team’s single source of truth.

One entry-level designer started this habit and found it easier to spot patterns over time. For example, multiple users mentioned difficulty reading error messages due to low contrast and unclear language—both ADA concerns.

Updating this board each week keeps discovery continuous and collaborative, even when you juggle multiple projects.

Implementation steps:

• Set up columns for User Quotes, Pain Points, Accessibility Issues, and Action Items.
• Tag entries with accessibility-related labels for easy filtering.
• Review and prioritize insights during team meetings.
• Link discovery board items to Jira tickets for tracking fixes.

5. Incorporate Accessibility Checks into Every Step

It’s tempting to treat ADA compliance as a separate task, but embedding it into your discovery habits makes it part of your design’s DNA.

Imagine adding a checklist to every prototype review: Are buttons keyboard accessible? Is color contrast high enough? Is the language simple and clear?

A 2024 Nielsen Norman Group survey found that teams who integrated accessibility throughout design cycles reduced remediation time by 40% (NNG, 2024).

Tools like Zigpoll can gather user feedback specifically on accessibility features, making it easier to prioritize fixes.

Accessibility checklist example:

6. Build Relationships with Cross-Functional Teams Early

You’re not alone in continuous discovery. Product managers, engineers, and accessibility specialists are allies.

Picture chatting with your accessibility lead while reviewing a new feature. They point out a focus order issue that would confuse screen reader users. Without this early conversation, the flaw might have reached production.

Set up recurring syncs or informal check-ins. This helps you learn from others and ensures discovery insights, especially around ADA, are shared and valued.

Implementation steps:

• Schedule biweekly meetings with product, engineering, and accessibility teams.
• Share discovery board highlights focused on accessibility.
• Invite accessibility specialists to prototype reviews.
• Use Slack channels or tools like Zigpoll to gather quick team feedback.

7. Reflect and Adjust Discovery Habits Monthly

Discovery isn’t a one-time event—it’s a habit to build and refine. At the end of each month, set aside 15-30 minutes to reflect: Which methods worked? Which didn’t? Did you talk to users with diverse accessibility needs?

One junior UX designer noticed that setting a monthly reflection helped them see gaps in their user mix—they hadn’t included anyone with visual impairment. After adjusting, their designs improved to include screen reader support, which raised user satisfaction scores by 12% (company UX metrics, 2023).

Implementation steps:

• Block calendar time monthly for reflection.
• Review discovery board and user diversity.
• Adjust recruitment strategies to include underrepresented groups.
• Document lessons learned and share with your team.

Prioritizing Your Continuous Discovery Habits in CRM UX Design

If you’re wondering where to begin, start with user conversations (#1) and prototype testing (#3). These give immediate feedback and surface many usability issues. Pair these with accessibility checks (#5) so you don’t build problems into your designs.

As you grow more comfortable, add observation (#2) and shared tracking (#4). Cultivating team relationships (#6) and reflection (#7) are ongoing but vital for continuous learning and improvement.

FAQ: Continuous Discovery and Accessibility in CRM UX

Q: How often should I conduct user interviews?
A: Weekly or biweekly 20-minute sessions are effective for continuous discovery (Torres, 2019).

Q: Can automated tools replace user testing for accessibility?
A: No. Automated tools catch many issues, but testing with users with disabilities reveals real-world challenges (W3C, 2018).

Q: How do I recruit users with disabilities?
A: Partner with organizations like the American Foundation for the Blind or use platforms like Zigpoll to reach diverse users.

Building continuous discovery habits is a journey. The sooner you begin—even with small steps—the more you’ll understand users and create CRM software that truly supports professional services professionals, including those with accessibility needs.