{"id":44,"date":"2009-03-12T00:27:19","date_gmt":"2009-03-12T00:27:19","guid":{"rendered":"http:\/\/www.spekle.com\/rsfm\/?p=44"},"modified":"2019-03-05T11:09:04","modified_gmt":"2019-03-05T11:09:04","slug":"innovation-in-packaged-applications","status":"publish","type":"post","link":"https:\/\/www.spekle.com\/RSFM\/innovation-in-packaged-applications\/","title":{"rendered":"Innovation in Packaged Applications"},"content":{"rendered":"<p>\t\t\t\tWhen I read this <a href=\"http:\/\/blogs.gartner.com\/jim_holincheck\/2009\/02\/26\/business-software-innovation-not-one-size-fits-all\/\">post<\/a> of\u00a0 Jim Holincheck of Gartner it really got me thinking. Jim reacts on a post which is arguing that Oracle is not focusing on\u00a0stability and quality before innovation in its packaged solutions. Jim responds that you have core and context applications. Context applications are applications that a company needs, but not to be competitive. A good example is a salary system for most of the companies, it doesn&#8217;t improve your market position but you need it to pay your employees. Core applications make you competitive, you could imagine that a system that supports the logistics of a parcel distributor can make him very competitive. Jim wonders what innovation is wanted in packaged applications.<\/p>\n<p>I think a variation on &#8216;Maslow&#8217;s hierarchy of needs&#8217; is in place here. A company first needs its core application(s) very fast followed by some essential context applications. Since these context applications do not make you more competitive you should minimise cost here. So stability is in place. When your context application is doing what is should do, you do not want to be burdened by a obligatory update because a vendor innovated some new options and\u00a0puts old versions out of support. I don&#8217;t think that a lot of companies use a lot of new features of Word compared to Wordperfect 5.1 functionality which was the standard 10 years ago. I think the innovation we need in context applications is a more modularized approach or a service approach where you can update by module and service in stead of a complete release. It&#8217;s like when you start blogging with WordPress. You install the very basic version and can add features by installing extensions. This would be a nice way of working for context applications.<\/p>\n<p>Innovation, meant as doing business smarter or different to make you more competitive (to earn more money) cannot come from packaged applications. Because\u00a0when the innovation is packaged it&#8217;s available for everyone. So it will only help you for a short while when you can implement it fast, you will not be more competitive after a while because everyone has implemented it. Packaged applications can help innovation when they can be flexible. Again being more modular or service enabled would make it possible to orchestrate the process you want and thus be different than your competitors and hopefully earn more money than them. Offcourse the packaged application should be open to support the orchestration. This idea of flexible and innovative processes is part of the &#8220;Technovision&#8221;\u00a0 of Capgemini and called\u00a0 <a href=\"http:\/\/www.capgemini.com\/services-and-solutions\/technology\/technovision\/clusters\/process-on-the-fly\/\">&#8216;Process on the fly&#8217;<\/a>.<\/p>\n<p>So I think the innovation wanted from packaged applications is being more stable when they are context applications, which can be reached by being modular and flexibel. This same feature can help a company to innovate by using these services\/modules in their &#8216;Process on the fly&#8217;.\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I read this post of\u00a0 Jim Holincheck of Gartner it really got me thinking. Jim reacts on a post which is arguing that Oracle is not focusing on\u00a0stability and quality before innovation in its packaged solutions. Jim responds that you have core and context [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-44","post","type-post","status-publish","format-standard","hentry","category-architecture"],"_links":{"self":[{"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/posts\/44","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/comments?post=44"}],"version-history":[{"count":1,"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/posts\/44\/revisions"}],"predecessor-version":[{"id":64,"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/posts\/44\/revisions\/64"}],"wp:attachment":[{"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/media?parent=44"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/categories?post=44"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.spekle.com\/RSFM\/wp-json\/wp\/v2\/tags?post=44"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}