Metin Eniste
Member
- Joined
- Nov 28, 2007
- Messages
- 83
I can't think of a good reason why you wouldn't want everyone trained to update the site. If you have a designated "updater," would he work 7 days a week? What happens when he gets sick, goes on vacation, wants to sleep, is away from his computer when a huge story breaks, or leaves for another job? You have to spread out the responsibility not just to avoid one person being overwhelmed/burned out, but also to emphasize the importance of the online product to the entire staff.
I'm at a small paper, too. We've found that you have to train everyone thoroughly and back that up with a robust best practices document containing step-by-step instructions for every aspect of your Web publishing process. That way, everybody can be self-sufficient; they have no excuse for emailing their stuff to the "web guy" rather than posting it themselves.
On top of that, you can't just say, "We need Web updates!" and leave it at that. Include it in the relevant employees' goals, keep track of how many updates each person has done, and make that part of the annual review process. It's worked well for us; now if our reporters are working on a story for the next day, they're accustomed to putting the first 5-6 paragraphs on the site ASAP with a tagline that says, "Read tomorrow's newspaper for more."
We do have a web editor who posts weather updates, traffic updates, wire stories, etc. throughout the afternoon, and he's ultimately responsible for the quality of the overnight update, but in theory he should just be fine-tuning at night. The heavy lifting is done by the section editors (i.e., the web editor tweaks the priority of stories, assign different keywords/taxonomies, fixes glaring errors, adds related videos or slideshows, etc. but the section editors make sure all stories and photos are entered into the system in the first place).
I'm at a small paper, too. We've found that you have to train everyone thoroughly and back that up with a robust best practices document containing step-by-step instructions for every aspect of your Web publishing process. That way, everybody can be self-sufficient; they have no excuse for emailing their stuff to the "web guy" rather than posting it themselves.
On top of that, you can't just say, "We need Web updates!" and leave it at that. Include it in the relevant employees' goals, keep track of how many updates each person has done, and make that part of the annual review process. It's worked well for us; now if our reporters are working on a story for the next day, they're accustomed to putting the first 5-6 paragraphs on the site ASAP with a tagline that says, "Read tomorrow's newspaper for more."
We do have a web editor who posts weather updates, traffic updates, wire stories, etc. throughout the afternoon, and he's ultimately responsible for the quality of the overnight update, but in theory he should just be fine-tuning at night. The heavy lifting is done by the section editors (i.e., the web editor tweaks the priority of stories, assign different keywords/taxonomies, fixes glaring errors, adds related videos or slideshows, etc. but the section editors make sure all stories and photos are entered into the system in the first place).