TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: format for technical writing portfolios From:Kathryn Marshall <kmarshall -at- MODACAD -dot- COM> Date:Fri, 12 Sep 1997 11:17:12 -0700
I do just about the same thing as far as what to include (TOC, resume,
different categories of writing); except I use a leather-bound book.
Each page is in a protective sheet. I put extra copies behind the actual
sample -- that way the interviewer can take what they want. My portfolio
isn't quite as long either (maybe 30 pages).
Chuck's method works for him and seems like a neat idea. Mine works for
me. Btw, you'd be surprised how many people are impressed by the fancy
leather binding. :-) Plus, I like it because interviewers are forced to
look at your work and can ask you questions directly about specific
projects. --Gives you added time to toot your own horn.
$0.02,
-Kathy
> ----------
> From: Chuck Martin[SMTP:cmartin -at- SEEKERSOFT -dot- COM]
> Reply To: Chuck Martin
> Sent: Friday, September 12, 1997 11:10 AM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: format for technical writing portfolios
>
> While there are no stricgt conventions, I developed an idea that has
> been
> very successful for me. I think it is very user-oriented.
>
> I take several work samples: book chapters, printouts from Help
> screens,
> journal articles, and make copies. Always doubl;e-sided; no need to
> waste
> paper. I create a cover. I include a table of contents, followed by a
> resume. I have all of this copied at a local copy shop, with the cover
> on
> color card stock. I have a blank back cover added, then have it tape
> bound.
>
> The result: when I go to an interview, instead of having a fancy
> leather-bound book that an interviewer has just a few minutes to
> glance
> through, I simply hand them the portfolio, tell them to keep it and
> review
> it at their leisure. They can then see in detail the quality of my
> work
> without feeling rushed.
>
> My most recent portfolio runs about 60-70 sheets of peper total, with
> three
> substantial samples of printed documentation, plus a half dozen
> printouts
> of Help screens, as well as other assorted material. While each of
> these
> costs several dollars each to produce, I think it's an excellent
> investment, as well as an example of how important I view the end user
> under any circumstance.
>
> At 05:19 PM 9/11/97 PDT, you wrote:
> >forwarded for a friend:
> >
> >>I'm putting together a portfolio of my technical writing, and I had
> a
> >>few questions about portfolio conventions:
> >>
> >>- How large should a portfolio be? Mine is ten pages double sided,
> >>and includes three different styles of work.
> >>
> >>- Should the portfolio be double-sided or single-sided? I am
> >>assuming that it should be printed up the way it would actually be
> >>used (i.e., double-sided)
> >>
> >>- Should I precede each piece with a paragraph or two discussing
> >>target audience, deadline constraints, style constraints, and so on?
> >>I haven't done so yet, but it seems like a good idea.
> >>
> >>- Should I only include complete pieces, or are fragments okay? So
> >>far I have been able to find examples of my work that are only a few
> >>pages long, but in the future I may have longer pieces I want to
> >>include.
> >
> >-- Kate O'Neill <kaethe -at- geocities -dot- com> or
>
> --
> "You don't look American"
> "Everyone looks American, because Americans are from everywhere"
> - Doonesbury
> Chuck Martin
> Technical Writer, Seeker Software, Inc | Personal
> cmartin -at- seekersoft -dot- com | writer -at- grin -dot- net
> www.seekersoft.com | www.grin.net/~writer
>
> ~~
> TECHWR-L (Technical Communication) List Information: To send a
> message
> to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send
> commands
> to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
> Search the archives at http://www.documentation.com/ or search and
> browse the archives at
>http://listserv.okstate.edu/archives/techwr-l.html
> Send list questions or problems to the listowner at
>
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html