Understand
Translate business requirements and stakeholder needs into clear user journeys, interface requirements and priorities.
ISFAP
UX/UI · Product Design · Digital Ecosystem
Case Study · 01
Designing a connected digital experience for student success.
A connected digital ecosystem spanning the public website, student experience and administration platform.
Explore case study
00 — Overview
ISFAP required more than a website. The project brought together multiple digital touchpoints serving students, administrators, funders and internal teams.
Role
UX/UI Design
Digital Product Design
Front-end Collaboration
Platforms
Public Website
Student Portal
Administration Portal
Collaboration
Business Analysis
Development Team
Stakeholders
01 — The Challenge
One ecosystem. Multiple audiences.
The challenge was to create a coherent digital experience across very different users, needs and workflows.
Students needed a clear way to manage their academic journey, tasks, documents and support. Administrators needed tools to manage funding, reporting and operational processes, while funders and internal teams required visibility into the wider programme.
01
Public Website
Communicating ISFAP's mission, funding opportunities and programme information.
02
Student Portal
Giving students access to tasks, documents, referrals, academic information and support services.
03
Administration Portal
Supporting funding management, reporting, student administration and operational workflows.
02 — Student Experience
Designing around the student journey.
The student portal brought everyday tasks, academic information, documents and support services into one accessible environment.
01
Entry point
02
Student dashboard
03
Tasks & workflow
04
Navigation system
03 — Administration
Making complexity manageable.
The administration platform brought funding, student management, reporting and operational workflows together within a structured working environment.
02
Supporting complex operational workflows.
The interface needed to provide administrators with clear access to funder management, student allocation, reporting and operational actions without losing sight of the wider system.
Funder Management
Administration Portal
04 — Beyond the Interface
Designing beyond the happy path.
Designing the platform also meant considering what users could access, what they couldn't, and how the experience responded when permissions or circumstances changed.
01
Access & Permissions
The right experience for the right user.
Different roles required different levels of access across the administration environment. Permission states needed to be communicated clearly while giving users an obvious route back into the appropriate workflow.
Role-based access
Permission state
02
Design considerations
01
Accessibility
Interface decisions considered usability beyond ideal viewing conditions, including colour-blind accessibility and the need to avoid relying on colour alone to communicate meaning.
02
Role clarity
Navigation and functionality needed to adapt to different user roles while keeping the overall system understandable and consistent.
03
Workflow visibility
Status indicators, task states and operational information helped users understand where they were within complex administrative processes.
05 — Role & Collaboration
From requirements to working product.
My role connected UX/UI design with business requirements and technical implementation, working closely with business analysis, stakeholders and the development team.
Design
Develop UX and visual interface solutions across the public website, student portal and administration environment.
Collaborate
Work alongside business analysis and an 11-person development team within an Agile delivery process.
Implement
Support implementation with production HTML and close collaboration between design and development.
06 — Outcome
One connected digital ecosystem.
The project brought public-facing communication, student services and administrative workflows into a more cohesive digital experience — designed around the needs of different users while maintaining a consistent system.