top of page

No, I’m not lazy. I’m using AI properly

  • Writer: Marianne Van den Ende
    Marianne Van den Ende
  • Jun 9
  • 2 min read

Yesterday, I had a conversation with some other parents. We were talking about work, projects, and I casually mentioned how I use AI tools like ChatGPT and image generators to help me with writing, Facebook posts, visuals, icons ... the whole range.


And then… silence.


Followed by pearl-clutching-level shock. The reactions ranged from:

  • “How dare you use that?”

  • “Wow, I could never.”

  • And my personal favorite: “Isn’t that just lazy?”


Lazy? Really?

I didn’t know what was more insulting. The idea that I was doing something scandalous for using a tool, or the assumption that using AI meant I wasn’t really working.


Here’s the thing they didn’t understand: Using AI well is work.

It takes experimentation. Tuning. Iterating. Prompting. Re-prompting. And refining again.

I read a quote this morning that nailed it perfectly:

“I’m not doing the task anymore. I’m building the system that does the task.”

And that’s exactly it.


I’m not outsourcing creativity or effort. I’m learning to design workflows. I’m building prompts and processes. I’m iterating on outputs. I’m treating AI not as a shortcut, but as a toolset.

Because here’s the truth:

AI is only as good as the person using it.

Garbage in = garbage out. Every time.

We’re not just clicking buttons

Using AI isn’t about sitting back and letting the machine do everything. It’s about getting specific. Being intentional. Knowing what you want and how to guide a system to help you get there.


That’s not lazy. That’s skill.


In fact, I believe we’re going to see a rise in AI consultants, prompt engineers, and workflow designers. Roles that exist solely to help people and companies leverage AI tools more efficiently.


Kind of like how we’ve had lean consultants to improve processes, or automation experts to optimize logistics. Only now, it’s about information work. About creating faster, more precise systems of thought, output, and creation.

So why the backlash?

Honestly? I think it comes down to two things:

  1. Misunderstanding: people still think AI is some sci-fi robot writing novels and stealing jobs. They don’t see it as a tool, they see it as a threat.

  2. Fear of being replaced: if a machine can generate something, then what’s our role? But that fear ignores the nuance: AI generates based on direction. Human direction.


And if you’ve never used it yourself, it’s easy to think it’s magic. It’s not. It’s interface. It’s language. It’s logic and creativity, wrapped into a tool that still needs a human at the helm.

We should be teaching this

What shocked me most in that conversation wasn’t the judgment. It was the missed opportunity.


AI tools are here. They’re powerful. And they’re only getting more integrated into how we live and work. The question isn’t “should we use them?” The question is: how well can we use them?


I genuinely believe there’s a skill gap forming. Not just in coding or AI development, but in AI fluency. Knowing how to get value from these tools, and how to build processes around them. Not just for efficiency, but for creativity. For possibility.


And right now? Most people aren’t there yet.


But they will be.


Or they’ll fall behind.

 
 
 

Comments


bottom of page