Business Processes and Workflow How to go from idea to implementation Ryan Moffitt, Senior Technical Advisor ® 2012 Aderant Holdings, Inc. All rights reserved.
Content Ideas and Planning Implementation Concepts Naming Conventions SME’s Defined Documentation Processes Create Documentation Review Change (while Signed <> True go to Review) Sign Off Design Requirements Interface (UI) Database Tables & Columns Implementation Conceptual Overview System Understanding Architectural Review Troubleshooting Monitoring and Reporting Training End User Administrative User Acceptance Application Interface Workflow ® 2012 Aderant Holdings, Inc. All rights reserved.
Ideas and Planning: Concepts Routing Decisions Approvals Contextual Values Data Concepts Software Design Error Handling ® 2012 Aderant Holdings, Inc. All rights reserved.
Ideas and Planning: Naming Conventions Defining the Firm Vernacular What is an Office? What is a Department? What is a Practice Group? How is an Attorney defined? How is a Partner defined? Make sure everyone in on the same page! ® 2012 Aderant Holdings, Inc. All rights reserved.
Ideas and Planning: SME’s Defined Have a clearly defined group of Subject Matter Experts for each different logical step. Accounting Rules Conflicts Rules Marketing Information End Users (Wide Sampling) Define Decision Makers Who is going to make the final call about business decisions? ® 2012 Aderant Holdings, Inc. All rights reserved.
Ideas and Planning: Documentation Single Most Important Piece Set the Expectations and the Scope and Don’t Change them Be VERY Detailed Set Standards Review and Refine Document every piece Data Interface Approvals E-Mails Assignments Naming Conventions Et Cetera Review and Refine again Document for the least skilled staff member ® 2012 Aderant Holdings, Inc. All rights reserved.
Ideas and Planning: Design Requirements Design the UI for Functionality with Importance on Data Integrity Don’t give up data integrity for user functionality Verify the Fields & Values Used by the Firm Fields and Tables getting updated Do Not Assume – Be Specific (When x happens, n field = y) Review standard naming conventions and how they relate to the firm’s use ( Does Department = HBL_DEPT.DEPT_CODE?) ® 2012 Aderant Holdings, Inc. All rights reserved.
User Interface Design the general idea of the information you want to present to the end user Design the exact text that you want to display to the end user. Determine the wording of all notifications, e-mails, alerts. (Keep in mind that dynamic text may be useful). Determine a standard syntax and maintain it throughout the workflow. ® 2012 Aderant Holdings, Inc. All rights reserved.
Implementation: Concepts Understanding of Workflow Concepts Review Tasks, Approvals, Status, etc. Define Responsibilities Who is responsible for which aspect of the workflows? Business Rules Technical Troubleshooting Escalations Reporting ® 2012 Aderant Holdings, Inc. All rights reserved.
Implementation: System Architecture Understanding of All the Moving Part Databases Services (Web and Legacy) AppFabric Client Applications Troubleshooting Know how to use logging, Windows Event Viewer, and AppFabric to troubleshoot issues Using reports and how to build custom reports to have an administrative view of the system ® 2012 Aderant Holdings, Inc. All rights reserved.
Implementation: Training End User Training Start Early – Get users used to any new technology as soon as possible Plan Roll Out Administrative Training Security Reporting Monitoring Task Management, etc. ® 2012 Aderant Holdings, Inc. All rights reserved.
Implementation: End User Acceptance Get the users buy in from the beginning Talk to users and listen to their input Easy to make small changes early to help with acceptance Have them test the Interface and the Workflow ® 2012 Aderant Holdings, Inc. All rights reserved.
Client Example: Matter Close ® 2012 Aderant Holdings, Inc. All rights reserved.
® 2012 Aderant Holdings, Inc. All rights reserved.
® 2012 Aderant Holdings, Inc. All rights reserved.
® 2012 Aderant Holdings, Inc. All rights reserved.
® 2012 Aderant Holdings, Inc. All rights reserved.
® 2012 Aderant Holdings, Inc. All rights reserved.
® 2012 Aderant Holdings, Inc. All rights reserved.