The FAQs.
Short, sendable answers to the questions I get asked most. Newest first. The first fourteen shipped together as part of the Foundational Collection, one practical answer beside each core resource.
-
When do I add the next person, and to which seat?
Weight the hires to the top of the funnel. The deep engineering seats compound; the enablement seats hit their ceiling first.
-
What does an AI Product Partner actually do all week?
Less than the title suggests and more than a calendar shows. The clearest picture of the job is one real week, from the morning briefing they built to the two lines they write in the board deck.
-
How does the AI Product Partner role actually start?
Not on an org chart. Point a trusted translator at a real, cross-functional problem, and let the role reveal itself before you name it.
-
How do I keep an AI pilot from stalling?
Stop letting a demo authorize a build. Prove adoption at each rung before you fund the next, and let the prototype find the real problem instead of selling a roadmap.
-
We have the tools. No one's using them. Now what?
The problem is not the tools; it is that deploying a tool is not the same as adopting it. Adoption is a people problem, and you fix it people-first, not by buying more software.
-
How do I know I can trust any of this?
Because it shows its work. Every claim is labeled by what kind of claim it is, sources are primary and linked, and corrections happen in the open.
-
Can I use an AI first draft in a regulated document?
For framing and a running start, yes. As the submission, no. The draft clears the blank page; the human writing, review, and quality process is untouched, and the author of record stays human.
-
How long should we keep AI meeting transcripts?
There is no magic number. Default the raw transcript to auto-delete, set the timer with your legal and records functions, and never let it override a legal hold or a required regulated record.
-
Isn't efficiency a good place to start?
Yes, as the on-ramp. No, as the destination. Take the hours back, then spend them on redesign, not on a faster version of the same company.
-
Isn't teaching the whole company the policy too expensive?
Yes, and the expense is the point. Senior time spent teaching is the signal that the policy matters. The cheap alternative, a PDF on a shared drive, is what produces a policy nobody follows.
-
How do I justify a win that doesn't show ROI?
You don't, not on ROI. Fund a small slice of time that is deliberately exempt from the business case, and measure it on adoption and belief, because the return is a change agent, not saved hours.
-
Should AI report to IT?
Not by default. Point AI at your most forward-thinking senior leader, high in the company. If IT is involved, its mandate has to change from control to enablement, or you have pointed the future at the department of no.
-
Should I keep AI away from my most important work?
Not never. But in a resource-constrained shop, point it at the low-judgment work first, and spend the bandwidth you free on the work only your best people can do.
-
If AI finds no red flag, is the target safe?
No. A clean day-one pass is not a clear. It means AI found no reason to stop in what it searched, which is not the same as no reason existing.
-
Can I use AI in a validated workflow?
Two different questions usually hide in that one. Drafting a document a human owns is not the same as putting AI inside a validated system of record, and mostly the second is where validation bites.
-
Who on my team should own AI?
The T-shaped operator your people already trust, not your most technical person and not an outside hire. Look for the shape, not the title.
-
What will the first 90 days cost?
Mostly attention, not budget. The real cost is one owner's 20% and an honest scorecard meeting. If you are writing a big check in the first quarter, you are doing it backwards.
-
What's a passing score?
There isn't one. You are only as native as your weakest pillar, so the goal is not a high number, it is a rising floor.
-
Which rung of the ladder should I start on?
Almost always one rung lower than your instinct. Start where you can make something real this quarter, then compose upward.
-
How do I audit my own company against its own rules?
Write the rules down first, most cannot, then check your loudest AI work against them, in public.
-
How do I get AI to write in my voice?
Do not describe your voice. Show it. Feed the model your real writing and correct what it gets wrong.
-
Doesn't thinking with AI make writing slower?
At first, and that is the point. You are buying depth, not speed. Over a few pieces it is faster.
-
How do I run build-versus-buy in a real meeting?
Out loud, with the people who own the requests. Route the three loudest, then the three smallest.
-
What if legal wants a longer, stricter AI policy?
A longer policy no one reads protects no one. The one-page version is not lax; it is the enforceable one.
-
Are we AI-native, or just AI-enabled?
One question tells you. What has your company reconsidered, versus just sped up?
-
Do I hire an AI Product Partner, or grow one?
Usually grow one, from someone who already understands the work. The scarce half is judgment, not tools.
-
How do I tell a real build from rebuilding a commodity?
One test. Could you buy it, and would buying it cost you nothing that matters? Then it is a commodity.
-
Which pillar should I fix first?
Not the one you like to show off. Start with the pillar you are worst at, and it is usually People.
-
Where do I actually start with AI at my biotech?
The honest first move is not a tool or a task force. It is one workflow, one owner, and one real question.