Case 1
Case 1
Eliminating response delay after on-chain transactions
Eliminating response delay after on-chain transactions
Discover
Discover
Users confused by on-chain delays → repeated clicks & support tickets
Users confused by on-chain delays → repeated clicks & support tickets
Define
Define
Problem
Problem
Confusion & lack of trust
Confusion & lack of trust
Goal
Goal
Stability despite blockchain limits
Stability despite blockchain limits
Develop
Develop
Options: backend change (costly) / instant frontend feedback
Options: backend change (costly) / instant frontend feedback
Chose frontend optimization
Chose frontend optimization
Deliver
Deliver
User balance updates instantly after an action, before the transaction is confirmed
User balance updates instantly after an action, before the transaction is confirmed
If the transaction succeeds, the balance stays updated
If the transaction succeeds, the balance stays updated
If it fails, the balance reverts, and a toast notification explains the error
If it fails, the balance reverts, and a toast notification explains the error
If the transaction succeeds, the balance stays updated
If the transaction succeeds, the balance stays updated
Result
Result
Support requests on this issue dropped significantly
Support requests on this issue dropped significantly
Perception of stability and reliability improved
Perception of stability and reliability improved
UX became smoother and more predictable, even within Web3 limitations
UX became smoother and more predictable, even within Web3 limitations
Case 2
Case 2
Improving scenario completion through A/B testing of tooltips
Improving scenario completion through A/B testing of tooltips
Discover
Discover
Pre-airdrop UX testing showed 6/8 users failed a scenario due to unclear mechanics and lack of familiar analogies, causing them to get stuck mid-flow
Pre-airdrop UX testing showed 6/8 users failed a scenario due to unclear mechanics and lack of familiar analogies, causing them to get stuck mid-flow
Define
Define
Problem
Problem
Unclear key elements caused failed scenarios
Unclear key elements caused failed scenarios
Goal
Goal
Boost completion, cut confusion and support
Boost completion, cut confusion and support
Develop
Develop
Suggested adding tooltips for interface elements
Suggested adding tooltips for interface elements
Team split: useful vs. visual noise
Team split: useful vs. visual noise
Initiated A/B test:
– Group A: no tooltips
– Group B: with tooltips
Initiated A/B test:
– Group A: no tooltips
– Group B: with tooltips
Deliver
Deliver
8/8 users with tooltips completed tasks
8/8 users with tooltips completed tasks
Control group faced confusion & failures
Control group faced confusion & failures
Team agreed to implement tooltips
Team agreed to implement tooltips
Result
Result
Higher completion
Lower support load
Case 3
Case 3
Shaping raw ideas into interface logic
Shaping raw ideas into interface logic
Discover
Discover
Product lacked clear definition in early stages
Product lacked clear definition in early stages
Team shared conflicting ideas, no single vision
Team shared conflicting ideas, no single vision
Define
Define
Problem
Problem
No shared product logic → misalignment and inefficiency
No shared product logic → misalignment and inefficiency
Goal
Goal
Build a clear structure and transparent documentation
Build a clear structure and transparent documentation
Develop
Develop
Ran sessions to define core scenarios
Ran sessions to define core scenarios
Created user flows and navigation structure
Created user flows and navigation structure
Introduced Figma Helper system for statuses, notes, and flow explanation
Introduced Figma Helper system for statuses, notes, and flow explanation
Deliver
Deliver
Clear reference point for all flows
Clear reference point for all flows
Faster decision-making and less misalignment
Faster decision-making and less misalignment
Devs and PMs navigated files independently
Devs and PMs navigated files independently
Case 4
Case 4
Building a visual system
from scratch
Building a visual system
from scratch
Discover
Discover
No visual foundation at project start: no brand, no style, no UI
No visual foundation at project start: no brand, no style, no UI
Team worked on product, landing, whitepaper, pitch decks in parallel → risk of inconsistency
Team worked on product, landing, whitepaper, pitch decks in parallel → risk of inconsistency
Define
Define
Problem
Problem
No unified visual system
No unified visual system
Goal
Goal
Build a cohesive identity scalable across all materials
Build a cohesive identity scalable across all materials
Develop
Develop
Ran competitive audit and defined differentiator (orange palette)
Ran competitive audit and defined differentiator (orange palette)
Designed concept with typography, UI patterns, graphic style
Designed concept with typography, UI patterns, graphic style
Built scalable design system and brand guide
Built scalable design system and brand guide
Created templates for marketing use
Created templates for marketing use
Deliver
Deliver
Cohesive visual language across all touchpoints
Cohesive visual language across all touchpoints
Team saved time working from one system
Team saved time working from one system
Identity became a core part of Cytonic’s Web3 positioning
Identity became a core part of Cytonic’s Web3 positioning
