Understanding the differences between the System Administrator and the Power User is essential to successful technology integration.

I've heard the complaints over the years about the evil power mongers known as sysadmins. I've read many articles complaining about company IT departments that unfairly lock down workstations so users can't install software.  The articles are often written by disgruntled power users wondering why they have the latest and greatest applications at home, but work for companies that force employees to use clunky programs.

This series on technology management helps business professionals to better understand technology management in a business network. It also hopes to give the average network user an appreciation of the reasons behind the decisions made in managing the business computer network.

The Systems Administrator

On a small to mid size network there may be little, if any, distinction between a systems administrator and a network administrator. The tasks may all be the responsibility of a single post. As the size of the network grows, the distinction between the areas will become more well defined.

In larger organizations the administrator level technology personnel typically are not the first line of support that works with end users, but rather only work on break and fix issues that could not be resolved at the lower levels.

Network administrators are responsible for making sure computer hardware and the network infrastructure are maintained properly. The typical systems administrator, or sysadmin, leans towards the applications (software) and OS (Operating System) side of things.  Systems administrators install software releases, upgrades, and patches, resolve software related problems and performs system backups and recovery.

The Power User

A power user is typically someone who has above average experience with computers and utilizes many advanced features of applications. They may also have experience with multiple computer platforms as well, such as Linux or Mac, in addition to Windows.  The tech savvy power user, who is used to tinkering with applications on a home network, often becomes frustrated when forced to use computers or applications at work that are slower and older than the computers they use at home.

Don't confuse the term power user here with the "Power Users" group on older versions of Microsoft Windows, which attempted to define a system that gives more permissions than a normal restricted user, but stops short of Administrator permissions.  The Windows Power User group has been dropped in more recent versions of Windows. I guess even Microsoft realized that trying to put a definition on power user was a difficult proposition.

Can you see the forest for the trees?

The power user sees the tree. They focus on how much can they do with a single computer. Power users will often compare the speed of using their Mac or Linux based computer at home, and wonder why they can't use their personal non Windows based computers at work.

The power often looks at troubleshooting network problems in the context of their home network of three computers.

The system administrator sees the forest. They focus on how well the computers work together as a system. An application that works well at home on your personal computer has to work well as part of a team of computers, communicating, sharing files between a large number of users.

The system administrator deals with troubleshooting network problems in the context of dozens, or even hundreds of computers using a network resource on a continuous basis. Every action they take is in the context of how it will effect many users.

The answer to simple network management is not the most popular

Unfortunately there is often tension between computer users and IT departments in the workplace. System administrators are demonized for unpopular choices in workplace technology beyond their control.

System administrators are under management pressure to contain costs. While many users wonder what is the harm in installing free software, cutting costs does not always mean replacing expensive software with open source software or freeware. 

Sysadmins need to understand the behavior of software and tasks performed by the software in order to deploy it and to troubleshoot problems. Compatibility problems constantly pop up, and problems with having untrained users sharing files between types of software can create time consuming training issues.

System administrators are often limited in terms of time and resources.  Often a business uses a core piece of software that dictates or limits what operating system can be used, and at times prevents upgrades to more modern operating systems or web browsers.

Writing about technology has given me the opportunity to address many questions heard over the years, and hopefully create a better understanding of technology issues from various points of view

Tags: 

• stereotypes
• systems administration
• technology
• management

Understanding the differences between the System Administrator and the Power User is essential to successful technology integration.

I've heard the complaints over the years about the evil power mongers known as sysadmins. I've read many articles complaining about company IT departments that unfairly lock down workstations so users can't install software.  The articles are often written by disgruntled power users wondering why they have the latest and greatest applications at home, but work for companies that force employees to use clunky programs.

This series on technology management helps business professionals to better understand technology management in a business network. It also hopes to give the average network user an appreciation of the reasons behind the decisions made in managing the business computer network.

The Systems Administrator

On a small to mid size network there may be little, if any, distinction between a systems administrator and a network administrator. The tasks may all be the responsibility of a single post. As the size of the network grows, the distinction between the areas will become more well defined.

In larger organizations the administrator level technology personnel typically are not the first line of support that works with end users, but rather only work on break and fix issues that could not be resolved at the lower levels.

Network administrators are responsible for making sure computer hardware and the network infrastructure are maintained properly. The typical systems administrator, or sysadmin, leans towards the applications (software) and OS (Operating System) side of things.  Systems administrators install software releases, upgrades, and patches, resolve software related problems and performs system backups and recovery.

The Power User

A power user is typically someone who has above average experience with computers and utilizes many advanced features of applications. They may also have experience with multiple computer platforms as well, such as Linux or Mac, in addition to Windows.  The tech savvy power user, who is used to tinkering with applications on a home network, often becomes frustrated when forced to use computers or applications at work that are slower and older than the computers they use at home.

Don't confuse the term power user here with the "Power Users" group on older versions of Microsoft Windows, which attempted to define a system that gives more permissions than a normal restricted user, but stops short of Administrator permissions.  The Windows Power User group has been dropped in more recent versions of Windows. I guess even Microsoft realized that trying to put a definition on power user was a difficult proposition.

Can you see the forest for the trees?

The power user sees the tree. They focus on how much can they do with a single computer. Power users will often compare the speed of using their Mac or Linux based computer at home, and wonder why they can't use their personal non Windows based computers at work.

The power often looks at troubleshooting network problems in the context of their home network of three computers.

The system administrator sees the forest. They focus on how well the computers work together as a system. An application that works well at home on your personal computer has to work well as part of a team of computers, communicating, sharing files between a large number of users.

The system administrator deals with troubleshooting network problems in the context of dozens, or even hundreds of computers using a network resource on a continuous basis. Every action they take is in the context of how it will effect many users.

The answer to simple network management is not the most popular

Unfortunately there is often tension between computer users and IT departments in the workplace. System administrators are demonized for unpopular choices in workplace technology beyond their control.

System administrators are under management pressure to contain costs. While many users wonder what is the harm in installing free software, cutting costs does not always mean replacing expensive software with open source software or freeware. 

Sysadmins need to understand the behavior of software and tasks performed by the software in order to deploy it and to troubleshoot problems. Compatibility problems constantly pop up, and problems with having untrained users sharing files between types of software can create time consuming training issues.

System administrators are often limited in terms of time and resources.  Often a business uses a core piece of software that dictates or limits what operating system can be used, and at times prevents upgrades to more modern operating systems or web browsers.

Writing about technology has given me the opportunity to address many questions heard over the years, and hopefully create a better understanding of technology issues from various points of view

Tags: 

• stereotypes
• systems administration
• technology
• management

Some people are constantly worried about making the right technology decision. They are always looking for the right time to buy technology, and for them, now is never the right time. They worry that price drops are just around the corner. They worry that new technology will make their new tools obsolete too soon.

Technology is a fast paced business, price drops are always around the corner, and new tools that make your purchase obsolete are inevitable. Don't  let fear of making a bad decision slow you down, or prevent you from making a decision.

Refusal to accept basic assumptions

Everything we do is assuming something, like when we drive, we assume the car coming at us won't swerve and crash into us, your monitor you are looking at won't explode in your face, the food you eat isn't poisoned, the person next to you in Wal-Mart won't stab you. Everything we do starts with a basic assumption.

The world is full of experts that self proclaim themselves as masters in some area of technology simply because they use a buzzword to describe some technology product or feature. But there also comes a point in time when you need to seek out someone you can trust, someone who understands your needs and your situation.

I have worked on both sides of the fence, as service technician and technology consultant representing a service provider, as well as a technology specialist and systems administrator servicing a network. In the pages of the Guru 42 Universe we do what we can to help you look at things from different perspectives to better understand and appreciate how things work in the world of technology.

As a service technician or technology consultant representing a service provider, you sometimes run into clients who ask for help, but refuse to accept advice you have to offer.

It is natural for us to get angry at others when they make an assumption that results in our inconvenience, but we have to remember everything we do is based on an assumption of some sort. Unless I have reason to believe otherwise, I assume that someone is acting in good faith. Keep in mind that these remarks are coming from someone who is often called cynical.

Open source projects, such as Wikipedia are based on the fundamental principle of "assume good faith." Wikipedia states the importance of the principal as follows, "In letting anyone edit, we must believe that most people who work on the project are trying to help it, not hurt it. If this was not true, a project like Wikipedia would not work."

The refusal to accept a basic premise and the need to gather more data beyond a reasonable means leads to various states of mental anguish for management


The Gilligan's Island Syndrome

The premise of the 1960's television sitcom "Gilligan's Island" is a charter boat is on a "three-hour tour" and runs into a tropical storm and gets shipwrecked on an uncharted island somewhere in the Pacific Ocean. What was meant to be a "three-hour tour" turns into a life long adventure.

In the business world many companies suffer from "The Gilligan's Island Syndrome." That is when a decision that should take three hours, turns into a life long adventure. The "Gilligan's Island" television sitcom was a funny show, and was of course, fictional. For many businesses, "The Gilligan's Island Syndrome" is very real, and very sad.

Paralysis by Analysis

A mental affliction which sometimes develops in an individual after prolonged exposure to the "The Gilligan's Island Syndrome" is "Paralysis by Analysis." This affliction is characterized by the constant need for information in any and all decision making.

Sadly enough "Paralysis by Analysis" becomes the negative mechanism for justifying no action being taken, under the misguided philosophy that you can't make a wrong decision if you make no decision.

There's a big difference between going with the flow and being too paralyzed to go anywhere. It is fine to gather information, but true leadership is about being decisive, coming up with a firm decision and sticking with it.

Wasting time

I have many personal stories of The Gilligan's Island Syndrome and Paralysis by Analysis from working in the business world as well as from the realms of schools and government. Many times the over analysis is done in the name of saving money. So a person is tasked with spending days to find the lowest of a product or service. Even if you forget for a minute that the lowest cost is not always the best value over time, how can you justify a significant amount of time used to analyze a purchase in order to save a few dollars.

Once a minute is wasted, there is no way to re-live it, no one to borrow it from. Time is more valuable than money, use it wisely.

Many times the over analysis is done in the name of saving money. So a person is tasked with spending days to find the lost of a product or service. Let us forget for a minute that the lowest cost is not always the best value over time. Often a significant amount of time is used to analyze a purchase in order to save a few dollars.

Wasting time can be far more devastating than wasting money. Wasting time almost always directly relates to a waste of money.

Think about it. But don't take too long. True leaders have the ability to make decisions quickly and effectively.
 

"Anyone who has never made a mistake has never tried anything new." — Albert Einstein

Save

Save

Save

Save

Tags: 

• technology
• management
• small business
• project management
• computers

Some people are constantly worried about making the right technology decision. They are always looking for the right time to buy technology, and for them, now is never the right time. They worry that price drops are just around the corner. They worry that new technology will make their new tools obsolete too soon.

Technology is a fast paced business, price drops are always around the corner, and new tools that make your purchase obsolete are inevitable. Don't  let fear of making a bad decision slow you down, or prevent you from making a decision.

Refusal to accept basic assumptions

Everything we do is assuming something, like when we drive, we assume the car coming at us won't swerve and crash into us, your monitor you are looking at won't explode in your face, the food you eat isn't poisoned, the person next to you in Wal-Mart won't stab you. Everything we do starts with a basic assumption.

The world is full of experts that self proclaim themselves as masters in some area of technology simply because they use a buzzword to describe some technology product or feature. But there also comes a point in time when you need to seek out someone you can trust, someone who understands your needs and your situation.

I have worked on both sides of the fence, as service technician and technology consultant representing a service provider, as well as a technology specialist and systems administrator servicing a network. In the pages of the Guru 42 Universe we do what we can to help you look at things from different perspectives to better understand and appreciate how things work in the world of technology.

As a service technician or technology consultant representing a service provider, you sometimes run into clients who ask for help, but refuse to accept advice you have to offer.

It is natural for us to get angry at others when they make an assumption that results in our inconvenience, but we have to remember everything we do is based on an assumption of some sort. Unless I have reason to believe otherwise, I assume that someone is acting in good faith. Keep in mind that these remarks are coming from someone who is often called cynical.

Open source projects, such as Wikipedia are based on the fundamental principle of "assume good faith." Wikipedia states the importance of the principal as follows, "In letting anyone edit, we must believe that most people who work on the project are trying to help it, not hurt it. If this was not true, a project like Wikipedia would not work."

The refusal to accept a basic premise and the need to gather more data beyond a reasonable means leads to various states of mental anguish for management


The Gilligan's Island Syndrome

The premise of the 1960's television sitcom "Gilligan's Island" is a charter boat is on a "three-hour tour" and runs into a tropical storm and gets shipwrecked on an uncharted island somewhere in the Pacific Ocean. What was meant to be a "three-hour tour" turns into a life long adventure.

In the business world many companies suffer from "The Gilligan's Island Syndrome." That is when a decision that should take three hours, turns into a life long adventure. The "Gilligan's Island" television sitcom was a funny show, and was of course, fictional. For many businesses, "The Gilligan's Island Syndrome" is very real, and very sad.

Paralysis by Analysis

A mental affliction which sometimes develops in an individual after prolonged exposure to the "The Gilligan's Island Syndrome" is "Paralysis by Analysis." This affliction is characterized by the constant need for information in any and all decision making.

Sadly enough "Paralysis by Analysis" becomes the negative mechanism for justifying no action being taken, under the misguided philosophy that you can't make a wrong decision if you make no decision.

There's a big difference between going with the flow and being too paralyzed to go anywhere. It is fine to gather information, but true leadership is about being decisive, coming up with a firm decision and sticking with it.

Wasting time

I have many personal stories of The Gilligan's Island Syndrome and Paralysis by Analysis from working in the business world as well as from the realms of schools and government. Many times the over analysis is done in the name of saving money. So a person is tasked with spending days to find the lowest of a product or service. Even if you forget for a minute that the lowest cost is not always the best value over time, how can you justify a significant amount of time used to analyze a purchase in order to save a few dollars.

Once a minute is wasted, there is no way to re-live it, no one to borrow it from. Time is more valuable than money, use it wisely.

Many times the over analysis is done in the name of saving money. So a person is tasked with spending days to find the lost of a product or service. Let us forget for a minute that the lowest cost is not always the best value over time. Often a significant amount of time is used to analyze a purchase in order to save a few dollars.

Wasting time can be far more devastating than wasting money. Wasting time almost always directly relates to a waste of money.

Think about it. But don't take too long. True leaders have the ability to make decisions quickly and effectively.
 

"Anyone who has never made a mistake has never tried anything new." — Albert Einstein

Save

Save

Save

Save

Tags: 

• technology
• management
• small business
• project management
• computers

Our goal in writing the "Beyond Great Ideas and Good Intentions" series of business lessons and lectures was to look at the mindset that creates success. In the process of identifying challenges in information technology success it is equally important to take a look at the attitudes that cause negative results and the perceptions of failure. 

I was closely following a major system upgrade in an online forum where end users were voicing their frustrations over a project that was bringing workflow to a standstill. The end users saw an application that was "just working fine" before the upgrade. With the upgrade underway end users were screaming about a technology support department that was not keeping up with resolving problems.

One of the end users stated that the changes made "were probably because of those IT types that want something new to tinker with." I was not an employee of the technology department making the changes, but as an outside observer with a fair understanding of the software involved, I had some good ideas of what was happening. The end users were speculating on the reasons for the changes because management was not addressing many of the issues they were facing.

Very often those "IT types" do not have the ultimate say in what gets implemented and when. I can say that with certainty from first hand experience from working in many different areas of technology. It is really frustrating to see remarks from end users unhappy with changes that are often beyond the control of the IT department. I really felt bad for the IT department that was caught in the cross fire between a mob of angry end users frustrated with a sea of problems and an overly ambitious management releasing untested bleeding edge technology that was not willing to address the issues.

The Perils of Project Management by Committee

For many IT Managers, there too many cooks in the kitchen telling them what kind of soup to cook. How would you like to be responsible for cooking the soup, and not even being allowed to shop for your own ingredients?

In many cases choices are influenced by non technical departments and the decisions are based on some form of committee not controlled by the technology department.

As the old joke goes, if a camel were designed by a committee it would have 12 humps.

Blame Everything on the IT Department

As someone who has been in the technology field for many years, I will tell you point blank, seasoned IT professionals do NOT want something new to tinker with when it comes to a production network or system. Seasoned IT professionals err on the side of caution when it comes to adding something new or changing anything. We understand that change, any kind of change that has an impact on end users, will create headaches.

The personal anecdotes in this section on the quest for business success are based on a long and diversified career helping a variety of business people integrate technology into their business. Sadly, I have seen first hand many technology decisions made for reasons other than technology.

When things don't turn out as expected, the IT department takes the blame.

Expectations and responsibility

In a recent forum post on the internet a person posted that they are looking for a piece of business software with "everything into one program."

If you are a small business shopping for some software, first thing you need to do is define "everything." Starting on a piece of paper, write down your thoughts. Start your technology planning as a list of tasks. You are going to need to break down you question into individual tasks.

People end up being very disappointed and even angry when they actually start to work with technology because it isn't what they thought it would be. It is good to set expectations first because you may be surprised as to things you can do.

There is not a one size fits all solution, and there is not a one application does all answer. Once you have a list of tasks, you can start shopping for software. Once you understand all the things you want to do, you can now start shopping for solutions with a new set of questions in mind.

Why Do Technology Projects Fail?

As a technology coordinator and systems administrator I try to focus technology conversations on the question, "What exactly is it that you are trying to do?"

One of the biggest challenges in information technology success is setting proper expectations for its use. Going back to my experiences with the introduction of microcomputers to schools and businesses in the early 1980s, I saw many instances where computers were installed without clear goals for their use.

A popular expression is that a little knowledge is a dangerous thing. We address that theme in various ways throughout the Guru 42 Universe. In some of the articles that follow we address the unfortunate stereotypes of technology professionals created by self proclaimed tech-savvy users.

The ability to drive a car does not make you an automotive expert. That analogy holds true as the use of technology has become mainstream, creating a world is full of "experts" that self proclaim themselves as masters in some area of technology simply because they know a buzzword to describe some technology product or feature.

As a business manager you have the expectation of having the tools available to you whenever you need them. Technology is a tool that can help solve many problems. Even the casual end user of technology for entertainment or communication purposes has the expectation to have their toys available to them. Losing access to our geek tools and toys is a major cause of concern because everyone has become so dependent on technology.

Business owners and managers have the responsibility of working with professional geeks such as system administrators to provide them with the tools and support they need to deal with global infrastructure headaches and constant security threats. End users have the responsibility of understanding the goals of the system administrators and supporting them by following the rules and not adding to the issues that can create problems.

 

“If you don't know where you are going any road can take you there” .. Lewis Carroll, Alice in Wonderland

 

 

Save

Tags: 

• Business
• success
• inspiration
• technology
• management