Beyond

A Competency-Driven Learning Management System

Leveraging Design Thinking and Flutter Flow to Create a Training & Compliance Management

A Journey from Empathy to Implementation

This project involves the creation of a Learning Management System (LMS) designed to support the competency development of carers at Bleep 360 Care. The LMS is structured to provide a comprehensive pathway for carers to improve their skills through targeted modules and assessments. Developed using Flutter Flow, the platform ensures that all design and development stages are seamlessly integrated to produce a user-friendly and effective learning environment.

Empathise: Deep Understanding Through User Engagement

In the empathise phase, my primary objective was to deeply understand the needs, challenges and frustrations of the end-users who would interact with the Learning Management System (LMS) at Bleep 360 Care. This phase was crucial for ensuring that the final product would be genuinely user-centred and address real-world problems faced by carers and healthcare professionals.

Engaging with the Regional Care Manager

To start, I closely collaborated with a regional care manager who was responsible for overseeing the competency training of carers. The manager was using a paper-based system to track and manage the carers’ progress. This system, while functional, was outdated and prone to errors, leading to inefficiencies that affected the quality and speed of care delivery.

During our discussions, the care manager highlighted a few pain points:

Inefficiency in Record-Keeping

The manual process of recording training progress was time-consuming and often led to discrepancies in records. Important data could be lost, and tracking individual carers’ progress was cumbersome.

Lack of Real-Time Data

The paper-based system did not provide real-time updates, which meant that the manager could not immediately see who was compliant and who needed further training. This delay often resulted in carers being non-compliant without anyone realising it until it was too late.

Difficulty in Assessing Competency

With the manual system, it was challenging to assess the competency of carers quickly. The process of reviewing completed training modules and identifying gaps in knowledge was labor-intensive.

By understanding these specific challenges, I was able to start thinking about how a digital solution could alleviate these problems and make the care manager’s job more efficient and less stressful.

 

Collaborating with Carers and Healthcare Professionals

In addition to working with the care manager, I spent time with carers and other healthcare professionals who would be the primary users of the LMS. Their input was invaluable as they were the ones who would ultimately be using the system daily to stay compliant and improve their skills.

From these interactions, I learned:

User Comfort with Technology

Carers had varying levels of comfort with digital platforms. While some were tech-savvy, others were less confident in using new software. This insight was critical in designing an interface that was simple and intuitive, catering to all users regardless of their technological proficiency.

Training and Compliance Needs

Carers expressed the importance of having easy access to training modules and assessments. They needed a system that would remind them of pending tasks and help them track their progress without having to navigate through complex menus.

Desire for Feedback and Support

Many carers valued having immediate feedback on their progress. They wanted a system that would not only track their compliance but also provide them with guidance on areas where they needed improvement.

These conversations helped me to understand the emotional and practical needs of the carers. I was able to empathise with their experiences, both the frustration with the existing system and their hopes for a better solution.

 

Observational Research

To supplement the direct interactions, I also conducted observational research. I watched how the care manager and carers interacted with the current system, noting down the steps they took and the challenges they encountered. This hands-on observation allowed me to see firsthand the inefficiencies and pain points that were not always fully articulated in discussions.

For example, I observed:

The Cumbersome Process of Updating Records

It took considerable time for the care manager to manually update training records, often leading to delays in recognising carers’ compliance status.

Errors in Data Entry

The manual system was prone to human error, which could lead to inaccuracies in the carers’ competency records.

This direct observation confirmed and deepened my understanding of the issues that needed to be addressed in the digital solution.

 

Conclusion

The empathise phase was critical in shaping the direction of the project. By engaging directly with the regional care manager, carers and other healthcare professionals, I was able to develop a deep understanding of their needs and challenges. This thorough understanding provided a solid foundation for the subsequent stages of the design thinking process, ensuring that the final LMS would be tailored to the actual needs of its users, ultimately leading to a more efficient, user-friendly and effective system.

Define: Crafting a Clear Problem Statement

In the Define phase, the goal was to take the insights gathered during the Empathise stage and distil them into a clear and actionable problem statement. This phase is critical as it sets the direction for the rest of the design process, ensuring that the solutions developed are focused on addressing the real needs of the users.

Synthesising Insights from Empathise

Having deeply understood the challenges faced by the regional care manager and the carers using the paper-based system, I began by synthesising the key insights:

Inefficiency and Time Consumption

The current paper-based system was laborious, requiring the care manager to spend a significant amount of time manually updating and tracking carers’ training records. This process was not only time-consuming but also prone to errors, leading to discrepancies in data and delays in recognising carers’ compliance status.

Lack of Real-Time Data and Visibility

The absence of real-time updates in the existing system meant that there was a lack of immediate visibility into carers’ progress and compliance. This gap made it difficult for the care manager to quickly assess who was up to date with their training and who needed further attention.

Diverse User Needs

The carers who would be using the LMS had varying levels of digital literacy. While some were comfortable navigating digital platforms, others found it challenging, particularly when the interface was not intuitive. This diversity in user capabilities meant that the LMS needed to be designed in a way that was accessible and easy to use for everyone, regardless of their technical proficiency.

Desire for Continuous Feedback

Carers expressed a need for a system that would provide continuous, immediate feedback on their training progress. They wanted a platform that not only tracked their compliance but also offered guidance on areas that required improvement, thus supporting their ongoing professional development.

 

Defining the Problem Statement

With these insights in hand, I formulated the problem statement that would guide the development of the LMS:

Problem Statement

Bleep 360 Care needs a digital Learning Management System (LMS) to replace its current paper-based competency tracking system. The new LMS should provide real-time data visibility, streamline the record-keeping process and be accessible to carers with varying levels of digital literacy. Additionally, the system should offer continuous feedback and guidance to support carers in maintaining compliance and improving their professional skills.

This problem statement encapsulated the core issues identified during the empathise phase and provided a clear direction for the next stages of the design thinking process. It emphasised the need for a solution that would not only digitise the existing processes but also enhance them by addressing the specific pain points of time inefficiency, lack of real-time data and the diverse needs of users.

 

Establishing Design Goals and Criteria

From the problem statement, I developed specific design goals and criteria that the LMS needed to meet:

  1. Efficiency and Accuracy: The LMS should significantly reduce the time spent on record-keeping and eliminate errors associated with manual data entry. Automation of routine tasks should be a key feature.
  2. Real-Time Tracking: The system must provide real-time updates on carers’ progress, allowing managers to have instant access to compliance data and make informed decisions quickly.
  3. User-Friendly Interface: The LMS should be designed with a focus on usability, ensuring that carers of all technical abilities can navigate the system easily. This includes clear navigation paths, intuitive icons and accessible language.
  4. Continuous Feedback Mechanism: The LMS should incorporate features that provide carers with ongoing feedback on their progress, including reminders for pending tasks, performance summaries and suggestions for improvement.
  5. Scalability and Flexibility: The system should be flexible enough to accommodate the evolving needs of Bleep 360 Care, with the ability to add new modules, assessments and features as required.

 

Conclusion

The Define phase was essential in transforming user insights into a clear and actionable problem statement that guided the design and development of the LMS. By focusing on the core issues identified during the empathise phase, I was able to establish design goals that ensured the final product would effectively address the needs of Bleep 360 Care. This clarity provided a strong foundation for the subsequent Ideate, Prototype and Test phases, ensuring that each step was aligned with the overarching objective of creating a user-centred, efficient and responsive LMS.

Ideate: Generating Creative Solutions

The Ideate phase of the design thinking process is where creativity and collaboration come into play. After clearly defining the problem in the previous stage, the goal here was to brainstorm a wide range of possible solutions for the Learning Management System (LMS) that would meet the needs of Bleep 360 Care. This phase was essential in ensuring that the final design would be innovative, user-centred, and effective in solving the identified problems.

 

Brainstorming with Stakeholders

To kick off the ideation process, I facilitated brainstorming sessions with the key stakeholders, including the regional care manager, carers and healthcare professionals. These sessions were designed to be open and inclusive, encouraging all participants to share their ideas, no matter how unconventional they might seem. By involving a diverse group of people, we were able to tap into a wide range of perspectives and expertise.

 

Key Ideas Generated:

  1. Modular Learning System: One of the prominent ideas that emerged was the concept of a modular learning system. This approach would allow carers to complete their training in smaller, manageable modules, rather than overwhelming them with large, comprehensive courses. Each module would focus on a specific competency, making it easier for carers to track their progress and for the care manager to monitor compliance.
  2. Real-Time Progress Tracking: Another idea was to integrate real-time progress tracking into the LMS. This feature would provide instant updates on carers’ progress, allowing the care manager to quickly identify who was compliant and who needed further training. This idea was seen as a direct response to the lack of visibility in the current paper-based system.
  3. User-Friendly Interface: Given the varying levels of digital literacy among carers, there was a strong emphasis on designing a user-friendly interface. The brainstorming sessions highlighted the need for clear navigation, intuitive icons, and accessible language. Ideas included using visual cues like progress bars and checkmarks to guide users through the system.
  4. Gamification for Engagement: To increase engagement and motivation, the idea of incorporating gamification elements into the LMS was proposed. Features such as badges, leaderboards, and rewards for completing modules were suggested as ways to make the learning process more interactive and enjoyable for carers.
  5. Automated Reminders and Notifications: Automating reminders and notifications was identified as a key feature to ensure carers stayed on track with their training. Ideas included setting up notifications for pending tasks, upcoming deadlines, and feedback on completed assessments. This would reduce the burden on the care manager to manually follow up with each carer.

 

Exploring Technological Solutions

Once we had a list of potential ideas, I explored various technological solutions that could bring these ideas to life. This involved researching different tools and platforms that could be used to develop the LMS, with a focus on flexibility, scalability, and ease of use.

Flutter Flow as the Chosen Platform:

During this exploration, Flutter Flow emerged as an ideal platform for prototyping and developing the LMS. Flutter Flow is a no-code platform that allows for rapid prototyping and easy collaboration with stakeholders. Its drag-and-drop interface made it possible to quickly create functional prototypes that could be tested and refined based on user feedback.

Key reasons for choosing Flutter Flow included:

Speed of Development

Flutter Flow’s intuitive interface allowed for quick iteration on designs, making it possible to rapidly test and refine ideas.

Collaborative Features

The platform enabled real-time collaboration with stakeholders, ensuring that their feedback could be immediately incorporated into the design.

Scalability

Flutter Flow’s capabilities ensured that the LMS could be easily scaled up with additional features as needed, without requiring significant redevelopment.

Prioritising Ideas for Prototyping

With a wide range of ideas on the table, the next step was to prioritise them based on feasibility, impact, and user needs. I worked closely with the care manager and carers to assess which features would be most beneficial and achievable within the project’s timeline and budget.

 

Final Prioritised Features

Modular Learning System

This was selected as a core feature, as it directly addressed the need for manageable training modules that could be easily tracked.

Real-Time Progress Tracking

Implementing this feature was a high priority, as it was critical for improving visibility into carers’ compliance status.

User-Friendly Interface

Ensuring the LMS was accessible to all users was essential, so the design focused on simplicity and intuitive navigation.

Automated Reminders and Notifications

This feature was also prioritised, as it would reduce the workload on the care manager and help carers stay on track with their training.

Conclusion

The Ideate phase was instrumental in generating a wide range of creative solutions that addressed the core challenges identified during the Define phase. By involving stakeholders in the brainstorming process and exploring various technological options, we were able to identify and prioritise key features for the LMS. These ideas laid the foundation for the next phase, where we would bring these concepts to life through prototyping and testing. The use of Flutter Flow as a prototyping platform further facilitated the rapid development and refinement of these ideas, ensuring that the final product would meet the needs of Bleep 360 Care and its carers.

Prototype: Bringing Ideas to Life

The Prototype phase of the design thinking process is where abstract ideas and concepts begin to take tangible form. After brainstorming and ideating solutions for the Learning Management System (LMS) tailored for Bleep 360 Care, it was crucial to create prototypes that could be tested and refined based on user feedback. The goal of this phase was to translate the ideas generated into a functional, albeit preliminary, version of the final product that stakeholders could interact with and evaluate.

 

Choosing Flutter Flow for Prototyping

One of the first steps in the prototyping phase was selecting the right tool to bring the concepts to life. Flutter Flow was chosen as the primary platform for prototyping due to its unique features that support rapid development, ease of use and collaborative capabilities. Flutter Flow is a no-code platform, which meant that I could focus more on design and functionality rather than getting bogged down in coding.

 

Key Reasons for Choosing Flutter Flow

Speed of Development

Flutter Flow allows for quick iterations, enabling the development of multiple prototypes in a short amount of time.

Visual Development

The platform’s drag-and-drop interface made it easy to design visually appealing and functional interfaces without needing extensive programming knowledge.

Real-Time Collaboration

Flutter Flow supports real-time collaboration, which was crucial in incorporating feedback from stakeholders, including the regional care manager and carers, as they could see updates instantly.

Cross-Platform Compatibility

Prototypes created in Flutter Flow are inherently cross-platform, ensuring that the LMS would be accessible on both web and mobile devices.

 

Building the First Prototype

The first prototype focused on the core features identified during the Ideate phase. The goal was to create a basic, functional version of the LMS that included the most critical elements, such as the modular learning system, real-time progress tracking, and user-friendly interface.

 

Core Features of the First Prototype

Modular Learning Interface

The prototype featured a clear and intuitive layout, with distinct sections for each module. Users could easily navigate through the modules, which were designed to be self-contained learning units.

Progress Tracking Dashboard

A central dashboard was created to allow carers and the regional manager to view progress in real-time. The dashboard included visual indicators like progress bars and checkmarks, making it easy to see which modules were completed and which were pending.

Automated Notifications

Basic functionality for automated notifications was integrated, sending reminders
(emails & in-system notifications) for upcoming deadlines or incomplete modules.

 

Iterating on the Prototype

After the initial prototype was built, it was presented to the stakeholders, including the regional care manager and a group of carers who would be using the system. Their feedback was instrumental in refining the prototype. Based on their input, several iterations were made to improve usability and functionality.