Most teams are stuck in mode one
Ask around your company how people use AI and you'll hear the same story: they open a chat window, ask a question, copy the answer, and move on. That's genuinely useful — and it's also the smallest slice of what this technology does.
AI work comes in three distinct shapes, and the skill that separates teams getting real leverage from teams getting novelty is simple: recognizing which shape the task in front of you calls for before you start.
Shape #1: The conversation
This is AI as a thinking partner. You bring a half-formed idea, a confusing spreadsheet, an email that isn't landing — and you work it out together, one exchange at a time.
Use this shape when:
- The answer changes your next question. You're brainstorming or exploring, and you couldn't have written the full request up front because you didn't know it yet.
- Your judgment is the point. Drafting, editing, thinking out loud — you want to be in the loop on every turn.
- It's quick. A rewrite, a "what does this number mean?", a gut-check. Setting up anything more would be overhead.
The conversation is where most people start, and it's where most people stop. The mistake isn't using it — it's feeding a ten-step project into it one question at a time because chatting is the habit.
Shape #2: The hand-off
Here you stop asking questions and start delegating outcomes. Instead of "what should the summary say?", it's "read these fifty documents, find the ones relevant to the acquisition, and produce a two-page memo." The AI plans the steps, does the work, and comes back with the finished thing.
The tells that a task is a hand-off, not a chat:
- It has several steps you'd normally do in sequence. Pull the numbers, compare them, draft the summary, format the document. Delegated, that's one instruction — not four errands.
- It ends in a real deliverable. A spreadsheet, a formatted report, an updated deck — not a wall of text you have to reassemble yourself.
- It spans your tools. The notes live in one app, the thread in Slack, the numbers in a spreadsheet. A good hand-off gathers all three itself.
- It should recur. A Friday roll-up of what shipped. A Monday briefing before your first meeting. Describe it once, schedule it, and start the week with answers instead of admin.
Delegating doesn't mean disappearing. You review the plan, you watch the work take shape, and anything consequential — sending an email, sharing a file — waits for your approval. You're managing, not micromanaging.
Shape #3: The built system
The third shape is where the first two stop being things you do and become things your business does. A built system is AI wired directly into your operations: connected to your real data, running on triggers instead of requests, with checks and approvals designed in.
The difference is who has to show up:
- A conversation happens when you open the window.
- A hand-off happens when you ask for it (or on the schedule you set).
- A built system happens every time the trigger fires — a lead comes in, an invoice posts, a report lands — whether anyone's at a desk or not.
This is the shape where the compounding lives, and it's also the one that deserves real engineering: instrumentation so you can prove the before-and-after, guardrails where mistakes are expensive, and a human in the loop exactly where judgment matters. (It's also, not coincidentally, the work we do for clients.)
A 60-second sorting test
Take the task you'd most like off your plate this week and ask:
- Would the second question depend on the first answer? If yes, it's a conversation — go have it.
- Is it multi-step, does it end in a real file, does it touch more than one tool, or should it recur? Any yes makes it a hand-off — describe the outcome, not your first question, and let the AI run the steps.
- Does it happen whether or not you remember to ask? Then it wants to be a built system — triggered, measured, and reviewed, not manually launched.
The habit to break is defaulting everything into shape one. The habit to build is writing down the outcome you want and noticing when the task is really a delegation — or a system — wearing a chat costume.
If you've got a list of tasks and aren't sure which are hand-offs and which are worth building properly, that's a 30-minute conversation. Book a call and we'll sort your list into the three shapes with you.