Textbook to screen

Redesigning how Amplify's digital textbook experience aligns with its print counterpart
Scroll to Explore
Desktop monitor and two smartphones showing Enel's energy management software interface with charts and data.
Overview
Amplify's Teacher Pairing Screens (TPS) give teachers a digital presentation to use at the front of the classroom, replacing the projector setups many schools relied on before.

While students follow along in their Student Edition (SE) physical textbooks, the TPS mirrors that same content on-screen for the whole class, but with interactive elements layered in: where a student would normally write or draw in their textbook, the TPS gives the teacher a matching space to write or draw digitally, alongside tools like calculators, shapes, and color options.
Row of white Tesla energy storage units outdoors in snow under clear sky that power Enel's systems.
Duration
4 Months (Nov - Feb 2025)
Role
Lead UX/UI Designer
Client
Amplify Math

How might we

create a consistent learning experience between the SE and the TPS to enhance student understanding and eliminate confusion?

Original UI that features a table listing of ISO-NE grid service programs with details like zone, name, rates, months, start times, events, and duration.
1

Research

Overview

To understand how students and teachers actually experience the disconnect between the SE and TPS, I ran three parallel research efforts: classroom observations, teacher focus groups, and ongoing cross-functional syncs with Product and Curriculum.
Purple arrow zigzagging upward to the right symbolizing growth or increase.
Classroom 
Observational Studies
A black arrow pointing right
Observed students’ behaviors and workflow in their physical classroom
A black arrow pointing right
17 - 20 Students per Classroom
A black arrow pointing right
1 - 3 Teachers per Classroom
Three purple user icons representing a group of people with one in front and two behind.
3 Focus Group Interviews
A black arrow pointing right
Interviewed 2 - 4 teachers (Kindergarten, 4th, and 5th grade)
A black arrow pointing right
Asked each group a consistent set of questions, encouraging open responses
A black arrow pointing right
Compared and contrasted insights across the different grade levels and teaching contexts.
Purple hand icon with index finger touching a central circle connected to two outer circles.
Cross-functional 
Research Syncs
A black arrow pointing right
Held bi-weekly meetings with Product and Curriculum teams
A black arrow pointing right
Collectively discussed and shared insights from our research findings

Deep dive

Classroom
observational studies

The purpose was to understand how K-5 students and teachers in an Amplify deployed School District interact with the problems on the TPS as presented in the SE.
Orange icon of a chair and desk viewed from the front.
Simple orange icon of a desk with chair.
Orange icon of a desk with table and chair viewed from front.
Orange icon of a desk with a chair behind it.
Orange desk with a rounded backrest chair in a simple vector style.
Icon of an orange desk with a chair behind it.

6 Classrooms

Simple orange user profile icon with a circle head and rounded body silhouette.
Simple orange user profile icon with a circle head and half-circle body on a white background.
Simple orange user profile icon with a circle head and semicircle shoulders on white background.
Simple orange user profile icon with a circle head and half-circle shoulders.
Simple orange user profile icon with a circle head and half circle body on white background.
Orange generic user profile icon with a circle head and rounded shoulders.

17 - 20 Students per classroom

1 - 3 teachers per classroom

Stakeholders

We collaborated with teachers, school administrators, and specific Amplify administrators to gain a deeper understanding of the technical implementation, maintenance, and alignment of the TPS and SE with the educational needs of their students.

Process

A black arrow pointing right
Sat at the back of the classroom to maintain an unobtrusive presence
A black arrow pointing right
Observed student interactions with both the SE and TPS screens
A black arrow pointing right
Captured supporting photos, ensuring that student faces were excluded
Enel X company logo in purple on a transparent background.
Quotation marks

The current SE problems [on screen] are not helpful at all.
The students need to recognize what is happening through repetition.
They need to see exactly the SE on screen.

Teacher #6
2nd Grade Teacher
Teacher standing beside a screen showing a math word problem and subtraction solution in a classroom.
Example of Teacher Using SE PDF
Child in a classroom solving math problems on a digital board with students watching.
Example of SE Written on Screen

Design Principles

Before I start any project, I set a few design principles to keep myself on track, goals I return to throughout the process.
Establish a Clear Connection Between SE and TPS
We must ensure that students can seamlessly connect the SE content with the TPS. This alignment is crucial to prevent any hindrances in their learning process.

Establishing a clear connection between these platforms should be a fundamental aspect of the problem's overall design, ensuring a cohesive and supportive learning experience.
Maintain Consistency Across Platforms
It's vital to maintain consistency between the SE and TPS. This involves using uniform design elements, terminology, and content presentation, which will reduce cognitive load and build familiarity.

We must focus on patterns that support learning through repetition, enhancing understanding and educational outcomes for students and educators.
Enhance Visual Clarity and Accessibility
Prioritize visual clarity and accessibility in the design. Ensure clear typography, ample spacing, and distinct visual hierarchies to adhere to accessibility standards. This ensures that information is easily accessible and navigable for all users.

Enhancing visual clarity will help students and teachers quickly identify relevant content and focus on learning objectives without unnecessary distractions.
3

Design Adaptation

Accessibility

Since these colors would be projected at the front of the room, I ran an accessibility check to see if students in the back could actually read them.
A user journey of how a solution engineer operates grid services.
A user journey of how a solution engineer operates grid services.

Color Contrast Test by Pivotal Accessibility

Why this matters

These colors would be projected at the front of the classroom, not viewed up close on a screen. If students in the back row can't distinguish the text from the background, they lose the ability to follow along.

Process

A black arrow pointing right
Ran the textbook's foreground/background color pairing through a WCAG contrast checker
A black arrow pointing right
Result: 3.04:1, below the 4.5:1 minimum for regular text (AA), and well below the 7:1 enhanced standard (AAA)
A black arrow pointing right
The average elementary classroom is ~900 sq ft, which puts the back row about 20-25 feet from the front, well past the distance where a marginal contrast ratio is forgiving
A black arrow pointing right
Flagged the pairing as a barrier to legibility, especially for students seated farthest from the screen, and used this as evidence to push for higher-contrast color choices in the redesign

Compatibility

Our platform's native components couldn't recreate the layout the textbook required, so we used Polypad — an existing interactive canvas — to build custom screens that matched the textbook's problem structure exactly.
A user journey of how a solution engineer operates grid services.

TPS Platform

Constraints

A black arrow pointing right
Teacher-pairing screens (TPS) only supported emoticons
A black arrow pointing right
Emoticons needed manual checks across iOS, Android, and Windows for consistent rendering
A black arrow pointing right
SE (student edition) required custom icons to visually align, which standard components couldn't support
A user journey of how a solution engineer operates grid services.

Polypad User Interface

Solution

A black arrow pointing right
Found an underused Polypad feature, built by one of our engineers, that allowed custom icon imports
A black arrow pointing right
Originally built for shape interactives and games, not icon-based screens
A black arrow pointing right
Asked to repurpose it for our use case

Notes

After talking it through with the engineer, we got the green light to use Polypad for our solution.

It opened up new possibilities for future activities where we wanted the on-screen problems to visually echo the SE, and it reinforced how much is possible when cross-functional teams collaborate closely.
4

Prototype Development

First Prototype

After conducting our research, we narrowed our ideas into three design directions that best addressed the solution engineer’s workflow and comparison needs.
A user journey of how a solution engineer operates grid services.

Key Ideas

A small Amplify logo with a white capital letter A on a square orange background.
Applied a consistent background shape behind the darker problem number to maintain visual uniformity
Two arrow-shaped labels each with the number 2 in different blue styles on white backgrounds.
Amplify mini logo: A white capital letter A on orange background.
Used the same textbook icon next to the bold "Discuss" text to enhance clarity and reinforce brand recognition
Two speech bubbles: a white one with ellipsis and overlapping blue and green chat bubbles.

Internal Testing

With a working prototype, I brought it to the internal team for testing. Their feedback on screen ratios, padding, and text consistency pointed to a few key layout fixes before moving forward.
Avatar of a woman with brown hair, black glasses, and a red top on a blue circular background.
Illustration of a person with long brown hair wearing a dark blue shirt on a blue circle background.
Smiling woman avatar with long blonde hair wearing a pink top and white collar on blue background.
Enel X company logo in purple on a transparent background.
Two orange quotation marks, stylized with sharp diagonal edges on a black background.

How will this look in a 4:3 ratio?
Or a 1:1 ratio?

Avatar of a smiling person with long brown hair, round glasses, and a pink shirt.
Internal Team Member
Principal UX Designer

Stakeholders

A black arrow pointing right
5 Internal Design Team Members
Team Members had deep knowledge of the SE textbooks. Many were former teachers or had extensive experience interviewing teachers and students, while others had conducted classroom observations across various school districts.

Findings

checkmark
Consider varying screen layouts to maintain consistency
checkmark
Apply appropriate padding for a visually appealing design
checkmark
Ensure the text size within Polypad matches the existing text on our screens
Enel X company logo in purple on a transparent background.
A 4:3 ratio TPS screen showing a discussion prompt about volume: what is true if one figure has greater volume than another and about equal volumes?

Ratio 4:3 Layout

A 16:9 ratio TPS screen showing instructions to organize cubes for Problem 2 and discuss Problem 3.

Ratio 16:9 Layout

A 1:1 ratio TPS screen showing an activity that asks to discuss what information is needed to verify if 'judges do not like cows' is true.

Ratio 1:1 Layout

Resolving Text Consistency

To meet the finding that Polypad's text should match our existing screens, we tested formatting across the platform's three primary layout ratios.
A black arrow pointing right
Ratio 4:3 - Assessed padding and line length against denser problem statements
A black arrow pointing right
Ratio 16:9 - Tested wider viewports where padding needed to scale proportionally
A black arrow pointing right
Ratio 1:1 - Checked how shorter text blocks held up in the most compact layout
Testing across ratios confirmed a consistent formatting approach that held up regardless of screen shape.
5

Final Design

Design Correlation

With Polypad in place, we turned to the finer details, making sure numbers, icons, and text formatting matched the SE precisely.
6

Handoff

Design Library

I built a reference doc for the design team to keep problem-number icons, activity icons, and color values consistent with the SE across units, specifying exact icon sizing (1:1 grid) and RGB values for odd/even unit number colors.
A user journey of how a solution engineer operates grid services.

Design Templates

To support every use case across the curriculum, I built a set of approved templates so designers had a consistent starting point instead of designing each screen from zero.
A user journey of how a solution engineer operates grid services.

Design 
Specifications

To support every use case across the curriculum, I built a set of approved templates so designers had a consistent starting point instead of designing each screen from zero.
A user journey of how a solution engineer operates grid services.

1:1 Design Spec

A user journey of how a solution engineer operates grid services.

16:9 Design Spec

A user journey of how a solution engineer operates grid services.

16:9 Design Spec with a 1:1 Layout Inside

7

Post-Implementation

Business impact

Launch is only the beginning of the design process.
After release, we track user behavior, performance metrics, and feedback to validate decisions and uncover opportunities for iteration.
Increased Teacher Satisfaction 
& Engagement
By aligning screen designs with textbooks and adhering to accessibility standards, we anticipate improved teacher satisfaction and engagement, resulting in increased adoption and retention rates of our educational product.
Purple arrow zigzagging upward to the right symbolizing growth or increase.
Increased Trust
By actively listening to teachers and incorporating their feedback, along with engaging them in person to understand their preferences and critiques, we foresee building increased trust and goodwill, potentially leading to favorable recommendations, higher retention rates, and renewals.
Three purple user icons representing a group of people with one in front and two behind.