Twitter | Search | |
Search Refresh
Bob Watson, PhD Sep 14
Saw this article mentioned in another thread, but thought it was still worth a mention in case you haven't seen it before (or for a while).
Reply Retweet Like
Documentation Demon Sep 14
Replying to @bobwatsonphd
just came here to say "by catch you don't mean broadcast on twitter?" Well preempted.
Reply Retweet Like
Bob Watson, PhD Sep 10
This photo captures so many cool aspects about * Amazing audience * Great speakers * Interesting topics * Live captioning * Live streaming * Live tweets
Reply Retweet Like
Bob Watson, PhD Sep 9
Well, I might as well just admit it. I'm not going to get much done as long as the live tweets are coming out of the conference.
Reply Retweet Like
Bob Watson, PhD Aug 19
A great and technical article on how to start tracking the value of informational content to the sales process. Could this work for ? Sure, just think like a marketer and know the customer journey to your product.
Reply Retweet Like
Bob Watson, PhD Aug 17
Found this post on "generating" API documentation, which got me thinking about the verb(s) developers use to describe documentation authoring vs. the verbs(s) uses to and what that means.
Reply Retweet Like
Bob Watson, PhD Aug 14
I love reading about how technical content is considered part of the customer experience and supports product success. The real story is here:
Reply Retweet Like
Bob Watson, PhD Aug 6
I found some interesting scholarly articles about that have a lot of takeaways for and everyone who for developers. Ironically, none of them mention tech comm.
Reply Retweet Like
Bob Watson, PhD Aug 6
If you want to know how and why developers search API docs, describes a case study that asked 27 Googlers those questions (and others).
Reply Retweet Like
Bob Watson, PhD Jul 24
So, what can we call documentation for a similar effect? Most of the reader's goals WRT documentation also occur offline. Solutions? Success Augmentation? Whachagot ?
Reply Retweet Like
Bob Watson, PhD Jul 11
“Stop thinking in terms of, “What content should we create?” and instead think about “What content do people want, need, and how does it support our business?”” Your audience knows better than you. Listen 2 them! True for and all who
Reply Retweet Like
Bob Watson, PhD Jul 3
“If your boss is asking you to quantify the value of your work, you need to understand that your work indeed has no value. Not at that company. Not with that boss.” Applies to , too.
Reply Retweet Like
Bob Watson, PhD Jun 25
If wants to usability test their documentation, here are some tips for setting up a testing space. It doesn’t have to be complicated or expensive.
Reply Retweet Like
Bob Watson, PhD Jun 13
I love it when devs talk about documentation. needs to be alert for these moments to: - help answer their questions - share tips and tricks - meet allies for future conversations - learn more about their audience
Reply Retweet Like
Bob Watson, PhD May 12
Finally had a chance to reflect on the PDX conference. In a few days, I’ll work up the nerve to watch the video of my talk and see what I can learn for next time.
Reply Retweet Like
Bob Watson, PhD May 9
While I was able to attend this year, I want to thank all the prolific tweeters for their efforts and tell them I’ve appreciated their work in the past when I’ve not been able to attend
Reply Retweet Like
Bob Watson, PhD May 8
The secret is out now! Had a great time at in PDX! What a great group of documentarians!!
Reply Retweet Like
Stoplight May 8
How to determine how much you will need to write based on your audience's tendencies
Reply Retweet Like
Amber Matz May 8
I love this description of 3 potential preferred coding styles of your API’s audience by
Reply Retweet Like
Bob Watson, PhD Mar 2
And please include quality documentation in your budget. You can thank me later.
Reply Retweet Like