Systems Thinking,
Applied to Software.

I graduated with a degree in Agricultural Engineering from the University of Benin (2024, 2:1). My real education came from watching how systems actually work in practice. During my SIWES attachment at NIFOR (Nigerian Institute for Oil Palm Research), I was embedded in the Agricultural Engineering Research department, observing and assisting in the fabrication and testing of oil palm processing machinery. I learned how engineering decisions made in design translate—or don't—into real production workflows. I watched teams solve problems on paper and then solve them differently in practice. During my NYSC service at the Tractor Hiring Agency, I observed operations from inside. I learned that systems fail not because people are incompetent, but because the gap between design and reality is wide. I learned to watch for friction. Where do operators struggle? Where do they improvise? What do they actually need that nobody's giving them? That observation became my framework: Watch where systems create friction for the people using them. That friction is design insight.

I've always been inquisitive. Ask why. Ask how. Ask what if. People called it talking too much. I called it trying to understand. That curiosity never changed. But somewhere along the way, I realized: I was already doing product management. Asking how do people actually think? Why do they do things that way? What do they actually need? Those aren't annoying questions—that's the entire job. So I formalized it. TSAcademy gave me frameworks and methodology. But the core skill? That's always been me.

From operations to product management, I've built one principle: The user under pressure reveals the truth. When someone is trying to solve a problem fast, they don't have time for elaborate workflows. They cut through to what actually matters. Build for that clarity. This means: - Constraints clarify. Limited resources force focus. Unlimited options force confusion. - Observation beats assumption. You can't guess what users need. You have to watch. - Shipped products teach faster than planning. Real users on real devices in real contexts reveal what matters. - Ruthless prioritization. Every feature that ships must solve a real problem for a real user under real pressure. I'm early in my PM career. That's an advantage. Every assumption gets tested. Every shipped feature has to earn its place.