{"id":67,"date":"2015-12-12T02:32:16","date_gmt":"2015-12-12T02:32:16","guid":{"rendered":"http:\/\/it-toolkits.org\/blog\/?p=67"},"modified":"2016-07-11T09:32:17","modified_gmt":"2016-07-11T09:32:17","slug":"the-benefits-of-techology-standards","status":"publish","type":"post","link":"https:\/\/standard-toolkits.org\/blog\/the-benefits-of-techology-standards.html","title":{"rendered":"The Benefits of Technology Standards"},"content":{"rendered":"

\"IT-Toolkits_Standard\"<\/a><\/p>\n

Experience has shown that good things happen when the right set of end-user technology standards are appropriately planned and applied. Tangible benefits can be realized across a broad spectrum, ranging from improved IT service quality, to lowered technology management costs, and more (as the list below demonstrates):<\/p>\n

    \n
  1. By limiting the variety of hardware and software products in use, IT departments will have the opportunity to develop focused, in-depth product expertise, thereby improving the quality and responsiveness of essential technical support services.<\/li>\n
  2. By limiting the variety of products in use, IT departments can better test and manage product compatibility, thereby reducing the number of platform conflict problems.<\/li>\n
  3. Standardization can lower technology acquisition costs through volume purchasing, bringing discounted pricing, as well as greater leverage to negotiate more favorable maintenance and training contracts.<\/li>\n
  4. With a focus on a specific set of technology products, the end-user community will have the opportunity to develop in-depth product expertise – to enhance operational productivity and maximize technology utilization.<\/li>\n
  5. Standardization can minimize the risks associated with an uncontrolled technology portfolio, facilitating disaster recovery planning, software licensing management, and security management.<\/li>\n<\/ol>\n

    This list is impressive, but by no means guaranteed.\u00a0 Standardization is not the answer to every problem, and the best standards will amount to little more than “bureacracy” if not properly designed and implemented. Under certain circumstances, standards can also backfire, creating more problems than they solve. When standards are created simply for power and control, lacking sufficient flexibility, and without full consideration of business needs, in all likelihood, they will be bypassed.\u00a0 This help no one – not the business, not the end-users and certainly not the IT department.<\/p>\n

    Step by Step to Standards Planning<\/h3>\n

    Step 1: Identify primary goals and objectives<\/strong>. What are your current needs and how will standards help you meet your goals and objectives? This analysis will form the basis for your standards justification needed to convince skeptical end-users and ambivalent managers.<\/p>\n

    Step 2: Identify requirements.<\/strong> What types of technology products (hardware and software) will be addressed by these planned standards?<\/p>\n

    Step 3: \u201cOne Size Probably Does Not Fit All\u201d.<\/strong> Make sure you provide sufficient alternatives within any hardware or software product set, to accommodate different needs and preferences.<\/p>\n

    Step 4: Consider remote locations.<\/strong> Small satellite offices may have unique needs to which established standards may not apply. You may need to create new standards for remote sites or carve out appropriate exemptions.<\/p>\n

    Step 5: Be flexible.<\/strong> Create standards with sufficient flexibility, providing for a “waiver” process so that “non-standard” products can be utilized whenever needed.<\/p>\n

    Step 6: Involve end-users in the standards process.<\/strong> Establish a workable process for standards development and approval, which involves the end-user community.<\/p>\n

    Step 7: Communicate.<\/strong> Keep end-users sufficiently informed about all elements of the standards process. You will need to let end-users know how standards are selected, what the current standards are, how to request a waiver, and how to submit a desired product for standards review. You can do this through a newsletter, policy manual, new employee orientation, training session, or through any other marketing method available to you.<\/p>\n

    Step 8: Ask for feedback<\/strong>. Provide an open, publicized mechanism for feedback on your standards selections and related processes. The more buy-in and participation you get the better. At least people will be talking about the process, even if the standards themselves are in dispute.<\/p>\n

    Step 9: Enforce standards consistently.<\/strong> Standards<\/em> will be meaningless if your end-users know that they can be easily ignored (or bypassed). If standards are to deliver expected benefits, you must have sufficient management support to enforce related policies and procedures. This level of management support will be easier to come by if you maintain open communications with your end-users, and if you are prepared to justify standards decisions with “facts and figures”.<\/p>\n

    Step 10:\u00a0 Integrate standards guidelines and purchasing procedures.<\/strong> Standards will be easier to control and maintain when they are supported by relevant purchasing procedures.\u00a0 If the IT department is responsible for technology acquisition, standards can be more readily enforced. However, depending upon organizational needs and considerations, it is not always feasible for the IT organization to carry the burden of order processing.\u00a0 In these cases, you might ask your purchasing department to forward non-standard<\/em> purchase requests to IT for review.<\/p>\n

    Step 11: Don\u2019t abdicate IT responsibility.<\/strong> If the only response given to a request for non-standard<\/em>technology is “no”, you’ll just end up with a fair number of unsupported products and a whole lot of finger pointing. Collaborative approaches are far more effective, to work with end-users and to find acceptable solutions to unique technology needs.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Experience has shown that good things happen when the right set of end-user technology standards are appropriately planned and applied.<\/p>\n","protected":false},"author":1,"featured_media":130,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-67","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-it-policy-development"],"_links":{"self":[{"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/posts\/67"}],"collection":[{"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/comments?post=67"}],"version-history":[{"count":0,"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/posts\/67\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/media\/130"}],"wp:attachment":[{"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/media?parent=67"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/categories?post=67"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/standard-toolkits.org\/blog\/wp-json\/wp\/v2\/tags?post=67"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}