Re: Survey: Who Uses GNOME

From: houghi (houghi_at_houghi.org.invalid)
Date: 03/09/05

  • Next message: houghi: "Re: Firewall"
    Date: Wed, 9 Mar 2005 01:20:59 -0000
    
    

    Gonzalo wrote:
    > To say that they found it easier to use because they were accustomed to
    > Windows might be valid, but that in itself is not a negative thing and
    > greatly oversimplifies the issue. Even if this was the only advantage, most
    > organizations can do without the additional retraining costs.

    Oh. I know that. That is what I wanted to say. If you would have done
    the test between KDE and Windows, then Windows might have been the
    prefered thing as that is what they already know.

    I personally HATE the mac desktop. The time I used it, nothing did what
    I expected it to do and I was experienced with both Windows and Linux at
    that time.

    > What we wanted to test essentially is whether the idea of the Linux desktop
    > was feasible for the selected group and by feasible we meant whether it
    > could be done without having to increase the in-house support staff of the
    > organization or without any decrease in productivity.

    Pitty you are not allowed to disclose that information as it could be
    only good for the company if they were more open about it.

    > To our satisfaction,
    > the users in the pilot project have become the biggest advocate for change
    > within the organization and we are already seeing big savings.

    That is true with ALL management decisions. Let staff participate or at
    least let them have the idea they participate. Let management take the
    large decisions (we are going to use Linux) and then ask staff for input
    on level of what the desktop should be like, what the colors should be
    like and what icons should be used.

    If you do that cleverly and with a somewhat open attidude to your staff,
    you will have followers that you can not believe.

    If directed corretly, they will come with solutions you and the
    management never thought of instead of working with some droids who do
    things 'because that is how we did it for years'.

    If you think that your staff is not able to make certain decisions, you
    have hired the wrong staff.

    -- 
    houghi		Please to not toppost			http://houghi.org
    						  My experience with SUSE
    You can have my keyboard ...
    		      if you can pry it from my dead, cold, stiff fingers
    

  • Next message: houghi: "Re: Firewall"

    Relevant Pages

    • Re: Funny - any comments?
      ... wanted to approach management about this issue. ... > is better than a slapped together system where IT staff simply must know ... >> The actual issue is the Exchange email server is in one Windows ... If absolutely necessary, the admin could ...
      (microsoft.public.security)
    • Re: Whats the best practice-2 companies, 2 cities and 1 email address
      ... In city A with about 250 staff ... Client is MS Office 2003 on Windows XP ... Client is MS Office 2000/2003/2007 and etc on Windows XP/Vista ... Keep the content in old mailbox in the new ones ...
      (microsoft.public.exchange.design)
    • Re: Windows Training issue
      ... However the problem I have is not so much in explaining to the staff how ... Windows Shell/User ... Organise the Windows environment including administrating user ... Understand the concepts and issues behind the simple networking ...
      (microsoft.public.windowsxp.general)
    • Re: Windows Training issue
      ... However the problem I have is not so much in explaining to the staff how to ... Windows Shell/User ... Organise the Windows environment including administrating user ... Understand the concepts and issues behind the simple networking ...
      (microsoft.public.windowsxp.general)
    • Re: Need advice on limiting logins by users
      ... Cris Hanna [SBS - MVP] ... Windows Small Business Server 2008 Unleashed ... We have 4 PC's in a work room for projects, temp staff, etc. and the ... staff member will take them in and login with their login info and go back ...
      (microsoft.public.windows.server.sbs)