helping facebook sellers scale faster at springo by removing manual chaos
in 3 months, we redesigned springo end-to-end — from messy beta to a polished mvp. the work included streamlined flows, a mini design system, and full delivery of launch-ready designs.
timeline
3-4 months
team
1 design manager
2 designers
1 product manager
disciplines
product thinking
visual design
rapid prototyping
design system
context
small sellers were stuck copy–pasting into facebook groups
but why it mattered?
reach: one post wasn’t enough to get noticed
time: hours lost in manual posting
consistency: prices & stock out of sync → lost trust
tracking: no way to know what worked
💡 what’s the big idea?
idea is to post once, broadcast everywhere, manage catalogue, track engagement.
ux audit of beta flow showed inconsistency across heuristics, states, and error handling. we started there
why: unclear/inconsistent experience → hesitation at every tap
how we tackled it
ship lean now, design to scale later
we proposed a two-track plan:
ship a clean mvp fast, while setting up a mini design system to prevent drift and enable scale
seller login flow
why: ia mapped directly to sellers’ jobs
from inconsistent visuals to a lightweight design system:
after spotting gaps in the beta, we built a mini system with unified grids, type, and components
why: predictable components = consistency + faster shipping + trust signals
from messy flows to a connected seller journey:
after auditing the beta, we rebuilt springo’s flows around what sellers actually needed
why: each screen had one dominant action + clear “what next?”
the after-math
what we delivered?
launch-ready mvp delivered in 3 months
lightweight design system in place
reduced ux debt before dev started
well the little did we know
😭 springo halted the product launch since the core feature for bulk posting across groups was blocked by meta
helping facebook sellers scale faster at springo by removing manual chaos
in 3 months, we redesigned springo end-to-end — from messy beta to a polished mvp. the work included streamlined flows, a mini design system, and full delivery of launch-ready designs.
timeline
3-4 months
team
1 design manager
2 designers
1 product manager
disciplines
product thinking
visual design
rapid prototyping
design system
context
small sellers were stuck copy–pasting into facebook groups
but why it mattered?
reach: one post wasn’t enough to get noticed
time: hours lost in manual posting
consistency: prices & stock out of sync → lost trust
tracking: no way to know what worked
💡 what’s the big idea?
idea is to post once, broadcast everywhere, manage catalogue, track engagement.
ux audit of beta flow showed inconsistency across heuristics, states, and error handling. we started there
why: unclear/inconsistent experience → hesitation at every tap
how we tackled it
ship lean now, design to scale later
we proposed a two-track plan:
ship a clean mvp fast, while setting up a mini design system to prevent drift and enable scale
seller login flow
why: ia mapped directly to sellers’ jobs
from inconsistent visuals to a lightweight design system:
after spotting gaps in the beta, we built a mini system with unified grids, type, and components
why: predictable components = consistency + faster shipping + trust signals
from messy flows to a connected seller journey:
after auditing the beta, we rebuilt springo’s flows around what sellers actually needed
why: each screen had one dominant action + clear “what next?”
the after-math
what we delivered?
launch-ready mvp delivered in 3 months
lightweight design system in place
reduced ux debt before dev started
well the little did we know
😭 springo halted the product launch since the core feature for bulk posting across groups was blocked by meta
helping facebook sellers scale faster at springo by removing manual chaos
in 3 months, we redesigned springo end-to-end — from messy beta to a polished mvp. the work included streamlined flows, a mini design system, and full delivery of launch-ready designs.
timeline
3-4 months
team
1 design manager
2 designers
1 product manager
disciplines
product thinking
visual design
rapid prototyping
design system
context
small sellers were stuck copy–pasting into facebook groups
but why it mattered?
reach: one post wasn’t enough to get noticed
time: hours lost in manual posting
consistency: prices & stock out of sync → lost trust
tracking: no way to know what worked
💡 what’s the big idea?
idea is to post once, broadcast everywhere, manage catalogue, track engagement.
ux audit of beta flow showed inconsistency across heuristics, states, and error handling. we started there
why: unclear/inconsistent experience → hesitation at every tap
how we tackled it
ship lean now, design to scale later
we proposed a two-track plan:
ship a clean mvp fast, while setting up a mini design system to prevent drift and enable scale
seller login flow
why: ia mapped directly to sellers’ jobs
from inconsistent visuals to a lightweight design system:
after spotting gaps in the beta, we built a mini system with unified grids, type, and components
why: predictable components = consistency + faster shipping + trust signals
from messy flows to a connected seller journey:
after auditing the beta, we rebuilt springo’s flows around what sellers actually needed
why: each screen had one dominant action + clear “what next?”
the after-math
what we delivered?
launch-ready mvp delivered in 3 months
lightweight design system in place
reduced ux debt before dev started
well the little did we know
😭 springo halted the product launch since the core feature for bulk posting across groups was blocked by meta
other projects
other projects
simplifying complex fintech dashboards at vegapay for real banking impact
simplifying complex fintech dashboards at vegapay for real banking impact
solving context switching at sketchnote by bringing conversations into workspaces
solving context switching at sketchnote by bringing conversations into workspaces