As technical writers and documentarians we help facilitate awesome.

Project for Awesome is a wonderful annual event held by the Vlog Brothers Hank and John Green, oriented towards reducing the world’s suck. And wow do we need that right now! From it’s humble beginnings flooding the YouTube algorithms to a powerhouse fundraising event that makes substantial differences in the world. In 2025, Project for Awesome raised $3,739,918, including several generous matching donations from individuals and organizations. 50% of donations went to Save the Children and Partners in Health, and 50% of donations were split between 30 charities chosen by the P4A community.

I just finished an interview with Diana Payton for Technical Writing Uncensored and I'm buzzing with the joy of a good conversation. One of the concepts we explored was communities of practice. You form a community of practice around an activity with a shared passion for getting better at doing that thing. What happens is much more than just refining that craft. People who are drawn to a particular kind of activity often have shared traits and can build a community where your own style of weirdness might be more of a norm.

I’ve written, and abandoned, four different blog posts in the last few weeks! Each blog post fighting with itself as it was actually two or three blog posts.

So here’s a quick note that jumps straight to the point, plus the standard "Media I'm enjoying" section at the end.

Between 2018 and 2020 I had three psychotic episodes. It was terrifying, it caused me to doubt everything. It was isolating and it made me worry I’d never be able to hold down a stressful job again. In 2025, I’m in the best mental health of my life. I love the high stress work I do, and I feel joyfully connected to friends, community and my vocations.

Three in a hundred people will experience psychosis, but you wouldn’t know it based on what people are prepared to be open about. Autistic people are more likely to experience psychosis and are more likely to communicate their distress differently, which means that mental health professionals (not to mention friends and family) might not understand the level of trauma and impact.

This is a technical writing blog. If you’re not neurodivergent, you know people that are. I feel like neurodivergency is pretty neurotypical in technical writing circles! Our people are statistically more likely to go through psychosis, but those that do often brush it off and just get on with things.

IQ predicts how well you'll do in your school years and how much salary you can make over the course of a career because it says what job you can get... but once you're in those professions everybody else is about as smart as you are, and that is where emotional intelligence kicks in. - Daniel Goleman

Many technical writers are fairly empathic people. To be good at our job, we need to care about user experiences, we need to be able to imagine different scenarios and meet different needs. I know that I am sometimes better at understanding the needs of others more than my own. Other peoples needs are interesting puzzles, my own needs can feel more like irritants that get in the way of me doing stuff!

But, it turns out, if you don't honor all the aspects of emotional intelligence you're selling yourself short and creating problems for yourself. As Ramona Hacker points out, too much empathy can sometimes be a barrier to full emotional intelligence. The noise of so much empathy can drown out too many other parts or give the illusion of strong emotional intelligence when there are aspects that need more work.

So often the SMEs we work with want to throw people into the middle of the conversation.

I was talking about Ngombor Community Development Alliance in the Write the Docs Slack recently and someone asked me what Ngombor had to do with documentation.

It was an excellent question as I'd thrown some Ngombor information at a channel without contextualizing. I'd been a terrible technical writer, marketer and organizational storyteller. What did fundraising for a community organization in Uganda have to do with technical writing? For some, it was a logical continuation of a conversation. For others it was baffling to be suddenly thrust into the middle of a conversation where they did not have the context to understand what I was talking about. In the heat of the moment, how would someone tell the difference between me and any random person trying to sell a product?

So often the SMEs we work with want to throw people into the middle of the conversation. They've been working on something for months, maybe years and they just want to display the logical conclusion. It's frustrating. I don't know how many times I've needed to help engineers understand that a little bit of context, a little bit of grounding information at the top of the doc is not patronizing, it's not unnecessarily slowing people down. Context and introductory information helps people (or machines), who are not in the middle of whatever the conversation is, access the meaning of a document. It helps people who might not have the precise words for describing their situation, find their way.

And I must laugh and pause here, and I hope you are laughing too. Most of the world doesn't really play baseball, it's not global terminology! When it comes to jargon, inside baseball is a little inside baseball!

Infodumping is when you provide a whole lot of information all at once. It's a term that's been used for some decades when critiquing literature and has been adopted by autistic communities to refer to our tendencies to excitedly enthuse on a topic.

Documentarians (aka technical writers, content champions and word nerds) are prone to this trait. In some ways technical writing is an ongoing wrestling match with infodumping as we take on vast amounts of information, process and subject matter expertise and transform it into content that can be used and understood with greater ease.

In an increasingly remote world, our non-technical writing colleagues can find our facility for writing things down a little bit overwhelming. It can be especially frustrating for technical writing when even asking questions can trigger overwhelm in others as it floods their brain with new angles and questions. We can feel stuck in a bind where we're simultaneously told to ask questions, but also please don't communicate so much!

This is why when I was putting together the Neurodivergent Quality of Life Prioritization Matrix management of over enthusiastic infodump over chat was one of the first criteria I listed.

In this blog post I share some tips and tricks I find helpful, as well as some advice from fellow Write the Docs peers. We'll never get it perfect, but perfect is never the point.

If you want to jump straight into the Agenda and Minutes Template:

• Create your own copy
• Master document, where you can leave comments and provide feedback

Minutes are important, and not just how we choose to use the finite amount of time we have in life. Minutes are recordings of decisions and discussions that occurred during a meeting. Done right, they are powerful and meaningful. As a technical writer, I've often used an agenda and minutes to drive decision making, make next steps clear and to manage my own enthusiastic use of workplace chat!

I have two strong opinions (aka hot takes? but is it really hot?). One is that technical writers have a vested interested in good meeting minutes and should just start writing them if the minutes are falling short.

I had a great conversation with Kate Mueller on the Not Boring Technical Writer podcast. The actual interview was a lot longer as we got quite carried away, so kudos to the editors for squeezing it down to size.

Connecting permaculture and documentation with Liz Argall

We cover a lot of ground in the episode, including how to help engineers overcome shame that can limit documentation, the glory of the right metrics used the right way and what can happen if you throw yourself into processes passionately. You'll see connections between what we spoke about and my recent Attend to the Work blog post.

One of the bits that didn't make it into the episode was

This essay started as a love letter to mindfully turning up. I wanted to write about the power that comes from turning up a little bit at a time consistently. As I attended to the work of blogging regularly it evolved to be a love letter to processes, structures, systems and their interconnections. This essay gives you a tour of philosophies and metaphors that may feel disconnected at first, but all feed into creating meaningful, effective work while avoiding burnout.

Due to the nature of this essay, I've only done minimal edits while typing. This essay is a love letter after all, and it wouldn't do to over work it!

Let's begin​

Over the last few blog posts, I've shared some resources for mindfully turning up for your docs and for yourself.

If you look at these resources you might get a sense of overwhelm. OMG, there's so much to do and I haven't done it all! It's easy for your mind to shut down and decide, if you can't do it all, what's the point?

If you want to jump straight into Search Term Analysis spreadsheet:

• Create your own copy
• Master document, where you can leave comments and provide feedback

About​

When we talk about content quality, findability is an important factor that extends beyond clean architecture. "Can the user find the data?" is a common question. Can the user find the data if they start with a Google search takes us deeper into this investigation.

At the Write the Docs Conference in Portland this year I gave a lightning talk on "Google Magic!" It showed how and get insight into your documentation in five minutes. Through this approach you can get a clearer understanding of your users and identify the most impactful ways to improve your docs.

This article goes into a bit more detail and provides a template for conducting several kinds of search term analysis.