{"id":45,"date":"2009-05-17T22:10:00","date_gmt":"2009-05-18T04:10:00","guid":{"rendered":"http:\/\/userharmony.com\/blog\/?p=45"},"modified":"2012-07-24T15:33:23","modified_gmt":"2012-07-24T21:33:23","slug":"10-ways-to-ensure-failure-to-produce-great-enterprise-software","status":"publish","type":"post","link":"https:\/\/userharmony.com\/blog\/2009\/05\/17\/10-ways-to-ensure-failure-to-produce-great-enterprise-software\/","title":{"rendered":"10 ways to ensure failure to produce great enterprise software"},"content":{"rendered":"

\"\"<\/a>
\nWhere do most enterprise software projects go wrong? As a software manager, how can you ensure that the next application your team is about to build will revolutionize your enterprise? Here are my top ten ways to ensure failure to raise the body of work beyond mediocrity:<\/p>\n

    \n
  1. Have no real vision behind the project<\/span>: If the application is not really going to solve any real pains for the consumers of the applications, don\u2019t do it. Cost savings, ease of maintenance – are all noble goals in themselves, but not as worth doing as making that application more useful for the end users.<\/li>\n
  2. Outsource everything to a consulting firm:<\/span> Firms like Ideo<\/a> are great when it comes to pinch-hitting that creative idea for you. However, they are not you. Consulting firms cannot replace the lack of in-house talent. They are not a sustainable model when it comes to creating innovation from ground up within the organization. So send your staff to learn from companies like Ideo, but give them fertile ground to grow the organization from within.<\/li>\n
  3. Implement only the customer\u2019s stated desire:<\/span> If the innovative direction of your product is purely driven by the \u201cstated\u201d features desired by customer, you are putting the customer solely in-charge of the product. Listen to the customer, but don\u2019t put them completely in-charge. Listen, observe, re-learn – from both stated and unstated desires.<\/li>\n
  4. Shield developers from customers:<\/span> Developers develop software. But have they put a face to the end user who may use the product? Do they feel the connection on a human level? Do they understand the frustrations experienced by the end users? A relationship with the users will result in better product than a relationship with a requirement specification.<\/li>\n
  5. Time-box everything:<\/span> Letting deadlines drive launch decisions rarely proves to be sustainable. Do it if you can really be ready, but don\u2019t sacrifice quality to meet a launch date. It’s not worth the negative karma from customers.<\/li>\n
  6. Deny mistakes:<\/span> Nothing is more refreshing than companies admitting they got it wrong. Nothing will restore the respect for you as a leader if you admit a bad decision. Refusal to do so will build a culture around you in which failure is seen as something terrible and to be avoided at all costs.<\/li>\n
  7. Don\u2019t take time to play:<\/span> If you want your team to be excited about coming back to work on any given Monday, then you have to make time to play. Channel play time into concrete innovations.<\/li>\n
  8. Don\u2019t talk to everyone:<\/span> Don\u2019t get second hand information from the layer of hierarchy that reports directly to you. Take time to wander around, mingle and get a real grip on problems that may prevent the software from being successful.<\/li>\n
  9. Don\u2019t harness everyone\u2019s ideas:<\/span> You are the boss. Are your ideas are the most important? Wrong. Ideas that will solve your company\u2019s problems may be closer and cheaper to find than you can imagine and they may not be your own. Start by asking your staff. Continue by inspiring them to improve every single day.<\/li>\n
  10. Have two different game faces – one for employees and one for investors:<\/span> If your team has no idea into the strategic decisions and direction the company is taking, and they have no idea of company\u2019s financials, they may never understand some of motivations for project decisions. Bring their heads into the game.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

    Where do most enterprise software projects go wrong? As a software manager, how can you ensure that the next application your team is about to build will revolutionize your enterprise? Here are my top ten ways to ensure failure to raise the body of work beyond mediocrity: Have no real vision behind the project: If […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5,3],"tags":[],"class_list":["post-45","post","type-post","status-publish","format-standard","hentry","category-innovation","category-leadership","category-teamwork"],"_links":{"self":[{"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/posts\/45","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/comments?post=45"}],"version-history":[{"count":4,"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/posts\/45\/revisions"}],"predecessor-version":[{"id":139,"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/posts\/45\/revisions\/139"}],"wp:attachment":[{"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/media?parent=45"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/categories?post=45"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/userharmony.com\/blog\/wp-json\/wp\/v2\/tags?post=45"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}