Operating System Display

Building the operating system for new interactive panel display

Overview

How might we statement

Problem

Learning barriers: Discomfort using panel operating system leading to less usage.
Inconsistency: Different experiences with similar line of products.

Solution

Flexibility and comfort: Automation of firmware and flexibility to customize.
Product consistency: Familiarity with existing product experiences.
01/Research
Designing for new products
From selecting hardware materials for manufacturing to designing the operating system display. We designed a new product
What problem are we trying to solve?
Given Promethean’s desire to leverage as much functionality as possible from users’ connected laptops or Modular Compute devices, we set out to discover how comfortable teachers are with completing certain “utility” tasks on their primary work devices.​
Key Insights
In particular, we were looking to answer the following questions: ​​What are our customers expecting when using Promethean’s modular compute devices (MCD)? ​What do they like about the experience of using MCDs today, and what annoys them?​ Are there any pitfalls we need to look out for? ​What is the getting started process, and do they login to the operating system? ​How are they currently signing into/out of their apps? ​

Though teachers vary in their technology skills, they’re relatively familiar with basic OS functions​

Many of the tasks we presented them with are ones teachers do on a daily basis so they’re very comfortable with them​

Tasks that are “set it ad forget it” such as time settings, are less familiar to teachers and we can’t assume it would be easy for them​

If we’re relying on teachers to use the native OS to complete tasks, it shouldn’t be a task that is performed infrequently​

How might we "talk" with different operating systems for seamless use with our products?​
02/Design