Spot on, Bob. So much of my time is spent "fixing up" other people's work or "having a look" at what's been written by the consulting firm who did the initial roll-out. I think it's vitally important as a writer to be able to analyse good and bad writing, and to be able to apply lessons learnt to your own writing. 2008/9/6 Bob Trussler <bob.trussler@xxxxxxxxx> > Jasmine, > Some time back, I had a manager ask how to interview a tech writer. It was > for a position in another state. > I told him to ask for some samples of their work to look at (a portfolio). > He responded that they may bring in work that is not theirs. > I suggested that he ask questions like: > Why is this good? > Why was it done this way? > What could have been done better? > What problems did you have? > There are ALWAYS problems so an answer of 'No problems" is suspect. > "Yes'', he said and marched off. ( and hired a writer with excellent > skills and experience) > > > Bob Trussler > >