Case Study

Smoothwall's
Record Manager

Streamlining Electronic Incident Recording for Schools

Time Frame
Over a year, as part of a retainer with Smoothwall
Devices
Mobile, iPad, Desktop
My Role
UX Design, UI Design
Smoothwall Record Manager — all events view
Smoothwall Record Manager — mobile view

Company Background

Who is Smoothwall?

Smoothwall is a digital safety technology provider with over 200 employees. They were recently acquired for over 70 million pounds and pride themselves on providing solutions for digitally safeguarding students within schools.

The Product

What is Record Manager?

A SaaS solution which allows schools to electronically record child protection issues and safeguarding incidents without the need for traditional daybooks or CP files. It integrates with other Smoothwall products to seamlessly flag and track events pertaining to a child's wellbeing.

Problem

What needed to change?

Rebuild and redesign needed due to the product's legacy architecture leading to scalability issues, frequent data leaks and GDPR problems.

Accessibility was not considered and the platform lacked structure and hierarchy. This meant the information provided to users was overwhelming, making it hard to keep track of student data and gain an overall view of what was happening in the school.

Solution

Our approach

Look at user requirements with a fresh perspective. Update and simplify the Record Manager interface, stripping out unneeded elements and restructuring the platform, to allow school staff to easily track and manage their student's safeguarding data.

Align the user interface with new company guidelines to achieve a cohesive Smoothwall and Familyzone product appearance.

My Process

The blue circle represents the iteration phase that took place. As this project spanned across a large time frame we naturally discovered more about the users which helped us to iterate and improve our designs.

Design process: Discover and Design iteration loop leading to Deliver
01
  • Gather all existing data to understand users and what frustrations they have with the product
  • Understand the current problems with the Record Manager further through stakeholder interviews
02
  • Ideate designs through wireframes
  • Understand how to create a more intuitive interface through creating user flows
  • Iterate and ideate with rough designs
03
  • Create the final designs to hand over
  • Create Prototype to show existing and potential customers how the product would operate
  • Test with users to gain and implement feedback

Discover

Research Objectives

Uncover key areas for innovation and use data to help craft a compelling vision for the development roadmap.
Understand the key features and minimise feature creep to enable the delivery of a MVP that unlocks cashflow for the product.
Discover key themes of users complaints about the old system and avoid repeating the same mistakes again with the new design.
User persona: Rhiannon Manuel, Head Teacher, Non-DSL

DSL vs Non DSL

DSL's have an unrestricted view of data, they can see everything. Non DSL's are only allowed to see data relating to behaviour incidents and past concerns they have raised.

A DSL can be anyone (or sometimes a team of people) at the school. They typically hold a senior position and are well trusted.

Action DSL Non DSL
Can report both safeguarding concerns and behaviour incidents ✓ ✓
Can track and update all behaviour incidents and safeguarding concerns that have been raised at the school ✓ ✗
Can view all student profiles ✓ ✗
Can only see student data pertaining to behaviour incidents ✗ ✓
Can only track and update concerns they themselves have raised ✗ ✓

Recurring User Research Themes

We conducted user interviews and reviewed previous research data to identify the following key themes.

  1. Improving usability of the platform

    Despite guidance through help meetings and instructional videos, many staff members still struggle to navigate the platform, indicating the interface lacks the clarity and simplicity required for ease of use.

  2. Information organisation needed

    School staff are overwhelmed with information and need to focus on students who need their attention most. Effective filtering and data organisation would significantly alleviate their burden and help them better serve students.

  3. Breaking down data silos for improved student safeguarding

    Users want consolidated data to understand a student's background, but disconnected school systems make cross-department collaboration difficult. Coordinating teams can take weeks, so breaking down silos is crucial for better safeguarding outcomes.

  4. Effective tracking of behaviour incidents or safeguarding concerns

    Lack of visibility into case status, whether open, in progress, or closed, leaves staff feeling lost. A means to see all active cases at a glance would greatly improve situational awareness and enable prompt, effective responses to student needs.

Key User Research Insights

Many Spinning Plates

Teachers have so much going on at once and need to quickly track and respond to alerts to try and minimise the time between an alert being raised and actioned.

Give The Full Picture

Context is key for teachers looking at data about a students behaviour online, pulling in data from other Smoothwall platforms is useful in giving them an overview of a child's behaviour.

Device Usage Data

Desktop: 74.1%

Tablet: 2.5%

Mobile: 23.4%

Keep It Simple

Users often had low computer literacy and lacked data analytics skills. Simplifying information in the product would be key and also could be leveraged to make the system cheaper to run.

Design

Red Routes

Identifying and prioritising the most critical user flows in the Record Manager product.

Red routes matrix plotting Record Manager user flows by how often they are used (daily, weekly, monthly, rare) against how many people use them (few, some, many, everyone).

Grids

In order to create a responsive product that adapts to various devices, including desktop, tablet, and mobile, we followed the set of grids shown below (not to scale). Two distinct grids were employed, one for the content section and the other for navigation. Given that the Familyzone product library utilises a sidebar and a top navigation bar, it was essential to adhere to this particular style.

Responsive grid layouts for desktop (1440 x 800), tablet (744 x 1133) and mobile (375 x 886), each showing a content grid alongside a sidebar and top navigation bar.

Dashboard Design

One of the most important things for a user to be able to do on Record Manager is to raise and track concerns / incidents pertaining to children at school. It was interesting to see that as soon as you log in, the original dashboard did not have a space that allowed for a concern, incident or general note to be raised.

Comparison of two user flows for raising a concern. The old flow takes many steps through view latest concerns, searching for a student and available forms. The new flow is just dashboard, click report, concern form.

Challenges of the old dashboard

Annotated walkthrough of the old Safeguarding dashboard and New Concerns list, calling out weak visual hierarchy, inconsistent colour and sizing, unclear notifications, ambiguous calls to action and no read/unread or filtering states.

Snapshot of the platform before

A collage of the old platform screens: a student profile, the new safeguarding concern form, an open referrals list, a case chronology and a student search.
Mid-fidelity desktop wireframes for Record Manager: student search, student profile, incident and safeguarding forms with a body map, an update form and a report a concern overview.

Wireframes

After understanding the critical user flows, we proceeded to design our wireframes. Since some components were already established and needed to be adhered to for consistency with the overall product appearance, we began with mid-fidelity wireframes. We started with a desktop first approach considering the device usage data of the product.

Discover

Visual Design

Adding Smoothwall brand colours to the existing Familyzone colour palette gave Record Manager a Familyzone feel while still identifying it as a Smoothwall product.

We utilised the existing Familyzone component library to create a unified appearance across all products while creating or updating components as needed for use cases specific to Record Manager.

Visual design system for Record Manager: button styles (primary, secondary, ghost, disabled), Poppins headings and Roboto body type, informative, success, warning and error notifications, an icon set, the Smoothwall logo and the primary, secondary and text colour palette.

Dashboard: All Events

Record Manager dashboard, All Events tab: a Report a Concern or Incident panel above a table of events showing date submitted, student name, event type, category, event title, status and actions.

Dashboard: Assigned To Me

Record Manager dashboard, Assigned To Me tab: a table of students showing image, name, class, year, house, attendance, tags and actions to view or unassign.

Notification component

DSL users receive many notifications such as replies to messages they have sent regarding particular events, access requests, chronology updates plus safeguarding and behaviour incident alerts.

Our vision was to create a separate inbox which would handle all replies (later catering for a two way chat function) and have a traditional notification drop down alongside it where each notification would link the user to the source of the notification.

Due to developmental constraints this was not possible so I needed to adapt the notifications component to allow users to read replies received as well as the other notifications.

Annotated Record Manager notifications design: the bell icon with a red unread badge in the top navigation, and an open notifications panel showing pinned notifications, new items with a light blue background, reply notifications with a read more button, and access requests that can be approved, denied or pinned.

Referrals Page

Record Manager Referrals page: a searchable, filterable table of referrals showing date, referral type, student name, class, year, house, status and a details action.

Student Profile

Record Manager Student Profile: student details, assigned staff, safeguarding and behaviour statistics and a profile timeline, with a details-expanded view showing a full event record and body map.

Safeguard Form

Safeguarding Concern Form: fields for student names, concern title, date and time, category and details, with DSL notification, important information checkboxes and an optional body map.

Behaviour Incident Form

Behaviour Incident Form: fields for student names, event title, date and time, category and details, with DSL notification, staff to notify, important information checkboxes and an optional body map.

Mobile Designs

We adopted a desktop-first approach for the Record Manager product. However, mobile screens were also crucial to allow staff to check in remotely. User research revealed that urgent alerts, such as suicide alerts, can occur outside of school hours. To ensure teachers can access the product and perform all necessary tasks, mobile access is critical.

Tablet break points were also considered in order to create an effective responsive product despite the device usage only being 2.5% for tablet. Until now responsive design had not been considered.

Mobile designs for Record Manager: eight phone screens showing the student profile, profile timeline, an expanded event record, the dashboard with report actions and events list, the body map creation modal and the assigned events list.