Why were we doing a redesign?
Why were we doing a redesign?
Why were we doing a redesign?
The CapSource platform allows educators to create requests for project proposals (RFPs) when building a Live Case program. Company users, known as industry partners, then create projects in the builder. Once approved by the educator, the project would run in their program…
…but in reality, the experience was anything but straightforward. Despite an existing self-service project builder, a poor user experience led to us writing the project requirements ourselves. We were losing potential users before project launch.
The CapSource platform allows educators to create requests for project proposals (RFPs) when building a Live Case program. Company users, known as industry partners, then create projects in the builder. Once approved by the educator, the project would run in their program…
…but in reality, the experience was anything but straightforward. Despite an existing self-service project builder, a poor user experience led to us writing the project requirements ourselves. We were losing potential users before project launch.
The CapSource platform allows educators to create requests for project proposals (RFPs) when building a Live Case program. Company users, known as industry partners, then create projects in the builder. Once approved by the educator, the project would run in their program…
…but in reality, the experience was anything but straightforward. Despite an existing self-service project builder, a poor user experience led to us writing the project requirements ourselves. We were losing potential users before project launch.
What research our redesign was backed by:
What research our redesign was backed by:
What research our redesign was backed by:
To get a sense of the project scope, the team conducted interviews with a few users and internal stakeholders. Focusing on industry partners, my key takeaways were:
The terminology was confusing
There was no quick way to get in touch with educators
No communication meant a lack of role clarification
(e.g. who should fill out what section?)
To get a sense of the project scope, the team conducted interviews with a few users and internal stakeholders. Focusing on industry partners, my key takeaways were:
The terminology was confusing
There was no quick way to get in touch with educators
No communication meant a lack of role clarification
(e.g. who should fill out what section?)
To get a sense of the project scope, the team conducted interviews with a few users and internal stakeholders. Focusing on industry partners, my key takeaways were:
The terminology was confusing
There was no quick way to get in touch with educators
No communication meant a lack of role clarification
(e.g. who should fill out what section?)
Design highlights:
Design highlights:
Design highlights:
(USER FLOW)
Redesigning the project building experience required a deep understanding of how industry partners would move along the process. I used our research insights to flesh out how educators and industry partners ideally should interact with the platform and each other.
(USER FLOW)
Redesigning the project building experience required a deep understanding of how industry partners would move along the process. I used our research insights to flesh out how educators and industry partners ideally should interact with the platform and each other.
(USER FLOW)
Redesigning the project building experience required a deep understanding of how industry partners would move along the process. I used our research insights to flesh out how educators and industry partners ideally should interact with the platform and each other.
(INFORMATION ARCHITECTURE)
Replicating the new user flow in the information architecture of the builder was key for creating a seamless ideal experience.
(INFORMATION ARCHITECTURE)
Replicating the new user flow in the information architecture of the builder was key for creating a seamless ideal experience.
(INFORMATION ARCHITECTURE)
Replicating the new user flow in the information architecture of the builder was key for creating a seamless ideal experience.
(CONTENT DESIGN REVISIT)
Often, a project proposal would be stalled at the project background stage. Interviews highlighted a need for clearer instructions on what to do when. I rewrote the language here, as well as streamlined what actions industry partners would complete here.
(CONTENT DESIGN REVISIT)
Often, a project proposal would be stalled at the project background stage. Interviews highlighted a need for clearer instructions on what to do when. I rewrote the language here, as well as streamlined what actions industry partners would complete here.
(CONTENT DESIGN REVISIT)
Often, a project proposal would be stalled at the project background stage. Interviews highlighted a need for clearer instructions on what to do when. I rewrote the language here, as well as streamlined what actions industry partners would complete here.
(TALKING TO EDUCATORS)
I also explored in-builder communication, eventually creating a 'Meet with Academic Partner' option right in the builder.
(TALKING TO EDUCATORS)
I also explored in-builder communication, eventually creating a 'Meet with Academic Partner' option right in the builder.
(TALKING TO EDUCATORS)
I also explored in-builder communication, eventually creating a 'Meet with Academic Partner' option right in the builder.
Impact of our redesign
Impact of our redesign
Impact of our redesign
Launched in July 2022
Reduced user call time by 10 hours per week
Design team now creates trigger points for messaging between users in flows
Launched in July 2022
Reduced user call time by 10 hours per week
Design team now creates trigger points for messaging between users in flows
Launched in July 2022
Reduced user call time by 10 hours per week
Design team now creates trigger points for messaging between users in flows
