Before Building Your AI Solution: Start with the RIGHT Problem

Before Building Your AI Solution: Start with the RIGHT Problem

According to a  RAND report, private sector investment in AI grew 18 times more between 2013 and 2024, and over half of mid-sized companies have already deployed at least one AI model.
Managers feel pressure to ‘do something with AI’, but most struggle to translate the leader’s ambition into action (AI transformation).

"AI adoption is almost everywhere today"

The biggest mistake? Organisations focus more on using cool technology than solving actual problems for their users.
If you’re solving the wrong thing, even the most advanced AI won’t help – it might make things worse 😐.

🧠 First Understand the Problem:

  • Don’t build a tool based on AI just because it’s trendy.
  • Stop and think if AI is truly needed for this problem, because not every problem requires AI.
  • Define the problem clearly. Like in each project, think: What user pain point are you trying to solve?

🔍 Use Research & Design Approaches:

  • Ensure that technical staff understand the project purpose and domain context.
  • Focus on data quality first – not having high-quality data available to train your model will give you ineffective AI models.
  • Resist the ‘shiny object’ syndrome – avoid bias toward the latest technology when simpler solutions work better.

🤖 AI Is Not One-Size-Fits-All:

  • Choose the right AI model (if needed) – choosing the wrong tool could hurt your product.
  • Avoid overengineering solutions.

🧩 Map Current Workflows:

  • Before automating, understand the current user journey – how is the user currently trying to solve the problem?
  • Which step can AI automate or improve?
  • Consider what skills users need to address the larger problem.

🧪 Test Early with Prototypes:

  •  Use tools like Google AI Studio, or run a “Wizard of Oz” test.
  • Validate assumptions with real users to uncover hidden problems.
  •  Think About Diverse User Experience: Different users face the same problem differently, due to language, location, and habits. Align AI behaviour with real user intentions. Make it natural, safe, and ethical.

⚡ Key Takeaways for AI Product Managers:

  • Define the primary goal clearly – What should your AI system do for users?
  •  Consider sub-goals and alternatives.
  • Prototype early
  • Test AI concepts before building.

AI can be a powerful tool in helping users solve problems. But before building an amazing AI solution, take a step back. Spend some time analysing the problem, understanding the users, and considering the context. That’s how you build AI that helps.

 

Previous Introducing FabricTools (PowerShell module)
Next How to Manage AI Projects Effectively

About author

Paulina Nowinska
Paulina Nowinska 5 posts

Product Manager, Scrum Master, and AI practitioner passionate about turning ideas into impactful, user- centered solutions. I blend Agile leadership, product strategy, and hands-on experience with AI, automation, and emerging technologies to guide teams through digital transformation. I’m building AI-driven projects, including Vibe Coding apps, exploring creative workflows, automation, and multi-agent orchestration to bring innovative solutions to life.

View all posts by this author →

You might also like

General 0 Comments

The most-read posts in 2018

Good morning #sqlfamily folks! The very first post in the new year 2019. Tell me: when this time passed??? The year 2018 has just gone. From the blog perspective, it was

General 0 Comments

Last Weeks Reading (2024-01-28)

📰 News Fabric end-to-end use case: Data Engineering part 2 – Pipelines If you’re new in Microsoft Fabric – check this series and build it with Sam. Set up Azure

SQLSaturday 0 Comments

Speaking at SQLSaturday #656 Denmark 2017

On Saturday, October 7th, I’m speaking at SQLSaturday #656 Denmark 2017! I’m presenting Maintenance of a DB project and Continuous Delivery using SSDT. I will unveil disadvantages of SSDT and

0 Comments

No Comments Yet!

You can be first to comment this post!

Leave a Reply