When it comes to commercial technology solutions, you will be addicted to the latest, best gadgets and solutions. Everyone wants it. In large organizations, conflicting and overlapping technical requirements can create angel technology management. If not packaged, the company’s technology platform can be like a “spaghetti” bowl at any time. In some cases, new technical requirements are sent to support such investments without a business case.
I strongly support business leaders who are not active role models when determining the technical solutions used in the organization. While it’s important to include an IT perspective in the technology interface, extending a non-IT to a technology solution typically makes decisions based on the organization’s business needs. Therefore, any technical requirement requires a business plan to support such investments. The establishment of a technical committee: This is the beginning of the technical approval process. Establish a technical committee to represent multiple people across functions.
For this team, choose members of Operations, Marketing, Accounting, Technology and Finance. The committee will provide the organization with a request to send a technical solution, priority and final approval request. Develop a submission process: Through the organization’s technology strategy, a good idea is to develop a process for submitting ideas. By developing a detailed submission process under the concept of “decoration and obsolescence”, you can eliminate “good things” and focus your committee on specific and specific solutions.
This process should include not only identifiable technical solutions, but also business cases that demonstrate legitimacy. For approved projects in the queue, monthly communications should be sent to the organization to summarize the committee’s activities. Focus on your project: The technical committee will focus on all organizations.
It’s best to release new technologies every time, but it’s not real and expensive. The committee noted all the requirements and helped to provide a high-level view of the entire company. In some cases, departmental requirements are often carried out on isolated islands, considering only the impact on the sector. It’s easy to have a couple: this is an important game. It’s easy to know that iPhone 3 will be rare after the iPhone 4 is released, but if the technology is managed by the committee, “good to go” fails because there is no business case.
The committee allows organizations to operate with technical barriers. The committee is responsible for improving the return on investment of these technology solutions and organizing them across departments, so there is no “pet” project. A project, a great picture: I have been researching technical committees in the past, but for me, the biggest “oh” time is the same number of technical solutions from different departments. If all of these requirements are met, the organization will not only create duplicate solutions for the same problem, but also charge IT costs.
The committee allows members to “beyond” organizational struggles and see an overview of technical requirements. The purpose of the committee is to ensure that approved terms are provided throughout the company. Doing business: This is the best way to get rid of confusion. Get the needed from a technical solution, a mature idea organizer. Thank you for your business (investment cost limit) and the few solutions and ideas.
The business case for a technology solution not only helps determine if the investment is beneficial, but also recommends to the author how the solution works on an existing platform. Post-mortem analysis: Finally, the responsibility of the committee and the provider is to carefully measure the form of the business case and compare it to the appropriate cost/income. The purpose of the ex post analysis is not to “call people” but to provide fair financial research for the project. If there is no such step to measure the team that can be released, the committee will be useless.