• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 418
  • Last Modified:

Policy Management

What is the problem with having departmental policies as opposed to corporate policies? I am on about any information management or information security policy - any IT related policy to be honest, but specifically stuff like information classification, data retention, records management, media sanitization etc etc. Where is the issue in each department having their own responsibilities to have such policy and procedures in place as opposed to corporate policies that mandate what each organisational department will do? I know it should be corporately dictated as opposed to departmentally but I am struggling to find some good justified reasons why – despite searching. Would prefer your comments as opposed to links.
0
pma111
Asked:
pma111
1 Solution
 
michkoCommented:
Imho, one main reason for corporate policies over departmental policies.  Consistency - across the board.

Organizations run easier if rules and guidelines are similar across the various departments.  It eliminates (or reduces) confusion and misunderstandings.  It also allows for easier transfer/temp placement of personnel.

Granted, some departments will have special requirements that may be more stringent than those required by the company as a whole - take those on a one by one basis.

For example - IT purchase policy.  You want to try to standardize on one model/type of hardware with a standard software configuration.   This makes supporting those desktops a lot easier.  If you let individual departments determine what to purchase, then your support becomes much more difficult.

I work for a municipality, but the idea can be extended to the corporate world.  Let's say we let our Police and Fire departments each purchase hardware/software on their own.  What happens if they don't coordinate with each other?  Or agree with the best route to take?  Next thing you know, we are trying to support two completely separate systems that are supposed to communicate with each other - and most likely don't.  

However, I also need to be flexible enough to realize not every department is going to fit a standard mold.  The workstations needed for our Marketing department, who frequently create publications, flyers, work with large image files, etc., are completely different from those needed for most of our other employees in Finance, HR, etc.  So, set the generic configuration across the board at the typical user level - then beef up the machines for those positions that require something more.

The same idea goes for records retention, etc.  Set the policy at the corporate level, and the exceptions at the department level.  It really does make things much easier, rather than having 15 separate departments all going their own way without any common thread.

Hope that helps.

0
 
pma111Author Commented:
Great advice, thank you its much appreciated
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now