Leading One Voice Journal from scope to handoff
What I learned engineering a cross-platform, offline-friendly journal with a six-person team and a nonprofit partner.
One Voice Journal is a cross-platform diary for personal and spiritual reflection. Through Develop for Good, I worked with Firm Collective as engineering manager, co-leading six engineers from early scoping through implementation and handoff.
Start by making the problem smaller
The product vision was broad at the beginning. Before implementation could move quickly, we needed to turn that vision into a clear first release: authentication, journal entry creation, and dependable offline behavior.
That scope gave the team a shared definition of success. It also made technical decisions easier because every choice could be evaluated against a concrete user journey instead of an open-ended wish list.
Offline support is a product decision
A journal should still feel trustworthy when a connection is unreliable. We used React Native for the cross-platform experience, Supabase for backend services, and WatermelonDB to support local data and syncing.
The important lesson was that offline behavior cannot be treated as a final polish item. It affects data flow, loading states, conflict handling, and the promises the interface makes to the person writing.
A handoff is part of the build
The project did not end at the demo. We polished documentation so future developers could understand the architecture, continue the work, and avoid rediscovering the same decisions.
Good leadership is not only about shipping the current version. It is also about leaving the codebase and the team with a clear path forward.