During the course of my tenure in the audio visual industry, I have interviewed a number of project managers and worked for a number of companies who claimed they “managed the entire project lifecycle from concept to completion.” In all honesty, I too have claimed to be a master of this skill. The problem with this statement is that in most cases, the only individual(s) truly involved in a project throughout its entire lifecycle is the client. Key players will join and leave the team along the way, but only the client is there from beginning through the end and beyond.
This is the first in a series of articles that will highlight what I have seen as important steps in successful AV projects. This is not intended to be an end-all, be-all project process. It will not have the detail to be such a document. It will point to several stops along the journey where a project may get off track, resulting in potential issues such as:
In all likelihood, there is no AV Sales Engineer or Design Consultant in the room when an organization identifies the need to improve or add technology. That decision is made within the four walls of the organization by an individual, committee or team. However, it is possible that the decision to review the current technology was based on a presentation by a manufacturer or integrator. Are either of these moments really the development of a concept, or just the identification of the existence of a want or need?
Where the process goes from here can make all the difference in the success of a project. Taking the identified want or need and developing it into a concept can be accomplished in a number of ways.
The right choice will depend on the organization. It is important to note that the development of a sound AV concept requires the active participation of users, leaders, and experts. Only together can a concept be developed that will yield a successful result. Together the team can review and evaluate the value and merits of various concepts.
The Concept should be built around form rather than function. The concept should answer the question “what are we going to use this space to do?” It doesn’t need to define the equipment that will be used. Difficulties often arise when AV system users have a preconceived idea of what technology they want. Those wants can be built around experience with prior systems, technology they have seen at demonstrations or on TV, and what they have heard from others. These wants often detract from the overall need to define what business or tasks the technology will need to support. It is the responsibility of the expert, whether an internal employee or contracted professional, to mate client wants with client needs. Only when the ideal balance of both form and function has been achieved, can you have a clearly defined concept.
Continued in the next issue of IMS Connections: How to develop your concept into a design.