Scenario Building Instructions
# Instructions For Scenario Building
SequenceStack enables you to create tailored scenarios for your organization by defining workflows and interactions using our sequence engine. There are some basic instructions you can provide to make your custom scenario tailored for your organization. At SequenceStack, you can augment your own custom instructions with our sequence engine.
Here is an example of an outstanding set of instructions.
Set up your headers right from the start.
Adjust Your Title Instructions
Let SequenceStack know what you purpose it
Include a note to help the reader get oriented.
There are times when simpler is better. In order to do this, you will need to limit the output.
By limiting the roles to one, you will only have one actor. This is much better as you will have only one person interacting with your sequence. If you don't limit it, you could have a diagram that is very difficult to control and manage.
By limiting the number of lifelines, you can make the diagram less cluttered and easier to manage. Aim for 3 or fewer lifelines to keep the sequence clear and concise.
###### Require URLs
URLs make sequences much more reliable. You can include your own or ask SequenceStack to find references for you. It is much better to provide your own.
'Include this in a note: "For more info, see SequenceStack Documentation"'
You can include additional instructions or notes for each step of your sequence to clarify the context and provide more details.
Include Descriptive Notes:
Before starting a sequence, add an overview or note to set expectations and context.
html
Copy code
"This sequence details the process for [Process Name], providing clarity on each role's responsibilities and actions."
Example Use Cases
Approval Workflow Scenario:
SequenceStack enables you to create tailored scenarios for your organization by defining workflows and interactions using our sequence engine. There are some basic instructions you can provide to make your custom scenario tailored for your organization. At SequenceStack, you can augment your own custom instructions with our sequence engine.
Here is an example of an outstanding set of instructions.
Title: "Hiring Approval Process At Acme Co for [_name_]"
Purpose: "We want to outline the initial review steps for hiring approval."
Only Use These Roles: Applicant, Hiring Manager
Limit of Lifelines To 3
Limit the number of messages to keep this sequence brief.
Include this note before your sequence: "For more info, see: [OPM hiring Guidelines.](https://www.opm.gov/policy-data-oversight/hiring-information/)
Building Your Sequence Headers
Set up your headers right from the start.
Setting The Right Title
Adjust Your Title Instructions
"Title: Some Action: - [One-word summary of input]"
Establish a Purpose
Let SequenceStack know what you purpose it
Use this purpose: "We want to break out the workflow for [_Specific Process_]"
Adding Content
Include a note to help the reader get oriented.
Include this note before your sequence: "For more info, see [website](https://www.google.com)"
Decluttering Your Sequence Output
There are times when simpler is better. In order to do this, you will need to limit the output.
Limit Actor Involvement
By limiting the roles to one, you will only have one actor. This is much better as you will have only one person interacting with your sequence. If you don't limit it, you could have a diagram that is very difficult to control and manage.
Limit the Number of Roles to 4
orLimit the actor to 1 role: "Marketer"
Minimize the number of Lifelines
By limiting the number of lifelines, you can make the diagram less cluttered and easier to manage. Aim for 3 or fewer lifelines to keep the sequence clear and concise.
Limit the number of lifelines to 3 (or whatever number you want)
###### Require URLs
URLs make sequences much more reliable. You can include your own or ask SequenceStack to find references for you. It is much better to provide your own.
When URLs are encountered, you must include the entire URL exactly as it is typed.
'Include this in a note: "For more info, see SequenceStack Documentation"'
Adding Instructions to Each Step
You can include additional instructions or notes for each step of your sequence to clarify the context and provide more details.
Include Descriptive Notes:
Before starting a sequence, add an overview or note to set expectations and context.
html
Copy code
"This sequence details the process for [Process Name], providing clarity on each role's responsibilities and actions."
Example Use Cases
Approval Workflow Scenario:
Updated on: 09/10/2024
Thank you!