Interviews with Ping Chen

I became a designer because I like making ideas usable. I started with product design training, then moved into UX because I wanted to solve problems at the behavior and experience level. Over time, I focused more on design strategy, research synthesis, and building clear systems.

My top priorities are clarity, low cognitive load, and real world usefulness. I start with research and constraints, then prototype early and iterate fast. My visual style is calm and structured, with clear hierarchy and simple language.

Mostly curiosity and focus. The most exciting part is when patterns start to appear from research and the solution becomes clear.

My strength is connecting human behavior with product decisions. I am good at synthesis, storytelling, and cross functional communication. Working across different projects and domains taught me how to make tradeoffs and keep a concept realistic.

I want to keep building products that support daily wellbeing, especially for neurodiverse users. My dream project is a multi platform support tool that combines lightweight tracking with helpful interventions, while staying calm and easy to use.

Learn the basics well: hierarchy, flow, and interaction patterns. Talk to real users early. Show your decisions and tradeoffs, not only final screens. Keep building, keep shipping, and ask for critique.

Stay close to the real problem. Remove features that do not support the goal. Write clearly and document why you made choices. Simple work is usually the hardest and most valuable.

I usually start by reviewing priorities and feedback. Then I do design work in blocks: research synthesis, wireframes, prototypes, and UI refinement. I end the day by documenting decisions and preparing the next steps.

I follow trends to understand expectations, but I do not design for trends. For me, usability and clarity matter more. A calm, accessible experience lasts longer than a visual trend.

Good design is easy to understand, easy to use, and respectful of time and attention. A user should know what to do next without confusion. It should also work well in real constraints, not only in a perfect demo.

It is ready when the main flows are clear, the core problem is solved, and the design holds up in testing. I stop when further changes add complexity without improving the outcome.

Aurora is one of my most meaningful projects. It is a music based emotional support concept for ADHD users. It connects mood logging, pattern insights, state matched playlists, and rhythm synced visuals to support focus and regulation.

I do not have only one. I admire designers and teams who make complex systems feel simple and calm, especially in healthcare and productivity products.

I live in the United States. I work across cultures and languages, and that pushes me to write and design more clearly. Music is part of my daily routine, so the Aurora concept also came from observing how people actually use music to manage their day.

I value direct feedback, fast iteration, and clear documentation. I like working with teams who care about users and outcomes. I believe good collaboration comes from shared goals, simple communication, and realistic scope.

I try to contribute by focusing my work on accessibility and inclusive design. I share process learnings with other designers, and I am interested in supporting projects that improve daily wellbeing for underserved or overlooked groups.

Participating helped me present my work in a clearer and more structured way. It also helped me compare my design thinking with global standards. Three benefits of design awards are: they increase visibility, they create credibility for new opportunities, and they push designers to communicate intent, process, and impact more clearly.

My main focus was reducing cognitive load while making emotional patterns visible. I wanted users to log a moment in seconds, then receive clear insights and state matched playlists that support focus, calm, or task initiation.

Aurora can be extended into a working product by integrating with existing streaming services, refining personalization models, and running longer pilot studies. I also plan to explore accessibility options and personalization controls so users can adjust the experience to their needs.

The concept was developed over approximately 8 weeks, including research, synthesis, wireframing, and high fidelity prototyping.

This project was self initiated. I pursued it after learning how often people with ADHD rely on music for regulation, and how current platforms do not support the emotional context behind listening.

Aurora is currently a concept and prototype, not in production. It is designed to be feasible for future development, either independently or through partnership with a music platform or wellness organization.

I am interested in products that support daily wellbeing through small, low effort interactions. Music is already part of daily life, so it is a natural channel for building sustainable support habits.

The work was influenced by calm, low stimulation wellness experiences and clear journaling tools. More importantly, the strongest influence came from user stories and real listening routines shared during interviews.

Aurora is designed for people with ADHD, as well as users who experience distraction, overstimulation, or frequent mood shifts and want lightweight support through music.

Aurora does not treat music as entertainment first. It links each listening moment with multi dimensional mood logging, then turns those moments into daily patterns and state matched playlists. It also highlights “moments that mattered,” instead of showing all entries equally.

Aurora refers to a gentle shift in light. The name reflects the design goal: small changes in sound and rhythm can help shift attention and emotional state in a calm way.

I used Figma for wireframes, interaction design, and prototyping. I also used standard research tools for interviews, note taking, synthesis, and affinity mapping.

The most unique aspect is the system that turns fleeting listening moments into reusable emotional knowledge: a song is linked to mood state, context, and time, then summarized into patterns and personalized support.

This was primarily an independent concept project. I collaborated with participants during interviews and concept feedback sessions, and used their input to shape the interaction model and information hierarchy.

Technology enables personalization and pattern recognition. It connects mood logs, time, and track metadata, then generates state matched playlists and simplified insights. Technology is used to reduce effort, not to add complexity.

Yes. I conducted qualitative interviews with 10 people with ADHD to understand real listening behavior, pain points, and coping strategies. The findings directly shaped features such as quick multi mood logging, highlighted moments, and daily trend summaries.

The main challenge was balancing emotional accuracy with low effort interaction. Early versions used more mood dimensions, but testing showed the flow was too long for ADHD users. I reduced inputs to core dimensions, kept logging fast, and shifted emphasis to insight first summaries.

Aurora is a concept that connects wellbeing, interaction design, and responsible personalization. I submitted it to share the idea globally and to test the clarity of the design narrative against international standards.

I learned to simplify without losing meaning. The biggest improvement was focusing on the few interactions that create long term value, and removing elements that looked impressive but did not reduce cognitive load.

Aurora is designed to be supportive and non judgmental. It does not aim to diagnose or replace clinical care. The goal is to provide an approachable, low effort tool that helps users recognize what supports them and apply it in daily life.

I like turning messy human problems into clear experiences. Design lets me make ideas usable, not just interesting.

I chose it. I was always drawn to making and improving things.

I design digital products and human-centered experiences. I want to do more work in health, wellbeing, and AI-enabled tools.

I do not think in terms of legends. For young designers, focus on fundamentals, learn from real users, and ship work with clear impact.

A good designer delivers a clean solution. A great designer frames the right problem, aligns stakeholders, and makes the solution work in real life.

Good design is clear, usable, and respectful of people’s time and attention. I evaluate it by outcomes, usability, and whether it reduces friction in real scenarios.

Good design saves time, reduces errors, and builds trust. It makes products easier to use and easier to adopt.

I would design more tools for neurodiverse users and caregivers. I want to focus on daily routines, not only crisis moments.

A cross-platform support tool that connects small interventions with long-term habit building. It would combine data, coaching, and simple daily actions.

Consistency and honest feedback. I iterate fast and stay close to real user needs.

I learn from designers who make complex systems feel simple. I also learn a lot from researchers and engineers who care about user outcomes.

I like designs that reduce cognitive load and remove unnecessary steps. Clear navigation, strong hierarchy, and calm visual language are always impressive.

Aurora is one project I am proud of. It reframes music as a regulation tool by connecting mood logs, pattern insights, and listening support.

Do more critique and more testing. I improved by documenting decisions, learning from failures, and building prototypes early.

I would likely work in research or education. I enjoy studying human behavior and making knowledge practical.

Design is structured problem solving for humans. It is the work of making choices clear and experiences usable.

Mentors, teammates, and users who shared honest feedback. Good work is always collaborative.

Working on real products with real constraints. Constraints taught me focus and tradeoff thinking.

Time, uncertainty, and learning new domains quickly. I handled them by simplifying scope and iterating with feedback.

Start with the problem and the user. Show key decisions, tradeoffs, and what changed after research and testing.

I want to keep building AI enabled experiences with strong human grounding. Expect more work that connects research with practical daily tools.

To make useful products that respect people’s attention and improve daily life.

I prefer to focus on responsibility. People can expect clarity, integrity, and decisions backed by evidence.

Design can reduce barriers and include more people. It can make services easier to access and safer to use.

I am exploring how small, low effort interactions can support long term behavior change. I am also interested in calm, accessible AI experiences.

Projects where user feedback directly changed the outcome. I enjoy seeing a concept become something people can actually use.

More inclusive design by default. Also more honest evaluation of AI, with fewer gimmicks and more real value.

Toward systems thinking and responsible AI. Designers will need to handle complexity while keeping experiences simple.

It depends on scope. I like short cycles: research, prototype, test, and iterate, then refine.

I start with users and constraints. I define the core job to be done and the success metrics.

Make it clear. Make it useful.

Both. Trends influence expectations, but good design should still be rooted in real needs.

Technology is a tool, not the goal. I use it only when it improves the user outcome.

Figma for UI and prototyping. I also use common creative tools for visuals and documentation.

They shape emotion, readability, and comfort. In wellness work, I prefer calm palettes and low stimulation visuals.

I like questions about tradeoffs and constraints. Those reveal the real design thinking.

I ask: what problem does it solve, and for whom. Then I look at how it reduces steps and confusion.

Yes, I believe in co design. My ideal partners are researchers and engineers who care about user outcomes.

Users who explain their daily routines in detail. Real stories shape better decisions than assumptions.

Books on usability and behavior helped a lot. I also learn from research papers and case studies.

By repetition and reflection. I study feedback, improve my process, and keep practicing fundamentals.

I would like to speak with researchers in attention and learning science. I want to understand how small cues can support focus.

Awards are encouraging and helpful for sharing work. I try to stay focused on the users and the craft.

I like soft blues and greens. I enjoy quiet places with nature. I like simple food and calm seasons like early autumn. I prefer brands that are clear and thoughtful.

I once tested a prototype that looked perfect on screen, but users ignored the main button completely. It reminded me that design is not what I intend, it is what people do.

A clear problem and good feedback. Small progress each day keeps me motivated.

I liked drawing and making things, but I did not know it would become design. Looking back, the curiosity was always there.

It is hard to predict. I hope we build tools that support human wellbeing and protect attention, not exploit it.

I design to make complex things feel calm and usable. I believe small daily support tools can create real change over time.

I work as an independent designer and collaborate with teams and clients on product strategy, research synthesis, and UX design. My work often supports early stage concepts and real products, from framing the problem to prototyping and refinement.

Design is structured problem solving for humans. It is the work of making decisions clear, reducing friction, and creating outcomes that people can trust.

I enjoy designing products that connect behavior, emotion, and daily routines. I am especially interested in wellbeing tools and AI enabled experiences that stay calm, practical, and respectful of attention.

Aurora is one of my favorite projects. It reframes music as an emotional regulation tool for people with ADHD by connecting mood logging, pattern insights, and state matched playlists, plus rhythm synced visuals for grounding during listening.

My early professional work focused on UX flows and interface components for digital products, including information architecture, interaction patterns, and iterative prototyping with cross functional teams.

My favorite platform is mobile, because small interaction choices can have a big impact on daily habits. I also like working with data informed personalization when it is transparent and user controlled.

I feel most creative after I have a clear problem statement and real user stories. Constraints and specific scenarios usually unlock better ideas than open ended brainstorming.

I focus on clarity, cognitive load, and the flow from intention to action. I also focus on how a product supports a user over time, not only in a single session.

Curiosity and focus. I like the process of turning uncertainty into a structured direction.

Relief and excitement, especially when the design is simple to use and people understand it quickly.

A successful design solves the right problem, works under real constraints, and helps users reach outcomes with less effort and less confusion.

I look at the problem fit, usability, and hierarchy. If a user cannot understand what to do in the first seconds, the design needs improvement.

Designers should reduce barriers and include more people. They should also avoid creating addictive or harmful patterns, and design with long term impact in mind.

Design is moving toward systems thinking, responsible AI, and more focus on outcomes. The future will require designers to handle complexity while keeping experiences calm and understandable.

I do not have a recent physical exhibition. I mainly share work through professional case studies and design awards. I would like to present more work publicly in the future when the right opportunity appears.

My main source is real user behavior and daily routines. I also learn from product teardowns, research papers, and well designed systems that make complex tasks feel simple.

My style is calm, structured, and minimal. I use clear hierarchy, low stimulation visuals, and simple language. My approach is research first, then rapid prototyping and iteration based on feedback.

I live in the United States. Working across cultures has helped me pay attention to context, language, and inclusivity. A challenge can be aligning different expectations, but it often leads to clearer design decisions.

I work closely with stakeholders to align goals, define scope, and translate user needs into product decisions. I share early prototypes, iterate quickly, and document tradeoffs clearly.

Choose designers who ask strong questions, validate assumptions with users, and can explain decisions clearly. A good collaboration includes clear constraints, fast feedback loops, and shared success metrics.

I start with the user problem and constraints. Then I do research and synthesis, define the core experience, prototype flows, test and iterate, and finally refine interaction details and visual system.

I prefer simple, functional items: a good ergonomic chair, a task lamp, a water bottle that is easy to clean, noise reducing headphones, and a minimal notebook for quick capture.

A typical day includes prioritizing tasks, reviewing feedback, designing and prototyping, and writing clear documentation for stakeholders. I usually end the day by organizing notes and planning the next iteration.

Learn fundamentals, test early, and write clearly. Build small projects that show reasoning and tradeoffs. Focus on outcomes, not only visuals.

A positive is creating real value for people. A negative is ambiguity and changing constraints, but that also keeps the work challenging and meaningful.

Reduce cognitive load. Make the next step obvious.

Problem framing, communication, systems thinking, and iteration. Visual skills matter, but clarity and decision making matter more.

Figma for UI and prototyping, common creative tools for visuals, and simple research tools for interviews, notes, and synthesis. I also rely on structured writing and documentation.

I break work into short cycles and set clear milestones. I prioritize high impact decisions first, then refine details later.

It depends on scope. I usually work in phases: research and framing, prototyping, iteration, and refinement. The timeline can range from weeks to months.

“How do we make this simpler without losing value?”

Working in agency style environments was important because it trained me to handle multiple projects, align stakeholders, and ship solutions under constraints.

I have worked with cross functional teams and clients through product design roles and contract work. The common theme has been complex workflows and the need to translate research into practical UX decisions.

I enjoy work that combines research and design strategy with practical product execution, especially when it supports wellbeing or reduces friction in daily routines.

I plan to continue designing human centered digital products, with more focus on wellbeing and responsible AI experiences.

Both. I can work independently, but I prefer collaboration with researchers, product managers, and engineers to ensure the design works end to end.

I am continuing to explore how small interventions, like music and lightweight logging, can support long term self regulation and reduce overstimulation in everyday life.

pingc1008@gmail.com

I care about designing calm, inclusive experiences that respect attention. I aim to create work that is easy to understand, easy to use, and meaningful over time.

Aurora reframes everyday listening as a form of lightweight emotional support. Many people already use music to focus, calm down, start tasks, or recover from stress. However, most music platforms treat these behaviors as entertainment preferences rather than regulation patterns. Aurora starts from a different point of view: listening habits can carry emotional information, and that information can help users understand what supports them.For neurodiverse wellness design, this is an important shift. Support does not always need to feel clinical, heavy, or separate from daily life. It can be built into habits people already have. Music is familiar, accessible, and emotionally meaningful. By connecting music with mood journaling and pattern recognition, Aurora turns small listening moments into a clearer self regulation practice.I think designers in digital wellness can learn two things from Aurora. First, low effort interaction matters. If a tool asks too much from users during moments of stress or distraction, it will not be used consistently. Second, insight is more valuable than data display. Aurora does not ask users to analyze every entry. It highlights what mattered, such as when music helped reduce stress or improve focus.The broader cultural message is that neurodiverse support should respect real daily behavior. Instead of forcing users into rigid wellness routines, design can meet them through tools they already use.

Aurora’s state matched playlist model is based on the connection between three types of information: the music a user is listening to, the emotional state they log in that moment, and the later pattern of whether that music seemed to help. Each journal entry links a track with a time stamp, mood intensity values, and a short contextual note. Over time, these entries create a personal map of how different sounds relate to focus, calm, stress, or task initiation.This is different from genre based recommendation. A song is not categorized only as pop, ambient, or electronic. In Aurora, the meaning of a song is shaped by the user’s lived experience. For one user, a steady beat may help start work. For another, the same tempo may feel too activating. The system therefore learns from personal emotional context, not only from listening history.In practice, Aurora uses this pattern to generate playlists for a target state. For example, if a user wants to focus, the app can prioritize tracks that were previously linked with improved focus or reduced distraction. If the user wants to calm down, it can surface tracks associated with lower stress or more stable emotional patterns.For neurodiverse communities, this approach suggests a more respectful model of personalization. Instead of assuming that one “focus playlist” works for everyone, the product learns from individual regulation patterns. This can influence digital health tools by moving them away from generic content libraries and toward adaptive support based on real user context.

The core design philosophy behind Aurora is simple: reduce effort, reveal patterns, and support regulation through familiar behavior. Every major feature follows this idea. The playlist system makes music more intentional. The journal captures emotional context without requiring long writing. The trend view turns scattered moments into simple insights. The visual mode adds a gentle sensory anchor during listening.What holds these features together is the belief that support for ADHD should not create more work for the user. Many wellness tools require users to stop, reflect deeply, categorize themselves, and maintain routines with high discipline. That can be difficult for people who already manage fragmented attention. Aurora tries to lower that barrier by connecting support to something many users already do every day: listen to music.Receiving the Iron A’ Design Award is meaningful because it recognizes this type of daily need as worthy of serious design attention. ADHD is often discussed through productivity or clinical treatment, but many lived challenges happen in small moments: starting a task, calming racing thoughts, recovering from overstimulation, or remembering what helped last time.I hope this recognition communicates to the neurodiverse community that their daily experiences deserve thoughtful products. Design can take these needs seriously without making the experience feel medical, heavy, or stigmatizing.

The most difficult challenge was balancing emotional depth with simplicity. Emotional states are rarely simple, especially for users with ADHD. Someone may feel stressed, motivated, distracted, and tired at the same time. A single mood label does not capture that complexity. At the same time, asking users to complete a long emotional assessment creates too much friction.One pivotal decision was to use a multi mood slider system rather than a single mood picker. This allowed users to express mixed states through a few core dimensions. However, the first version included too many emotional dimensions. Through feedback and testing, I realized that the interaction felt too long. For ADHD users, the logging moment must be fast enough to complete before attention shifts.I reduced the input to fewer, more relevant mood dimensions and made the journal entry short. The design moved away from full diary writing and toward quick moment capture: current music, mood intensity, and a brief note. Another important decision was to make the summary page insight first. Instead of showing every entry equally, Aurora highlights the moments that matter.This process changed how I think about accessible emotional design. Accessibility is not only about readable text or clear buttons. It is also about emotional effort. A good support tool should respect the user’s limited attention, energy, and patience, especially during vulnerable moments.

The project was developed over about eight weeks. I began with semi structured interviews with ten adults with ADHD, focusing on how they use music during work, emotional shifts, task initiation, and overstimulation. At the beginning, I thought the main solution would be better mood based playlists. The research quickly showed that the problem was deeper.Participants described using music as a coping tool, but they also described frustration. Generic focus playlists did not always work. Sometimes a song helped unexpectedly, but later they could not remember which song it was or why it helped. This redirected the project from a playlist app toward a music memory and regulation system.The biggest design shift was moving from “recommend music” to “help users understand what music does for them.” That led to the journal module. Each listening moment could become a small data point: what was playing, how the user felt, and what was happening. Then the product could turn those moments into patterns.Another redirection came from input complexity. Early mood tracking concepts were too detailed. They captured more data, but they were not realistic for daily use. I simplified the interaction and focused on repeatable behavior.The final prototype was organized around three modules: state matched playlists, music journaling with trend insights, and rhythm synced visual listening. Together, they translate a subjective relationship with music into a coherent user experience: capture the moment, learn from the pattern, and receive support when needed.

Aurora is currently a concept and interactive prototype, but I see a clear path for it to evolve into a real product. The next step would be deeper testing with neurodiverse users over a longer period of time. The prototype shows the interaction model, but a real product would need to study whether users continue logging moments, whether the playlist recommendations improve over time, and whether the visual mode supports focus without overstimulation.Technically, Aurora could integrate with existing music streaming platforms. It would not need to replace them. Instead, it could add a regulation layer on top of listening behavior by connecting track metadata, mood input, and user feedback. The user would remain in control, with clear options to edit patterns, remove entries, or adjust what the system learns from.My larger vision is for wellness tools to become more practical, personal, and low effort. Many people need support during ordinary moments, not only during crisis moments. For neurodiverse individuals, daily support might mean starting a task, staying grounded, or remembering what helped yesterday.Aurora suggests that everyday tools can become more supportive when they understand context. If developed further, I hope it can raise expectations for digital wellness products: less generic advice, less pressure to perform wellness, and more adaptive support that fits naturally into daily life.

One thing I would like the broader design community to understand is that Aurora is not about making music feel therapeutic through branding. It is about respecting the real ways people already use music to regulate themselves. Many users do not describe this behavior in clinical language. They simply say, “This song helps me start,” or “This track calms me down.” Aurora was designed to honor those small moments and make them easier to reuse.The intention was also to avoid turning self regulation into another demanding task. Many wellness products ask users to track, analyze, improve, and optimize themselves. For people with ADHD, that can become a burden. Aurora tries to do the opposite. It asks for a small input and returns a clear benefit: a useful playlist, a highlighted moment, or a simple emotional pattern.I also want to emphasize that this project does not claim to replace clinical care. It is a daily support concept. Its value is in making emotional self awareness more approachable and less judgmental.For the design community, Aurora is a reminder that inclusive design often lives in details: the number of choices, the length of a form, the speed of an interaction, the tone of a sentence, and the amount of visual stimulation on screen. These small decisions can decide whether a tool feels supportive or exhausting.

The multi mood slider system was developed because the research showed that emotional states are often blended. Participants rarely described themselves with one clear label. They might feel anxious but motivated, tired but restless, calm but unfocused. A single mood selection would make the interface simpler, but it would flatten the experience too much.The first version explored a wider emotional model with more dimensions. It was more expressive, but it created a long input process. That was a problem for the user group. If logging takes too much time, it becomes another task to avoid. Through iteration, I reduced the system to fewer core dimensions that are more relevant to everyday ADHD regulation, such as focus, calm, stress, and distraction.To prevent the added nuance from becoming cognitive friction, I made three choices. First, the sliders are quick and visual. Users do not need to write a full explanation. Second, the app does not force every emotion to be filled out. Third, the trend view does not show raw slider data as a complicated chart. It translates the entries into simple patterns and highlighted moments.The blended gradient is used as a visual summary of mixed states, not as a code the user must decode. The goal is to make emotional complexity visible while keeping interpretation easy.

The visual language of Aurora was guided by one principle: the interface should support regulation, not compete with it. Because the product is designed for users with ADHD and other users who may experience distraction or overstimulation, the aesthetic needed to be calm, low contrast, and easy to scan.Color decisions were based on emotional clarity but used with restraint. Mood colors appear as soft gradients and small accents rather than aggressive full screen signals. This allows the product to represent emotional states without making the interface feel intense. The journal cards use blended color to suggest mixed emotion, while the overall system remains quiet and readable.Motion was treated carefully. The rhythm synced visuals respond to BPM and audio energy, but the movements are minimal, repetitive, and predictable. I avoided sharp transitions, excessive particles, and high stimulation effects. Users can choose from different visual modes because regulation is personal. Some people need calm motion, while others may benefit from a more active rhythm for task initiation.The guiding principles were clarity, predictability, and sensory comfort. Every visual decision had to answer a question: does this help the user stay grounded, or is it only decorative? If it did not support the emotional purpose of the product, it did not belong in the interface.