Today was one of those days where everything felt… technical. Once we divided our responsibilities, each of us dove deep into our domains—technology, product, and content. I also handled some legal and financial matters, making sure all the moving parts align.
Then, we regrouped. We shared progress, pinpointed challenges, and figured out where we needed help. It’s a simple routine, but one that keeps us moving forward. And today, we hit an exciting milestone: in two weeks, we’ll have a working system ready to demo.
Splitting responsibilities in a small team isn’t just about efficiency—it’s about trust. In the early days, everyone wears multiple hats, but knowing who owns what helps prevent decision paralysis. For us, we follow a simple rule:
- Play to strengths – Each person takes the lead in what they do best.
- Own it fully – If it’s yours, drive it forward. Don’t wait for permission.
- Sync often – Regular check-ins ensure we stay aligned and unblock each other.
Beyond the technical work, one moment really hit me: realizing how close we are to launching something that will help emergency responders and security forces build resilience, regain focus, and grow from the intense experiences they face daily. That’s the bigger picture. That’s why we’re here.
We’re at day 319. There are 1,095 in this journey. Step by step, we’re getting there.
What’s your approach to dividing responsibilities in your team? Would love to hear how others handle this challenge.
