The Church Media Community
Equipping You to Communicate Effectively
support CMN & share a
library of 19K+ images, videos, etc
Go Pro!
 
Go Back   The Church Media Community > Teams & Leadership > Leadership Issues
Forgot Password?
                          Register

Reply
 
Thread Tools Search this Thread Rate Thread Display Modes
  #1 (permalink)  
Old Wednesday, October 6th, 2010, 03:46 PM
Media Guy

 
 Join Date: Feb 2003 
 Last Online: Monday, April 23rd, 2012 
Technology Allowance

We're starting to look at another round of technology upgrades for staff. The last few rounds we standardized hardware and software so that everyone was on the same playing field. That's certainly an option again, but I'm seeing some companies move to a technology allowance and give the individual user choice of what equipment they want to use as long as it meets certain standards and compatibility requirements.

When we first started this our staff was much less tech savvy. We now have a younger and more tech aware group and in some cases (media creation for instance) the 'standard issue' system doesn't really cut it for long, and then they have resorted to using their own personal systems to accomplish the job.


Have any of you moved to this model? If so, what are your experiences?

Dan
Reply With Quote Start a New Topic From This Comment
  #2 (permalink)  
Old Wednesday, October 6th, 2010, 11:13 PM
Esoteric's Avatar
Church Media Mentor
Become a CMN Business Member!
Become a CMN Professional Member!

 
 Join Date: Dec 2008 
 Last Online: Today 
I have many clients that do this actually. For example a large church in the area has three video content guys. Two of them prefer Final Cut Pro and the other one loves Adobe Premier. They are each allowed to use the software they want as long as their work meets the specs.

Now the only problem is when guy #3 moves on, then they may have to buy another license for FCP if the guy replacing him prefers FCP (unless they hire a Premier specialist). Unless they have a site license (which I believe they did for FCP but not for Premier).

Mike
__________________
Mike Campbell

Esoteric Visions Lighting and Video
www.EsotericVisions.com
A/V/L designers, installers, and integrators for churches. 10+ years of industry experience.
Reply With Quote Start a New Topic From This Comment
  #3 (permalink)  
Old Thursday, October 7th, 2010, 09:34 PM
Paris MkVI's Avatar
Official Player-With-Toys

 
 Join Date: May 2008 
 Last Online: Today 
I firmly believe in letting the task define the tools. Sometimes it is absolutely essential, especially in media.

And I don't just mean video. Just turn your graphic artist loose on an underpowered system with inadequate storage and RAM and then make them turn stuff out in Photoshop and other apps. Watch their hair turn gray and fall out. Watch them age before your eyes. Hear them growl to themselves when they leave for the day to go home and get the job done on a decent machine on their own time.

Let the task define the tool.
Reply With Quote Start a New Topic From This Comment
The Following User Says Thank You to Paris MkVI For This Useful Post:
jksbc (Wednesday, October 13th, 2010)
  #4 (permalink)  
Old Tuesday, October 12th, 2010, 09:58 AM
Toetagger's Avatar
Church Media Regular

 
 Join Date: Nov 2009 
 Last Online: Thursday, May 10th, 2012 
I think a hybrid approach would be best. Meaning there is an allowance but maybe 2 or 3 options to choose from with the option to "build your own". Meaning if someone doesn't know what to pick they can just order something premade but someone who is tech savvy can go get something that meets the requirements and tailors to their specific needs and/or preferences.
__________________
Justin - GatewayLife Church
Sound, Lighting, and Media Volunteer
Reply With Quote Start a New Topic From This Comment
  #5 (permalink)  
Old Friday, April 29th, 2011, 01:59 AM
New Church Media Member

 
 Join Date: Apr 2011 
 Last Online: Friday, April 29th, 2011 
Keep on updating on dis...
Reply With Quote Start a New Topic From This Comment
  #6 (permalink)  
Old Friday, April 29th, 2011, 10:36 AM
Church Media Regular

 
 Join Date: Feb 2006 
 Last Online: Monday, May 21st, 2012 
We have a stepped approach. It takes a bit more energy to keep up, but here is how it goes:
Power users get their desktops/laptops replaced every 2-3 years depending on machine and software. When it is time for their CPU's to be replaced the latest and greatest is purchased and their "old" machine gets moved to the 2nd level with is the almost power users. Those are the people who don't need as fast of machines, but often do a lot of repetitive tasks(database searches, web updates, etc.). Then we move the next machines down to those that just do admin work, volunteer stations or we donate the boxes to charity.

The key to this type of setup is having a really thought through plan. We choose not to give allowances based solely on one thing: what happens when that video editor leaves? The church could have dropped $5-10k one one machine and software. Once they are gone, how do you get the software or machine back based on a 3-5 depreciation schedule. Some software is way cheaper for a non-profit (Adobe has great deals on their non-profit stuff), but it can't be loaded on a personal machine and can't be given away as per their EUL.

It seems to me like technology allowance is great for PDAs (what are those again?!), cell phones, iPad's, etc. but not for computers and software.
Reply With Quote Start a New Topic From This Comment
Reply

  The Church Media Community > Teams & Leadership > Leadership Issues

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:



Add to Google


Register Now for FREE!
Our records show you have not yet registered to our community. To sign up for your FREE account INSTANTLY fill out the form below!

Username: Password: Confirm Password: E-Mail: Confirm E-Mail:
Agree to forum rules 


All times are GMT -6. The time now is 09:55 PM.

   
 
© 1995-2008, ChurchMedia™, ChurchMedia LLC

SEO by vBSEO 3.1.0