User Flow Mickael Rutembya · Flow Atlas

Capability Detail

/expertises/<slug>

Visitor inspects a single CV-derived capability: score, evidence breakdown, skills, related offers, and links to experience proofs.

Flow intent

What the user is trying to do

« Understand how this specific capability is scored, what evidence backs it, and which services can deliver it. »

Entry points

ElementDestination
Capabilities catalogue capability tile/expertises/<slug>
Offer detail related capability/expertises/<slug>
CV capability anchor/parcours/?capability=<slug>

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR A["Visitor clicks capability"] --> B["Land on /expertises/<slug>"] B --> C["Read score and evidence breakdown"] C --> D["Review skills list"] D --> E["Click related offer"] E --> F["Land on offer detail"] D --> G["Click related experience proof"] G --> H["Land on experience detail"] C --> I["Return to capabilities catalogue"] I --> J["Compare with other capabilities"] click B "https://mickael-umt.com/expertises/agentic-ai/" "Open Capability" click F "https://mickael-umt.com/expertises/agentic-ai/" "Open Offer" click H "https://mickael-umt.com/parcours/agentic-ai-production-assurance/" "Open Experience" click I "https://mickael-umt.com/expertises/" "Open Capabilities"

Screens

ScreenKey contentCTA
Capability detailScore, rank, confidence, evidence breakdown, skillsCompare in ranking, See related experience
Related offerMechanism, deliverables, pricingRequest quote, Contact
Experience proofAtomic commit, proof notes, timelineBack to capability

Scenario

Scenario

CTO validates AI capability score before engaging

Trigger

  • CTO is evaluating AI consulting partners
  • Finds the site via organic search for "AI production assurance"
  • Clicks through to the AI capability detail page

Experience

  1. Page loads with documented score, confidence level, and evidence breakdown.
  2. CTO reviews the skills list and sees 10+ explicitly cited competencies.
  3. CTO clicks "Voir le parcours associé" to verify the experience proof.
  4. Atomic commit links show verifiable GitHub contributions.
  5. CTO returns to the capability page and clicks "Comparer dans le classement".

Trust and safety rules

  • All scores are conservative when public evidence is incomplete — no inflated claims.
  • Confidence levels are explicitly stated (Documented, Inferred, etc.).
  • Evidence links point to atomic proofs, not whole experiences — prevents cherry-picking.
  • Related offers are filtered by capability family — no irrelevant cross-sells.

Interaction notes

  • Page uses data-capability attribute for potential filtering.
  • Family label is bilingual (fr/en) via data-fr/data-en.
  • Skills list is rendered server-side from the capability model.
  • Related offers and experience proofs are optional sections.

Result states

StateWhat the visitor seesWhat happens next
BrowsingVisitor reads score and evidence, no clickMay return to catalogue or leave
ComparingVisitor clicks "Compare in ranking"Returns to capabilities with filtered view
VerifyingVisitor clicks related experience proofReads atomic proof, may return
ConvertingVisitor clicks related offerMoves to offer detail → contact/quote flow