Overview
FactorFlow is a decision-making web application I built to help users make clearer choices by breaking decisions into weighted factors and scoring the outcome.
The project originally started as DecisionFlip, a simpler version built as part of a project. As I refined the idea and prepared it for real-world use, I rebranded it to FactorFlow, a name that better reflects how the product actually works.
Problem
Making decisions between two options is harder than it should be.
People usually overthink, rely on emotion, or go back and forth without clarity. The core issue is that people don't have a simple way to structure their thinking.
Most tools either feel too complex (spreadsheets, frameworks) or too shallow (coin flips, random generators). There's a gap for something that is structured, simple, and fast.
Solution
FactorFlow guides users through a clear process:
- →Enter two options
- →Evaluate them across key factors
- →Assign importance to each factor
- →Choose which option each factor favors
- →Get a weighted result
Instead of guessing, users see a result based on what they actually value.
My Role
I built this project end-to-end:
- • Product concept and direction
- • UX flow and interaction design
- • UI design and visual system
- • Frontend development (Next.js, Tailwind)
- • Decision logic and scoring system
This was a full product build, not just a UI.
Process
Starting Point (DecisionFlip)
The first version was functional but basic. It allowed users to compare two options using a simple factor system and produced a result.
But it wasn't polished: UX was rough, interactions weren't as clear, and the overall experience didn't feel complete.
Refinement
I focused on improving three things:
- Clarity: I reworked the structure so users always know what step they're on and what to do next.
- Interaction Design: I simplified the core interaction into slider = importance and selection = which option it favors.
- Visual Design: I redesigned the UI to feel more like a real product with consistent spacing, strong contrast, clear hierarchy, and modern styling.
Rebrand to FactorFlow
The name DecisionFlip didn't match the product. It sounded random and unstructured, but the actual product is about weighing factors and understanding flow between them.
So I rebranded to FactorFlow, which better represents the logic, feels more aligned with the experience, and positions it as a real tool.
Key Features
- • Two-option decision system
- • Factor-based evaluation
- • Adjustable importance (weighted sliders)
- • Clear score comparison
- • Score breakdown for transparency
- • Clean, responsive UI
UX Decisions
- • Limited to two options to reduce complexity
- • Used predefined factors to reduce friction
- • Built a step-based flow for clarity
- • Focused on strong visual feedback
Challenges
- • Making a structured system feel intuitive
- • Aligning naming with product functionality
- • Balancing simplicity and logical depth
Future Improvements
- • Custom factors
- • More than two options
- • Better onboarding
- • Clearer weighting explanation
- • Save and share functionality
Outcome & Takeaways
What This Demonstrates
- • Refining a basic project into a real product
- • Improving UX through iteration
- • Aligning branding with functionality
- • Building a complete working system
Key Learnings
- • Clarity matters more than features
- • Naming impacts perception
- • Good UX removes thinking
- • Iteration creates real products
Ready to try FactorFlow?
Make clearer decisions with structured factor analysis.