Some really nice thoughts and comments/links.
Process design is a relative term. For any designed process the Business can succeed or fail till a logical point/checkpoint > One can never design a Once in a Lifetime Process and take a back-seat| Business is dynamic, Customers are dynamic and so are the designed processes
Bad process for one may be a Great one for the other. And a Good process today can also end up in a thrash can tomorrow
Time + User Base + Biz Priorities + Surround Systems + Architecture Changes + Latest Trends + other factors > have impact on the Process Design
Case 1: For a file attachment to case data/ work-objects, we can design the process that embeds the attachment to the Work Object and gets rendered each time the work instance is opened.(considering a small file having only the address details)
Case 2: Based on some future requirements and enhancements, if the file size of the attachment grows and multiple attachments come to the picture > our design will fail as it will hot the performance based on payload / launching the work object details screen
In this case > leveraging a Enterprise Content Management solution may be the ideal solution, where in the Files can be pushed to the ECM and the Work object can be made light weight > by just adding a EXM URL link to the file.
We cannot consider Design as Bad in the 1st Case : as investing on ECM at initial phase for a small file might be a costly affair
Whats your take ?? – Can Companies Still Succeed With Poorly Designed Processes?
Happy Reading!! 🙂