tag:blogger.com,1999:blog-29020225.post3853086510866697088..comments2023-11-08T08:32:41.971-05:00Comments on Improving It: My process is not Mickey Mouse, but it doesn't need ITPhil Ayreshttp://www.blogger.com/profile/14708790980510403134noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-29020225.post-28428715846485574082010-03-23T08:32:50.254-04:002010-03-23T08:32:50.254-04:00Adam, Scott, I agree with both of you that a bit o...Adam, Scott, I agree with both of you that a bit of code and focus on technology becomes necessary at some point. Unlike Lean suggests, BPM projects rarely go for a truly incremental / continuous improvement approach (in my experience anyway), as the business customer knows that it is unlikely they'll ever persuade IT to help them with Phase 2. So the try to do everything in Phase 1, leading to poor focus of resources, and half-hearted efforts at really architecting a solution to avoid these coding issues.<br /><br />I have also experienced too many times the way just a little Javascript here, and a little there suddenly morphs into having the rules of the system enforced in the UI code. It produces a seamless effect for the end user, but makes even the easiest change to the system much harder.<br /><br />There is an approach in UI design that users learn what not to do faster in a UI that tells them about their errors on submission, rather than at the entry of every field (although the learning curve is steeper). This is the reverse of modern user experience design, so I fear we will see more and more systems that do not separate their logic from their presentation, making them almost monolithic in nature.<br /><br />Thanks, PhilPhil Ayreshttps://www.blogger.com/profile/14708790980510403134noreply@blogger.comtag:blogger.com,1999:blog-29020225.post-75117757495481456452010-03-22T19:42:35.136-04:002010-03-22T19:42:35.136-04:00I think there's a good lesson to learn from &q...I think there's a good lesson to learn from "Lean" here- which is that technology should not get in the way of improving the process. And you can save a lot of $ if you first get the process right and then invest in the code/tech required to make it sustainable. (Often, unfortunately, Lean advocates forget the last part - investing in tech to make the process improvements stick, rather than trending back to previous norms over time).Scott Francishttp://www.bp-3.com/blogsnoreply@blogger.comtag:blogger.com,1999:blog-29020225.post-58415013040978343902010-03-21T20:39:19.342-04:002010-03-21T20:39:19.342-04:00Hi Phil,
Good article, but I don't agree with ...Hi Phil,<br />Good article, but I don't agree with your bottom line. <br />"Rationalization" and "a way of delivering work faster" are only two of the process problems.<br /> <br />A bit of code is always needed to spice up the forms and create custom reports. It might not be a lot of coding, or even highly skilled coding – but it is still coding.<br /><br />http://adamdeane.wordpress.com/2010/03/09/bpm-no-coding-myth/Adam Deanehttp://adamdeane.wordpress.comnoreply@blogger.com