Crea un primer flujo de la conversación

How to design the initial flow of a user-system conversation?

Designing an effective user-system conversation flow is a crucial step in ensuring a smooth and satisfying experience in any application. Beyond linear test dialogs, a conversational flow contemplates multiple paths a user can take during their interaction with a system. Here you will learn how to create these flows effectively to improve communication between your system and users.

What is the difference between test dialogs and conversational flows?

Test dialogs are simple conversations with a single path. Conversational flows, on the other hand, are maps that visualize all the possible paths the conversation can take. For example, if the system suggests a dish of the day, the user could accept it, reject it, or request a vegetarian alternative. The flows work with these possibilities, allowing for diverse responses and ramifications.

Why is it essential to co-create flows with your team?

Co-creating with the team not only improves the quality of the conversational flow, but is also an excellent documentation tool for the development stage. Collaborating on this task ensures a shared understanding and a more robust design, as well as allowing the incorporation of different perspectives and competencies.

How to use FigJam to develop conversational flows?

FigJam is an ideal collaborative tool for making conversational flows. It allows you to annotate ideas, co-ideate, and develop flowcharts in a dynamic and visual way, interacting in real time with your team.

What shapes and elements to use in FigJam to define conversational flows?

• Dark blue shape: Indicates the beginning of the flow.
• Blue rhombus: Marks system decisions.
• Light blue shape: Marks the system dialogs.
• Arrows: Represent the possible user responses and the resulting paths.

These visual representations allow to clearly structure and visualize the different potential paths of the conversation.

How to organize flows for different use cases?

For each prioritized use case, create a different flow. For example, in a meditation application, you could have flows for users who want to meditate, listen to music to fall asleep or read a story. Here's an example of how to structure this in FigJam.

Use case: Meditate

1. Start of the flow: Determines if the user is new.
2. System presentation: Offers the available options.
3. System interaction: Adjusts the flow according to the user's previous experience (new or expert).
4. User decision: Chooses meditation duration (5 or 10 minutes).
5. System action: Starts the meditation.

How to map strategies to repair a conversation?

Anticipating inconveniences and responses to anomalous situations is essential. Some possible problems to map include:

• Responses to functions not yet available: "I can't do this yet, but I can help you with..."
• Misunderstandings or lack of understanding: "I'm sorry, I didn't understand what you asked."
• Internet connection problems: "I can't connect to the network, I can't help you at this time."

These strategies not only improve the user experience, but also strengthen the system's ability to handle unexpected situations efficiently.

What is the importance of iterative conversational flow design?

Flow design is an iterative exercise that starts with paper drafts and progresses to a more consolidated digital representation. Continuous refinement and validation of flows with real users is crucial to fine-tune and improve the user experience.

As a student or professional engaged in UX design, it is critical that you continue to explore and hone your skills. Constant learning and adaptation to user needs will allow you to create successful and enriching conversational systems. Go ahead and enjoy the process of creation and improvement!