01 / Selected work
Work that shows the decisions behind the product.
Luminor’s work connects organizational priorities, user needs, operational realities, and delivery constraints.
These representative case-study directions examine what changed, why it changed, and how the product became clearer—not only how the final interface looked.
02 / What the work reveals
Work should explain what changed.
A strong case study should make the original problem clear.
It should show what the organization needed to improve, what users were trying to accomplish, what stood in the way, and which decisions changed the direction of the product.
It should also explain the constraints. Policies, legacy technology, internal processes, security requirements, accessibility, and delivery timelines all shape what is possible.
The final story is not only about design output. It is about how the organization moved from uncertainty to a product it could build, operate, and improve.
What every case study makes visible.
Each case-study direction makes visible:
The business context
Why the initiative mattered and what the organization needed to change.
The people and operations
Who depended on the product, how work happened, and where friction or failure occurred.
The product decisions
What was prioritized, simplified, tested, changed, or deliberately excluded.
The constraints
How policy, regulation, technology, data, accessibility, security, and delivery requirements shaped the solution.
The path to implementation
How the design was documented, validated, and prepared for development.
The outcome
What improved for users, teams, operations, or the wider organization.
Enterprise Platform
Make complicated work easier to manage.
This representative direction examines an internal platform supporting high-volume activity, multiple user roles, dense information, and operational decision-making.
It shows how the team understands the current operation, identifies avoidable friction, simplifies key workflows, and creates a product structure that supports both common tasks and important exceptions.
The case study will include:
- Business and operational context
- Existing workflow and system analysis
- Employee research
- Role and permission requirements
- Information architecture
- Workflow and interface decisions
- Technical collaboration
- Design system considerations
- Validation and implementation support
- Operational and adoption outcomes
Customer Portal
Give customers clarity without hiding the complexity behind the service.
This representative direction examines a self-service product designed to help customers access information, manage an account, complete transactions, or request support.
It shows how the experience balances customer expectations with security, compliance, internal processes, technical dependencies, and the realities of service delivery.
The case study will include:
- Customer needs and service barriers
- Support and operational data
- Existing journey analysis
- Information and content structure
- Authentication and account requirements
- Transaction and service workflows
- Usability testing
- Accessibility considerations
- Implementation support
- Completion, support, satisfaction, or adoption outcomes
Healthcare Product
Connect the product around the care journey.
This representative direction examines a healthcare product serving patients, providers, administrators, and care teams.
It shows how the work connects different users, responsibilities, information needs, and service handoffs without losing sight of privacy, accessibility, clinical priorities, or the emotional circumstances in which the product is used.
The case study will include:
- Patient and provider needs
- Administrative and clinical workflows
- Information movement across the service
- Privacy and accessibility requirements
- Journey and service blueprinting
- Product architecture
- Interaction and content decisions
- Validation with relevant users
- Delivery collaboration
- Care, service, or operational outcomes
Government Service
Make the service easier to access and easier to deliver.
This representative direction examines the modernization of a public-facing or internal government service.
It shows how policy, administrative requirements, citizen needs, accessibility, staff workflows, and institutional constraints translate into a clearer digital service.
The case study will include:
- Policy and service context
- Citizen and employee research
- Existing forms and process analysis
- Accessibility and inclusion requirements
- Service journeys and blueprints
- Application and case-management workflows
- Content and information design
- Technical and procurement constraints
- Implementation support
- Public and operational value
08 / Start a conversation
Working through a similar decision?
Tell us what the organization needs to improve, what has already been decided, and where uncertainty remains.
Discuss the initiative