Build: building with AI, and how it gets checked

If someone has sent you this: they’re considering something new, and they’d like to agree with you what gets built with AI and how it gets checked before anyone relies on it. Tick what you’ve done, and talk about the rest.

Last updated

Download the PDF
Email it

Tick it on your own, or each of you separately and then compare.

What gets built

How it gets checked

Before anyone relies on it

Why these points are important

AI has made it quick to build something that looks finished. In my experience, the time saved in building tends to reappear later as time spent finding out what doesn’t work, unless the checking was planned from the start.

What usually goes unchecked

  • What happens when a payment fails.
  • What a customer sees on a phone.
  • Emails sent automatically.
  • Who can see whose information.
  • The small print in a contract template.

Each of these works most of the time, which is why nobody looks.

Why the builder shouldn’t be the only checker

Whoever built something tests the way they expect it to be used. Customers use it the way they actually do.

What I’d do first

I’d pick the one part that would hurt most if it failed in front of a customer, agree what “working” means for it, and have someone else try to break it.

When you’re the one it’s been sent to

If you’re building it, it helps to say which parts you can’t check yourself. Saying so early is cheaper than finding out after launch.

Where coaching fits

People at this point often use coaching to decide how much to build before the idea has been tested, and what they’d stop building if a test went badly. I won’t tell you what to build. I’ll ask the questions that show what each part of the build is meant to prove.

If you’re considering something new, AI Checkpoint is a free reflection on what AI could change about it, and who’s checking: simonbowen.com/reflections/ai-checkpoint