Team Meeting: A Project Delay

Try listening first, then use the text to check what you heard. Audio uses a computer-generated voice.

Rachel: OK, let's get started. The main item today is the mobile app launch. As you know, we were aiming for March 3rd. Victor, where are we with testing? Victor: Honestly, not where I'd like to be. The payment feature works on iPhones, but we're still seeing crashes on older Android phones — about one in five test transactions fails. Rachel: One in five? That's too high to launch with. What's causing it? Victor: We think it's the new security library. The vendor released an update last week, and our code isn't fully compatible yet. Their support team says a fix is coming, but they won't commit to a date. Rachel: So we're depending on someone else's timeline. Aisha, what does a delay mean for marketing? Aisha: It's not a disaster, but it's not ideal. We've already booked social media ads for the launch week. I can move them, but if we cancel less than ten days ahead, we lose the deposit — roughly two thousand dollars. Rachel: So we need a decision by February 21st at the latest. Victor, is there a plan B? Victor: There is. We could launch without the new library and use the old payment system for the first month. It's slower, but it's stable. The risk is that we'd have to update the app again in April. Rachel: I'd rather not launch something we know we'll replace in four weeks, but I'd also rather not miss March entirely. Let's do this: Victor, give the vendor until Friday. If there's no fix by then, we go with plan B and keep the March 3rd date. Aisha, keep the ads booked for now. Aisha: Works for me. Rachel: Great. So, action items: Victor contacts the vendor today and reports back Friday; Aisha prepares a backup message in case we move the date; I'll update the leadership team this afternoon.