Open to roles in Bengaluru

Product & UX Designer Design Leader

Komal Patel: Clarity by design

I turn complex product journeys into clear,
human-centred experiences.

I bring hands-on eCommerce and product-customization experience, thoughtful
UX decisions, and collaborative design leadership.

Bengaluru

Komal Patel in a black blazer and round glasses, arms folded

Work

Selected work

Three projects exploring commerce, customization, and accessible learning.

NeonChamp

Custom neon shopping and customisation. Helping shoppers understand preview, size, colour, backboard, hardware and price within one clearer purchase journey.

Role
UI/UX Technical Leader
Status
Shipped
Redesigned NeonChamp customiser on desktop: numbered steps beside a live neon preview
NeonChamp home page on mobile

CanvasChamp Photo Book

Photo book creation and customisation. Giving shoppers confidence about size, cover, paper, layout and image quality before they pay.

Role
Concept direction and design decisions
Status
Concept proposal, not launched or tested
Photo Book concept editor on desktop with a layout applied to a spread
Photo Book concept on mobile showing a crop applied to a photo

EduSight

Accessible learning support. Helping teachers record progress, identify skill gaps and guide next steps for visually impaired children.

Role
Hackathon team anchor (V1), sole designer (V2)
Status
Hackathon concept, prototype not built
EduSight teacher dashboard on desktop showing which students need attention
EduSight on mobile

About me

A designer who brings clarity to complexity.

My path started in 2005, when a documentation role introduced me to website design. I taught myself HTML and CSS from software help documentation, and grew from web design into UX and design leadership.

Most of my work sits in eCommerce and product customisation: neon signs, photo books and personalised prints, where shoppers make many connected choices before they pay.

I stay hands-on in the screens while mentoring designers and working with project managers, developers and customer success teams through delivery.

About my journey

A personal introduction — coming soon.

Expertise and leadership

Hands-on design. Thoughtful leadership.

What I'm responsible for on a product team, and where you can see it in the work.

  1. 01

    eCommerce journeys and product customisation

    Product pages, landing pages and customisers where preview, options and price have to stay connected. I owned CanvasChamp design work for 9+ years, across desktop and mobile.

    Where to see it:

  2. 02

    Information architecture and interaction design

    Turning long, branching tasks into clear steps and states, so people always know where they are, what changed and what comes next.

  3. 03

    Responsive UI and accessible experiences

    Designing desktop and mobile as their own layouts, and treating accessibility as part of the design rather than a final check.

  4. 04

    Design reviews and implementation quality

    Reviewing hierarchy, states and consistency, preparing developer-ready designs, and checking the built UI against what we agreed.

    Where to see it:

    • CanvasChamp continuous releases
  5. 05

    Team mentoring and cross-functional collaboration

    Specific feedback in rounds, so designers learn the reasoning and not just the fix. Working with project managers, developers and customer success teams through delivery.

    Where to see it:

    • Remote design team at Commerce Pundit
  • A team of 11–12 designersLed and mentored during remote working, with reviews and feedback in rounds.
  • 9+ years on CanvasChampOwned the design work on a live personalised-print store through continuous releases.
  • Delivery alongside other teamsCollaborated with project managers, developers and customer success teams from brief to release.

How I work

An adaptable approach.

Projects differ, so the steps flex. These are the habits I come back to, not a fixed formula every project followed.

Understand the context

Start from the business ask and the people it affects, then restate it as a product problem the team can agree on.

Activities and outputs

  • Conversations with product, business and customer success
  • Reviewing the current flow and where people get stuck
  • Field observation when it is possible

From my work

EduSight began with classroom visits and conversations with teachers before any screens were drawn.

Structure the journey

Map the steps, decisions and states before designing screens, so the flow makes sense before it looks finished.

Activities and outputs

  • User flows and information architecture
  • Step order and dependencies
  • Edge cases, empty and error states

From my work

On NeonChamp, a staged customiser became one numbered flow beside a live preview and subtotal.

Explore and design

Explore a few directions quickly, then take the chosen one into detailed, responsive design.

Activities and outputs

  • Sketches and storyboards
  • Wireframes and high-fidelity UI for desktop and mobile
  • Clickable prototypes and reusable components

From my work

NeonChamp started from storyboard sketches. The Photo Book concept became a clickable set of screens with its own design system.

Collaborate and validate

Review options with the people who build, sell and support the product, and check decisions against the evidence available.

Activities and outputs

  • Design reviews in rounds
  • Critique sessions and feasibility checks with developers
  • Testing assumptions where research is available

From my work

EduSight went through two rounds of mentor critique. Usability testing with users is still to come, and the case study says so.

Support implementation

Stay with the work while it is built, so what ships matches what was agreed.

Activities and outputs

  • Developer-ready designs and specs
  • Accessibility specifications
  • UI quality reviews of the built product

From my work

On CanvasChamp I ran UI quality reviews through continuous releases.

Endorsement

Hardik SuranaCustomer Success ManagerCommerce Pundit

Having worked closely with Komal, I saw her bring structure to complex eCommerce requirements, align design decisions with business and development teams, and carry the experience through implementation. She combined strong UX judgment with dependable ownership.

Contact

Let’s build clearer product experiences.

I'm open to Senior Product Designer and Product Design Lead roles in Bengaluru, where I can shape complex journeys and help a design team grow. Email is the quickest way to reach me.

Direct details

Based in
India
Looking for
Open to senior product-design opportunities in Bengaluru

Email me

For a role, a project or a collaboration, email is the quickest way to reach me.

ctckomal@gmail.com

Email me

About me

Komal Patel seated at a desk, chin resting on her hand, with books and plants behind herSelf-taught, curious, and still learning. Good design brings clarity, meaning and accessibility to complex problems.

My design journey began in 2005 with a part-time documentation job that brought back a childhood wish to make things. I had no design degree, so I followed my curiosity. I was studying BCA after a commerce background and working on project-bidding documents to support my family. I didn't know Photoshop, Dreamweaver, HTML or CSS.

While helping my first mentor, Nagendra Mishra, improve the colours on website designs, I realised how much I enjoyed shaping what people see and use. I took three days of leave, taught myself HTML and CSS from software help documentation, went to an interview, and was hired as a junior web designer.

Education, family, career breaks and changing technology have all been part of the path. Each one made me more observant, more patient, and better at helping other people do their best work.

See my career path
  • Self-taught since 2005From documentation work to leading product design.
  • eCommerce & customisationHands-on product-customisation experience.

Career timeline

The path so far.

From documentation work to leading product design, one step at a time.

  1. 2005

    Finding design by accident

    Part-time project-bidding documentation while studying. Improving a website's colours for my first mentor showed me what I wanted to do.

    Part-time work

    While studying BCA

    2005

    Expertise

    • Documentation
    • Colour
    • Curiosity

    Contribution

    • Wrote project-bidding documents part-time
    • Helped my first mentor improve a website’s colours
  2. 2006

    Teaching myself the web

    No formal design education. I learned HTML and CSS from software help documentation, and took three days of leave to do it.

    Self-taught

    No formal design education

    2006

    Expertise

    • HTML
    • CSS
    • Web basics

    Contribution

    • Learned HTML and CSS from software help documentation
    • Took three days of leave to do it
  3. 2007

    First design role

    Hired at IndiaNIC Infotech as a Junior Web Designer, creating websites that went live. Trained in Yahoo Store development and applied those skills to eCommerce projects.

    IndiaNIC Infotech

    Junior Web Designer

    2007

    Expertise

    • Web design
    • HTML and CSS
    • Yahoo Store
    • eCommerce

    Contribution

    • Created websites that went live
    • Trained in Yahoo Store development and applied it to eCommerce projects
  4. 2010

    Designing for clients, start to finish

    At Communication Crafts I took client websites and interfaces from first concept through to production.

    Communication Crafts

    Senior Web Designer

    Jun 2010 – Jun 2013

    Expertise

    • Web design
    • Interface design
    • Client delivery

    Contribution

    • Delivered client website and interface design from concept through production
  5. 2013

    Responsive sites and visual systems

    At MetaTagg Solutions I turned business requirements into responsive websites and visual systems developers could build from.

    MetaTagg Solutions

    Senior Web Designer

    Jun 2013 – Mar 2016

    Expertise

    • Responsive design
    • Visual systems
    • Requirements to UI

    Contribution

    • Translated business requirements into responsive websites
    • Prepared implementation-ready visual systems for developers
  6. 2017

    Leading personalised-product journeys

    From February 2017 to August 2026 I led UI/UX on CanvasChamp at Commerce Pundit Technologies as UI/UX Technical Leader, Design Lead and Team Mentor. I mentored a 12-person design team and later directed the NeonChamp customiser redesign.

    Commerce Pundit Technologies

    UI/UX Technical Leader, Design Lead and Team Mentor

    Feb 2017 – Aug 2026

    Expertise

    • eCommerce UX
    • Product customisation
    • Design systems
    • Team leadership

    Contribution

    • Led UI/UX on CanvasChamp across desktop and mobile
    • Standardised reusable UX patterns, handoff and implementation QA
    • Mentored a 12-person design team, from freshers to seniors
    • Directed the NeonChamp customiser redesign
  7. Today

    Leading, and learning in the open

    In 2026 I anchored my team at Design Hackathon 9 with EduSight, built FitBite Desk with AI tools, and I’m getting ready for Hackathon 10. Next: a Product Design Lead role in Bengaluru.

    What I’m working on

    Hackathons and AI-assisted builds

    2026

    • Design Hackathon 9

      EduSight

      Anchored the team through field research and the V1 prototype, then designed V2 on my own.

      Read the case study
    • AI experiment

      FitBite Desk

      A small app that helps office workers plan and pack homemade lunches, designed and built with AI tools.

      View case study View live app (opens in a new tab)
    • Design Hackathon 10

      Upcoming

      My next hackathon project. Details coming soon.

    Leadership approach

    Close enough to the work to help others decide better.

    The goal is a team whose design judgement grows until it needs less correction from me.

    • Turn business asks into product problems

      Before screens, agree with product what we are solving, for whom, and what we won't change.

    • Review for hierarchy, states and consistency

      Specific feedback in rounds, so designers learn the reasoning, not just the fix.

    • AB

      Raise the decisions design can't make alone

      Like which backboard NeonChamp should recommend, or the final button label. I take them to product with options.

    • Build reusable patterns

      One option card, one way to warn, one way to confirm. Patterns save the team from solving the same problem twice.

    • Protect responsive quality

      Mobile gets its own pattern when the desktop one doesn't fit, rather than a squeezed copy.

    • Stay through implementation

      Developer handoff, a shared source of truth for state, and a review of the built UI with QA.

    Tools and purpose

    The right tool for each step.

    How I use AI

    AI helps me explore more directions and get to a testable draft sooner. I used it to produce the Figma screens for the Photo Book concept under my direction, and to synthesise EduSight field notes, which I kept separate from what teachers actually said.

    I decide what goes forward. I check the output against the problem, the brand and accessibility, and I'm accountable for the result.

    • FigmaUI, prototypes, design systems
    • FigJamFlows, mapping, workshops
    • PhotoshopImagery and retouching
    • IllustratorIcons and illustration
    • HTML and CSSFeasibility and handoff
    • JiraDelivery with the team
    • Claude, ChatGPTExploring and drafting
    • GeminiResearch support
    • NotebookLMSynthesising notes

    Beyond design

    What keeps me curious and calm.

    • Macramé and Nest of Macrame

      I make macramé pieces through my small brand, Nest of Macrame. Knotting teaches patience, attention to detail, and how small parts build something strong.

    • Learning, reading and AI

      Reading and trying new tools keeps me open to better ways of working, and keeps me asking where AI helps and where human judgement matters most.

    • Meditation and gratitude

      A daily practice that helps me stay calm, listen without judgement, and design with care for how people feel.

    I create with my hands, learn with curiosity, and design with gratitude.

    Résumé

    Komal Patel, résumé. Komal Patel in a black blazer and round glassesSenior Product & UX Designer and UI/UX Technical Leader, focused on eCommerce and product customisation.

    I work across responsive design, accessibility and design leadership, from product pages and customisation flows to developer-ready designs and UI quality reviews.

    Based in India, looking for roles in Bengaluru. The full résumé is below, or open the PDF version.

    • Design lead & mentorMentored a 12-person design team at CanvasChamp.
    • Open to roles in BengaluruSenior Product Designer and Design Lead roles.

    CanvasChamp

    Feb 2017 – Aug 2026

    UI/UX Technical Leader, Design Lead and Team Mentor · Commerce Pundit Technologies

    Led UI/UX on a live personalised-print store: product pages, landing pages and customisation flows across desktop and mobile. Mentored a 12-person design team, prepared developer-ready designs and ran UI quality reviews through continuous releases.

    NeonChamp customiser redesign

    Shipped

    UI/UX Technical Leader · design direction and review

    Set the direction that turned a staged customiser into one numbered flow beside a live preview and subtotal. Guided the designer and worked with product, engineering and QA through delivery.

    CanvasChamp Photo Book concept

    Nov 2026

    Concept direction and design decisions

    A clickable 24-screen concept and design system for the Photo Book journey, prepared for the client to consider. Not launched or tested.

    EduSight

    Jul – Nov 2026

    Team anchor (V1 hackathon), sole designer (V2)

    Field research with blind teachers, a hackathon prototype, then a V2 product design with a design system, 64 prototype screens and accessibility specifications. Not yet built or usability-tested.

    MetaTagg Solutions

    Jun 2013 – Mar 2016

    Senior Web Designer

    Translated business requirements into responsive websites and implementation-ready visual systems.

    Communication Crafts

    Jun 2010 – Jun 2013

    Senior Web Designer

    Delivered client website and interface design from concept through production.

    IndiaNIC Infotech

    2007

    Junior Web Designer

    Created websites that went live. Trained in Yahoo Store development and applied those skills to eCommerce projects. Before this, I taught myself HTML and CSS in 2006.

    Back to work

    Design collection · eCommerce

    eCommerce Pilot Themes 18 storefronts

    Eighteen storefronts, each with its original homepage preserved and a complete shopping journey designed to match: product listing, product detail, cart, checkout and order success. Desktop 1920 and mobile 390, connected as clickable Figma prototypes.

    • Visual design
    • Responsive UI
    • Prototyping
    • Figma prototypes
    Open the prototype collection (opens Figma in a new tab)
    • 18themes
    • 9desktop screens per theme
    • 3mobile screens per theme
    • 36clickable prototypes
    Cover of the eCommerce Design Collection in Figma: title, theme index and a collage of six storefronts

    What I did

    The homepages set each brand's look. My job was to carry that look through every step a shopper takes, so a buyer never feels they've left the store.

    • Kept each brand intact

      Every theme keeps its original homepage. Type, colour, imagery and buttons on the new pages follow it.

    • Designed the full journey

      Product listing, product detail, cart, checkout and order success, for desktop at 1920 and mobile at 390.

    • Made it clickable

      Each theme has a desktop and a mobile prototype, 36 in all, so the flow can be walked through end to end.

    One journey, six steps

    Shown here with Theme 03, Pilot Beauty. Every theme follows the same path.

    1. Pilot Beauty homepage page, desktop

      Homepage

    2. Pilot Beauty product listing page, desktop

      Product listing

    3. Pilot Beauty product detail page, desktop

      Product detail

    4. Pilot Beauty cart page, desktop

      Cart

    5. Pilot Beauty checkout page, desktop

      Checkout

    6. Pilot Beauty order success page, desktop

      Order success

    All 18 themes

    Desktop and mobile homepage for each storefront.

    • Pilot Home Decor theme, desktop and mobile homepage
      01

      Pilot Home Decor

    • Pilot Flower Shop theme, desktop and mobile homepage
      02

      Pilot Flower Shop

    • Pilot Beauty theme, desktop and mobile homepage
      03

      Pilot Beauty

    • Pilot Bakery theme, desktop and mobile homepage
      04

      Pilot Bakery

    • Pilot Electronics theme, desktop and mobile homepage
      05

      Pilot Electronics

    • Pilot Furniture Shop theme, desktop and mobile homepage
      06

      Pilot Furniture Shop

    • Pilot Fashion Shop theme, desktop and mobile homepage
      07

      Pilot Fashion Shop

    • Pilot Food Shop theme, desktop and mobile homepage
      08

      Pilot Food Shop

    • Pilot Leather Bag Shop theme, desktop and mobile homepage
      09

      Pilot Leather Bag Shop

    • Pilot Kids Shop theme, desktop and mobile homepage
      10

      Pilot Kids Shop

    • Pilot Bookstore theme, desktop and mobile homepage
      11

      Pilot Bookstore

    • Pilot Fashion Store theme, desktop and mobile homepage
      12

      Pilot Fashion Store

    • Pilot Wedding Store theme, desktop and mobile homepage
      13

      Pilot Wedding Store

    • Pilot Wedding Store 2 theme, desktop and mobile homepage
      14

      Pilot Wedding Store 2

    • Pilot Sport Store theme, desktop and mobile homepage
      15

      Pilot Sport Store

    • Pilot Sunglass Store theme, desktop and mobile homepage
      16

      Pilot Sunglass Store

    • Pilot Furniture Store theme, desktop and mobile homepage
      17

      Pilot Furniture Store

    • Pilot Shoes Studio theme, desktop and mobile homepage
      18

      Pilot Shoes Studio

    Walk through the prototypes

    The Figma file links every theme to its desktop and mobile prototype.

    Open in Figma (opens in a new tab)
    Back to selected work

    Independent product experiment · AI-assisted

    FitBite Desk

    Turning healthy lunch intentions into a repeatable weekday routine.

    Role
    Product Designer and AI-Assisted Builder
    Project
    Independent, built with AI tools
    Product
    Responsive web app
    Status
    Live

    Overview

    A small daily problem, designed as one routine.

    FitBite Desk is an independent, AI-assisted product experiment: a meal-planning and habit-organisation web app for busy office workers who want to carry homemade lunches more consistently.

    The problem

    Packing lunch looks simple, but the decision is spread across planning, evening preparation and morning packing. When those moments don’t connect, good intentions fall back to buying lunch at work.

    My contribution

    I defined the problem, the scope and the Plan → Prepare → Pack model, wrote and reviewed the product language, and used AI tools to build and refine a responsive product.

    What was delivered

    A live responsive product: a focused public proposition, the weekday routine, a landing and sign-up journey, account entry, and clear non-medical boundaries.

    Evidence boundary. No formal user research, production analytics or outcome metrics are available yet, and none are claimed here. The audience, friction points and behaviour described below are design hypotheses.

    Product framing

    Three moments, one outcome.

    Deciding what to carry, preparing it in the evening and packing it in the morning happen at different times. Each one can break the routine on its own.

    Everyday friction

    • Deciding what to carry before groceries and prep are sorted.
    • Fitting chopping, cooking and portioning into end-of-day fatigue.
    • Remembering the meal, dressing, cutlery and supporting items in the morning.
    • Detailed tracking adds more to think about, not less.

    Scope decisions

    • Keep a focused proposition instead of drifting into a feature-heavy planner.
    • Focus on the next practical action, not calorie counting or detailed health tracking.
    • Leave out clinical guidance and medical outcomes, and say so clearly.

    Design hypotheses Not yet validated

    1. One outcome spans three moments.Connect planning, prep and packing through one model with short actions.
    2. Preparation reduces morning pressure.Move effort to the evening and make tomorrow’s task visible.
    3. Memory needs external support.Make the final packing check a visible list.
    4. More tracking isn’t always more support.Keep the experience concise, supportive and non-judgemental.

    A routine is easier to repeat when the interface does not make the user reconstruct it every time.

    Core journey

    Plan → Prepare → Pack.

    Each stage has one job, a likely point of friction and a short design response.

    1. 01

      Plan

      Task
      Decide what to carry on office days.
      Friction
      The choice has to happen before groceries and prep.
      Design response
      Office-friendly meal selection, simple planning and a link to the grocery list.
    2. 02

      Prepare

      Task
      Reduce the next morning’s workload.
      Friction
      Evening prep competes with end-of-day fatigue.
      Design response
      A short evening checklist of chop, cook and portion tasks, sized to the time available.
    3. 03

      Pack

      Task
      Leave home with everything.
      Friction
      One missing item can undo a prepared meal.
      Design response
      A short morning list that keeps the meal, dressing, cutlery and supporting items visible.

    Primary flow: understand the routine → choose to start → sign in or create an account → enter the product.

    Key design decisions

    How the design answers the problem.

    Decision 01

    Make the next action obvious

    One model, Plan → Prepare → Pack, repeated in the same words from the landing page through sign-in. Navigation stays minimal and calls to action stay short, so the architecture is no bigger than the problem.

    Decision 02

    Calm by design, not another tracker

    Short lists, everyday portion cues and supportive language take the place of measuring, logging and guilt-driven progress.

    Decision 03

    Useful without pretending to be medical

    The product helps people plan, prepare and pack homemade meals. It does not diagnose or treat conditions, give personalised medical advice or prescribe. “Mindful” labels are only food preferences people choose, and portion cues are everyday, not clinical.

    Decision 04

    Design for preparation, not motivation

    Motivation can’t make up for missing ingredients or unfinished prep, so the product points effort to the evening before. The closing message says exactly when the routine starts.

    Responsive experience

    One journey, every screen size.

    • The landing page moves from two columns on desktop to one reading sequence on mobile.
    • Primary actions stack on narrow screens and stay large enough to tap.
    • The weekday loop keeps its order and labels with no sideways scrolling.

    Shown: the public landing experience. Signed-in screens are not shown here, and their responsive review is still to do.

    Ownership and AI workflow

    AI sped up the build. The product decisions stayed mine.

    This was an independent project: no separate engineering team and no team to manage. I used Lovable and other AI tools for exploration and implementation, and reviewed everything that shipped.

    1. Frame

      Defined the problem and scope, set the three-stage model, decided what not to build and set the non-medical boundary.

      I decided

    2. Explore

      Compared content structures, generated and edited alternatives, refined the UX copy and looked for edge cases.

      AI supported, I edited

    3. Build

      Used Lovable to move from direction to a responsive implementation.

      AI supported execution

    4. Review

      Owned hierarchy and UX decisions, reviewed wording and health boundaries, checked accessibility and visual quality, and made the final priority calls.

      I decided

    5. Ship

      Published a live, usable product experiment.

      Delivered

    Responsible design and validation

    What was checked, and what still needs testing.

    Checked on the landing page

    • Semantic headings and clear section labels
    • Visible focus states and generous touch targets
    • Strong green-on-cream contrast
    • Mobile reflow with no sideways scrolling

    Still to do

    • Full WCAG 2.2 AA audit
    • 200% zoom review
    • Validation of the signed-in flow

    Questions for real users

    • Do people understand Plan → Prepare → Pack without explanation?
    • Which stage breaks most often?
    • Does the evening checklist reduce morning effort?
    • Do the non-medical labels feel clear and trustworthy?
    • Which routine cues support repeat use without being intrusive?

    Outcome and next steps

    Shipped, and ready to be tested.

    Delivered and live

    • A focused public proposition
    • The Plan → Prepare → Pack model
    • Landing and sign-up journey
    • Account entry and authentication
    • Clear non-medical boundaries
    • A live responsive implementation

    These are shipped elements, not claims about adoption, retention, behaviour change or health outcomes.

    Next

    • Test the routine with office workers on mobile, including the signed-in flow
    • Run the full accessibility audit
    • Measure repeat use once analytics are in place

    What it taught me

    • Saying no protects the one behaviour a narrow product exists for.
    • Product copy is interaction design when it explains what happens and when.
    • Clear boundaries build trust in health-adjacent products.

    Next project

    NeonChamp

    A staged neon-sign customiser, redesigned into one flow with the price in view.

    Previous: EduSight

    NeonChamp Case Study

    01 · Product design case study

    NeonChamp

    From a custom sign idea to checkout, without the guesswork

    I led the redesign of NeonChamp's sign customizer. It turned a staged, one-panel-at-a-time tool into a single flow where customers see their sign, their choices and the price together.

    Domain
    eCommerce: made-to-order LED neon signs
    My role
    Design direction, UX/UI review and designer guidance
    Platforms
    Desktop and mobile web
    Tools
    Figma

    Outcome: a clearer customizer, cart and checkout, designed and reviewed through delivery. Section 08 sets out what to validate next.

    02 · Problem

    Connected choices, shown one at a time

    A custom neon sign is a chain of connected decisions. Size changes the price, and the power adapter depends on the customer's country. Customers need to see each choice's effect before they commit.

    The legacy customizer showed those decisions as separate stages. Customers saw one panel at a time, used arrows to move on, and never saw their whole configuration together.

    Legacy customizer, one stage open. The size list fills the panel while every other choice waits behind the rail.Screenshot of the legacy tool from the project files (no Figma frame)

    So…How do we make a complex configuration easy to follow without removing the rules customers must complete?

    The question I framed for the team

    03 · History

    Where the experience started

    The legacy tool had a white workspace, a vertical rail of six stages and a room preview in the middle. Price and Add to Cart sat in the top bar, away from the options that changed them.

    1. Select Product
    2. Create Your Own
    3. Color
    4. Back Board
    5. Power Adapter
    6. Hardware Options

    Customers reached it from homepage buttons, header links and category pages, which embed the same customizer.

    The whole legacy workspace. Stages on the left, preview in the centre, price and action in the top-right corner.Screenshot of the legacy tool from the project files (no Figma frame)

    04 · Geography

    Who it serves, and where

    The product structure points to four intended groups. These are segments, not research participants.

    Word-first

    People who start with a name, phrase or slogan.

    Logo or artwork-first

    People who arrive with a file they want turned into a sign.

    Business buyers

    People browsing categories for signage ideas.

    International

    Customers who need the right adapter for their country.

    The power step shows this geography directly

    USA / Canada120VUK / Ireland230VEurope230VAustralia / NZ230VJapan100VOthersRegion not listed

    These segments come from the product structure and site content. No research participants are documented for this project.

    05 · Physics

    Reconstructed from documented screens

    How choices move through the journey

    Four documented screens, one path. Each decision changes what the customer sees, pays and does next.

    1. 1Discovery

      Homepage, menu or category page. Three entry buttons match three ways to start.

    2. 2Customization

      Text or upload, then numbered choices beside a live preview and subtotal.

    3. 3Cart

      Each item lists its configuration, with delivery windows on shipping.

    4. 4Checkout

      Four numbered steps, with the order summary always in view.

    ChoiceShown in the static designsIntended live behavior
    Text and fontThe sign appears in the room with its width and heightThe preview redraws as the customer types
    SizeCards show dimensions and price, plus a custom size inputThe dimensions and subtotal update
    ColorNamed swatches and a Color Ring linkThe sign glows in the chosen color
    BackboardCards show Free or an added priceThe subtotal updates
    Power adapterRegion and voltage, with no priceThe plug type is set for the order
    Hardware, waterproofFree or a price, with info iconsThe subtotal updates
    ActionThe subtotal sits beside the main buttonAdds the configured sign to the cart

    06 · Chemistry

    Answering "will it look right, and what will it cost?"

    A made-to-order sign is a bigger commitment than a stock item, so I pushed for responses that remove doubt at the moment of choice.

    See it in place

    A room preview with an on/off switch, dimension lines and different room backgrounds.

    See the cost

    Prices on every option card, Free labels on included items, and the subtotal next to the button.

    Check before paying

    A Show Details link on each cart item, delivery windows on shipping options, and info icons on fees.

    Hypothesis  These changes may reduce hesitation and surprise at checkout. No research on customer feelings was done, so this needs testing.

    07 · Biology

    One decision pattern, learned once

    The redesign uses one option card for sign type, size, backboard, adapter and hardware: an image, a label, a price or Free, and a selected state with a border and a checkmark. Learn it once, and every later step works the same way.

    Checkout repeats the customizer's numbered logic in four steps.

    1. Login
    2. Shipping & Billing Address
    3. Shipping Method
    4. Payment Method

    These patterns appear in the interface. No customer habits or workarounds were observed.

    The same card, step 6. Icon, label, value and a clear selected state, exactly as in sizes and backboards.Figma: NCU-3604, 3rd version, full flow (2101:287343)

    08 · Mathematics

    Evidence available, and what to measure next

    What exists today, and what I'd measure next.

    Available

    • Legacy screenshots
    • Final Figma frames
    • Project notes
    • A reconstructed attention map

    Proposed metrics

    Path start rateText path versus upload path
    Step drop-offWhich step loses the most people
    Customizer to cartWhether subtotal and button lead to action
    Cart edits, removalsMistakes found only after configuring
    Upload errorsArtwork files that fail or need replacing
    Cart to orderWhether fees and delivery hold up
    Hypothesis  Reconstructed attention map, not measured analytics. It suggests that size, color and backboard need the clearest feedback.

    09 · Design Engineering

    How the design evolved and shipped

    The Figma file documents three stages. Each is shown on its own, not merged into one flow.

    1. Before

      Legacy tool

      Six stages behind a rail, one panel at a time.

    2. NCU-3604

      New tool, 3rd version

      Text and upload tabs, numbered steps beside the preview.Figma: 2101:286773, 2101:287065, 2101:287343

    3. NCU-4775

      Enhancement round

      Builds on the same numbered structure.Figma: NCU-4775 (Creative) New Tool Enhancements NC USA (2101:289591)

    My contribution

    I set the direction and reviewed key screens at each breakpoint. I guided the designer through rounds of feedback on hierarchy, selected states and consistency. With product, I raised the decisions design couldn't make alone, such as which backboard to recommend and the final button label.

    Team execution

    Developers built the preview, pricing and state handling. We agreed that preview, subtotal and cart come from one configuration. QA tested both paths, and I reviewed the built UI with them.

    A storyboard made to explain the flow

    Reconstructed

    The storyboard sketch and the requirements brief in my files were reconstructed for this case study. They are not original discovery work. No usability testing is documented.

    Reconstructed  Storyboard made for this case study. It is not an original project sketch.

    10 · STAR

    The project in four lines

    Situation

    NeonChamp's customizer split connected choices across separate stages, with price and action away from the decisions.

    Task

    Lead the design direction to make configuration clear without dropping any product rules, across desktop and mobile.

    Action

    I set the direction: separate intents, one numbered flow beside the preview, priced visual options and a subtotal tied to the action. I guided the designer and worked with product, engineering and QA through delivery.

    Result

    A clearer customizer, cart and checkout. I defined the funnel metrics to validate it.

    11 · Before and After

    The customizer, decision by decision

    The same tasks, old and new, at a readable scale. What changed, why, and what it cost.

    Text path NCU-3604, 3rd version (2101:286773) Full flow NCU-3604, 3rd version (2101:287343) Two separate Figma variants, labeled on every screen.

    Before · Legacy tool

    1. Stage railSix stages; only one is open.
    2. One panel at a timeEarlier choices disappear.
    3. Arrows to move onNext and previous sit on the preview.
    4. Price and Add to CartIn the top bar, away from the options.

    After · Redesign Text path

    1. PreviewThe sign in a room, with dimensions and an on/off switch.
    2. EntryText and Upload are separate tabs from the start.
    3. ConfigurationNumbered steps in one scrolling panel.
    4. ColorSwatches inline, with a Color Ring link.
    5. PriceShown over the preview as choices change.
    6. Next actionSubtotal fixed beside the main button.

    Task 1Preview

    Before: large, but apart from the controls, and moved with arrows.

    After: beside the steps, with on/off, dimensions and room options.

    Trade-off: takes half the desktop width.

    Before
    After Text path

    Task 2Configuration

    Before: one stage at a time, with upload and ready-made signs mixed into Select Product.

    After: Text and Upload tabs, then one numbered, scrolling panel.

    Trade-off: a long panel, so mobile needs its own pattern, and switching tabs needs a rule for incompatible input.

    Before
    After Text path
    Upload tab: view the upload variantFigma: NCU-3604, 3rd version (2101:287065)

    Task 3Size

    Before: a text list of presets.

    After: image cards by shape with dimensions and price, plus custom size.

    Trade-off: more imagery to load.

    Before
    After Full flow

    Task 4Color

    Before: its own stage, with a grid of bulb icons.

    After: a row of named swatches inside the same panel, with a Color Ring link.

    Trade-off: small swatches rely on names on hover for clarity.

    Before
    After Full flow

    Task 5Backing, power and hardware

    Before: three separate stages.

    After: cards in the same panel, labeled with a price, Free or a voltage.

    Trade-off: the "Recommend" tag needs a business rule.

    Before
    After Full flow

    Task 6Price and next action

    Before: price and Add to Cart in the top bar.

    After: a subtotal bar fixed to the main button.

    Open question: the button label differs between variants, Create Neon Sign in the text path and Add to Cart in the full flow.

    Before
    After Text path

    12 · Final Screens

    The finished journey, desktop and mobile

    From the homepage to payment. Select any screen to see it in full.

    Homepage and categories

    Homepage. Three entry buttons match the three ways customers start, so the first click already sorts intent.Figma: NCU-4497 Homepage Changes _Updated (2101:14921)
    Mobile. One primary action, Create Neon Sign, leads the stack.
    Navigation. Creation routes come first, and the mega menu groups browsing by category and occasion.Figma: NCU-4433 Header - Desktop - 1920 (2101:40039)
    Logo signs. The customizer sits at the top, so browsers can start designing without leaving the page.Figma: NCU-3949 Logo Neon Signs - updated (2101:230880)
    Business. The same embedded tool, framed for business buyers.Figma: NCU-4333 Neon Signs for Business
    Letters and numbers. The preview adapts to a single character.Figma: NCU-4492 Neon Letters Numbers

    Cart and checkout across devices

    On desktop the order summary sits beside every step. On mobile it moves below the form, and a sticky bar keeps the total next to the step's action, so the customer always sees what they are paying and what comes next.

    Cart. Show Details lists each configured option; shipping options state their delivery windows.Figma: Shopping Cart (2101:293470)
    Mobile cart. A single column, with totals and the checkout button kept together.Figma: iPhone 13 & 14 - 14 (2101:295308)
    Checkout. Four numbered steps, with the full order summary always beside them.Figma: Shopping Cart series (2101:294004 to 2101:295058)
    Mobile login. Summary below the form, total and action in a sticky bar.Figma: iPhone 13 & 14 - 7
    Payment. Each option explains what happens next before the customer commits.
    Mobile payment. The final action sits in the same place as every earlier step.Figma: iPhone 13 & 14 - 13

    Final screens · Gallery

    Screenshot

    Next project

    CanvasChamp Photo Book

    A concept for a calmer Photo Book journey, built on nine years of shipped work.

    CanvasChamp Photo Book Case Study

    Komal Patel · UI/UX case study

    From a favourite photo to a book you trust.

    I helped shape CanvasChamp, a live personalized-print store, from Feb 2017–Aug 2026. This case study pairs that shipped work with a new concept for a calmer Photo Book journey.

    Shipped · live on CanvasChampConcept · not launched or tested
    Live site, Nov 2026
    Live CanvasChamp homepage, Nov 2026, with promo slider and Create your canvas panel
    Concept homepage on desktop with full-width hero, quick-order panel and product grid
    Concept homepage on mobile with the offer copy above the photo book
    Concept homepage, desktop and mobile
    01Hero

    Shipped platform. New concept.

    Shipped CanvasChamp work
    Photo Book concept
    Type
    Live eCommerce platform
    Concept prototype, to be offered to the CanvasChamp client
    Role
    UI/UX Technical Leader, Design Lead and Team Mentor, Commerce Pundit Technologies
    Concept direction and design decisions. Figma screens produced with AI assistance under my direction
    Dates
    Feb 2017–Aug 2026
    Nov 2026
    Team
    Mentored a 12-person design team; worked with 5 designers, frontend, development, QA, PMs and CSM
    Solo, AI-assisted
    Scope
    Photo printing and personalized products, desktop and mobile
    Photo Books, homepage to add-to-cart, desktop and mobile
    Tools
    Figma, Photoshop, Jira
    Figma, Claude, ChatGPT
    On the live platform

    I led design across product pages, landing pages and customization flows, and mentored the team through continuous releases.

    In the concept

    A clickable 24-screen Photo Book prototype with its own design system, built to give shoppers confidence before they pay. Usability testing is the next step.

    02Problem context

    A personal memory meets a run of technical choices.

    People arrive with a holiday, a baby, a wedding. Then they face size, cover, paper, layout and image quality. Today's Photo Book tool makes those choices harder than they need to be.

    1. One page at a timeHard to see how facing pages work together.
    2. Price in a dropdownThe breakdown sits in the header, out of sight.
    3. Layouts can wipe a pageSee the warning on the right.
    4. Crop is zoom and rotate onlyLittle control over what stays in frame.
    5. No Photo Books listingShoppers can't compare formats first.
    Live Photo Book tool with a warning that changing the layout will lose the page design
    Live tool, Nov 2026Changing a layout warns that your page design will be lost.
    Who it affects

    First-time and repeat shoppers on desktop and mobile, from families and gift buyers to small businesses. Behind them, the marketing, development, QA and support teams who handle every unclear step.

    Why it matters

    A photo book is printed exactly as designed. A blurry photo, an empty page or a surprise fee missed on screen shows up when the book arrives, or the shopper gives up before buying.

    03History of the project · Feb 2017–Aug 2026

    A growing catalogue, shipped release by release.

    Shipped

    Background

    CanvasChamp grew into a large catalogue of personalized products, each with its own sizes, materials, layouts and promotions. Keeping the experience clear got harder with every release.

    Shipped

    My part

    I turned business needs into flows and responsive interfaces, prepared developer-ready designs, ran UI quality reviews, and mentored designers through urgent releases.

    My shipped Photo Book work: CCA-3967

    I designed the Photo Book product page with its Select Design Method pop-up, Hire a designer and Upload artwork flows. It went live. The Photo Book editor itself was designed by another CanvasChamp designer.

    CCA-3967 Select Design Method pop-up on the Photo Book page
    ShippedSelect Design Method pop-up.
    CCA-3967 Hire a designer flow with designer fee in the bottom bar
    ShippedHire a designer flow.
    CCA-3967 Upload artwork flow with free proof and quality check
    ShippedUpload artwork flow. Prices in these Figma frames are mock-up values.
    Concept Why a Photo Book concept

    The client wanted to add new features to the Photo Book design tool, so I chose Photo Books as the focus for this concept. It also gave me the opportunity to revisit the design flow I had previously created and shipped. I plan to present the concept to the client; the decision to adopt it is theirs.

    04Geography of the project

    Photos everywhere, decisions on one screen.

    Target users

    Adults turning personal photos into gifts and keepsakes: families, gift buyers, home-decor shoppers, photographers, small businesses.

    Concept focus

    Gift buyers, home decorators and small businesses, as hypotheses to test.

    Market

    US first for the concept. UK, India, Australia, New Zealand and Canada later, with their own currency, units, payments and shipping.

    Environment

    At home, at work or travelling, with photos spread across phone, computer and cloud.

    Devices

    Desktop and mobile. The concept's desktop tool also takes photos from a phone by QR code.

    Where it hurts

    Upload, cropping, layout, preview and price, especially with many photos or on a phone. Many shoppers need guidance on cropping, sizing and image quality.

    05Physics of the project

    Format first, then photos, then design.

    Concept journey · clickable
    1. Homepage
    2. Photo Books listing
    3. Photo Book detail
    4. Add photos
    5. Start choice
    6. Editor: crop and layout
    7. Review
    8. Add to cart
    New step in the conceptExisting step, redesignedCart and checkout are out of scope.

    The design method (design online, upload artwork, hire a designer) moves from a pop-up into the buy box. A new listing lets shoppers choose a format before the tool.

    Concept Photo Books listing on desktop with format filters and book types
    Concept Photo Books listing on mobile
    ConceptThe new Photo Books listing: shoppers choose a format first, then move on to photos and design. The live site has no listing step.

    Friction in the live tool, and the concept's response

    "Likely effect" is my expert assessment, not user research.

    Friction (live, Nov 2026)Likely effectConcept response
    Dropdowns, then a separate design-method pop-upDesigner fee appears only after the shopper commitsMethod and fee in the buy box, before "Start designing"
    One page at a timeHard to judge how facing pages work togetherSpreads view, All pages, page strip with warnings
    Layout change warns the page will be lostShoppers may avoid trying layoutsLayout applies with a confirming toast
    Fixed note about grid linesQuality issues aren't tied to the photo causing themInline "may print blurry" warning with Swap photo
    Price breakdown in a header dropdownThe total's make-up is out of sight while designingPrice and page count stay in the top bar
    06Chemistry of the project · from my years on CanvasChamp

    Shoppers start with warmth and can end in doubt.

    • QualityA low-resolution photo will print badly.
    • CroppingA face or detail will be cut off.
    • ExpectationThe printed book won't match the preview.
    • PriceDiscounts, upgrades and fees change the total in hard-to-follow ways.

    The concept aims for connection, confidence and reassurance.

    How the visual direction supports it
    1. A quiet, light canvasCustomer photos carry the emotion.
    2. Colour with a jobBrand red for the main action, blue for selection, amber only for things to check.
    3. Reassuring copy"We print exactly what you see. A quick check now saves a reprint."
    4. Warnings that name the fixNever colour alone.
    Concept mobile review sheet: Before you add to cart, with reassuring copy and Fix links
    ConceptThe review sheet carries the reassuring copy and a Fix link for each issue.
    07Biology of the project

    The re-checking loop I saw on the live site.

    1. A memory or occasion starts the project
    2. The shopper uploads and customizes
    3. Doubt about quality, crop, size or price
    4. They re-crop, re-upload or go back to product details
    5. They buy after repeated checking, or leave

    Steps 3 and 4 repeat. The workaround: comparing earlier choices in their head, because the tool didn't hold the answers in one place.

    Concept

    From checking alone to deciding with feedback in view

    1. Upload progressKeep designing while photos upload ("Uploading 18 of 42").
    2. Photo tray countsUsed, unused, needs attention.
    3. "3 to check" counterIn the top bar, with warning badges on pages.
    4. Toast after Crop or LayoutConfirms the change.
    5. Final reviewEach issue with a Fix link.

    These are design intentions; whether they reduce re-checking is still to be tested.

    Concept desktop editor with upload progress, a to-check counter, page warnings and a toast
    Concept mobile editor with a 2 to check counter and Crop applied toast
    ConceptThe editor on desktop and mobile, with the check counter, page warnings and a confirming toast.
    08Mathematics of the project

    How success will be measured.

    The concept hasn't been tested yet, so this is the plan for measuring it.

    Evidence behind this page

    An expert review of the live Photo Book tool and page (Nov 2026), labelled as expert assessment, and my own first-hand experience leading CanvasChamp design.

    How I'd validate the concept

    Planned, not done: moderated usability sessions on desktop and mobile, measuring:

    Task success: build a book and reach add-to-cart Critical errors Backtracking Time on task Confidence the print matches the preview Post-task ease rating
    09Design engineering · concept work, Nov 2026

    How the concept was built.

    Patterns, not copies

    Studied Snapfish for the editor and Zazzle for shopping, for patterns only. Kept what worked in CanvasChamp's tool: one tool rail, layouts grouped by photo count, phone upload.

    Design system first

    Brand red kept, one typeface, blue for selection, amber for warnings, components for all four page types, and a reusable Photo Book image slot.

    Two homepage directions

    Option A restyled the live layout. Option B introduced new section styles and a Photo Books tile, and became the main flow.

    A listing that didn't exist

    A Photo Books listing so shoppers choose a format before the tool.

    Real options, honest placeholders

    Shapes, 4 x 4 in, 20 pages, two covers, two papers, three design methods and 1 to 4 photos per page come from the live site. Prices, fees and delivery stay [TBC].

    Prototype

    11 desktop and 13 mobile screens, wired from homepage to an add-to-cart end screen, with back and close links.

    Editing you can see

    The live crop offers only zoom and rotation. In the concept, Crop shows its result straight away and a toast confirms it.

    BeforeLive tool
    Live crop modal with zoom in, zoom out and rotation only
    Crop modal: zoom and rotation only.
    AfterConcept
    Concept editor after crop applied, the photo zoomed in with a confirming toast
    Crop applied in place, confirmed by a toast.
    10STAR story

    The story in four lines.

    Shipped work
    Photo Book concept
    Situation
    A fast-growing catalogue with many options, promotions and devices made consistency hard.
    The live Photo Book tool shows one page at a time, hides the price breakdown, and can wipe a page when the layout changes.
    Task
    Lead UI/UX direction, improve discovery and customization, keep responsive quality, support the team through releases.
    Redesign the Photo Book journey from homepage to add-to-cart, on desktop and mobile.
    Action
    Flows, responsive pages and customizers; reusable patterns; developer-ready specs; UI quality reviews; mentoring.
    Design system first; method and fee in the buy box; one-step autofill start; spreads editor with visible crop and layout results; in-place quality warnings; a review before the cart.
    Result
    A live platform I designed for from Feb 2017–Aug 2026, including the Photo Book page and design-method flow (CCA-3967).
    A clickable 24-screen prototype and design system, ready for usability testing. Not launched or tested.
    11Before and after · live site, Nov 2026 → concept

    Six moments, redesigned.

    Grey panels show the live site. Red panels show the concept. The "Choosing options" before screens are my own shipped design (CCA-3967), so that pair shows me rethinking my own work. The editor before screens were designed by another CanvasChamp designer.

    Choosing options

    Dropdowns and a separate pop-up become one buy box with the method and fee.

    BeforeLive · my CCA-3967
    Live buy box with dropdowns and a Select design method button
    Live Select design method pop-up
    Dropdowns for each option, then the design method in a separate pop-up.
    AfterConcept
    Concept Photo Book detail page on desktop with option tiles, design method and price summary
    Concept Photo Book detail on mobile, scrolled to the design method and price summary
    Option tiles, method and fee in one buy box, on desktop and mobile. Prices [TBC].

    Starting the book

    The tool no longer drops you on the front cover.

    BeforeLive tool
    Live tool opening on the front cover with Select size
    The tool opens on the front cover.
    AfterConcept
    Concept start choice on desktop: Fill my pages or place photos myself
    Concept start choice on mobile
    Fill my pages, or place photos myself.

    Adding photos

    An upload panel inside the tool becomes a guided step.

    BeforeLive tool
    Live tool upload panel
    Upload panel inside the tool.
    AfterConcept
    Concept Add photos step on desktop with sources and a selected count
    Concept Add photos step on mobile with 8 selected
    Sources, a selected count and "already in your book".

    Changing a layout

    A destructive warning becomes a change you can see.

    BeforeLive tool
    Live tool warning that the page design will be lost
    Warning: the page design will be lost.
    AfterConcept
    Concept desktop editor after layout applied, page 5 shows two photos and a toast
    Concept mobile editor after layout applied
    Page 5 switches to two photos; a toast confirms.

    Before buying

    A hidden price breakdown becomes a review that names each issue.

    BeforeLive tool
    Live tool price breakdown dropdown in the header
    Price breakdown in a header dropdown.
    AfterConcept
    Concept desktop Before you add to cart checklist with Fix links
    Concept mobile Before you add to cart sheet
    "Before you add to cart", with a Fix link for each issue.

    Mobile

    One page at a time becomes spreads, a bottom tool bar, and price with Add to cart pinned.

    BeforeLive mobile tool
    Live mobile Photo Book tool showing the front cover, upload panel and grid-line note
    Front cover only, with upload below the canvas.
    AfterConcept
    Concept mobile editor with spreads and a bottom tool bar
    Spreads, a bottom tool bar, price and Add to cart pinned.
    11Feature matrix

    Area by area.

    Each user benefit is a design intention, not a measured result. Existing evidence is the live site as captured in Oct and Nov 2026.

    AreaExisting experience (evidence)Proposed redesignUser benefitEvidence/status
    HomepagePromo slider and "Create your canvas" panel; Photo Books is one tile in a discount-led gridFull-width hero, quick-order panel, promise bar, product grid with a Photo Books tileProducts read as products; offers keep their own bandObserved · Concept, untested
    Photo Books listingNo listing step; the Photo Book page leads straight into the toolFormat filters (type, size, cover, binding, pages, occasion, price), how it works, occasionsCompare formats before choosingObserved · Concept, untested
    Detail buy boxDropdowns; design method in a pop-up; designer fee appears laterOption tiles; method and fee in the buy box; price summary; sticky buy barFull cost known before committingObserved · Concept, untested
    Adding photosUpload panel inside the tool, with several sources and duplicate togglesStep 2 of 3 picker with counts and "already in your book"; uploads continue while designingLess waiting, fewer duplicatesObserved · Concept, untested
    Starting the bookOpens on the front cover; "Auto set images" sits in the upload panelStart choice: Fill my pages (recommended) or place photos myselfAutofill as a clear first choice, with control keptObserved · Concept, untested
    Editing viewOne page at a timeSpreads and All pages, page strip with warning badgesSee the book as it opensObserved · Concept, untested
    Layout changeWarning that the page design will be lostLayout panel; result applies with a toastSafe to try layoutsObserved · Concept; Undo is a label only
    CropModal with zoom and rotation onlyCrop panel from the photo toolbar; result shown in placeControl over what's in frameObserved · Concept, untested
    Print qualityFixed note about grid linesInline "may print blurry" warning with pixel size and Swap photoProblem and fix in one placeObserved · Concept, untested
    PriceBreakdown in a header dropdownPrice and page count always visible; one red primary actionCost stays in viewObserved · Concept, prices [TBC]
    Pre-purchase checkNot seen in captures"Before you add to cart" list with Fix linksCatch mistakes before printingConcept, untested
    Mobile Photo BookTabbed tools; one page at a time; grid-line noteBottom tool bar, a "swipe for next spread" hint, price and Add to cart pinnedFull editing on a phoneObserved · Concept, untested
    12Final screens · concept prototype, Nov 2026

    The final screens, desktop and mobile.

    Concept, not launched or user-tested. Prices and delivery shown as [TBC]. Figma screens produced with AI assistance under my direction.

    Concept homepage on desktop
    Concept homepage on mobile
    01Homepage. Products lead with photos and names; offers move to their own band. On mobile, the offer copy sits above the photo book so the product stays in view. Offer text [TBC].
    Concept Photo Books listing on desktop with format filters
    Concept Photo Books listing on mobile
    02Photo Books listing. Choose a format first; filters speak in book terms.
    Concept Photo Book detail on desktop
    Concept Photo Book detail on mobile, scrolled to the design method
    03Photo Book detail. Design method and its fee sit in the buy box, so the fee is in the summary before you start. Mobile view shown scrolled to the design method.
    Concept Add photos step on desktop
    Concept Add photos step on mobile
    04Add photos. Three sources, a selected count, and "already in your book" to stop duplicates.
    Concept start choice on desktop
    Concept start choice on mobile
    05Start choice. Autofill is recommended, but placing photos yourself is one tap away.
    Concept editor after crop applied on desktop
    Concept editor after crop applied on mobile
    06Editor, crop applied. Spreads, price in the top bar and a "to check" counter keep the whole book in view; the edit shows straight away.
    Concept editor after layout applied on desktop
    Concept editor after layout applied on mobile
    07Layout applied. Changing a layout no longer wipes the page; it updates and confirms. On mobile, tools move to a bottom bar and price and Add to cart stay within thumb reach.
    Concept review before adding to cart on desktop
    Concept review before adding to cart on mobile
    08Review before buying. One last check names each issue and links straight to the fix.

    Prices, fees and specs beyond the observed range are [TBC]. Shipped work: Feb 2017–Aug 2026. Concept: Nov 2026, not launched.

    Back to top ↑

    Next project

    EduSight

    Accessible learning for blind and low-vision children, and the teachers who support them.

    UX case study · V1 hackathon, 2026 → V2 product design

    EduSight

    Accessible learning that tells each teacher what a child knows, and what should happen next.

    Accessible learning platformEdTech · LMSPhone and desktop web
    Role
    Team anchor in a 3-person hackathon team (V1); sole designer for V2
    Duration
    Jul to Nov 2026

    See the screensTry the prototypes

    Tools used

    • Figma
    • FigJam
    • NotebookLM
    • ChatGPT
    • Claude
    Designer
    Komal Patel
    My role
    Team anchor (V1); sole designer (V2)
    Timeline
    Field research Jul–Aug 2026 · V1 hackathon Sep 2026 · V2 design Oct–Nov 2026
    Users
    Teachers, students aged 6 to 14, school administrators, guardians
    Platform
    Phone-first for students and guardians; desktop and phone for staff

    Problem statement

    How might we help teachers track the learning progress of visually impaired children aged 6 to 14, identify individual skill gaps, and determine the next learning steps for each child?

    TRACKWhat can this child do now, skill by skill?
    IDENTIFYWhich skill is getting in the way?
    DETERMINEWhat is the one next step to try?

    The approved statement for both versions. Every section below traces back to one of these three verbs.

    01 Project overview

    One teacher's question, carried through two versions

    EduSight helps teachers of blind and low-vision children aged 6 to 14 see what each child can do, spot the skill that is holding them back, and choose one clear next step. Children learn by ear from their own teacher's recorded voice, then practise and hear feedback.

    Context
    Field visits with classroom observation and teacher conversations at a school for blind students in Gujarat, India.
    Primary user
    The teacher, who is often blind too and works with a screen reader.
    Also served
    Students (learning and practice), guardians (progress and consent) and school administrators (set-up and records). They support the teacher's loop; they don't replace it.
    Project type
    V1: hackathon concept and working prototype. V2: full product design in Figma for a production learning platform, not yet built.
    My contribution
    V1: team anchor in a 3-person hackathon team. V2: sole designer of the research synthesis, design system, 64 prototype screens and accessibility specifications.
    EduSight · Teacher · Student overview
    Teacher's student overview for a sample student: progress by subject with status labels, lesson minutes this week, accessibility needs such as Braille display and screen reader, and recent activity

    02 Context

    Classrooms where the teacher may also be blind

    We spent our field visits at a school for blind students in Gujarat, India, in classrooms and in conversation with teachers.

    Children
    Blind and low-vision learners aged 6 to 14. Some also have other disabilities, so the pace of learning varies widely within one class.
    Teachers
    Many are blind themselves. They teach with Braille, abacus, slates and tactile models, and use phones through TalkBack.
    Devices
    Shared laptops and phones. Keyboard skills come before laptops. Connectivity is not guaranteed.
    At home
    Parents repeat lessons in the evening, coordinated through WhatsApp.

    03 Problem and solution

    Marks are recorded. Meaning is not.

    Teachers can give a score, but not say which skill broke or what to teach next. EduSight's answer connects evidence, gap and next step in one loop.

    The problem

    • Progress lives in memory and formsOne teacher memorises each child's improvement and uses ordinary Google Forms. Field
    • Marks don't show the skill gapState apps log marks for compliance, not skills. AI-assisted Team
    • Finishing isn't the same as masteringExisting apps deliver content; listening doesn't prove understanding. AI-assisted
    • Visual concepts are hard to explainDiagrams and shapes are the hardest topics; teachers worry about teaching them wrongly. Field
    • Results don't lead to a next stepThe lowest point of the teacher journey. Team
    • School and home drift apartParents are told, but follow-through depends on the parent. Field

    The designed solution

    • Skill-based progressEach outcome is Secure, Developing, Emerging or Not started, with the evidence behind it.
    • Teacher guidance"Needs attention" explains why a child is flagged; the teacher decides what to do.
    • Lessons in the teacher's own voiceRecorded part by part, with transcripts and image descriptions.
    • Accessible practice and feedbackEvery question can be heard again; a wrong answer gets a hint and one more try.
    • Guardian connectionPlain-language progress, teacher messages and consent choices.
    • School coordinationSet-up, classes, records and guardian links for administrators.
    V2: designed and prototyped in FigmaNot yet builtV1: hackathon prototype

    04 Design thinking process

    Five stages, run twice

    The stages ran once for the V1 hackathon and again for V2. Only activities with a record in FigJam, Drive or Figma are listed.

    Stage 1

    Empathise

    • Field visits with classroom observation and teacher conversations
    • Interview notes with three blind teachers
    • Desk research: apps in use, assistive devices, published studies
    • AI-assisted synthesis of field notes (NotebookLM)
    Stage 2

    Define

    • Research insights and root problems
    • Experience journey map with emotion scores
    • Job to be done
    • Eight How Might We questions
    • Problem statement, refined three times
    • V1 personas (AI-assisted composites)
    Stage 3

    Ideate

    • Mind map and round-robin
    • 8-by-8 ideation round
    • 12 divergent concepts, scored out of 40
    • Opportunities ranked out of 15
    • Information architecture and MVP user flows
    Stage 4

    Prototype

    • BrightPath lo-fi exploration (ChatGPT)
    • V1 hackathon prototype
    • V2 design system (8 Figma pages)
    • V2 product screens for four roles
    • Five interactive prototypes
    Stage 5

    Review and iterate

    • Two rounds of mentor critique
    • Design reviews and fixes
    • Accessibility specifications
    • Design QA and prototype link audits
    • Usability testing with users: not yet done

    Review fed back into Define twice: once after mentor critique, once when V2 widened the product to four roles.

    05 Project timeline

    From field visits to a full product design

    Solid bars use dates recorded on files and boards. Dashed bars mark phases whose exact start or end wasn't recorded.

    DatedPhase without exact datesMilestoneV1 in green, yellow and orange · V2 in blue and pink
    • Field visits and interviewsJul to Aug 2026 · V1 · classroom observation, three teachers
    • Synthesis, define and ideationAbout Aug to early Sep 2026 · V1 · FigJam board; exact dates not recorded
    • BrightPath lo-fi5 Sep 2026 · V1 · AI-assisted exploration
    • Hackathon submission14 to 15 Sep 2026 · V1 · EduSight deliverables
    • V2 planning and V1 recoveryOct 2026; V1 recovered and baselined 31 Oct · V2 · start not recorded
    • Design system and pages 01–18Approved 1 Nov 2026 · V2 · approved
    • Prototypes, edge cases and QA1 to 2 Nov 2026 · V2 · pages 19–22
    Chapter 1 of 6Next: Research →

    06 User research

    Four kinds of evidence, kept apart

    Each finding is labelled by where it came from, so a field observation is never confused with an AI summary or a team assumption.

    Field team notes from visits and interviews AI-assisted NotebookLM summaries of field material Team team analysis and artefacts Secondary published research Inference my interpretation
    1

    Field visits

    Classroom observation and teacher conversations at a school for blind students in Gujarat, India, in 2026.

    Field
    2

    Teacher interviews

    Conversations with three blind teachers. Captured as team notes in FigJam.

    Field
    3

    Desk research

    Apps in current use, government systems, assistive devices and published studies on motivation.

    Secondary
    4

    AI-assisted synthesis

    NotebookLM mind maps and summaries organised the field notes. Used only where they agree with sources 1 and 2.

    AI-assisted
    A

    Qualitative research

    Objective

    Understand how teachers of blind children follow each child's learning today, and where that breaks down.

    Method

    Semi-structured conversations and classroom observation, written up as bullet-point team notes. Not recorded as verbatim transcripts.

    Participants

    Three blind teachers and observed classes of blind and low-vision students. No names, subjects or other identifying details are published.

    Themes

    Tracking and records · teaching visual concepts · tools and screen readers · paperwork · parents and home learning.

    Interview notes

    Bullet-point notes in the note-taker's own words, not recorded quotes. Class sizes and grades are left out so the school can't be identified.

    Limits

    One site, a small sample and paraphrased notes. Original recordings exist but were not re-transcribed for this case study.

    B

    What three teachers told us

    Paraphrased from interview notes; teachers are not identified

    Teacher A

    • Collects information with ordinary Google Forms.
    • Has no tracking tool, so remembers each student's improvement.
    • Cannot record videos alone; relies on speech engines and TalkBack.
    Field notes

    Teacher B

    • Diagrams and shapes are the hardest things to explain without sight.
    • Does the same paperwork as a mainstream school.
    • Must not teach a visual concept the wrong way.
    Field notes

    Teacher C

    • Activities that depend on seeing are limited.
    • Parents are informed, but follow-through depends on the parent.
    • Knows student records need daily updates; students need guidance.
    Field notes
    C

    Field observations and supporting evidence

    Field photos stay private; no children are shown

    Shared devices

    Students worked on laptops in pairs; classrooms mixed Braille books with laptops.

    Field

    Mixed needs

    Some children have other disabilities too, so a next step has to be set per child, not per grade.

    Field

    Passive apps

    Apps in use host videos and textbooks but have no practice, feedback or saved progress.

    AI-assisted

    Repetition

    Some children replay a lesson four or five times, and respond best to their own teacher's voice.

    AI-assisted
    D

    Quantitative research

    No survey or measurement study was run. This project's evidence is qualitative, so there are no response counts or charts here.

    The hackathon board held some population figures and device-usage percentages. The board itself labels the percentages as planning benchmarks needing field validation, and the population figures cover all disabilities, not blindness alone, so they are left out.

    E

    Key insights

    1

    Marks are recorded; meaning is not

    Teachers can give a score but not which skill broke or what to teach next. The apps teachers described track marks, not skills.

    FieldTeamAI-assisted

    2

    The teacher's voice is the curriculum

    Some children need to hear a lesson several times, and a familiar voice may help more than new content.

    AI-assistedInference

    3

    The teacher may also be blind

    Every teacher screen has to work with a screen reader, not only the student screens. This changed the whole staff side of the product.

    Field: all three teachers

    4

    Learning leaks home

    The gap follows the child home. Parents need to know what to practise, not only the marks.

    FieldAI-assisted

    5

    Add insight, not admin

    Teachers already fill in several mandatory systems. EduSight must not become one more.

    FieldAI-assisted

    Method note: insights come from team field notes from visits to a school for blind students in Gujarat, India, and conversations with three blind teachers. AI tools (NotebookLM and ChatGPT) were used to organise notes and make early explorations; their outputs were checked against the team's own notes. The original recordings were not re-transcribed for this case study.

    07 Define

    Turning notes into one sharp problem

    The define work sits on the hackathon FigJam board. Where a card is the team's own reasoning rather than something a teacher said, it is labelled.

    A

    Empathy map: the teacher

    Built from the three interviews

    Says

    • "using normal google forms to collect info and data"
    • "memorising each students improvements and performances"
    • "do all documentations same as how's in a normal school"
    • "students need guidance"
    Note-taker's wording

    Does

    • Teaches with abacus, slates, Braille and 3D models
    • Uses TalkBack and speech engines on a phone
    • Keeps records updated daily
    • Tells parents what to practise
    Field

    Thinks

    • What did this child complete last time?
    • Is this activity right for this child?
    • What is stopping this child from progressing?
    Team journey map

    Feels

    • Careful about teaching a visual idea the wrong way
    • Stretched by paperwork on top of teaching
    • Unsure whether practice continues at home
    Inference
    B

    Personas

    V1 · AI-assisted composites from field notes

    These four personas were written for the V1 hackathon with AI help, from the team's field notes. They are composites, not real people. All four are illustrations, not real people: the teachers are drawn characters and the students are shown as Pip, so no photograph or photo-style image is used. Ages and the source's "research confidence" ratings are left out because no original evidence supports them.

    Illustrated character for the Nisha persona: a teacher with glasses holding a tablet with a tick
    Nisha JoshiSpecial education teacher · multi-channel organiserIllustration
    Context
    Teaches across many platforms and prepares accessible material for blind learners.
    Goals
    One place to track progress; interactive questions with feedback.
    Behaviours
    Heavy, confident use of several digital tools.
    Needs
    Accessible home-learning resources she can send to families.
    Frustrations
    Student information spread across systems; parents translating inaccessible lessons at home.
    Illustrated character for the Rohan persona: a teacher wearing headphones
    Rohan MehtaSpecial educator · screen-reader-firstIllustration
    Context
    Works through a screen reader every day.
    Goals
    Unified progress tracking and verbally descriptive lessons.
    Accessibility
    Every tool must work non-visually.
    Needs
    Accessible learning platforms instead of visually biased resources.
    Frustrations
    Grades, attendance and welfare data sit in separate systems.
    Pip, the EduSight mascot, standing in for the Aarav persona
    Aarav ShahStudent · independent assistive-technology userIllustration: Pip
    Context
    Uses technology often and independently.
    Goals
    Learn on his own without asking for help to navigate.
    Accessibility
    Screen-reader-compatible apps and clear non-visual instructions.
    Frustrations
    Visually biased interfaces and inaccessible interactions interrupt learning; connectivity isn't always reliable.
    Pip, the EduSight mascot, standing in for the Meera persona
    Meera ParmarStudent · learns through repetition and feedbackIllustration: Pip
    Context
    Uses technology regularly, often with support.
    Goals
    Hear things again until they make sense.
    Accessibility
    Replayable audio, tactile materials and immediate, encouraging feedback.
    Frustrations
    Poorly described pictures, silent blackboard teaching and tiring tactile routines.
    C

    Problem definition

    Each card shows its source
    01

    Evidence is fragmented

    Progress sits in memory, forms and mandatory apps that don't talk to each other.

    FieldAI-assisted

    02

    Completion looks like mastery

    Apps show that content was opened, not whether it was understood.

    AI-assistedTeam

    03

    Skill gaps are a guess

    Skills and their prerequisites aren't connected, so support may target the wrong difficulty.

    Team

    04

    Tracking adds workload

    Recording is separate from teaching, so records go stale.

    FieldTeam

    05

    Content isn't accessible

    Pictures are skipped by screen readers; videos teach silently on a board.

    AI-assisted

    06

    Learning stops at the school gate

    Home practice depends on how much each parent can follow.

    Field

    D

    Root cause analysis

    From the team's FigJam board
    Show the root cause table
    Root problems: surface symptom, root cause, consequence and opportunity
    Root problemSurfaceRoot causeConsequenceOpportunity
    Marks without meaningTeachers can record marksRecords are score-based, not skill-basedIndividual progress stays unclearTurn assessments into skill-level progress
    Gaps are hard to locateLearning gaps are hard to nameSkills and prerequisites aren't connectedSupport may target the wrong difficultyA structured skill map
    Next step takes timeDeciding what to teach is slowResults are disconnected from objectivesChildren wait longer for the right helpConnect every gap to a next step
    Recording adds workUpdates need extra effortRecording is separate from teachingRecords become incomplete or outdatedFast, phone-friendly capture
    Improvement is hard to seeProgress is hard to showResults from different attempts are scatteredInterventions are hard to judgeA simple skill-progress timeline

    The "children wait longer" consequence is my inference; the board left that cell blank.

    E

    Teacher journey

    Emotion scores are the team's estimates, not measurements
    Teacher journey from preparing a lesson to reassessing Seven stages with the team's emotion scores: prepare minus 1, conduct activity 0, observe and assess minus 1, record minus 1, identify gap minus 2, decide next step minus 2, reassess plus 1. neutral (0) Prepare Activity Assess Record Identify gap Decide next step Reassess "Recording adds work" "Results don't tell me what to do" Improvement seen
    Show the full journey matrix
    Teacher journey matrix: goals, actions, thoughts, pain points and opportunities for each stage
    RowPrepare−1Conduct activity0Observe and assess−1Record−1Identify gap−2Decide next step−2Reassess+1
    GoalUnderstand the child's current levelHelp the child practise a skillUnderstand performanceSave the resultFind where support is neededChoose what to teach nextCheck whether the child improved
    ActionReview notes, remember past workBraille, tactile, audio or practical activityWatch accuracy, confidence and support neededWrite it down in a separate placeCompare resultsPick an activityAssess again
    Thought"What did this child complete last time?""Is this activity right for this child?"(none recorded)(none recorded)"What is stopping this child?""Which activity should I try next?""Is this approach working?"
    Pain pointInformation is scattered or out of dateActivity may not match abilityDepends on subjective observationTakes extra timeMarks don't explain the gapResults aren't linked to next stepsImprovement is hard to see
    OpportunityChild status understood in 30 secondsActivities matched to the skillOne-tap status with a short noteRecorded within one minuteLink results to prerequisite skillsOne objective, one accessible activityShow change across attempts

    Thoughts are written by the team on the FigJam board, not quoted from teachers. Opportunities come from the board's "moments that matter".

    AssessTrackIdentify gapDecide next stepSupportReassess
    F

    Key user needs

    Seewhat each child can do now, without relying on memory
    Locatethe specific skill holding a child back
    Acton one clear, accessible next step
    Recordprogress faster than a form, with a screen reader
    Sharewhat to practise at home with families
    G

    Job to be done

    Wording from the team board
    WHEN

    I assess a child during a learning activity,

    I WANT TO

    quickly understand their current skill level and learning gap,

    SO THAT

    I can select the right next learning objective and activity.

    H

    How might we

    Highlighted questions led to the selected concept
    1. How might we help teachers quickly understand each child's current skill level?
    2. How might we help teachers record progress without interrupting their teaching?
    3. How might we distinguish activity completion from actual skill mastery?
    4. How might we help teachers identify the prerequisite skill causing difficulty?
    5. How might we convert assessment results into one clear next learning objective?
    6. How might we recommend accessible activities suited to each child's ability?
    7. How might we clearly show a child's improvement over time?
    8. How might we support teachers with limited internet access or shared devices?
    Final

    How might we help teachers track the learning progress of visually impaired children aged 6 to 14, identify individual skill gaps, and determine the next learning steps for each child?

    Early drafts covered organisations, regions and daily independence. The final statement narrows to one user, the teacher, and one job: learning. Adding "next" turned a record into a decision.

    08 Ideate

    Twelve ideas, scored, and two that worked better together

    The team generated concepts against the opportunity areas, scored them, took mentor critique, and chose the direction that answered the problem statement most directly.

    A

    Prioritised opportunities

    Team scores out of 15: value, feasibility, differentiation
    14Skill-based progress trackingValue 5 · Feasibility 5 · Differentiation 4
    14Skill-gap identificationValue 5 · Feasibility 4 · Differentiation 5
    14Next learning stepValue 5 · Feasibility 4 · Differentiation 5
    13Quick assessment recordingValue 5 · Feasibility 5 · Differentiation 3

    Opportunity areas on the board: Skill Intelligence (priority 1), Adaptive Learning (priority 2), Accessible Active Practice, Multimodal Learning and School–Home Continuity. Key question: "What does this child know now, and what should happen next?"

    B

    Concept alternatives

    Scores out of 40 shown where the board recorded them
    Skill CompassA living map of each child's skillsTop 1 · 39/40 with NextStep
    NextStepRecommends the best next activityTop 1 · 39/40 with Skill Compass
    RepeatSmartAdaptive revision that repeats what's neededTop 2 · 37/40
    Skill PassportAcademic and independence profileTop 3 · 35/40
    Teacher EchoTeacher-recorded replay playlists
    VoiceCheckAccessible spoken micro-assessments
    Parent BridgeHome practice for families
    AccessLensChecks resources for accessibility
    LearnOfflineLearning packs that sync later
    Touch + TrackTactile work recorded digitally
    Ready2LearnTalkBack, then keyboard, then apps
    Independence TrackerMobility, hygiene and routines
    C

    Evaluation criteria

    Research evidenceUser impactInnovationDesirabilityFeasibilityHackathon fitScalabilityDifferentiation

    Why the winner won, in the board's words: strongest research evidence, directly answers the problem statement, and a clear hackathon demo story.

    D

    Mentor critique

    Paraphrased from critique sticky notes; mentors not named
    Worked

    "This is working. It solves the stated problem." The flow was "well laid out with voice and touch tracks".

    Push further

    Show more research evidence with pictures, videos and figures. Explore more opportunities; adaptive learning alone felt generic.

    Ideas offered

    Compass is "a very good idea"; add voice feedback, vibration or haptics. Try gamification and points. Rephrase the key insight with the user need.

    What changed in response: the key insight was rewritten around the user need, and points became badges and certificates (see section 15). Haptic feedback was not carried into V2 and remains an open idea.

    E

    Selected direction

    Skill CompassWhere is this child now?
    NextStepWhat should happen next?
    SakshamPath"Give every child a personalized path to capability, not simply a record of marks."
    MasteredMove to the next skill
    DevelopingTargeted practice on the same skill
    Needs supportCheck the prerequisite gap

    This is the V1 skill logic from the team board. V2 renamed the states Secure, Developing, Emerging and Not started.

    F

    Information architecture by role

    V2, read from the approved Figma screens
    Student phone · 4 tabs
    • HomeToday's lesson, continue
    • SubjectsSubject → lesson list → lesson
    • ProgressMy progress by subject
    • BadgesBadges and certificates
    Teacher desktop + phone
    • TodayNeeds attention, classes
    • ClassesClass → student → observations
    • HelpStudent help requests
    • LessonsLibrary → 10-step authoring
    • Records · MessagesSettings, sign out
    School admin desktop
    • OverviewFirst-run set-up, 8 steps
    • PeopleStudents, staff, guardians
    • Classes · CurriculumYears, subjects, outcomes
    • Certificates · ReportsAwards and records
    • Privacy · SettingsConsent and retention
    Guardian phone · 4 tabs
    • HomeThis week, what to practise
    • ProgressChild's progress in plain words
    • MessagesFrom teachers, reply
    • MoreConsent centre, language

    V1 IA from the team's sketch, for comparison: students had Home, Learn (recorded class), Progress and Help; teachers had Home, Lessons, Progress (attendance) and Help (review questions). No admin or guardian role existed.

    G

    User flows

    Simplified. Diamonds are decisions

    Teacher: assess and decide the next step

    1. Today
    2. Select class
    3. Select student
    4. Skill status
    5. Add observation
    6. Gap found?
    7. Why you see this
    8. Assign practice
    9. Reassess
    Returning teacher resumes where they leftNew child: record a baseline firstTeacher changes the suggestionRepeated difficulty: add supportSave fails: data kept, retryConnection lost: saved offline, syncs laterMissing field: inline error, focus moves to it

    Student: learn, practise, get feedback

    1. Welcome
    2. Sign in with code
    3. Home
    4. Lesson overview
    5. Lesson player
    6. Practice
    7. Correct?
    8. Feedback
    9. Results
    Replay this partWrong answer: try again with a hintAsk the teacher for helpOffline: downloaded lessons still play

    Teacher: author a lesson in their own voice

    1. Lesson library
    2. Details
    3. Record or upload
    4. Processing
    5. Parts
    6. Transcript review
    7. Image descriptions
    8. Say it aloud
    9. Practice questions
    10. Preview
    11. Ready?
    12. Publish or schedule
    Not ready: checklist names what is missingSave as draft at any step

    School admin: set up the school

    1. Welcome
    2. School
    3. Languages
    4. Year
    5. Subjects
    6. Classes
    7. Staff
    8. Privacy
    9. Review
    Link a guardian to a studentRevoke access: confirm first

    Guardian: follow progress, manage consent

    1. Phone number
    2. One-time code
    3. Home
    4. Progress
    5. Messages
    6. Change consent?
    7. Confirmation
    Reply to a teacherWrong code: try again

    The teacher flow and its alternate and error paths come from the team's FigJam flow. Student, authoring, admin and guardian flows are read from the V2 prototype.

    09 V1 · hackathon, 2026

    Three names, one loop

    The concept was renamed twice as it took shape. The loop it promised stayed the same.

    FigJam conceptSakshamPathSkill map plus next-step recommender
    Lo-fi exploration, 5 SepBrightPathKey screens for students and teachers
    Hackathon submission, 14–15 SepEduSightEvidence → Gap → Next step → Proof
    BrightPath low-fidelity key screens in four groups: entry and onboarding, student learning flow, teacher creation and management, and review, quiz and performance
    BrightPath low-fidelity key screens. Early AI-assisted exploration made with ChatGPT, V1 hackathon, 2026. AI-assisted

    What V1 proved

    • The teacher-to-learner loop works as one flow: assign, learn, check, update.
    • Accessibility set-up belongs at the start, not in settings.
    • Skill states are easier to act on than one score.

    Where V1 stopped

    • Demo sign-in and simulated processing.
    • Browser text-to-speech instead of the teacher's own voice.
    • No role for guardians or the school.
    • Teacher screens were not designed for a blind teacher.

    10 V1 to V2

    The same loop, made real

    V2 is designed as a full learning platform for schools. Each change is tagged: Feedback came from the field or mentors, Product came from taking the idea to production.

    V1 · hackathon
    What V1 wasA web prototype built in the hackathon by a three-person team. It ran on sample data with a demo sign-in, read lessons aloud with the browser's built-in voice and generated practice quizzes from templates. Its screens are not reproduced here because they show sample records; the lo-fi exploration above shows the V1 design direction.Team · V1 source code, read-only review
    • Student and teacher only
    • One score and three labels
    • Browser text-to-speech
    • Sighted-first teacher screens
    V2 · designed and prototyped
    V2 student home on a phone with today's lesson and a continue button
    Teacher · Student overview
    V2 teacher view of one student with progress by subject and outcome status
    Changes from V1 to V2 with the reason for each
    AreaV1 hackathonV2 designWhy
    Lesson audioBrowser text-to-speechTeacher records or uploads their own voice, part by part, with a transcriptFeedback
    TeachersSighted-first screensScreen-reader-first staff screens on desktop and phoneFeedback
    ProgressOne score, three labelsPer-outcome status (Secure, Developing, Emerging, Not started) backed by observationsFeedback
    Next stepTeacher assigns a lesson"Needs attention" list with a "Why you see this" lineProduct
    RolesStudent and teacherStudent, teacher, school administrator and guardianFeedback Product
    RewardsPoints idea from critiqueBadges and certificates designed; cash awards a proposal onlyFeedback Product
    LanguageEnglishEnglish and Gujarati planned from the startProduct
    PrivacyNot coveredConsent centre, school isolation, guardian one-time codeProduct
    AISimulated processingNo simulated AI; suggestions follow rules the teacher can see and changeProduct

    11 From insight to decision

    Every design decision has a reason

    Traceability from observation to need to design
    What we sawWhat teachers needWhat V2 designs
    Progress lives in the teacher's memorySee what each child can do nowStudent overview with progress by subject and outcome status
    Results don't lead to actionOne clear next step"Needs attention" cards with a plain "Why you see this" line
    Recording adds workRecord in under a minuteOne-screen "Add observation" with status and a short note
    Children replay their teacher's explanationRecord once, replay oftenTeacher recording in short parts; student player with "Replay this part"
    Teachers may be blindTools that work with a screen readerKeyboard-first authoring, spoken status messages, visible focus everywhere
    Learning continues at homeParents know what to practiseGuardian app with plain-language progress and teacher messages

    12 Style guide

    Accessible by default, friendly by choice

    The V2 design system in Figma: tokens, components and rules, all approved on 1 November 2026. Values below are copied from the Figma pages.

    A

    Colour

    Each family has a tint, a main colour and a text-safe shade
    Blue#1F36D9
    50500700
    Primary · links · mathsButtons, focus, selected
    Yellow#F6C21A
    50400800
    Reward · highlightNever text on white
    Orange#F59A23
    50400800
    Quiz · warningDark text on fill
    Green#137B43
    50600800
    Success · scienceSecure status
    Purple#6E35D8
    50600800
    ReadingStudent subject colour
    Pink#C3286D
    50600800
    MusicStudent subject colour
    Cyan#1BA8D7
    50400700
    Listening · infoPip's props
    Red#B3261E
    50600ink
    Error onlyAlways with an icon and words
    White#FFFFFF
    Canvas#FFFDF8
    Surface#F8F6F2
    Line#E4DED3
    Disabled#E9E6E0
    Ink 2#556070
    Ink#1F2430
    Show all contrast pairings
    Accessible colour pairings with contrast ratios
    SamplePairingRatioResult
    AaPrimary text on canvas15.26 : 1AAA
    AaSecondary text on canvas6.27 : 1AA
    AaWhite on primary button8.11 : 1AAA
    AaInk on reward yellow9.35 : 1AAA
    AaWhite on success green5.33 : 1AA
    AaWhite on reading purple6.64 : 1AA
    AaWhite on music pink5.46 : 1AA
    AaInk on quiz orange7.84 : 1AAA
    AaInk on listening cyan5.64 : 1AA
    ■Reward yellow as a fill against the page1.63 : 1Advisory: decorative only, never the only cue
    B

    Typography

    Fredoka for display, Atkinson Hyperlegible Next for everything read
    Display / LFredoka SemiBold 40 / 48Well done, Aarav
    Heading 1Atkinson Bold 28 / 36Today's lesson
    Heading 2Atkinson Bold 22 / 30Needs attention
    Body / L20 / 32 · student defaultListen to the story, then answer one question.
    Body / M18 / 28 · staff defaultThree students are still working on place value.
    Body / S16 / 24 · minimumSaved 2 minutes ago
    Label / LBold 20 / 24Continue
    OverlineExtraBold 14 / 18 · 1.2 px trackingMaths · Grade 3

    The full ramp also has Display XL 56/64, Display M 30/38, Heading 3 19/26, Label M 17/22 and an underlined link style. Nothing a student reads is smaller than 16 px.

    C

    Layout

    Spacing

    481216243248
    Plus 64. 4 px baseline.

    Radius

    sm 12md 16lg 24full
    Plus xl 32. Button edge: 6 px rest, 8 hover, 2 pressed.

    Touch targets

    24
    WCAG
    44
    staff
    48
    student
    64
    primary

    Grids

    Desktop 1440 · 12 columns. Tablet 1024 · 8. Phone 390 · 4.
    D

    Components

    Exported from the Figma component pages
    Button component set: five styles in six states (rest, hover, pressed, focus, disabled, loading), compact teacher buttons, round play buttons and question chips
    Buttons: five styles in six states at 64 px for students, compact 44 px buttons for teachers, round play buttons and question chips. Focus is a thick dark ring, never colour alone.
    Form controls: text fields, a reading-speed select with its open list, checkboxes, radio buttons and switches, each in rest, focus, filled, error and disabled states
    Form controls: labels sit above fields, and errors always show an icon and a message, never colour alone.
    Navigation components: tabs, a student bottom-bar item, teacher side-navigation items in each state, and the student lesson top bar with stars
    Navigation: tabs, student and teacher navigation items in every state, and the student lesson top bar.
    Status pills (Developing, Emerging, Not started, Secure, Done, Needs action, Pending), each with an icon and a word, plus summary stat cards
    Status pills pair an icon with a word, so status never depends on colour. Stat cards show change with an arrow and words.
    Student table rows in rest, hover, selected and keyboard-focus states, showing lesson, progress, accuracy and status
    Class table rows in rest, hover, selected and focus states.
    E

    Icons

    Thirty-two icons including play, pause, replay, headphones, mic, braille, text size, home, users, chart and trophy
    24 px icons with a 2 px rounded stroke that take their colour from the parent. Icon-only buttons always need an accessible name.
    F

    Accessibility patterns

    Keyboard focus order specs for the student sign-in screen and the teacher lesson library, with numbered stops and WCAG notes
    Focus order is drawn on the frames for developers: student sign-in (left) and teacher lesson library (right), with the WCAG criteria each one meets.
    A learner card listing accessibility needs (Braille display, screen reader, large print, extra time, audio speed) next to progress by subject and weekly activity
    Each learner's accessibility needs sit next to their progress, so teachers plan with both in view. Sample data.
    Two teacher guidance cards: a needs-attention card explaining three incorrect attempts with an Assign practice button, and a suggestion card with an Assign story button
    Teacher guidance cards explain why and offer one clear next step. The teacher can dismiss them.
    A student screen reflowed at 320 pixels wide with no horizontal scrolling
    Edge caseReflow at 320 pxContent stacks; nothing scrolls sideways.
    A student screen with text at 200 percent; the page grows taller and nothing is cut off
    Edge caseText at 200%The page grows longer instead of clipping.

    What the specs cover

    1. WCAG 2.2 AA for every role
    2. Reading order and focus order on each frame
    3. Spoken labels for icons and status
    4. Skip links and landmarks on staff screens
    5. Reflow at 320 px and text at 200%
    6. Reduced motion: Pip shows a still pose

    Checked in Figma only. Testing with TalkBack, NVDA and JAWS is still to do.

    G

    Pip, the mascot

    A red panda who supports, never instructs
    Pip waving
    WelcomeFirst run, sign-in
    Pip reading a book
    ReadingLessons list
    Pip wearing headphones
    ListeningBefore audio, never during
    Pip thinking
    ThinkingPractice start, empty states
    Pip giving a thumbs up
    EncouragingTry again
    Pip celebrating with arms raised
    CelebratingResults, badges
    One per screenLarge for ages 6 to 10, small or off for 11 to 14. Students choose Big, Small or Off.
    Never during audioPip leaves the screen while a lesson plays, so nothing competes with the teacher's voice.
    Short motionOne second or less, plays once. Reduced motion shows a still pose.
    Students firstTeachers see Pip only in empty states. No Pip for administrators or guardians.

    Two more poses, Greeting and Waiting, are drafted in Figma and waiting for sign-off.

    13 App UI

    App UI

    One question, answered for each person

    Sixty-four prototype screens across five journeys, plus the shared states that keep every role out of dead ends. All screens are V2 Figma designs with sample data; nothing here is built yet.

    Full lengthEvery screen is shown at its full height, so nothing scrolls inside a frame.
    Sample dataNames such as Asha are invented. No real student appears.
    Designed, not builtThese are approved Figma designs and a clickable prototype.

    Student

    Phone · 16 screens · sign in, learn, practise, feedback, progress

    1 Sign in Language first, then a code

    Student phone screen, Welcome and language. English or Gujarati is chosen before anything else.
    X1Welcome and languageEnglish or Gujarati is chosen before anything else.
    Student phone screen, Who is signing in. Students, staff and guardians each take their own path.
    X2Who is signing inStudents, staff and guardians each take their own path.
    Student phone screen, Student sign-in. A sign-in code from the teacher. No email or password.
    X3Student sign-inA sign-in code from the teacher. No email or password.

    2 Find a lesson Home, subjects, lesson list

    Student phone screen, Home. Continue learning, a note from the teacher and this week's progress.
    S1HomeContinue learning, a note from the teacher and this week's progress.
    Student phone screen, Subjects. Each subject keeps one colour and icon everywhere.
    S2SubjectsEach subject keeps one colour and icon everywhere.
    Student phone screen, Lesson list. Lessons for the chosen subject, in order.
    S3Lesson listLessons for the chosen subject, in order.

    3 Learn In the teacher's own voice

    Student phone screen, Lesson overview. What the lesson covers and its parts, before starting.
    S4Lesson overviewWhat the lesson covers and its parts, before starting.
    Student phone screen, Lesson player. The teacher's recording, part by part, with Replay this part.
    S5Lesson playerThe teacher's recording, part by part, with Replay this part.

    Designed for listening

    1. Lessons are the teacher's own recorded voice, not text-to-speech
    2. Every part can be replayed as often as needed
    3. Pip leaves the screen while audio plays
    4. Main actions are 64 px tall

    4 Practise One question at a time

    Student phone screen, Practice start. A calm start screen before the questions.
    S10Practice startA calm start screen before the questions.
    Student phone screen, Question — choose one. Large answer cards, one question per screen.
    S11Question — choose oneLarge answer cards, one question per screen.
    Student phone screen, Question — answer A chosen. The chosen answer is marked with a tick and words, not colour alone.
    S11Question — answer A chosenThe chosen answer is marked with a tick and words, not colour alone.

    5 Feedback Encouraging, never punishing

    Student phone screen, Feedback — try again. A hint and another try, with Pip encouraging.
    S13Feedback — try againA hint and another try, with Pip encouraging.
    Student phone screen, Feedback — right. Right answers are celebrated briefly.
    S13Feedback — rightRight answers are celebrated briefly.
    Student phone screen, Results. Score in words, a badge, and the part worth hearing again.
    S14ResultsScore in words, a badge, and the part worth hearing again.

    6 Progress What I can do now

    Student phone screen, My progress. Progress by subject, explained in words.
    S19My progressProgress by subject, explained in words.
    Student phone screen, My badges. Badges earned for effort and progress.
    S21My badgesBadges earned for effort and progress.

    Rewards

    1. Badges and certificates recognise progress
    2. Cash awards are not part of the student app
    3. Any cash award would be a school decision; proposal only, not approved

    Teacher: tracking and help

    Desktop · 7 screens · choose a screen to see it at full length

    Teacher · T1
    Teacher desktop screen, Today: Needs attention comes first, with the reason each child is listed.
    Today Needs attention comes first, with the reason each child is listed.1 of 7

    Teacher: lesson authoring

    Desktop · 16 screens · from recording to publishing

    Teacher · X4
    Teacher desktop screen, Staff sign-in: Staff sign in on the school's own account.
    Staff sign-in Staff sign in on the school's own account.1 of 16

    School administrator

    Desktop · 14 screens · set-up, people and records

    School admin · AD0
    School administrator desktop screen, Administrator first-run welcome: A first-run welcome explains the eight set-up steps.
    Administrator first-run welcome A first-run welcome explains the eight set-up steps.1 of 14

    Guardian

    Phone · 11 screens · progress, messages and consent

    1 Sign in Phone number and a one-time code

    Guardian phone screen, Guardian sign-in: phone number. Guardians sign in with the phone number the school holds.
    X5Guardian sign-in: phone numberGuardians sign in with the phone number the school holds.
    Guardian phone screen, Guardian sign-in: enter code. A one-time code confirms it is them.
    X5bGuardian sign-in: enter codeA one-time code confirms it is them.
    Guardian phone screen, Guardian home. This week at a glance, and what to practise at home.
    G1Guardian homeThis week at a glance, and what to practise at home.

    2 Follow progress Plain language, no jargon

    Guardian phone screen, Child’s progress. The child's progress, explained for families.
    G2Child’s progressThe child's progress, explained for families.
    Guardian phone screen, Messages from teachers. Messages from the child's teachers.
    G3Messages from teachersMessages from the child's teachers.
    Guardian phone screen, Message thread — writing a reply. Replying to a teacher.
    G3bMessage thread — writing a replyReplying to a teacher.

    3 Stay in control Messages and consent

    Guardian phone screen, Message thread and reply. The thread after the reply is sent.
    G3bMessage thread and replyThe thread after the reply is sent.
    Guardian phone screen, More. Settings, language and the consent centre.
    G9MoreSettings, language and the consent centre.
    Guardian phone screen, Consent centre. Every permission the school asked for, in one place.
    G4Consent centreEvery permission the school asked for, in one place.

    4 Change consent Confirm, then a clear receipt

    Guardian phone screen, Withdraw consent: confirm. What changes if consent is withdrawn, before confirming.
    G4wWithdraw consent: confirmWhat changes if consent is withdrawn, before confirming.
    Guardian phone screen, Consent changed: confirmation. Confirmation of what changed.
    G4dConsent changed: confirmationConfirmation of what changed.

    Privacy by design

    1. Guardians see only their own child
    2. Consent can be withdrawn at any time
    3. No Pip on guardian screens: the tone stays adult

    Shared states

    Empty, loading, error, offline, recovery and responsive

    Phone Offline, empty and error states

    Phone screen, Offline. Downloaded lessons still work; answers wait on the phone.
    StudentOfflineDownloaded lessons still work; answers wait on the phone.
    Phone screen, Saved on this phone. Results are kept and sent when the phone is back online.
    StudentSaved on this phoneResults are kept and sent when the phone is back online.
    Phone screen, Unsent answers. Signing out warns first, on a shared phone.
    StudentUnsent answersSigning out warns first, on a shared phone.
    Phone screen, Offline. Requests can still be read; replies send later.
    TeacherOfflineRequests can still be read; replies send later.
    Phone screen, Empty. No open help requests, and where new ones appear.
    TeacherEmptyNo open help requests, and where new ones appear.
    Phone screen, Could not load. What happened, what to do, and an error code.
    School adminCould not loadWhat happened, what to do, and an error code.
    Phone screen, Wrong code. The error says what to check and how to get a new code.
    StudentWrong codeThe error says what to check and how to get a new code.

    Recovery, not dead ends

    1. Every error says what happened and what to do next
    2. Nothing typed is lost on an error
    3. Offline is a normal state, not a failure
    4. Errors use an icon and words, never colour alone
    Shared states · Empty
    Desktop screen, No lessons yet: An empty library explains how to make the first lesson.
    No lessons yet An empty library explains how to make the first lesson.1 of 9

    Responsive frames (reflow at 320 px and text at 200%) are shown in the style guide, section 12F. Teacher phone layouts exist in Figma but are not exported here.

    14 Interactive prototype

    Five journeys you can click through

    Each link opens a Figma prototype at the start of one journey. These are design prototypes, not a deployed app.

    Viewing may need access to the Figma file. Best viewed on a laptop; phone journeys open at phone size.

    15 A considered decision

    A student asked for prize money

    What is designed, what is only proposed, and what no one has approved yet.

    Field

    The request

    One student suggested cash rewards for good quiz scores, plus certificates and an exam mode.

    V2 decision

    The answer

    V2 recognises progress with badges and academic certificates, not money. The product makes no payments.

    Designed

    Badges for effort and progress, and academic certificates that a school can issue and revoke with a recorded reason. These exist as Figma screens only; nothing is built.

    Proposed, not designed

    An optional school-run cash award, off by default. It would need research validation, a fairness and safeguarding review, guardian consent and the school's approval first. No payment or prize flow has been designed.

    Not approved

    No school or authority has approved a reward, certificate or cash-award policy. Scholarships are outside EduSight: the product does not manage or pay them.

    Research on rewards suggests tangible rewards can weaken motivation (Deci, Koestner and Ryan, 1999), and children's data needs extra care under India's DPDP Act, 2023.

    16 Evaluation

    What has been checked, and what hasn't

    V2 has been reviewed as a design: automated checks in Figma, scripted prototype walks and a design review. It has not been tested with teachers or students yet.

    1,287

    Touch targets checked

    Every control on 176 phone frames measured in Figma. None is smaller than 44 px.

    218

    Prototype actions

    181 forward and 37 Back across 64 frames, with no dead ends. 21 end-to-end walks re-run after the last fix.

    AA

    Colour pairings

    Every text pairing in the style-guide table passes, calculated from the colour tokens. One decorative fill (1.63 : 1) is advisory.

    Source: the Figma QA and handoff page, 1–2 November 2026. These are checks of the design file by plugin scripts and design review, not tests with people or assistive technology.

    A

    Iterations from design review

    Text at 200%Fixed-width text broke words apart.Text boxes now grow with the content.
    Pip settingThe Pip toggle overflowed its card.The control was resized to fit at every text size.
    Sign-out dialogFixed-height actions covered the message.The dialog now grows to fit its text.
    Prototype navigationThe bottom bar did not respond in Present mode.Screen-level hotspots were added for every tab.
    B

    Not done yet

    Usability testing

    No sessions with teachers, students or guardians have been run on V1 or V2. The validation plan in section 17 is the next step.

    Screen-reader testing

    Accessibility specs are checked in Figma only. Testing with TalkBack, NVDA and JAWS is still needed.

    Outcomes

    V2 is not built or launched, so there are no outcome measures to report.

    Gujarati

    Planned from the start, but Gujarati screens and audio have not been reviewed by native speakers.

    17 Reflection

    What this project taught me

    The user behind the user

    I started designing for children and learned the product only works if it works for their teacher, who may be blind too.

    One word can change a product

    Adding "next" to the problem statement turned a progress tracker into a decision tool.

    Label your evidence

    AI tools helped organise a lot of field material quickly. Keeping their output separate from what teachers actually said kept the story honest.

    A

    Assumptions still open

    Unvalidated

    Teachers value skill-level tracking

    Enough to change how they record progress today.

    Teachers can update it regularly

    Within lessons, on shared or low-connectivity devices.

    Teachers trust the suggestions

    Because each one explains why, and can be changed.

    B

    Next: validate with teachers

    From the team's validation plan
    1. A teacher understands a child's dashboard within 30 seconds.
    2. An assessment entry is completed within one minute.
    3. Teachers classify statuses consistently.
    4. The teacher agrees with, or corrects, the suggested gap.
    5. The teacher confidently picks the recommended next step.
    ← ScreensChapter 6 of 6Finish →

    Thank you

    To the three teachers and the students at a school for blind students in Gujarat, India who shared their classrooms, and to my hackathon teammates and mentors. EduSight V2 is designed for them.

    Pip the red panda celebrating
    EduSight · UX case study · Komal PatelV1 hackathon, 2026 · V2 design, 2026

    V2 screens are Figma designs with invented sample data. No real student information or photos are shown. Personas are AI-assisted composites from field notes.

    Next project

    NeonChamp

    A staged neon-sign customiser, redesigned into one flow with the price in view.