Client delivery dashboard
A delivery dashboard a client uses to track their own messages, built end to end.
Next case studyLeading a cross-service change
I led an identifier migration across the platform's core services, coordinating five engineers, with no known client impact attributable to the team.
- Role
- Led the change, coordinating five engineers
- Client
- A business-messaging platform
- Scope
- Across the platform's core services
- Delivery
- Completed before it was required
01
The problem
Meta’s change to how WhatsApp identifies users meant some users would be represented by a new user ID rather than a phone number. The business-messaging platform could no longer rely on the phone number alone to identify a user.
The identifier change touched the platform’s core services and its database, and Meta gave no exact switchover date.
02
What I did
I led the change. I ran the planning sessions, coordinated five engineers across the platform’s core services and the database migrations, and planned selected services myself where I had deep domain knowledge. When priorities changed, I explained the reprioritisation to stakeholders.
The team worked test-first, and every change went through automated AI review and human review before merging. The work took about two months.
Diagram of the change. A new user ID feeds a line that branches down to the core services, drawn as numbered boxes, some of which lead to database tables. A dimension line beneath marks about two months.
03
Results
Engineers
5 engineers
coordinated across the platform's core services, working test-first.
Duration
about 2 months
to complete the change.
04
Stack
- Python
- PostgreSQL
- WhatsApp Business Platform
Contact
Get in touch
Tell me about your project, your team or the problem you're working on.
Or find me on LinkedIn