Making a classification tree for messaging appearance

Creating a decision tree for when to display which message in CAD applications involves considering various factors such as user actions, system state, and the context of the design process. Here’s a simplified decision tree to help determine the appropriate message type:

Example of how “Decision tree for when to display which message in cad applications” may look like. This is only for reference not an actual Decision Tree

1. Define phase:

• Study and analyse the current message work flow within the application.
• Gather the issues and inconsistencies
• Identify the need for message and notification

2. Research Phase:

Identify Triggering Events:

• Determine the events or actions that will trigger the display of messages or notifications within your application. These events could include user actions, system events, or external triggers.
• Understand the difference between notification and messages

Error message displayed due to User action. Example from Fusion 360.

Define Message Types:

Study the message — type, format, occurrence, consistency in competitive CAD application.

• Understand the criteria for when to use which type of message:

1. Error Messages:

• Use when there is a validation error, such as invalid geometry, conflicting constraints, or input data errors.
• Display when an operation cannot be completed due to technical limitations, such as insufficient resources or compatibility issues.
• Provide actionable guidance on how to correct the error or resolve the issue to proceed with the design.

2. Warning Messages:

• Use when there are potential issues or risks associated with the user’s actions, but they do not prevent the operation from being completed.
• Warn about potential design flaws, ambiguous inputs, or situations that may lead to unexpected outcomes.
• Offer suggestions or precautions to mitigate risks and improve the design quality.

3. Confirmation Messages:

• Use when confirming critical actions that may have significant consequences, such as saving, deleting, or overwriting a file.
• Confirm irreversible actions to ensure users are aware of the impact and can proceed with intentionality.
• Provide options for users to confirm or cancel the action to prevent accidental data loss or unintended changes.

4. Informational Messages:

• Use for providing contextual information, tips, or guidance related to specific tools, commands, or design features.
• Offer explanations of technical terms, instructions on using advanced functionalities, or shortcuts to improve user productivity.
• Display when additional information or clarification is needed to enhance user understanding and facilitate effective use of the CAD software.

5. Status Messages:

• Use to provide real-time feedback on the progress or status of ongoing operations, such as rendering, simulation, or analysis.
• Display progress indicators, status updates, or completion notifications to keep users informed about the system’s activity.
• Enable users to monitor the progress and anticipate when tasks will be completed to manage their workflow efficiently.

3. Map out scenarios

Create a list of scenarios or situations in which messages or notifications should be displayed. Each scenario should correspond to a specific triggering event and context within the application.

Collect scenarios and map out those scenarios to trigger points and type of message

Collecting Data:

Gather data to understand different scenarios in CAD, user behaviour, user expectations and need of guidance. This could be further deep dive to the research phase.

• List down different and possible scenarios of occurrence and need to display messages/notifications to the user using your app (if working on existing application).
• Reach out to your stakeholders working on your product to gather their understanding, knowledge on message/notification appearances.
• Demo prototypes to get feedbacks from stakeholders and users to understand their expectations in different scenarios.
• Enact modelling on your CAD application and check the corresponding message response on competitive application/s as well.

4. Define conditions

For each scenario, define the conditions or criteria that determine whether a message or notification should be displayed. These conditions may include the state of the system, user inputs, or the outcome of previous actions.

Define conditions for different scenarios.

Example:

1. type of message appears when user is working with an active command.
2. how will user know they forgot to define basic requirements for using the modelling tool.
3. how to guide users when lost or stuck.
4. loader appears when user has to wait, how much longer should they wait!
5. putting in wrong or invalid values?

5. Create the Decision Tree:

Using the triggering events, scenarios, conditions, and message types identified in steps 1–5, create a decision tree that illustrates the flow of messages and notifications in your application. Start with a root node representing the initial triggering event and branch out to represent different scenarios and conditions.

6. Test and Iterate:

Test the decision tree with sample data and scenarios to ensure that messages and notifications are triggered correctly and displayed as expected. Iterate on the decision tree based on feedback and refine it as needed to improve accuracy and effectiveness.