GrantMe - EdTech

Streamlined content management with internal tool redesign

Impact

Reduced task completion from 15 to 10 mins (33%) during user testing

Role

Full Time Product Designer

Team

Product Manager, COO, Student Success Manager, Student Success Team (Content Management Team)

The problem with old scholarship data

We have over 3,000+ scholarships that our content team keeps updated. These scholarships change their application process every year, and we could not keep up. This resulted in students writing scholarship applications based on old information, which led to negative reviews, poor user experience, and even refunds.


For this problem, we worked with the content team to improve our scholarship updating process.

The process

Setting a goal to create direction

To drive clarity on what to design for, I discussed with the product manager, COO, and content team manager, on what metric we should monitor.


15 minutes to update one scholarship was too long

With the volume of scholarships we had to update, spending 15 minutes per update was too long. With the number of people we had, it would be unfeasible to update all the key scholarships in time.

Our goal was to reduce the task duration of updating one scholarship.

Flow redundancies and in-person interruptions slowed the process down

I job-shadowed, conducted interviews, and reviewed screen recordings to understand the Jobs To Be Done to update a scholarship.

Learnings

  • There were 2 main flows: Updating scholarships based on deadlines, and updating scholarships based on reports of problems
  • A lot of time went into browsing each scholarship's website for updates
  • Team members were often interrupted with people asking them questions/giving requests

There were many opportunities to reduce steps and save time in their current flow


After drafting a user flow, I could easily and quickly identify where time could be saved.

Time was lost to

  • Looking for which scholarships to update next
  • Finding the link to a scholarship website
  • Updating the status of the scholarship

Keeping stakeholders informed led to operational improvements

I presented our findings of the main areas of problems to our CEO, founder, and Product Manager. From this, we gained alignment and feedback, and initiated 2 projects.

I became responsible for designing an internal tool to streamline the scholarship management process!

Inspiration from familiar tools

I researched how other tools looked, with special attention to the tools our team already uses to leverage the Consistency and Standards usability heuristic.

Learnings

  • Hubspot's Tasks experience makes transitioning between tasks seamless
  • A dashboard that focuses on one component drives faster action
  • A complicated dashboard (Ex: Kanban board) starts off slower, but the user has a better understanding of the state of the system

Determining information hierarchy to jump-start wireframes

I worked with my design mentor to create object-diagrams and ideate on how information should be organized.

Insights

  • Group scholarships based on the 2 different flows: Scholarship Reports and Scholarship Updates
  • Have a summary row at the top so managers and team members easily know the status of the system
  • Navigation menus are unnecessary since we only have 3 flows

Iterating with the team

I worked closely with my product manager and the Student Success content team to ideate and iterate on the design.

Simple flows felt faster

Insights

  • A more focussed view of the homepage drove faster action and felt clearer compared to the kanban board
  • The kanban board felt cluttered, not everything on the page is needed at the same time
  • Team members preferred when Scholarship details opened as a slideout, it felt "easier"

Identifying unclear elements through user testing

After determining the flow approach, I added details to the designs for further testing.

Insights from user testing

  • The relationship between the summary statistics and the content was unclear, object labels were not consistent enough
  • There was confusion with what the "Start" button did, and how it's similar to clicking a specific scholarship in the list
  • The tabs for Approach B was grouped incorrectly, users were confused on if the tabs would have repeat or unique scholarships

Bringing clarity to confusing elements

I iterated based on the user testing results. I also initiated a design review with my design mentor to get more feedback.

Insights

  • Turned the Reports section to a conditional alert with a slideout flow
  • Cleared up the wording so similar objects were labelled exactly the same
  • Clarified the tab groups, moved "All funding" so it is a separate section

Remaining flexible during change

At this point, the Scholarship Report flow was changed. Now, we wanted Scholarship Reports to be secondary to Scholarship Updates, which is not what the current design communicates. I quickly met with the product manager and Student Success team manager to clarify the flow changes and align on what to expect.

Key changes

  • Removed the Report alert, as visually, an orange alert looks very important
  • Added the Reports flow to the All Scholarships section, underneath the Scholarship Updates section (the Coming Up In 3 Months section)
  • Adjusted the titles and copy accordingly

Simplifying transitions between Scholarships

From our research, we found that time was lost to identifying scholarships to update, finding the scholarship link, and updating scholarship status. I worked closely with the Student Success Team to ideate, test, and design what the slide-out flow would look like.

Key design outcomes

  • Moved scholarship website link to the top and blue, like a typical link
  • Update the scholarship status automatically by clicking a button
  • After updating a scholarship, automatically transition to the next scholarship

Impact

Unfortunately, this tool has yet to be built as the company goes through some structural changes. However, during testing with the team, I found the following:

-5 minutes

Save 5 minutes per scholarship update

This 33% improvement is significant, especially given that we have approximately 3,000 scholarships that need to be updated every month. This 5 minutes saved per scholarship amounts to 250 hours saved a month!

Reflection

How to iterate quickly with teammates

With our users being teammates within the same office, it was a lot easier to collaborate with them. However I still needed to be mindful about using their time intentionally. Thus, opportunities to design more efficiently included being able to use lo-fi designs to iterate, and being able to job shadow easily. Identifying these opportunities helped me design a solution more quickly, and also build buy-in as the team was very involved in the process.



Handling changes mid-design

The flow for a key action was changed mid-way through the project. Despite that, What helped this transition go smoothly without adding too much time to the project was the swift communication with the manager on exactly what was changed. During this conversation, I asked questions to clarify exactly what was changed and what wasn't. From there, in conjunction with the information-hierarchy work we did earlier, I was able to easily adjust the changed flow without having to change any other part of the design.

← Back to Case Studies