Sprinklr
Description
TBD
Client
Sprinklr
Year
Type
App Design
DISCOVERY
Frax's founder Sam and I met to discuss the scope of the project. We locked in process, timelines, check-in cadences, and resources. These were important early conversations to understand both his goals and the workflow we'd use.
Insight
Only one dev available for building the FE, who also had other responsibilities to balance
Maintain some previous architecture so learned behaviors weren't lost completely
We aligned around a standard iterative process, with the distinction of concurrent design system work and paper wireframing—allowing us to maintain speed and hit our internal timeframe.
RESEARCH
Clean up usability issues in core features, leverage common web3 patterns (token swaps, staking) to inject existing external user behaviors
Create common layouts and a stricter set of components for consistency across all views
Recommendation
Improve navigation to minimize nested contexts and overload while improving feature discoverability
Consolidate views where possible to group by feature type so similar functions are accessible in the same place
Reduce unnecessary information inside of each context
DESIGN
DESIGN
OUTCOMES
Some later designs eventually ran out-of-scope, and dev responsibilities meant windows to sync were narrow.
Full handoff meant not being able to measure metrics after delivery
Learnings
Keep tight stakeholder communication when dealing with complex features.
Prioritizing patterns expedited high-fidelity mockups
Wins
Positive team feedback.
A thorough design system and consideration for key patterns /layouts means Frax is able to extend the designs without my input