As a general rule, one User will take responsibility for each step and will enter data into the input screen. However, there are also processes that could be done by more than one person and for which a standard procedure is not clear, for example where a committee is responsible for making decisions. [Team Swimlane] makes it possible to avoid processes becoming fragmented, and allows coordination between all those involved.
1. Usage Example of [Team Swimlane]
- a. Undefined Process
- To decide collegial responders and the number of responders, depending on the nature of the project (e.g. "Examining a Public Proposal")
- b. Fostering Organizational Intention
- Collect the dissenting opinion before conducting discussions in a meeting (informal decision for time-critical projects)
- c. Discussion by Multiple People
- Ask the whole team to discuss it until the issue is resolved
- d. Processing by Proxy
- To process as an act of one person for the sake of convenience, but the team support some or all of it
- [Team Swim Lane] is a definition format provided by Questetra, which is an extension of the international standard notation BPMN
2. Understand the outline of the Steps on the [Team Swimlane]
- a. Allocation of Issue
- When an instance reaches a Task in the [Team Swimlane], the instance will be displayed in the [My Tasks] list of the all candidate Users
- b. Processing Completion
- When someone [Finishes] the Task, then it disappears from the [My Tasks list] of all Users
- Select [Save and Quit] if you want to enter only some Data Items
- If Data input is competing, only the input of the last saved will be recorded
- It is effective to use the [Discussion] type Data Item that can be appended to existing data
- An option to require all of the Operators to complete handling the Steps is also available
