You are here

Making a decision

Listen to a meeting in which colleagues make a decision to practise and improve your listening skills.

Do the preparation task first. Then listen to the audio and do the exercises.



Language level

Intermediate: B1


When I was working my boss just give the order and I change everything with the aim to get a better performance and hand in the best results.

Where I work the decisions made according to the type of decision, sometimes the manager follow structured approach and agile approach in other times.

Our team leader discusses the best choice with all of us and after considering the suggestion from us, the team leader makes the best decision. So the main decision is made from Team leader, but we are free to add any ideas and to ask detail information about; how long the project will last, which is our role in the project and how much they are going to pay us for our job that has to be done.

Sorry, I thought the discussion was about management project approaches. About decisions , we used to discuss them first, share opinions about every suggestion, and if we failed to all agree on something, we ended up taking a vote.

When I was at university, we followed agile methodology when developing projects, because it was more effective and flexible. In software engineering, the customer doesn't often have clear ideas about what he needs, he might know the main features and objectives of the system he'd like, but his requirements may change throughout the project execution, that's why adopting an agile approach is the best decision in such a case.

I usually given my opinion and let my team Flexibility to make a decision, but almost my opinion being good for them.

It obviously depends on the situation. Of course, every company wants to have a plan before the project starts. You have to know what human and material resources you need to get the job done. And, clearly, you should know how long the project will last.
But, as usual, unpredictable situations happens. So, you need the plan, the good one, but no matter how good it is if you can't adapt it to the appeared conditions

Hello Kirk,
Now i don't work with another people. When I worked in a English Learning Course, we would make a meeting to take a decision. Our vital aims is to be induce new students to enroll to our course. In our meeting, generally the boss would explain our mission to reach to the goals. And then we could say something about the project and our tasks. Sometimes we could interrupt and add our thoughts. But mostly decision are made by boss and her close friends.

I work part-time at a drug store, so our owner usually decide a lot of things.
But in my college, we can decide almost things by ourselves, so we exchange our opinions, and make a majority decision.
I think to decide by majority is very easy, but to be influenced by majority is a little bad, so having own opinion is very important.

In our university it completely depends on the objective of decision which we should make. For example, if we want to make schedule for next semester, the dean of faculty and his/her assistant console with professors and assistant professors and then make schedule. Making schedule of mid term tests and so on are the same as scheduling for semesters. But it differs for each professor. Everyone has three kinds of programs which are named daily, monthly, and semestrial. Professors make these schedules based on the subject of his/her course and the statutes of university.
If I compare them to process which is discussed above, they are probably very different. For example, course policy should be made at the beginning of each semester. Therefore, I think we usually make structured decisions which is stated by David, and we slightly use agile planing.