User Flow Mickael Rutembya · Flow Atlas

Decision profiles

/engagement/audiences/

Visitor matches their role and priority tension to a before/after transformation avatar.

User intent

What the visitor is trying to do

« I want to see which transformation avatar matches my role, priority tension, and organisational context. »

Entry points

ElementDestination
Engagement "Pour qui"/engagement/audiences/
Avatar card "Offre associée"/expertises/<slug>/
Qualification recommended URLExternal booking link

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR Start(["Visitor arrives"]) --> Audiences["/engagement/audiences/ (Audiences)"] Audiences --> Offer["/expertises/<slug>/ (Related offer)"] Audiences --> Eng["/engagement/"] Eng --> Qualifier["/contact/#call-qualifier"] Qualifier --> End(["Engagement started"]) click Audiences "https://mickael-umt.com/engagement/audiences/" "Open Audiences" click Offer "https://mickael-umt.com/expertises/agentic-ai/" "Open Offer" click Eng "https://mickael-umt.com/engagement/" "Open Engagement" click Qualifier "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification" click End "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification"

Screen inventory

IDScreenUser task
P0Audiences listingBrowse decision profiles and before/after avatars
P1Related offerReview the capability offer associated with the avatar
P2Engagement formatsCompare collaboration formats
P3QualificationSubmit structured call-qualification form

Flow scenario

Scenario A1

Engineering manager matches avatar to context

Trigger

  • Visitor opens /engagement/audiences/ from the engagement page
  • Scans the before/after transformation avatars
  • Clicks "Offre associée" on the matching avatar

Experience

  1. The audiences page shows decision profiles with before/after blocks for each avatar.
  2. Each card includes the role, priority tension, and a related offer link.
  3. The visitor identifies their context and clicks the associated offer.
  4. The offer detail shows mechanism, deliverables, and public evidence.
  5. The visitor returns to the engagement page to compare formats and pricing policy.
  6. The visitor submits a call qualification; the system recommends a meeting format and booking link.

Trust and safety rules

  • All pricing is public and deterministic; no coefficient reaches the browser.
  • The calculator access gate blocks disposable and non-routable domains.
  • Payment pages are blocked by robots.txt and carry no editorial SEO value.
  • No card data touches the server; Stripe hosts the checkout page.
  • Avatar fit is an estimate based on visitor answers; it does not guarantee outcome.

Interaction rules

  • Mobile fields use 16 px text to avoid browser zoom.
  • Reduced-motion preferences disable nonessential transitions.
  • Language toggle switches FR/EN across all strings.

Result states

StateWhat the visitor seesWhat happens next
BrowsingAudiences listing with before/after avatarsVisitor identifies matching profile
MatchedRelated offer and engagement formatsVisitor opens offer or qualification
QualifiedConfirmation with quote context and recommended formatOwner reviews lead or buyer books directly
ConvertedStripe return page with entitlementsBuyer downloads or books