About
Kenny Okeke

My professional experience spans engineering, consulting, and project-based roles, where much of my work centered on solving real client problems within practical constraints. I've led 50+ projects and initiatives with a total portfolio of $10M+ end-to-end, working across 15+ cross-functional teams and covering early definition, execution, and close-out.

In consulting environments, I partnered closely with customers to understand their needs and clarify ambiguous requirements, translating those needs into solutions delivered across diverse teams. This often meant working across technical and non-technical stakeholders, aligning expectations, timelines, and priorities, and ensuring solutions were grounded in operational reality and client value.

Across these roles, I also spent time on the client side of engagements, where I was responsible for specifying requirements and articulating needs. Experiencing work from this perspective reinforced how critical clear problem definition and shared understanding are to successful outcomes, strengthening how I approach collaboration and execution today.

Over time, I began to recognize a consistent pattern in the work I gravitated toward. Across my roles, I was drawn to solving customer problems, making decisions under uncertainty, and aligning teams around a clear direction. I was already working as a Product Manager.

Outside of formal work settings, conversations centered on technology and how products are designed and experienced helped crystallize this realization. I realized that my way of thinking extended beyond my role and into how I engaged with the technology I used every day. I became increasingly interested not just in using technology, but in the systems and design decisions behind the tools themselves.

Rather than viewing product management as a transition, I came to see it as a formalization of responsibilities I had already taken on, combined with a desire to build technology-driven products I genuinely care about. I pursued an MBA to sharpen my judgment through structured decision-making, data analysis, and evaluating tradeoffs across customers, teams, and scale — allowing me to operate more intentionally as a product manager in technical environments.

I view product management as operating at the intersection of desirability, feasibility, and viability. Strong product decisions sit where customers genuinely want a solution, technology can realistically support it, and the business can sustain it over time.

In practice, I ground decisions in customer insight to understand desirability, partner closely with engineering to assess feasibility, and evaluate options through the lens of business impact and scale to ensure viability. My role is to navigate the tradeoffs between these dimensions and bring clarity when priorities compete.

Working in this space requires comfort with ambiguity and accountability for decisions. I focus on making calls that hold up across customer needs, technical realities, and business constraints, while keeping teams aligned around a shared direction as work evolves.