// Curriculum data for the English trainer. // 8 days of workplace-English content, intermediate level. // The app rotates through these by day index: contentIndex = dayKey % CURRICULUM.length window.CURRICULUM = [ { topic: "Daily standup & status updates", emoji: "🧭", words: [ { en: "standup", ru: "ежедневная короткая встреча (стендап)", def: "a short daily meeting to share progress", ex: "I'll give an update at the standup." }, { en: "blocker", ru: "препятствие, блокер", def: "something that stops your progress", ex: "My main blocker is waiting for the design." }, { en: "to be on track", ru: "идти по плану", def: "to be progressing as planned", ex: "We're on track to finish by Friday." }, { en: "to wrap up", ru: "завершать", def: "to finish something", ex: "Let's wrap up this task today." }, { en: "to follow up", ru: "напомнить/вернуться к вопросу", def: "to check back on something later", ex: "I'll follow up with the client tomorrow." }, { en: "to escalate", ru: "эскалировать (поднять вопрос выше)", def: "to send a problem to a manager", ex: "We may need to escalate this issue." } ], dialogue: [ { who: "A", name: "You", text: "Hi team, what did you work on yesterday?", tr: "Привет, команда, над чем вы работали вчера?" }, { who: "B", name: "Sara", text: "I finished the report and sent it to the client.", tr: "Я закончила отчёт и отправила клиенту." }, { who: "A", name: "You", text: "Great. Anything blocking you today?", tr: "Отлично. Сегодня что-нибудь блокирует?" }, { who: "B", name: "Sara", text: "Yes, I'm still waiting for the sales numbers.", tr: "Да, всё ещё жду цифры от отдела продаж." }, { who: "A", name: "You", text: "OK, I'll follow up with them after the standup.", tr: "Ок, я свяжусь с ними после стендапа." }, { who: "B", name: "Sara", text: "Thanks, that would help a lot.", tr: "Спасибо, это очень поможет." } ], reading: { title: "How to run a good standup", text: "A daily standup is a short meeting, usually fifteen minutes, where each team member answers three questions: what they did yesterday, what they will do today, and whether anything is blocking them. The goal is not to solve problems in the meeting — it is to share information quickly. If a topic needs a longer discussion, the team should take it offline and meet separately. A good standup starts on time, stays short, and ends with clear next steps.", questions: [ { q: "How long is a typical standup?", options: ["5 minutes", "15 minutes", "1 hour"], answer: 1, ex: "Текст говорит: usually fifteen minutes." }, { q: "What is the main goal of a standup?", options: ["To solve all problems", "To share information quickly", "To write a report"], answer: 1, ex: "Цель — быстро поделиться информацией." }, { q: "What should happen to longer discussions?", options: ["They stay in the standup", "They are taken offline", "They are cancelled"], answer: 1, ex: "Команда берёт их 'offline' — отдельной встречей." } ] }, listening: { title: "Status update", text: "Morning everyone. Yesterday I worked on the login page and fixed two bugs. Today I'm planning to start on the dashboard. The only blocker is that I need access to the test server, so I'll ask IT about that. I should be done by the end of the week.", questions: [ { q: "What did the speaker work on yesterday?", options: ["The dashboard", "The login page", "The test server"], answer: 1, ex: "'worked on the login page'." }, { q: "What will they start today?", options: ["The dashboard", "A bug fix", "A report"], answer: 0, ex: "'start on the dashboard'." }, { q: "What is the blocker?", options: ["No access to the test server", "Too many bugs", "No time"], answer: 0, ex: "Нужен доступ к тестовому серверу." } ] }, speaking: { prompt: "Imagine you're at the standup. Say: yesterday you finished a task, today you'll start a new one, and you have no blockers.", target: "Yesterday I finished my task. Today I'll start working on the new feature. I don't have any blockers." }, writing: { prompt: "Write a short message to your team in a chat: report what you did today and that you're on track. (2-3 sentences)", model: "Hi team! Today I finished the client report and sent it over. I'm on track with the rest of my tasks and should wrap up by Friday. Let me know if anything urgent comes up.", tips: "Используй present perfect (have finished) для недавних результатов и present continuous (am working) для текущих задач." } }, { topic: "Asking for help & clarification", emoji: "🤝", words: [ { en: "to clarify", ru: "уточнить, прояснить", def: "to make something clearer", ex: "Could you clarify what you mean?" }, { en: "to figure out", ru: "разобраться, выяснить", def: "to understand or solve something", ex: "I can't figure out this error." }, { en: "to walk someone through", ru: "провести по шагам, объяснить", def: "to explain step by step", ex: "Can you walk me through the process?" }, { en: "to get stuck", ru: "застрять", def: "to be unable to continue", ex: "I got stuck on step three." }, { en: "to make sense", ru: "иметь смысл, быть понятным", def: "to be logical and understandable", ex: "Does that make sense?" }, { en: "to double-check", ru: "перепроверить", def: "to check again to be sure", ex: "Let me double-check the numbers." } ], dialogue: [ { who: "A", name: "You", text: "Hey, do you have a minute? I'm a bit stuck.", tr: "Есть минутка? Я немного застрял." }, { who: "B", name: "Tom", text: "Sure, what's up?", tr: "Конечно, что случилось?" }, { who: "A", name: "You", text: "I can't figure out this error. Could you walk me through it?", tr: "Не могу разобраться с ошибкой. Можешь объяснить по шагам?" }, { who: "B", name: "Tom", text: "Of course. First, open the settings. Does that make sense so far?", tr: "Конечно. Сначала открой настройки. Пока понятно?" }, { who: "A", name: "You", text: "Yes, got it. And then?", tr: "Да, понятно. А потом?" }, { who: "B", name: "Tom", text: "Then just click 'reset'. Let me know if it still doesn't work.", tr: "Потом просто нажми 'reset'. Скажи, если не сработает." } ], reading: { title: "It's OK to ask questions", text: "Many people feel uncomfortable asking for help at work because they don't want to look inexperienced. But asking good questions is actually a sign of professionalism. A clear question shows that you care about doing the job right. Before you ask, try to solve the problem yourself for about fifteen minutes. When you do ask, be specific: explain what you tried, what you expected, and what actually happened. This saves everyone's time and helps your colleague help you faster.", questions: [ { q: "How does the author feel about asking questions?", options: ["It's unprofessional", "It's a sign of professionalism", "It wastes time"], answer: 1, ex: "Asking good questions is a sign of professionalism." }, { q: "What should you do before asking?", options: ["Nothing", "Try for about 15 minutes", "Ask immediately"], answer: 1, ex: "Try to solve it yourself ~15 min." }, { q: "What makes a good question?", options: ["Being vague", "Being specific about what you tried", "Apologizing a lot"], answer: 1, ex: "Будь конкретным: что пробовал, что ожидал, что вышло." } ] }, listening: { title: "Asking for clarification", text: "Sorry, could you repeat that? I didn't quite catch the last part. So, just to clarify — you want me to send the file by Friday, right? And should I copy the whole team on the email, or just you? I want to make sure I get this right.", questions: [ { q: "What does the speaker ask first?", options: ["To repeat", "To send a file", "To copy the team"], answer: 0, ex: "'could you repeat that?'." }, { q: "When is the deadline?", options: ["Monday", "Friday", "Today"], answer: 1, ex: "by Friday." }, { q: "What is the speaker unsure about?", options: ["Who to copy on the email", "The file name", "The meeting time"], answer: 0, ex: "Копировать всю команду или только собеседника." } ] }, speaking: { prompt: "You're stuck on a task. Politely ask a colleague for help and explain what you tried. (Use: 'do you have a minute', 'I got stuck', 'could you walk me through')", target: "Hi, do you have a minute? I got stuck on this task. I tried restarting it but it didn't help. Could you walk me through it?" }, writing: { prompt: "Write a message asking a colleague to clarify a task. Say you didn't fully understand the instructions and ask one specific question.", model: "Hi Tom, thanks for the task earlier. I read through the instructions, but I'm not sure I fully understood them. Could you clarify whether I should include the data from last month or just this month? I want to make sure I get it right. Thanks!", tips: "Вежливая просьба: 'Could you clarify...?' / 'I'm not sure I fully understood...'." } }, { topic: "Giving & receiving feedback", emoji: "💬", words: [ { en: "feedback", ru: "обратная связь", def: "opinion on how to improve something", ex: "Thanks for the feedback on my presentation." }, { en: "constructive", ru: "конструктивный", def: "useful and helpful (not negative)", ex: "That was constructive feedback." }, { en: "to improve", ru: "улучшать", def: "to make or become better", ex: "We can improve this process." }, { en: "to suggest", ru: "предлагать", def: "to put forward an idea", ex: "I'd suggest trying a different approach." }, { en: "to take into account", ru: "учитывать", def: "to consider something", ex: "I'll take your points into account." }, { en: "to appreciate", ru: "ценить, быть благодарным", def: "to be grateful for something", ex: "I really appreciate your help." } ], dialogue: [ { who: "A", name: "You", text: "Could I get some feedback on the proposal?", tr: "Можешь дать обратную связь по предложению?" }, { who: "B", name: "Emma", text: "Sure. Overall it's strong, but I have a couple of suggestions.", tr: "Конечно. В целом сильное, но пара предложений." }, { who: "A", name: "You", text: "Go ahead, I appreciate it.", tr: "Давай, буду благодарен." }, { who: "B", name: "Emma", text: "I'd suggest making the budget section clearer.", tr: "Предлагаю сделать раздел бюджета яснее." }, { who: "A", name: "You", text: "That makes sense. I'll take that into account.", tr: "Логично. Учту это." }, { who: "B", name: "Emma", text: "Great. The rest looks really good, nice work.", tr: "Отлично. Остальное выглядит хорошо, молодец." } ], reading: { title: "How to give constructive feedback", text: "Good feedback focuses on the work, not the person. Instead of saying 'you did this wrong', try describing what you saw and its effect: 'when the report was late, the client got nervous'. A useful method is to start with something positive, then describe what could be improved, and end with a specific suggestion. This keeps the conversation friendly and productive. Remember that feedback should help the other person grow, not make them feel bad.", questions: [ { q: "What should feedback focus on?", options: ["The person", "The work", "The past"], answer: 1, ex: "Focus on the work, not the person." }, { q: "What is a good structure for feedback?", options: ["Only negative points", "Positive → improvement → suggestion", "Only positive points"], answer: 1, ex: "Положительное → что улучшить → конкретное предложение." }, { q: "What is the goal of feedback?", options: ["To make people feel bad", "To help the person grow", "To show who is boss"], answer: 1, ex: "Помочь человеку расти." } ] }, listening: { title: "Receiving feedback", text: "Thanks for the feedback, I really appreciate it. You're right that the slides were a bit crowded. I'll make them simpler next time and leave more white space. I'll also practice the timing so I don't run over. Would you be able to look at the next draft before the meeting?", questions: [ { q: "What does the speaker agree to improve?", options: ["The slides", "The budget", "The report"], answer: 0, ex: "Сделать слайды проще." }, { q: "What else will they work on?", options: ["Timing", "Grammar", "Design colors"], answer: 0, ex: "Practice the timing." }, { q: "What does the speaker ask at the end?", options: ["To check the next draft", "To cancel the meeting", "To write the slides"], answer: 0, ex: "Посмотреть следующий черновик." } ] }, speaking: { prompt: "Give a colleague constructive feedback: start positive, name one thing to improve, suggest a fix. (Use: 'overall', 'I'd suggest', 'take into account')", target: "Overall, your presentation was really clear. I'd suggest slowing down a bit on the numbers. If you take that into account, it'll be even better next time." }, writing: { prompt: "Reply to feedback you received. Thank the person, agree with one point, and say what you'll change.", model: "Hi Emma, thanks so much for the feedback, I really appreciate it. You're right that the budget section was unclear — I'll add a simple table to make it easier to read. I'll send you the updated version by tomorrow. Thanks again for taking the time to look!", tips: "Структура: благодарность → согласие с пунктом → что изменишь → повторная благодарность." } }, { topic: "Small talk before meetings", emoji: "☕", words: [ { en: "small talk", ru: "светская беседа", def: "light casual conversation", ex: "We had some small talk before the meeting." }, { en: "to catch up", ru: "наверстать, поговорить о новостях", def: "to share news with someone", ex: "Let's catch up after the call." }, { en: "weekend", ru: "выходные", def: "Saturday and Sunday", ex: "Did you have a good weekend?" }, { en: "to look forward to", ru: "ждать с нетерпением", def: "to be excited about something future", ex: "I'm looking forward to the trip." }, { en: "to take it easy", ru: "отдыхать, не напрягаться", def: "to relax", ex: "I just took it easy this weekend." }, { en: "by the way", ru: "кстати, между прочим", def: "used to introduce a new topic", ex: "By the way, did you see the email?" } ], dialogue: [ { who: "A", name: "You", text: "Morning! How was your weekend?", tr: "Утро! Как прошли выходные?" }, { who: "B", name: "Leo", text: "Pretty good, just took it easy. You?", tr: "Нормально, просто отдыхал. У тебя?" }, { who: "A", name: "You", text: "Nice. I went hiking, the weather was great.", tr: "Здорово. Я ходил в поход, погода была супер." }, { who: "B", name: "Leo", text: "That sounds amazing. Anyway, shall we get started?", tr: "Звучит круто. Ну что, начнём?" }, { who: "A", name: "You", text: "Sure. By the way, did you see the agenda?", tr: "Давай. Кстати, видел повестку?" }, { who: "B", name: "Leo", text: "Yes, I've got it open. Let's dive in.", tr: "Да, открыта. Погнали." } ], reading: { title: "Why small talk matters at work", text: "Small talk — the short, casual chats before a meeting starts — may seem unimportant, but it actually builds trust between colleagues. When you ask about someone's weekend or comment on the weather, you show that you see them as a person, not just a coworker. Keep it light and positive: avoid heavy topics like politics or complaints. A good rule is to match the other person's energy. If they give short answers, don't push; if they seem happy to chat, enjoy the moment before getting down to business.", questions: [ { q: "What does small talk build?", options: ["Trust", "Stress", "Reports"], answer: 0, ex: "It builds trust between colleagues." }, { q: "What topics should you avoid?", options: ["Weather", "Heavy topics like politics", "Weekend plans"], answer: 1, ex: "Avoid heavy topics like politics or complaints." }, { q: "What's a good rule?", options: ["Always talk a lot", "Match the other person's energy", "Never make small talk"], answer: 1, ex: "Match the other person's energy." } ] }, listening: { title: "Before the call", text: "Hey, how's it going? Yeah, the weekend was nice — I finally tried that new coffee place downtown, it was really good. Anyway, I'm looking forward to today's session, I think we'll make some real progress. Oh, by the way, I might be five minutes late to the next meeting, I have another call right before. Just wanted to give you a heads-up.", questions: [ { q: "What did the speaker do on the weekend?", options: ["Went hiking", "Tried a new coffee place", "Stayed home"], answer: 1, ex: "Tried a new coffee place downtown." }, { q: "How does the speaker feel about today's session?", options: ["Bored", "Looking forward to it", "Worried"], answer: 1, ex: "'looking forward to today's session'." }, { q: "What heads-up does the speaker give?", options: ["They'll be late to the next meeting", "They'll skip the meeting", "They forgot the agenda"], answer: 0, ex: "Может опоздать на 5 минут." } ] }, speaking: { prompt: "Start a meeting with small talk: greet, ask about the weekend, react to their answer, then move to the agenda. (Use: 'how was your weekend', 'that sounds', 'shall we get started')", target: "Morning! How was your weekend? That sounds great. Anyway, shall we get started? I sent the agenda earlier." }, writing: { prompt: "Write a friendly chat message to a colleague before a meeting: ask how they are, share one short thing about your day, then mention the meeting.", model: "Hey Leo! How's your day going? I just had a really good coffee this morning, so I'm feeling ready. Are we still on for the 2pm meeting? I'll share my screen when we start. See you soon!", tips: "Дружелюбный тон, present simple/continuous, короткие предложения." } }, { topic: "Scheduling & meetings", emoji: "📅", words: [ { en: "to schedule", ru: "назначать (встречу)", def: "to set a time for an event", ex: "Let's schedule a call for Tuesday." }, { en: "to reschedule", ru: "переносить", def: "to change the time of an event", ex: "Can we reschedule to Thursday?" }, { en: "available", ru: "свободный, доступный", def: "free to meet", ex: "I'm available after 3pm." }, { en: "to conflict", ru: "пересекаться (о времени)", def: "to happen at the same time", ex: "That conflicts with my other meeting." }, { en: "to join", ru: "присоединиться", def: "to enter a meeting or call", ex: "I'll join in five minutes." }, { en: "agenda", ru: "повестка", def: "a list of topics for a meeting", ex: "Please check the agenda beforehand." } ], dialogue: [ { who: "A", name: "You", text: "Hi, could we schedule a quick call this week?", tr: "Привет, можем созвониться на этой неделе?" }, { who: "B", name: "Mia", text: "Sure. When works for you?", tr: "Конечно. Когда тебе удобно?" }, { who: "A", name: "You", text: "I'm available Wednesday after 3pm.", tr: "Я свободен в среду после 15:00." }, { who: "B", name: "Mia", text: "Hmm, that conflicts with my meeting. How about Thursday?", tr: "Хм, это пересекается с моей встречей. Как насчёт четверга?" }, { who: "A", name: "You", text: "Thursday works. I'll send the invite and the agenda.", tr: "Четверг подходит. Пришлю приглашение и повестку." }, { who: "B", name: "Mia", text: "Perfect, thanks. I'll join on time.", tr: "Отлично, спасибо. Буду вовремя." } ], reading: { title: "Making meetings shorter", text: "Many companies have too many meetings, and people feel they have no time for actual work. One simple fix is to make meetings shorter by default: instead of sixty minutes, try forty-five, and instead of thirty, try fifteen. Always share an agenda in advance so people come prepared. During the meeting, one person should take notes and write down action items — the specific tasks people agreed to do. End every meeting by repeating who does what and by when. This small habit saves hours every week.", questions: [ { q: "What is one fix for too many meetings?", options: ["Make them longer", "Make them shorter by default", "Cancel all meetings"], answer: 1, ex: "Make meetings shorter by default." }, { q: "What should be shared in advance?", options: ["An agenda", "Lunch", "The budget"], answer: 0, ex: "Always share an agenda in advance." }, { q: "How should every meeting end?", options: ["With a coffee break", "Repeating who does what and by when", "With small talk"], answer: 1, ex: "End by repeating who does what and by when." } ] }, listening: { title: "Rescheduling a meeting", text: "Hi Sam, I'm really sorry, but I need to reschedule our meeting tomorrow. Something urgent came up and I have to handle it. Would Thursday morning work for you instead? I'm available any time before noon. If that doesn't work, just let me know what suits you, and I'll move things around. Again, apologies for the change.", questions: [ { q: "Why does the speaker want to reschedule?", options: ["They're on holiday", "Something urgent came up", "They forgot"], answer: 1, ex: "Something urgent came up." }, { q: "When do they suggest instead?", options: ["Thursday morning", "Friday evening", "Wednesday night"], answer: 0, ex: "Thursday morning." }, { q: "What if the new time doesn't work?", options: ["They cancel forever", "They ask Sam to suggest a time", "They get angry"], answer: 1, ex: "Let me know what suits you." } ] }, speaking: { prompt: "Ask a colleague to schedule a call, suggest a time, and offer to send the agenda. (Use: 'could we schedule', 'I'm available', 'I'll send')", target: "Hi Mia, could we schedule a quick call this week? I'm available on Wednesday after 3pm. If that works, I'll send the invite and the agenda." }, writing: { prompt: "Write an email to reschedule a meeting. Apologize, suggest a new time, and ask if it works.", model: "Hi Sam, I'm sorry, but I need to reschedule our meeting tomorrow — something urgent came up. Would Thursday at 10am work for you instead? If not, let me know what time suits you and I'll adjust. Sorry again for the short notice. Thanks for understanding!", tips: "Apologize → suggest new time → ask flexibility → polite closing." } }, { topic: "Reporting a problem", emoji: "🚨", words: [ { en: "issue", ru: "проблема, вопрос", def: "a problem or concern", ex: "There's an issue with the system." }, { en: "to break down", ru: "сломаться", def: "to stop working", ex: "The server broke down this morning." }, { en: "to affect", ru: "влиять, затрагивать", def: "to have an effect on", ex: "This affects all our users." }, { en: "urgent", ru: "срочный", def: "needing fast action", ex: "This is urgent, please look at it now." }, { en: "to fix", ru: "чинить, исправлять", def: "to repair or solve", ex: "We're working to fix the issue." }, { en: "workaround", ru: "временное решение", def: "a temporary way around a problem", ex: "There's a workaround for now." } ], dialogue: [ { who: "A", name: "You", text: "Hi, we have an urgent issue with the website.", tr: "Привет, у нас срочная проблема с сайтом." }, { who: "B", name: "Dan", text: "Oh no, what's happening?", tr: "Ой, что происходит?" }, { who: "A", name: "You", text: "It broke down and it's affecting all users.", tr: "Он сломался, это влияет на всех юзеров." }, { who: "B", name: "Dan", text: "I'll look into it right away. How long has it been down?", tr: "Сейчас посмотрю. Сколько он уже не работает?" }, { who: "A", name: "You", text: "About twenty minutes. Is there a workaround for now?", tr: "Минут двадцать. Есть временное решение?" }, { who: "B", name: "Dan", text: "Yes, I'll share a workaround while we fix it.", tr: "Да, дам workaround, пока чиним." } ], reading: { title: "How to report a problem clearly", text: "When something goes wrong at work, the way you report the problem matters. A clear report includes four things: what happened, when it started, who is affected, and what you have already tried. Avoid panicking or blaming people — focus on the facts. If the issue is urgent, say so directly so people know how fast to react. Offering a temporary solution, even a small one, shows that you're not just reporting problems but also helping solve them. Clear, calm reports get fixed faster.", questions: [ { q: "What four things should a clear report include?", options: ["What, when, who, what you tried", "Who, why, who to blame, cost", "When, where, weather, mood"], answer: 0, ex: "What happened, when, who is affected, what you tried." }, { q: "What should you avoid?", options: ["Facts", "Panicking or blaming", "Being specific"], answer: 1, ex: "Avoid panicking or blaming people." }, { q: "What does offering a temporary solution show?", options: ["That you don't care", "That you help solve problems", "That you're angry"], answer: 1, ex: "It shows you're helping solve them." } ] }, listening: { title: "Reporting an issue", text: "Hi Dan, I need to report an issue. The payment page stopped working about an hour ago, and it's affecting all our customers in Europe. I already checked our end and everything looks fine, so it might be on the provider's side. I think this is urgent because we're losing orders. Could you take a look as soon as possible?", questions: [ { q: "What is the problem?", options: ["The payment page", "The login page", "The dashboard"], answer: 0, ex: "The payment page stopped working." }, { q: "Who is affected?", options: ["Only one user", "All customers in Europe", "No one"], answer: 1, ex: "All customers in Europe." }, { q: "Why is it urgent?", options: ["They're losing orders", "It's Friday", "It's a small bug"], answer: 0, ex: "They're losing orders." } ] }, speaking: { prompt: "Report a problem to a colleague: say what happened, who is affected, and that it's urgent. (Use: 'urgent issue', 'affecting', 'look into it')", target: "Hi, we have an urgent issue. The website is down and it's affecting all users. Could you look into it right away?" }, writing: { prompt: "Write a short message reporting a problem: what happened, when it started, who is affected, and what you tried. Mark it as urgent.", model: "Hi team, this is urgent. The login system stopped working around 2pm and it's affecting all users. I already checked the server and restarted it, but the issue is still there. Could someone from IT look into it right away? Thanks!", tips: "Чёткая структура: что → когда → кто → что пробовал → просьба. Без паники, по фактам." } }, { topic: "Agreeing & disagreeing politely", emoji: "⚖️", words: [ { en: "to agree", ru: "соглашаться", def: "to share the same opinion", ex: "I agree with your idea." }, { en: "to disagree", ru: "не соглашаться", def: "to have a different opinion", ex: "I disagree, but I see your point." }, { en: "fair point", ru: "справедливое замечание", def: "a good, reasonable argument", ex: "That's a fair point." }, { en: "to see both sides", ru: "видеть обе стороны", def: "to understand both opinions", ex: "I can see both sides here." }, { en: "to compromise", ru: "идти на компромисс", def: "to meet in the middle", ex: "Let's compromise on the deadline." }, { en: "to push back", ru: "возражать, мягко сопротивляться", def: "to oppose an idea politely", ex: "I'd push back on that timeline." } ], dialogue: [ { who: "A", name: "You", text: "I think we should launch next week.", tr: "Думаю, надо запустить на следующей неделе." }, { who: "B", name: "Kim", text: "I'm not sure. That feels a bit rushed.", tr: "Не уверен. Как-то спешно." }, { who: "A", name: "You", text: "Fair point. What worries you most?", tr: "Резонно. Что беспокоит больше всего?" }, { who: "B", name: "Kim", text: "We haven't tested it enough yet.", tr: "Мы ещё недостаточно протестировали." }, { who: "A", name: "You", text: "I can see both sides. Let's compromise — soft launch?", tr: "Понимаю обе стороны. Давай компромисс — мягкий запуск?" }, { who: "B", name: "Kim", text: "That works for me. Good idea.", tr: "Меня устраивает. Хорошая идея." } ], reading: { title: "Disagreeing without conflict", text: "At work, you will often disagree with colleagues, and that is completely normal. The skill is to disagree without creating conflict. Start by showing you heard the other person: 'I see your point' or 'that's a fair point'. Then introduce your view with softer language — 'I'm not sure' or 'I'd push back on that a little'. Avoid words like 'you're wrong', which make people defensive. Focus on the idea, not the person. The goal is not to win the argument, but to find the best solution together, which often means compromising.", questions: [ { q: "Is disagreement at work normal?", options: ["No, never", "Yes, completely normal", "Only for managers"], answer: 1, ex: "It is completely normal." }, { q: "What phrase helps soften disagreement?", options: ["'You're wrong'", "'I'm not sure'", "'Stop talking'"], answer: 1, ex: "'I'm not sure' смягчает." }, { q: "What is the goal of a disagreement?", options: ["To win", "To find the best solution together", "To be loud"], answer: 1, ex: "Find the best solution together." } ] }, listening: { title: "A polite disagreement", text: "I see your point about moving fast, and I agree that speed matters. But I'd push back a little on launching next week. From what I can see, we still have a few open bugs, and I'm worried that could hurt the first impression. What if we compromise and do a soft launch with a small group first? That way we move quickly but also stay safe.", questions: [ { q: "Does the speaker agree speed matters?", options: ["Yes", "No", "Not sure"], answer: 0, ex: "'I agree that speed matters'." }, { q: "Why do they push back?", options: ["Open bugs", "No budget", "Bad weather"], answer: 0, ex: "Still a few open bugs." }, { q: "What compromise do they suggest?", options: ["Cancel the launch", "A soft launch with a small group", "Launch immediately"], answer: 1, ex: "A soft launch with a small group." } ] }, speaking: { prompt: "Politely disagree with a colleague who wants a very tight deadline, and suggest a compromise. (Use: 'I see your point', 'I'd push back', 'compromise')", target: "I see your point about finishing fast. But I'd push back a little — two days is too tight. What if we compromise and aim for Friday instead?" }, writing: { prompt: "Reply to a colleague's idea you partly disagree with. Acknowledge their point, share your concern politely, and suggest a compromise.", model: "Hi Kim, I see your point about launching next week, and I agree we shouldn't wait too long. But I'd push back a little — I'm worried we haven't tested enough. What if we compromise and do a soft launch with a small group first? That way we move fast but stay safe. What do you think?", tips: "Признай точку → мягко возрази ('I'd push back a little') → предложи компромисс." } }, { topic: "Wrapping up & follow-ups", emoji: "✅", words: [ { en: "to summarize", ru: "подводить итог", def: "to give a short version of what was said", ex: "Let me summarize what we agreed." }, { en: "action item", ru: "задача-результат встречи", def: "a task someone will do after a meeting", ex: "My action item is to send the report." }, { en: "deadline", ru: "крайний срок", def: "the time something must be finished", ex: "The deadline is next Friday." }, { en: "to assign", ru: "назначать (задачу)", def: "to give someone a task", ex: "I'll assign this task to you." }, { en: "to deliver", ru: "доставлять, сдавать (результат)", def: "to produce the promised result", ex: "We'll deliver the update on Monday." }, { en: "next steps", ru: "следующие шаги", def: "what happens after this", ex: "Let's agree on the next steps." } ], dialogue: [ { who: "A", name: "You", text: "OK, let me summarize what we agreed.", tr: "Ок, подведём итоги." }, { who: "B", name: "Pat", text: "Sure, go ahead.", tr: "Давай." }, { who: "A", name: "You", text: "You'll send the data, and I'll write the report.", tr: "Ты пришлёшь данные, я напишу отчёт." }, { who: "B", name: "Pat", text: "Right. The deadline is Friday, correct?", tr: "Верно. Дедлайн — пятница, верно?" }, { who: "A", name: "You", text: "Yes. I'll deliver the report by Friday morning.", tr: "Да. Отчёт сдам в пятницу утром." }, { who: "B", name: "Pat", text: "Perfect. Clear next steps, thanks!", tr: "Отлично. Чёткие шаги, спасибо!" } ], reading: { title: "Why meetings end without results", text: "Have you ever left a meeting feeling confused about what happens next? This is one of the most common problems at work. People discuss a lot, but nobody writes down the action items — the specific tasks, who owns them, and the deadlines. Without this, everyone assumes someone else will do it, and nothing gets delivered. The fix is simple: the last five minutes of every meeting should be used to summarize. Say each action item out loud: 'Pat will send the data by Wednesday.' When everyone agrees, the meeting is truly over.", questions: [ { q: "Why do meetings often end without results?", options: ["Nobody writes down action items", "Too many slides", "Wrong room"], answer: 0, ex: "Nobody writes down the action items." }, { q: "What should the last five minutes be used for?", options: ["Small talk", "Summarizing action items", "Lunch plans"], answer: 1, ex: "Summarize action items." }, { q: "What should be said out loud?", options: ["Each action item, owner, deadline", "The weather", "A joke"], answer: 0, ex: "Each action item: who does what by when." } ] }, listening: { title: "Wrapping up a meeting", text: "OK everyone, let's wrap up. To summarize: Sara will finish the design by Wednesday and send it to the team. Tom will write the text by Thursday, and I'll put everything together for Friday's deadline. If anything changes, let's update each other in the group chat. Thanks for a productive meeting, and let's touch base again on Thursday. Have a good one!", questions: [ { q: "What will Sara do?", options: ["Finish the design", "Write the text", "Put everything together"], answer: 0, ex: "Sara will finish the design by Wednesday." }, { q: "When is the final deadline?", options: ["Wednesday", "Thursday", "Friday"], answer: 2, ex: "Friday's deadline." }, { q: "When will they meet again?", options: ["Thursday", "Next month", "Monday"], answer: 0, ex: "Touch base again on Thursday." } ] }, speaking: { prompt: "Wrap up a meeting: summarize who does what, confirm the deadline, and thank the team. (Use: 'let me summarize', 'will deliver', 'next steps')", target: "OK, let me summarize. You'll send the data, and I'll write the report. The deadline is Friday, and I'll deliver it by Friday morning. Thanks everyone, clear next steps!" }, writing: { prompt: "Write a follow-up message after a meeting: list the action items with owners and deadlines, and thank everyone.", model: "Hi team, thanks for the great meeting. Quick summary of our action items: Sara will finish the design by Wednesday, Tom will write the text by Thursday, and I'll put it all together for Friday's deadline. Please update the group chat if anything changes. Let's touch base again on Thursday. Thanks everyone!", tips: "Список action items с именами и сроками + благодарность. Это самый полезный навык для рабочих чатов." } } ];