It’s not every click someone makes. A core activity is the lowest level where naming the work still helps the business. Too broad and nobody knows what’s inside. Too tiny and the labels turn into noise.
Think of a workshop with labeled drawers: drill bits, sanding pads, invoices to mail. The label isn’t the whole project, and it isn’t a single screw. It’s the useful unit. A workflow shows the order of work and a subfunction groups similar work; the core activity is the label you hand to someone and say, “This is the thing we do here.” “Open Gmail” is too small and “Manage client intake” is too broad, but “Review new client intake form” is right.
How it shows up
This is where work becomes teachable. You can turn a core activity into a skill, attach an SOP, and hand Claude or Codex the checklist, the examples, and the rule for when to stop and ask. Skip this level and you’re asking AI to “help with operations,” which is too mushy. An agent can’t read the invisible system in your head, so you have to make the labels visible first.
Why you care
A core activity is the unit of work you can name, improve, delegate, and eventually teach to an agent. Good ones read like work, not a department name: “Prepare monthly close checklist,” “Route signed agreement.” Get this level right and AI stops guessing at your business and starts following the work.