2022.03 — 2022.07
The Account Center Website allows users to manage subscriptions and products, offering a personalized experience and streamlined navigation to improve engagement and customer satisfaction.
Get to know more about persona, user journey and their pain point
Define questions and problems
Figure out the solution
Validate ideas(Tracking data & User Interview & Usibility Test)
Enhance user retention and engagement through personalization, interactive features, and targeted promotions. Optimize business performance with data-driven insights to improve products, marketing, and reduce churn. Strengthen brand identity for a more familiar and trustworthy experience. Improve usability with intuitive navigation, clear information hierarchy, and seamless subscription management.
The company is transitioning from a point-based system to a subscription model and integrating all sound-related products into a unified membership center. Also, the previous interface lacked clarity, causing users to struggle with navigation and account management. The business goal is to improve user retention, self-service efficiency, and marketing effectiveness by making the membership center a seamless hub for product and subscription management.
Product Designer
User Flow
Wireframe
Design System
UI Design
Iterations
Figma
1 PM
1 Front-End Engineer
Problem Statement
The company had multiple web and mobile products under different domains, leading to inconsistent login and account management experiences. Users often felt confused about where to manage their profiles, linked accounts, or notifications. Internally, this fragmented setup also caused redundant development and support efforts.
We needed to create a centralized Account Center that provides a unified user experience across products, while being flexible enough to scale with future needs.
How We Identified the Core Problems
Due to limited resources, we did not conduct formal user interviews. Instead, we gathered insights through internal discussions, platform usage observations, and competitor analysis.
Based on these inputs, we synthesized the following five key problem areas, prioritized by their frequency of mention and potential business impact.
1. Lack of Personalization and Engagement Reduces User Retention
The membership center lacks personalized experiences and fails to recommend suitable products or services based on user behavior. There is no tailored promotion or notification system based on user preferences, reducing incentives for purchases and renewals. The absence of interactive features discourages users from revisiting the membership center, negatively impacting retention rates.
2. Insufficient Data Analysis Limits Business Growth Potential
The company struggles to effectively collect and analyze user behavior data, hindering product optimization and market decision-making.
Marketing strategies lack data-driven insights, leading to inefficient allocation of marketing resources.
The membership center fails to serve as a growth-driving tool, limiting potential revenue opportunities.
Furthermore, we lack insight into why users choose to discontinue using our product.
3. Lack of Brand Identity and the Cold Perception of Tech Products
Lack of brand recognition enhancement, and technology products are often abstract or overly technical, giving a cold and unfamiliar impression.
4. Disorganized Information Architecture Reduces Readability and Management Efficiency
The membership center's information architecture is disorganized, making it difficult for users to navigate and understand the content.
Key information (such as billing, subscription status, and product management) lacks a clear hierarchy, reducing readability.
After product integration, the existing system fails to effectively support all types of subscriptions and management functions.
5. Switching from a point system to a membership-based system.
Problem Framing & How Might We
In the original experience, users had to jump between multiple pages to find basic account information—such as subscription status, product ownership, and billing records. This fragmented structure caused confusion, reduced user confidence, and led to unnecessary support inquiries.
To guide our redesign, we framed the core challenge as:
How might we help users clearly understand and manage their subscriptions, purchases, and billing in one place—without overwhelming them or sacrificing future scalability?
This question helped us focus on building a centralized, modular Member Center that not only solves immediate usability issues but also prepares the platform for future product growth.
Design Goal
The goal of this project was to create a unified Account Center to address the fragmented cross-product account experience, disorganized information architecture, and lack of personalization or engagement in the current system.
The design aimed to:
Design Strategy
To better align our solution with user needs, we developed user personas by drawing on existing insights from Noise Eraser’s user interviews, given the overlap in user base with the Member Center. This approach helped us ground our design decisions in real user behaviors and expectations.
Persona 1: Audio Post-Production Manager – Emily Tsai
Age: 37
Position: Head of Post-Production at a Podcast Production Company
Industry: Podcast Audio Production and Editing Services
User Scenario:
Emily has purchased DeepWave’s noise reduction tool, audio normalization module, and cloud-based audio conversion API. She uses the Account Center to manage subscription statuses, check usage records, and invite editors to join the account.
Goals:
Pain Points:
Persona 2: Solo Founder in Voice Technology – Tony Chang
Age: 32
Role: Founder / Developer / User (Solo Operator)
Company Size: 1-person business
Industry: Voice transcription, audio enhancement tools, AI audio solutions
Background:
Tony is a solo entrepreneur building his own audio-based SaaS product. He purchased multiple DeepWave modules such as speech-to-text services and the labeling platform to support both product development and freelance client work. As the only user in his account, he handles everything from setup to daily use.
Goals:
Pain Points:
Chosen (A):
Design an interactive Member Center that integrates personalized content, promotional tools, and brand storytelling—featuring:Integrate personalized product recommendations, promotions, and engagement content into the Member Center and homepage using mascot-enhanced UI
Not Chosen (B):
Basic static interface with minimal promotion or brand interaction.
User Perspective
Through internal observations and feedback from our customer support team, we found that users often felt disconnected from the brand and unaware of available benefits. New users didn’t know where to begin after signing up, while existing users had no visibility into referral or coupon status. The Member Center, in its prior state, felt passive and offered little reason to return.
These insights guided our decision to redesign the Member Center as an engagement-driven dashboard, making value offerings more visible, encouraging repeat visits, and supporting trust-building in early brand stages.
We launched a modular Member Center UI that includes:
Reference: Notion, Shopee, Adobe — all use dashboard-style entry points for retention and engagement
Why Choose Option A Over Option B?
Chosen (A):
Visually highlight the savings in the yearly plan (e.g., "Original Price: TWD 1,490 → Now: TWD 1,390") to encourage users to upgrade by reinforcing the “buy more, save more” mindset.
Not Chosen (B):
Display only flat pricing options (e.g., monthly and yearly plans) without emphasizing savings or comparative value.
Rationale:
Trade-off:
Pros of A:
Cons of A:
Pros of B:
Cons of B:
PM / Engineering Collaboration:
Final Decision:
We implemented a dual-option pricing card, where:
This makes savings tangible and nudges users toward committing to a longer-term plan.
Validation:
Benchmarked similar patterns from Spotify, Canva, and Adobe
Trade-Off Analysis — Reducing Form-Filling Effort to Boost Engagement
Why Choose Option A Over Option B?
Chosen (A): Progressive Disclosure – Ask users “How did you hear about us?” after initial engagement
Not Chosen (B): Early Form-Filling — Ask “How did you hear about us?” during sign-up
Rationale:
Asking non-critical questions too early can create unnecessary friction during sign-up, which is a sensitive conversion point. By deferring this question until the user has completed a meaningful action, we reduce perceived effort and improve the likelihood of a genuine response.
Although we did not conduct direct user interviews, our design approach was informed by established UX research and behavioral psychology. We recognized that during early onboarding—especially at the point of registration—users are often hesitant to commit too much effort upfront, particularly when it comes to filling out non-critical information like “How did you hear about us?”
To avoid unnecessary friction and reduce the risk of early abandonment, we chose to defer such questions until after users had completed a key action and begun to explore the product. At that point, trust has started to form, and users are more likely to respond.
We used lightweight, skippable prompts that feel conversational and non-intrusive, ensuring that the experience remains smooth while still allowing us to gather valuable marketing insights over time.
Minimize the number of fields and only ask what’s truly necessary at the beginning.”— Nielsen Norman Group, “Form Design Quick Fixes”
Key takeaways:
Trade-off:
Pros of A:
The timing is intentional—by this point, the user has developed initial trust in the product, making them more willing to respond.
The prompt is designed to feel like a lightweight, conversational message—non-intrusive and seamlessly integrated into the experience.
It can also be made skippable, preventing negative emotions from disrupting the core user journey.
Higher response rate, better data accuracy, lower drop-off during onboarding.
Cons of A: Slight delay in data collection; requires additional logic to trigger the prompt contextually
Pros of B: Immediate access to user acquisition data
Cons of B: Increased onboarding friction; lower form completion and user satisfaction
Collaboration with PM & Engineers:
Business Constraints:
Final Decision-Making Process:
Validation:
Our design decisions are aligned with best practices observed in platforms like Duolingo, Notion, Figma, and Superhuman, which all utilize progressive disclosure and delayed data capture to optimize UX.
After the user completes a key action (e.g., posting their first job or browsing the recommendation list), a short, guided prompt appears.
2.2. Main Purposes of Using a Progress Bar on a Marketing Page
Why Choose Option A Over Option B?
Chosen (A): Use a Progress Bar on the Marketing Page
Not Chosen (B): No Progress Indicator / Static Multi-step Form
Rationale:
We introduced a visual progress bar to improve form completion by leveraging psychological drivers such as the sunk cost effect and goal-gradient effect. When users see they’ve already completed more than 50%, they feel motivated to finish. Real-time progress feedback also reduces uncertainty and perceived effort, especially on marketing pages where abandonment risk is high.
After the user completes a key action (e.g., posting their first job or browsing the recommendation list), a short, guided prompt appears.
Pros of A:
Cons of A:
Pros of B:
Providing Real-Time Feedback
Cons of B:
PM/Engineering Collaboration:
Final Decision:
We implemented a step-based progress bar paired with contextual prompts like:
“You're 80% done—click next to unlock your free gift!”This design capitalized on user psychology and provided a clearer sense of progression. We also paired visual progress with micro-rewards, such as coupons or entry to lucky draws, at key thresholds (e.g., 50%, 100%).
Validation:
Why Choose Option A Over Option B?
Chosen (A):
Design with explicit privacy cues and user control over data
(e.g., displaying privacy policy, explaining data usage, providing edit/delete options)
Not Chosen (B):
Silent data collection with no explanation or visible control
(e.g., not telling users how their data is used or omitting privacy-related UI elements)
Rationale:
In today's digital environment, users are highly sensitive to how their personal data is handled. Without transparent communication, even routine information collection may lead to hesitation or drop-off. By proactively showing privacy policies, encryption assurances, and giving users control over their data, we reduce anxiety and build trust—ultimately increasing the chance that users will complete onboarding or provide additional information.
Trade-off:
Pros of A:
Cons of A:
Pros of B:
Pros of B:
PM / Engineering Collaboration:
Final Decision:
We included a simple, reassuring privacy section in key UI areas:
This transparent, user-centric approach improves both trust and conversion.
Validation:
Why Choose Option A Over Option B?
Chosen (A):
Designing a multi-step unsubscription flow with benefit reminders, retention offers, and feedback collection
(e.g., "Are you sure you want to leave? You’ll lose access to premium features like X and Y." + options like "Pause subscription" or a one-time discount)
Not Chosen (B):
Allowing immediate, single-click cancellation with no additional steps or information
Rationale:
While we respect the user’s freedom to unsubscribe, a frictionless one-click cancellation can lead to impulsive decisions and unnecessary churn. By gently guiding users through a short flow that reminds them of what they’re giving up, offering a reason to stay, and asking why they’re leaving, we create a moment of reflection. This both improves retention and provides valuable insight for product improvement—without feeling overly manipulative.
Trade-off:
Pros of A:
Cons of A:
Pros of B:
Cons of B:
PM / Engineering Collaboration:
Final Decision:
We implemented a three-step cancel flow:
Validation:
Benchmarked similar flows from platforms like Spotify, Netflix, and Duolingo, which all use multi-step cancel flows with soft retention nudges
Why Choose Option A Over Option B?
Chosen (A):
Provide a centralized Member Center that shows purchased products, subscription status, and payment history, using a card-based layout for future scalability
Not Chosen (B):
Keep navigation minimal and separate — place order details and subscription settings under different pages with less visual integration
Rationale:
While we didn’t conduct formal user interviews, we reviewed internal feedback and inferred from common support queries that users often felt confused about what they had purchased, what they were subscribed to, and when their next billing date would be. The existing experience—where order and subscription details were scattered across multiple pages—made it difficult for users to get a clear picture of their account status.
To reduce this confusion and build user trust, we decided to design a centralized Member Center that offers a clear, visual summary of ownership, billing, and subscription data. By doing so, we aimed to make users feel more in control and less anxious about managing their account.
We wanted to empower users by giving them clarity and control over their purchases and subscriptions. Instead of scattering information across multiple pages, we opted for a single, centralized member dashboard where users can track what they bought, view their next billing date, and manage their account. This not only reduces friction but also builds trust and improves retention.
Additionally, since the company plans to launch multiple card-based products, using this UI structure early makes future scaling easier.
Trade-off:
Pros of A:
Cons of A:
Pros of B:
Pros of B:
PM / Engineering Collaboration:
Business Constraints:
Final Decision:
We launched a member center with a clean, card-based layout that includes:
Final Decision:
Benchmarked against platforms like Notion, Netflix, and Adobe, where centralized dashboards improve transparency
Why Choose Option A Over Option B?
Chosen (A):
Display subscription status with a “Purchased” label and disabled button on product cards, using a card-based layout with supporting text for clarity and future scalability
Not Chosen (B):
Leave all buttons active regardless of purchase status, and use a basic list or single-module layout without visual feedback
Rationale:
To prevent users from accidentally making duplicate purchases, we chose to clearly display a "Purchased" status on already-subscribed items and disable their action buttons.
Additionally, anticipating future product expansion, we implemented a card-based layout with accompanying text, which makes it easier to accommodate additional items and maintain a unified user experience. This structure allows users to quickly identify what they’ve purchased and supports long-term scalability.
Trade-off:
Pros of A:
Cons of A:
Pros of B:
Cons of B:
Cons of PM / Engineering Collaboration:
Technical / Business Constraints:
Final Decision:
We implemented a modular card-based layout showing:
This solution helps users clearly see what they’ve already purchased and lays the foundation for future product integration.
Validation:
Referenced best practices from Apple, Adobe, and YouTube Premium, which all use visual purchase indicators and disabled buttons
To evaluate the effectiveness and impact of the Account Center platform, we defined a set of key success metrics across product usage, user engagement, and business performance:
User Engagement
Feature Adoption
Retention & Satisfaction
Operational Impact
Business Growth
This app uses the Design system of Noise Eraser including button, input, header, footer, and radio button.
1. To foster smoother collaboration, it's crucial to build a culture of mutual trust and open communication before the project begins. Establishing alignment and seeking consensus early on helps avoid misunderstandings later. When differing opinions arise during the process, it's important to share ideas transparently and ensure our actions remain aligned with the overall goal. Effective cross-functional communication and coordination are also key to achieving mutually beneficial outcomes.
2. Throughout the product development process, I proactively evaluate development cost, timeline, and impact. When appropriate, I explore open-source solutions like Lottie to streamline development without compromising quality.
3. In UI design, I aim to think systemically—beyond individual screens—to create scalable designs that support multilingual needs and responsive layouts. This approach not only ensures a consistent user experience but also enables engineers to implement the design more efficiently.
#ProductivityApp #MeetingTool #CollaborationUX #NoteTakingApp #WorkTools #UIUXDesign #ProductDesign #WebAppUX
#AIAudio #NoiseCancellation #VoiceEnhancement #AudioUX #WebAppDesign #AIUX #SoundDesign #ProductivityTech
#AccountManagement #AdminDashboard #WebUX #SystemDesign #UserManagement #DesignSystem #EnterpriseUX #PlatformUX
Line ID: hmc10116