Short answer

Before finalizing a digital identity system design, explicitly question and validate assumptions about user trust, technical skill, and business model feasibility, as these are common failure points.

Field
User-Centred Design
Source
Proceedings of the ... Annual Hawaii International Conference on System Sciences/Proceedings of the Annual Hawaii International Conference on System Sciences (2020)
Method
Systematic Literature Review
Evidence
Moderate effect

The design of digital identity management systems frequently relies on unexamined assumptions about user trust, their technical capabilities, and the ease of establishing win-win business models, which can hinder real-world adoption. This user-centred design research insight is drawn from a 2020 study published in Proceedings of the ... Annual Hawaii International Conference on System Sciences/Proceedings of the Annual Hawaii International Conference on System Sciences. Using Systematic literature review, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Before finalizing a digital identity system design, explicitly question and validate assumptions about user trust, technical skill, and business model feasibility, as these are common failure points.

Study
User-Centred DesignHigh ImpactModerate effect

Digital Identity Systems Often Overlook User Trust and Capability Assumptions

The design of digital identity management systems frequently relies on unexamined assumptions about user trust, their technical capabilities, and the ease of establishing win-win business models, which can hinder real-world adoption.

Proceedings of the ... Annual Hawaii International Conference on System Sciences/Proceedings of the Annual Hawaii International Conference on System Sciences · 2020

01

Key Findings

  • 01Digital identity solutions are built upon assumptions regarding organizational collaborations and trust relationships.
  • 02Assumptions are made about users' ability to manage cryptographic materials.
  • 03The ease of identifying mutually beneficial business models is often assumed.
  • 04These assumptions can act as inhibitors to the successful deployment of digital identity systems.
02

Application

Design takeaway

Before finalizing a digital identity system design, explicitly question and validate assumptions about user trust, technical skill, and business model feasibility, as these are common failure points.

How to apply

When designing any system involving user authentication or data sharing, conduct workshops with potential users and stakeholders to uncover and address implicit assumptions about trust, usability, and value proposition.

Project actions

  • 01When designing a digital system, list all the things you assume users will know or do.
  • 02Talk to potential users early to see if your assumptions about their trust and skills are correct.
03

Method & Evidence

AimWhat are the common non-technical assumptions embedded within digital identity management system architectures, and how do they impact their potential for real-world implementation and interoperability?
MethodSystematic Literature Review
ProcedureThe researchers conducted a systematic review of existing literature on digital identity solution architectures to identify and extract the underlying non-technical assumptions related to organizational, business, trust, and human-user factors.
ContextDigital Identity Management Systems

Variables

IVNon-technical assumptions (organizational, business, trust, human-user)
DVInteroperability and potential for real-life inhibitors of digital identity management systems
04

Strengths & Limitations

Strengths

  • +Provides a structured overview of a complex field.
  • +Identifies critical, often overlooked, non-technical factors.

Limitations

The findings are based on a review of existing research, so they might not cover every possible scenario or new development in digital identity.

Reliability & validity

The reliability of the review depends on the quality and comprehensiveness of the literature searched. Validity is enhanced by the systematic approach to literature selection and analysis.

Think critically

To what extent do current digital identity solutions adequately address the 'human factor' and 'business viability' assumptions, and what are the consequences of these oversights?

05

Design Principles

"Validate all non-technical assumptions through user research and stakeholder engagement before system deployment."

Understanding these non-technical assumptions is crucial for designers developing digital identity solutions. Overlooking them can lead to systems that are technically sound but practically unworkable due to user resistance, lack of perceived value, or unaddressed security concerns.

06

What This Means for Your Design

When creating digital ID systems, designers often assume people will trust them, know how to use them, and that businesses will make money easily. This research shows these assumptions can be wrong and stop systems from working.

How to use in your project

  • 1.Use this research to justify the need for user research into trust and capability when designing digital identity solutions.
07

Add to My Project

08

Quick Cite

Paragraph starter

This research underscores the critical importance of addressing non-technical assumptions in digital identity management. By identifying and validating assumptions related to user trust, technical capabilities, and business model viability, designers can create more robust and user-centric solutions that are more likely to succeed in real-world applications.

09

Source

Proceedings of the ... Annual Hawaii International Conference on System Sciences/Proceedings of the Annual Hawaii International Conference on System Sciences

The Review of Non-Technical Assumptions in Digital Identity Architectures

journal · 2020

View source

Questions About This Research

What does the research say about digital identity systems often overlook user trust and capability assumptions?
Before finalizing a digital identity system design, explicitly question and validate assumptions about user trust, technical skill, and business model feasibility, as these are common failure points. Evidence: Proceedings of the ... Annual Hawaii International Conference on System Sciences/Proceedings of the Annual Hawaii International Conference on System Sciences (2020).
Why does "Digital Identity Systems Often Overlook User Trust and Capability Assumptions" matter for design?
Understanding these non-technical assumptions is crucial for designers developing digital identity solutions. Overlooking them can lead to systems that are technically sound but practically unworkable due to user resistance, lack of perceived value, or unaddressed security concerns.
How can designers apply this research?
Before finalizing a digital identity system design, explicitly question and validate assumptions about user trust, technical skill, and business model feasibility, as these are common failure points.
What were the main findings?
Digital identity solutions are built upon assumptions regarding organizational collaborations and trust relationships.. Assumptions are made about users' ability to manage cryptographic materials.. The ease of identifying mutually beneficial business models is often assumed.. These assumptions can act as inhibitors to the successful deployment of digital identity systems.
What research method was used?
Systematic Literature Review.
How strong is the evidence?
Evidence strength is rated Moderate effect, based on a 2020 journal from Proceedings of the ... Annual Hawaii International Conference on System Sciences/Proceedings of the Annual Hawaii International Conference on System Sciences.
What should I do differently in my next project?
When designing any system involving user authentication or data sharing, conduct workshops with potential users and stakeholders to uncover and address implicit assumptions about trust, usability, and value proposition.
What are the limitations?
The review is based on existing literature, which may have its own biases or gaps. The focus is on architectural assumptions, not necessarily implementation-specific details.