delveo’s practical guide to inclusive process design: qualitative benchmarks for 2025

Why Inclusive Process Design Matters in 2025

Inclusive process design has moved from a nice-to-have initiative to a core operational requirement for organizations that want to attract diverse talent and foster innovation. In 2025, teams often find that traditional process optimization—focused solely on efficiency—misses the human element, leading to burnout, turnover, and groupthink. A process that works well for one demographic may inadvertently exclude others, whether through language barriers, cultural assumptions, or accessibility gaps. This guide from delveo provides qualitative benchmarks to help you evaluate and improve inclusivity without relying on flawed or fabricated statistics. We focus on experience-based insights and practical steps you can take today. This overview reflects widely shared professional practices as of April 2026; verify critical details against current official guidance where applicable.

What Are Qualitative Benchmarks?

Qualitative benchmarks are descriptive criteria used to assess the quality of inclusivity in processes, rather than numerical targets. For example, instead of saying 'increase diverse hires by 20%,' a qualitative benchmark might state 'all recruitment materials are reviewed by a diverse panel for inclusive language.' These benchmarks rely on observation, feedback, and narrative evidence. Practitioners often find that qualitative measures reveal more about actual experience than metrics alone. They help teams understand not just whether something happened, but how it felt to participants—crucial for identifying subtle exclusion patterns.

Why 2025 Is a Turning Point

Several factors make 2025 a critical year for inclusive process design. First, global workforce expectations have shifted: employees increasingly expect transparency and fairness in how decisions are made. Second, regulatory pressures in some regions are moving from diversity quotas to process-related requirements. Third, advances in collaboration tools have made it easier to collect qualitative data from remote and hybrid teams. Many industry surveys suggest that organizations with inclusive processes report higher employee satisfaction and lower attrition. At the same time, there is growing skepticism about performative diversity efforts—making genuine qualitative benchmarks more valuable than ever.

Core Concepts: Defining Inclusive Process Design

Inclusive process design means intentionally shaping workflows, policies, and interactions so that all participants can contribute fully and feel valued. It goes beyond simply avoiding discrimination—it proactively seeks to remove barriers and amplify diverse perspectives. A process might be efficient but still exclude people if it assumes a certain level of technical proficiency, cultural background, or physical ability. For example, a decision-making process that relies on quick, vocal brainstorming in meetings can marginalize introverts or people who process information more slowly. Inclusive design considers these nuances and builds in multiple modes of participation. The 'why' behind this approach is straightforward: when people feel included, they are more likely to share unique ideas, challenge assumptions, and commit to team goals. This isn't just ethical—it's a competitive advantage. Practitioners often report that inclusive processes lead to better problem-solving and fewer costly oversights.

The Three Pillars of Inclusive Process Design

Effective inclusive process design rests on three pillars: representation, participation, and belonging. Representation ensures that diverse identities are present in decision-making bodies. Participation ensures that once present, those individuals have genuine influence—not just a seat at the table but a voice that is heard. Belonging is the subjective feeling of being accepted and valued, which qualitative benchmarks aim to capture. A process that achieves representation but fails on participation or belonging can still feel exclusionary. For instance, a team might have diverse members but if meetings are dominated by a few voices, others may feel their input is unwelcome. Qualitative benchmarks help assess all three pillars through tools like shadowing, anonymous feedback, and self-assessment.

Common Misconceptions

A common misconception is that inclusive process design requires lowering standards or slowing down work. In reality, many inclusive practices—like providing agendas in advance or using round-robin speaking turns—can improve clarity and efficiency for everyone. Another misconception is that it's enough to have a written policy. Policies matter, but they are ineffective without consistent application and follow-through. A third misconception is that inclusion is solely an HR concern. In fact, it affects every part of an organization: product design, customer service, internal communication, and strategic planning. By understanding these core concepts, teams can avoid superficial fixes and focus on meaningful change.

Setting Qualitative Benchmarks: A Step-by-Step Guide

Setting qualitative benchmarks requires a deliberate, iterative process. This step-by-step guide will help your team define what inclusive looks like in practice, collect relevant data, and use that data to drive improvement. The goal is not to create a one-time checklist but to build a continuous learning loop. Teams often find that the process of setting benchmarks itself increases awareness and commitment to inclusion. Start by gathering a diverse group of stakeholders—including front-line employees, people from underrepresented groups, and leaders—to co-create the benchmarks. This ensures buy-in and relevance.

Step 1: Identify Key Processes

Begin by listing the core processes you want to evaluate. Common candidates include recruitment, onboarding, performance reviews, meeting facilitation, feedback channels, and project decision-making. Prioritize processes that have the greatest impact on employee experience and where you suspect exclusion may occur. For example, many teams start with meeting practices because they happen frequently and visibly affect participation. In one composite scenario, a company noticed that certain team members rarely spoke in weekly stand-ups. By focusing on meeting inclusivity, they identified that the rapid-fire format discouraged thoughtful contributions. The benchmark they set was: 'In every meeting, at least two minutes of silent reflection is included before soliciting input.'

Step 2: Draft Descriptive Criteria

For each process, draft 3-5 descriptive statements that illustrate inclusive behavior. Use language that is observable and actionable. Instead of 'be respectful,' try 'all participants are addressed by their preferred name and pronouns.' Instead of 'encourage diverse ideas,' try 'the facilitator explicitly invites input from those who have not yet spoken.' Test these criteria with a small group to ensure they are clear and relevant. Revise based on feedback. This step often takes several rounds, but it's critical for creating benchmarks that people can actually use.

Step 3: Choose Data Collection Methods

Qualitative data can come from various sources: direct observation, anonymous surveys, structured interviews, and self-reflection journals. Observation is powerful but requires trained observers to avoid bias. Surveys can reach a larger audience but may miss nuance. Interviews provide depth but are time-intensive. A balanced approach often combines methods. For instance, you might observe three meetings a month, send a monthly pulse survey, and conduct quarterly focus groups. The key is to be consistent and transparent about how data will be used. One team I read about used a simple traffic-light system in surveys: green (feels included), yellow (neutral), red (excluded). Over time, patterns emerged that guided their improvements.

Step 4: Analyze and Act

Once data is collected, look for themes and patterns—not just isolated incidents. If multiple people report feeling interrupted, that's a systemic issue. Share findings with the team in a non-blameful way, focusing on process improvements rather than individual failings. Develop an action plan with specific owners and timelines. For example, if the benchmark about silent reflection isn't being met, the facilitator might need training or a visible reminder. After implementing changes, collect data again to see if the benchmark is now met. This cycle of assessment and adjustment is the heart of qualitative benchmarking.

Comparison of Three Benchmark Approaches

Different organizations adopt varied approaches to setting and using qualitative benchmarks. Below is a comparison of three common methods: the descriptive criteria approach, the experience sampling method (ESM), and the maturity model. Each has strengths and weaknesses, and the best choice depends on your organization's size, culture, and resources.

Each approach can be tailored. For instance, a team might use descriptive criteria for meetings and ESM for daily check-ins. The key is to choose methods that fit your context and to iterate as you learn. Many industry experts recommend starting with descriptive criteria because they are simplest to implement, then adding ESM or maturity models as the team gains sophistication.

When to Use Each Approach

Descriptive criteria work well when you need quick wins and clear expectations. ESM is ideal for capturing emotional responses that people might not share in surveys. The maturity model suits larger organizations that want to benchmark across teams and track long-term progress. Avoid using only one method exclusively—triangulating multiple sources gives a richer picture. Also, be aware that any approach can be gamed if people feel judged. Emphasize learning over evaluation to encourage honest data.

Real-World Scenario: Redesigning Meeting Practices

Meetings are a common pain point for inclusivity. In one anonymized composite scenario, a team of 15 people from different cultural backgrounds and time zones found that their weekly decision-making meetings were dominated by a few vocal members. Quiet team members often felt their contributions were ignored or dismissed. The team decided to apply qualitative benchmarks to redesign the process. They started with a short survey asking everyone to rate, on a scale of 1-5, how included they felt in meetings, and to describe one moment when they felt heard or unheard. The results showed a clear pattern: people who spoke less frequently rated inclusion lower.

Benchmarks Set

The team co-created three benchmarks: (1) before each meeting, an agenda is shared with at least one written update from each member; (2) during the meeting, the facilitator uses a round-robin format for key decisions, giving each person a chance to speak; (3) after the meeting, a brief anonymous poll asks 'Did you feel your perspective was considered?' with a target of 80% positive responses. These benchmarks are observable and linked to specific actions.

Outcome and Adjustments

After implementing these changes for two months, the team observed that participation became more balanced. The anonymous poll consistently showed 70-85% positive responses—an improvement from the baseline of 50%. However, some members felt the round-robin made meetings longer. The team adjusted by using round-robin only for the first three agenda items and then allowing open discussion. They also added a time limit per person. This flexibility demonstrates that benchmarks are not rigid rules but guides for continuous improvement. The team now reviews benchmarks quarterly and updates them based on feedback.

Leadership Modeling: Setting the Tone from the Top

Leaders play a critical role in inclusive process design. Their behavior sets the norms for the entire team. If a leader interrupts, dismisses ideas, or fails to seek input, no amount of process design will create inclusion. Conversely, when leaders model inclusive behaviors—like actively listening, crediting others, and admitting mistakes—they create psychological safety. Qualitative benchmarks for leadership can include: 'Leader asks for dissenting opinions in at least two meetings per week,' or 'Leader shares credit for team successes in public communications.' These benchmarks are not about policing leaders but about helping them develop self-awareness.

How to Coach Leaders

One effective approach is to have leaders participate in a 360-degree feedback process focused on inclusion. For example, a leader might receive anonymous feedback that they dominate discussions. The benchmark could be: 'In the next month, the leader will speak for less than 30% of the time in meetings, as measured by a timer.' The leader can then practice this and reflect with a coach. Over time, such practices become habitual. Another benchmark might be: 'Leader schedules regular one-on-ones with team members to ask about their experience of inclusion, and shares a summary of what they learned.' This demonstrates that inclusion is a priority, not a checkbox.

Common Pitfalls

A common pitfall is expecting leaders to change overnight without support. Behavioral change requires practice, feedback, and accountability. Another pitfall is focusing only on senior leaders and ignoring middle managers, who often have the most direct impact on daily experience. Inclusive process design must cascade through all levels. A third pitfall is mistaking performative actions—like making a public statement about diversity—for genuine behavior change. Qualitative benchmarks help guard against this by focusing on observable, repeated actions.

Recruitment and Onboarding: A Test of Inclusive Process

Recruitment and onboarding are high-stakes processes where exclusion can happen quickly and have lasting effects. A job description with jargon or unnecessary requirements can deter qualified candidates from underrepresented groups. An interview process that lacks structure can lead to bias. Onboarding that assumes familiarity with unwritten rules can leave new hires feeling isolated. Qualitative benchmarks for these processes can ensure they are welcoming and equitable. For recruitment, a benchmark might be: 'All job descriptions are reviewed by a diverse panel for inclusive language before posting.' For interviewing: 'Every candidate is asked the same core questions, and interviewers receive bias training annually.' For onboarding: 'New hires have a mentor from outside their team for the first three months.'

Scenario: Redesigning a Hiring Process

In another composite scenario, a tech company noticed that women and people of color were less likely to accept offers after the final interview stage. Through exit interviews and anonymous feedback, they discovered that the final panel interview felt adversarial and lacked warmth. The team set a benchmark: 'The final interview day must include an informal meet-and-greet with potential peers, and the interview panel receives feedback on their interpersonal style.' After implementing this, the offer acceptance rate among underrepresented groups increased. While exact numbers are proprietary, the qualitative feedback showed that candidates felt more welcomed and able to picture themselves in the role.

Onboarding as a Process

Onboarding is often rushed, but it's a critical time for setting expectations and building belonging. A benchmark could be: 'By the end of the first week, the new hire has a documented 30-60-90 day plan co-created with their manager.' Another: 'The new hire is introduced to at least three cross-functional team members in the first two weeks.' These simple actions show that the organization is invested in the person, not just their output. Regular check-ins during the first 90 days can capture qualitative data on how included the new hire feels, allowing adjustments in real time.

Feedback Culture: Building Trust Through Inclusive Practices

Feedback processes are often a source of anxiety and can be particularly challenging for people from cultures where direct criticism is uncommon. An inclusive feedback culture ensures that all employees receive constructive, developmental feedback regularly, and that their own feedback is heard and acted upon. Qualitative benchmarks can help create a system that is fair and transparent. For example: 'Every employee receives both positive and developmental feedback at least once per month, documented in a shared system.' Or: 'Feedback is collected anonymously from all team members before a performance review to provide a fuller picture.'

Designing a Feedback Process

One approach is to separate performance evaluation from coaching conversations. The evaluation is summative, while coaching is formative. A benchmark might be: 'Coaching conversations happen at least twice per month and focus on growth, not judgment.' Another benchmark: 'Managers are trained to ask open-ended questions like "What support do you need?" rather than only giving directives.' In practice, one team I read about implemented a 'feedback Friday' where anyone could give anonymous feedback about processes, which was then discussed openly in the next week's meeting. The qualitative benchmark was: 'At least one process change results from feedback each quarter.' This created a visible link between feedback and action, increasing trust.

Challenges and Solutions

A common challenge is that feedback can feel risky, especially in hierarchical organizations. To address this, leaders must model receiving feedback gracefully—thanking the giver even if they disagree. Another challenge is that feedback systems can become bureaucratic. Keep it simple: a shared document or a quick survey can suffice. The qualitative benchmark should focus on the quality and frequency of feedback, not just its existence. Avoid the pitfall of making feedback only about weaknesses; celebrate strengths equally.

Technology and Accessibility: Ensuring Digital Inclusion

In 2025, most processes involve digital tools, from project management software to video conferencing. If these tools are not accessible, they can exclude people with disabilities, those with limited internet bandwidth, or those who prefer different communication styles. Inclusive process design must consider technology accessibility as a fundamental requirement. Qualitative benchmarks can include: 'All team communication tools support screen readers and keyboard navigation,' and 'Meeting recordings are automatically captioned and transcribed.' These benchmarks ensure that no one is left out due to technical barriers.

Evaluating Tool Inclusivity

When selecting a new tool, involve a diverse group of users in the evaluation. Create a benchmark checklist: Is the tool compatible with assistive technologies? Does it offer multiple ways to interact (e.g., chat, voice, video)? Is the interface simple and intuitive? For example, a team might benchmark that 'all documents are shared in accessible formats (e.g., HTML or tagged PDF) at least 48 hours before a meeting.' This allows users who need screen readers or extra time to prepare. Another benchmark: 'During video calls, participants can use raised-hand reactions and chat to avoid speaking over each other.' These small adjustments can dramatically improve inclusivity.

Common Accessibility Gaps

Common gaps include lack of alt text on images, poor color contrast, and reliance on real-time collaboration without asynchronous options. Teams often overlook that not everyone can attend live meetings due to time zones or caregiving responsibilities. A qualitative benchmark could be: 'All major decisions are documented and shared asynchronously, and input is accepted for at least 24 hours after the meeting.' This ensures that voices are heard regardless of schedule. By treating accessibility as a process benchmark, organizations can systematically remove barriers rather than addressing them ad hoc.

Measuring Progress: How to Know If You’re Improving

Measuring progress on qualitative benchmarks requires a shift from 'did we hit the number?' to 'are we seeing the patterns we want?' This is inherently subjective, but there are ways to make it rigorous. One method is to conduct regular 'inclusion audits' where a small team observes processes and rates them against the benchmarks using a rubric (e.g., 1=not present, 5=fully present). Another is to track the frequency of inclusive behaviors reported in surveys. For example, the question 'In the past month, how often did you feel your ideas were valued?' answered on a 1-5 scale can be tracked over time. The goal is trend improvement, not perfection.

Creating a Dashboard

Organizations can create a simple dashboard that shows qualitative indicators alongside quantitative ones. For instance, include a section on 'Meeting Inclusion Score' based on survey responses, and a section on 'Recruitment Inclusivity' based on candidate feedback. The dashboard should be reviewed quarterly by the leadership team. It's important to avoid comparing teams in a punitive way; instead, use the data to share best practices. One team might excel at meeting inclusion while another excels at feedback. Cross-pollination helps everyone improve.

Adjusting Benchmarks Over Time

As the organization matures, benchmarks should evolve. What felt inclusive in year one might become baseline in year two. For example, a benchmark like 'agenda shared 24 hours in advance' might be upgraded to 'agenda co-created with team input.' Regular review cycles—say, every six months—ensure that benchmarks remain relevant and challenging. Also, be open to dropping benchmarks that have become universally met; celebrate the achievement and set new ones. This keeps the process dynamic and avoids stagnation.

Common Questions About Inclusive Process Design

Teams often have practical concerns when starting with qualitative benchmarks. Below are answers to some frequently asked questions, based on common experiences shared by practitioners.

How do we avoid bias in our benchmarks?

Bias can creep in when the people setting benchmarks are homogeneous. Involve a diverse group from the start. Use language that is specific and observable to reduce interpretation differences. Pilot test benchmarks with a small group and revise based on feedback. Also, consider that what seems inclusive to one group may not feel inclusive to another—hence the need for multiple perspectives.

What if our team is resistant to change?

Resistance often stems from fear of judgment or extra work. Frame benchmarks as tools for learning, not evaluation. Start small with one process, show quick wins, and share positive outcomes. Involve skeptics in the design process so they have ownership. Emotional safety is crucial; avoid blaming individuals for past exclusion. Focus on systems and processes, not people.