Dori wrote on 09/27/2007 12:00:02 PM: > Tim wrote: > > Purpose: provide sale staff a reference for the core competencies needed > to do their jobs well.
> So what are those? Be specific, don't use gobbledegook like > "core competencies". Exactly what is "doing their jobs well" -- selling > one puppy a week? Unloading a litter every day? too much to list, including: company history brand values and mission product info (pretty easy, we have only one w/ about 12 accessories) selling in our markets understanding our markets (varying customer needs in each market) computer use specific computer apps use phone use phone etiquette ...and so on... > Tim wrote: > > They are going to need a great training program, not only a manual to > refer to. > And who is responsible for developing that training program? Possibly sales manager (my immed. boss) and Sales/Mktg VP, maybe the HR VP... > Are they qualified to do so? I have no idea. A lot happens ad hoc here, in response to some sudden need or perceived vacuum, not too much detailed planning ahead in my dept...there are some working to change that, but it's slow going. Hard to make changes when sales are going well...often it takes a revenue emergency to shock a company into rapid change/upgrade/improvement mode. > Testing crew...? You must be assuming this company has devoted some > resources to this. I'm IT! Creator, developer, tester, writer, and maybe ... > So your company is planning to abuse its sales staff and > customers by having them discover and report the bugs? Not nice, and > not a good idea. I don't know that there will be any bugs on that end, and sales wouldn't be responsible for them, IT would...we'd work that out in advance before launch. Me and my manager and IT would probably test it...basically just opening it and seeing if I can navigate in it, I'm thinking. Isn't the output just a document but in online format, like Help for Word, or a web page? Maybe I can't visualize the bad possibilities because I've never done this before on this scale...I've written "How to do my job" 5-10 page manuals in various positions, and "How to maintain your PC" procedures for staff. Also did a tiny part of a large operational procedures manual/documentation project for Blue Cross Blue Shield. Thinking either web author software like Dreamweaver/similar or a HAT (Flare or roboCOP...;-] ) will work best. It'll be on our server/network I'd guess, so the IT staff will install it and work out whatever it needs other than content (my job) to make it work...no need to take it outside to the Internet, all staff can access it here at work and log onto our network from afar w/ notebooks w/ wi-fi or dialup. A wiki or safe-login website would work if we ever send reps into the field very much. The product is so good that it often sells itself, and many sales just come in over the phone by referral, previous phone work, trade show contacts, etc. > A one-hour meeting with several key stakeholders to brainstorm (10 > minutes), select and prioritize the 'storm results (10 minutes), create > an action/deliverables plan and preliminary timeline from those > prioritized results (40 minutes). Good idea, when that time rolls around...till then i have my own outline, putting the pieces together myself. Looking at minimal need for staff input via the doc itself, we have email for that...Flare does provide that wiki-like response area, I'm told by another expert user...if we need it. > Tim wrote: > > It will need constant updating, probably by designated sales or IT > staff. > Me if I'm lucky enough to be hired (I'm a temp, no plans for hire yet). > In my crystal ball I see you as Webmaster for the Sales Support > Intranet Site..... Our sales staff is only 13 people, so IT would probably do that. Can't imagine there's that much updating they'd need a full timer...unless I help develop the training. THAT would be fun! WHo knows...at this point I'll be happy if I can master my own paperwork and get started writing the manual...all this investigating and research is so scattery it's driving me nuts. I need things more bolted down. Thanks for the FutureView...one of my potential future lives. > Tim wrote: > > I'm confused about how this works, though the IT people here can clue > me. > What platform does it sit on? Like a web site sits on a server. Does the > Wiki do that? ... > You need some very basic "Intro to the Internet" information. I do know the internet and its basic structure and flow...just not the new techie parts like wikis. Oh, I know Wookies!* Does that help??? > And on having fun...it could happen! > > Dori Green It's already fun...except for the frustrations. It's just kind of boggling...so I'm boggled and scattered on that part. Can't wait for the writing to start! Thanks for all your help and comments, Dori, Tom and Bob and Carol and Ted and Alice! Tim Mantyla *"Get your groove AND your Millenium Falc On!" ______________________________________________ Author Help files and create printed documentation with Doc-To-Help. New release adds Team Authoring Support, enhanced Web-based help technology and PDF output. Learn more at www.doctohelp.com/tcp. Interactive 3D Documentation Parts catalogs, animated instructions, and more. www.i3deverywhere.com _______________________________________________ Technical Communication Professionals Post a message to the list: email [EMAIL PROTECTED] Subscribe, unsubscribe, archives, account options, list info: http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com Subscribe (email): send a blank message to [EMAIL PROTECTED] Unsubscribe (email): send a blank message to [EMAIL PROTECTED] Need help? Contact [EMAIL PROTECTED] Get the TCP whole experience! http://www.techcommpros.com
