Product and engineering · PicPay
Redesigning the mobile flow without pretending dependencies don't exist
Reorganizing work across iOS, Android, web and product teams to improve priorities, predictability and collaboration in a financial business unit.
- Organization
- PicPay
- Period
- 2021–2022
01 · Problem
The problem behind the problem
The shortage of iOS specialists and the mismatch between platforms created queues, priority conflicts and low confidence in forecasts.
02 · Decisions
How I turned context into action
- Ran an assessment with developers and leadership to make bottlenecks and tensions visible.
- Structured a cross-team flow with a backlog prioritized by ROI and cost of delay, clear rationale and links to the roadmaps.
- Replaced fragile promises with forecasting based on lead time, throughput and work aging (probability, not estimate).
- Mentored product and tech people in value slicing, negotiation and dependency management, using Team Topologies and Flight Levels.
03 · Metrics
Results and observed signals
- Strategic moonshot objective reached at 90%. How it was measured: Strategic OKRs of the business (B2B) unit, focused on outcomes.
- New collaboration model between mobile stacks and consuming teams.
- Delivery probabilities instead of estimates to communicate reliability.
- Explicit policies for work transition and prioritization across teams.
04 · Lesson
What remained
Predictability does not come from more detailed estimates. It improves when the system reduces queues, invisible dependencies and aging work.