User centric roadmap setup

imjaykr1118 Avatar

Published on 24/09/2022 by Jay Kim

Prioritise ideas and requirements

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

Understand ‘Why’

To truly understand the challenges students face each semester, I asked current Monash students to break down a semester into key stages and list the typical activities at each stage. I then asked them to explain how they personally complete each activity.

A semester journey mapping workshop

Semester Journey Workshop

Understand the students’ activities to find opportunities

For example, when it comes to tracking assessment due dates, some students with fewer assessments found that adding deadlines to their Google or Apple calendar worked well. On the other hand, students managing a larger number of assessments found this setup tedious and preferred simply printing out a list of due dates.

Hearing about these workarounds gave me valuable insight into just how unsatisfied students are with the current process and highlighted what the system at Monash is missing.

Impactfulness score

The results of the workshops highlighted where the key pain points were and how desirable potential solutions would be. This provided the team with a valuable starting list of features. To define the MVP for the app launch, we needed to further refine this list by assessing both feasibility and impact, allowing the team to prioritise effectively.

For the feasibility check, the mobile development team and I reviewed each item to determine how ready the necessary data was to support the feature. Unfortunately, some highly desired features—like the assessment weight breakdown—were unlikely to be available in the near future. These features required significant changes to the workflow on the teaching staff’s side to first clean and structure the data. We decided to set aside these long-shot features as future action items to address with the relevant stakeholders.

When it came to estimating impact, we aligned on two key criteria: how broadly each feature would affect the user base and how frequently each feature would likely be used.

Scale by study type
How many students does this feature affect?

5: All types
4: All coursework students
3: All research students
2: Some coursework students
1: Some research students

Scale by geometrics
How many students does this feature affect?

5: All campuses
4: All Australian campuses
3: Malaysian campuses
2: Clayton campuse only
1: Other

Frequency
How often do students look up this information?

5: Daily
4: Weekly
3: Monthly
2: Yearly
1: Less then yearly

Uniqueness
How many mobile features can be utilised?
(e.g. camera, NFC, notification, widget, geo-fence)

5: More than 4 features
4: More than 3 features
3: More than 2 features
2: At least 1 feature
1: None

The impact analysis on features based on the workshop results

Timetable: The best impact with the least effort

The analysis quickly revealed a clear opportunity for the mobile app: to become a one-stop hub for managing daily schedules. This emerged as the most consistently frustrating task that coursework students faced several times a week.

How can we help?