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.
Granted sample docs don't contain proprietary info, why do you keep such
tight control over them?
Leonard C. Porrello
-----Original Message-----
From: techwr-l-bounces+leonard -dot- porrello=soleratec -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+leonard -dot- porrello=soleratec -dot- com -at- lists -dot- techwr-l -dot- c
om] On Behalf Of John Posada
Sent: Wednesday, April 23, 2008 6:50 PM
To: ekarenski-techwrl -at- yahoo -dot- com
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Samples vs. Portfolio
Karen...I've never done anything in 20 years that I didn't consider
proprietary. There is a difference between proprietary and confidential.
It
also doesn't mean I cannot show it during an interview. The point is how
you
control the material you show.
- Do not let it out of your sight. Having it in binders in clear pockets
helps you control the pieces
- Do not let the viewer take notes of the contents..about your effort to
create the content fine.
- Do not let them make photocopies of any pieces. If they say they are
doing
it to show someone who isn't at the meeting, tell them you'd be happy to
come back. You want the oportunity to explain what you did with each
piece
anyway.
- Do not send your portfolio or samples by mail.
On 4/23/08, Karen <ekarenski-techwrl -at- yahoo -dot- com> wrote:
>
> I'm back on the techwr-l archives reading about portfolios and a lot
of
> the associated issues (i.e. copyright, leaving them for review, etc.).
>
> I've basically had 2 positions over 12 years where almost all of the
> information is proprietary. I'm trying to get over that hurdle by
writing my
> own documentation about a software application I wrote for organizing
a
> silent auction.
>
> My head's spinning a bit (I think I've been reading the archives and
job
> postings too long today.)
>
> I've seen a few job posts where they request samples with your resume.
I
> would prefer to show them at an interview; however, we all have to
play the
> game sometimes.
>
> Sometimes people ask for samples or a portfolio for interviews.
>
> I know that presentation is important, especially when creating a
> portfolio. However, is there anything you would do differently when
asked to
> provide samples vs. a portfolio?
>
>
> --
> John Posada
> Senior Technical Writer
> NYMetro STC President
>
> - Said the Zen master to the hot dog vendor "Make me one with
everything."
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats
or
printed documentation. Features include support for Windows Vista & 2007
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as
Leonard -dot- Porrello -at- soleratec -dot- com -dot-
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
