Tips for Text Input to Create a Model

Use active voice.

• Avoid using the passive voice: "HR is notified and initiates the off-boarding process."

• Use the active voice: "The employee notifies HR, which then initiates the off-boarding process."

Be specific about the subject and object of a sentence.

Using the active voice causes you to specifically mention both the subject and the object of the sentence.

• Avoid letting an implied subject do the action: "The employee's manager is informed."

• Use the active voice to specifically name the subject and the action: "HR informs the employee's manager."

  • Alternatively, if the passive voice is used, name the subject from which the action initiated: "The employee's manager is informed by HR."

Keep consistency in the naming of roles and entities.

Follow consistent naming for roles that participate in a business process. For example, avoid referring to the role of the "manager" later as "supervisor". Stick to one identification or name for the initial creation of the model, which can be later modified in the Editor.

This tip applies to any other entity such as IT-system or Data Object. Avoid using synonyms for the same entity in the same process description. For example, don't use the term "vendor" and later "supplier" for the same entity in the same process description.

Focus on repetition over AI guesswork.

Repeatedly mentioning a role's name is more effective than letting AI infer whether the role participates in the process activities or not.

Be specific and consistent with entities that are connected to a named activity of the process.

If an entity is connected to a process activity, specifically mention that entity while writing about the activity in the process description.

• Avoid using a shortened form of an entity: "An interview is then arranged on teams."

• Use the entity's established form consistently: "The manager then arranges an interview with the employee on Microsoft Teams."

Avoid adding unnecessary details.

Keep the description clean, clear, and concise. Including details that aren't critical to the core business process and its flow can result in the creation of unnecessarily complex process models.

Clearly emphasize the start and end events of the process.

Start event: Specifies the trigger of the first process activity, it doesn't refer to an activity that is within scope of the process. Start events are usually indicated with phrases like:

• “The process begins when . . .”

• “The process starts with . . .”

• “Once the admin enters the . . .”

End event: Specifies the final outcome of the process. Clearly indicate the end of a process with sentences like:

• “The process ends when the final report is generated.”

• “The process concludes with the submission of the completed form.”

• “In the end, you receive a confirmation email.”

• "As a result, system sends confirmation email."

Add instructions to create the model and specify elements you wish to exclude.

You can enter additional prompts to explore models that reflect the information you'd like to view, such as suggesting which elements can be excluded from a process. For example:

• "Exclude IT Systems or data objects in the model."

• "Make it simpler, exclude IT Systems."