Keep Your Team Learning While You Automate

Protect the Friction That Makes Your Team Smarter

Teams are racing to automate every workflow they can. But speed without awareness creates a hidden problem: your output stays high while your team's understanding of the business quietly drops.

A recent study from the Anthropic Fellows program confirmed this. People who handed tasks entirely to AI retained significantly less knowledge about what they'd worked on, even when the quality of their output held steady. They moved faster. They just didn't get any smarter.

This is why I ask clients a question most automation agencies won't: "Where does your team need to keep struggling?"

Because struggle is where skill lives.

When a sales team manually reviews call notes, they spot the pattern that three prospects churned for the same reason. When a founder writes their own proposals, they can actually walk a prospect through the thinking behind them. Remove that friction and you lose the learning that makes your team sharper quarter over quarter.

The strategic question isn't "what can we automate?" It's "where does our team build the awareness that drives better decisions?"

Start with an intentional automation audit. Sort each task in your workflows into two categories: execution and discovery.

  • Execution tasks are repetitive, rules-based, and low-context. Data entry, status updates, report formatting, file routing. Automate these fully. Nobody develops strategic thinking by copying data between spreadsheets.

  • Discovery tasks require pattern recognition, judgment, or context-building. Reviewing customer feedback for trends, analyzing why deals stalled, reading sales call notes to spot recurring objections. These are the tasks where your team builds the awareness that compounds over time.

Here's how to apply this:

  • Tag every task in your current workflows as execution or discovery

  • Automate execution completely: data transfers, report generation, routine notifications, system syncing

  • Use AI as a research assistant for discovery tasks: let it surface data and summarize inputs, but have your team write the final analysis and make the calls

Not sure which workflows to automate and which to leave alone? We'll help you sort them out.