Sodimac Colombia · E-commerce · UX proposal
Research and conceptual definition of a flow that protected active processes and offered relevant solutions without preventing people from exercising their decision.
The starting point
The request came from the Sodimac Colombia team through the Product Manager in my design squad. The existing flow was basic and needed to be assessed against user expectations, market practices and the operating reality of a home-improvement retailer.
Deleting an account could affect orders, scheduled services, claims, credits, balances or documents that still required access.
The problem
It could hide consequences or unintentionally remove access to active processes.
It could become a deliberate barrier and damage trust.
Design questionHow might we let people delete their accounts with clarity and autonomy while addressing situations that could be prompting an unnecessary or premature decision?
Research before drawing
I reviewed deletion experiences across digital products and comparable retailers.
I classified common causes so the experience could address the problem behind the request.
I identified orders, services, balances, claims and other processes that could remain active.
I structured contextual alternatives, confirmations and consequences for team evaluation.
Two reference levels
Instagram, Facebook, LinkedIn, Amazon, WhatsApp, Dropbox, Slack, Reddit, GitHub, Netflix, Pinterest and X/Twitter.
Home Depot, Lowe's, Menards, Ace Hardware and Wayfair.
The goal was not to copy an interface, but to recognize patterns: clear consequences, identity verification, active-process detection, relevant alternatives and final confirmation.
Understanding intent
Retention as a consequence of solving
The flow was not designed to persuade at all costs. People could reject the alternatives and continue with deletion.
Enlarge diagram ↗Retention is framed as the result of solving a cause—not adding friction or hiding deletion.
Editorial reconstruction for this case · Not an implemented interfaceBefore an irreversible action
PrincipleEthical retention means solving causes, not making decisions harder.
Verifiable outcome
Transparency about scope
Engineering effort and available time influenced the decision not to continue with this scope.
This case demonstrates the analysis and decisions considered—not a post-launch outcome.
A UX solution is not defined by usefulness alone. It must also fit the product moment, technical capacity and available priorities.
The project reinforced that a simple action can depend on many processes, that ethical retention begins by understanding the cause and that a proposal can reveal valuable risks even when it does not reach production.
Next case