7: Be visual, document less, automate more. BPMS tools that need programmers are a thing of the last century. Today’s best in class tools are very visual and easy to understand even by non-technical users. Ensure that you use the workflow charting capability of your BPMS solution to describe every aspect of the processes you are automating. Expose your users to the tool, get them used to seeing the tool being used. Soon they will have the vocabulary of BPMS and be thinking in workflow terms. This really improves communication between the implementation team and the users and significantly speeds design and acceptance. If your BPMS tool frightens the users you picked the wrong tool.
Tell us what you think
Click here to take a brief 7 question survey to help me improve my blog. Thanks.-
Recent Posts
- Lost in Petty France: taking agile to the enterprise
- Managing deployed mobile apps
- Best practices for tighter timeframes
- Should developers performance test their code before checking it in?
- What is the benefit of doing performance testing earlier in the application lifecycle?
- What is the value of Data?
- ALF, OSLC and SLI – enough of the soup, time for some meat
- Will we ever ‘just say “no”?’
- Testing times for system designers
- Thinking about focus
Archives
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- October 2012
- September 2012
- August 2012
- July 2012
- May 2012
- April 2012
- March 2012
- December 2011
- November 2011
- October 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
Categories
Meta
Twitter Updates
Error: Twitter did not respond. Please wait a few minutes and refresh this page.