DEV Community: sonnia okoye

Our Company's Newest Employee is an AI. It's Rewriting My Job Description.

sonnia okoye — Fri, 04 Jul 2025 21:37:16 +0000

We thought we were just getting a faster way to work. We got a new creative partner that’s changing everything.
magine you run a team. For years, your main job has been managing a to-do list. You take big company goals, break them into small, neat tasks, and hand them out. You measure success with charts and deadlines. Your world is orderly, predictable, and feels under control.
That was my world. Until we hired an AI.
Now, this AI isn't a person. It's a "super-assistant" that lives inside our computers. We brought it in to help our team with their creative and technical tasks, hoping it would make them faster And it did. At first, it was like magic. Tasks that used to take days were getting done in hours. Our productivity charts went through the roof. I felt like a genius.
But then, I realized the charts were lying. The numbers were up, but the "feeling" of control was gone. We hadn't just bought a faster tool; we had introduced a brilliant, unpredictable, and slightly weird new partner onto our team. And it was quietly changing everyone's job, especially mine.
The Problem with a Super Fast Assistant
Think of the AI like an intern who has read every book in the world but has zero life experience.
If you give it a vague task like, "Draft a client proposal," it will instantly create a proposal. It will look perfect. But it might be based on a template from a completely different industry, or it might sound like a lawyer from the 1980s. It’s fast and impressive, but it has no common sense. It doesn't understand our client or our company's style.
This created two huge problems:
Guessing Games: We could no longer predict how long a task would take. A simple job could be done in 5 minutes if the AI knew exactly what to do. But a slightly more complex job could take days of fixing the AI's weird mistakes. Our neat to-do lists and deadlines became meaningless.
Strange Mistakes: When a human makes a mistake, you can ask them why. You can trace their logic. When the AI makes a mistake, there’s no "why." It just blended two ideas from its vast library of knowledge that shouldn't have gone together. Fixing it feels like solving a bizarre puzzle.

This Isn't Scary, It's an Opportunity
Some people see this change and get nervous. They see a loss of control. I see the biggest business opportunity of our lifetime.
The companies that thrive will be the ones that master this new partnership. They will build teams of great "storytellers" and "editors" who can direct AI to create amazing things at unbelievable speeds.
Imagine launching a new product in a week instead of a year. Imagine testing a new marketing idea in an afternoon instead of a month.
This is the future of work. It’s less about the robotic process of a factory assembly line and more about the creative collaboration of an artist’s studio. And frankly, it's making our jobs more human, more creative, and more exciting than ever before.

What’s one AI tool you can’t live without and one you just discovered that blew your mind? Ask ChatGPT

sonnia okoye — Wed, 02 Jul 2025 18:14:49 +0000

How I Delivered My First AI Win Without Engineers. A PM's Real‑World Playbook"

sonnia okoye — Wed, 02 Jul 2025 10:53:04 +0000

A practical case study from a digital project manager on scoping, building, and launching a real AI-powered chatbot MVP no engineers needed."
tags: ai, project-management, startups, customer-experience, nocode
series: "From Chaos to Clarity: My Journey into Digital PM in the Age of AI"

If you're a digital PM or startup operator being told to "bring in AI" without a proper roadmap, you're not alone.

In this post, I walk through how I turned a vague CX goal into a functioning, measurable AI customer experience project without engineers, custom code, or fancy frameworks.

🧠 No engineers

🧰 No custom code

📉 Just a real business problem, scoped clearly, solved with the right tools

The Problem Was Obvious (But Nobody Scoped It)

We reviewed customer support tickets. One issue dominated:

“Where’s my order?” made up 30% of our volume.

Leadership wanted to “use AI to improve CX.” AI isn’t a strategy it’s a tool.

So I reframed it as:
Reduce repetitive “Where’s my order?” support requests by 50% using AI automation

That’s how solid projects start: with a clear pain point and KPI.

MVP Plan: What We Did (and Didn’t Do)

We didn’t hire engineers or build complex systems.

We used:

✅ Chatbase to build a GPT powered chatbot
✅ Google Sheets as a simple order status database
✅ Zapier to connect the chatbot to the sheets with no code

Time from planning to live test? Just 10 days.

Results After 2 Weeks

Tested on 20% of site visitors:

Metric	Result
Queries handled by AI	58%
Customer satisfaction	↑ from 3.5 → 4.4
Ticket volume	↓ 42%
Escalations	↓ 47%

These quick, real results built support for a full rollout.

Lessons for Other PMs If you're leading AI adoption, focus on: Start with repetition, not ambition then tackle the most common queries Pick tools that fit your stack and ignore buzz, choose utility Scope fast, iterate fast,the MVPs that work beat perfect plans. Measure impact AI only matters if it saves time or improves experience

Let’s Discuss

Have you done your own AI MVP?

What hurdles did you face?

Share your experience or your toughest challenge below 👇

Coming next in the series: Part 3 “No Engineers Needed: AI Tools That Actually Work for Small Teams”

Connect with me:

🔗 LinkedIn – Sonnia Okoye

🐙 GitHub – @sonniaokoye

The David vs. Goliath Playbook: How Small Teams Can Build Big Tech-Caliber AI Customer Experiences

sonnia okoye — Mon, 23 Jun 2025 18:49:04 +0000

For decades, the narrative has been the same, the Big Tech, with its colossal R&D budgets, server farms, and armies of PhDs, sets the standard for customer experience. Their AI-powered recommendation engines, impossibly fast support bots, and hyper-personalized journeys have felt like an unachievable competitive goals. For most startup founders, small business owners, and product leaders, the game seemed rigged honsetly.

but guess what That era is over.
The very tools and foundational models pioneered in the labs of Google, Meta, and Microsoft are no longer their exclusive domain. They have been productized, packaged into APIs, and made accessible to anyone with a credit card and a clever idea. The new competitive advantage isn’t the size of your research budget; it’s the speed of your execution, the depth of your customer empathy, and the intelligence of your strategy.
This is the playbook for the lean, the agile, and the ambitious. It’s how you, as a small team, can build AI-powered customer experiences that don't just mimic Big Tech, But to tailor them to meet the needs of the business and, in many cases, exceed expectations in focus and effectiveness.

There are Three fundamental shifts have demolished the old barriers to entry whuich i called the great equalizer

The API-fication of Intelligence: Foundation models like OpenAI's GPT-4, Anthropic's Claude, and Google's Gemini are now utilities. You can "rent" a world-class AI brain via a simple API call for pennies. Big Tech did the heavy lifting of training; you get to do the creative work of applying it.
The Rise of the No-Code/Low-Code "Nervous System": You don't need a team of machine learning engineers to connect these AI brains to your business processes. Platforms like Zapier, Make.com, and Retool act as a central nervous system, allowing you to build sophisticated workflows that link your CRM, support desk, and marketing tools with powerful AI capabilities—often with zero code.
The Agility Advantage: A small team's greatest superpower is its proximity to the customer and its lack of bureaucracy. While a Big Tech company debates a new feature in committee for six months, you can identify a customer pain point on Monday, build a prototype AI solution on Wednesday, and deploy it by Friday. The game has changed. The resources are in your hands, the cost of entry has collapsed, and the agility of a small team has never been more valuable. The question is no longer if you can compete with Big Tech on AI-powered customer experience. The question is, how will you choose to win?

I Started in Research, Became a Business Owner, and Now I Build Digital Solutions That Solve Real Problems

sonnia okoye — Mon, 16 Jun 2025 13:04:04 +0000

"Sometimes, the best builders aren’t the ones who started with code but they're the ones who started with people."

When I studied economics at the University of Jos Nigeria, I had no idea that one day I’d be leading product research, building internal systems, or launching digital platforms in the UK. What I did know, even then, was that I cared about people, data, and impact.

My first step into the world of work was as a research assistant for a health focused NGO in Nigeria. I helped design surveys, analyse data, and translate community stories into strategic reports. That was the first time I understood the power of structured thinking how the right question could lead to meaningful change.

From Research to Building a Brand

After that, I stepped into something bigger entrepreneurship. I launched Glitzential, a beauty and fashion start-up, where I handled everything from customer onboarding to project implementation.

What people didn’t see was the digital layer:

I was creating internal systems, managing CRM data manually, and customising processes to improve customer experience. I wasn’t just running a business I was engineering one in real time.
That experience became my foundation. Because when you’ve built with limited tools, you develop an instinct for solutions.

🛠️From Support to Strategy
Over time, I evolved.
I led digital projects at Ozenas Media Tech, launching e-learning and streaming platforms for creative professionals in Nigeria. I moved from coordinator to product innovation lead, overseeing UI, user research, and cross-functional teams.
I then relocated to the UK, earned an MSc in International Business and Data Analytics and began working with UK and remote companies across retail, health, and SaaS industries.
in the UK, I’ve worked as a:

Project Manager
Business Analyst
Start-up Coordinator
Digital Strategist

At every stage, I stayed close to the user, the data, and the business goal.

🔍 What I Build Now

Today, I’m focused on:

Automating processes that cost teams time
Analysing customer journeys for smarter marketing
Designing systems that scale without breaking
Empowering support teams with internal tools
Creating bridges between technical teams and business outcomes

I’ve come a long way from being the one who just “makes it work.” Now, I’m the one who makes it better.
💬 Why I’m Writing This
This isn’t just an origin story.

It’s a public declaration that "talent exists beyond traditional borders". That people who started in support, research, or admin like I did deserve a seat at the table of innovation.

🧠 Final Thoughts
I’ve worked across industries, countries, and platforms. But the mission remains the same:

Make systems that work better for people.
That’s what I plan to keep doing in public with purpose.
🤝 Let’s Connect
If you:

Are transitioning from support to strategy
Need a PM who understands both data and delivery
Or want to collaborate on smart, human-first digital projects

Follow, comment, or reach out. I’d love to hear your story too.

From Chaos to Clarity: My Journey into Digital Project Management in the Age of AI (part 1)

sonnia okoye — Fri, 13 Jun 2025 11:03:37 +0000

"Tech isn’t about the tools....it’s about the people, the process, and the problems we choose to solve.”

It wouldn’t feel right to jump in and start sharing my opinions without first telling you a bit about my journey into tech.

Like many kids growing up in Africa, I was raised in a culture where success was defined by becoming a doctor, lawyer, or engineer. That was the dream because that was what success looked like back then. No one imagined that one day, the world would shift, and entirely new, life changing career paths would emerge.

My transition into tech didn’t happen overnight. It came through curiosity, resilience, and a genuine desire to solve real-world problems using digital tools. And like many others, I had to unlearn, relearn, and find my own path.

I’m sharing this because behind every professional profile is a story and this is mine.

What was your childhood dream job and how has it changed? What does your current or future career dream look like now? care to share?

Why Developers Should Be Involved in Scoping, Not Just Delivery

sonnia okoye — Thu, 12 Jun 2025 06:35:08 +0000

Too often, developers are handed features and deadlines they had no say in then expected to "just build it." But here's the truth: involving devs early, during project scoping, doesn’t slow things down. It prevents chaos later.

As a Digital Project Manager, I’ve seen how dev input at the earlyplanning stage saves time and avoid delays and mistakes:

Exposes assumptions before they become blockers

Surfaces smarter, simpler technical solutions

Helps avoid overpromising and underestimating

Builds shared ownership between product and engineering

I try to create space for developers in sprint planning, roadmap reviews, and even at early stage ideation when possible. Their insights on feasibility and edge cases save so much time and frustration down the line.

If you're a developer do you feel sometime looped into scoping discussions, or just pulled in when the "fun" starts?
If you're a PM or product lead, how do you include devs early without slowing progress?

Let’s talk. 👇

Developers Hate Meeting But Here's How I Make Mine Useful and short

sonnia okoye — Tue, 10 Jun 2025 18:26:39 +0000

Let’s be honest most developers and frankly speaking, most humans hate meetings.

As a Digital Project Manager, I have learned that the best way to support a dev team isn’t just managing timelines, it’s knowing when to talk, what to cut off, and how to keep people focused without slowing them down and making the meeting impactful.

Here’s what works for me:

✅ Default to async
I push updates to Notion, Slack or Jira first. Meetings are for alignment, not just reading status updates out loud.

✅ No agenda!!! No meeting !!!
If I can’t clearly write why we are meeting and what we need to decide, I cancel it.

✅ 15- 30 minute max standups
Anything longer is a red flag, either too much detail or unclear priorities.

✅ Let devs run the demo
When possible, I let engineers show their work in sprint reviews. It gives them ownership and cuts fluff.

✅ I take notes, not them
My job is to free up their mental space, not add more overhead.

If you’re a dev, what’s the least annoying thing a PM or coordinator can do?

If you’re a PM, what’s your go to tips for keeping meetings clean, useful, purposeful and short?

Let’s swap ideas. 👇

Developer hates meetings, but here's how i make mine useful and short

sonnia okoye — Tue, 10 Jun 2025 18:20:41 +0000

Let’s be honest, most developers and frankly speaking, most humans hate meetings.

As a Digital Project Manager, I have learned that the best way to support a dev team isn’t just managing timelines,it’s knowing when to talk, what to cut and how to keep people focused without slowing them down.

Here’s what I have found works:

✅ Default to async
I push updates to Notion, Slack, or Jira first. Meetings are for alignment, not reading status updates out loud.

✅ No agenda? No meeting.
If I can not clearly write why we are meeting and what we need to decide, I cancel it.

✅ 15-30minutes max standups
Anything longer is a red flag, either too much detail or unclear priorities.

✅ Let devs run the demo
When possible, I let engineers show their work in sprint reviews. It gives them ownership and cuts fluff.

✅ I take notes, not them
My job is to free up their mental space, not add more overhead.

If you’re a dev, what’s the least annoying thing a PM or coordinator can do?

If you’re a PM, what’s your go to tips for keeping meetings clean and useful?

Let’s swap ideas. 👇