The other extreme, but still the same rules
Well, it’s been too long since I updated my lil’ corner of cyberspace. Apologies.
But two weeks ago, I made about as extreme a move in media (without having to move, physically) one could make: from the “write until you drop,” infinite news hole of a Website, to the backtimed, “two minutes is an eternity” land of television.
Some would call that backwards. I call it a new challenge, with a bigger audience, and a chance to explore new territory. I’m jazzed.
This will no doubt change my perspective on things (I’m the new assistant news director at KTVZ), but as for the point of this Website, it really doesn’t change things. I’m still seeing lots of press releases, good bad and … well, not so bad.
A good press release is a good press release, for any form of media. Sure, much less of it can be used in a minute-long TV news segment, but you don’t want to pre-write the segment (or article) anyway - you want to entice the editor/reporter to write a story. Spoon-feed a tasty tidbit or two and let them fill in the blanks - do their job.
My brain is still wrapping itself around my new duties (haven’t touched a camera yet, much less the fancy video-editing system), but … to no surprise, one major rule is that the Clock Rules in TV (and radio, of course). There’s always more to say than time to say it, but then again … it’s not about words, is it? It’s about powerful, telling images. When it’s at its best.
You can’t get that out of a news release, but the best sure can provide a sense of where those images will come from, and whet a reporter’s appetite.
Sure, there’s a daily Beast to be fed, and it’s not all powerful and there’s fluff and, yes, the dreaded “happy talk.” But my new boss talks of the power TV holds, beyond any other medium - you get to know these people who come into your living room every night, for better or worse (oh am I not looking forward to being on camera;-)
But magic can happen, I’ve already had a taste of it. And I’m anxious, and ready, for more.
References (1)
-
Response: 193387c5be57f5f12fbd193387c5be57

Reader Comments