Web Stuff
Product Management Blog

 










Subscribe to "Web Stuff" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

 

 

  Monday, July 22, 2002


The question of eWork has been weighing heavy in my mind for several weeks now.  I am convinced of the potential business benefit of the product.  I believe that it could help the state do business in a more efficient manner.  However, there are some issues with eWork that need to be addressed.  If the following issues cannot be resolved, I would recommend that we concentrate on other things besides eWork:

  1. In order for eWork to be successful, there would need to be a product management resource that could devote most of his or her time to selling the product to agencies and getting them to develop processes with it.  We wouldn't even be able to come close to having a positive hard ROI until we have 150 or so processes in production.
  2. ITS would need to create a robust eWork development product that not only was able to produce quality eWork processes rapidly, but also be more economical than private eWork consulting services.  I believe that the agencies will choose not to develop very many eWork processes if they have to pay $200/hour to get it done.  At a minimum, ITS would need 2 full time eWork developers.
  3. eWork has to be an enterprise initiative, with the full support and backing of the CIO.  The risk of failure is higher if it is simply another product that ITS is force feeding to the agencies.

If ITS cannot allocate the resources mentioned above, and if eWork does not come to agencies as more of an enterprise initiative rather than an ITS product, then I say we don't do it.  There are plenty of other products that we could focus our attention on.  It is still a risky proposition even if those resources are allocated.  eWork is a BPM engine, and we would need to get agencies to take a fundamental look at their business processes, as we are currently doing with DHRM for a pilot project.  This is not an intuitive or automatic activity for most agencies.

I have these concerns, and I haven't even talked about how we would pay for it, and then recover the cost.  That adds a completely new dimension to my concerns, and it increases risk even further, especially in such a tight budget environment.


7:51:31 AM    comment []



Click here to visit the Radio UserLand website. © Copyright 2002 Dave McNamee.
Last update: 10/2/2002; 4:29:53 PM.

July 2002
Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      
Jun   Aug