By the end of this lesson you can
- Identify technical, business, legal and time constraints.
- Design creatively within constraints.
- Negotiate constraints with evidence.
The idea
Every product has constraints. Good designers find them early and use them to focus the work.
Types of constraint
- Technical: legacy systems, data availability, performance, platform limits, third-party services.
- Business: budget, pricing, brand rules, partnerships.
- Legal and regulatory: data protection, accessibility law, financial or health regulations, consent requirements.
- Time and people: deadlines, team size, skills.
- User context: devices, connectivity, environments.
Working with constraints
Ask early: "What can't we change?" Separate true constraints from assumptions. Many supposed constraints ("the system can't do that") turn out to be negotiable when someone asks how hard it would be.
Designing within them
Explore options that work today, plus an ideal version for the future. Phase work so the first release fits constraints while moving towards the ideal. Use evidence (user impact, cost of support calls) to argue for removing a constraint when it really harms users.
Why it matters in real projects
Designs that ignore constraints get rejected or watered down late, which wastes time and damages trust. Designers who understand constraints produce work that ships, and they know when and how to push back. Constraints also spark creativity by narrowing the problem.
A realistic example
A designer wants instant identity checks during sign-up for a lending app. Engineering explains the third-party check can take up to two minutes, and regulation requires it before any loan offer.
The designer redesigns the flow: the check starts in the background as soon as the minimum details are entered, while people continue with other questions. A clear progress message explains the wait. Most checks finish before people reach the offer page, and drop-off during the wait falls.
Step by step
Ask early
Ask PMs, engineers and legal what cannot change.
List constraints
Categorise them by type.
Test assumptions
Ask how hard each "constraint" would be to change.
Design options
Create a version within constraints and an ideal version.
Phase
Plan steps from today's version to the ideal.
Argue with evidence
Use user and business impact to challenge harmful constraints.
Common mistakes
Mistake Discovering constraints at handoff.
Instead Ask in the first week.
Mistake Accepting every constraint as fixed.
Instead Ask how hard it is to change.
Mistake Arguing from opinion.
Instead Use evidence of impact.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 30 min
Constraint map
Map constraints for a project.
Steps
- List constraints by type.
- Mark each as confirmed or assumed.
- Design a constrained and an ideal version of one screen.
- Write a phasing plan.
Deliverable
A constraint map, two designs and a phasing plan.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Constraints are technical, business, legal, time and user context.
- Find them early and test assumptions.
- Design within them and phase towards the ideal.
- Challenge harmful constraints with evidence.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Design constraints (opens in a new tab)Interaction Design Foundation
- Scoping your service (opens in a new tab)GOV.UK Service Manual
Your notes
Marking complete updates your course and roadmap progress.