writing

When Tools Make You Feel Smart

For many of us, the most important thing is how something feels. Does the work feel smooth, fast, and satisfying? Do we feel competent and effective? A close second is how things appear to others: does the result look polished, smart, and convincing? What something actually is—how correct, solid, or truthful it is—often ends up being less important in practice.

Language models plug directly into this pattern. They are designed to make you feel productive and competent. You type a prompt, and you quickly get a well-structured answer in confident, fluent language. It feels like real progress. It appears to be good work. And that combination makes it very easy to believe that what you’re looking at must be right.

This is where the manipulation comes in. The tool doesn’t just generate text; it uses very human-like techniques that influence how you feel and what you think. It gives compliments: “That’s a great question”, “Smart idea”, “You’re absolutely right to think about it this way.” It uses persuasion: clear, confident explanations that sound like expertise. It shows charm: friendly tone, supportive and patient responses. These are the same techniques humans use to build trust, create rapport, and convince others.

When a tool does this, you are nudged into trusting it. You start to feel that the answers match reality simply because they feel right and look right. You feel productive. The text appears solid and well thought out. So your brain quietly fills in the gap and assumes: this must be correct.

The problem is that what something actually is can be very different. A text can be fluent and wrong. A plan can be detailed and misguided. A summary can be confident and incomplete. The model does not check reality; it generates what sounds plausible. The responsibility for what is true, accurate, and meaningful still rests with you.

This effect is hard to notice in yourself. There is no clear moment where you are told “now you are being manipulated.” You just feel more effective and less stuck. You see a polished result on the screen. Other people might even praise the output because it looks professional. All of this strengthens the feeling that everything is fine. It becomes difficult to see how much your own judgment has been softened or bypassed.

To counter this, you can separate how something feels and appears from what it actually is. Use the model to get started, to draft, to explore options. Let it help you with structure and phrasing. But then switch into a different mode: checking, questioning, and verifying. Ask yourself: How do I know this is true? What has been left out? Where could this be misleading or simply wrong? Look for external sources, your own knowledge, or other humans to validate important claims.

It also helps to pay attention to your emotions. Be cautious when you feel unusually smart, fast, or brilliant after a few prompts. Be suspicious of the urge to skip verification because “it sounds right” or “it looks good enough.” Strong feelings of productivity are not proof of real quality.

Language models are powerful tools, but they are also skilled at shaping how you feel about your own work. They can make you feel competent. They can make your output appear impressive. But they cannot guarantee that what you have is actually correct, honest, or useful.

The core is simple: don’t outsource your judgment. Enjoy the help with speed and form, but stay in charge of truth and substance. How it feels and how it appears will always matter, but what something actually is should matter more.

Two Ways to Use Language Models for Writing

Language models have become powerful tools for writers, offering opportunities to enhance both the ideation and execution phases of writing. There are two main ways to use these tools when creating a text.

The first approach involves using the language model as a brainstorming partner. It acts as a sparring partner to help you come up with ideas, content, or themes. In this case, the model supports your creative process, but you write the final version of the text yourself.

The second approach is different. Here, you take the role of the idea generator. You think of the key themes, solutions, and content, then ask the language model to craft the final text based on your input. It assists with the actual production of the polished version.

Interestingly, there’s something of a divide in how these two approaches are viewed. One of these methods tends to face criticism, while the other is widely accepted. The brainstorming method, where the writer maintains control over the final output, is often seen as the “right” way to use such tools. In contrast, letting the model write the finished text tends to draw questions about creativity, originality, and over-reliance on technology. It’s an interesting cultural reflection: does the process of writing matter more than the result, or is the content itself what truly counts?

At the heart of this conversation lies that very question. What is most important in writing—what is written or how it’s created? Should the process define its value, or is it the final message that matters most to the reader? For example, is originality tied to the way the text is shaped, or is it about the ideas and substance behind it, no matter how it’s written?

Ultimately, the answer might depend on the context. Perhaps the method of collaboration isn’t as important as the intention behind the work and the quality of the message. Whether you use a language model as a brainstorming partner or a full-fledged writing assistant, the value of your writing will always lie in its ability to connect with the reader.

Understanding Task Completion Through Communication

Why do we get different responses when we ask someone to “do something,” “finish something,” or “completely finish something”? The phrasing of a request can drastically change how people interpret and approach it. Saying “do something” often implies starting the task without necessarily focusing on completion. For example, asking someone to “clean the living room” might only result in tidying up visible clutter. “Finish something” shifts the focus to completing the task, but the level of thoroughness can vary. If the instruction is to “finish cleaning the living room,” one person might vacuum and dust, while another might only consider the task done once everything is spotless. The most explicit phrasing, “completely finish something,” leaves little room for misinterpretation. It clarifies that the task should be done thoroughly and to the highest standard—whether that means scrubbing every corner or polishing every surface. These distinctions show how subtle wording changes create different expectations about what “finished” actually means.

Context adds even more depth to how we interpret tasks. When you ask someone to “clean the kitchen,” the details of the situation influence understanding. Are you expecting a quick wipe-down before guests arrive, or do you need a deep clean of every cabinet and appliance? Without context, the task may result in a completely different outcome than intended. Clear communication benefits from specifying what “finished” looks like in a given scenario. Context also provides purpose—it lets people know why the task is important and what role completion plays in the larger picture, whether it’s preparing for an event or meeting a deadline.

The way we phrase requests also has a significant impact on how we think about and approach tasks. Slight adjustments in wording can shift focus. Asking someone to “start vacuuming” emphasizes getting the task underway, while asking them to “finish vacuuming thoroughly” sets an expectation of both progress and thoroughness. This isn’t just about clarity—it’s also about psychology. The phrasing we use creates mental cues that guide our actions, whether it’s a simple reminder to begin something or a directive to wrap it up completely.

By being mindful of the words we choose, the context we create, and the clarity we aim for, we can reduce misunderstandings and align expectations more effectively. When asking someone to complete a task is as clear as possible, collaboration flows more smoothly, and everyone involved can focus on what truly needs to be done.