User need discovery complexity is the effort and unpredictability involved in identifying unmet user needs.
User need discovery complexity measures the effort and unpredictability involved in identifying unmet user needs. It helps stakeholders estimate value and effort for investment decisions. section 10.2.2
Assess it by considering:
Novel, unproven concepts in a subdomain’s genesis phase, where research and experimentation are extensive. section 10.2.2
Mature or commoditized concepts, where industry convergence makes new differentiation difficult. section 10.2.2
Multiple perspectives rather than a single person’s gut feeling, reducing cognitive bias and improving assessment conversations. section 10.2.2
Two high-complexity conditions
A novel subdomain may require substantial research and experimentation before unmet needs become clear. A mature subdomain may require equally difficult discovery because users and competitors have converged on familiar functionality. section 10.2.2
How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it
How deep it goes
Defines discovery effort and unpredictability, then distinguishes high complexity in genesis and commodity conditions.
Examples
Uses novel unproven concepts and mature commoditized functionality as contrasting discovery examples.
What it assumes
Assumes subdomain assessment and teaches the distinction between novelty-driven and differentiation-driven uncertainty.
What you can do after
Evaluate discovery complexity through logical reasoning and input from product and UX specialists.
How it connects
Connects Wardley Mapping with model complexity, product design complexity, and domain model design complexity.
complexitypart of · Complexity is the degree of difficulty in understanding, analyzing, changing, or operating a system or problem, arising from its structure, behavior, or interacting parts.
This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.
