Debra Bush
Senior UX Designer · Enterprise & Workflow Systems
I design UX for complex operational workflows, using research and validation to turn messy systems into clear, reliable, and scalable product experiences.
Case Studies
Selected work demonstrating how I design and validate complex workflows and systems for products where clarity, risk, and human judgment directly shape outcomes.
Rodger
UX and Systems Design
A systems-first case study in designing and validating coordination, failure handling, and human decision-making.
Project Summary
Rather than starting with screens, I mapped the underlying service logic first: how requests move through the system, how roles interact, and how breakdowns are handled when real-world conditions disrupt ideal flows.Rodger was designed years before gig work became app-based, exploring how a dispatch and task-tracking system could scale without losing clarity, accountability, or human judgment.The system models the same coordination, permissioning, and failure-state challenges found in enterprise operations dashboards and internal tooling.The result was a role-aware dispatch model built around communication, clear handoffs, and decision support rather than blind automation.
Design Decision: Language as a Safety Mechanism
In many interfaces, “Submit” is treated as a neutral action, suggesting simple progression or data handoff. In workflow systems where actions trigger real-world consequences, that neutrality can obscure intent and increase risk.While designing role-based workflows and launcher systems, this distinction surfaced repeatedly. Actions that finalized a request or activated a system state required language that clearly signaled commitment and consequence. Terms like “Launch” or “Request” made that finality explicit in ways “Submit” did not.“Launch,” by contrast, signals activation, exposure, and impact. Users pause before launching. They double-check. They expect downstream effects.In high-stakes operational systems, this distinction matters. Language does not simply label actions; it signals responsibility, frames risk, and shapes user behavior.To support this, content was treated as a configurable layer rather than hard-coded logic, allowing terminology to evolve alongside workflow risk without requiring system redeployment.
My Role
• Mapped the complete task lifecycle from request → assignment → reroute → resolution
• Defined and separated user-facing, driver-facing, and operations-facing responsibilities
• Designed system logic to handle real-world edge cases, including access failures, time overruns, and no-shows
• Sketched administrative tools for tracking service status, notifications, and expenses
• Intentionally prioritized human judgment and clarity over full automation in service handoffs
Interaction Model & Interface Translation
After mapping the service logic and task lifecycle, I translated the system into a concrete interaction model defining primary screens, hierarchy, and state-based behaviors.Low-fidelity wireframes were used to validate layout, role-based visibility, and decision points before moving into higher-fidelity interface structure. Particular attention was paid to how users enter, exit, and recover from failure states without losing context.
Design Principles Demonstrated
• A systems-first approach to solving real-world coordination problems
• Early fluency in role-based UX and service design
• Comfort designing for failure states, not just happy paths
• Evidence of product and systems thinking applied early to real-world coordination problems
Outcome & Impact
The system models challenges common to enterprise internal tools and operational dashboards, including role-based permissions, state transitions, and failure recovery workflows.Rodger anticipated core patterns of modern workflow platforms years before they became mainstream.The work demonstrates early strength in scalable coordination design, role separation, and operational clarity under uncertainty.It reflects a systems mindset that prioritizes supporting human judgment rather than attempting to eliminate it.Design decisions were reviewed through scenario walkthroughs and failure-state reviews to ensure clarity under real-world conditions and prevent ambiguity at critical handoff points.
Artifacts
These artifacts document the UX process from early discovery through interaction modeling, including information architecture, role-based flows, and failure-state handling.• Information architecture and role definitions for the Rodger platform
• Task assignment logic balancing user needs with driver proximity
• Flow diagrams modeling notifications, reassignment, and task resolution
• Early wireframe-level explorations of administrative and operational tools
Keep’s Depths: Designing Stable Systems for Iteration at Scale
From the start of development on Keep’s Depths, we designed a set of shared visual systems to act as internal guardrails, keeping the project within scope while supporting long-term iteration across multiple releases.These systems prioritized consistency, predictability, and shared understanding, allowing the product to evolve safely over time without fragmenting identity or internal decision-making.
Chapter Logos
This consistency reduced decision overhead for teams, accelerated iteration, and prevented visual drift across chapters.
The logo system for Keep’s Depths was designed as a stable, recognizable silhouette that could persist across chapters without fragmenting the game’s identity.Consistency in overall shape was intentional, providing a visual anchor for players and a reliable frame for internal decision-making. Within that constraint, elemental treatments and surface detail were allowed to change to reflect each chapter’s theme.In the final chapter, the silhouette is deliberately broken to signal narrative escalation and thematic rupture, demonstrating how systems can define when it is safe to break their own rules.
Splash Screens
These splash screens extend the logo system into full environmental compositions. While each chapter introduces new visual language, lighting, and tone, shared compositional structure and logo placement reinforce continuity across updates. Shared composition and placement rules allowed new environments to be introduced without re-teaching visual hierarchy or interaction expectations.
Across key surfaces, the logo was consistently positioned in the top-left corner. This placement established predictable visual hierarchy, allowed primary imagery to guide the eye rightward, and influenced internal alignment decisions within the logo itself, including text flow and structural balance.
AI Use & GuardrailsProject Neptune : Keep's Depths
Content design for governance, alignment, and long-term trust
ContextThis work demonstrates how content design can function as governance, setting shared expectations and reducing risk in ambiguous, fast-moving environments. This work focused on internal alignment and decision clarity rather than public-facing policy.
Keep’s Depths is an in-development game project with multiple creative systems and a small team. As AI tools became part of the workflow, we needed shared clarity around how those tools could be used without undermining authorship, quality, or intent.
Problem
Without clear guardrails, AI use introduced ambiguity around decision ownership, quality standards, and what constituted finished work. This created friction and risked inconsistency over time.
Constraints
• Preserve human authorship and accountability
• Avoid tool-driven decision making
• Keep the policy readable and usable, not legalistic
• Apply the same quality standards to AI-assisted and non-AI work
Approach
I treated the policy as a content design problem rather than a technical one. The goal was shared understanding, not enforcement. I focused on defining:• where AI supports exploration and iteration
• where it is explicitly excluded
• how review and quality gates work
• who owns final decisionsThe intent was to create alignment without slowing creative momentum.
Artifact Overview
The resulting AI Use Policy defines clear boundaries for how AI tools are used within the project, emphasizing human intent, review, and responsibility.
Keep’s Depths – AI Use PolicyOur ApproachWe see AI the same way we see any modern development tool.It is not a replacement for creativity, judgment, or craft.
It is a way to support them.Ignoring useful tools doesn’t make a project purer. It usually just makes it harder to execute well. At the same time, letting tools drive decisions instead of people is how quality and intent get lost. Our goal is to sit firmly in the middle of that line.How We Use AIAI is used selectively during development to support parts of the process where it makes practical sense, such as:• Exploring early ideas and directions
• Iterating on concepts and testing variations
• Assisting with workflows where speed or scale is helpfulWhen AI is involved, it is always guided by clear human intent and reviewed with care. Outputs are shaped, refined, and evaluated just like any other piece of work. Nothing ends up in the game by default, and nothing ships without explicit human intent.Creative decisions remain human decisions.What Ends Up in the GameSome AI-assisted work may appear in patches or releases.When it does, it has gone through the same process as everything else:• Directed and adjusted by a human hand
• Refined through manual iteration
• Held to the same quality standards as fully hand-crafted contentIf something doesn’t meet that standard, it doesn’t ship. Simple as that.A significant amount of what you see in Keep’s Depths is created entirely without AI involvement at all.What We Don’t Use AI ForThere are clear boundaries around how we work:• AI is not used as a shortcut for originality
• Raw or uncurated AI output is never shipped
• Creative decisions are not automated
• Artists, designers, and developers are not replaced with promptsAI can assist the process. Authorship stays human.Why We’re Open About ItGame development changes. Tools change. Being honest about that is healthier than pretending nothing ever evolves.We believe transparency builds trust, and trust matters more to us than maintaining a myth about how things are made.In ShortKeep’s Depths is a human-made game.AI may be part of the development process, but human intent, taste, and responsibility are behind every final decision.That’s the standard we hold ourselves to.
Design Principles Demonstrated
• Content design beyond screens
• Systems thinking and governance
• Writing for alignment, not performance
• AI literacy with restraint
• Senior-level judgment in ambiguous spaces
Outcome & Impact
• Shared expectations across collaborators
• Faster iteration without loss of intent
• Reduced ambiguity around authorship and quality
• A reference point that supports long-term consistency
Human-Centered Inventory & Planning System for Recurring Decisions
A calm, emotionally intelligent system for managing everyday complexity, designed to reduce cognitive load and support sustainable habits over time.
Project Summary
Pantrii began as an exploration of how everyday systems can feel supportive rather than demanding. The problem wasn’t inventory tracking itself, but the friction, guilt, and cognitive overload that often accompany food planning and waste reduction. This work focused on reducing decision fatigue in a recurring, state-driven system rather than optimizing for speed or engagement.Rather than optimizing for speed or feature density, I focused on designing a pantry system that paired functional clarity with emotional tone. The goal was to create a tool that helps people make better decisions without requiring constant attention, discipline, or stress.
My Role
• Mapped user flows for scanning, inventory management, and recipe-triggered planning
• Built a component system centered on calm visuals, legible hierarchy, and predictable patterns
• Designed core interaction flows supporting recurring decisions over time
• Designed the brand identity, UI mockups, and core interaction flows
• Balanced functional requirements with emotional impact, ensuring every design decision served both utility and mood
Design Principles Demonstrated
• Ability to design emotionally intelligent UX for real-world, recurring tasks
• Sensitivity to cognitive load, decision fatigue, and behavioral friction
• Comfort integrating brand, system logic, and accessibility into a cohesive whole
• A design approach that prioritizes sustainable use and clarity over novelty or engagement metrics
Outcome & Impact
• Established a scalable foundation for a pantry and meal-planning system designed around habit formation rather than pressure
• Demonstrated product design instincts that harmonize brand, flow, and emotional tone
• Served as a conceptual base for future explorations in emotionally aware systems and AI-assisted planning tools
Artifacts
• Early flow diagrams outlining scanning and inventory logic
• UI explorations testing hierarchy, calm color systems, and interaction affordances
• Mobile mockups demonstrating end-to-end flows from pantry state to meal decision