Re: What do you call policy/process/procedure structure?

["Peter Neilson" <neilson -at- windstream -dot- net>]

Bingo, Gene!

Bear in mind that your resume will be read at most ONCE to see if it  
matches what the HR staff at hiring company think they need. They will  
will have their own way of treating your words that refer, for instance,  
to the User Interference Portability Subescalation Standards Plan, and it  
won't be good. Instead try to show how you helped your employer out of a  
difficulty.

One of the standard pieces of advice, which rarely applies to tech  
writers, is to show in numbers how much money your work made for the  
company, or at least saved. We writers almost never see those figures, but  
if we do it's because things have gone from bad to dreadful, for reasons  
beyond our control but not beyond our blame. "The product failed to sell  
because the tech writing was late, and it cost us $10,000,000." With luck  
the entire TW staff have jumped ship before the sinking. As one tech  
illustrator said, upon being introduced to a piece of scary and crazy  
software, "Oh, now I understand it. It DOESN'T WORK!"

In the advertising business, where I have occasionally hung my hat, the  
key phrase seems to be, "You hurt, we help." To get into that frame of  
mind you need to understand the potential client's pain, and it's often  
not what you initially think it is. You have to live inside his head.

On Tue, 21 Apr 2020 15:18:36 -0400, Gene Kim-Eng <techwr -at- genek -dot- com> wrote: