Firefly Notes
Meetings

Q3 roadmap sync

· 5 min · 3 Speakers

Ready
  1. Recording
  2. Transcribing
  3. Summarizing
  4. Ready

Speakers

  • Amara Okafor
  • Ben Liu
  • Chloe Martin

Agenda

Confirm Q3 priorities, agree owners for the onboarding redesign, and pick a launch date for the reporting API.

  1. Amara Okafor

    Morning, everyone. Let's get started, we've got three things to cover today: Q3 priorities, the onboarding redesign owners, and picking a launch date for the reporting API.

  2. Ben Liu

    Sounds good. I already sent around the draft priorities doc, did everyone get a chance to skim it before this call?

  3. Chloe Martin

    Yeah I read through it. I think the top three make sense, but I want to push back a little on ranking performance work below the onboarding redesign.

  4. Amara Okafor

    That's fair, let's talk it through. Ben, what was the reasoning for putting onboarding first?

  5. Ben Liu

    Mostly churn data. We're losing about eighteen percent of new signups in the first week, and support tickets keep pointing to confusion in that first setup flow.

  6. Chloe Martin

    Okay that's compelling, I didn't have that number. If churn's that high, I agree it should sit above performance.

  7. Amara Okafor

    Great, so let's lock in the order as onboarding redesign, reporting API, then performance work. Everyone okay with that?

  8. Ben Liu

    Works for me.

  9. Chloe Martin

    Agreed, let's move on.

  10. Amara Okafor

    Alright, onboarding redesign owners next. Chloe, would you be up for driving the design side, working with the product team on the new flow?

  11. Chloe Martin

    Yeah I can take that. I'll need someone from engineering paired with me though, since the flow touches a bunch of backend validation steps.

  12. Ben Liu

    I can pair with you on that, I've already got context from the churn investigation anyway.

  13. Amara Okafor

    Perfect, so Chloe owns design and coordination, Ben owns the engineering side. Can we get a rough plan by, say, next Friday?

  14. Chloe Martin

    Next Friday works, that gives us about a week to sketch the wireframes and get feedback.

  15. Ben Liu

    Good with me too, I'll block time this week to map out the backend pieces that need touching.

  16. Amara Okafor

    Great, that's settled then. Now let's talk about the reporting API launch date. Ben, where's development at right now?

  17. Ben Liu

    We're about eighty percent through the core endpoints. QA hasn't started yet, and honestly I'd want at least two weeks of testing before we call it stable.

  18. Chloe Martin

    If dev wraps in, what, a week and a half, and we add two weeks for QA, that puts us somewhere around the third week of August.

  19. Amara Okafor

    That tracks with what sales has been telling customers, roughly. Could we commit to August twenty-first as a target launch date?

  20. Ben Liu

    I'm okay with that as a target, but I want to flag it's tight if QA finds anything major. Can we build in a few buffer days?

  21. Chloe Martin

    What if we say August twenty-first is the internal target, but we don't announce publicly until we're through the first week of QA?

  22. Amara Okafor

    That makes sense, less risk of overpromising. So internal target August twenty-first, public announcement decision made after week one of QA.

  23. Ben Liu

    Sounds reasonable, I'll get QA scheduled and send the plan by Wednesday.

  24. Chloe Martin

    And I'll loop in marketing so they're not caught off guard when we do decide to announce.

  25. Amara Okafor

    Perfect. So to wrap up, priorities are confirmed as onboarding, reporting API, then performance. Chloe and Ben own the onboarding redesign with a plan due next Friday, and the reporting API targets August twenty-first internally with QA feedback driving the public date. I'll send notes out this afternoon, thanks everyone, good session.