Hard/Soft Constraint Classification

Purpose

Systematically categorise constraints affecting a validated need into hard constraints (immutable boundaries the innovation must operate within) and soft constraints (assumptions, preferences, or current limitations that can potentially be challenged through innovation, technology advancement, or strategic choice). The classification determines where creative effort should focus: design within hard constraints, innovate against soft constraints.

When to use

A1.4 Step~2 (Technical Constraint Mapping), after brainstorming potential constraints across technical, regulatory, organisational, and user/market categories. Also applicable in A4 (Development) when new constraints emerge and require classification.

Output

Technical Constraint Map (visual) with accompanying narrative. Hard constraints (red) define solution space boundaries; soft constraints (yellow) mark innovation targets. Each constraint annotated with classification rationale and design implications.

Inputs

• Brainstormed constraint list (15–40 potential constraints across 4 categories)
• A1.3 Problem Definition Brief (boundaries, success criteria)
• Domain expert access (2–4 experts for validation interviews)
• Regulatory/legal reference documents (for regulated domains)

Procedure

1. Validate each constraint. For each brainstormed constraint, confirm through expert interview: Is this actually a constraint, or a misconception? How binding is it? Discard invalid constraints.
2. Apply Hard classification test. A constraint is Hard if it meets all three criteria: itemize
3. Immutable within reasonable innovation timeline (0–3 years)
4. Violating it causes solution failure (legal liability, physical impossibility, organisational non-starter)
5. No known workarounds or alternative approaches exist itemize Examples: laws of physics, federal regulations (HIPAA, GDPR, FDA), fundamental safety requirements.
6. Apply Soft classification test. A constraint is Soft if it meets any one criterion: itemize
7. Challengeable with technology advancement (currently limiting but improving)
8. Based on assumptions or preferences (not absolute requirements)
9. Workarounds exist (constraint can be avoided with creative approaches)
10. Organisational choice (could be changed with leadership decision) itemize Examples: current AI accuracy thresholds, “users won't adopt new workflows,” “must be on-premise.”
11. Document classification rationale. For each constraint: classification (H/S), evidence supporting classification, expert who validated, confidence level.
12. Derive design implications. For Hard constraints: what solution boundaries does this impose? For Soft constraints: what innovation approach could challenge this? What investment would be required?

Quality criteria

• All four constraint categories represented (technical, regulatory, organisational, user/market)
• Every classification validated by ≥1 domain expert
• No “all Hard” or “all Soft” maps (both signal insufficient analysis)
• Design implications documented per constraint
• Soft constraint relaxation pathways identified

Common errors

• Classifying without expert validation — Lead assumptions substituted for domain knowledge
• Wishful Soft — classifying genuinely hard regulatory constraints as soft because the team hopes they'll change
• Defensive Hard — classifying soft assumptions as hard to avoid the effort of challenging them
• Missing organisational constraints — focusing on technical/regulatory while ignoring capability limitations, brand constraints, or resource ceilings

Theoretical basis

Constraint Theory and Innovation Under Constraints (Goldenberg et al., 2001; Moreau & Dahl, 2005). Research demonstrates that well-defined constraints enhance innovation by focusing creative effort.