Living and building in Lagos is a special kind of chaos. Generators humming through the walls at odd hours, Okada horns screaming past like they're personally offended by traffic, WhatsApp messages arriving at all hours from people who assume you're always available, and underneath all of it, the constant low pressure to hustle harder, faster, on top of whatever you're already carrying. For the longest time I genuinely thought I was handling all of it fine. While building CozonPay, I found out I'd been lying to myself about that.
There was one particular week in May I still think about. I was implementing the payment link system — real, careful work that needed my full attention if it was going to be done right. My laptop was open in front of me, but my mind was scattered across five other places at once. Thinking about how to promote the feature on Twitter once it shipped. Worrying, in the background, about whether the power would hold. Wondering if I should actually be recording music instead of doing this. Checking my phone every few minutes out of a habit I didn't even consciously choose anymore. I wrote some code, ran a quick test, saw it pass, and moved on to the next thing, satisfied with a surface-level confirmation that everything was fine.
Later that night, going back over the day's work with a clearer head, I realized I'd left a critical security check incomplete. Not implemented halfway and forgotten — genuinely skipped, because I'd been too scattered earlier to notice the gap while I was actually inside the code. It wasn't a disaster. Nothing broke, nobody was affected, I caught it before it shipped anywhere near a real user. But it could have been a disaster, easily, and that possibility is what actually hit me hard once I sat with it. I'd been physically present at my desk for hours that day. Mentally, I'd barely been there at all.
In fintech — especially something handling actual people's money, the kind of money someone needs to arrive safely because they're depending on it — that gap between being physically present and actually being present is dangerous in a way it isn't in most other kinds of work. A distracted mistake in a blog post is embarrassing. A distracted mistake in a payment system is somebody's money at risk, and that's not a category of mistake I was willing to keep making just because staying scattered felt normal.
So I made real changes after that week, not the polished, Instagram-mindfulness version of discipline, but something built specifically around how my actual days in Lagos work. I started running dedicated focus blocks — phone on airplane mode, physically left in another room, for two-hour stretches at a time, with one specific task written down in a notebook before I even opened my laptop, so there was no ambiguity to drift toward halfway through. I leaned harder into single-tasking too, more ruthlessly than I had before — when I was inside the P2P transfer feature, nothing else got a tab open, no exceptions. When it was ArtistBio's turn, everything payment-related got closed first, completely, not just minimized.
I won't repeat the full detail here since I've written elsewhere about the walking practice and the broader "doing less" shift that grew out of this same period — both genuinely came from this same stretch of realizing how scattered I'd let myself become. What I'll say specifically about that May week is that it changed how seriously I take the gap between looking busy and actually being present. I started catching bugs earlier, consistently, not because I got smarter overnight but because I was finally paying attention to the same degree the work actually required. The code started feeling more intentional, less like something assembled in fragments between distractions. And oddly, I ended up with more energy left in the evenings for music, not less — laying down hooks and experimenting with sounds as Owlzila, something that had quietly stopped happening during the scattered stretch without me fully noticing it had stopped.
Building here teaches you, whether you ask for the lesson or not, that focus is closer to a survival skill than a personality trait. Between unstable power, expensive data, and distractions arriving from every direction at once, the people who actually succeed tend to be the ones who've figured out how to protect their attention deliberately, instead of assuming it'll just take care of itself.
I'm not going to pretend I've got this fully solved. Some days I still slip back into the old scattered pattern, phone in hand before I've even decided to pick it up. But I'm better at catching it now than I was in May, and CozonPay is genuinely better for it — simpler, more reliable, actually useful for small businesses and individuals who just want to collect money without friction or stress, instead of a feature-heavy product built by someone who was only ever half paying attention to any single part of it.
If you're building anything in Lagos, or anywhere with a similar amount of noise pulling at you constantly, I'd tell you what I wish someone had told me before that week in May: presence isn't optional once real stakes are involved. Protect one hour of genuinely undistracted work a day if that's all you can manage right now. You'll likely catch things you would've otherwise missed entirely — and depending on what you're building, that might matter more than you realize until the moment it actually does.
Real success, I've come to think, was never really about doing more. It's about being fully where you actually are while you're doing it — something I only understood properly after almost learning it the expensive way.
How do you handle distractions while building in an environment like this? I read every comment, so tell me honestly — I'd genuinely like to know I'm not the only one who's had a moment like that May week.