Describing the details of a technical project to an audience with varying understanding of the topics presented can pose a significant challenge. The presenters want to keep all listeners interested, but that can be difficult to do when some listeners want to hear the technical details and others would be bored and confused by them.
Ideally, the presenter will try to find some middle ground. It can be difficult, but it is usually possible to describe some of the technical functions of software in simpler terms, using less technical terminology than one usually would while discussing a project with peers. It is also advisable to restrict audiences to similar technical levels, but this is not always possible. Another tip that may be helpful are to pay attention to which audience members seem bored or confused, and to adjust your presenting style accordingly. When it simply would not be possible to omit certain technical terminology, the presenter can use said terminology, and then provide a simple description of the terms without singling out any specific person. In other words, the presenter could state that a LinkedList is used to temporarily store data, and then make a short explanation to the entire audience about how a LinkedList is a data structure to which elements can be quickly added or removed. This method will help everyone understand what the presenter is saying, as well as keep the presentation interesting and relevant to the technical people in the audience(Duran et al., 1999).
There will be times that the nature of the project necessitates a large amount of technical terminology be used. In such a presentation, it could be helpful to advise the people who will make up the audience in advance to study or at least become somewhat familiar with certain material as to better understand the presentation. The likelihood of audience members actually doing this advance studying depends largely on the reason for their being at the presentation. Many people who have a vested interest in what is being presented would hopefully take the time to learn how the project works. On the other hand, those who are required to be at the presentation but do not have any interest in the inner workings of the project are probably less apt to learn about it on their own(Tiger et al., 2012). Keep in mind that these two examples of audience members are not mutually exclusive, a person could have a vested interest in the project and still not want to study it in advance. The only thing to do in a situation like this, is as I said earlier. Use the terminology when necessary, and provide a brief explanation so the entire audience will have an understanding of what is being said.
Tiger, D., & Hess, G. (2012). Agile Approach to Design Leads to Client and Job Satisfaction. T+D, 66(4), 108-109. http://libaccess.sjlibrary.org/login?url=http://search.ebscohost.com/login.aspx?direct=true&db=aph&AN=73887969&site=ehost-live
Durán Valenzuela, J. L., & Sánchez Villacorta, F. (1999). The relationships between the companies and their suppliers. Journal Of Business Ethics, 22(3), 273-280. http://libaccess.sjlibrary.org/login?url=http://search.ebscohost.com/login.aspx?direct=true&db=ofm&AN=507668122&site=ehost-live
First Picture Link:
Second Picture Link: