◇ Storyboard

◇ Feature Set

◇ Information Architecture & User Flows

◇ Task Flows and User Flows

🟢 Try the live build: fxpress.netlify.app — the feature set described below is what the widget actually ships.

Ideate

What features carry the product's value, and what control models serve different users?

What Ideate Answered

Define produced a sharpened problem statement, eight POVs, eight HMWs, two personas, and a journey map locating where the design has to intervene. Ideate turned that into something the live widget could be built from — a prioritized feature set naming what FXpress would actually do, an information architecture organizing it, and the core interactions that carry the product's value.

Two principles guided the Ideate work:

• Fexi advises, the human authorizes — Decision support belongs at the moment of decision, inside the send flow, not in a separate chatbot to consult. Fexi recommends and explains; it never acts without an explicit yes.
• One product, adaptive depth — A conservative Protected default that expands into a Power surface as a user's behavior signals readiness. The product reads behavior and adapts; it never asks the user to declare a mode.

The Feature Set

Features were prioritized from the research up — every feature traces to something a participant said, a synthesis theme, or a journey-map opportunity — and sorted into four tiers by how directly they serve a validated need and how essential they are to the core value proposition.