Optimizing Your Clarity Support Team

1. Optimizing Your Clarity Support Team

2. Agenda • Components of Support • Company Support Profile - Survey • Sample Org Charts • Common Support “Holes” • Missing Roles • Turnover in Staffing • Request Process • Survey Results • Keys to Successful Support • Q&A

3. Components of Support - Functions • Management – Overall Application and Process Leadership • Technical Development – Level 2 • Portlets, Reports, Processes, Configuration, Universes • Technical Infrastructure • Infrastructure HW/SW Upgrades and Maintenance • Database Monitoring and Health – including performance monitoring • Application Monitoring and Health – including performance monitoring and log review • Performance Monitoring • Functional – Level 1 • User Questions • Data Administration – OBS, Lookups, New Projects/Resources • Security Setup and Maintenance • Job and Processes Monitoring • Functional – Level 2 • Business Analysis – requirements • Testing – Enhancements and projects • Defect Investigation • Project / Release Management – Upgrades, Releases • SMEs & Evangelists & Trainers • Mentoring • Training

4. Components of Support - Bodies • Core Application Team • Requirements Definition • Configuration / Portlet Development • Project Management • Solution Architecture • Operating Committee • Set Initial Priority and Sequencing of Enhancements • Provide Context and Justification for Local Requests • Communication with Local Groups • Approval of Release Contents, then Later, Notes • Application Owner • Works with Leadership to Define Roadmap • Resolves Conflicts and Owns Priority • Ensures solutions are in best interest of the Organization • Communicates Change

5. Components of Support - Activities

6. Components of Support - Activities

7. Components of Support - Activities

8. Company Support Profile • How Many Here are Happy with Current Support and Staffing? • We are Always Asked – What is the Right Level of Support • We Did a Survey of 15 companies years ago • Time for an Updated Version • Survey • Fill Out Paper • You Can Keep Anonymous • Collaborate with Others in Your Company – Submit One • We Will Collect and Then Give You all the Data

9. Previous Model From Surveys – Example Notes: • Excludes major project work like upgrades or major functionality deployments like resource management • Excludes some amount of consulting for architecture and project BA/Developer resources • Figures will vary based on organization maturity and structure for monitoring and controlling with the organization

10. Survey Questions • See Handout

11. Sample Org Chart – 20K+ Users

12. Sample Org Chart – 1,500 Users

13. Support “Holes” – Missing Roles • Insufficient Hosting and DB Support (On Premise) • No performance monitoring • No resources to help with efficient upgrades – takes too long • Lack of Ongoing Mentoring/Training • No Support for New RM/PMs • No mentoring to help them better use Clarity and get new requirements • Clarity Architecture • Roadmap • Portlets and Reports with Poor Performance • Complex Solutions vs. Changing Process • Poor Setup of RM / FM Architecture of Fields / Roles / Skills / OBS • Others?

14. Support “Holes” - Turnover • How Many Have Had Support Staff Leave? • How Did you Replace? • Hire a Clarity expert? • Train someone internal? • What Type of Resource found successful? • Outsourced to a firm? • How Do You Protect Against Turnover or the Impact of Turnover? • Over Time, Do You See Support Increasing or Decreasing? • What are Some Ways We Can Reduce Support? • Automate monitoring, log reading, etc?

15. Support “Holes” – Request Process • Not enough enhancements are completed – they take too long and users lose patience and confidence

16. Support “Holes” – Request Process Planned Work Unplanned Work Enhancements / Change Req Projects / Initiatives User Requests / Defects Incidents Level 1 Prioritization Process Architecture Level 2 Level 2 (BA, Portlets, Prototype) Level 3 (Jobs, escalation) Level 3 (Queries, Scripts, Migration, Reports) Level 4 Level 4 (Migration)

17. Open Discussion • Other Support Holes? • Summarized Findings of Survey

18. Keys to Successful Support • Short Cycle Time • Let the users drive functionality quickly. If the users believe their enhancements, defects, etc. take too long or do not meet their needs, they will look elsewhere to get their data or implement their process. • SMEs are a Critical Role • Having users constantly mentored and trained is very important. The organization constantly changes and people need a refresher. • Have a Vision and Stay Current • Identify targeted functionality or reporting each year. Always have a goal or vision for where you want the adoption of Clarity to be next year. Part of this is also staying current with Clarity – do not let the environment get too far behind in releases • Staff a Solid Team • People are always the most important element. A few good people can keep you moving forward even on a shoestring (Big Bank Example of Support Shift). Outsource if you need to.

19. Questions Contact US 888.813.0444 Email Contact info@regoconsulting.com Web Site www.regoconsulting.com Thank you.