92 replies
by jdmercha
by inno4te
by jsdutcher69
by lisa.stanley
by ole88
by dcduring
by pam.reilly
Policies should definitely be developed by both IT and management together. The specific involvement of each should depend on the capabilities of each. For example, more IT involvement will be required when the IT manager is not himself an IT person. Companies that have a legal department should definitely get legal input as well.
If technical writers are available, I agree with other comments that the final document should be at least edited and formatted by them.
by jamesrl
If you are looking at pushing back on your manager, thats not an issue we can help you with. I hope you are dialouging with your manager on this kind of issue.
The duties of a manager and the duties of an employee vary infinitely from company to company, and indeed from department to department. I certainly wrote policies and procedures when I was a technical specialist. Management was responsible to provide feedback on those policies, and to get buy in from HR. But I wrote them.
As a manager currently, I do some technical tasks that could easily be done by one of my employees. I choose to do them. Thats my perogative. And if I chose to delegate them at some point, thats also my perogative. I only hope that what I do makes sense and helps the company.
You sound like you have a chip on your shoulder regarding your manager. None of us here can help you with that. Perhaps you aren't aware of all the tasks assigned to that manager, or perhaps you don't have an effective or efficient manager - we can't help you with that.
James
by jamesrl
This is NOT the scenario where the rogue sys admin is setting policy all on his lonesome. This is a situation where the manager has directed the sys admin to craft the wording of the policy - the manager has obviously given guidelines, though only the original poster can tell us whether they got enough detail to work with.
Don't presume you are the only one with 20 years experience. I have been in IT that long as well. And I have written policies both as a manager and as non-management. In the case of a non manager, you can craft the wording, but someone in management needs to approve it, and seek approval from all appropriate stakeholders. The frustrating part that I can relate to from the original posters perspective is that if you aren't given specific enough guidance it can be a long frustrating process.
Emotionally crippled sociopaths?? Surely you exagerate when you say most.....
James
by paul
Systems Admin's "20 Years Ago" can't even be compared. Hell, 20 years ago very few organisations had IT to the desktop, thus policy was hardly a prime consideration.
I am now a consultant, so have been out of the front line for a year or so. However, in my last few IT Director roles, I always wrote policy in conjunction with my team. My contribution was primarily on behalf of the business, and I wanted to see active participation from my team with suggestions and stories from the "front line" that could influence the policy.
Sure, you do get over-zealous net admins, but they can be told pretty effectively not to take that approach.
FYI - In my last role, we trimmed the IT usage policy down from a small novel into a leaflet, removed a lot of the "treat staff like small children" feel from it, and ended up with a far happier user base with far less problems and systems abuse.
Paul
by dafe2
Your right, managements role is the approval or re-write.
Management & the executive will be the one's responsible for policing, enforcing & educating on both.
by awfernald
will utilize all the expertise (including the grunts) available to craft intelligent policy. It doesn't make sense to dictate policy that will be ignored or that can't be followed for some reason.
The grunts should reply to the policy with the procedures they use to actually implement the policy. If you do this correctly, you won't actually be implementing new policies or procedures, simply documenting the existing ones (unless there is a need to change them).
by liame
Yup... and if that policy that the manager makes involves a subordinate writing up policies then they do it. Period.
Just because management set policy doent mean they have to be involved in drafting it. Policies dont get written in a few minutes by one person in my experience. A typical process would be something like - subordinate drafts and then discusses with manager. Revisions made by subordinate. Manager then takes the document to the other parties (eg HR, VP/CIO etc), revise again as necessary and then finalise. Document signed off by the big cheese.
The wording of the question strongly suggests the question setter has an issue with their boss and their (perceived and/or real) workloads. It sounds like they feel put upon and this question is a symptomatic not the real heart of the issue for them.
by net designer
by tonythetiger
by notsochiguy
Yes, the way it was dumped on you sucks. Yes, ideally, you would have more than just one person's input. Yes, policies really should be management driven. However, I would urge you to look at the positives:
You've been given an opportunity to outline the way you think things should be. Start thinking about some things that detract from your work (personal PC work requests, non-standardized equipment,virus cleanups, etc), and find a fair way to work them into the policy. Just be sure to only include items that you could reasonably defend, if called on it.
Even if you supervisor doesn't show it/say it, the fact he dumped this on you shows he has, even unconsciously, the faith that you can get this done (I am open to the possibility he is just oblivious to the importance of this, though).
If you have company policies on other facets of the business, I'd encourage you to take a look at them. In the policy you create, try to emulate the tone and nature (general terms vs. specific, normal language vs. legalese, etc) of those policies. Company policies tend to reflect the company culture, so you'll want to make sure your's fits in accordance to what is already out there for your outfit.
Also, if you are having trouble, there are a lot of templates available out on the web you could peruse (although I haven't looked for any in particular, I'd wager there are some on TR). Looking at these may help you keep from adding too much to your policy.
If you really want to get perspective on this, get up from the desk, go walk around the office, and pay attention to all the non-essential, non-standard stuff going on and think about what you can do about it.....
Are you back? Feel better? ;)
by net designer
by it_lobo
Have you looked at the one TechRepublic has in the downloads??
https://www.techrepublic.com.com/5138-10634-5549585.html?tag=search
You wrote "This is NOT the scenario where the rogue sys admin is setting policy all on his lonesome."
I didn't say it was. I said that the issue at hand is who is responsible for writing policy.
You wrote "This is a situation where the manager has directed the sys admin to craft the wording of the policy - the manager has obviously given guidelines, though only the original poster can tell us whether they got enough detail to work with."
How did you interpret the original post to say anything like that? Your entire assertion is derived from your imagination. The original poster said nothing of the sort.
You wrote "Don't presume you are the only one with 20 years experience."
I didn't presume anything of the sort. I was making the point that I am not a kid fresh out of school and that I have decades of office experience. I didn't say anything about being the only person with relevant experience. Again, your interpretation is derived strictly from your imagination.
You wrote "In the case of a non manager, you can craft the wording, but someone in management needs to approve it..."
I agree. That is my position as well.
So, why did you originally enter a post telling everyone not to participate in this discussion? That was my question to you in my response to your post and you completely failed to address that issue in your reply.
by tonythetiger
Now that you point it out it is clear to me. He was saying that there isn't one single answer.
Okay. In that case forget everything that I said related to his post.
Well this is embarassing enough. I'm just glad that I didn't include a lot of flame-o-matic phrases.
set by management, Procedures by those who have to implement them.
The policy can be very vague, like a mission statement. This is a help though, because it means you can justify the procedures you want against the policy.
Personally I favour no implementatioon details in the policy. You will meet legislative requirements, support the business function etc.
Procedures should be made and managed by the team. The last time I did this sort of thing, the manager never went near the content of the procedure, the only thing he cared about was that they implemented the policy.
What's the big issue at the monent in the department. Write a draft that could be seen to implement the vague appreciation you have of company policy your manager has given, then have him review it.
In your position I'd consider this a heaven sent opportunity to shine, but I like it when everybody in the company knows who I am. I don't care that they don't like what I've done, to chnage it all they have to do is get off their ass and contribute.
by tomsal
I know it seems obvious to many that the IT manager would make the policy, but its not so clear cut at some companies. Like this one for instance the "top" IT guy is also involved in overseeing the total operations of the business and he has little time to spend on IT policy by himself and to be honest, its more towards the end of his priority list than the top.
So what we do is approach it as a team effort. Then we logically talk about it what is going on in the company, where we feel we are exposed to vulnerabilities and lack of legal coverage (ie. no copying software, downloading unlicensed content, etc.).
For one policies aren't static, some things will stay the same of course, but other areas of policy adapts with time and newer technologies. The techs (me being one) know HOW AND WHY stuff works better than anyone else in the company so its logical to have their (our) input when dicussing IT policies.
by tonythetiger
by tomsal
True. We provide services for the benefits of the other departments. Let's face in IT our customer is literally our fellow associates in all the other departments.
However when the subject is IT policy, certainly the other departments can't (or at least they shouldn't be allowed to) write the policy. That's like them writing their own rules for what they can download, the extent of freedom they have with surfing the web, etc.
I think IT policy should be drafted in the IT department, then passed to management for review, editing, approval, then IT finalizes it.
by jamesrl
I've been flamed by Snopes.....
Now he can flame.....
If you want details you can google alt.folklore.urban, my name, and look for the posts in 1993 and 1994.....
Snopes stopped posting there a few years later.
James
Policy writting is a management responsibility and the current management best practices and theory is that the manager for the area that has responsibility for that material is the one to write the policies for that area / subject. Thus the IT manager is responsible for writing the IT policies; a good manager will then give them to their line managers/supervisors for comment and feedback as they may note operational aspects that the manager missed.
I have both management and IT qualifications and have worked in both general management and then IT.
NB: I am on a 24 kbps line and did not read all the responses already given, so if I am repeating another response - sorry.
by liame
Look at it this way, think what the company wants from the policy and write up something quick and rough. Talk to any 'stakeholders' you can get hold of for 5 minutes and ask them what they want out of the policy.
If your manager has not given you input into what the policy should contain go ahead and find out for yourself. You may well find that he is under pressure to have a policy in place more to put a tick in a box than to actually manage anything.
by hockeyist
In my experience it's the leaders who write policy & procedures and it's managers who approve and enforce them.
Are you a leader?
by no1trini
by tonythetiger
Procedures enact policy. They should always be written for the people who have to do them, therefore it's a lot more practical for the people who have to use them to write them. You get buy in and ownership that way, not to mention no excuses about unworkable ones.
Unworkable policy is a different matter entirely.
by tonythetiger
by jamesrl
The IT department provides services on behalf of the company. The IT department has a responsibility to ensure that the company's resources are wisely used, and the HR policies (no porn) can be enforced.
The IT department often is charged with giving information to the user's supervisor or to HR. What they chose to do with the information is not up to IT.
James
by tomsal
The IT department, I contend, does have something to do with policy concerning the companies technology as one of the large reasons a company pays for IS staff is to not only configure and maintain the technology but to prevent it from failing and securing it against threats.
Example of what I mean...Regardless if a manager, hell if an executive gives authority for someone to go to whatever site or do whatever online -- if there is reason for the IS department to suspect the system will be comprised either by being hijacked or virus infection -- IS over-rides the authority of even the executive.
That's one thing about here, you guys heard me sound off a lot, but at least that is one thing my place understands. I've even stopped the owner of the place from going to a site because of the threat it poses to our network.
He didn't get upset (well a little at first) after I explained and told him why my concern. Then he was fine by it because he at least knows enough that that's one of the reason he pays me.
So yeah...in 9 out of 10 cases IS has no say, but in that 10th case where there is a threat involved..IS has every right to over-ride even the higher ups.
Just make sure you give as much factual information as possible to explain your reasoning and communicate it without emotion.
by wordworker
...a committee with at least one representative from Network Admin, Data Network Services, Development, Help Desk, Infrastructure, Telecommunications, IS Security, Database Administrators, and any other group on your IS org chart.
Once the "ground level" soldiers on the Security Policy Committee agree on what policies should be written in the first place, and on how each policy should be worded, then those documents should be presented to IS Senior Management.
Once IS Senior Management approves the policies, they must be communicated OUT to the lines of business, or they're not worth the paper they're printed on.
Well written policies, with revision tables showing when they were drafted and each time they were reviewed and revised, will come in very handy for companies facing SOX or HIPAA compliance audits. Auditors will ask: What's your policy? How are you enforcing it? Where's the proof that you're enforcing it?
by jamesrl
You would have all of that and more (HR should be involved in policies, because they deal with the consequences).
But not every organization has all these types of people. I worked in a large corporation with an IT department of 5000, and there were no Technical writers.
There should be feedback from stakeholders, including internal user groups if they exist.
As far as communicating, at a previous employer we had a good policy. You had to sign a document acknowledging the policies and the consequences(up to and including termination) before you had a network ID and password given to you.
James
by net designer
and get thoroughly confused on a regular basis.
I was one for about four years until an audit where they made me into four people with same name each doing a part time job.
by bhunsinger
Cobble together a policy, by stealing one from TR
Then get buy in from the other people.
Procedures; assmue that your manager has just asked you to stop the B$ that wastes your time and list all the things you would stop, But
ask for buy in.
Start what should be a dialogue on your term s and let them convince you.
by pam.reilly
Policies should be defined at the interface between general
management and IT: that is at IT Director level or equivalent.
Policies are to serve the stakeholders: that is the company and
its customers and staff. IT operations should obviously be
consulted as to what is practical and achievable but the general
responsibility for policies lies with management and the ultimate
responsibility lies with the CEO.
Policies clearly are not in the technical domain. IT management could take the lead on this, with input from others across the enterprise, including some tech staff. These should support the organization's mission and goals.
Craig Herberg
by regalgs
I have been sitting here for the last 4 plus hours writing and updating policies and procedures for HIPAA Compliance. I am the Head IT person. However, due to the fact that I know more about the HIPAA regs than any of my staff much of this I am having to write. That being said, there is a list of these that I am going to pass off to my staff to write. Why?
1. I can't do all the work.
2. They need to learn how to do it so that they can become better at what they do and learn a new skill.
3. They have insight that I want as well.
Then I will review and update. Then from there what we all have written will be reviewed by the Firm's Ops team (all owners + CFO).
As was stated earlier - No right answer, but use it to learn and become a better IT person. Education comes in lots of ways - some you pay for, some you get paid for.
by rao.ambaji
IT Manager shall involve in writing Policies.
In line with the Policy, Procedures shall be written by the Network or System Administrator, finally vetted by the IT Manager.
by jahhbone
by bluebottle
What most of us forget is the modern day compliance requirements of nations and to this end policies now require input from HR, IT and the Business; some believe that the policy should
be "written" by the HR Manager and not the IT department!
by jclambert
by znovaky
Working for a large, religious non-profit, our team included the legal department. Their perspective in protecting the organization from liability played heavily into the design of our policy manual. They also had the wisdom to make the policy broad in order to make it's implementation flexible.
The downside of the broad approach is that I (lone IT Mgr. supporting 125 users) now find people violating the policy because they don't see how it applies to real life. Consequently, I am crafting a document called "Policies in Practice" with the help of my Director and his boss, the COO. This doc can be flexible and can grow and change as the environment changes, which is quite frequently.
In any case, it's essential to get buy-in from the top stakeholders. Otherwise, the policy will carry no authority.
by mwill
It Matters not who is tasked with the policy writing within an organization as this will be purely a individual issue with each organization based on size and personnel/skills other then that what is important is the policy is well thought out to consider what is the primary functions of the system and will the policy ensure the efficent functioning of the network is maintained for it's intended purposes. Secondly the policy must be effectively promulgated to all users from CEO to lowest person in the network and understood. Thirdly it must be enforced and monitored for changes as the business or organization needs change. Lastly
the policy must be a policy that can be one that can technically be implemnted or nothing that was planned or promulgated is going to work anyway.
down from the top. Any IT specific policies must be in accord with the business policy. It should advise one possible adjustment to business policy where it's impact is not understood. The the top level policy is restated, if the business agrees.
If manager's 'above' or even at the same level as the IT manager do not agree, then it won't matter how 'good' the policy is IT will not be allowed to implement it.
by tonythetiger
Some managers, and a lot of computer users, put the cart before the horse. An anology: I'll get a user who tells me "I need photoshop". I'll think, "No, you probably need to do some of the things that photoshop does." I'll say "What are you trying to do that you can't do with the tools already installed on your computer?"
Policy is the same. It is not an end, but one of several possibly means.
by john.jones
by jbgokhale
To get the mix right, the policies need to be formulated by the Management where as the Procedures which are put in place to implement the policies need to come from the System / Network Administrators.
Inputs from the end users are a must to make sure that the Policies and Procedures laid down are workable.
by james.august
I would say, technically, the IT Manager should do it. However, his job is to delegate his duties to his employees.
I work for a School District, so we have the ability to form a Committee geared towards Web and Interenet usage. We accepted the task of updating our current AUP (Acceptable Use Policy). Took us about 2 months, but it would have taken longer if we had made one from scratch. We lucked out abd found an AUP that other compnaies and school districts have used and taylored it to our needs. Of course we got permission from these people 1st.
by emill
IT Policy should be a task of an internal qual. team or person. This should also be in line with whatever industry standards you follow- It may CFR 21 part 11 it may be HIPPA it may be ISO- if those dont ring a bell maybe we should look at SOX- one of these will require you to spend some time developing a set process - or procedure or spend time filling out a check to a angry auditor- there are many companies that can take care of this for you. Stelex Inc. Bensalem PA .
Thanks and good luck --
by ddecoursey
My experience shows that most admins get trained to apply Group Policies At the server/domain level. The application of these domain level policies can reflect the Compuuter use Policies of the Organization. Much interpersonal networking occurs in these NetAdmin classes. This sends the newly trained admin off with a broad exposure to why and how other organizations implement policies.
One would hope both the admin and the IT manager have been through this industry standard training and are on the same page about usage policies. In my position , my mission is to protect our data and make our network manageable with as limited staff as can be. Other organizations will have different objectives.
The difficult part is dealing with people of power that have no indoctrination to a corporate computing environment. Their attitude ,in most instances, is that since they have used a computer at home that they are qualified to interject that level of computer usage into opinions powerful enough to conflict with, or over ride, established policy. In this scenario dealing with "where is my control panel?" or " sending this joke email via the global address list cant be harmful" is a frustrating issue to overcome .
by frsal
If techies could youre right, they would restrict everything a user does to mess up a pc or network. Not to mention the over zealous manager who thinks that all users are loosers.
If you look at the bigger picture what about a goverment installation or a school. Policy comes from the top they wrote it and we simply enforce it. I strongly believe it is not our role to dictate what can and can't be done. I use all automatic filters and windows policy that way I can say sorry it's not my call it is all automatic with regards to what you can and cannot do.
by craig_b
in business terms just as HR, operations and whoever. Then the policy gets cascaded down and implemented in a more specific form by each department in the business. IT policy often conflicts with business requirements, so you need buy in in order to implement.
I worked at place where it was policy to completely lock down the workstation, IT(services) applied this to the devlopment department as well. Operationally and therefore business wise this was a total non-starter and it got changed after a lot of arguing.
Course some wet behind the ears network admin categorizing me as a dumb user didn't go down too well either.
IT does not know enough about the business to make decisions and business doesn't know enough about IT. So IT policy has to be a collaborative effort or one or the other is likely to suffer.
by craigr
by dmambo
When you look at the long-term impact of policies, and the fact that most people read them once (if you're lucky) and then forget them, the best bet is to buy a book with boiler-plate policies. If needed, you can use the canned policies as templates and customize them to suit your needs. Pass them to management for approval then file them in the cabinet next to The Lost Ark and get back to business.
Unless you have strict enforcement, which in reality I've rarely seen, it's not worth the worry to sweat over writing the policy.
by theidemann
Our company has decided that we need an open ended Policies and Procedures plan so that, as our user demands change, we do not have to go through so much red tape to make even minor changes go live. Our policy before that was like the Mosaic Law. Set in stone by management, it felt it would take a thousand years to change, and that only God himself would be able to give the order. In the end, a simple meeting between department heads using my suggestions as network administrator, and bang!!!, now we have an effective policy that allows changes when necessary, and a clear understanding of what is and is not allowed accross the board.
Yup...It's nice working for a company with less than 200 users.
by npervis9
Such as the user's can install the tools they use best as opposed to those most convenient for IT.
IT should collaborate with the business, so it can provide the required services as efficiently and as safely as possible.
If some twonk says everyone above level x should have unfettered access to their pcs we've got to point out the problems, equally some one in IT should not be able to say, you can't have hotmail, change your wallpaper, or listen to muics while you are working.
by danetter
A system is a system is.... Policy and procedure amount to a system. Who are the users of the system, and what do they need for efficient working? Microsoft provides a how not to do it example. It can take an extreme amount of time to find an answer to a simple question. I think a team is almost always needed for a system design of much importance and/or complexity, and should include management, implementers, aand users.
No, I never was an IT person, but I have been involved with systems design and development for some 30 years, from strategic weapons systems to fire control systems to pest management. Lack of adequate user involvement is a good way to kill a system.
by amberhaze
by rdivilbiss
As a former CIO, it was my responsibility to set policy, and I did. It was the CEO and Board of Directors responsibility to approve the policies and make them enforceable, however (and this is important) a good manager will probably delegate writing of all or part of policies that specifically deal with IT operations to the people in charge of implementing the policy. Why?
Would you want me telling you how you have to do your job when you know best what would be workable on a day to day routine.
I can, but I trusted the various managers and admins to have a better grip on the nuances and details so they could write the proceedures they could live with.
Its all well and good to have a policy, but without workable procedures it won't (and possibly can't) be followed.
Delegating all or part of the writing is also a way to develop soft skills in key staff you may be grooming for advancement.
by mary.hoerr
Seems to me the question should be broken into 2 parts: policies and procedure development.
Policies are specifically business decisions. They describe WHAT needs to happen.
Procedures are IT decisions. They describe HOW something is to happen.
Your question does not describe the problem being addressed; the type of product being implemented, but there is a bigger issue. How do policies and procedure inter-relate?
A model for writing the policies requires a business analyst working with an IT analyst and associated stakeholders, or some similar level of expertise. This allows for the business unit to drive the architecture of the IT model.
The procedure requires the IT analyst to work with the business analyst, but also all of the stakeholders effected by the procedure. This drives the decisions on which equipment to buy, or build, based upon the needs of the business.
Physically writing of the policy belongs in a realm outside of the asked question. Physically writing the procedure should be left to the analyst most familiar with the day to day application of the procedure.
by comp1systems
It would seem to me in the IT arena that the IT Manager
would be the one to be responsible for writing and
updating Policies and Procedures. IT Admin have their
hands full with various projects that would clearly take time
away from the actuality of sitting down and constructing
policies for network and computer use. The IT Manager
oversees the ongoings of the day-to-day operation. Being
the case, he is able to report on how things are going,
necessary improvements, IP address assignments, etc.
Because the IT Manager plays a vital roll, the purpose of
keeping within the guidelines of computer use, as stated,
the IT Manager should be responsible for writing the
Policies and Procedures.
by 3kl
Or third, but IT as a whole looks foolish to the company or organization if your releases/warning/documents are written by an unskilled writer. I am associated with an organization fighting the PR problem and our releases don't help.
On a side note, keep the policy team small and get support from the higher-ups. Without those two pieces you will be fighting a long (and probably losing) battle to get a decent policy implemented. (speaking from several months on a policy team re-writing the policies for an org with around 13,000 people in it)
by allyinfo
Hi,
I am both a network admin and technical writer, and don't think that outside people always know what is going on within the company. . . so, if you have the ability to intereview the company executives to find out what their specific needs are, then you are the person to write the policies. . if not, then the next best person suited. If you come from outside the company, then the company's mgt must make themselves available for interviewing, along with the admins to bring their needs together for this to work. There are also security requirements that neither of them might know, and an outside person will see this and help them implement the different needs into their structure so they have a more wellrounded design for the policies and procedures for the company. Many internal people have never been educated in all of the different areas to be covered.
Working for a large, religious non-profit, our team included the legal department. Their perspective in protecting the organization from liability played heavily into the design of our policy manual. They also had the wisdom to make the policy broad in order to make it's implementation flexible.
The downside of the broad approach is that I (lone IT Mgr. supporting 125 users) now find people violating the policy because they don't see how it applies to real life. Consequently, I am crafting a document called "Policies in Practice" with the help of my Director and his boss, the COO. This doc can be flexible and can grow and change as the environment changes, which is quite frequently.
In any case, it's essential to get buy-in from the top stakeholders. Otherwise, the policy will carry no authority.
by ink760
I was a PM for a legal department. I think that it's great for the lawyers to get involved, this way you know you have the proper language. The only downfall to this is that because lawyers are usually so busy, IT policies usually get pushed to the side and attorney has a draft policy sitting on their desk that they are dying to pass onto whoever the new lawyer in the department is. I think that it takes someone involved in Records Management, Legal and IT to really sit down and do this the right way. Forming a task force with these three departments is the ideal answer, but without a corporate sponsor pushing, the team usually falls apart after a few meetings.
I'm trying to go to law school now so that I can officially work with companies to address their issues regarding IT policies in large corporations because I know how tough it is trying to deal with attorneys who know nothing about RM and technology.
by ttfh
Policy is generally considered a management function. In the formation of a Security Office (I prefer the name Integrated Security Office Program- ISMP), it is one of the three management areas that have strategic importance: Policy Management, Project Management (Portfolio Management, PMO, Program Management and Project Management at the Operational organizational level) and Risk Management. IT Security or Risk Management Policy is involved with the 10 areas of security as defined under the Common Body of Knowledge, ISO 17799, NIST 800 or DITSCAP. You can not control a function if you have not defined it, managed the processes and implemented the technology. Hence, Policy is made up of the areas of Knowledge Management, Process Management and Technology Management. Each of these areas have their "experts". Policy must be managed centrally, but management could and should reach out to individual experts in these areas who have the knowledge, the process control and the technology knowledge who can define who, what, when, how and the why of policy. The technical people know the limits (constraints) of technology, the project managers know the process and everyone has knowledge of how policy should define and control certain aspects of the world that they live in. It is also a business function. Policy is not written by any one person, but is developed as a continuing process over a period of time. You can't buy policy.You have to develop it like you would a computer application. It is something that fits the organization, the people, the processes and the technology that you are working for. It is truly a group effort.
From an National Security Agency 4011 certified Security Services Project Manager that routinely writes Policy.
Most of all, remember that policy is a process.
by bjorgensen
Network administrator should enforce only. Should report violations to one person only for action. Network administrator should receive confirmation of every reported violation.
Policies/Procedures should be generated by top management in consultation with the legal advisor. Network Administrator and IT Manager should advise this committee.
by olapaders
Policy and Procedure are completely different.
Procedures enforce policy, so in IT they should be written by IT and in my view by the people who execute them. The manager should ensure that company policy is met by them.
Policy cannot just be set by IT though.
To me that should be done at top management level and before it starts said managers should have a good idea of how and whether the policy will impact their dept. That's bound to be an iterative process and will be subject to review anyway.
IT certainly can and should make recomendations about policy as should every other department.
Over here the process is to put mechanisms into place to review current policy and to be able to adjust it to meet the business needs. Anything else is the tail wagging the dog.
by ssnaz
In my opinion and experience it should be the IT Manager , because is the position that has a more complete vision of the IT department and has the total responsability of IT in the company.
Remember the policies will tell every body what can be done or not. So they will have to be approved by the Management who also approves the general policies.
The procedures are more relared to the operational side ,it means that they have to be developed by all the people involved in the process to get the maximum quality of the final service or product. Normally, they are developed having in consideration the related policies.
The procedures can be approved by the IT manager.
If you need further assistance let me know,
Bari.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending