Comments on: Team Documentation Design Reviews http://www.gryphonmountain.net/2008/07/team-documentation-design-reviews/ Technical Communication and Other Writing Topics, by Ben Minson Wed, 11 Jan 2012 04:05:49 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Gary Franceschini http://www.gryphonmountain.net/2008/07/team-documentation-design-reviews/#comment-147 Gary Franceschini Sat, 09 Aug 2008 21:21:56 +0000 http://www.gryphonmountain.net/?p=82#comment-147 Sorry, I'm late to the party here, but I wanted to comment on Gordon's statement that everyone doing their own thing is odd. I have worked for large and small companies and what Ben describes accords with my experience. Different designers doing their own thing is husbanded rather than frowned upon as it increases creativity (as Ben says). Yes, some basic guidelines do exist, but my current crew finds that so long as an individual design retains the look and feel of our application, anything that is effective is worthy of consideration. Gary Sorry, I’m late to the party here, but I wanted to comment on Gordon’s statement that everyone doing their own thing is odd. I have worked for large and small companies and what Ben describes accords with my experience. Different designers doing their own thing is husbanded rather than frowned upon as it increases creativity (as Ben says). Yes, some basic guidelines do exist, but my current crew finds that so long as an individual design retains the look and feel of our application, anything that is effective is worthy of consideration.

Gary

]]> By: Ben http://www.gryphonmountain.net/2008/07/team-documentation-design-reviews/#comment-146 Ben Thu, 31 Jul 2008 23:08:47 +0000 http://www.gryphonmountain.net/?p=82#comment-146 Gordon, Our team is still young and small enough (speaking of the team itself, not necessarily the people in it :)) that we have freedom to find what works best for us and our users. We do share templates with each other, but right now, we're using the freedom allowed within our organization's style guide to be creative and experiment. Print publishing goes all the way back to when our organization was founded, but its use of software is more recent, and the inclusion of professional writers for documentation newer still. I'll be glad to report on the results. Gordon,

Our team is still young and small enough (speaking of the team itself, not necessarily the people in it :) ) that we have freedom to find what works best for us and our users. We do share templates with each other, but right now, we’re using the freedom allowed within our organization’s style guide to be creative and experiment. Print publishing goes all the way back to when our organization was founded, but its use of software is more recent, and the inclusion of professional writers for documentation newer still.

I’ll be glad to report on the results.

]]> By: Gordon http://www.gryphonmountain.net/2008/07/team-documentation-design-reviews/#comment-145 Gordon Thu, 31 Jul 2008 07:20:53 +0000 http://www.gryphonmountain.net/?p=82#comment-145 Definitely interested in hearing how this works out for you, as I'm struggling to see specific benefits. Don't you work with templates, don't you have an agreed basic structure to which everyone contributed? I'm sure you do, and it's probably just because it's early and I've only had one coffee, but this reads a little like you all do your own thing when it comes to content design. Which is, in my experience, odd! Set me straight, please. Definitely interested in hearing how this works out for you, as I’m struggling to see specific benefits.

Don’t you work with templates, don’t you have an agreed basic structure to which everyone contributed?

I’m sure you do, and it’s probably just because it’s early and I’ve only had one coffee, but this reads a little like you all do your own thing when it comes to content design. Which is, in my experience, odd!

Set me straight, please.

]]>