Introduction
As the leader of a team, you have to consider how to organise your team, how the team should address problem solving and decision making, and you need to learn how to effectively run a team meeting.
Objective
The student will learn how to organize a team, lead a team through problem solving and decision making, and to run an effective meeting.
Study Time: 4.0 hours
Overview
There are a number of different ways to organise an engineering team in an industrial setting. These include functional based organisation, project based organisation, and the often confusing matrix-based organisation.
One of the challenges a team must face is evaluating problems, coming up with solution plans and making decisions relative to those plans. These are best approached in an organised fashion, and thus having a framework for approaching them is advisable and will be discussed in this section.
Team members usually share their ideas in a meeting setting. Meetings can consume huge amounts of time which could be spent more productively working on the project. Therefore, it is important to know how to effectively and efficiently conduct a meeting.
Project Management in a Functional Organisation
A functional organization is one in which team members are placed into teams or groups wherein all the members of a particular group perform the same function within the overall organization. Graphically it looks like this:
In an engineering organization, one functional group might be comprised of all the designers, while a second might include all of the stress analysts, and another all of the thermos and heat transfer specialists. Manufacturing engineers would be a separate group, as would test engineers, and all such groups that perform a specialized function. When a Project Manager is assigned the task of leading a particular project, they have to approach each Functional Manager to have a technical specialist assigned to work on their project, and they are at the mercy of that Functional Manager as to who they get, for how long, and have no say in whether that person may be reassigned and replaced on their project effort.
Advantages:
- Maximum flexibility in the use of staff – ability to reassign staff to the appropriate projects virtually immediately
- Individual experts can be utilized by many different projects
- People can be switched back and forth between projects easily
- Each project has access to all the expertise available in a functional area
- The functional unit serves as a base of technological continuity, procedural awareness, and policy continuity
- The functional unit contains the path for professional advancement for individuals whose expertise is in that functional area
Disadvantages:
- The client is not the focus of activity – the functional unit determines its own priorities and it takes precedence over any particular project.
- The functional unit tends to be oriented toward the activities particular to its function
- Since none of the technical specialists working on the project truly report to the project manager, lines of responsibility are blurred and lack of coordination may well occur
- Response to client needs may be slow (same reasons just given)
- Project needs that fall within a functional area usually get good attention, but needs which fall outside the domain of any functional unit may get short shrift.
- The motivation of the people assigned to a project tends to be weak
- This approach does not promote a holistic approach to the project
Project Management in a Project Based Organisation
A project based organization is one in which team members are placed into teams or groups which are assigned to work on a particular project. They report directly to the manager for that project and are disconnected from other specialists in their expertise. Graphically it looks like this:
Frequently these project teams are referred to as Integrated Project Teams, of IPTs, because the experts from the individual fields are all integrated into one team whose sole task to is work on a particular project.
Advantages:
- The project manager has full line authority over the project and all members of the team working on the project are responsible to him
- Permission or authorization by external functional leaders is not required
- Lines of communication between all team members are very short
- Several similar successive projects can benefit from a close-nit team of experts – this can be perceived as a major strength by customers – e.g. the Lockheed Skunkworks
- The team can develop a sense of pride, ability, accomplishment and identity
- Team members often develop a strong identity and commitment
- Centralized authority leads to ability to make decisions quickly and react rapidly to problems
- Structurally simple and flexible
- Supports a holistic approach to the project
Disadvantages:
- When a company has multiple similar projects, there can be considerable duplication of effort
- A project manager may try to ensure availability of technical knowledge, even when it is not yet needed, leading to over staffing
- Access to the wide range of technical experts who existed in the functional unit does not occur as readily – leading to the possibility that technical expertise that could help a project may be bypassed
- There tends to be an inconsistency in the way policies and procedures are carried out,
- The project tends to take on a life of its own – team members form a strong attachment to the project and each other – which can lead to an us-versus-them sentiment
- Friendly rivalry between teams can deteriorate to bitter competition
- Uncertainty about life-after-the-project can develop for team members – where will they end up when the project ends?
Project Management in a Matrixed Organisation
A matrixed organization is one in which individual employees are simultaneously assigned to both a functional manager, to whom they report on technical issues, and also a project manager, to whom they report on project-related issues. Graphically, this looks like this:
Advantages:
- The project manager has full authority over the project (similar to the project-based organization)
- The project has full access to the expertise and resources of the functional unit
- Project team members maintain a connection to their functional home
- Reduces anxiety about what will happen after the project ends
- Maintains promotional opportunities within area of functional expertise
- Response to client needs remains rapid (as with project-based)
- Allows for a better company-wide balance of resources
- Holistic view of the project
Disadvantages:
- The balance of power between the functional unit and the project is delicate
- It can become unclear to the employee just who they really report to
- Tug-of-war can occur between the functional leader and the project leader, with the employee caught in the middle
- Violates the principle of unity-of-command
Problem Solving and Decision Making as a Team
A problem can be considered to simply represent a situation where what is actually happening differs from what is desired. Here are the steps we might reasonably follow, if our team faces a problem:
- Recognize the problem
- Define the problem
- Collect information / gather data
- Analyse current processes from which the problem results
- Identify possible causes
- Generate alternative processes to eliminate the causes
- Select the best course of action
- Implement change steps
- Assess the results
- Learn from the results
- Make the changes permanent
During such a problem solving activity, using a process as just described, decisions will have to be made. How does a team make decisions? There are a number of modes which may be applied, such as:
- Leader rules – Team supplies info to a manager who decides
- Majority rules – Team votes
- Consensus – Team agrees
The level of enthusiasm and commitment that the team has to implementing the solution which has been decided upon, is generally related to the amount of input the team had into the decision, as shown in the following figure.
Graph: Level of enthusiasm and commitment that a team has to implementing the solution
which has been decided upon relating to the amount of input the team had in the decision.
Therefore, the approach that is used in executing the decision making process is important. If we wish to attain the greatest commitment to the solution, the consensus approach is probably the best one. So, how does one go about building a consensus solution? Here are some tools which may be useful:
Action–Consequence Analysis (a.k.a. Fish Bone Analysis)
- Place description of the solution strategy or action in the box
- Label each “rib” with a category of consequences
- Create smaller “bones” for the consequences of each category
- Use the “fish bone” figures to compare and assess different solution approaches
Nominal Group Technique (NGT)
- A structured process giving everyone on the team an equal voice in the decision
- Each team member makes a list of ideas, without discussion
- When finished, go around the room, each member stating one of their ideas
- All ideas are recorded on the board
- Rotate until all ideas are on the board….clarify any that need it
- All members get a number of votes equal to 1/3 of the ideas
- Go down the list and members vote
- Eliminate the bottom half of the list (lowest votes)
- Return to step 6 and repeat
- Continue process until final selection is made
Running a Meeting
Meetings are vitally important for management and communication within a project team. When conducted correctly, meetings can save time, improve communication, increase motivation, increase productivity, solve problems and generate new ideas and initiatives. Effective meetings can achieve buy-in from all participants. Meetings are more effective at diffusing potential conflict than emails or written memos. Non-verbal communication such as facial expression or body language is lost in written communications. The opportunity for feedback, questioning, brainstorming, problem solving, and interactive thought is not available through written communications either. That's why meetings are a necessary means of interacting as a team.
Face-to-face meetings are the most effective means of conveying feelings and meanings. These are therefore preferable to phone or video-conferencing meetings, when dealing with a serious matter. However, in today’s global business-world, team members may be located at other facilities, and even in other time zones, so use of modern communication technology may be necessary. Fortunately, recent advances in video-conferencing have made it possible to conduct meetings over the internet nearly as effectively as in person.
Here are some guidelines for running an effective meeting:
- Plan the meeting and create an agenda.
- First off, determine if a meeting is really necessary. Meetings take people away from their assigned tasks. Therefore a meeting is appropriate only if there is a legitimate reason why all the participants should be gathered together at the expense of their individual assignments.
- Create an agenda containing all the items that need to be discussed and resolved. Assign a reasonable amount of time that each topic should take, and endeavour to stick to this time rather than letting the meeting stretch on and on.
- Circulate the meeting agenda well before the meeting.
- This allows participants to be prepared and know what to expect.
- It also allows them to schedule their efforts around a set time for the meeting.
- Run the meeting effectively.
- Call the meeting to order on time. Delaying because someone is late only creates the impression that there is no need to arrive at future meetings on time.
- If someone is late, do not waste time repeating things so as to catch them up. It is their responsibility to catch up.
- Pass out copies of the agenda. Also pass out either the minutes or the action item list from the prior meeting as a reference of what has gone on before.
- Make sure everyone knows everyone else in attendance.
- Stick to the assigned time schedule.
- Assign someone to take minutes of the meeting.
- This is important as it creates a record of what was discussed and decided.
- It can be circulated to those unable to attend so that they are aware of what went on.
- It provides something that can resolved disagreement relative to what occurred when at a later date people remember things differently.
- Begin by quickly summarizing the purposes of the meeting.
- Do not allow participants to steer the discussion off topic
- Keep control - You need to manage the meeting, do not let the meeting manage you.
- Never allow participants to become insulting, to talk over others, to conduct conversations extraneous to the meeting, or to belittle other participants. If someone is consistently behaving in such a manner, ask them to leave and deal with them after the meeting.
- Agree on outcomes, actions and responsibilities.
- Create an action item list for every action that was agreed to during the meeting.
- Make sure someone is assigned to follow up on each action item, with an expected completion date.
- There should be a running action item list which includes all the open action items from all meetings that have been conducted. This list should contain the responsible individual and completion date and the list should be circulated to all team members.
- End your meeting on a positive note that inspires action. Summarize what each member has to do in order to accomplish the tasks discussed and put on the action item list.
- Ensure that the minutes and action item list are produced in clear and concise written form and circulated to all participants, whether they were in the particular meeting or not.
- Follow up on all agreed action items and ensure they are ready to be reported on at the next meeting
Each student should submit Coursework 1 as described in the coursework descriptor document, using the teaching materials, additional research performed on the topics, and discussion with other students conducted via the VLE discussion forum.
Summary
Teams are most effective when they function with a well-understood organizational structure, with a well-defined approach to problem solving and decision making, and when they communicate and assign responsibilities effectively. The topics discussed in this section should assist the team in achieving these goals.
References & Bibliography
Dym, C. & Little, P. (2009). Engineering Design, 3rd edition. Hoboken, NJ, USA: Wiley.
Heizer, J., Munson, C. & Render, B. (2017). Operations Management. New York: Pearson.
Horenstein, M. (2002). Design Concepts for Engineers, 4th Edition. \Upper Saddle River, NJ, USA: Prentice.
McSween, D. (2015). How to Conduct a Board Meeting Properly. Accessed 14 September 2015, Online <http://smallbusiness.chron.com/conduct-board-meeting-properly-75586.html>
Meredith, J. & Mantel, S. (2012). Project Management, 8th edition. Hoboken, NJ, USA: Wiley.