How to build tools without knowing how

Target Connect Key User Group · 15 minutes · drive it from /talk/?present=1 · → advances, ← back, F fullscreen, T timer, O overview

Green = say this out loud · plain = do this · red = fill in / don't forget. Notes deliberately live here, not in the deck.

0:00Open

"How to build tools, widgets and doodads"

I'm not a developer. If you sat me at an empty file I wouldn't know where to start. But I've built about thirty tools people use every week.

Open cold — no agenda. Let the two facts sit together. The honesty is the credibility; don't oversell later.

1:00The idea

Learn just enough to get something smarter than you to do the work

I can't write code. I've learned just enough of the vocabulary to point AI at the right thing — and that turns out to be the whole job.

Set up the promise: tips for making AI build something bigger than a single prompt gives you.

2:00Ecosystem

Twelve things → one ecosystem→ reveals

Ask AI for twelve tools and you get twelve strangers — different fonts, different colours, nothing shared.

Press → and the four clashing tools snap into one brand.

Same twelve tools, one set of rules. Now it's a platform — and each new tool is easier than the last, not harder.

2:45The build

Four switches: HTML · CSS · JSON · API4 clicks

HTML — let the ugly version sit 3 seconds. "A page is a list of what's on it, nothing about how it looks."

CSS — point at the code pane, flip it: the markup doesn't move. Then the colour swatches re-brand five tools at once. "One file, thirty tools."

JSON — type into the pink numbers; the card updates live. "Content in a labelled box. The team edits data, nobody needs me."

API — the moment. Say the posting count out loud. Then take a shout from the room — type a job title into the box, press enter. "A door into someone else's system you're allowed to knock on."

Keys 1–4 jump to any switch if you lose your place.

6:45Recap

Four files. Four ideas.

Structure, style, content, data. That's the whole vocabulary.

Hover each card and its code example expands below — walk through the four. No mouse? Keys 1–4 do the same. Then advance.

7:00Nothing

Look what you can do with nothing

No money. No coding knowledge. Here's what I made anyway.

7:45Showcase

Events Feed live

This isn't a list I keep updated. It reads Target Connect's events feed and builds itself, live, every time.

9:00Showcase

Pathway widgets live

Static pages get looked at. Things you can do something with get used.

Flashcards + verb roulette. Built for the pathway activities in Target Connect.

10:15Showcase

Founders Showreel — JSON again live

Two different widgets — a showreel and a wall — reading the exact same JSON file. The tools never change; the data does.

The catch: the team can't edit JSON. So they fill in an Airtable — a spreadsheet — and overnight a robot turns it into the JSON. Nobody in that chain knows what an API is.

11:15Showcase

Skills Explorer — API live

Live occupation data from a government skills service. None of that data is mine. I just know how to ask for it.

12:00The count

Thirty tools. One rule book.

Thirty-plus tools. One shared stylesheet. No backend, no database, no logins — just files. Nothing to break into, no student data to lose. It's why it got past IT.

FILL IN: one concrete student story — a session or a stat where a tool changed the conversation. Most persuasive 30 seconds in the talk, and only you have it.
12:45Live build

Let's make something — right nowhelpchat

Switch to Target's helpchat in the other tab. Paste the prompt shown on the slide. When it gives you HTML, copy it, come back, paste into the box — it renders live on the right.

If it's ugly, tell it what's wrong in plain English and paste the new version. That back-and-forth is the point.

Plan B — if helpchat misbehaves, click the discreet "plan b" button (bottom-right of the box). It copies a known-good countdown widget to your clipboard; paste it in and carry on. Don't fight it live.

14:15Close

AI does the building. Knowing what to ask is yours.QR

You just watched four switches — structure, look, content, truth. I can't write a line of any of them. Knowing they existed was enough.

Point at the QR: "Everything here, plus a plain-English guide to all four, is on that page. Scan it." Your name and email are on screen too. Then stop talking — no thank-you slide.

If you're running over

  • Cut a showcase slide (pathways first) — press O, jump ahead.
  • Then trim the build to 3 switches.
  • Never cut the API switch, the live build, or the close.

If something breaks

  • Live data fails: falls back to a cached snapshot on its own (badge goes amber). Numbers still real.
  • A tool won't embed: a branded card appears instead. Carry on.
  • Lost your place: O for overview, 1–4 for build switches.

Questions you'll get

Before you start