Case study product/purple-pen · The Purple Pen · 2020

Empowering teachers and students

I helped The Purple Pen flesh out a system that gives teachers and students a tool to create personal lessons based on authentic learning principles — from a year of spreadsheets and sketches to a high-fidelity prototype they could demo end to end.

Role
Design Lead
Timeline
2020
Team
Barry, the founder, and The Purple Pen advisory group
Stack
Style guide + pattern library · InVision prototypes
The Purple Pen on a laptop and a phone: the curriculum wizard's 'In this project, what matters more?' dial between Content Knowledge and Academic Skills, and the mobile login for The Curriculum Wizard.
FIG 01 The Purple Pen: the curriculum wizard on desktop and mobile.

The Purple Pen

A call from my high school teacher

This project started when my high school teacher contacted me to ask a couple of questions about my profession. It turned out he had a project that needed a lot of design work — and it couldn't have been one I believed in more. I'm a product of the Chicago Public Schools system myself, but nobody knew it better than Barry, who had taught in some of the best and worst schools across Chicago.

Barry and a group of supporters wanted to change the way children are taught by giving parents and teachers the ability to create their own lesson plans and learning criteria: aligned to the Common Core State Standards, but tailored to the needs of an individual learner. The guiding principle was to find the optimal education experience by balancing authentic learning with common standards and assessments.

The Purple Pen's guiding principles diagram: Authentic Performance Learning, project-, problem- and portfolio-based, inside a ring of local design and local control, inside a square of Common Core and other standards and standardized assessments, surrounded by Authentic Learning, Control and Results.
FIG 02 The guiding principles: authentic learning, balanced against common standards and assessments.

The kickoff

The Purple Pen group had been working on the product for over a year, developing their own assets and methods of documentation. There were even some fully articulated interface designs for a few of the application's key dashboards and page views. I began by talking with Barry about the problem they faced, the methods educators used today, and what the ideal process for an educator would look like. To help them, I realized I needed a higher-level view of the whole process before I could get a real grasp of the product.

Two of the team's original interface designs: a student activity page for developing a driving question, and a wizard curriculum design tool page asking what type of authentic learning you are designing.
FIG 03 Where the team was when I joined: a year of work and a few finished screens.

A year of thinking had gone into the product before a designer touched it. The first job wasn't to design anything. It was to understand it.

Getting caught up

The whole flow lived in spreadsheets

The only place the entire flow had been documented was a series of Excel sheets and text documents. Reading through them, and mapping them back to the screens that already existed, was how I built the high-level view I needed.

A collage of the spreadsheets that documented the product: a wizard navigation sheet listing every page by section, dashboard sheets for student and administrator, and rubric tables.
FIG 04 The product, as documented: spreadsheets and text files.

Splitting priorities

Three flows that held the whole product

After multiple rounds of feedback we were able to agree on three product flows that together encapsulated the entire product the team envisioned. Splitting the work that way gave every conversation a home and kept the wizard — by far the most complex piece — from swallowing everything else.

Three architecture diagrams side by side, version 1.0: the site map with sign up, sign in, account and project; the wizard's six curriculum sections and every step within them; and the teacher screens for account, project and help.
FIG 05 The architecture, v1.0: three flows, one product.

The wizard

A pattern library first, then every screen

A lot of the project's complexity was contained in the curriculum wizard: a long series of selections and options to customize your result. The Purple Pen team was ready to start building the product, so to give the initial screens some guidance I created a style guide and pattern library we could all reference and eventually add to.

An architecture sheet of the wizard's reading strategies: sixty strategies from A's and B's and 5W's Chart through Venn Diagram and Notecards, laid out in eight rows as a selectable sequence.
FIG 06 One corner of the wizard's complexity: sixty reading strategies a teacher can choose from.
The Purple Pen style guide in four sheets: logo and colour palette, typography, forms with radios and checkboxes, and buttons and icons including the pen-nib dial controls.
FIG 07 The style guide and pattern library everyone could reference and add to.

With the pattern library in place I was able to quickly redesign every screen they had originally created and begin working on new functionality. With the whole flow in high fidelity and ready for a prototype, I could start focusing on the complexity inside each step of the process.

Every wizard screen redesigned with the pattern library, arranged in columns by section: basics, curriculum non-cognitive academic skills, interstitial, overall authentic design, cognitive academic skills, content knowledge and the long wizard summary with its states.
FIG 08 Every screen, redesigned on the pattern library.
A content knowledge wizard step, The Types and Number of Sources, with a Conference Proceedings panel open for adding sources and choosing pre-, during- and post-reading strategies, above a list of other source categories.
FIG 09 One step, in detail: choosing the types and number of sources for a project.

Constant feedback loop

Prototype, share, test, adjust

As soon as I developed a new flow or a complex selection sequence, I shared the prototype on InVision so the whole team could test and approve the functionality.

The prototypes let us quickly test different controls and patterns against the same problem. I could diagnose issues before they happened, and make adjustments based on scenarios I hadn't addressed or planned for.

1 New flow or sequence
2 InVision prototype
3 Whole team tests
4 Adjust and approve
Six variations of the dial selection control used to set a value: student reading level, what matters more in this project, confidence with reading instruction, the critical and creative thinking hierarchy, and pre- and post-activity confidence.
FIG 10 The same control, six problems: prototypes let us test each one.

Opportune branding

The logo was every control

When I first began working with The Purple Pen I was told repeatedly how important the brand was, and how important it was that users were well aware of it. Early on, that had led the team to make every single control the logo symbol. Checkboxes, radios, even arrows: the logo was being heavily overused.

The original selection controls: pen-nib symbols used as selected and unselected radio buttons for choosing who determines the subject, and as back and next arrows.
FIG 11 The original selection controls: the logo as radio, and as arrow.
Animated: the Critical and Creative Thinking Hierarchy step, where a pen-nib dial rotates to point at a level from Decode and Comprehend up to Create and Apply.
FIG 12 Where the logo earned its spot: the pen nib as a dial for setting a value.

After some initial pushback from the advisory group, I was able to convince them there were better opportunities to use the logo, and that for accessibility's sake we should stick to standard controls. And thankfully I found the perfect opportunity to use the branding: a few selection controls used throughout the process to set a value.

The finished 'In this project, what matters more?' step: a pen-nib dial pointing between Content Knowledge on the left and Academic Skills on the right, numbered 0 to 7 each way, with a Next button.
FIG 13 The branded dial in the finished wizard.

Outcome

An application they could demo end to end

I helped The Purple Pen deliver an application they could fully demo and present — one that completely shows the new tool's ability to complete an entire lesson plan. The Purple Pen recently won an award for innovation from Reimagine Education, and is currently looking for investors.

Seven finished wizard screens: the project's local design team, prioritizing and selecting academic standards, determining the subject and topic, the critical and creative thinking hierarchy, what matters more, the types and number of sources, and the project's stages and deadlines.
FIG 14 The finished wizard: a complete lesson plan, step by step.

A project I believed in from the first phone call. The best part was watching a year of spreadsheets become something a teacher could pick up and use.