Robyn NíConney
writer
I loved being the bridge between our product team and our users at EveryAction and NGP VAN. In the articles below, I was told that the UX of the product should speak for itself. Ideally, help content should be quickly scannable and provide clear steps for success.
The documents I created focused on a value-add perspective, addressing WHY you'd want to use a feature. I also made sure to call attention to any subtleties in a feature that might not be obvious from the UI.
01
This is a typical help article for EveryAction and NGP VAN. Their articles are longer format and are designed for scanability. There is a left-hand navigation element automatically added from the <h2> headers and action phrases are called out with a bold font. Articles are written for fundraising experts, so you will see the use of industry-appropriate terminology.
02
This is another example of a how-to help article. Again, scannability is key here. This help center has a limited editor for formatting articles and there is no ability to customize each page using CSS. The resulting standard is spare and clean.
03
This help article uses many images to help explain more visual concepts. I try to add appropriate images and animated gifs when I can.
04
This help doc guides developers or staff members who are setting up custom variables for professional fundraisers and marketers. We didn't know what level of expertise the audience might have so I tried to make sure it was easy enough for beginners to understand while still giving more experienced developers what they need.
05
This page is a ghostwritten blog post designed to help our clients use a variety of tools together to complete a common task. In this case, it's helping political campaigns organize their donor call time so it's easy to track who has been contacted and who needs a follow-up.