Turn your lessons into experiences.
Lessons students want to explore, participate in and remember.
Edugine helps tutors create and run live learning experiences where students actively participate, interact and collaborate — while tutors see what students are doing and guide the lesson in real time.
Lesson
C1ENWhen Departments Collide: R&D, Production & Management
Navigate the clash between R&D, production, and management — three departments that speak different languages about the same problems. Master cross-functional vocabulary, learn to translate between technical and business perspectives, and survive a resource allocation meeting where everyone wants more. A practical C1 English lesson for scientists on cross-department communication, stakeholder language, and managing competing priorities. Ideal for chemistry professionals, R&D teams, and corporate
How this lesson works
Students participate
Students interact directly with the lesson — responding, speaking, solving tasks, making decisions and joining activities.
You see what is happening
See student responses, answers, mistakes and activity in real time where supported.
You guide the experience
Guide the lesson, manage activities and timing, and respond to what students are doing where supported.
Everyone participates
Students actively contribute and interact instead of simply consuming lesson content.
Three Emails, One Problem, Zero Understanding. Content Block
Content Block
On Monday morning, a product quality issue triggered three emails from three departments — about the same batch, on the same day, to the same operations director. EMAIL 1 — From: R&D Manager "We have identified an anomalous exothermic behaviour in Batch 7741 during the second-stage condensation reaction. FTIR analysis indicates incomplete crosslinking, possibly due to a deviation in the stoichiometric ratio of the curing agent. We recommend halting production until we can conduct a full kinetic study. Estimated time: 2-3 weeks." EMAIL 2 — From: Production Supervisor "Line 4 is down. Batch 7741 came out sticky and won't cure properly. We've been running the same settings as always. R&D changed something in the formula three weeks ago and didn't tell us. We need an answer TODAY — we have 12 tonnes of raw material sitting on the floor and a crew waiting." EMAIL 3 — From: Commercial Director "Client called. Their delivery is late. I don't understand the technical details but I need to know two things: when can we ship, and who is paying for the delay? If we lose this client, that's €800K annually. I need answers by end of day, not a research project." The operations director read all three emails, understood about 40% of the combined information, and called an emergency meeting for 2 PM. Nobody in that meeting spoke the same language.
Discussion questions
- Which email communicated the problem most effectively? Why?
- What information is missing from each email that the other departments need?
- Have you ever experienced a situation where different departments described the same problem in completely different ways?
Translate Between Departments. Word Cards
Word Cards
- Anomalous exothermic behaviour|You're from R&D. A production supervisor just said "the batch is hot and sticky." Say the same thing in R&D language.
- Line is down|You're from Production. R&D just said "we recommend halting the process pending further investigation." Say what this actually means for your team.
- Cost implication|You're from Management. R&D wants three weeks for a kinetic study. How do you ask about the financial impact without sounding like you don't care about science?
- Deviation|R&D uses this word to mean a scientific result outside expected range. Production uses it to mean someone didn't follow the SOP. Explain why this causes confusion.
- Timeline|Production says "we need this fixed today." R&D says "give us 2-3 weeks." Write one sentence that bridges the gap.
- Root cause|Management asks "what went wrong?" — R&D hears a scientific question, Production hears blame. Rephrase it so both departments hear the same thing.
- Stakeholder update|You must write one email that R&D, Production, AND Management can all understand. What three things must it include?
- Escalate|Production wants to escalate the problem to the CEO. R&D thinks escalating means they failed. How do you explain that escalation is not blame?
Who Says It This Way? Sorting
Sorting
R&D
Production
Management
One Batch Failure, Four Perspectives. Jigsaw Reading
Jigsaw Reading
The R&D Scientist
Three weeks ago, R&D completed a reformulation of the adhesive to reduce costs by replacing 10% of the main resin with a cheaper alternative. The lab tests showed identical performance across all parameters. The technology transfer document was sent to Production by email with a note saying "minor formulation update — no process changes required." R&D considered the change trivial and did not schedule a handover meeting. What they did not account for was that the cheaper resin had a slightly different particle size distribution, which affected mixing behaviour at production scale.
The Production Supervisor
Production received an email three weeks ago about a "minor update." The supervisor read it, saw "no process changes required," and filed it. When Batch 7741 started behaving differently, he assumed it was a raw material quality issue and adjusted the mixing speed on his own to compensate. He did not inform R&D because the email had said no changes were needed. When the batch failed, he felt blindsided — he had done exactly what the email told him to do: nothing different.
The Quality Manager
QC tested Batch 7741 using the standard test protocol. The results were borderline — within spec on paper but close to the lower limit. The quality manager flagged it as "pass with observation" and released the batch. She did not know about the reformulation. If she had known a formula change was involved, she would have applied tighter release criteria and flagged the borderline result as a hold for further investigation. Nobody told her.
The Commercial Director
The commercial director promised the client delivery by Thursday. When he heard about the batch failure on Monday, he was furious. He asked three questions: when, how much, and whose fault. R&D said they needed two weeks. Production said it wasn't their fault. QC said they had released it within spec. Nobody could give him a clear answer. He told the client there was a "minor logistics delay" and promised delivery by the following Monday — a promise he had no authority or evidence to make.
Comprehension questions
- Which department is most responsible for the failure? Or is nobody individually to blame?
- What would have prevented this situation — better communication, better processes, or better people?
- Which department's perspective surprised you or changed your opinion?
Say It So Everyone Understands. Word Choice
Word Choice
- I knowseeappreciate your urgency, but we need 48 hours before we can commit to a solution.
- Could you walktakeshow me through the production data so I can compare it with our lab results?
- From a commercialmoneysales perspective, what is the minimum we need to deliver to keep the client?
- I think we're talking about the same problem but using different languagewordsterminology — let me clarify.
- Before we sendescalatemove this to senior management, can we agree on what we actually know?
- I'd like to propose a temporarysmallquick fix for production while R&D works on the permanent solution.
- The takeawaylessonpoint is that no formula change should go to production without a handover meeting.
- Let me saytellsummarise what each department needs so we can find common ground.
- Can we set up a recurringregularnormal cross-department check-in to prevent this from happening again?
- From now on, every change — no matter how minorlittlesmall — must include a written handover.
The Resource Allocation Meeting. Mission Briefing
Mission Briefing
Scenario
After the Batch 7741 failure, the operations director has called a resource meeting. The company has a limited budget and must decide how to allocate resources for Q4. R&D wants funding for a new analytical instrument. Production wants to hire two additional operators and upgrade a reactor. Management wants to invest in a CRM system and sales training. The total budget is €300,000 — not enough for everything. The team must agree on priorities within 15 minutes.
R&D Manager
You need a new HPLC instrument (€120,000) to improve analytical capacity. Without it, your team cannot support both new product development and quality investigations simultaneously. The Batch 7741 failure would have been detected earlier with better analytical tools.
Must use: Your real concern is that R&D always loses the budget fight to Production and Sales. You feel undervalued and you are considering leaving. If R&D gets nothing again this quarter, you will bring this up. Do not reveal your frustration until you feel ignored.
Production Supervisor
You need two additional operators (€90,000 annually) and a reactor upgrade (€150,000). Your team is overworked, running double shifts, and making mistakes because of fatigue. The Batch 7741 issue was partly caused by an operator adjusting settings independently because there was no time to call R&D.
Must use: Your real concern is safety. You had a near miss last month that you haven't reported because you were afraid it would reflect badly on your team. If anyone questions your team's competence, you will reveal the near miss to show they are overworked, not careless.
Commercial Director
You want €80,000 for a new CRM system and €40,000 for sales training. Your sales team is losing deals because they cannot track client communications properly. The Batch 7741 client almost left because nobody had a record of what was promised to them.
Must use: Your real concern is that you already told two potential new clients that the company can deliver a product it has not finished developing yet. If R&D gets the HPLC instead of finishing the new product, you will have to break those promises. Do not reveal this unless someone asks about upcoming sales commitments.
Operations Director
You chair this meeting. You have €300,000 and must allocate it fairly. You want consensus, not a fight.
Must use: You already know the CEO is planning a 15% budget cut next quarter. Whatever is not approved now will not happen for at least a year. You do not want to reveal the upcoming cut because it will cause panic. Use it only if the meeting is stuck and you need to force a decision.
It's Getting Personal. Drama Event
Drama Event
Scenario
The resource allocation meeting is getting heated. Three departments are fighting for a limited budget. Then external factors start making everything more complicated...
- 🧠
Revelation
The HR director sends a message to the operations director during the meeting: two R&D analysts have handed in their resignation this morning. They cited "lack of investment in the department" as their reason. The R&D manager does not know yet.
- ⏱
Pressure
The Brenntag client from the Batch 7741 incident has just emailed: they want a face-to-face meeting this Friday to discuss "the future of the partnership." The commercial director needs something positive to tell them.
- 🔄
Twist
The production supervisor receives a text from a shift leader: the reactor that was scheduled for upgrade has just developed a leak. It can be patched temporarily, but a full repair costs €30,000 that was not in any budget. Where does the money come from?
- 🧨
Crisis
The CEO's assistant calls the operations director: the CEO has seen the Batch 7741 report and wants to know why three departments are blaming each other instead of fixing the problem. He wants a unified action plan on his desk by tomorrow morning.
- 🚧
Constraint
Finance informs the operations director that €50,000 of the €300,000 budget has been frozen due to an unpaid supplier invoice dispute. The actual available budget is now €250,000.
- 🧭
Opportunity
A government innovation grant application is open — the company could apply for €150,000 in co-funding for new R&D equipment. But the application deadline is in 10 days and requires a detailed business case that nobody has started writing. Who has time to do it?
- 🎯
Decision
The meeting has been going for 30 minutes. The operations director says: "We leave this room with a decision or I make it myself and nobody will be happy. Last chance — what's the priority?"
- 🔄
Twist
An anonymous employee satisfaction survey has just been published on the company intranet. R&D scored the lowest satisfaction in the company at 34%. The top complaint: "Management does not understand or value what we do." The R&D manager has not seen it yet, but everyone else in the room has.
- 🎲
settings
- 🎲
settings
- 🎲
settings
- 🎲
settings
Departments, Politics, and Priorities. Debate Roulette
Debate Roulette
- R&D should always get priority in budget allocation because without innovation, the company has no future.
- The real problem in most companies is not money — it is that departments do not talk to each other.
- Production workers deserve more respect than they get — they are the ones who actually make the product.
- Every formula or process change, no matter how small, should require sign-off from all affected departments.
- Sales teams should never make promises to clients without written confirmation from R&D and production.
- Cross-department meetings are usually a waste of time because each department only cares about its own problems.
- Companies should rotate employees between departments so everyone understands what the others actually do.
- The person who chairs a resource meeting has the most power in the company, even if their title is not the highest.
Why Edugine?
Turn your lessons into experiences.
Edugine helps tutors create and run live learning experiences where students actively participate, interact and collaborate — while tutors see what students are doing and guide the lesson in real time.