A new role is growing between your team and IT

You know exactly where the friction is in your work. Requests that come in twice, data you type out three times, checks that are the same every time. So you neatly write out how the process runs, and you send that to IT. And what you get back is not what you meant. You might recognise that.

In a training course on AI and workflows, a participant shared something just like that. His team had written out the process step by step, because they wanted to use AI for it. IT replied with a few scripts, and with the message that AI was not actually needed. It was just programming. Both sides had done good work, and yet nobody felt they understood each other.

Copy the prompt at the bottom of this article. With it, you turn your own process into a description you can use to build yourself, or that helps IT understand you better.

Why you talk past each other

I actually see that at quite a few companies. There are people who know the business well. They know what they want: less double work, less copy-pasting, fewer of those silly tasks that make nobody happy. But then they have to go to someone who can build something for that, with or without AI.

And the people in IT often do not have that knowledge of the business. They are focused on IT, and they have different goals. For them, it is about compliance and security. For you, it is about keeping the business running. Those are both good goals, only they are not the same. So you translate your question for someone who speaks a different language, and he translates his answer back. The more steps there are in between, the more gets lost along the way.

Frequently asked questions

Why do business and IT so often not understand each other?

The business knows the work and wants it to run more smoothly. IT knows the systems and guards compliance and security. They are both good goals, but they are not the same, and every translation in between costs something.

What does someone in that new role do?

That person knows the business and can build with AI tools. They work within the infrastructure and the policies of IT, and build a system within that which the team manages itself.

Do I need to be able to program for that?

You do not really have to, because with today's agents you explain what you want in plain language. What you mainly need is knowledge of your own work and the principles of how you build with AI.

Where do I learn to build workflows with AI myself?

In the training courses 'AI automation with n8n and MCP' and 'Vibe Coding with AI' you build your own workflows and tools hands-on. You can find all dates at Workshops & Events.

Keep reading for free

Register free with your e-mail address and read on. Your account opens the free articles in the learning space; the rest is for subscribers, from Learn Plus up.

No comments yetRead the comments

Comments

Members comment here and read each other's comments. Register for free or sign in to join the conversation.

No comments yet. What do you take away?