A 90-Minute UX Sprint — Utah Tech Week 2026
Overview
During Vibe-a-Thon at Utah Tech Week 2026, each team received three random prompts and had
90 minutes to design a solution using only an AI tool of their choice and pitch it.
Prompts
Harry Potter / Alaskan Wilderness / “I can’t organize the food storage.”
I proposed a mobile-first pantry management app for a remote cabin, themed like a spell book but built on real inventory logic. I led the product concept, UX flow, and visual direction, using Magic Patterns to prototype quickly while keeping hierarchy and usability clear.
Sprint Artifacts
Scenario Journey
1. A remote cabin pantry needs to stay organized with limited resupply and high cost for mistakes.
2. Arrive at the cabin and unload supplies
3. Log items quickly (scan or manual)
4. Assign each item to a storage zone (freezer, dry, pantry, etc.)
5. Check what’s expiring soon to plan meals first
6. Update quantities as items are used
7. Before the next supply run, review low-stock + expiring items
8. Generate a requisition list grouped by urgency and category

Core User Flow
Start → Inventory Hub
Add + Organize
Inventory → Add Item → Scan or Manual → Select Zone → Set Quantity + Unit → Set Expiration → Save → Inventory Updates
Track + Update
Inventory → Select Item → Item Detail → Adjust Quantity / Change Zone / Edit Expiration → Save → Inventory Updates
Plan Resupply
Inventory → Low Stock + Expiring Signals → Requisition List → Group by Category + Urgency → Mark Acquired → Inventory Updates

Site Map
Home / Overview
  • Inventory list (filters: zone, category, expiration)

  • Item detail (quantity, expiration, location)
  • Storage zones (browse by physical location)
  • Add item (manual / scan)
  • Requisition list (shopping list by urgency)
Assumptions + Constraints
  • Resupply is limited, so visibility of quantity + expiration is critical
  • Users need fast input, so scan + manual fallback are both supported
  • Organization must mirror real space, so items are grouped by storage zone
  • Theme supports clarity, it can’t compete with core information hierarchy

AI Workflow & Direction
I used Magic Patterns to accelerate layout generation, but I directed structure and hierarchy intentionally.
  • Prompted by component, not full page, to maintain consistency
  • Defined core tasks first (quantity, zone, expiration, priority)
  • Controlled hierarchy so expiration and location stayed visible
  •
Translated theme into action labels (Accio, Revelio, Conjure) without sacrificing clarity
  • AI sped up execution. System thinking and product decisions stayed with me.
I reframed the constraint into a real product problem: how do you manage food inventory in a remote cabin where resupply is limited and mistakes are costly?
I designed a mobile-first pantry management app themed as a magical spell book, grounded in real inventory logic.
Key flow screens: pantry list with stock indicators, add-item form, and a requisition list grouped by category and urgency. I kept quantity, expiration, and location front and center to fix the real problem: disorganized, miscounted food storage in a harsh environment.
Reflection 
It was challenging to create a solution using only an AI design tool from scratch. It required a different way of thinking, but the result felt cohesive because I locked the system first: core tasks, hierarchy, and shared components. Once the logic was set, the UI could move fast without drifting.

You may also like

Back to Top