Who technology decisions should be made by depends on the circumstances. For instance, if the technology being purchased is an email system, servers, security, telephony systems, network equipment or anything of a similar nature the technology department should primarily make that decision. The technology department (IT guys or gals) is best suited to know the needs of the organization since they are servicing helpdesk tickets every day. They are also in the best position to know what type of system, network speed or application is going to meet 90-95 percent of the needs based on their review of existing and available systems. Also, at this point the question has less to do with features and more to do with base functions and price.
If, on the other hand, the decision is around a line of business application like an accounting system, billing system, grant management system, or a company's main product line the business managers and leaders need to be highly involved with providing the requirements for the solution and they need to have a large say in what is decided. These individuals are going to be using the system the majority of the time, they understand the business or regulatory environment best, they are the ones interacting with customers and know what is being requested, and if their wishes and needs are unaccounted for the system may never live up to expectations which could prove disastrous for any organization (public or private sector).
Since technology drives most of what we do today in our working and personal lives we need to ensure decisions are made thoughtfully and prudently. I personally believe that decisions worth making should be made as a team. The input of others make for better decisions and result in supporters, of the decision, from the beginning. With a team making a decision there are more voices and while that leads to more opinions to consider it also leads to a stronger decision. However, the team needs to be comprised of the right individuals and ground rules needs to be laid out at the beginning of the process. Assembling a team to help make a decision does not allow the executive to abdicate their responsibilities of providing leadership and guiding the group to a clear decisive choice.
Further, a team needs to realize their purpose and have a shared goal. I have seen groups come together who believe their purpose is to stop the decision from being made. They use their position on the committee as a means to prevent change and throw up roadblocks at every opportunity. This serves no purpose and therefore these individuals need to be removed quickly from the process. The right group is made up of individuals that realize a decision must be made, have the good of the organization in mind, will be helpful in supporting the decision, and have practical and thoughtful considerations as to why a particular decision should be made.
When making a decision the following roles need to be accounted for in some fashion.
- Executive Leadership: This individual is responsible for making the case regarding why a particular decision needs to be made. This is typically a problem or opportunity statement. "To grow ABC Corporation's market share by 15 percent we need to find ways to increase outreach."
- Legal: In today's regulatory and business environment questions about the legality of a decision may arise and it is best to understand these parameters immediately as opposed to making a decision and then trying to have it fit into a legal framework.
- Financial: Any decision is likely going to involve an investment of resources or may need an estimate of revenue to know which path to take. When evaluating options questions will arise about cost, resources on hand, and the like. It is disruptive to stop the process to find this information and therefore having the knowledge as part of the group is important.
- Human Resources: If your decision involves hiring more staff or contracting with a firm to supply staff you are going to need someone who understands the processes and internal practices. If an organization decides to hire it may require promoting someone else to supervise these new resources, it may require training and a host of other items will need to be considered.
- Technical: Someone on the committee needs to understand the state of technology in use at the organization. You may own several applications or systems that can do what is being requested if banded together. If a purchase is going to be made it will need to be folded into the existing applications and therefore your IT team is going to need to know about it.
- Procurement: Eventually a question will be asked related to completing the work in house or purchasing it externally. When this question arises it will be important to have someone knowledgeable with the procurement practices of the organization.
The above roles are not intended to be exhaustive rather they are intended to serve as the foundation for a committee. An organization will need to add more individuals to the group to make the right decision. You may need business managers, process owners, and customer representation on your committee as each team needs to be carefully built. If these roles are filled with the right people and the people have the right frame of mind a decision will be made that the entire organization can stand by.
Of course, there will always be times when a decision is made be a single person (or a very small group) out of urgency or necessity to the organization. This is bound to happen and at times is unavoidable. The goal is to have this be the exception and not the rule.
What other roles do you think need to be accounted for when making major decisions? If you think I missed a particular role or skill set please leave a comment so the entire community can benefit.