User Feedback & Usability¶
User feedback formed an important part of Toodle's development. Infinite Loopers gathered feedback to understand how users experienced the application, identify confusing workflows and improve usability.
The team used structured feedback forms, practical testing tasks, stakeholder discussions and in-app problem reports. Findings were reviewed and converted into improvements where necessary.
Feedback Objectives¶
The user feedback process focused on:
- Evaluating how easily users could navigate the application.
- Checking whether instructions, buttons and workflows were understandable.
- Identifying problems affecting common tutor-management activities.
- Assessing the application's usability on different devices.
- Collecting suggestions for improving the overall user experience.
Feedback complemented automated testing by highlighting difficulties that might not be detected through code-level tests.
Feedback Collection¶
The team gathered feedback through three main channels.
| Channel | Purpose |
|---|---|
| Structured user testing | Participants completed practical tasks and evaluated their experience |
| Stakeholder discussions | Feedback on project requirements, workflows and improvements |
| In-app problem reporting | Authenticated users reported issues encountered while using Toodle |
Structured User Testing¶
Participants were given tasks relating to the application's main workflows and were asked to provide feedback after interacting with the system.
Testing considered the experiences of students, tutors and academic staff.
Example workflows included:
- Signing in and navigating the application.
- Completing student onboarding.
- Exploring courses and tutoring opportunities.
- Applying to tutor a course.
- Managing availability and allocations.
- Using timesheets, excusals and volunteering features.
- Accessing role-specific dashboards and navigation.
The purpose was to observe how participants interacted with the application and identify areas requiring clarification or improvement.
User Roles¶
Toodle supports four application roles:
| Role | Main Workflows |
|---|---|
| Administrator | User management, staff access and platform administration |
| Lecturer | Course coordination, applications, allocations and approvals |
| Tutor | Availability, allocated work, timesheets, excusals and swaps |
| Student | Onboarding, course applications and volunteering |
Some earlier feedback materials referred to the academic staff role as Course Organiser. This reflects terminology used during development, before the responsibilities were separated into Administrator and Lecturer roles.
Historical feedback records retain their original terminology where necessary.
User Feedback Results¶
The collected feedback dataset contains 21 responses.
Participants evaluated aspects of Toodle's usability, including overall satisfaction, navigation and the clarity of the interface.
Survey Results¶
| Measure | Positive Responses | Percentage |
|---|---|---|
| Overall satisfaction rated 4 or 5 out of 5 | 17 of 21 | 81.0% |
| Navigation rated 4 or 5 out of 5 | 15 of 21 | 71.4% |
| Buttons and instructions rated clear or mostly clear | 20 of 21 | 95.2% |
The results indicate that most respondents had a positive experience, particularly regarding the clarity of buttons and instructions.
Navigation received comparatively lower ratings, highlighting an area where further refinement was valuable.
Device Usage¶
Of the 21 respondents, 11 primarily tested Toodle on a mobile phone.
This made mobile responsiveness an important consideration when interpreting user feedback.
The team considered findings relating to mobile navigation, notifications and layout consistency when improving the interface.
Key Feedback Themes¶
Feedback and issue tracking highlighted several areas for improvement.
| Area | Findings and Focus |
|---|---|
| Navigation | Making features easier to locate and understand |
| Onboarding | Improving guidance for users accessing Toodle for the first time |
| Tutor workflows | Clarifying allocations and session-swap processes |
| Mobile experience | Improving navigation, notifications and sidebar behaviour |
| Interface consistency | Addressing layout differences and dark-mode presentation |
| Reporting | Improving the usability of pages containing longer reports |
These findings helped the team prioritise usability improvements alongside feature development.
From Feedback to Improvements¶
Feedback was handled through a structured process:
- Collect: Receive observations through testing sessions, surveys, stakeholder discussions or in-app reports.
- Record: Document the issue or suggestion with relevant context.
- Prioritise: Consider its severity, impact and importance to the user workflow.
- Implement: Create or update development tasks and make the required changes.
- Verify: Test the affected functionality and check for regressions where practical.
- Close: Update the relevant tracker record when the work is considered completed.
The team used Trello for development planning and Jira for tracking identified issues.
This process connected user feedback to the team's adapted Scrum workflow.
Bug Tracking and Resolution¶
Issues identified through feedback and testing were recorded in Jira.
The Jira export dated 11 October 2026 contains 21 issues, all marked Done.
These records include bugs, usability improvements and development tasks. They should not be interpreted as 21 individual user-reported defects.
Examples of tracked areas included:
- Login and account-related problems.
- Onboarding guidance.
- Allocation and swap workflow clarity.
- Mobile navigation and notifications.
- Dark-mode consistency.
- Profile and reporting issues.
A Done status indicates recorded completion in Jira; it does not independently confirm that every issue was retested by its original reporter.
For details of the tracking process, see Bug Tracking.
In-App Problem Reporting¶
Toodle includes a Report a Problem feature that allows authenticated users to describe difficulties encountered while using the application.
Reports include information such as:
- The affected page or workflow.
- A description of the problem.
- Whether the issue prevented the user from completing a task.
These reports provide an additional feedback channel beyond scheduled testing sessions.
Reported issues can be reviewed and incorporated into the team's normal tracking and development process.
Supporting Evidence¶
The team's feedback evidence includes:
| Evidence | Description |
|---|---|
| User feedback survey | Anonymised dataset containing 21 responses |
| Jira issue export | Anonymised records of 21 tracked issues and their statuses as of 11 October 2026 |
| Trello board | Sprint planning and development tasks |
| Automated and manual testing | Verification of functionality and relevant improvements |
Survey responses and issue exports should be anonymised before being included in publicly accessible documentation.
Personal information, respondent usernames and identifying details should not be published unnecessarily.
Lessons Learned¶
User feedback helped the team understand that a feature can work correctly from a technical perspective while still being difficult to understand or navigate.
The feedback also reinforced the importance of testing different roles and devices, particularly where users follow different workflows.
By incorporating feedback into the development process, Infinite Loopers was able to identify usability concerns and refine Toodle beyond its initial implementation.
Summary¶
Toodle's user feedback process combined practical testing, structured surveys, stakeholder input and in-app reports.
The 21 survey responses provided insight into overall satisfaction, navigation, interface clarity and mobile usability.
Together with Jira issue tracking and ongoing testing, this feedback supported the team's efforts to make Toodle more understandable, consistent and practical for its intended users.