Teachers see who needs support

A shared model clarified the interface

Each practice and assessment product had its own assignment data. I facilitated an object-modeling workshop with product and engineering partners to define the shared assignment object, its product-specific differences, and the information teachers needed in the classroom.

Every assignment had a title, type, assigned date, and due date. Some attributes varied by product, such as questions answered or pages read. The interface needed to surface the shared information first while retaining product context through labels and icons.

I designed for the product's technical constraints

I co-authored the requirements and owned the information architecture, interaction patterns, page content, states, prototypes, handoff, and launch planning.

The Angular page shell rendered content from a React app in an iframe, which constrained layout, filters, dialogs, and other interactions. The initial API returned aggregate completion counts only. With engineering and API owners, I added student IDs, completion time, and timeframe pre-filtering. That made student names visible in the interface while protecting page performance.

We deferred a fuller student-performance summary for a later release. Teachers wanted more detail, but adding it would have delayed the core improvement: helping teachers identify which assignments and students needed attention.