| |
|
October 14, 2010
|
|
4:23 am
|
KaranSachar:
|
Nice & Sober! RT @samarthav: My #Adobe blog has a brand new theme now! Your opinion? http://bit.ly/7yoj1i #techcomm #tcchat |
|
9:41 am
|
robocolumn:
|
Cool look too RT @samarthav: My #Adobe blog has a new theme! I love the fresh look. Your opinion? http://bit.ly/7yoj1i #techcomm #tcchat |
|
2:30 pm
|
TC_Chat:
|
It's #tcchat day already! Join us at 9am PT/Noon ET today for Managing Collaboration in Doc Projects with @larry_kunz #techcomm |
|
2:30 pm
|
2moroDocs:
|
It's #tcchat day already! Join us at 9am PT/Noon ET today for Managing Collaboration in Doc Projects with @larry_kunz |
|
2:33 pm
|
iluvMarthasVY:
|
RT @2moroDocs: It's #tcchat day already! Join us at 9am PT/Noon ET today for Managing Collaboration in Doc Projects with @larry_kunz |
|
3:10 pm
|
cebrouillard:
|
RT @TC_Chat: It's #tcchat day already! Join us at 9am PT/Noon ET today for Managing Collaboration in Doc Projects with @larry_kunz #techcomm |
|
3:21 pm
|
2moroDocs:
|
@cebrouillard Thanks for the RT about today's #tcchat! |
|
3:30 pm
|
ChatSchedule:
|
30 minutes until #tcchat starts - RT if you'll be here |
|
3:32 pm
|
TC_Chat:
|
Re today's #tcchat, look at @larry_kunz presentation: Managing Doc Projects in a Collaborative World http://slidesha.re/9SafeN . #techcomm |
|
3:33 pm
|
2moroDocs:
|
Re today's #tcchat, look at @larry_kunz presentation: Managing Doc Projects in a Collaborative World http://slidesha.re/9SafeN |
|
3:33 pm
|
TC_Chat:
|
30 mins to #tcchat! #techcomm |
|
3:34 pm
|
2moroDocs:
|
RT @ChatSchedule: 30 minutes until #tcchat starts - RT if you'll be here |
|
3:50 pm
|
ChatSchedule:
|
10 minutes until #tcchat starts - RT if you'll be here |
|
3:53 pm
|
juliov27612:
|
RT @ChatSchedule: 10 minutes until #tcchat starts - RT if you'll be here |
|
3:55 pm
|
larry_kunz:
|
Looking forward to having a great conversation about your #techcomm experiences & best practices #tcchat |
|
3:55 pm
|
2moroDocs:
|
5 mins to start of #tcchat S1. To my followers: I'll be tweeting much over the next hour re the chat. |
|
3:58 pm
|
juliov27612:
|
twubs doesn't seem to want to behave today. I'll have to be better about the #tcchat hashtag. |
|
3:58 pm
|
TC_Chat:
|
#tcchat starts in a few minutes. Join in! Talking about Managing Collaboration in Doc Projects with @larry_kunz #techcomm |
|
3:59 pm
|
lrmeyer747:
|
RT @ChatSchedule: 10 minutes until #tcchat starts - RT if you'll be here |
|
4:00 pm
|
juliov27612:
|
RT @TC_Chat: #tcchat starts in a few minutes. Join in! Talking about Managing Collaboration in Doc Projects with @larry_kunz #techcomm |
|
4:01 pm
|
2moroDocs:
|
@juliov27612 Twubs hasn't been working the past couple of days. HootSuite, tweetdeck, tweetchat, http://wthashtag.com/Tcchat #tcchat |
|
4:01 pm
|
TC_Chat:
|
@juliov27612 Twubs hasn't been working the past couple of days. HootSuite, tweetdeck, tweetchat, http://wthashtag.com/Tcchat #tcchat |
|
4:01 pm
|
2moroDocs:
|
Welcome to today?s #tcchat! Topic: Managing Collaboration in Documentation Projects, with guest Larry Kunz @larry_kunz #tcchat |
|
4:02 pm
|
2moroDocs:
|
I?d like to welcome Larry, who is a project manager, STC Fellow, and recipient of the 2010 STC President?s Award. #tcchat |
|
4:02 pm
|
2moroDocs:
|
Larry, I appreciate your taking time from your busy schedule today to discuss this timely topic. #tcchat |
|
4:02 pm
|
2moroDocs:
|
Reminders: please don?t use #techcomm tag. It will overwhelm it. Add #tcchat to your tweets. Thx! Also, no proprietary info! |
|
4:02 pm
|
larry_kunz:
|
@2moroDocs Thanks, Julie. Pleasure to be here, and I'm looking forward to a good chat today. #tcchat |
|
4:04 pm
|
PattyBlount2:
|
#tcchat Good afternoon from Long Island. |
|
4:04 pm
|
2moroDocs:
|
How about starting with a roll call? I'm here in Seattle - #tcchat |
|
4:04 pm
|
hemantbaliwala:
|
Pune, India :) #tcchat |
|
4:05 pm
|
juliov27612:
|
Here in NC #tcchat |
|
4:06 pm
|
ermphd:
|
Greetings allfrom DFW Hello @2moroDocs #TCchat |
|
4:06 pm
|
2moroDocs:
|
Sorry - I'm having some tech difficulties. Will post Q1 #tcchat |
|
4:06 pm
|
2moroDocs:
|
Let?s begin! We?ll cover 4 main topics: sources of info, challenges, planning, and community #tcchat Here comes Q1. |
|
4:07 pm
|
2moroDocs:
|
Q1: Sources: Who or what are sources of info for your docs? Customers? Developers? SMEs? #tcchat |
|
4:07 pm
|
rjacquez:
|
Two most excellent Tweet Chats going on now: #lrnchat http://bit.ly/dmgjjF and #tcchat http://bit.ly/dcsxai |
|
4:09 pm
|
juliov27612:
|
A1: All of the above. Also previous experience and research comes into play. #tcchat |
|
4:09 pm
|
PattyBlount2:
|
#tcchat q1: reqs docs first, followed by developers. I rarely have customer contact, which hoping social media will change. |
|
4:09 pm
|
ermphd:
|
A1 System help files, Vendor info in devices, Govt info on regs #TCchat |
|
4:09 pm
|
2moroDocs:
|
All - I'm not seeing anything, so sorry for the delay. Will keep trying! #tcchat |
|
4:10 pm
|
juliov27612:
|
A1: Social media eases customer involvement. May even change requirements as involvement increases. #tcchat |
|
4:10 pm
|
hemantbaliwala:
|
Q1: FDD, and then everyone else #tcchat |
|
4:11 pm
|
juliov27612:
|
@2moroDocs You're coming through, but things appear slow. #tcchat |
|
4:11 pm
|
larry_kunz:
|
For Q1: Do any of you get info from other internal sources like Tech Support & Marketing? #tcchat |
|
4:11 pm
|
robocolumn:
|
A1. All of them plus Support Desk and other internal users. Everyone has a view on the docs usability #tcchat |
|
4:12 pm
|
juliov27612:
|
A1. In past experience, tech support and marketing rarely get involved until late in game. Changing now? #tcchat |
|
4:12 pm
|
robocolumn:
|
@larry_kunz Ugghh! Marketing? LOL! #tcchat |
|
4:12 pm
|
PattyBlount:
|
@larry_kunz q1 #tcchat No formal process; I usually explore Support's tech doc library myself for bits that should be in my doc. |
|
4:13 pm
|
juliov27612:
|
A1. I think you see tech support involved after first release of product. #tcchat |
|
4:13 pm
|
hemantbaliwala:
|
Well at times, we get good inputs from the technical training team. #tcchat |
|
4:14 pm
|
2moroDocs:
|
@juliov27612 I'm not seeing anything on the #tcchat tag anyplace I look, but will keep trying. Go ahead and discuss info! |
|
4:14 pm
|
juliov27612:
|
A1. I see Larry's point, though. Better content strategy for all players to be involved. #tcchat |
|
4:14 pm
|
ermphd:
|
A1 Our TS Agents send add/chg requests to the gal who updates the #Adobe #AirHelp module #TCchat |
|
4:15 pm
|
PattyBlount:
|
@juliov27612 #tcchat Agreed. Cross-functional. |
|
4:15 pm
|
juliov27612:
|
@2moroDocs I'm seeing it in tweetdeck. #tcchat |
|
4:15 pm
|
lrmeyer747:
|
Our doc team held regular meetings with support engineers, who shared the most common issues they heard from customers. #tcchat |
|
4:15 pm
|
MikeStarrWriter:
|
A1: For most software docs, I'm the source... I install the software and dope it out with a few questions to SMEs for clarification.#tcchat |
|
4:16 pm
|
juliov27612:
|
Trainers could be a valuable input too. Especially if a new product has basis in an old one. #tcchat |
|
4:16 pm
|
lrmeyer747:
|
We also had good input from training -- sometimes we could sit in on classes and hear customer questions. #tcchat |
|
4:16 pm
|
PattyBlount2:
|
Apologies all on #tcchat. Tweetdeck does not like my @pattyblount2 account for some reason and keeps defaulting back to @pattyblount. |
|
4:16 pm
|
robocolumn:
|
@juliov27612 Absolutlety. The more the merrier just so long as they understand their doc standards / styles may be different. #tcchat |
|
4:16 pm
|
larry_kunz:
|
Tech support. Training (thanks, @hemantbaliwala). But not marketing, huh? (I heard that laugh, @robocolumn) #tcchat |
|
4:17 pm
|
juliov27612:
|
@MikeStarrWriter That's one way, but doesn't that make it more difficult than to understand user's view? #tcchat |
|
4:17 pm
|
juliov27612:
|
@robocolumn Yes, as much input as possible given the schedule. #tcchat |
|
4:18 pm
|
2moroDocs:
|
@juliov27612 I'll check there. In the meantime, everyone feel free to discuss things. I'll put out Q2 as well. #tcchat |
|
4:18 pm
|
2moroDocs:
|
Q2: What do you see as your biggest challenge w/collaboration: editing, accuracy, localization, tracking, or something else? #tcchat |
|
4:18 pm
|
juliov27612:
|
All: Julie still having tech issues. She'll be in as she can. #tcchat |
|
4:18 pm
|
ermphd:
|
Our help files were4 orginally developed by marketing and that has been part of the problem , feature oriented not task #TCchat |
|
4:19 pm
|
PattyBlount2:
|
#tcchat Q2: biggest challenge is collaborating and getting access to product. |
|
4:19 pm
|
juliov27612:
|
I suppose a valid question is how to distill all the input into the "truth"? #tcchat |
|
4:19 pm
|
ermphd:
|
Q2 in our case keeping up with the pace of change #TCchat |
|
4:20 pm
|
juliov27612:
|
A2: I think accuracy is biggest challenge. #tcchat |
|
4:20 pm
|
2moroDocs:
|
Yea! I can see things now. A 30-tweet backlog. #tcchat Thx @juliov27612, @ermphd @pattyblount2 |
|
4:20 pm
|
robocolumn:
|
A2: Good question. Review comments is a common issue for us. Oh and translating tech speak into something comprehensible #tcchat |
|
4:20 pm
|
mojoneill:
|
(having problems with twubs on all browsers. May have to gimp along as best I can via tweetdeck. ) #tcchat |
|
4:21 pm
|
hemantbaliwala:
|
For me different perspectives about users by different teams makes things lil complicated. #tcchat |
|
4:21 pm
|
larry_kunz:
|
@juliov27612 Yes, good question. Would u say "truth" encompasses relevance and findability as well as accuracy? Other things too? #tcchat |
|
4:21 pm
|
juliov27612:
|
A2: Localization may not be as big a concern once all the sources are incorporated. Still need to know who has final say. #tcchat |
|
4:22 pm
|
ermphd:
|
@@juliov27612 A good point #tcchat |
|
4:22 pm
|
lrmeyer747:
|
A couple of collab.challenges: Deadlines (differing expectations of what can be done when), what constitutes "doc" vs. "marcomm" #tcchat |
|
4:22 pm
|
juliov27612:
|
@hemantbaliwala Doesn't the product manager have final say on user perspective? #tcchat |
|
4:23 pm
|
ermphd:
|
In our case for customer facing marketing drives the train #TCchat |
|
4:23 pm
|
kemulholland:
|
A2 trying to implement collaborative practices & let ppl know that I'm happy to fix broken stuff is a challenge 4 this new kid #tcchat |
|
4:23 pm
|
PattyBlount:
|
@larry_kunz #tcchat Completeness is a big challenge. How do you know when you've captured all info? |
|
4:23 pm
|
juliov27612:
|
@larry_kunz I think that "truth" is hampered if relevance and findability are somehow thwarted from original intent. #tcchat |
|
4:23 pm
|
mojoneill:
|
@juliov27612 doesn't the USER have final say on user perspective? #tcchat |
|
4:23 pm
|
hemantbaliwala:
|
@juliov27612 Definately he does have... but till then it gets confusing... #tcchat |
|
4:23 pm
|
2moroDocs:
|
For accuracy, is it related to access time to SMEs? Are they less avail than b4. Any ideas for addressing that? #tcchat |
|
4:24 pm
|
juliov27612:
|
@lrmeyer747 Marcomm is part of the doc. Just a different view. #tcchat |
|
4:24 pm
|
davkow:
|
Late to the #tcchat session today. Topic: "Managing Collaboration in Documentation Projects." @2moroDocs |
|
4:25 pm
|
juliov27612:
|
@mojoneill User is final arbiter, but the product manager should have that ear. #tcchat |
|
4:25 pm
|
robocolumn:
|
@PattyBlount In truth I don't think I'm ever 100% sure I've captured 100%. Functional specs, presentations only go so far. #tcchat |
|
4:25 pm
|
2moroDocs:
|
@davkow Thx for coming by. There have been some tech difficulties #tcchat Good disc! |
|
4:25 pm
|
juliov27612:
|
@2moroDocs Give them smaller bits of information to check. Take some tech responsibility on self. Pray. :D #tcchat |
|
4:26 pm
|
juliov27612:
|
@PattyBlount @larry_kunz Won't be sure you've captured it all until customer sees it. #tcchat |
|
4:26 pm
|
larry_kunz:
|
@PattyBlount Good point about completeness. Is completeness any less of a concern when you can make easy/frequent updates to doc? #tcchat |
|
4:26 pm
|
ermphd:
|
A2 My SMEs are with easy reach, but often very busy #TCchat |
|
4:27 pm
|
juliov27612:
|
@robocolumn Agree that you're never 100% sure. Even customer may not know all the gaps. #tcchat |
|
4:27 pm
|
2moroDocs:
|
Q3: Re accuracy, what challenges are there to make sure your existing documentation is still useful and current? #tcchat |
|
4:27 pm
|
PattyBlount2:
|
@robocolumn #tcchat Yes, same problem here. Wish I could corral all SMEs into a room for a week and do a doc sprint. |
|
4:27 pm
|
lrmeyer747:
|
We found that reviewers were more receptive to getting smaller pieces to review. #tcchat |
|
4:27 pm
|
robocolumn:
|
@PattyBlount I ensure I actively look for all UI elements (e.g. popup menus) when documenting. Still some get through the net :-( #tcchat |
|
4:28 pm
|
kemulholland:
|
A2 accuracy & access 2 experts - give your SME 1 topic or para at a time, often get tech review done same day u write it. #tcchat |
|
4:28 pm
|
ermphd:
|
@larry_kunz Larry, that's why we like #AirHelp w easy updates #tcchat |
|
4:28 pm
|
juliov27612:
|
A3: I think reconciling the original user stories with the actual user experience. #tcchat |
|
4:28 pm
|
robocolumn:
|
@juliov27612 I customers don't know about the gaps that's more acceptable I guess. #tcchat |
|
4:29 pm
|
kemulholland:
|
getting technical feedback = eating an elephant. Small bites, lots of them. #tcchat |
|
4:29 pm
|
PattyBlount2:
|
@larry_kunz #tcchat Completeness was a concern when we had to wait for next release to fix issues. HTML lets us fix probs outside of prod. |
|
4:29 pm
|
juliov27612:
|
@kemulholland Not suggesting one para at a time. But maybe 2 or 3 topics. Spread out over time for full document. #tcchat |
|
4:29 pm
|
ermphd:
|
A3 Getting marketing to think out of the box, like putting sims in the doc #TCchat |
|
4:29 pm
|
2moroDocs:
|
@juliov27612 Sometimes I would send off a few paragraphs or topics instead of an entire giant file. That seemed 2 work #tcchat |
|
4:29 pm
|
lrmeyer747:
|
Can be challenging to determine if existing doc is useful/current while documenting new features under tight deadlines. #tcchat |
|
4:30 pm
|
PattyBlount2:
|
@robocolumn #tcchat You have prod. access then? |
|
4:30 pm
|
2moroDocs:
|
Also, I wld address their comm style. Some wanted written. Sometimes a quick mtg worked best. Depends on SME #tcchat |
|
4:30 pm
|
juliov27612:
|
@PattyBlount2 Yes, technology today allows more frequent updates. If the employer willing to pay the price. #tcchat |
|
4:31 pm
|
kemulholland:
|
@juliov27612 If I'm updating a topic & only one para changes, that's all I ask my SME to look over - but I do provide context. #tcchat |
|
4:31 pm
|
juliov27612:
|
@lrmeyer747 Hopefully you get some of that feedback as you go. Real problem becomes getting it all in. Prioritization of content. #tcchat |
|
4:31 pm
|
2moroDocs:
|
Not seeing anything again --- #tcchat grrr..... |
|
4:31 pm
|
larry_kunz:
|
@lrmeyer747 Yes....With "mini" reviews & focus on new features, it's hard to keep big picture in mind. Any ideas on how to do that? #tcchat |
|
4:31 pm
|
robocolumn:
|
A3: @PattyBlount2 makes a good point. The output type and their deliverable time scales can be an issue (e.g. CHM files in a build). #tcchat |
|
4:32 pm
|
juliov27612:
|
@kemulholland Good working plan. Better than giving them entire doc for 1 para. :D #tcchat |
|
4:33 pm
|
juliov27612:
|
@larry_kunz Mini reviews have always been challenging. Maybe paint a scenario for the content to provide context? #tcchat |
|
4:34 pm
|
2moroDocs:
|
Q4: What about tracking? How do you track status and checkpoints when the project plan is fluid (as in agile)? #tcchat |
|
4:34 pm
|
kemulholland:
|
key thing 2 remember is...NOBODY WANTS TO READ IT! Sorry but it's true. Minimize what u ask of reviewers. #tcchat |
|
4:34 pm
|
ermphd:
|
@juliov27612 I agree with you and Karen, context is keuy to saving SME time and energy #tcchat |
|
4:35 pm
|
gdevore:
|
If you add pictures to your docs both you and your users will know when they are out of date. Really hard with just text #tcchat |
|
4:35 pm
|
2moroDocs:
|
@kemulholland True. I've always worked around their schedules as best I could. Try to use up as little time as possible. #tcchat |
|
4:35 pm
|
juliov27612:
|
A4: Old methods still work. Keep track in a spreadsheet. That sort of thing. #tcchat |
|
4:35 pm
|
lrmeyer747:
|
@larry_kunz To avoid losing big picture -- in review memos, I try to describe how new features are related to existing functionality #tcchat |
|
4:35 pm
|
ermphd:
|
@kemulholland Brovo Karen, Its hard to accept the reality that nobody wants to read what we write, lol #tcchat |
|
4:36 pm
|
robocolumn:
|
@PattyBlount2 We can build the online help content at any time and publish to the server. Offline help = more problematic. #tcchat |
|
4:36 pm
|
2moroDocs:
|
One option I've seen: gather everyone in a room for an hour & walk thru main tech issues in docs. A while ago, tho. #tcchat |
|
4:37 pm
|
juliov27612:
|
@ermphd @kemulholland I've always known that. Even as a customer. :D #tcchat |
|
4:37 pm
|
ermphd:
|
@gdevore Adding pics and sims is what makes the doc more accessible to busy users and reviewers #tcchat |
|
4:37 pm
|
PattyBlount2:
|
@2moroDocs #tcchat Yes, would love to gather in a room for all content dev, but there's no time. |
|
4:38 pm
|
juliov27612:
|
@2moroDocs Been there and done that. Problem is that some folks lose focus in larger group. #tcchat |
|
4:38 pm
|
2moroDocs:
|
Going 2 jump 2 new section. #tcchat |
|
4:38 pm
|
PattyBlount:
|
@2moroDocs q4. #tcchat I'll let you know when I figure that out 1 |
|
4:38 pm
|
larry_kunz:
|
In agile SMEs are already focused on what you ask them to review - vs. reviewing stuff they worked on months ago. Agree? #tcchat |
|
4:39 pm
|
2moroDocs:
|
Q5: Today, doc strategy needed to create, deliver, & govern docs ? not just doc plan. What needs to be addressed to govern? #tcchat |
|
4:39 pm
|
lrmeyer747:
|
I still use spreadsheets to track review info and schedules, but I make them as simple as possible, and easily printable. #tcchat |
|
4:39 pm
|
juliov27612:
|
@larry_kunz They should be. However, that may not be reality in development cycle. #tcchat |
|
4:40 pm
|
2moroDocs:
|
@juliov27612 That would definitely be a concern #tcchat |
|
4:40 pm
|
jenisecook:
|
RT @rjacquez: Two most excellent Tweet Chats going on now: #lrnchat http://bit.ly/dmgjjF and #tcchat http://bit.ly/dcsxai |
|
4:41 pm
|
ermphd:
|
@2moroDocs Govern? please define #tcchat |
|
4:41 pm
|
juliov27612:
|
A5: One thing that we tend to forget is the people in the work flow. Have to be realistic about the stress of the shorter cycles. #tcchat |
|
4:41 pm
|
robocolumn:
|
A5: Personally feel some HATs fail in the tools that allow you to govern doc status. #tcchat |
|
4:42 pm
|
juliov27612:
|
@ermphd I think manage or direct would have been better words than govern. :D #tcchat |
|
4:42 pm
|
2moroDocs:
|
down again. will keep at it #tcchat |
|
4:42 pm
|
juliov27612:
|
Govern sounds like politics in #tcchat LOL |
|
4:43 pm
|
robocolumn:
|
@juliov27612 LOL! Spoken like a true technical communicator. #tcchat |
|
4:43 pm
|
ermphd:
|
@juliov27612 Right on. Manage perhaps? #tcchat |
|
4:43 pm
|
juliov27612:
|
@robocolumn I bow humbly to be acknowledged as such. #tcchat |
|
4:44 pm
|
ermphd:
|
@juliov27612 your last just came, So we agree on manage not govern :) #tcchat |
|
4:44 pm
|
2moroDocs:
|
@ermphd I'd say manage things like UGC. @larry_kunz - other items? #tcchat |
|
4:45 pm
|
juliov27612:
|
A5: Creating leaner workflows is part of the challenge. #tcchat |
|
4:47 pm
|
juliov27612:
|
A5: If there's no clear, concise process, you have to define one to succeed nowadays. (forgot tag) #tcchat |
|
4:47 pm
|
larry_kunz:
|
@juliov27612 "Govern" not exactly = "manage." Search on 'governance' in comment on this article by @rahelab: http://bit.ly/aoDdBQ #tcchat |
|
4:48 pm
|
2moroDocs:
|
@ermphd @juliov27612 Sounds good to me. #tcchat |
|
4:48 pm
|
larry_kunz:
|
@2moroDocs Governance also encompasses things like who owns what content, who has final signoff. #tcchat |
|
4:49 pm
|
juliov27612:
|
@larry_kunz That's why I also suggested direct. Maybe even conduct (in terms of orchestra) might work. :D #tcchat |
|
4:51 pm
|
kemulholland:
|
@juliov27612 Agreed - doc dev practices must keep pace with product dev practices or the mismatch causes doc mgmt/dev probs. #tcchat |
|
4:51 pm
|
2moroDocs:
|
@juliov27612 With all new considerations (UGC, short dev cycles), is it more diff to plan for than doc plans of old? #tcchat |
|
4:52 pm
|
juliov27612:
|
@larry_kunz Correct, but the word govern just sets me into ickiness (considering the current situation in DC). #tcchat |
|
4:52 pm
|
robocolumn:
|
@2moroDocs Generally I'd say yes. There's still ignorance about the doc function and what is required to meet it. #tcchat |
|
4:53 pm
|
juliov27612:
|
@2moroDocs Old doc plans were centered on the deliverable structure. New plans must also consider impact on all stakeholders. #tcchat |
|
4:53 pm
|
lrmeyer747:
|
@juliov27612 Agree -- "clear" and "concise" are critical attributes of any process! #tcchat |
|
4:54 pm
|
2moroDocs:
|
@larry_kunz Thx for this link - #tcchat |
|
4:54 pm
|
juliov27612:
|
@2moroDocs Plans should include as many stakeholder as possible in all phases of content lifecycle. #tcchat |
|
4:55 pm
|
ermphd:
|
@juliov27612 And plans must be realistic in tems of timelines #tcchat |
|
4:55 pm
|
juliov27612:
|
@lrmeyer747 Agree. Have to build it, if it doesn't already exist. Rail against the machine! #tcchat |
|
4:55 pm
|
2moroDocs:
|
@robocolumn Makes sense. There's always that to contend with. #tcchat |
|
4:55 pm
|
larry_kunz:
|
I think the doc plan is now subordinate to the content strategy. It defines the tactics for carrying out the strategy. #tcchat |
|
4:55 pm
|
juliov27612:
|
@ermphd Yes. Schedule is always a consideration. Have to prioritize appropriately and indicate risks. #tcchat |
|
4:56 pm
|
lrmeyer747:
|
@larry_kunz re: focus -- even in agile, I like provide a link between new & existing to test my own understanding #tcchat |
|
4:56 pm
|
juliov27612:
|
@larry_kunz Exactly! #tcchat |
|
4:57 pm
|
2moroDocs:
|
Running out of time. Quick ques: what new info must be governed/managed? UGC? What else? #tcchat |
|
4:57 pm
|
juliov27612:
|
#tcchat Doc plan should always be the tactical implementation of the strategy. |
|
4:58 pm
|
juliov27612:
|
@2moroDocs Too much to list in 140. Product feedback, previous unresolved reviews, lots of stuff. #tcchat |
|
4:59 pm
|
kemulholland:
|
that said, @larry_kunz - if u r hired to stanch the bleeding, u worry abt content strat l8r. Sometimes we're the EMS. #tcchat |
|
4:59 pm
|
juliov27612:
|
Gotta run. Great discussion (I needed it). Have a great week all. #tcchat |
|
5:00 pm
|
2moroDocs:
|
@juliov27612 stakeholders = users, dev, customers, world at large ? More stakeholders than in yrs past? #tcchat |
|
5:00 pm
|
lrmeyer747:
|
Working with UGC could be a discussion topic all by itself! It raises many new questions. #tcchat |
|
5:01 pm
|
ermphd:
|
@juliov27612 Good synthesis Strategy drives the doc plan #tcchat |
|
5:01 pm
|
2moroDocs:
|
@juliov27612 Thank you so much for attending - esp with all the tech difficulties! #tcchat |
|
5:01 pm
|
larry_kunz:
|
@kemulholland Very true. When up to your neck in alligators, you don't care that your original goal was to drain the swamp. #tcchat |
|
5:01 pm
|
kemulholland:
|
@2moroDocs Can we conclusively identify those who are NOT stakeholders? #tcchat |
|
5:01 pm
|
juliov27612:
|
@2moroDocs Absolutely more stakeholders. In past it was throw it over the wall. #tcchat |
|
5:01 pm
|
2moroDocs:
|
It is 10:00 here, so the scheduled hour is up. Thank you all for coming, and for sticking around thru all the tech problems 2day! #tcchat |
|
5:02 pm
|
juliov27612:
|
@2moroDocs It was fun! #tcchat |
|
5:02 pm
|
2moroDocs:
|
I'll stay around if anyone wants to continue discussion - #tcchat |
|
5:03 pm
|
larry_kunz:
|
Thanks, everyone, for a great conversation! #tcchat |
|
5:03 pm
|
2moroDocs:
|
@lrmeyer747 That's on the schedule! UGC is next week's topic. Was the top vote-getter in the poll. #tcchat |
|
5:04 pm
|
2moroDocs:
|
@kemulholland I wouldn't think so. In this day and age, have to assume anyone in the world is. Anyone can make a video & upload it. #tcchat |
|
5:04 pm
|
lrmeyer747:
|
@2moroDocs Cool; thanks. I will try not to miss that one. #tcchat |
|
5:05 pm
|
2moroDocs:
|
@larry_kunz Thank you, Larry, for being our guest today and suggesting this topic! #tcchat |
|
5:05 pm
|
kemulholland:
|
thx, @2moroDocs, for moderating. & everyone else, thx 4 sharing ur insights! #tcchat |
|
5:06 pm
|
lrmeyer747:
|
@2moroDocs thanks for another great #tcchat session. |
|
5:07 pm
|
larry_kunz:
|
@2moroDocs It was my pleasure. It was a very, very productive hour! #tcchat |
|
5:08 pm
|
2moroDocs:
|
@kemulholland Thx for participating! #tcchat |
|
5:09 pm
|
2moroDocs:
|
@lrmeyer747 Thank you! Appreciate your dropping by - #tcchat |
|
5:10 pm
|
2moroDocs:
|
@robocolumn Thanks for joining in today! Appreciate your participation - #tcchat |
|
5:11 pm
|
2moroDocs:
|
@ermphd Thanks, Ed! Glad you could stop by #tcchat today! |
|
5:14 pm
|
2moroDocs:
|
I hope that you all didn't have as many tech problems as I did. If you did, could you please let me know 4 planning purposes? Thx! #tcchat |
|
5:58 pm
|
2moroDocs:
|
@rjacquez Thanks for the #tcchat mention! |
|
7:17 pm
|
2moroDocs:
|
@jenisecook @rjacquez @cebrouillard @iluvMarthasVY @ChatSchedule Thx for sharing info & announcements re #tcchat today! |
|
7:23 pm
|
2moroDocs:
|
@larry_kunz, @juliov27612 @pattyblount2 @lrmeyer747 @kemulholland Thanks for participating in today's #tcchat S1 - |
|
7:26 pm
|
2moroDocs:
|
@hemantbaliwala @robocolumn @gdevore @davkow @MikeStarrWriter @ermphd @rjacquez Thx 4 dropping by & participating in 2day's #tcchat! |
|
7:31 pm
|
2moroDocs:
|
If I'm not mistaken, folks attended S1 of #tcchat from various locations around the world. Thanks for dropping by! |
|
7:32 pm
|
PattyBlount2:
|
@2moroDocs As always, thanks for all you do to coordinate such a feat! #tcchat |
|
7:33 pm
|
2moroDocs:
|
Transcripts for S1 of today's #tcchat. http://bit.ly/d3zuLL Will post S2 later on. |
|
7:33 pm
|
TC_Chat:
|
Transcripts for S1 of today's #tcchat. http://bit.ly/d3zuLL Will post S2 later on. |
|
8:04 pm
|
KnowledgeBishop:
|
Later today, join host @2moroDocs for session 2 of #TCchat: The topic - Collaboration and #Techcomm. Don't miss it! |
|
8:07 pm
|
brandleadership:
|
RT @KnowledgeBishop: Later today, join host @2moroDocs for session 2 of #TCchat: The topic - Collaboration and #Techcomm. Don't miss it! |
| |
|
October 15, 2010
|
|
12:37 am
|
2moroDocs:
|
Can it be? Only a short time b4 #tcchat S2 begins. Topic: Managing Collaboration in Doc Projects #techcomm 7pm PT, Noon GMT+10 |
|
12:37 am
|
TC_Chat:
|
Can it be? Only a short time b4 #tcchat S2 begins. Topic: Managing Collaboration in Doc Projects #techcomm 7pm PT, Noon GMT+10 |
|
12:39 am
|
mojoneill:
|
@2moroDocs Woot! Psyched for the chat. Hoping for fewer tech problems! #tcchat #techcomm |
|
12:39 am
|
mojoneill:
|
@2moroDocs ...errr...tech problems on my end, that is. #tcchat #techcomm |
|
12:42 am
|
2moroDocs:
|
@mojoneill I hear ya! I had a few myself earlier. S2 should b better. :) #tcchat |
|
1:05 am
|
sarahmaddox:
|
I'm at #tcchat in Sydney. Hallo all. |
|
1:09 am
|
roseacea:
|
@sarahmaddox Hi Sarah, I'm here too. #tcchat |
|
1:15 am
|
2moroDocs:
|
Hi @roseacea and @sarahmaddox! I thought it's in another hour, but I'm game to start now if you are! #tcchat. Hang on a sec- |
|
1:15 am
|
2moroDocs:
|
@mojoneill Do you have time now for #tcchat? |
|
1:16 am
|
sarahmaddox:
|
@cabowman @roseacea #tcchat Rose suggested that we're an hour early, because of daylight savings time here in Sydney. |
|
1:17 am
|
mojoneill:
|
I'm game if you are.
#tcchat |
|
1:17 am
|
sarahmaddox:
|
@2moroDocs Hallo :) We changed our clocks here down under - daylight savings time in summer #tcchat |
|
1:17 am
|
mojoneill:
|
fyi: twubs isn't working for me, so I'm using http://tweetchat.com/room/tcchat
#tcchat |
|
1:19 am
|
sarahmaddox:
|
@mojoneill Hallo Michael! #tcchat |
|
1:19 am
|
2moroDocs:
|
@sarahmaddox @cabowman @roseacea Oh. I was wondering about time changes coming up, did I miss something? #tcchat |
|
1:19 am
|
mojoneill:
|
Sara! How's it going? I've been having some fantastic convos with some of your colleagues in SF. :)
#tcchat |
|
1:19 am
|
2moroDocs:
|
I'm going to start with the questions we discussed earlier. So, here comes Q1 #tcchat |
|
1:21 am
|
2moroDocs:
|
@sarahmaddox Did they just change? Ours change at the end of the month, I think. #tcchat |
|
1:21 am
|
2moroDocs:
|
Here goes - #tcchat |
|
1:22 am
|
2moroDocs:
|
Re Collaboration in Doc Projects, we covered 4 main topics: sources of info, challenges, planning, and community #tcchat |
|
1:23 am
|
2moroDocs:
|
Here's link to preso by Larry Kunz: Managing Doc Projects in a Collaborative World http://slidesha.re/9SafeN #tcchat |
|
1:23 am
|
sarahmaddox:
|
@mojoneill Oh great! I love the team in SF. Been there a couple of times. Lucky me! #tcchat |
|
1:24 am
|
2moroDocs:
|
Q1: Sources: Who or what are sources of info for your docs? Customers? Developers? SMEs? #tcchat |
|
1:25 am
|
2moroDocs:
|
A1: earlier, ppl said docs, dev, tech support, training, customers (rarely), some marketing #tcchat |
|
1:25 am
|
mojoneill:
|
A1: Developers, SMEs ideally. More often it's the software itself. Sometimes an internal dev wiki. #tcchat |
|
1:26 am
|
mojoneill:
|
A1: I'd add tech support and professional services, sales and marketing as well. Many inputs... #tcchat |
|
1:26 am
|
sarahmaddox:
|
A1: #tcchat our customers provide a fair bit of useful input. They help each other out too, via comment on the docs. |
|
1:27 am
|
2moroDocs:
|
Is there more collaboration w/dev these days, do you think, with agile in particular? #tcchat |
|
1:27 am
|
sarahmaddox:
|
@mojoneill A1: #tcchat I really like "the software itself". |
|
1:27 am
|
2moroDocs:
|
@sarahmaddox Thought you might have much customer input #tcchat |
|
1:28 am
|
sarahmaddox:
|
@2moroDocs #tcchat Yes, I'm finding that the devs and the tech writers interact very regularly. Hourly sometimes. |
|
1:29 am
|
roseacea:
|
A1: Product itself supported by internal docs (use cases), defect tracking system, SMEs #tcchat |
|
1:29 am
|
mojoneill:
|
I've seen a mix. Depends on the team & their interpretation of agile, which can be quite varied: http://bit.ly/9zrxjm #tcchat |
|
1:30 am
|
roseacea:
|
A1: marketing have a lot of input on our screencasts #tcchat |
|
1:31 am
|
2moroDocs:
|
Someone earlier today also mentioned that they often have mtgs w/tech support, sharing info from customers #tcchat |
|
1:31 am
|
2moroDocs:
|
So it seems like a wide range of input. So, on to Q2 #tcchat |
|
1:32 am
|
mojoneill:
|
A1: My meetings with tech support and PS group often entail speaking through the fabric cubicle wall that partitions us. ;P #tcchat |
|
1:32 am
|
2moroDocs:
|
Q3: What do you see as your biggest challenge w/collaboration: editing, accuracy, localization, tracking, or something else? #tcchat |
|
1:33 am
|
roseacea:
|
A1: Help content has included feedback from customers in Beta program #tcchat |
|
1:33 am
|
mojoneill:
|
A3: Misapplication of this: "Working software over comprehensive documentation" #tcchat |
|
1:34 am
|
mojoneill:
|
A3: Time and energy are close seconds. #tcchat |
|
1:35 am
|
mojoneill:
|
Wait, I missed Q2. Somehow I'm on Q3. lol
#tcchat |
|
1:35 am
|
2moroDocs:
|
@mojoneill Referring to agile? Sometimes diff, esp if meeting hourly as Sarah mentioned? #tcchat |
|
1:36 am
|
2moroDocs:
|
Nope. That's my error! I jumped ahead in my list. (What a day!) #tcchat |
|
1:36 am
|
mojoneill:
|
@2moroDocs sorry, I can't intuit the meaning of your sidebar question. #tcchat |
|
1:37 am
|
sarahmaddox:
|
A1: #tcchat I agree with @mojoneill re time and energy. Especially responding to customer comments and incorporating feedback into docs. |
|
1:37 am
|
2moroDocs:
|
Wondering if the working software mention referred to agile at all. #tcchat |
|
1:37 am
|
sarahmaddox:
|
#tcchat Ooops that last "A1" should be "A3" |
|
1:38 am
|
sarahmaddox:
|
@2moroDocs LOL #tcchat #commentoftheday |
|
1:38 am
|
mojoneill:
|
@2moroDocs Oh yes. Was a quote from the manifesto. #tcchat |
|
1:38 am
|
2moroDocs:
|
@sarahmaddox Do you respond to those immed, or wait on some until a later time? Some sort of triage for doc input? #tcchat |
|
1:40 am
|
2moroDocs:
|
@sarahmaddox Hadn't seen #commentoftheday before. Thx for that! #tcchat |
|
1:41 am
|
2moroDocs:
|
Q3/Q2: Earlier, ppl commented much on review cycles, & how diff that cld be #tcchat |
|
1:43 am
|
mojoneill:
|
Review Cycles: Difficulty is strange and sometimes conflicting criteria of review. #tcchat |
|
1:44 am
|
sarahmaddox:
|
@2moroDocs #tcchat Q3/Q2: We triage the input daily. Tech writers pick up the doc-related questions. Support picks up the others. When poss |
|
1:44 am
|
2moroDocs:
|
A2: Thoughts included sending smaller chunks 4 review, mini reviews #tcchat |
|
1:44 am
|
mojoneill:
|
Attempting to standardize on the first 20 pages of http://amzn.to/alIcIl proving difficult w/ non twriters. #tcchat |
|
1:45 am
|
2moroDocs:
|
@mojoneill what are differences in review criteria? #tcchat |
|
1:46 am
|
2moroDocs:
|
@sarahmaddox Q3/Q2 Is something you watch thru the day, & perhaps bring up in some of your mtgs through the day? #tcchat |
|
1:47 am
|
mojoneill:
|
"Thou shalt not use 'you' in tpubs". "Not allowed to copy and paste." Everything should be a picture. Everything should be concept. #tcchat |
|
1:47 am
|
mojoneill:
|
Don't use procedures. #tcchat |
|
1:48 am
|
mojoneill:
|
We should write a book so they can read it in the bathroom.... #tcchat |
|
1:48 am
|
2moroDocs:
|
So re collaboration w/customers where docs concerned, actually involves multiple groups: docs, support.. #tcchat |
|
1:48 am
|
mojoneill:
|
Too much detail. Too little detail. #tcchat |
|
1:50 am
|
2moroDocs:
|
@mojoneill One potential prob w/pictures is the old maintenance issue: do they become outdated quickly? #tcchat |
|
1:51 am
|
2moroDocs:
|
IMO, that will b more of a problem coming up. Will b more videos, pics. Outdated fast, particularly w/quick agile updates? #tcchat |
|
1:52 am
|
mojoneill:
|
@2moroDocs yeah. that's a cost for sure. It's going to get very expensive to produce video content that doesn't stale quickly
#tcchat |
|
1:54 am
|
2moroDocs:
|
Last topic: mentioned that, for docs, now create, deliver, & govern. Govern new, due to UGC for one thing. #tcchat |
|
1:54 am
|
sarahmaddox:
|
About videos in docs #tcchat they have limited usefulness? I get v impatient. Stop watching after 2 minutes. Much prefer text. So do many. |
|
1:55 am
|
2moroDocs:
|
@mojoneill Think that will result in use of quick videos more (like using a Flip camera or something similar). No time 4 other? #tcchat |
|
1:55 am
|
sarahmaddox:
|
Govern is maybe too strong a term for collaborative content incl UGC #tcchat who owns it? :) |
|
1:56 am
|
mojoneill:
|
@2moroDocs @sarahmaddox move from high production value & long production time to quick and dirty? Jing does a good job w/ that. #tcchat |
|
1:56 am
|
mojoneill:
|
(raises hand) Umm, I don't understand the question.
#tcchat |
|
1:58 am
|
sarahmaddox:
|
How about "massage" instead of "govern"? #tcchat "Curate" is good too, but I like the idea of being a content masseuse ;) |
|
1:59 am
|
mojoneill:
|
I think there is overlap between content curation, massaging, and knowledge management #kmers #tcchat |
|
1:59 am
|
2moroDocs:
|
@sarahmaddox Think you're right there. Perhaps users will make vid more, & doc groups: text? #tcchat |
|
1:59 am
|
kirstyt:
|
@2moroDocs But not all states have changed times! Brisbane/Qld is still on standard time, not daylight time! #tcchat |
|
2:01 am
|
sarahmaddox:
|
#tcchat Let's do the time warp again ;) |
|
2:01 am
|
2moroDocs:
|
This hour is up already! Sorry for being late due to the time change, everyone! Will stay here though for the next hour too! #tcchat |
|
2:02 am
|
2moroDocs:
|
Everyone welcome to stay around for S2 - the afterparty/startup! #tcchat We're on 24/7! |
|
2:02 am
|
sarahmaddox:
|
@2moroDocs Thanks so much Julie, it was great chatting again #tcchat I should have thought of the time change! |
|
2:02 am
|
2moroDocs:
|
@kirstyt Great! This is a fun day. I'll give a quick recap, then we can continue. Give me a sec - #tcchat |
|
2:04 am
|
2moroDocs:
|
@sarahmaddox Thank *you* Sarah! I'm learning much about time zones! Should have checked myself. Mostly learning what I don't know! #tcchat |
|
2:05 am
|
kirstyt:
|
@2moroDocs OK, great! #tcchat |
|
2:05 am
|
2moroDocs:
|
Ok: we've been talking about Collab in Doc Projects. 4 main areas: sources of info, challenges, planning, and community #tcchat |
|
2:06 am
|
larry_kunz:
|
Hi, everyone. I just came online and saw that y'all have already had a great #tcchat |
|
2:06 am
|
2moroDocs:
|
What I'll do this time is post the questions as they were so far today, then list some responses, & anyone can of course comment! #tcchat |
|
2:07 am
|
2moroDocs:
|
Q1: Sources: Who or what are sources of info for your docs? Customers? Developers? SMEs? #tcchat |
|
2:08 am
|
kirstyt:
|
#tcchat A1: SMEs - functional consultants, soln architects. Sometimes devs, but gen consultants give us better user-focussed info. |
|
2:08 am
|
2moroDocs:
|
A1 thru the day: docs, dev, tech support, training, customers (both rarely & lots) #tcchat |
|
2:08 am
|
mojoneill:
|
Hiya larry!
#tcchat |
|
2:08 am
|
kirstyt:
|
#tcchat A1: Rarely customers. Little interaction with them & some products highly customised to their site. |
|
2:10 am
|
2moroDocs:
|
@larry_kunz Hi Larry! Thanks for coming by so late your time! We're still at it! Just posted Q1. #tcchat |
|
2:11 am
|
mojoneill:
|
@kirstyt do you have forums, other ways to observe customers directly?
#tcchat |
|
2:11 am
|
2moroDocs:
|
Well, it seems to me like sources of info (in addition to testing the app itself) really run the gamut. #tcchat |
|
2:12 am
|
2moroDocs:
|
Wonder: how do collab requirements differ for each group? Say tech support, users, mktg, consultants #tcchat |
|
2:13 am
|
kirstyt:
|
@mojoneill We have forums, but v little participation in them. Consultants on-site 90% time, so usually v.good with user knowledge #tcchat |
|
2:14 am
|
mojoneill:
|
@kirstyt interesting. do the consultants write up regular reports? do you create and maintain user personas to help define audience? #tcchat |
|
2:15 am
|
larry_kunz:
|
@2moroDocs Sources of info run the gamut. Yes, two-edged sword: you get great info, but harder to manage the project. #tcchat |
|
2:15 am
|
2moroDocs:
|
Some ppl had regular mtgs w/tech support. For users, some immed response, but triage impt. Seems like coll w/tech support frequent #tcchat |
|
2:15 am
|
kirstyt:
|
@mojoneill No and no. :( But personas or similar would prob. be useful. #tcchat |
|
2:16 am
|
2moroDocs:
|
@sarahmaddox Let me track down a link @larry_kunz sent about that earlier. Others also suggested "manage" as a term. #tcchat |
|
2:16 am
|
2moroDocs:
|
RT @larry_kunz: Search on 'governance' in comment on this article by @rahelab: http://bit.ly/aoDdBQ #tcchat |
|
2:18 am
|
PattyBlount:
|
#tcchat good evening, all. Am I too late? |
|
2:18 am
|
2moroDocs:
|
Q2: What do you see as your biggest challenge w/collaboration: editing, accuracy, localization, tracking, or something else? #tcchat |
|
2:18 am
|
2moroDocs:
|
@mojoneill Got the Q number right this time! #tcchat |
|
2:19 am
|
mojoneill:
|
Hi Patty! #tcchat |
|
2:19 am
|
mojoneill:
|
@2moroDocs Ha! Second time is the charm, eh? ;P #tcchat |
|
2:19 am
|
2moroDocs:
|
@PattyBlount Never too late Patty! We're just getting on to Q2. Thx for dropping by! #tcchat |
|
2:20 am
|
kirstyt:
|
A2: Editing, accuracy, l10n - yes. Appropriateness, also how much personal preference has come into play if editing others content. #tcchat |
|
2:20 am
|
kirstyt:
|
A2: I'm noticing how much personal preference comes into play with both content and l10n as I straddle both now. #tcchat |
|
2:21 am
|
mojoneill:
|
@kirstyt l10n? #tcchat |
|
2:21 am
|
2moroDocs:
|
@mojoneill Let's hope! (Everyone - in last hour, I mislabeled Q2 as Q3.) #tcchat |
|
2:21 am
|
kirstyt:
|
A2: Also, finding an effective way for ppl to work together and collaborate globally. #tcchat |
|
2:22 am
|
kirstyt:
|
@mojoneill Sorry, l10n = localisation (i18n= internationalisation, t9n = translation, g11n = globalisation) #tcchat |
|
2:22 am
|
mojoneill:
|
@kirstyt Part of the challenge of editing is not doing a complete rewrite just because it's someone else's voice. #tcchat |
|
2:23 am
|
mojoneill:
|
@kirstyt well, the luddite in me often fights with the troglodyte in me...so I get confused by l10n, i18n, t9n, and g11n. :P #tcchat |
|
2:25 am
|
kirstyt:
|
@mojoneill When we were part of the g11n team, we got so jealous of their abbreviations, we decided we were the d2o team (doco). ;) #tcchat |
|
2:25 am
|
2moroDocs:
|
@kirstyt Have you found ways to facilitate that? #tcchat |
|
2:26 am
|
2moroDocs:
|
@kirstyt Thanks for this! #tcchat |
|
2:27 am
|
mojoneill:
|
@kirstyt what's your tool chain look like for collaboration -> output #tcchat |
|
2:29 am
|
2moroDocs:
|
Q3: Speaking of editing, do u see the role of editor changing on collaborative projects? #tcchat |
|
2:31 am
|
PattyBlount2:
|
#tcchat q3: editing on collaborative projects will likely be split among all collaborators. |
|
2:32 am
|
2moroDocs:
|
Q3 @kirstyt Wondering: how is editing affected w/your collaborating globally (as mentioned earlier)? #tcchat |
|
2:32 am
|
kirstyt:
|
@2moroDocs Not yet! #tcchat |
|
2:33 am
|
kirstyt:
|
@mojoneill Good question. At moment, it's very traditional flow, not partic. collaborative. #tcchat |
|
2:33 am
|
2moroDocs:
|
Anyone have shortened editing cycles due to agile or dealing with UGC? #tcchat |
|
2:34 am
|
larry_kunz:
|
Some editors report having trouble squaring agile's "good enough to ship" with the traditional editor's goal of 100% perfect. #tcchat |
|
2:35 am
|
2moroDocs:
|
@kirstyt That's interesting. So content input perhaps more collaborative, but editing basically the same? #tcchat |
|
2:35 am
|
mojoneill:
|
RT @larry_kunz: Some editors report having trouble squaring agile's "good enough to ship" with the traditional editor's goal of 100% perfect. #tcchat |
|
2:36 am
|
2moroDocs:
|
@larry_kunz Doesn't one of your slides note that there's no or little time for comprehensive edits any longer? #tcchat |
|
2:36 am
|
mojoneill:
|
@larry_kunz that can very often be the case. #tcchat |
|
2:36 am
|
kirstyt:
|
A3: Think both editing and writing can change with global collab. Editors may have to change viewpoint, as per @larry_kunz #tcchat |
|
2:36 am
|
mojoneill:
|
Without a formal role as "editor", who decides "good enough to ship"? #tcchat |
|
2:36 am
|
2moroDocs:
|
BTW - I'll send that link out to Larry's presentation again for those that haven't seen it yet. One sec! #tcchat |
|
2:36 am
|
kirstyt:
|
@2moroDocs Minimal editing happening. I edit when I can, but no one is devoted to it. #tcchat |
|
2:37 am
|
2moroDocs:
|
RT @2moroDocs: Here's link to preso by Larry Kunz: Managing Doc Projects in a Collaborative World http://slidesha.re/9SafeN #tcchat |
|
2:38 am
|
PattyBlount2:
|
@kirstyt #tcchat Same here. No single editor, just shared responsibility for editing across team. |
|
2:39 am
|
eastcoasterin:
|
Tuning into #tcchat trying to absorb some info ;) hopefully stress level will drop as a result |
|
2:39 am
|
mojoneill:
|
does editing happen through direct action (editor makes changes) or task assignment (fix this typo, update this graphic, etc...)? #tcchat |
|
2:40 am
|
2moroDocs:
|
Does style guide then increase in importance? Or does it even matter as much? #tcchat |
|
2:41 am
|
2moroDocs:
|
@eastcoasterin Hi there! Thanks for dropping by. We're are discussing how editing has changed. Consensus: not much time 4 it! #tcchat |
|
2:41 am
|
larry_kunz:
|
@2moroDocs Yes -- little or no time for comprehensive edits....Edits (like much of the writing) now tend to be narrowly focused. #tcchat |
|
2:41 am
|
mojoneill:
|
Question: What's your TW to Developer ratio? Or TW to product ratio? #tcchat |
|
2:42 am
|
kirstyt:
|
@2moroDocs A style guide matters, but I've seen it doesn't get ingrained in some TCs without their writing being edited. #tcchat |
|
2:43 am
|
2moroDocs:
|
@kirstyt There's a Catch 22! Need the style guide to ensure consistency, reduce need 4 editing. No time for it! #tcchat |
|
2:45 am
|
eastcoasterin:
|
@2moroDocs hello! disclaimer: I am probably in a unique situation - the only tech writer/editor in the company. staying tuned! #tcchat |
|
2:45 am
|
mojoneill:
|
I'd take clarity and usability in 2 diff styles over density and difficulty in 1 single style any day. #tcchat |
|
2:46 am
|
KnowledgeBishop:
|
RT @2moroDocs: RT @2moroDocs: Here's link to preso by Larry Kunz: Managing Doc Projects in a Collaborative World http://slidesha.re/9SafeN #tcchat |
|
2:46 am
|
2moroDocs:
|
@eastcoasterin I'm sure you have plenty of company on that one! A number of lone writers out there. #tcchat Glad you're here! |
|
2:47 am
|
2moroDocs:
|
Yes! RT @mojoneill: I'd take clarity and usability in 2 diff styles over density and difficulty in 1 single style any day. #tcchat |
|
2:47 am
|
2moroDocs:
|
@KnowledgeBishop Hi there! #tcchat |
|
2:48 am
|
2moroDocs:
|
I'm going to jump to last question. #tcchat |
|
2:48 am
|
mojoneill:
|
Hiya Tristan! #tcchat |
|
2:48 am
|
2moroDocs:
|
Q3: Today, doc strategy needed to create, deliver, & govern docs ? not just doc plan. What needs to be addressed to govern? #tcchat (Con't) |
|
2:50 am
|
2moroDocs:
|
Q3 con't: through the day, there was question about the term 'govern' - others: manage. Let me find info from Larry. RT coming! #tcchat |
|
2:51 am
|
KnowledgeBishop:
|
@2moroDocs: Hi! At a family reunion. Just wanted to say hello! #tcchat |
|
2:51 am
|
2moroDocs:
|
RT @larry_kunz: @juliov27612 "Govern" not exactly = "manage." Search on 'governance' in comment: http://bit.ly/aoDdBQ #tcchat |
|
2:52 am
|
PattyBlount2:
|
#tcchat OK, must head to sleep now. Been a long day. |
|
2:52 am
|
2moroDocs:
|
@KnowledgeBishop Thx for dropping by - #tcchat |
|
2:53 am
|
2moroDocs:
|
@PattyBlount2 Yes, quite a day for you. Thanks for dropping in so late! #tcchat |
|
2:53 am
|
mojoneill:
|
Later Patty! #tcchat |
|
2:54 am
|
kirstyt:
|
A3: Too big an answer for twitter! :) Full lifecycle considerations, roles, responsibilities, approval ... #tcchat |
|
2:57 am
|
2moroDocs:
|
@kirstyt That makes sense. #tcchat Don't know if Larry is still here or not. It's very late on the East coast. #tcchat |
|
2:59 am
|
2moroDocs:
|
I'm thinking that perhaps more planning is needed than before. Not just a doc plan: a strategy to involve all new aspects, roles #tcchat |
|
3:00 am
|
2moroDocs:
|
Complexity of everything has increased, for sure. More planning, coordination needed? #tcchat |
|
3:01 am
|
mojoneill:
|
How has complexity increased for you? #tcchat |
|
3:01 am
|
kirstyt:
|
Yes, exactly, full strategy needed (as a portion of the full content strategy) #tcchat |
|
3:01 am
|
larry_kunz:
|
@2moroDocs Yes, content strategy takes precedence. Doc plan is tactical & should support the content strategy. #tcchat |
|
3:02 am
|
2moroDocs:
|
Well I can see that another hour has elapsed. I can officially close this, but, as usual, will be glad to stay around. #tcchat |
|
3:03 am
|
2moroDocs:
|
Boy, my feed is so slow today. I'm just seeing your last responses @larry_kunz and @kirstyt #tcchat |
|
3:03 am
|
mojoneill:
|
wow. thanks for another fascinating tcchat! #tcchat |
|
3:04 am
|
2moroDocs:
|
@mojoneill I'm thinking that there are just so many more players and factors. UGC is the biggest I can think of. Mobile another. #tcchat |
|
3:05 am
|
mojoneill:
|
sure. with identical inputs, depth must decrease if breadth increases. #tcchat |
|
3:05 am
|
2moroDocs:
|
@mojoneill Thanks! Appreciate your participation today! #tcchat |
|
3:06 am
|
juliebhunt:
|
RT @2moroDocs: RT @2moroDocs: Here's link to preso by Larry Kunz: Managing Doc Projects in a Collaborative World http://slidesha.re/9SafeN #tcchat |
|
3:07 am
|
2moroDocs:
|
@mojoneill and what happens when you get spread too thin? or is that already occurring? No time for editing, etc? #tcchat |
|
3:08 am
|
2moroDocs:
|
@juliebhunt Hi Julie! Thanks for the RT of Larry's presentation. #tcchat |
|
3:08 am
|
mojoneill:
|
@2moroDocs well, I think you answered your own question with "spread too thin". too thin means a decrease in some aspect of quality #tcchat |
|
3:09 am
|
mojoneill:
|
@2moroDocs "spread just thin enough" might be the better goal. :P
#tcchat |
|
3:10 am
|
2moroDocs:
|
@mojoneill and is editing the first to go? when I started out, accuracy always #1. Hope that hasn't been affected! #tcchat |
|
3:11 am
|
2moroDocs:
|
@mojoneill Makes sense. Some experimentation, I suppose, to see where the line is. #tcchat |
|
3:12 am
|
mojoneill:
|
@2moroDocs I think there are a lot of artifacts that linger on in TW from the days of printed manuals + audiences expecting books. #tcchat |
|
3:13 am
|
mojoneill:
|
editing, as a distinct profession, might be one of those in some environments. more likely it's a role that gets picked up as needed #tcchat |
|
3:14 am
|
2moroDocs:
|
I think I'm going to have to call it a night, unfortunately. Family reqs here. :-) #tcchat Thanks everyone 4 coming tonight/today! #tcchat |
|
3:15 am
|
mojoneill:
|
thank you for hosting and moderating! #tcchat |
|
3:17 am
|
2moroDocs:
|
@mojoneill Yes, that's something I wonder about more & more. #tcchat |
|
3:20 am
|
2moroDocs:
|
@mojoneill Thank you so much! #tcchat 'Night all! |
|
9:02 am
|
ellispratt:
|
@sarahmaddox "massage" instead of "govern"? #tcchat "Curate" is good too // 'content fondling'? Probably not... |
|
4:05 pm
|
KnowledgeBishop:
|
Because #techcomm has a powerful future, I #follow @TC_chat and the #tcchat tag! |
|
4:08 pm
|
ermphd:
|
RT @KnowledgeBishop: Because #techcomm has a powerful future, I #follow @TC_chat and the #tcchat tag! <true dat!> |
|
4:09 pm
|
lrmeyer747:
|
RT @KnowledgeBishop: Because #techcomm has a powerful future, I #follow @TC_chat and the #tcchat tag! < so do I; always lots to learn! |
|
7:43 pm
|
2moroDocs:
|
New post: Going Global, One Inch at a Time http://bit.ly/cQTfFE . #tcchat #techcomm |
|
7:56 pm
|
larry_kunz:
|
RT @2moroDocs: New post: Going Global, One Inch at a Time http://bit.ly/cQTfFE . #tcchat #techcomm |
|
9:56 pm
|
ermphd:
|
RT @2moroDocs: New post: Going Global, One Inch at a Time http://bit.ly/cQTfFE . #tcchat #techcomm <shrinking world has benes & challenges> |
|
10:00 pm
|
KnowledgeBishop:
|
Because they turn #tcchat into my happy place, I #follow @pattyblount2, @ermphd, @mojoneill and @SarahMaddox! |
|
10:17 pm
|
2moroDocs:
|
@lrmeyer747 Thank you for the #FF - and for participating in the #tcchat gatherings - |
