Please enable JavaScript.

Coggle requires JavaScript to display documents.

MIND MAP 2018 (CHATBOT :silhouettes: (UI made of dialogs (May or may not…

- - - - Buttons, text, other elements
      - Entirely speech-based
  - - - The stubborn bot insists upon maintaining the current course of conversation, even when the user attempts to steer things in a different direction.
      - Do: Design your bot to consider that a user might attempt to change the course of the conversation at any time.
      - Don't: Design your bot to ignore user input and keep repeating the same question in an endless loop.
    - - The clueless bot responds in a nonsensical manner when it doesn't understand a user's attempt to access certain functionality. A user may try common keyword commands like "help" or "cancel" with reasonable expectations that the bot will respond appropriately. This approach is not recommended.
      - Do: Implement middleware that will examine user input for the keywords that you specify (ex: "help", "cancel", "start over", etc.) and respond appropriately.
      - Don't: Design every dialog to examine user input for a list of keywords.
      - By defining the logic in your middleware, you're making it accessible to every exchange with the user. Using this approach, individual dialogs and prompts can be made to safely ignore the keywords, if necessary.
    - - The mysterious bot fails to immediately acknowledge the user's input in any way.
      - Do: Design your bot to immediately acknowledge user input, even in cases where the bot may take some time to compile its response.
      - Don't: Design your bot to postpone acknowledgement of user input until the bot finishes compiling its response.
      - By immediately acknowledging the user's input, you eliminate any potential for confusion as to the state of the bot. If your response takes a long time to compile, consider sending a "typing" message to indicate your bot is working, and then following up with a proactive message.
    - - The captain obvious bot provides unsolicited information that is completely obvious and therefore useless to the user.
      - Do: Design your bot to provide information that will be useful to the user.
      - Don't: Design your bot to provide unsolicited information that is unlikely to be useful to the user.
      - By designing your bot to provide useful information, you're increasing the odds that the user will engage with your bot.
    - - The bot that can't forget inappropriately integrates information from past conversations into the current conversation.
      - Do: Design your bot to maintain the current topic of conversation, unless/until the user expresses a desire to revisit a prior topic.
      - Don't: Design your bot to interject information from past conversations when it is not relevant to the current conversation.
      - By maintaining the current topic of conversation, you reduce the potential for confusion and frustration as well as increasing the odds that the user will continue to engage with your bot.
  - - - Buttons, images, carousels, and menus
    - - visual, audio, and/or selectable messages and help to assist conversation flow
- - - - Roles
        
        Scrum Master
        
        Scrum Team
        
        Product Owner
      - Product Backlog (kanban)
        
        Sprint Planning
        
        Sprint Backlog (kanban)
        
        Sprint Execution
        
        Sprint Review
        
        Potentially Shippable Increment
        
        Sprint Retrospective #
        
        Daily Scrum
    - - Teste do produto ao final de cada sprint
      - Duration: from 1 to 4 weeks
      - Time dictated by the team
    - - Alignment with Why and How
      - Working Allocated
      - Keep the same team for at least 12 months
  - - - 4 KRs for each macro objectives
        
        Each KR, 1 numerical goal
    - - 40% Top down
      - 60% Bottom up
  - - - No physical structure - based on information
        
        Cost reduction
        
        Internet of Things
        
        Price / performance ratio doubles every 1 to 2 years
      - Change concept have/possess to use
        
        Internet of Things
- - - - More chuncks in inferface = more difficult
        
        Critical for first time users.
        
        They don't have the practice to encode
        the interface into long term memory
    - - Avoid breaking the visual foundation when
        accomodate new features
  - - - Should feel like an invisible hand that guides the user
    - - Minimize the user’s memory load by making actions and options visible.
        "recognizing something is easier than remembering"
    - - Self-evident: users should know how to go from point
        A to point B without any outside guidance.
    - - Keep words and actions consistent.
        “The Principle of Least Surprise.”
    - - Show Only The Most Important Destinations
      - Communicating The Current Location
      - Make Navigation Self-Evident
  - - - Linear Navigation
        
        Step-by-step
        
        Each next step looks like a logical continuation of the previous one
        
        Good for goal-driven apps and e-commerce websites
      - Voice User Interfaces
        
        Mobile device for: call someone, ask directions, get help with homework, play a song, find out movie times, check the time
        
        IoT and Smart Home systems
    - - Remove irrelevant information (noise) and prioritize relevant information (signal) by putting content first and elaborating clear visual language
      - Content First
        
        Minimalist: remove all unnecessary elements of the interface and focus on what’s really important: content and functionality
        
        More whitespace between different elements
        
        Limited numbers of decorative items
      - Clear Visual Language
        
        Strong visual signifiers (contrasting colors for CTA btn) + minimalist layouts = really easy-to-use experience
      - Large Headlines
        
        More whitespace and large typography for headers: make text both easier to notice and easier to read.
    - - Functional Animations
        
        Brings clarity to the user interface
        
        Is used to simplify the process of interaction with products
        
        describe complex transitions and spatial relationships
      - Delightful Animation
        
        Used to create an emotional connection with users
- - - - Units & measurements
      - Metrics & keylines
      - Structure
      - Responsive UI
      - Split screen
    - - Color Tool
    - - Floating Action Button
      - Raised Button
      - Flat Button
    - - 3D World
      - Lights and Shadows
      - Interaction - shape changes
      - Movement: material can be spontaneously generated or destroyed anywhere in the environment
      - Motion
  - - - Features
        
        Backlogs
        
        Tasks
- - - - Board with colors, shapes, words, feelings, sounds, videos, photos and drawings
    - - Manifest Creation in text form. Manifest Translation in visual format. Alternatives Generation.
    - - Which of the possibilities translates the manifest better? Which paths differentiate the company from its competitors? Test the application of core and brands.
    - - Present to the customer and receive feedback. Seek total customer satisfaction.
    - - Document with company history, strengths, ways to sell, what sells / product, customer profile