Date: 2026-03-05
Format: Conversational, ~30 min
Vibe: Very casual, warm. Told Andrea upfront it was conversational and about getting to know her. Put her at ease immediately.
Fred noted there are 5 PMs across the product org with overlaps in what's being built. Asked about Andrea's experience working across teams, building consensus, making progress.
Andrea's answer: Used the Ting migration project — touched every team in the org. Worked closely with senior management (regular one-on-ones with CCO at WaveLo) for top-down support. Built a knowledge base as the central place for project information. Did all project scoping and regular updates. Used the CCO relationship to drive alignment and unblock teams. "We were all speaking the same language."
What landed: The migration scope (every team) and the knowledge base as a coordination mechanism.
Gap: Could have been more specific earlier — started broad before anchoring in the migration example.
Follow-up from Q1. How did Andrea stay informed across silos?
Andrea's answer: Differentiated from migration (sequential, easy to track) to product management work where parallel streams existed. One-on-ones with team leaders to surface what wasn't in reports. Necessary because teams were siloed with no cross-functional communication other than what she was doing.
What landed: The instinct that reports don't tell the full story — one-on-ones surface what's about to happen.
Gap: Didn't explain the context (no centralized dashboard existed) which would have turned a routine habit into a deliberate strategy. Answer was shorter and less specific than it could have been.
Fred described the tension of multiple product pillars needing to align with a singular product vision. Asked for a relevant story.
Andrea's answer (strongest of the round, ~5 min): Lalamove story. Trajectory from marketing manager to driver ops manager. Two-sided marketplace where supply was critically low. Key insight: "we didn't sell to our drivers" — drivers aren't employees, they can't be compelled. Phased approach:
- Early: picked up the phone, talked to drivers directly, increased training attendance (key conversion bottleneck)
- Mid: promotion program — monthly best driver prize, photos posted in driver channels
- Late: community building — barbecue socials, dinners, creating belonging beyond just income
Result: Grew driver base significantly, hit 80% of a very ambitious target.
Connected it back to Fred's pillar tension: in a two-sided marketplace, the trade-off was dialing down user-side resources to focus on driver supply, because without drivers the platform couldn't serve users at all. Prioritization grounded in business reality.
Bonus: Fred is Brazilian and recognized Lalamove (operates in Brazil). Built natural rapport.
Fred asked how she tracked metrics and whether it was in partnership with other teams.
Andrea's answer: Partnered with data analytics team for raw data — app engagement from Mixpanel, operational metrics (training scheduled, DAU, MAU, retention cohorts, acquisition). Senior ops leaders had built some initial structure; Andrea adopted, transformed, and built new reporting/dashboards for both senior leadership and operational teams.
Gap: Question was vague, answer matched the vagueness. Focused on mechanics (who built what) rather than strategy (what she measured and why). Stronger version: "I partnered with data for infrastructure, but I owned what we measured and why."
Asked about managing user expectations around inherent complexity in AP/procurement workflows vs. usability.
Fred's response:
- Depends on user segment: SMBs expect consumer-grade experiences; enterprise expects customization
- Tension between mid-market simplicity and enterprise complexity (ERP integrations, etc.)
- Even within mid-market: internal procurement (employee buying a laptop) has consumer-grade expectations
- Finance teams are the primary daily users of his product pillar
- Currently layering AI/automation into workflows — auto-filling invoices and orders to reduce time-on-task
Insight for future rounds: Fred's product philosophy is segment by user sophistication. AI in his domain = reduce time-on-task, not replace users. Internal vs. external procurement is a useful segmentation to reference.