
STC members are not automatons. Neither their profession nor their association is monolithic in nature. Just as engineering embraces a wide variety of specialization, so does the field of technical communication. As I pointed out before, our specializations tend to be broader in scope: a technical writer rarely, for example, writes only design specifications or testing documentation. Rather, that writer, if he or she is an STC member, is usually well-versed in all phases of system development documentation as well as with marketing or training, for example.
Our strong suit is our ability to quickly your documentation requirements and
do the job as quickly and efficiently as possible. Yes, we are masters of
the written word and how and where that word is published. We tend to be
well-read and confident in our ability to work with anyone, anywhere, at
any time.
We see the trees, the forest, and the fires that often occur during the development of a project. Why? Because technical communication is more than organizing and laying out information attractively. It's more than being able to read a schematic or data flow diagram. We understand engineers and programmers and, of equal importance, we understand those who will use your product. We work with those users, or consumers, of your products and can tell you, in your language, of their needs and issues.
We don't require our staff to be members of STC or any other organization. They are members; members because they care about themselves, their field, and their clients.
That's what STC is about and that's what James River Technical Communications LLC is about. You can only benefit from using us.
The most important value we add is… communication
We care for & about our field and our clients