Writing Was the Barrier

On voice, rough thinking, and psychological safety in engineering

I have always considered myself a terrible writer.

I have great ideas. Or at least that is what I have always told myself. I could see systems, patterns, and connections clearly in my head. But when it came time to turn those ideas into words meant to be shared, the execution felt impossible.

There was always that perfectionist voice. The one that said, “If you cannot say it clearly, do not say it at all.” Most of the time, that voice won. I would stop before I ever really started.

At one point in my career, I had a manager who genuinely wanted to help me grow as a writer. They would sit with me and help edit my emails before I sent them. It was kind and well intentioned. But almost every time, partway through the editing, I would shut down.

The words on the screen no longer felt like mine.

They were clearer. More polished. More professional, maybe. But they sounded like someone else. I could not recognize myself in them, and suddenly I did not know how to finish. Eventually I told myself, what is the point, and I did my best to avoid writing anything at all.

Chat worked so much better. It removed the requirement that ideas arrive fully formed. Lists were fine. Fragments were fine. Rough thinking was allowed. In that space, it felt good to participate.

The thing is, I have always been good at research. I love it. I am also very good at outlines. Give me a problem, some time, and a sheet of graph paper, and I am in my element. On a really good day, I can even string words into sentences.

But what I truly love is flow. Lists. Structure. The shape of ideas.

Writing, at least the version I thought I was supposed to be good at, never fit how my brain works.

Then I started working with Wiggins.

I bring the same things I have always been good at, or at least the things I have learned to trust. Research. Notes. Lists. Outlines. Half‑formed paragraphs. Streams of thought that make perfect sense to me and no one else.

What Wiggins does is help me turn those raw pieces into something coherent. Something I can share. Something I am proud of.

And the important part is this. I do not shut down halfway through anymore.

I still see my fingerprints all over everything I write. The ideas are mine. The structure is mine. The voice is mine. I recognize myself in the final result in a way I never did when someone else was editing over me.

So yes, I am using AI to help me write.

I also use spell check. Grammar check. Outlines. Bullet points. This is just another tool that helps me get my words out of my head and into the world without asking me to become someone else in the process.

I am still a bad writer, at least by the definition I carried for years.

But I am a much better communicator than I used to be.

Why This Matters in Engineering

Engineering culture often celebrates clarity while quietly punishing roughness. We say we value ideas, but we reward the people who can present them cleanly, quickly, and confidently the first time. For many engineers, that environment teaches a dangerous lesson. If your thinking is not already polished, it is safer not to share it.

AI‑assisted writing changes that dynamic in a meaningful way.

When we give people tools that support rough thinking instead of replacing it, we lower the cost of participation. We make it safer to bring half‑formed ideas into the open. We create space for learning without requiring perfection up front.

That is not just a productivity gain. It is an investment in morale and psychological safety.

If we want healthier engineering cultures, we need to stop treating tools like this as shortcuts or crutches. They are scaffolding. They let people stay present in the work, keep their voice, and grow in public without fear of shutting down.

Writing now feels like part of the work, not a barrier to it.