All articles

Aiver Ilaya
Aiver IlayaDirector, Aliso Digital
ShareLinkedIn
Aiver Ilaya, director of Aliso Digital

Written by

Aiver Ilaya.

Director of Aliso Digital, a Melbourne-based IT consultancy specialising in digital transformation programs, process mapping and documentation.

There’s been a lot of talk about AI replacing writers.

But for me, it’s not something to fear.

I use AI every day in my work as a technical writer—and it helps me do the job better.

AI isn’t taking over my work.

It’s making me faster, more efficient, and able to focus on the parts that matter most.


🧠 What Technical Writing Looks Like Today

Technical writing is more than just writing.

It’s interviewing subject matter experts.

It’s mapping out workflows.

It’s creating help content, SOPs, product guides, and more.

It’s breaking down complex systems into usable content.

Most of that still relies on human skill.

But there are tasks that take time and drain energy.

Formatting.

Converting data.

Rewriting repetitive sections.

Organising feedback.

That’s where AI fits in.


⚡ How I Use AI to Work Smarter

Drafting initial content

Sometimes you just need a starting point.

I’ll feed AI a brief, a few bullet points, or a meeting summary.

It gives me a rough first draft to work from.

I always rewrite and shape it—but it saves me hours.

Structuring long documents

AI can quickly help turn messy notes or transcripts into a logical structure.

If I have a big dump of info, I can ask AI to group it, label sections, and highlight gaps.

It’s like having an assistant who doesn’t complain about sorting through chaos.

Rewriting content for clarity

Got a paragraph that’s too technical or clunky?

I ask AI to rewrite it for plain language.

I might not use the exact suggestion—but it gives me ideas and speeds up editing.

Formatting and consistency

AI tools help check for style issues, broken formatting, or inconsistent headings.

It saves me from missing small things when reviewing long docs.

Creating tables and summaries

When I need a quick table based on steps or categories, AI helps build one fast.

It’s also great for summarising long text into bite-sized overviews.


🔍 What AI Doesn’t Replace

AI can’t replace working with humans.

It can’t interview subject matter experts.

It can’t observe how a process actually works in the real world.

It doesn’t know your team, your tools, or your style guide.

It won’t spot the gaps in a flow diagram or ask why a step is missing.

And it won’t take responsibility if the documentation is wrong.

That’s on us.


🛠️ Why Technical Writers Should Embrace AI

Using AI doesn’t mean you’re lazy.

It means you value your time.

You want to spend less of it on the repetitive bits and more of it on the thinking, collaboration, and quality work.

When used well, AI makes you:

  • Faster at first drafts
  • Better at reviewing large volumes of text
  • More consistent across documents
  • More focused on content quality and accuracy

And if your team is under pressure to deliver more with fewer people, AI helps you meet deadlines without burning out.


💬 AI as a Tool Not a Threat

I see AI as part of the toolkit.

Like spellcheck.

Like templates.

Like style guides and checklists.

It helps me write faster—but I still decide what’s right.

I choose what gets published.

I validate with subject matter experts.

I bring context and judgement that AI can’t.

I’m not afraid of AI.

I’m using it to do better work, faster.

And I think more technical writers should too.

Read More

Related Posts

Hybrid Means Paying to Commute, Then Sitting on Video Calls

Here’s a typical hybrid day.Leave home early.Train or traffic.Find a desk.Then spend 6 hours on video calls with people who aren’t in the building. It’s hard to see what the commute bought.So let’s put numbers on it. 🚆 The commute is the cost Australian research puts a number on it.People

Structure Is the Technical Writer’s Actual Job

Ask most people what a technical writer does and they’ll say writing. Fair enough, it’s in the title. Spend a few years doing it though, and you notice the writing is rarely what makes documentation succeed or fail. Well written procedures nobody can find are useless. Plainly written procedures organised

The Gap Between a BPMN 2.0 Process Map and a Screen

Most system rollouts have 2 sets of documents that never quite meet. On one side sits the process work. A BPMN 2.0 process map, current state, future state, pools and lanes showing who does what. On the other side sits the design work. Wireframes, screen flows, a prototype somebody built