DEV Community

Nathan (Nate) Brumand
Nathan (Nate) Brumand

Posted on Originally published at nathanbrumand.com

Start With the Work, Not the Tool

Start With the Work, Not the Tool

I've spent most of my working life on the practical side of business: customers, employees, schedules, suppliers, cash flow, and all the small decisions that never make it into a press release. That shapes how I look at AI. I'm interested in one question: does this help a real business do its work better, this month, at a cost that makes sense? If the answer is unclear, I'd rather say so than pretend.

The demo vs Monday morning

Most AI demos are impressive. They're also clean. The data is tidy, the request is clear, and nobody is interrupting with a customer on the other line.

Real businesses don't look like that. Information lives in inboxes, spreadsheets, notebooks and people's heads. When a tool that looked great in a demo meets that reality, it usually needs more setup, more checking and more patience than anyone expected.

That isn't a reason to avoid AI. It's a reason to bring it in with open eyes. The useful question isn't "what can this tool do?" It's "what does our work actually look like, and where would help make a difference?"

Understand the process first

One lesson years in business taught me, long before AI: a new tool rarely fixes a process nobody understands. It usually makes the confusion faster.

Before adding AI anywhere, answer a few plain questions:

  • What exactly happens today? Who does the task, how often, and how long does it take?
  • What does "good" look like? If you can't describe a good result, you can't check whether a tool produced one.
  • Where does it go wrong? Mistakes and delays are usually where the real opportunity is.
  • Who owns the result? Every task needs a person who is responsible for it, with or without AI.

The human always decides

AI can gather, sort, draft and suggest. A person decides.

Anything that affects a customer, an employee, money or a commitment should pass through a human who reads it and owns it. The tool can prepare a reply; someone approves it before it goes out. That's about responsibility and trust, not only about avoiding errors.

Try one task

If you run a small business or lead a team with no tech staff, keep it simple:

  1. Pick one task that wastes time every week.
  2. Note how long it takes now, even roughly.
  3. Try a tool on it for a few weeks, checking the output yourself.
  4. Keep it only if it clearly helps. If it doesn't, drop it and move on.

There's no prize for adopting the most tools. There's real value in adopting the right one.


Adapted from my longer piece on nathanbrumand.com. I'm Nathan (Nate) Brumand. I write The AI-Business Connection about practical AI in business. More: nathanbrumand.com

Top comments (0)