Toolkit: Inclusive Engineering Toolkit
Author(s): Jenny McLaughlin, MA APMQ
Resource type: Knowledge article: Inclusion in engineering contexts (e.g. how inclusion shapes engineering practice, design decisions, teamwork, and outcomes in real engineering contexts)
Topic: Explore the relationship between inclusion, human-centred design, safety, and systems thinking in engineering practice. Drawing on examples including the Heathrow Inclusive Design programme, Inclusive Design Overlay, Accessible and Inclusive Airport standards, and the Equitable Safety Initiative to demonstrate how inclusive approaches can influence engineering decisions and outcomes.
Title: Inclusion as a Core Engineering Competency: Improving Safety, Systems and Engineering Outcomes.
Relevant disciplines: Any.
Keywords: Inclusive Engineering; Systems thinking; Risk; Inclusive or Responsible design; Equity, Diversity and Inclusion; Accessibility; Engineering practice; Reflective practice; Professional conduct; Teaching and learning; Knowledge or Guidance
Licensing: This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Downloads: A PDF of this resource will be available soon.
QAA Inclusive Higher Education Framework mapping: Toolkit resources are designed to be applicable across engineering disciplines, but educators may find it useful to understand their alignment with the QAA Inclusive Higher Education Framework. The framework sets out five areas of activity that support inclusive practice across higher education, covering curriculum design, teaching and learning, assessment, learner support, and institutional approaches to inclusion.
This resource aligns most closely with the following QAA Inclusive Higher Education Framework area of activity: Curriculum Design and Delivery and Community and Belonging.
Within the Inclusive Engineering Toolkit, these areas provide a reference point for understanding how resources support inclusive engineering education and practice, rather than defining a rigid taxonomy or classification system.
AHEP mapping: This resource addresses several of the themes from the UK’s Accreditation of Higher Education Programmes fourth edition (AHEP4): Equality, Diversity and Inclusion. In addition, Design, Integrated or systems approach, Ethics and Risk.
Education Level: Beginner.
Upon successful engagement with this resource, learners will be able to:
- Explain why inclusion is a core engineering competency rather than an additional consideration, and describe its relationship to safety, systems thinking and engineering outcomes.
- Recognise how engineering assumptions can unintentionally create barriers, exclusion and safety risks for different people.
- Apply principles of inclusive engineering and human-centred design to identify opportunities for safer, more accessible and more equitable engineering solutions.
- Analyse engineering challenges using a systems-thinking approach, considering interactions between people, processes, environments, technologies and organisational systems.
- Evaluate how different individuals may experience safety differently and use Equitable Safety principles to identify hidden risks and unintended consequences.
- Use reflective questioning to challenge assumptions about “typical” or “average” users, workers, operators and maintainers.
- Demonstrate how inclusion contributes to improved safety, usability, resilience, innovation and professional practice across the engineering lifecycle.
- Recommend practical actions to embed inclusive thinking into engineering decision-making, risk assessment, design development, operation and continuous improvement activities
Teachers have the opportunity to:
- Facilitate discussion on inclusive engineering, Equitable Safety and systems thinking;
- Support learners to identify assumptions and hidden risks within engineering decisions;
- Apply the PEARLS framework to realistic case studies.
- Explore how safety, accessibility, dignity and agency are experienced differently by different people;
- Develop practical, evidence-informed engineering responses that lead to more inclusive and equitable outcomes.
Central argument
Inclusion is not an add-on to engineering; it is an essential part of good engineering practice. By applying systems thinking and understanding the full diversity of human needs, engineers can identify risks, uncover opportunities and design solutions that work for more people. The result is safer, more resilient and more successful outcomes. Inclusion should therefore be viewed as a core engineering competency, not simply an EDI consideration.
Introduction
Engineering has always been about solving complex problems. Whether designing infrastructure, transport systems, digital technologies, products or services, engineers make decisions that shape how people experience the world around them. Yet engineering practice has often relied on assumptions about a hypothetical ‘average’ user. The challenge is that no such person exists.
People experience products, environments and systems differently. Disability, age, neurodiversity, health conditions, language, culture, socioeconomic circumstances, caring responsibilities, confidence and previous lived experiences all influence how individuals interact with engineered solutions. When these differences are not considered, barriers emerge. Sometimes those barriers create inconvenience. Sometimes they create exclusion. In many cases, they create safety risks.
This is where inclusion becomes an engineering issue, not a separate social aspiration. Inclusion asks engineers to move from awareness to action: to notice when a system has not been designed for the full diversity of people who will use, build, maintain or be affected by it, and to respond before harm, exclusion or workaround becomes normalised.
Inclusion should therefore be recognised as a core engineering competency: a practical route to better decision-making, safer systems, more ethical practice and stronger outcomes for society. It is part of how engineers understand context, interrogate assumptions and design with responsibility.
Why inclusion is an engineering issue
Inclusion is often discussed in relation to accessibility, representation or equality. Whilst these are essential considerations, the implications for engineering practice are frequently overlooked. Every engineering decision is based on assumptions: who will use a system, how they will behave, what capabilities they have, what risks they may encounter and what constitutes acceptable performance.
When those assumptions are narrow, engineering solutions can unintentionally exclude people or introduce risks that remain hidden until late in delivery or operation. A standard face mask, a colour coded indicator, a risk assessment, a site access route or an evacuation procedure may appear neutral, but each one carries assumptions about bodies, cognition, confidence, communication, culture and context.
The human cost of those assumptions is often felt first at the edges. A person may find themselves adapting silently to a design that has not considered them. They may work harder, move more cautiously, rely on unofficial support or decide not to speak up because the system around them signals that the issue sits with them rather than with the design. Those experiences are not marginal. They are evidence that the engineering problem has not been fully understood.
Inclusive engineering is therefore not about designing for a ‘minority’ group. It is about recognising human diversity as a design parameter. It asks engineers to move from designing for an assumed norm to designing with awareness of variability, context, interdependence and lived experience. This is not separate from technical excellence. It is part of it.
Many innovations now considered mainstream originated from efforts to address exclusion or access barriers. Captions, voice recognition, predictive text, touch screens and video calling show how designing for difference can improve usability and participation for many people, including those with temporary or situational needs. Inclusion can therefore be a source of innovation as well as a route to equity.
Inclusion, safety and human-centred design
One of the strongest reasons for embedding inclusion into engineering practice is the relationship between inclusion and safety. Traditional safety approaches rightly focus on hazards, controls, compliance and risk reduction. However, if those approaches assume a standard user, worker or maintainer, they may overlook the fact that safety is experienced differently by different people.
The principle of equitable safety* is grounded in a simple but powerful proposition: safety is experienced uniquely by everyone. This shifts the question from ‘Is this safe?’ to ‘For whom is this safe, in what context, and under what conditions?’ That reframing matters. A maintenance access route may appear adequate for one worker while creating significant barriers for another. An evacuation process may assume sensory, cognitive or physical capabilities that not everyone possesses. A site welfare arrangement may meet minimum requirements while still failing to provide dignity, confidence or psychological safety for all.
*The Equitable Safety Initiative is a group of organisations driving change within standards, policy and practice, recognising that safety is experienced differently by everyone. The initiative is referenced in the Construction Leadership Council’s Equity, Diversity, Inclusion and Culture Change workstream objectives (Construction Leadership Council, n.d.).
A personal example illustrates the point. During a health and safety visit, walking across rebar on a construction site, I knew I was not safe. Yet even as the client and project manager, I did not feel safe enough to speak up in that moment. That experience matters because it exposes a wider systems question: if someone with formal authority can hesitate, what happens for a subcontractor, a new apprentice, a disabled worker or anyone who already feels they have less power in the system?
This is why equitable safety1i must include physical and psychological safety. A person cannot raise a safety concern if the culture, language, process or hierarchy around them makes speaking up feel unsafe. Engineers must therefore consider not only whether a control exists, but whether people can understand it, access it, trust it and challenge it when it does not work for them.
Human-centred design (ISO, 2019) helps engineering teams recognise these differences by considering the full range of people who interact with a system across its lifecycle: those who design, build, operate, maintain, use, visit, regulate, clean, respond to emergencies and live alongside it. By anticipating difference, engineers can identify risks that remain hidden when decisions are made around the perceived majority.
This does not mean adding complexity for its own sake. It means recognising the complexity that already exists and responding to it with empathy, evidence and professional judgement. If safety is non-negotiable, then safety should be equitable.
Why systems thinking matters
Many attempts to improve inclusion focus on individual adjustments or isolated interventions. These can be important, but they rarely address the wider systems that shape people’s experiences. Systems thinking offers a more useful perspective because it considers the relationships between people, processes, environments, behaviours, technologies, governance and culture (Meadows, 2008).
In engineering, a design decision rarely affects only one outcome. A change to layout can influence movement, wayfinding, staffing, emergency response, maintenance access, perceived safety, passenger confidence and operational resilience. A procurement decision can influence who is consulted, whose knowledge is valued and which risks are prioritised. A standard or process can either enable inclusive decisions early or push them into late-stage remediation.
The difficulty is that systems often give us comfort. They provide process, standards, sign-off routes and familiar evidence. These are necessary, but they can also create a false sense that someone else has already checked the assumptions. Inclusive practice asks engineers to stay curious within those systems: to ask what the evidence is based on, whose experience has informed it and what bias may sit inside the data, standard or precedent being used.
At Heathrow, inclusive design work has used approaches such as the Accessible and Inclusive Airport Standards (Heathrow, 2025), the Inclusive Design Overlay (RIBA, 2023), and the Wheel of Considerations (Heathrow, 2026) to encourage project teams to ask wider questions. These approaches prompt consideration of people, environments, activities, risks, legacy and system interactions. The intention is not to make every engineer an inclusive design specialist. It is to equip engineers to ask better questions, recognise assumptions and identify when additional expertise or lived experience is needed.
The Wheel of Considerations is particularly useful because it makes inclusion discussable and trackable across a project lifecycle. By considering people who use a space and people who do not, the environments they move through, the activities they need or want to undertake, the risks created by low agency, the legacy of previous projects and the wider systems connected to the design, teams can make inclusion part of everyday engineering judgement rather than a late-stage review.
In this sense, inclusion is a practical application of systems thinking. It helps engineers see how decisions interact across an asset lifecycle and how unequal outcomes can be designed in or designed out.
Inclusion as a professional competency
Engineering education has traditionally emphasised technical competence, analytical capability and problem-solving. These remain essential. However, engineering is fundamentally a social activity, shaped by the needs, behaviours and experiences of the people it serves. The complex challenges facing society increasingly require engineers to combine technical expertise with human-centred judgement, ethical reasoning and systems awareness in order to create solutions that are both technically effective and socially successful.
Future engineers will need to design for diverse populations, anticipate unintended consequences, balance competing stakeholder needs, manage complex risks and demonstrate responsibility for the social outcomes of their work. These capabilities cannot be developed through technical knowledge alone. They require students to understand exclusion, engage with different perspectives, challenge assumptions and evaluate the implications of engineering decisions for people who may experience systems differently from themselves.
This is also a matter of professional responsibility. Safety duties require engineers and project teams to consider foreseeable risks to people affected by construction, operation and use. Inclusive engineering strengthens that responsibility by widening what teams are able to foresee. It challenges the idea that risk can be fully understood if the people most likely to experience barriers are absent from the conversation.
Inclusion should therefore be treated as a core professional competency, alongside safety, sustainability and ethics. It is not an optional addition at the end of a design process. It is a discipline of thinking that should influence problem definition, data collection, user research, design development, risk assessment, testing, commissioning, operation and post-occupancy learning.
Implications for engineering education
If inclusion is a core engineering competency, it cannot be confined to a standalone lecture or optional module. Engineering educators can embed inclusion throughout curricula by connecting it to the activities students already undertake: defining problems, setting requirements, analysing risk, developing concepts, testing prototypes, evaluating trade-offs and reflecting on outcomes.
Students should be asked not only whether a solution works technically, but who it works for, who it may disadvantage, what assumptions were made and what evidence was used to understand diverse needs. They should encounter case studies where exclusion has created harm or poor performance, as well as examples where inclusive approaches have improved safety, usability, resilience or innovation.
The Equitable Safety framing offers a useful classroom shift. Instead of asking students to design for a generic user, educators can ask them to design for the edges and then examine how that improves the centre. What risk becomes visible when we consider a neurodivergent maintainer, a short-statured worker, a person with colour vision deficiency, someone managing fatigue, or a passenger under stress? What changes when students consider confidence, dignity and agency as design outcomes, not just technical performance?
This does not require all educators to become inclusion specialists. It requires curricula to make inclusive thinking visible, assessable and connected to engineering judgement. It also requires educators to create learning environments where students can ask difficult questions, recognise what they do not know and learn from people with different lived experiences.
Reflective questions for educators and students
The following questions can support classroom discussion, design reviews, project-based learning and assessment:
Understanding people
- Who are we designing for?
- Who might be excluded or required to adapt silently?
- Whose perspectives are represented in our decision-making, and whose are missing?
Understanding assumptions
- What assumptions are we making about users, workers, operators or maintainers?
- What does “normal” or “typical” mean in this context?
- Could those assumptions create barriers or risks including both using context of temporary or situational requirements?
Understanding safety
- How might different people experience safety differently?
- Have we considered physical and psychological safety?
- Would everyone feel able to speak up if this design, process or control did not work for them?
Understanding systems
- What wider systems influence how this design is experienced?
- What unintended consequences could emerge?
- How might a decision in one part of the system affect another?
Understanding outcomes
- Who benefits from this solution?
- Who may experience additional effort, harm or disadvantage?
- How would we know whether the design is genuinely inclusive in practice?
Conclusion
Inclusion is often associated with social outcomes, but the evidence presented in this article demonstrates its relevance to engineering practice. Engineering decisions influence how people interact with infrastructure, technology, products and services, shaping outcomes related to safety, accessibility, usability and participation. Understanding the diversity of the people affected by those decisions is therefore an important aspect of effective engineering practice.
The application of human-centred design, systems thinking and equitable safety principles provides engineers with practical approaches for managing complexity, identifying risks and improving outcomes. In this context, inclusion is not simply a matter of compliance or representation; it supports sound engineering judgement and contributes to the delivery of solutions that perform more effectively across a wider range of users, environments and operating conditions.
The evidence base for inclusion extends beyond equity considerations alone. Research and practice demonstrate its contribution to safer systems, more informed decision-making, improved risk identification, enhanced user experiences and better overall system performance. As engineering challenges become increasingly complex and interconnected, the ability to recognise and respond to human diversity becomes an important element of professional competence.
Suggested educator use
- Use as pre-reading before a design, safety, ethics or systems-thinking session.
- Ask students to apply the reflective questions to a live design brief, case study or capstone project.
- Use the maturity model to review how inclusion is currently integrated across a module or programme.
- Invite students to identify where a design assumes an average user and then redesign using an “edges first” lens, bringing in concept of temporary or situational difference/requirements (i.e permanently hearing impaired, temporarily hearing infection, situational a loud environment – has same impact and requirement)
- Pair with a lived-experience speaker, accessibility audit or co-design exercise where feasible.
References
- Construction Leadership Council (n.d.) Equity, Diversity, Inclusion and Culture Change. Available at: Equity, Diversity, Inclusion and Culture Change – Construction Leadership Council (Accessed: 24 September 2026).
- International Organization for Standardization (ISO) (2019) ISO 9241-210:2019 Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems. Geneva: ISO.
- Meadows, D.H. (2008) Thinking in Systems: A Primer. White River Junction, VT: Chelsea Green Publishing.
- Heathrow (2025) Accessible and Inclusive Airport Standard: Part 2 – Requirements.
- Royal Institute of British Architects (RIBA) (2023) Inclusive Design Overlay for the RIBA Plan of Work. Available at: Inclusive Design Overlay to the RIBA Plan of Work (Accessed: 24 September 2026)
- Heathrow (2026) Heathrow Design Guides – Access and Inclusive Design Process.
Further reading
McLaughlin, J. (2025) The edges protect the centre: Equitable safety and inclusive design in the built environment. IOM3. Available at: IOM3 | The edges protect the centre (Accessed: 24 September 2026).
Acknowledgements
This contribution draws on previous work, including PEARLS and Wheel of Considerations, co-authored by Emily Castle, Carly Dickson and Jenny McLaughlin.
Any views, thoughts, and opinions expressed herein are solely that of the author(s) and do not necessarily reflect the views, opinions, policies, or position of the Engineering Professors’ Council or the Toolkit sponsors and supporters.
All contributions published through the Inclusive Engineering Toolkit have been subject to a structured peer review process to support quality, relevance, and consistency.
The Inclusive Engineering Toolkit recognises that inclusive language and terminology may vary across contexts and communities, and that contributors may use different approaches depending on context and preference, including identity-first and person-first language. Users are encouraged to contact us at admin@epc.ac.uk with any questions, concerns, or feedback regarding language used within toolkit resources.