Deliverables
Deliverables
Product Design
About
About
Qaku is a Web3-based Q&A platform. It started as an internal tool to cover team needs, but after positive feedback it was planned to launch publicly for a wider audience interested in Web3 and browser-stored projects.
My role was to revisit the existing UX/UI, conduct research, and redesign the product with a high-fidelity interface. I worked closely with stakeholders, designers, and developers under time constraints to make the platform user-friendly and clear.
The MVP was launched internally (on Vercel) and is now undergoing final implementation updates.
Credits
Credits
Waku
Home page
Home page
Key Problems Identified
Key Problems Identified
A unified interface for hosts and participants led to role ambiguity, reduced clarity, and unnecessary cognitive load.
The creation flow lacked clear structure and prioritization, resulting in excessive input requirements and friction during task completion.
The Q&A management experience did not provide sufficient visibility or information hierarchy, limiting users’ ability to track and moderate activity efficiently.
Navigation contained redundant and low-value entries, diluting focus and weakening overall information architecture.
A unified interface for hosts and participants led to role ambiguity, reduced clarity, and unnecessary cognitive load.
The creation flow lacked clear structure and prioritization, resulting in excessive input requirements and friction during task completion.
The Q&A management experience did not provide sufficient visibility or information hierarchy, limiting users’ ability to track and moderate activity efficiently.
Navigation contained redundant and low-value entries, diluting focus and weakening overall information architecture.
Solutions
Solutions
Defined distinct role-based flows for hosts and participants to reduce ambiguity and improve task clarity.
Restructured the creation flow by prioritizing primary inputs and progressively disclosing secondary options to reduce friction.
Standardized and simplified form patterns to improve consistency and usability across workflows.
Redesigned the management experience with clearer hierarchy, dedicated detail views, and performance metrics to enhance oversight and decision-making.
Refined the navigation structure by removing redundant entries and consolidating content into two core states for improved focus.
Introduced search and date-based filtering to support efficient content retrieval at scale.
Developed a modular widget system to enable seamless Q&A interaction across devices and contexts.
Defined distinct role-based flows for hosts and participants to reduce ambiguity and improve task clarity.
Restructured the creation flow by prioritizing primary inputs and progressively disclosing secondary options to reduce friction.
Standardized and simplified form patterns to improve consistency and usability across workflows.
Redesigned the management experience with clearer hierarchy, dedicated detail views, and performance metrics to enhance oversight and decision-making.
Refined the navigation structure by removing redundant entries and consolidating content into two core states for improved focus.
Introduced search and date-based filtering to support efficient content retrieval at scale.
Developed a modular widget system to enable seamless Q&A interaction across devices and contexts.
Before vs After
Before vs After
Approach
Approach
I began with a structured audit of the existing product to understand its core user journeys, technical constraints, and friction points. I mapped the primary workflows, including:
Q&A and poll creation
Scheduling and publishing
Real-time answer management
External crypto wallet integration
URL and node configuration
Browser-based storage and session handling
To ground the redesign in real usage patterns, I analyzed Slido as a reference benchmark for live Q&A and polling experiences. The goal was not to replicate it, but to understand established interaction patterns and identify gaps in clarity, flow efficiency, and information hierarchy.
Through this review, I identified recurring issues such as interface clutter, role ambiguity, and unnecessary complexity in content creation flows.
In parallel, I conducted internal interviews with the Waku team to better understand their real-world use cases and operational constraints. I also worked closely with developers to map technical dependencies and ensure that proposed solutions aligned with architectural realities.
This allowed me to define a clearer problem space before moving into structural redesign.
I began by reviewing the existing website and identifying the main flows and features:
Creating Q&A
Creating polls
Scheduling publishing
Integrating an external crypto wallet for enhanced identity
URL & node settings
Managing answers in real time
Browser-based storage of Q&As and polls
Since the team was already using Slido, I used it as the main UX reference. My research included analyzing real-time Q&A and poll use cases, looking at friction points such as cluttered interfaces and overly complex poll creation flows.
I also conducted internal interviews with the Waku team to understand their specific tasks, and collaborated with developers to map technical constraints.
Design Approach
Design Approach
Since the platform was evolving into a public-facing product, I worked closely with graphic designers to align the visual direction with its broader positioning.
We established a restrained monochrome foundation to reinforce clarity and reduce visual noise, ensuring the interface remained focused on content and interaction. To maintain warmth and guide user behavior, I introduced yellow as a functional accent for primary actions and interactive states.
I then formalized the visual language into a scalable design system — defining reusable UI components, color tokens, and typographic variables. This improved consistency across flows, accelerated implementation, and reduced friction in developer handoff while supporting future product growth.
Since the platform was evolving into a public-facing product, I worked closely with graphic designers to align the visual direction with its broader positioning.
We established a restrained monochrome foundation to reinforce clarity and reduce visual noise, ensuring the interface remained focused on content and interaction. To maintain warmth and guide user behavior, I introduced yellow as a functional accent for primary actions and interactive states.
I then formalized the visual language into a scalable design system — defining reusable UI components, color tokens, and typographic variables. This improved consistency across flows, accelerated implementation, and reduced friction in developer handoff while supporting future product growth.
Mobile Landing page
Mobile Landing page
Home page
Home page
Mobile Home page
Mobile Home page
Testing & Outcomes
Testing & Outcomes
After launching the MVP, I ran internal usability testing sessions to surface friction points and validate early assumptions.
One key insight was that the “Integrate Wallet” panel was visually overemphasized, drawing attention away from primary actions despite being a secondary feature.
In subsequent iterations, I rebalanced the visual hierarchy to better align attention with core workflows, improving clarity and task focus.
After launching the MVP, I ran internal usability testing sessions to surface friction points and validate early assumptions.
One key insight was that the “Integrate Wallet” panel was visually overemphasized, drawing attention away from primary actions despite being a secondary feature.
In subsequent iterations, I rebalanced the visual hierarchy to better align attention with core workflows, improving clarity and task focus.
Q&A and Polls creation flow
Q&A and Polls creation flow
Mobile Q&A and Polls creation flow
Mobile Q&A and Polls creation flow
Published Q&A
Published Q&A
Q&A and Polls live
Q&A and Polls live
Identity
Identity
The product was internally nicknamed Qaku, derived from the team name Waku and inspired by the sound “quak.”
The logo was designed by the graphic design team, and I integrated it into the product’s identity system.
The product was internally nicknamed Qaku, derived from the team name Waku and inspired by the sound “quak.”
The logo was designed by the graphic design team, and I integrated it into the product’s identity system.
Mobile Published Q&A and Polls
Mobile Published Q&A and Polls
Desktop Manage Q&A
Desktop Manage Q&A
Mobile Manage Q&A
Mobile Manage Q&A
Manage Polls
Manage Polls
Participant View Q&A
Participant View Q&A
Mobile manage Q&A
Mobile manage Q&A
Results
Results
Received positive early feedback from initial users, validating the revised interaction model and simplified workflows.
Reduced content creation time by approximately 40% through streamlined flows and clearer input prioritization.
Increased engagement by improving information hierarchy and reducing friction across key user journeys.
Established a scalable, token-based visual system adaptable for future Qaku and Waku-related initiatives.
Successfully adopted internally, with Qaku now used for organization-wide Q&A sessions.
Received positive early feedback from initial users, validating the revised interaction model and simplified workflows.
Reduced content creation time by approximately 40% through streamlined flows and clearer input prioritization.
Increased engagement by improving information hierarchy and reducing friction across key user journeys.
Established a scalable, token-based visual system adaptable for future Qaku and Waku-related initiatives.
Successfully adopted internally, with Qaku now used for organization-wide Q&A sessions.