Please enable JavaScript.

Coggle requires JavaScript to display documents.

UI UX, 17 Accessibility - Coggle Diagram

- - - - But it isn't just another method - They have the ability totally define scenarios or sections of something abstract or technical form the perspective of the user.
    - - Here the goal is to register for the project.
      - Step 1 - Welcome Screen
      - Step 2 - Go to some sort of login page.
      - Step 3 - Get access to the product.
      - So it helps us think about our product and the users who interact with it in three simple questions.
        
        What is the goal of thing?
        
        Who is doing it?
        
        How do they do it?
    - - Step 1 : - What is the purpose of the your user flow? - You need to name your flow and that name describe the flow. That is the goal that user will achieve by completing the steps.
      - Step 2 : - Try to make it in one direction- try your best to tell the story that goes in one direction. Step 3 : - A user flow should represent a complete task. > Describe each of the steps to get there
        
        To ensure that you product is organised, the scope of each flow should really be a single task or gaol for your user.
        
        Steps should not be too short or too long - it should be medium - It should be a story.
        
        If any negative experience occurs - we need to possibly break that out and get them back into some sort of funnel.
        
        Remember your user flow should be the clearest model your product.
  - - - You flow should go in one direction.
        
        Do it in site maps but don't do it in user flow.
        
        What we should do is break them in the following, Split them up in different flows and categorise them.
        
        You flow should represent a complete task. , Click button- which button , fill form - which form - is should be descriptive, End goal should have the description - what is the end goal is?
        
        So that anyone can read it and understand it.