Creative Debra
Learning & Systems Designer
I design human-centered learning and operational systems that reduce friction, improve usability, and help people navigate complexity with confidence.
Portfolio
Selected work demonstrating creative direction, systems thinking, and a systems-driven approach to UI consistency, visual hierarchy, and scalable design decisions across long-term product development.
Enterprise AI Enablement & Up-Skilling
Driving Workflow Productivity Through Human-Centered Learning Design
Estimated Course Duration: 12–15 Minutes (Microlearning Format)
Design Methodology: Systems Thinking, RTCC Prompts, Behavioral Scaffolding
Core Artifact: Interactive HTML Case Study Slide Deck
1. Executive Summary & ChallengeThe Problem Space
Enterprise organizations are investing heavily in advanced Large Language Model (LLM) infrastructures, but software budgets do not automatically equal workforce capability. Most employees approach highly powerful generative models with conversational, single-sentence queries. This lack of structure leads to:• Severe iteration fatigue: Learners abandon prompts early when outputs don't instantly match their intent.
• Low confidence and trust: Users struggle to identify hallucinations, relying on manual rewriting.
• Wasted operational hours: Companies miss out on projected efficiency gains.The Objective
Design and build a scalable, modern, and productized microlearning system that transitions non-technical corporate teams from "chatting with software" to "cooperating with a digital partner."2. Target Audience & Learner PersonaThis program is specifically designed to fit into the workflows of:
• Non-technical business professionals handling heavy administrative documentation.
• Knowledge workers producing marketing content, technical summaries, and customer emails.
• Customer-facing operations teams requiring standardized, high-volume communication scripts.3. Instructional Architecture: The RTCC FrameworkTo reduce the mental effort needed to write effective instructions, the course introduces a simple, memorable four-part tool:
Role + Task + Constraints + Context
By dividing prompt construction into visual blocks, users can confidently assign appropriate boundaries to the machine:
• Role: Instruct the model on its expert persona.
• Task: Focus the action using strong action verbs (e.g., restructure, summarize).
• Constraints: Enforce style guides, word counts, and language rules.
• Context: Provide key audience backgrounds, background data, or style examples.4. Evidence-Based Design DecisionsWhen building educational materials for modern learners, every layout choices must serve cognitive and business purposes.Choice A: Microlearning Chunking
What: Organizing content into a modular, 12–15 minute asynchronous package.
Why: Corporate learners face time limits. Shorter lessons improve completion rates and fit easily into standard business days.Choice B: Side-by-Side Prompt Contrast
What: Showing side-by-side tables comparing a conversational prompt with an optimized prompt.
Why: Demonstrating the concrete contrast in output quality reinforces the value of applying the framework.Choice C: Active Sandbox Simulators
What: Incorporating an applied multi-state scenario directly into the presentation.
Why: Real-world skill transfer requires active decision-making. By giving learners immediate corrective and constructive feedback, we guide behavior improvement instantly.5. Targeted Business OutcomesWhen evaluated using the Kirkpatrick Model of Training Evaluation, this educational architecture aims to drive:
• Cycle Reductions: Reducing typical prompt cycles from an average of 7.5 iterations down to 3.5.
• Speed Improvements: Decreasing routine workflow execution times by up to an estimated 55%.
• Increased System Adoption: Driving returns on internal enterprise software investments.
• Standardization: Keeping outgoing brand voice consistent across distributed global teams.
Reducing Friction Between Purchase and Product Value
Most onboarding fails because complexity arrives before confidence.
A human-centered onboarding and enablement framework focused on reducing abandonment through confidence-first learning design.
The Problem
Most onboarding systems compete directly with the work users are already trying to accomplish. New employees, customers, and teams often enter unfamiliar systems under time pressure, uncertainty, and competing priorities. When onboarding prioritizes feature exposure over immediate success, users are more likely to disengage before reaching meaningful value. Adoption is not only influenced by product capability. It is heavily influenced by confidence, momentum, and whether users feel capable of succeeding inside the system quickly.
The Framework
Confidence Before CompliancePeople absorb information differently once they feel capable, welcomed, and emotionally grounded. Confidence Before Compliance prioritizes early momentum and practical familiarity before introducing deeper process, policy, or system complexity.The Friction LoopMost onboarding failures are not caused by unwilling users. They emerge when onboarding competes with real work, pressure, uncertainty, and cognitive overload. The Friction Loop maps how confusion compounds into abandonment before meaningful success occurs.The Right Now Branching ArchitectureThe Right Now Branching Architecture organizes onboarding around immediate user goals instead of feature-first exploration. By helping users accomplish a real task first, systems can introduce additional tools, workflows, and complexity gradually through contextual learning.
View the Onboarding Philosophy in Figma
Key Design Principles
Progressive DisclosureIntroduce complexity gradually as confidence increases. Prioritize immediate usability before exposing advanced workflows, settings, or system depth.Momentum CreationEarly success increases confidence, curiosity, and long-term engagement. Onboarding should create forward motion before attempting comprehensive education.Contextual LearningPeople retain information more effectively when learning is connected to a real task or immediate goal. Instruction becomes more useful when delivered inside active workflows.Guided ExpansionAfter a user completes an initial task successfully, additional tools and capabilities can be introduced progressively. Expansion should feel optional, supportive, and low-pressure.Behavioral OnboardingOnboarding systems should account for pressure, uncertainty, time constraints, and cognitive overload. User behavior is often shaped more by emotional state than by product capability alone.Reusable Enablement SystemsEffective onboarding systems scale through reusable templates, modular learning paths, milestone-based growth systems, and adaptable infrastructure that supports long-term adoption.
Why This Matters
Most onboarding systems are designed around feature exposure instead of human behavior under pressure. When onboarding competes with deadlines, uncertainty, and real work, users are more likely to disengage before reaching meaningful value.A confidence-first onboarding approach can help reduce abandonment risk, improve activation, lower cognitive overload, and increase long-term adoption. By treating onboarding as reusable operational infrastructure rather than isolated training sessions, organizations can build scalable enablement systems that support both immediate success and sustained platform growth.
The Artifact
View the Onboarding Philosophy in Figma
Rodger
UX and Systems Design
A systems-first exploration of real-time coordination, designed before gig platforms existed and built around clarity, accountability, and human judgment.
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 a concept exploration in real-time coordination, designed years before gig work became app-based. The goal was to imagine a dispatch and task-tracking system that could scale without losing clarity, accountability, or human judgment.The result was a role-aware dispatch model built around communication, clear handoffs, and decision support rather than blind automation.
My Role
• Mapped the complete task lifecycle from request → assignment → reroute → resolution
• Designed system logic to handle real-world edge cases, including access failures, time overruns, and driver no-shows
• Defined and separated user-facing, driver-facing, and operations-facing responsibilities
• Sketched administrative tools for tracking service status, notifications, and expenses
• Intentionally prioritized human judgment and clarity over full automation in service handoffs
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 well before it was formalized in my career
Outcome & Impact
Rodger anticipated core patterns of modern gig-economy platforms years before they became mainstream. The work demonstrates early strength in scalable coordination design, role separation, and operational clarity under uncertainty.
Artifacts
These hand-drawn logic maps and system notes predate modern design tools. They document how I reasoned through coordination frameworks, role logic, and task routing using paper sketches and flow diagrams.
• Role definitions and feature notes for the Rodger platform
• Task assignment logic balancing user needs with driver proximity
• Early flowcharts for driver notifications and task resolution routing
Pantrii
Human-Centered Inventory & Planning System
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.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
• Designed the brand identity, UI mockups, and core interaction flows
• Built a component system centered on calm visuals, legible hierarchy, and predictable patterns
• Mapped user flows for scanning, inventory management, and recipe-triggered planning
• 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 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 early 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