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.
-
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.
-
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.
-
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.