Giving proposals/suggestions
Enhancing the ability to present proposals & suggestions clearly and persuasively in a software engineering work environment.

Part 1
Warm-up
Answer the questions
What did we discuss in the last lesson?
Have you ever had to present/give a proposal/suggestion at work?
What challenges do you face when presenting/giving a proposal/suggestion?
Part 2
Vocabulary
Read the word, its’ meaning, and the examples
Then make up your own sentences using the word.
Student can skip the words they already know.
groundbreaking
/ˈɡraʊndˌbreɪ.kɪŋ/

If something is groundbreaking, it is very new and a big change from other things of its type
The scientist made a groundbreaking discovery in the field of genetics.
The company launched a groundbreaking product.
intuitive
/ɪnˈtuː.ɪ.tɪv/

easy to use or learn without any special knowledge
The software's intuitive design makes it easy to use.
An intuitive interface improves user experience.
perspective
/pəˈspek.tɪv/
a particular way of considering something
His perspective on the issue is quite different from mine.
She provided valuable perspective during the discussion.
embrace
/ɪmˈbreɪs/

to accept or support something willingly or enthusiastically.
The company is embracing new technologies.
She embraced the opportunity to learn a new language.
alternative
/ɑːlˈtɜr.nə.tɪv/

Something that can be chosen instead of something else
We need to find an alternative to our current system. (n)
They proposed an alternative solution to the problem.(adj)
timeboxing
/taɪmˌbɑksɪŋ/
Setting a fixed amount of time for an activity to enhance productivity
We will use timeboxing to keep our meetings short.
Timeboxing helps in managing time more effectively.
Make up your own sentences using the words.
Part 3
Reading comprehension and discussion
Read the article and answer questions.
Teacher helps student correct their pronunciation.
The importance of proposals and suggestions in Software Engineering
In the dynamic field of software engineering, proposals and suggestions are vital tools for driving innovation, improving processes, and addressing challenges. Every member of the development team, including developers, DevOps engineers, product designers, IT business analysts, quality control (QC) specialists, product managers and so on… can contribute valuable ideas that help shape the future of a project or product.
Why proposals and suggestions are important:
- Innovation: Proposals introduce new ideas and approaches that can lead to groundbreaking features or technologies.
- Process improvement: Suggestions often highlight inefficiencies or problems in current workflows, leading to more streamlined and effective processes.
- Problem solving: Proposals provide structured solutions to existing challenges, ensuring that issues are addressed systematically and thoroughly.
- Team engagement: When everyone is encouraged to share their ideas, it fosters a collaborative and inclusive work environment.
Why everyone should give proposals:
- Different viewpoints: Each role brings a unique perspective, which can lead to more comprehensive and effective solutions.
- Empowerment: Allowing all team members to contribute ideas, it makes them feel important increasing job satisfaction and motivation.
- Continuous improvement: Regular suggestions from all team members help keep processes and products getting better over time.
By embracing proposals and suggestions from all team members, software engineering teams can achieve greater innovation, efficiency, and overall success.
Check your understanding
Why are proposals and suggestions considered vital tools in software engineering?
How does encouraging everyone to give proposals contribute to team engagement?
Discussion
Can you give some examples of proposals and suggestions that team members can make?
Sample answer
- They drive innovation, improve processes, and address challenges.
- It fosters a collaborative and inclusive work environment.
Examples of proposals from different roles:
Developer: Proposing to refactor legacy code to improve maintainability and performance.
DevOps Engineer: Suggesting the implementation of a continuous deployment pipeline to automate and streamline deployments.
Product Designer: Proposing a redesign of the user interface to enhance accessibility and user experience.
IT Business Analyst: Suggesting the integration of customer feedback into the development cycle to align features with user needs.
QC Specialist: Proposing the adoption of automated testing to improve test coverage and efficiency.Product Manager: Suggesting the prioritization of feature development based on market research to ensure the product remains relevant.
Discussion
Is it more important to focus on new ideas or fixing current processes? Explain.
Ideas:
- New ideas: innovation & growth, meeting market demands, enhanced creativity
- Fixing current processes: efficiency & productivity, quality & reliability, customer satisfastion
Should proposals be submitted formally or informally? What are the benefits and drawbacks of each?
Ideas:
- Formal: clear & structured, provides documentation, shows professionalism
- Informal: Quick & easy, encourages participation, flexible.
Is it better to have a few detailed proposals or many quick ideas? Why?
Ideas:
- Detailed: in-depth analysis, higher quality, easier to implement
- Quick: encourages creativity, more options, faster innovation
What are the dangers of accepting too many proposals? How can these be avoided?
Ideas:
- Overwhelm, loss of focus, poor quality, hard decisions, high costs
- Avoid: set rules, prioritize, work together,…
Is it important to have a person or group in charge of reviewing proposals? Why?
Ideas:
Consistency, expertise, efficiency, quality control, prioritization
Should customer feedback be prioritized over team suggestions? Why?
Ideas:
- Customer: direct insight, market relevance, customer satisfaction, revenue impact
- Team: technical feasibility, innovation, efficiency, ownership
Are there types of proposals that should be avoided? If yes, which ones and why?
Ideas:
Unrealistic, redundant, low-impact, unclear, high-risk
Part 4
Useful phrases
Teacher guides the student the useful phrases.
Useful phrases for proposals and suggestions in software engineering
Formal suggestions/proposals
When you are in a meeting with important clients or key members of your company, it is crucial to use formal language. Here are some formal expressions suited for making proposals in software engineering:
- I propose that we…
- Example: I propose that we migrate our application to a microservices architecture to improve scalability.
- I suggest that we…
- Example: I suggest that we implement a continuous integration pipeline to streamline our development process.
- I advise we/you…
- Example: I advise we conduct a thorough security audit to identify potential vulnerabilities.
- I would recommend we…
- Example: I would recommend we refactor the legacy code to enhance maintainability and performance.
- I put forward that we…
- Example: I put forward that we adopt automated testing to improve our test coverage and reduce manual effort.
Less formal suggestions
In less formal meetings with team members, suppliers, or customers with whom you have a good relationship, using less formal language can be more appropriate. Here are some expressions for making less formal suggestions in software engineering:
- I think we should…
- Example: I think we should look into using Docker for containerization to simplify our deployment process.
- Why don’t we…?
- Example: Why don’t we integrate customer feedback more regularly to ensure our features align with user needs?
- How about…?
- Example: How about we set up a sprint review meeting to track our progress more effectively?
- What about…?
- Example: What about using a new project management tool to improve our workflow?
- We could try…
- Example: We could try implementing pair programming to enhance code quality and team collaboration.
- Let’s have a go at…
- Example: Let’s have a go at using an A/B testing framework to optimize user experience.
Using these phrases appropriately can help you communicate your ideas effectively, regardless of the formality of the meeting.
Students will practice making their own suggestions and proposals using the provided phrases
Exercise 1: Formal suggestions/proposals
Instructions: Use the following formal phrases to make a suggestion or proposal based on the given scenarios. Write one sentence for each scenario.
Student can choose only 2 scenarios to make the example.
- I propose that we…
- I suggest that we…
- I advise we/you…
- I would recommend we…
- I put forward that we…
Scenarios:
Scenario: The current project is experiencing frequent delays due to manual testing processes.
Scenario: The product’s user interface is receiving negative feedback for being non-intuitive.
Scenario: The company is considering expanding its product to a new market.
Scenario: There is a need to improve team collaboration and communication.
Sample answer
- I propose that we implement automated testing to reduce delays and improve efficiency.
- I advise we conduct a user experience study to understand and address the issues with our interface.
- I would recommend we perform a market analysis to ensure our product meets the new market’s needs.
- I put forward that we adopt new collaboration tools and regular team-building activities.
Exercise 2: Less formal suggestions
Instructions: Use the following less formal phrases to make a suggestion based on the given scenarios. Write one sentence for each scenario.
Student can choose only 2 scenarios to make the example.
- I think we should…
- Why don’t we…?
- How about…?
- What about…?
- We could try…
- Let’s have a go at…
Scenarios:
Scenario: The development team finds it challenging to track progress with the current project management tool.
Scenario: There is a need to improve code quality and reduce bugs.
Scenario: The sprint planning meetings are taking too long and not being productive.
Scenario: The team wants to boost innovation and creativity.
Sample answer
- I think we should look into using a different project management tool that better suits our needs.
- Why don’t we implement code reviews before merging any changes?
- What about setting stricter time limits for each agenda item to keep the meeting focused?
- We could try hosting regular brainstorming sessions to generate new ideas.
Part 5
Debate
Topic: Should suggestions from senior members be more important than those from juniors? Why?
In a debate on this topic, you need to talk about whether it’s important to learn some of the local language before going on a vacation. Say if you agree or disagree, give reasons, and use simple examples.
Preparation (3 minutes)
Student has 2-3 mins to think about their ideas.
Suggesting points:
- Senior: More experience, knowledge of past projects, have vision, better in risk management
- Junior: new ideas, up-to-date with trends, team dynamics,…
Debate (8 minutes)
Student has 2-4 mins to present their ideas.
Teacher helps student to expand their ideas, think critically & more views about this topic (by asking more questions about this topic).
Sample answer
In my opinion, it's a great idea to learn a few words and phrases in the local language before you go on vacation. When you know a little bit of the language, you can communicate better with local people. This can be very helpful in restaurants, shops, and when asking for directions. It also shows that you have respect for the culture of the place you are visiting. This can make local people friendlier and more welcoming, and it can make your trip more enjoyable and memorable.
However, some people think learning the local language is not necessary. They argue that many people around the world speak English, especially in places where tourists go a lot. They also point out that there are apps for your phone that can translate languages instantly. These people believe that it's better to use your time to plan other aspects of your trip, like where to visit and what to see, instead of spending time learning a new language. They think that with English and technology, you can manage well enough without knowing the local language.
Review
Let’s review the lesson with teacher
New words in this lesson
The importance of proposals and suggestions in Software Engineering
Useful phrases for proposals and suggestions
See you next lesson
Homework
Do homework
Write a sentence for each vocabulary today.
