Progress Update #1: Building the AI Product Management Learning Repository
Progress Update #1: Building the AI Product Management Learning Repository
A Sneak Peek: The Double Trio Framework for AI Product Management
#beyondAI
To build an AI solution, you need Data, IT, and AI. But to transform an AI solution into an AI product, you also need Governance, Business, and People. While Data, IT, and AI might seem like the tough parts, the real challenge arises when you incorporate Governance, business acumen, and a focus on People.
It’s about ensuring the AI product not only functions effectively but also meets ethical standards, addresses real business problems, and delivers a great user experience. The "double trio" (Data, IT, AI - Governance, Business, People) frames what you need.
It's the balance of each, not just the mastery of a few.
I recently discussed this on LinkedIn. And it serves a purpose.
This framework, which I've developed and frequently use at the onset of any new AI product, forms the cornerstone of all my AI Product Requirement Documents. It also shapes how I manage tasks and train aspiring AI Product Managers. Those of you who have followed my LinkedIn posts might already be familiar with elements of my Double Trio pattern.
Originally developed for my personal use, this concept could also be beneficial for navigating your AI initiatives. However, the main purpose of this newsletter is to share my decision about how I'll be organizing all AI PM-related content within the AIPM repository I am currently building.
It is focusing on two primary areas:
Operational Trio
Technical Trio
You likely already have an idea of what fits into each category. And that’s why I think it is a good choice.
But let me give you some examples; I think these will help you understand the holistic field of AIPM and allow for quick and easy navigation through the AIPM contents in the repository:
AI Ethics is associated with Governance from the Operational Trio.
Machine learning models align with AI from the Technical Trio.
Stakeholder communication is closely linked to People from the Operational Trio.
System architecture and infrastructure fit under IT from the Technical Trio.
Market analysis falls under Business from the Operational Trio.
Each new piece of content submitted to the AIPM repository will be aligned with one of these trios or placed at their intersection, similar to MLOps.
Why have I named it the Double Trio?
I’ll soon write a more detailed introduction to the Double Trio framework to help you fully grasp the reasoning behind this approach, and there, I will also share my thoughts about the naming. 😉
For now, that's all.
Happy Sunday,
JBK 🕊️