The Context

A real product,built by students

Blueprint was the final project of the Jala University development degree. The students were not doing an exercise: they joined an existing product, with a backlog, a codebase and a company on the other side. The design had to be clear enough for people building their first real product.

60+

students mentored on the design

6

months, from redesign to implementation

3

new features: Dark Mode, Filters and Card View

The Product

Draw the process once,run it every day

Blueprint turns a company process, like hiring a candidate, into a workflow anyone on the team can follow. Each person sees only the steps and actions that belong to them.

Flow editor with hiring steps connected by actions and a step settings panel
01
Build the flow

Steps and actions on a canvas, with versions, required fields per step and permissions.

Publish step explaining why to publish the workflow template
02
Publish the template

Once published, the flow becomes a template the team can use to open new instances.

Application Tracking instance with the flow stepper, candidate data and comments
03
Move each case forward

Every instance shows where it is in the flow, its data, comments with mentions and the next possible actions.

The Brief

Improve what exists,add three features

The tool already worked. The three new features answer the same need: see the work, find the work, and use the tool for hours without tiring your eyes.

Feature 01

Card View

A board grouped by step, next to the list view, with one toggle between them. Each card shows the ID, the person, the role, the requester and the owner. Cards move between steps by dragging, and a column the user can't edit shows a lock and explains why instead of failing in silence.

Card view board by step, with a card being dragged into a locked column and a permission message
Feature 02

Filters

One panel with the fields that matter: workflow status, name, ID, step, role, requester, owner and dates. Each field opens its own condition, like people as removable chips or a date on a calendar. Active filters stay visible above the results, with a single Clear filters.

Filters panel with workflow status, requester chips and a date picker
Feature 02 · Empty state

No results is not a dead end

When a filter returns nothing, the screen says so in plain words, suggests trying another condition and offers the next action: create a new card.

Empty state for a filter with no cards, with active filters and a New Card button
Feature 03

Dark Mode

People spend the whole day inside Blueprint. Dark Mode lives in the account menu and covers every screen, including the status colors of each step, which keep the same meaning on both backgrounds.

Drag the handle to compare the two themes

Card view board in dark mode Card view board in light mode
Design Decisions

Designing beyondthe happy path

Students tend to build the screen that works. I designed the moments when something goes wrong too, so nobody had to invent them during implementation.

Unauthorized page with an illustration and two actions
No access, with a way out

The unauthorized page explains what happened and offers two paths: ask for permission or return to the dashboard.

Confirmation modal before deleting a comment
Confirm what can't be undone

Deleting a comment asks for confirmation first, because the history of a case is shared by the whole team.

New instance form with a required field highlighted
Errors next to the field

Required fields are marked where they are, at the moment they matter, and not in a message at the top of the form.

Users and groups screen in three columns
Groups people can manage

Users and groups in three columns: pick a group, see who is available and who is already in it, and move people with one click.

UI Kit

One set of components,two themes

Navigation, cards, lists, filters, dropdowns, toasts and statuses were organized as components. That made Dark Mode a matter of swapping colors, not redrawing screens, and gave the students one reference to build from.

Blueprint components in dark mode: sidebar, groups, card, filters, dropdown and toasts
Handoff and Mentoring

The design only countsonce it's built

I ran the handoff to the young developers and stayed with them through the implementation phase, so the new features made it into the product the way they were designed.

Documentation

Complete specs for each feature: states, behaviors and edge cases, written for people building their first product.

Training sessions

Sessions to walk through the design, explain the decisions behind it and answer questions before the code started.

Ongoing support

Continuous support during implementation, answering questions and reviewing what was built along the way.

Learnings

What teachingtaught me about design

A spec is a product too.

Whoever builds is the first user of the design. If the documentation is confusing, the feature will be too.

Error states are part of the scope.

What isn't designed gets improvised. Drawing the empty, locked and denied screens up front meant nobody had to guess.

Themes start in the components.

Organizing the interface as components is what lets one design work in two themes. Without it, Dark Mode would be a second product.

Explaining the why scales.

With 60+ people building, I couldn't review every screen. Teaching the reasoning behind each decision let the students make the right call on their own.

Good design for a team in training is design they can build.

Let's talk