People often start with the wrong question:

“Can we replace this person with a language model?”

That is not a very useful way to think about it. A better question is:

“Which parts of this work are humans bad at – and can we let a language model handle those parts?”

Humans are good at some things, and bad at others. Language models are the same: they are good at some things and bad at others, but not on the same things as humans. The point is not to replace people, but to let models do the things humans are worst at.

Humans are good at judgement, context, and dealing with messy situations. We can understand nuance, read between the lines, and make choices when there is no clear right answer. We are also good at empathy, trust, and relationships. We know the people we work with, we feel their reactions, and we adjust our tone and message. And our creativity is tied to lived experience: we connect ideas from our own lives, culture, and values.

Humans are, on the other hand, consistently bad at repetitive and boring work. We lose focus when we have to do the same thing again and again. We struggle with large amounts of information: reading 50 pages of documentation, checking 200 rows in a sheet, or comparing 20 different options. We are not good at perfect consistency over time. And we are often bad at slow, tedious structuring: turning scattered notes into clear text, documentation, or clean summaries.

Language models have different strengths. They are very good at handling a lot of text quickly: reading, summarizing, comparing, and restructuring information. They are good at generating first drafts: emails, outlines, descriptions, and alternative formulations. They can apply clear instructions and formatting rules much more consistently than humans.

They also have weaknesses. A model has no real-world experience. It does not know your team, your history, or your unwritten rules. It can sound confident but still be wrong, so it must be checked. And it struggles when the goal is vague. “Summarize this in five bullet points for a manager” is much easier than “Do something useful with this”.

Because humans and models are good and bad at different things, you should not try to replace humans directly with a model. A job is not one thing; it is a collection of tasks. Some tasks need human judgement and relationships. Some are repetitive and text-heavy. Many can be split: the model does the first version, the human finishes it.

A practical way to think about it is like this: if a task depends on empathy, trust, or difficult decisions, keep it with a human and maybe let the model assist in the background. If a task is boring, repetitive, or full of text, let the model do as much as possible and let the human review. If a task needs a draft, let the model create it and the human refine it.

For example, when writing something, the human can decide what needs to be written, who it is for, and why it matters. The model can turn notes into an outline and a first draft. Then the human edits, adds real examples, and takes responsibility for the final result. The same pattern works for emails, reports, meeting notes, documentation, and many other things.

You can start simply. List the tasks you do in a typical day or week. Mark the ones you find boring, repetitive, or easy to postpone. Those are usually the ones humans are worst at and where a model can help. Ask the model to do the first pass on these tasks: summarizing, drafting, restructuring, or formatting. Then you review and correct. Over time, you will see which parts of your work are better done by a model and which should clearly stay with you.

The mindset shift is important: do not focus on replacing people. Focus on letting the model handle the parts of work humans are bad at, so humans can spend more time on what they are good at. Let the model do the repetitive, text-heavy, attention-heavy tasks. Let humans use their judgement, experience, and empathy.

The goal is not to copy humans with a language model. The goal is to combine different strengths.