SharePoint Adoption Broken? Fix it with Workflow and Forms!
•
0 likes•327 views
This deck was used during my SharePoint Workflow session at DogFoodCon held in Columbus, OH in September of 2014.
Recommended
Recommended
More Related Content
What's hot
What's hot (7)
Similar to SharePoint Adoption Broken? Fix it with Workflow and Forms!
Similar to SharePoint Adoption Broken? Fix it with Workflow and Forms! (20)
Recently uploaded
Recently uploaded (20)
SharePoint Adoption Broken? Fix it with Workflow and Forms!
- 1. SharePoint Adoption Broken? Learn how to fix it with Workflow and Forms Presentation by @BradOrluk
- 2. About me Brad is a Nintex Technical Evangelist with over 10 years of IT architecture, administration and sales experience. As an Information Architect at a Fortune 500, he has worked on business and IT process improvement and automation on a variety of real world global projects and productivity initiatives. Brad’s unique technical, yet business focused, background gives him the ability to help users leverage their SharePoint investments to drive value and increase adoption across their businesses.
- 3. Agenda What’s important to you? OOTB vs OTS vs Custom Dev Empowering Users Common Workflow mistakes What’s possible?
- 4. Want to automate manual business processes? Need to drive adoption? Want to write custom code?*
- 6. Good Uses of SharePoint Workflow • Managing how people work – Document approval & feedback – Collaborative reviews & discussions – Gathering signatures
- 7. Good Uses of SharePoint Workflow • Automating some of SharePoint’s behavior – Approve site creation requests – Parse incoming email in a list and act on it – Publishing items to target – Moving documents through lifecycles
- 8. Possible Uses of SharePoint Workflow • Manipulating other applications, data sources – Employee onboarding – Resource scheduling • SharePoint lists become work queues • Giving new life to Lotus Notes database content
- 9. Bad Uses of SharePoint Workflow • Transaction-oriented processes • Blocking or modifying activity • Application-to-application service activity • Aggressive data transformations • Work that doesn’t involve SharePoint at all
- 10. Pitfall 2 Not Planning to Fail
- 11. Consensus May Not Exist • Get 3 employees and 1 manager together • Talk about a process • Little agreement • Documentation disagreement, too
- 12. Initial Failure as a Winning Strategy • People do not want to hear these hard truths. • You may have to create an initial workflow just to show how awful a process is. • Only then can you change it.
- 13. Pitfall 3 Not Focusing on Basic Processes
- 14. Start Simple Process Step Step Step Automate this first Automate these later
- 15. Everyday Processes • Steal time • Get in the way • Annoy users
- 16. Everyday Processes • Have few stakeholders (even if many participants) • Are easier to automate (Provisioning, onboarding, etc…) • Free up time to focus on more critical stuff
- 17. Pitfall 4 Over complicating it
- 18. The Form is the User Interface • Not the workflow • Not the data
- 19. Form-Only App Problems • Hidden logic • Disconnected logic • Security • Complexity without code • Inheritance / Knowledge Transfer
- 20. Make the Workflow Do the Work • Documented • Auditable • Easier to change • Easier to manage
- 21. You’re Already Using SharePoint • The list itself can be the report • Users can sort, group, filter on metadata (Leverage Views!) • Write progress information to item properties • Stage Workflows already do this
- 27. DEMO
- 28. • Nintex.com Resources – Request an evaluation – Request a hosted team site • Connect.nintex.com – Documentation – Tutorials – Community Forums • YouTube – How to videos – Testimonials • Evangelists Blogs – www.bradorluk.com – www.vadimtabakman.com
- 29. Q & A
- 30. THANK YOU!
- 31. www.nintex.com
Editor's Notes
- We should ask ourselves some questions before we decide to develop a new application. For instance, how long will we have to deliver the final product, who will own the final solution, will this application be static at completion or will it need to be improved or adjusted to accommodate some unforeseen process down the line, can this be accomplished with OOTB toolsets (1st party or 3rd),?
- Presenter guidance: Use this time to demo Office 365 to the audience. How to demo: There are different ways to demo the new Office. It really boils down to how much time you have with the customer(s) and what the customer(s) are interested to see. The best way to demo is to set up your demo tenant at http://www.MicrosoftOfficeDemos.com. It includes demo content as well as demo script specifically designed for small and midsize businesses. If you are not able to demo, here are other options: - For one-on-one customer engagement, assuming you use Office 365 for your own company, you can also just show your own environment to demo how you use it. - Or pick one of the videos from this list: http://www.youtube.com/user/MicrosoftOffice365 http://www.microsoft.com/en-us/office365/customer-stories.aspx http://office.microsoft.com/en-us/support “What Office 365 means to me” http://www.youtube.com/watch?v=Vn-qSzO_0lg