Employable
Overview
Employable is a platform designed to integrate transformative AI solutions to address the challenge graduates face when applying for jobs through integrating post-interview feedback, improving job applications, and streamlining the recruiters’ process through engagement and job seeker analytics into a single, user-focused solution. This project's emphasis is on 'Agile Design'.
My Role
Solo project!
Timeline
September - October 2024
Achievements
Highest mark in cohort! 🕺
Every year, 300,000 students graduate from Australian universities. However, only 41% of applicants receive feedback post-interviews.
Approaching homeless individuals can be difficult, as they often feel vulnerable and reluctant to interact with researchers, stemming from past negative experiences or a lack of trust. Hence, we conducted secondary research, critically analysing reputable government reports, academic research, and news articles, based on research quality criteria we developed.
Agile Principles + Design Thinking + Double Diamond
I adopted an integrated approach that combines Agile principles with Design Thinking and the Double Diamond framework. This methodology facilitated a flexible, iterative, and user-centred process throughout the project. By systematically progressing through the phases of empathise, define, ideate, prototype, and test, I ensured our solution addresses key user pain points while remaining adaptable through continuous feedback.
Empathising with the graduates
The process began by immersing ourselves in the experiences of recent graduates (i.e., Sarah). We employed persona development, empathy mapping, and user journey mapping to capture human-centred perspectives. This focus on empathy aligns with Agile’s emphasis on “individuals and interactions over processes and tools” (Beck et al., 2020). By understanding graduates’ frustrations and aspirations, I laid a foundation for design decisions centred on user satisfaction and engagement.
Persona development
Empathy mapping
User journey mapping
Key insights
Defining the problem
In the define phase, I focused on framing the problem in a way that aligns closely with the user’s needs, through 5W1H context analysis, systems mapping, and HMW (How Might We) framework. This aligned with with Agile's value of customer collaboration, where engaging with the user is seen as more critical than adhering strictly to predefined contracts or agreements. Understanding the user's real needs and problems allows for a better collaboration process.
5W1H context analysis
I used the 5W1H framework to analyse the problem by asking critical questions: Who, What, When, Where, Why, and How. This thorough context analysis allowed us to gain a comprehensive understanding of the user's situation and the factors surrounding the issue. By exploring each of these aspects, I was able to uncover the essential details needed to align our solution with the user's true needs.
Systems Mapping
I also applied systems mapping to visualise the relationships and interdependencies between different elements in the system. I mapped out how various components, including users, stakeholders, and external factors, interacted with each other. This helped me understand the broader context and identify potential challenges and opportunities, ensuring that the solution was aligned with the larger system.
HMW (How Might We) Framework
Additionally, I used the How Might We (HMW) framework to transform the insights we gathered into open-ended question. This question prompted me to think creatively about potential solutions and set the stage for ideation. By framing the problem as "How Might We" questions, I was able to focus on actionable opportunities for innovation rather than being constrained by limitations.
How might organisations use innovative emerging technologies, including but not limited to artificial intelligence, quantum computing, digital twins, to fundamentally redesign how they attract, recruit and retain the modern workforce?
Ideating the solution
In the ideation phase, I put an emphasis on coming up with innovative yet practical solution to the problem, through Crazy 8 and Storyboarding. This aligned with with Agile's value of responding to change, as effective ideation fosters flexibility and creative exploration, responding to new insights and ideas.
Crazy 8
I utilised Crazy 8 to uncover the root causes to a surface-level problem and rapidly generate a diverse array of solutions (Tomitsch et al., 2018). This technique promotes quick, creative brainstorming, enabling us to explore unconventional ideas that tackle the root causes of the problem area. I selected my top three concepts and collaborated with other students to give each other feedback for the most promising solutions, supporting Agile principle on “collaboration and cross-functional teams”.
Storyboard
Then, I created a storyboard to visualise how our selected ideas would unfold in real-world scenarios. This helped me step into the user’s perspective, ensuring the solution’s flow was intuitive and practical. It also provided a clear framework for collaboration and refinement, aligning with Agile’s focus on adaptability and continuous improvement.
Prototyping the solution
Integrating the Double Diamond and Design Thinking framework supported an iterative cycle of exploration and refinement (Design Council, 2019). The nature of Design Thinking is non-linear; thus, prototyping and testing were interwoven. Initial prototypes underwent user testing sessions, which informed subsequent iterations. This ongoing process ensured that each iteration was grounded in real user experiences, aligning with Agile’s value of “working solutions over comprehensive documentation”
Wireframes
Hi-fi prototype
Testing the solution
I then presented our prototypes to another students and received feedback which prompted further adjustments, reinforcing that design is an evolving process. Each testing round provided insights that guided prototype modifications, showcasing our iterative approach. This cyclical relationship between prototyping and testing allowed me to enhance functionality and user experience continuously, ensuring the final solution effectively addresses user needs.
Feedback and Findings
Use of Minimum Viable Products (MVP)
MVPs will be used to receive the maximum amount of useful customer feedback from the least amount of completed work (Project Management Institute Inc., 2017), achieving the Agile principle of simplicity. By splitting Employable’s planned offerings into MVPs, I also aim to minimise any delays between product development, receiving customer needs, and market feedback (Anderson, 2016).
Furthermore, the use of modular feature rollouts ensures users can leverage immediate value early that incrementally evolves and expands based on user needs and feedback (Beck et al., 2001), hence allowing Employable to adapt to market volatility and make more informed decisions between releases.
Implementation Plan Timeline
Assumptions, Risks, and Responsibilities
Stakeholder Engagement
What makes Employable Special?
What did I learn through this project?
Thank you for reading!
