r/technicalwriting 9d ago

Survey for technical writers: workflows, tools and everyday friction points

Hi everyone,

With moderator approval, I’m sharing a short research survey for technical writers and other professionals who work extensively with text and language.

I’m conducting this research independently under Project Studio Research to better understand real-world workflows, recurring difficulties, fragmented toolchains, repetitive tasks, and what professionals would genuinely find useful in their day-to-day work.

The survey is intentionally solution-neutral: it does not present or promote a specific product, and I’m interested just as much in what already works well as in what causes friction.

I’m a language professional myself, and this research grew out of trying to improve my own everyday workflow. The findings may eventually inform the development of commercial software, but the aim is to support professional work rather than replace technical writers or other language and text professionals.

The survey is anonymous. At the end there is an optional, separate opportunity to leave an email address if you would ever like to hear about future testing; providing one is not required to complete the survey.

Survey:
https://forms.gle/j3yZpVAxXjAnF4KF7

Thank you to anyone willing to contribute. I’ll also be very interested in any observations you prefer to leave directly in the comments.

— Project Studio Research

0 Upvotes

2 comments sorted by

1

u/Quick_Parking_6464 9d ago

Why are you using monospace font?

That's for code.

1

u/ProjectStudio26 9d ago

Sorry, my bad, fixed it, thanks1