Modelling your Business Processes with Resolver Core
•
0 likes•173 views
The document discusses modelling business processes using workflows in Resolver. It defines key workflow concepts like states, triggers, transitions, conditions, actions and roles. It emphasizes designing workflows with a people-first mindset by understanding the problems from talking to employees and coming up with many potential solutions rather than just focusing on organizational needs. Effective workflows can track work stages, communicate with stakeholders, and make conditional decisions to improve efficiency and reduce wasted time, bad data and employee turnover.
Recommended
Recommended
More Related Content
Similar to Modelling your Business Processes with Resolver Core
Similar to Modelling your Business Processes with Resolver Core (20)
More from Resolver Inc.
More from Resolver Inc. (20)
Recently uploaded
Recently uploaded (20)
Modelling your Business Processes with Resolver Core
- 1. Modelling your Business Processes with Resolver
- 3. Hello! I am Ryan Thiessen Product Director at Resolver @RThiessen ryan.thiessen@resolver.com
- 4. And, I am Tim Chisholm Manager, Design at Resolver tim@resolver.com
- 5. What do we mean by Workflow?
- 6. “work·flow the sequence of industrial, administrative, or other processes through which a piece of work passes from initiation to completion
- 7. Modelling Processes using Workflow Administrative processes for work like: ▪ Incidents ▪ Audits ▪ IssuesObjects
- 8. Modelling Processes using Workflow CompletionInitiation
- 9. Modelling Processes using Workflow ClosedReviewOpen
- 10. Modelling Processes using Workflow ▪ Tracking the stage of a specific process ▪ Understanding ownership over that stage ▪ Set rules on changes stages toward completion ▪ Communicating with relevant stakeholders ▪ Conditional data driven decisions
- 11. Without Workflows Where are we with that thing? I don’t know, it’s waiting for someone to do something!
- 12. With Workflows What stage are we at with our quarterly audit? It’s in review with Bill.
- 13. With Effective Workflows Is all our work done? Yep.
- 14. Workflow Toolbox
- 15. States Triggers Transitions Conditions Actions Workflow Toolbox
- 16. States Workflow Toolbox ▪ Special “creation” state exists while a new form is started before anything is saved. ▪ Must have at least one state after creation that new objects are given. ▪ Must define who can create new objects for each type of “work”.
- 18. Workflow Toolbox ▪ 3 types of triggers Button Timed Event ▪ Each state has it’s own triggers. Triggers
- 20. Workflow Toolbox ▪ Defines the flow following a trigger to determine the next state. ▪ A trigger may have multiple transitions, the first one to meet all conditions will succeed. ▪ A transition can remain in current state. ▪ Transitions support the next 2 tools conditions and actions. Transitions
- 22. Workflow Toolbox ▪ Simple logical questions base on fields or related data to the current object ▪ Supports Numeric, Select List, Formulas, and Date values ▪ Simple greater than(>), less than(<),equal to(=), not equal(<>) ▪ Can join multiple conditions with AND, OR keywords Conditions
- 23. Creation Review Closed Amount > $1000 Amount < $1000 Submitted Date > 5 days ago Close Remind Submit
- 24. Workflow Toolbox ▪ Send email message ▪ Set or clear a field (select list or date) ▪ Initiate Event ▪ Unlink related objects ▪ Add or Remove Role Assignments Actions
- 25. Creation Review Closed Amount > $1000 Amount < $1000 Submitted Date > 5 days ago Notify Director Set Closed Date Set Closed Date Remind Supervisor Close Remind Submit
- 26. Workflow Toolbox ▪ Role defines what objects you can create to start a workflow ▪ Role access and ownership is defined for each state ▪ Setting role memberships assigns users a specific role for that process.Roles
- 27. Creation Owned by: Employee Review Owned by: Supervisor Closed Owned by: Manager Amount > $1000 Amount < $1000 Submitted Date > 5 days ago Notify Director Set Closed Date Set Closed Date Remind Supervisor Submit Remind Close
- 28. States Triggers Transitions Conditions Actions Workflow Toolbox Roles State Role Ownership Condition Action New StateTrigger
- 29. Workshop
- 30. What to consider when designing a workflow?
- 31. Bringing the tools of design to business Design Thinking
- 32. A company doesn’t do the work
- 33. People do
- 35. INEFFICIENT Wasted time on redundant actions and approvals BAD DATA Unmotivated workers are a high-risk to provide bad data HIGH TURNOVER Workers that feel misused are a threat to leave Problems with org-first design
- 39. How do I design a workflow for my people?
- 41. Talk to your people (They are going to have insights)
- 43. Come up with a lot of ideas