Government Technology
This is page 2 of the discussion. Read the opening post
After Hours
This is page 2 of the discussion. Read the opening post
Society is more communication crazy than ever, and our technology is responsible for this, of course. We live in a culture in which everyone seems to talking on a cellphone; checking and responding to e-mail on their Blackberry, laptop or phone; listening to tunes on an IPOD; or interacting with one or more of the seemingly billion devices that are used to keep us in constant contact.
This leads me to my point, which is that as consumers of services, we desire (perhaps demand) to be kept informed of the status of the service being provided to us. We want to know when the service is going to be performed, how long it's going to take, how much it costs, what's being done about problems with the service, and so on.
When we don't get the answers to these questions in a timely fashion, we become frustrated. The harder we work to obtain answers or--if the answers are not satisfactory--the more angry and frustrated we become--to the point that even if the service has been successfully provided, its value is greatly diminished--it might even be considered a failure.
There is a lesson to be learned here. If we are service providers, the more we communicate about the service--before, during, and after its delivery--the more positively the service will be received. This even works if you are failing in some capacity to provide the service in the expected way. It is better to own up to a failure and say what is being done to rectify it than it is to stay quiet about it. In other words, you can get away with less than 100% stellar performance so long as you keep the lines of communication open. People will generally cut you some slack so long as you are open and honest with them.
However, failing to communicate, especially when you are not performing well, magnifies your issues and can completely blow them out of proportion.
Obviously there is a limit to everyone's patience when it comes to poor performance, no matter how much you communicate, particularly if poor performance is the norm, but you might be amazed at how far the limits can be stretched.
How does this translate to IT? We unfortunately tend to try to be the strong, silent type when it comes to our work when, in fact; we need to be exactly the opposite. We should be masters at communicating during all facets of our service provision, from inception to delivery of our service and them some!
There should be no doubts by the customer regarding our service. We should be clear and communicate what we know, even if that means communicating that we do not know anything.
While the personal touch is always best, the form of communication can vary so long as it is truly informative. Voice messages, e-mail, system prompts, even paper is acceptable so long as it communicates something meaningful. You really do want to avoid having your customer say, ?No S%#t Sherlock, tell me something I don't already know.?
While I won't go into numerous examples of how you should communicate, if you stop and think about it, you will probably come up with dozens upon dozens of ways in which you should be communicating better.
And if you are still stuck after pondering for awhile, ask your customers; I'm sure they wont be shy in letting you know exactly how they feel.
by pmoleski
In general I agree with your comments. Communications, often as simple as good manners will carry the day in almost every tough situation. I also agree that at a certain point a problem has to be fixed. Relationships and good manners have to be backed up with delivered service.
There is in my experience a point in time where over communicating, in particular at a technical level, with executive level management is damaging to credibility and leaves an impression of things not being under control.
During a crisis it is important to keep line management informed what is going on. It may even be important enough to let the executive suite know there is a problem if it could end up in their being asked questions by the media or shareholders etc. For the most part it is important to let the technical people do their work and the biggest challenge for the CIO is not to spread inaccurate information. While solving the issues there may be many theories and ideas floating around. At any point in time the view of the situation can change rapidly as the technical folks work through the issue. Executive level management wants to know if there is any customer affecting impacts, are the right people involved to resolve the issue, and were appropriate technical and process pieces in place for the business process involved. What I have learned not to do is to give them the blow-by-blow updates of working through the technical issues. Because things change so quickly, even if I get the facts right, by the time things are resolved I may give people several different stories. At a certain point the communications becomes counter productive if it is to detailed and leaves an impression that the IT organization does not know what it is doing. If the executive suite needs to be involved because of large business impacts or authorizations of emergency funds to resolve an issue then the discussion is at the level of business impacts and dollars, which is the language of the executive suite.
I have found that the same holds true with project work. On any given day and issue, the project may be struggling to come up with solutions to keep things moving. If the communications to the executive suite is too detailed then their view of IT will be less then it should be, as it will go up and down on a daily basis as the project goes.
In summary, I agree that communications is a key element of success. However, I would qualify that with a note to target the content, and frequency of communication to be appropriate to the audience, in particular to the executive level. Appropriate communications is one of the more fun aspects of senior level IT management. When asked I often describe my job as that of translator between the technical and business world. I have to speak both languages fluently and translate between them as appropriate on the fly.
Phil
Excellent comment Phil. I do agree, less can be more, and the
communication should be context and audience sensitive.
Unfortunately I keep seeing the trend towards less communication/no
communication rather than over communication. While no one wants
to be deluged with information that is constantly changing, at times
anymore I would welcome that as an alternative to silence. But
your point is well taken and on the mark. Thanks for the comments.
by micheles
by chgragg
by lellis17
by larryjg
by chenig
The bottom line is this - project management is an art not a science.
I've been at this for a while and yes, I do have a PMP. (If you are serious about being a PM, get the certification. Otherwise, you'll spend your entire career explaining why you didn't.) I have worked w/ PMs who think that project management is a matter of applying the right structure and measuring tools and making the project fit the norm. I watch them fail all the time w/ this one size fits all approach.
I come out of software development (another discipline based on art and not science). I want to know the business need driving the project into being. Why is the application being replaced? Who is going to use the data warehouse? What's the rationale of the web site? Sometimes I work for the organisation and I already know the political landscape (and land mines). If I come from the outside, I'm going to ask a million questions and make it my business to understand your business.
The PMBOK is a good structure (except for the discussion of how to manage people which is enough to get you fired in some places). I'd add a security aspect to a project because so many clients are so security conscious. The principles of structured project management methodology are required. But if you come from the formulaic approach, as our mythical PM #1, you may think that's all you need to do. PM #2, who really should get her PMP, should apply the same methodology once she understands the project context, organisational goal and the team she's working among. No question that winging it is not a successful approach. You have to do the basics.
But I'll take #2 every time.
Heck, I've BEEN #2, until I wised up and took the exam.
Found a nifty starter for a RFP for antispyware solution. While
it could be beefier, it sure is a good start regarding the technical
questions. Check it out here.
Me neither. Been an incredibly busy 2 weeks for me and this one
slipped right past me. For shame! Did it happen to you
too? Want to catch up? Here is a great place to start.
One of the hottest forum topics you will find on the TechRepublic boards is one that deals with age. The topic starter is usually something in the ballpark of "I think technology is for young people".
Then the comments come flooding in. I know, because I have been tempted myself to jump on those threads because I am so outraged. But for the most part, I believe I have resisted putting down my angry comments and let a cooler head prevail.
Now I thought I would take a few moments and deal with the topic in a more levelheaded fashion.
Age is an interesting characteristic in the work place. There are many preconceptions associated with it. Let's start with the tried and true: If you are too young, then you must not have much experience; therefore, you aren't qualified to do the job.
Conversely, there is the old adage that if you are over 50, you are old and slow and set in your ways. There are dozens of stereotypes that one can come up with regarding age and work that seem to be even more intensified these days due to technology.
Technology in some ways has both leveled the playing field and tilted it at the same time. The youth of the world have technology thrust upon them at an early age. Even my 2-year-old nephew carries a fake PDA and Cell Phone. Is it any surprise then that his generation and those who come after will be completely comfortable and possibly extremely proficient with technology when they enter the work place?
Couple that with the enthusiasm (brashness?) of youth, and I am not surprised when I read comments like "the old just need to get out of the way".
Considering the rapid pace at which technology changes, and the fact that older people are more encumbered with family and other responsibilities, it does become more of a challenge to keep up with the latest technology.
However, for any bit of truth you may find in those statements, you need to throw them out the window. Let me say it very clearly now so there is no confusion on this: There is no place for discrimination/stereotyping in the workplace, whether it is based on age, sex, race, religion, or any other characteristic.
Not only is it illegal, it is just plain wrong. No one likes to be typecast, one way or the other, based solely on age. Frankly, if you are doing that, you are doing yourself a great disservice ? because you are prejudging a worker's ability on something that more than likely has no affect on his or her skills.
I obtained my first IT management position when I was 24 years old. At the time, I had employees who reported directly to me that spanned the range from 18 to 50. As a newly minted manager, using age as a criterion, who would I expect to be my best employee --the 18-year-old or the 50-year-old? Before you answer that, why would I even consider making that determination based on anything but performance? Do you see how ludicrous that is? When I sat in management meetings with my peers who were decades older than me, were my comments worthless or more valuable because of my age?
Similarly with hiring; when I look for qualified candidates I am looking for self-starters who can follow through and think for themselves. I don't care if they are young, old, green or blue or come from another solar system. The bottom line is; can they do the job in the manner that I need them to? Hey, I am smart enough to realize that a manager that surrounds himself or herself with stars shines just as brightly as they do.
I won't sit here and tell you that age doesn't come along with advantages and disadvantages. It is how a person deals with age that shapes them as an individual. I am certainly a different person today than when I was 24. I believe I am better at some things, and worse at others. But as a whole, I feel that I am better overall, as my goal is to always improve myself.
Yet at the same time, I feel that I fit no particular stereotype for my age. So don't you dare discriminate against me because of a number. Judge me based on my skills and abilities and my performance. Leave the rest in the trash heap ? where it belongs.
by mgelman
The real problem is that there isn't much of an upward path for
engineers beyond 5-10 years experience except management.
Management is fine except (1) there aren't enough slots for everyone to
be a manager and (2) many engineers don't make good managers.
by cdjones
by rzimmerman
by blueknight
Excellent comments Ramon. I too was hired as an IT Manager at an early age - 20. After I was hired, I found out that I had been selected over my former manager which was a great surprise. I was curious why such a young person such as myself had been selected over someone with many more years of experience. I was told that I had been hired because, given former manager's years of experience, he should have progressed beyond the point where he was in his career. The hiring manager noted that I was bright, I learned very quickly, was able to make good decisions and had the people/customer relations skills that were needed for the job.
Age really has little bearing on performance, in life or work. When I was in the Reserve Peace Officer Academy (at age 45, and oldest in class by 10+ years) I was second fastest in the class (behind a 19 year old) in a timed shotgun course. The time limit was 50 seconds and the average was 43 seconds. The 19 year old did it in 20 seconds... I came in at 22 seconds despite a ruptured calf muscle. The point? If you're serious about what you do, are determined to succeed and rely on your training you will succeed no matter your age. If you lack training or commitment, then you have a problem.
My love of the IT field has never diminished despite having experienced age discrimination in job hunting when my position was eliminated at age 47. Most of the hiring managers were 10-15 years my junior and I suspect that even though I don't look my age, they made it the primary criteria for selection never taking into consideration my wide variety of experience. I eventually was hired by a manager who recognized above all, that my experience in virtually every area of the IT field was very valuable and would make me an asset to the organization; age was never a concern.
Having just turned 57, many pretty much think I should retire. But since I still feel 40 something, am in in good physical condition and love my work, I have no intention of retiring anytime soon and I see no reason why I should. In the meantime, I'll continue to learn new technologies and to contribute as much as I can to the success of my organization.
Your last paragraph pretty much sums up my sentiments exactly.
by raelayne
I'm 55. I've been working in software engineering since my early
20s, mostly to support a ridiculous education habit. Every five
years or so I get sick of what I'm doing and move on to something
new. I like to think I keep my skills up to date as well.
My boss is 25 years younger than I. I've never had a problem
changing jobs, but I am beginning to feel the pressure -- how easy is
it going to be next time? And what am I thinking, never staying
long enough to build up a good retirement plan? But fact is, I
love this field because things change so darned fast, and I find that
really fun and invigorating.
What I want to do -- in my heart of hearts -- is work for Google or
Ideo or eBay. I miss the energy of a bunch of smart people
kicking ass. Somehow I think it's unlikely that I'll get that
kind of job. Is there anyone older than 40 at Google? You
think anyone cares what my GRE scores were now? I could work in
government (ZZZZZZ), I could stick with my current company and ride
things out till I retire. I could start my own company (way too
much trouble). So here it is, youngsters: it's very
sad getting old, when the action is all somewhere else. I'm
no less smart, I'm no less motivated; the whole picture just shifts
somehow once you're 50. And I'm not blaming anyone else --
it must be hard-wired. Although I recently hired a 70-year-old
genius technologist, I generally prefer to hire youngsters (you might
call them recent college grads) myself. It's a condundrum!
Kill all stereotypical hype!!!!!
I agree with you wholeheartedly. That is discrimination of the elderly over 40 years old. DIE, AGE STEREOTYPE, DIE!!!!!
Companies and organisations should focus on SKILLS and PERFORMANCE.
-swg
by rzimmerman
HR 4127 known as the Data Accountability and Trust Act is more than
likely to become law. Some feel that rather than strengthen data
accountability, it actually weakens it. Check out Roger Grime's take on the law and find out why this should concern us.
Everyone knows about WeatherUnderground don't they? Apparently
not, because I often get strange looks when I mention it. Want to
add a weather link to your government web site? WeatherUnderground is one of the best.
I was reading a comment the other day on one of my blogs
when I noticed someone mentioned ?boring government work?. This struck a cord with me because I have
never found government IT work to be boring at all. I don?t think I am some weirdo or glutton for punishment
regarding the workplace, so there must be something regarding government IT
that makes me feel that way. Actually
there are several things that make government IT quite exciting and I thought I
would share them with you.
The first is variety in the nature of the business
itself. Depending on the size of
government you work for, your customers business can include Police, Fire, EMS,
Health and Human Services, Public Works, Public Safety, Education, Animal
Control, Armed Services, Defense and many others besides your typical Finance
and Administration type of work. This
makes for an interesting and challenging range of customers to satisfy and work
for. To me, one of the most interesting
parts of IT is learning the business of your customers. With so many that fall under the umbrella of
government, there is always something new to learn.
The second is size.
Governments span the gamut from itty-bitty to huge and monolithic. The smaller governments tend to be local
government, while the larger tend to be state and federal. So there are organization sizes to meet
everyone?s tastes.
Related to size is span of control and interaction, but it
is not just size dependent. In
government, your position tends to be less specialized than in the private
sector and you tend to wear more hats than your typical private sector
counterpart. This is partly due to size
and partly due to budget. There are
usually not enough IT positions to go around in government and therefore each
position has to do more and be more involved in different areas. That?s not to say that as the organization
gets larger your position won?t be more specialized, but even in the largest
state governments and at the federal level, you will find areas where IT staff
are generalists as opposed to purists.
Also related to size somewhat but again not completely
dependent, is the ability to make a difference. If you have the initiative you usually can find a way to make a
real impact in your organization and to the community/constituency the
government supports.
Third is meaningfulness.
Not taking anything away from the private sector, because I as much as
anyone else appreciates the goods and services I can purchase, but I get a
sense of satisfaction knowing that I work for the ?people?. The work I do and have done in the past does
and has made a difference to the community that I live in or even state or
nation wide.
Fourth is forced creativity. Most government IT shops do not have the resources that can be
brought to bear on a problem or opportunity that a private sector organization
can. That being said, the good IT
practitioners in government find ways to get things done that are often times
extremely innovative and clever. Always
having to do more with less can make you a much sharper individual than always
having the tool at hand to do the job.
Fifth is opportunity.
Because government IT jobs tend to pay less than in the private sector
they are more willing to give you the chance to prove yourself than perhaps
your private sector counterpart. Having
been on the hiring side of the table for many years, I know that there were
qualified candidates that I could only dream of acquiring due to salary
restrictions and I therefore had to go with someone with less experience or
expertise and let them grow in the position.
Speaking of growing in positions, it is not uncommon to find
senior management that started at the lowest level position in the organization
and worked their way up. This often
corresponds with the organization investing in the employee through training
and/or letting them learn on the fly.
You get more chances to experiment and make mistakes in government than
you do in the private sector.
Lastly, for everything I have said here, EVERY job in any organization can be boring or have
its boring moments. Much of it has to
do with your own personal initiative, the management of your organization, and
your workplace and organizational culture.
I know people who hate their government jobs and I know people who hate
their private sector jobs. I have
worked in the most wonderful environments and I have worked in miserable
environments. Obviously one makes a choice
what to do in those situations, and the choice is a personal one. However, there is nothing inherently boring about government
IT. It is a reputation that is largely
undeserved.
I encourage anyone looking for a new opportunity to
consider government work. You just may
find that all those horror stories that you have heard or read are just
exaggerations of common workplace ills.
I know I have never regretted my decision to come to work for government
many years ago and I am still with government.
Just in a different place and with a different mission than before -
More new stuff to learn and more opportunities to make a difference. Boring?
Not a chance.
Keep up with the issues and challenges that
uniquely affect public-sector IT with TechRepublic's free Government IT
newsletter, delivered each Tuesday. Automatically sign up today!
by chewybass
Ramon, you are right. I wouldn't trade my job for anything else. Interestingly enough I find I'm more on the bleeding edge of new technology than most of my friends in the public sector. My work is exciting, never dull, and as you stated, has offered me the opportunity to recieve training that I wouldn't normally be able to obtain. Sure, I'm not compensated as gloriously as those in the public sector, but I haven't been without a job for the past 15 years. Working in government is a great opportunity with many rewards. Try it, you may like it.
A. B.
Florida
by allaroundit
Having recently come from the private sector working for some rather large companies in both IT and manufacturing; I find government IT very slow and behind the 8 ball. Innovation and employee drive are lacking due to the reward system (everyone gets a standard COL [cost of living] increase; there are not really any performance increases or bonuses/incentives). Therefore, everyone is treated the same regardless of how they perform - which promotes a "work avoidance" attitude. Reprimanding employees is difficult due to unions - so once they are in, you can't get the bad apples out. (Not so in the private industry since most people are "at will" employees. If you perform, you are rewarded - if not, you are let go.)
This could be due to the lack of accountability in gov't. We are "supposed" to be fiscally responsible - however decisions are made at random since "bottom line" does not really matter. After all, as they say, we don't make anything and don't worry about the bottom-line. (I disagree with this thought, however this has been vocalized from management. Needless to say, we should all be fiscally responsible and shouldn't be doing IT just for the sake of IT.)
Furthermore, I do not agree with the hiring selections I see happen that further exasperate the issues. (An IT Operations manager with no prior IT experience, and a CIO who was previously a helpdesk manager.) This is less likely in private industry as generally you need a proven track record of success. (I have actually been told here that I need to adjust to the "slowness" and realize things just take 5 times longer than anywhere else to materialize.)
The place I am at is at least 5 years behind the industry. (I've attended many conferences and have heard the same things repeated, and the same complaints - so I know I'm not alone here.)
That being said, I'm glad to hear it is going well for at least 2 people who have posted - but from my experiences I believe you may be in the minority.
by allaroundit
Having recently come from the private sector working for some rather large companies in both IT and manufacturing; I find government IT very slow and behind the 8 ball.
Innovation and employee drive are lacking due to the reward system (everyone gest a standard COL [cost of living] increase; there are not really any performance increases or bonuses/incentives). Therefore, everyone is treated the same regardless of how they perform - which promotes a "work avoidance" attitude. Reprimanding employees is difficult due to unions - so once they are in, you can't get the bad apples out. (Not so in the private industry since most people are "at will" employees. If you perform, you are rewarded - if not, you are let go.)
This could be due to the lack of accountability in gov't. We are "supposed" to be fiscally responsible - however decisions are made at random since "bottom line" does not really matter. After all, as they say, we don't make anything and don't worry about the bottom-line. (I disagree with this thought, however this has been vocalized from management. Needless to say, we should all be fiscally responsible and shouldn't be doing IT just for the sake of IT.)
Furthermore, I do not agree with the hiring selections I see happen that further exasperate the issues. (An IT Operations manager with no prior IT experience, and a CIO who was previously a helpdesk manager.) This is less likely in private industry as generally you need a proven track record of success. (I have actually been told here that I need to adjust to the "slowness" and realize things just take 5 times longer than anywhere else to materialize.)
The place I am at is at least 5 years behind the industry. (I've attended many conferences and have heard the same things repeated, and the same complaints - so I know I'm not alone here.)
That being said, I'm glad to hear it is going well for at least 2 people who have posted - but from my experiences I believe you may be in the minority.
by allaroundit
by pmoleski
I have worked in both a for profit organization and now in government for many years. To me there is not that much difference in the role of an IT shop in either environment. We enable the rest of the business to do their work and stay ahead of the technology curve. By the time the business needs something we should have the technology services at least researched if not already available as a service. In many cases we are bringing forward the new services as our own initiatives selling the business on the benefits to them to gain the budget approval and buy in. If we are proactive and understand what the business needs now and into the future my experience is that the budget dollars will flow because the technology has value.
In both cases if the business is struggling or the government is in cutback mode then there are valid projects with value that end up waiting because the environment to proceed is not their. The key is to be ready for the opportunity. Have the strategic plans for technology infrastructure and business supporting applications in place. Do what is possible in the current fiscal environment and when the opportunity comes have the business case sitting waiting. Use the down times to research and perfect the visions, communicate the vision and have it integrated into the rest of the plans for the business. Then when things shift your plans will move forward along with the rest of your organization.
I believe that this advice holds true for any level position in the IT field whether private or public. However, there are sometimes issues that can make patience and a longer-term perspective important within the government field. Government tends to operate on a yearly expense basis for budgeting that means everything is tied to the yearly budget cycle. This is because funds have to be publicly approved in most cases by elected officials. That means that plans have to be tied into that cycle if they expect to be funded. The other thing that happens is that depending who is in power their views on what are good programs for government to pursue will change. This means that an idea that makes sense to IT folks may never be done if it is at odds with the current government and or public view on an issue. The elected officials are our owners every bit as much as stockholders are in the private arena. This means in the government world to make an idea fly may mean getting a consensus to proceed that includes the business areas of the organization, the political owners, the public, and stakeholders who have an interest in the topic. When all of that is in place there may also be a series of Regulations and Laws that may need to be created or changed to allow an initiative to proceed. Finally it may take many years for a program to be fully rolled out and accepted within a large jurisdictional arena.
So if anyone working in a government IT job is bored because things seem to take along time to get a decision before proceeding I would suggest they become more involved in the above process. In government, in particular at the approval level understanding the business, understanding the political and regulatory environment, and building a shared vision or consensus can make the technical issues seem almost trivial. To conclude I would say that well I am never bored because I fill my time with all of the above I have learned to have patience and a long term perspective in pursuing long term IT goals within government. The reward is that when all the above is done well I have been able to seize the opportunities and as Ramon said enjoy the fruits of IT work that affects a great many people and has a lasting positive affect on society.
Phil
by hadg
Ramon,
As an IT director for a county government, I fully agree with your comments on
government IT. I enjoy my job thoroughly for the same reasons you
commented. One moment I am working with emergency operations, then with
the prosecutors, or with public safety, etc. I get to know the roles that
everyone plays in government and their specific needs. This has also
provided me with a greater appreciation for government work. Public
servants are easy targets for criticism, public sentiments of not deserving
raises, lazy or uncaring workers are common. However, my experience has
been the opposite. I have found hard working dedicated people working in
government.
From an IT perspective, I am given more range to implement projects and new
technology. As for the comment of not caring for the bottom line - they
have not been involved in the budget process. I watch my budget like a
hawk, as I have to make that money last all year. I have to balance training
with equipment with upcoming needs and/or regulations.
I think that IT can be boring anywhere, just as you stated. It depends on who?s pulling the strings. I am lucky to work for a manager who is
interested in moving my department forward and growing it. We are implementing technology such as EDMS to
tie into our GIS. As well as working towards
a wireless coverage of our county. As a
manager myself I try to allow my staff the freedom to work independently. I try to implement new technology whenever I
can.
Looking for a website/organization that promotes technology in higher
education? Look no further than Educause. "EDUCAUSE
is a nonprofit association whose mission is to advance higher
education by promoting the intelligent use of information technology."
An article that compares the pros and cons of open source wikis.
You know I'm all over it! You should be too :-) Check it
out here.
I received an email recently in response to my blog on
ageism asking how one might break into the IT field at a late age, with minimal
experience, and an older IT skill set. Hmm? What could I suggest?
I could say, "Go back to school, get/finish that 4-year
degree in IT, and make sure you do plenty of work study to get some IT
experience." But that?s not really a satisfactory answer. Most folks in
their later years don?t have the time to get that 4-year degree part-time, and
full-time is usually out of the question. Additionally, they need money now, not tomorrow.
There is a variation of the above strategy that can work
though--certification. Get a
certification in an IT specialty, and you can often get doors opened for you,
even without experience. IT certifications can be completed in anywhere from a
few months to a couple of years depending on the certification you are trying
to receive, how hard you study, and your aptitude for the content.
On top of that, there are many different ways to prepare for
certifications: from boot camps, to self study, to online classes, to corporate
training, or a combination of all of these. Depending on the route you take,
you can spend very little or quite a bit, depending on your style and learning
needs.
The next question would be, "What certification/s to go
for?" Without even debating which ones are better than others, the obvious
answer is ? the hottest ones in the job market, if they meet your interest.
This is where some soul-searching has to come in to play. Are
you willing to make the commitment to learn the material to pass the tests, and
are you willing to go where the jobs are? Because you can be the hottest IT
commodity in town, but if there is no need for that specialization in your town,
you are out of luck.
Given that your answer is yes to both the above questions,
here are my suggestions. Now, not everyone may agree with my rationale for the
following, but I think that these will give you the best chances to get your
foot in the door without having a ton of experience.
Then there are the more traditional and more popular certifications
from the major vendors of hardware and software. Obviously there is nothing
wrong with pursuing these certifications. However, older, out-of-the-workforce
individuals with dated IT skills who are joining the larger pool of IT
professionals (with the same certifications) are going to be at a disadvantage
due to experience and sheer numbers, thus, the emphasis is on open source.
Now, why is this discussion being held in a government
technology newsletter? Easy. Governments will be the prime employment targets
for these folks. Governments (which includes education) were/are early adopters
of open source tools, and they tend to have smaller budgets which means they
tend to pay less. Therefore, they are more willing than the private sector to
take a chance on a freshly-minted certification-holder.
Lastly, the above advice holds true for anyone, not just the
older worker. It can be a good way to switch careers in midstream or start one
in lieu of college. However, I will always recommend getting a formal four-year
degree if at all possible.
So if you are that person trying to break into the field
again, or tired of your current position, you might give my suggestions a try.
There are no guarantees that come with it. Although, investing in new knowledge
is never a waste of time in my opinion.
Good luck!
by zlitocook
Or you could take a two year tech. degree from a good collage and use your life Experience and know how to get into the field. I started late at 39 and have had great jobs. Most were contracts but I have had three full time jobs, I have mentored alot of people just out of school. And most were expecting to get high pay and a great job right out of school. There are alot of jobs out there you just need to look for them and keep trying! Take a help desk position just to get your foot in to the door. Just remember you are what you think you are not what the employer is looking for! I mean be better then what they are looking for, if you go for a help desk position. Be happy and say you enjoy talking with people, but if you can not talk to people tell them so. Just be your self .
by mattdull
A foot in the door is the way to go, I started in IT changing print toners for a Fortune 500 company with only an A+ and MCP certification, since then I have moved on to a Sr. Tech Consultant at nearly 6 times the salary with another company in less than 3 years. Start at the bottom and shine your way up. People skills are a must, you have to network once you get in.
by mikencove
I entered IT at age 37, with a good bit of life experience, but no IT degree. A guy I didn't even know took a chance on me, so I got my foot in the door with a major IT company. I "paid him back" by putting in the time to get professional certifications to back up my skills. I was in software QA, so my certs were the American Society for Quality certs in this area. Having a 4-year degree already, I was eventually able to get a MS-IS via evening courses.
For general IT certifications, I'd recommend A+ and MCSE. After that, find an area (CISCO, for example) and concentrate in that.
by pmoleski
There are many career paths in IT, often beyond the pure technical. Below are a few examples. There are almost endless other combinations depending on your starting background.
Entry network tech, goes to senior tech, goes to network administrator, goes to IT project leader, goes to project manager or goes to IT manager
Entry data analyst, goes to entry programmer, goes to senior programmer, goes to systems analyst, goes to IT project leader, goes to project manager or goes to IT manager
Entry data analyst, goes to entry programmer, goes to senior programmer, goes junior database analyst, goes to senior database analyst, goes to IT project leader, goes to project manager or goes to IT manager
Business user, goes to business IT tester, goes to business requirements definer, goes to business project leader or process change leader (alternatively called a business analyst), goes to project manager or business manager or sometimes IT manager
There are similar paths starting with the helpdesk or computer room operations and leading through to change control and finally operations management. Operations disciplines such as ITIL are a field onto themselves. These are often available in larger companies or organizations. Related fields include security policy, systems development methodology, IT organization and governance. Consider researching things like CoBIT (may have this one wrong as it is relatively new to me. It is related mostly to IT governance I think), and CMM to get started. Often just acknowledging that you know what CMM stands for can almost be enough as many technical people find this branch of IT to be to dry for their tastes.
Once at the level of project manager or IT manager then things can open up to the senior IT management ranks. For myself I moved around through many different IT management jobs before moving up later in my career.
The point I am making is that the IT field is broad and can include many well paying disciplines beyond the pure IT technology jobs that often are highlighted in the Blogs and discussion threads. I agree with Ramon?s comment that it is often easier to break into IT through the less popular/common route. Hopefully some of the above will give you an idea.
by mvarela
I entered the IT field at age 36. I took an administrative assistant position to get into the IT department and then took some basic programming, Windows and hardware classes. I was able to get an entry level IT position managing a project management enterprise software suite which gave me some server administration experience. After taking some graphic classes, HTML and JavaScript I took a webmaster position in another agency and have since followed up with accessibility, usability, design, and content management classes.
I have been taking technology related classes while working full time for 8 years now. The field changes so fast I expect to take classes for the rest of my career just to stay ahead of the curve anyway.
I agree with finding an area to specialize in, technology is getting so complex that finding one area to excel in is more feasible than trying to know everything.
To add an ironical twist to getting into technology at a late age, I'm starting to teach classes in web design to Jr high students at a private school. Kids of course who have never known a world without advanced technology.
by blueknight
You CAN Teach an Old Dog New Tricks
After a very quick read of comments, I thought I'd suggest something I didn't see... if starting IT late in life you could gain experience doing volunteer work for a non-profit, or if you are able, try doing an internship. Both would give you more knowledge and work experience. That experience can become part of your resume and the organization(s) you work for will be good references to get you in the door of a company you'd really like to work for. Working as an intern while working a regular job could be difficult, but you may be able to find a part-time internship position that works with your schedule. That's the hard part; fortunately, it's temporary and the benefit is great.
We have one partiular fellow working in our Network Services group (includes desktop/LAN support and communications) who began working here as an intern. At that time, he was about 42 years of age. He had been an iron worker but an industrial accident ended that career. He trained for a new career in IT and worked here for 6 months or so as an intern. Today (about 7 years later), I'd place him as one of the top 2 to 3 technicians in his group. You CAN teach an old dog new tricks.
Jim
An Old Dog IT lifer - 39 years and counting)
by jwxt
It is never to late.... Diversify your background with certifications, and education. One good way to get some resume pad is work for free. A way to do this is send your resume to the emails/HR contact on sites like Monster and Dice. Let them know you are willing to work for free during the hiring imterim. I was able to work on a Cisco project, and a network migration in this route. You can choose not to accept the positions in this way also. Very much a win win
Joey Hernandez
by btljooz
Thank you, Ramon, for such an informative answer to the email that you mentioned. It does give some extremely intriguing ideas...as do the posts commenting on and adding to what you said. :)
However, I did notice that the posters were mostly 'thirty-somethings' when they were able to break in to the IT field. Can I conclude by this that Forty-? is a bit 'old' to be trying to make a fresh start in this particular field? I'm going on 48 in January! Is it too late for me? Just curious......
by btljooz
Thank you, Ramon, for such an informative answer email that you mentioned. It does give some extremely intriguing ideas... as do the posts commenting and adding to what you said, for that matter.
However, I did notice that the posters were mostly 'thirty-somethings' when they were able to break in to the IT field. Can I conclude by this that Forty-? is a bit 'old' to be trying to make a fresh start in this particular field? I'm going on 48 in January! Is it too late for me? Just curious......
by bg6638
I qualify as one of the older out of workforce individuals, since I have 30+ years of COBOL & Foxpro DOS programming experience. However, I also have worked with Msoft technologies from DOS 1.x-6.0, NT 3.5, NT 4.0, Win2K, Win2K3, SQL, Exchange, ISA server, etc, as a System Administrator. I am working on an MCSE 2K3 and CCNP, but completion is at least a year away. Unfortunately, I only have an Associate's degree, which no accredited college will accept any transfer credits from. My employer went bankrupt over a year ago, and in nearly two years time I have had only 3 interviews! I have worked with recruiters and also have sent numerous "blind" resumes to no avail, and yes, I am placing emphasis on System Administration, NOT programming! I know that I need to keep trying, but I am really beginning to wonder.
BTLjooz,
Don't worry about your age. Choose a
path, whether it is to get a cert or a degree and excel at it.
Good work shows through. Again, I still push an open source cert
so you stand out. And btw, too add some experience, volunteer
your new found expertise with a Not For Profit. They would
absolutely LOVE to have a certified person do some work for them for
free. It's a win win for both of you.
Ramon
For anyone working in technology with dreams of becoming
senior management, you might be surprised to find that while your hard
technical skills will get you so far, it will be your softer skills that will
take you the rest of the way.
By soft skills, I mean those skills that are part of day to
day life as a senior manager: Writing a
clear and concise memorandum, listening, communicating, public speaking,
running a meeting, conducting interviews, and managing people and resources to
accomplish objectives.
These skills are not found in your study guide for your MCSE
or your Oracle Database handbook. They
are acquired by some if they are lucky through formal education, while others
have had to pick them up over time by modeling others. Often times, it is a combination of both.
I was most fortunate to have a class while pursuing my
MBA at the University of Louisville that was called ?Leadership?. It was taught by the Executive in Residence
at the time, T. Ballard Morton. It was
and remains the most important class I ever had in a university setting and the
one class whose content I use every single day of my work life. I want to publicly thank Mr. Morton for
coming up with such a class in the first place and for making such an impact in
my life. You can read his thoughts here
on the class and how he came up with it as well as what he stressed to us
budding managers.
For those of you who do not have a T. Ballard Morton in your
life, I wanted to share a few of the golden nuggets with you that he provided
to me during that wonderful semester under his tutelage.
The first nugget is this book: The Elements of Style. If you
don?t have it, go get it. If you do, reacquaint yourself with
it. What is this book? I quote Wikipedia ?The Elements of Style ("the
little book" ? 1918,
"Strunk & White") is an American
English writing
style
guide originally detailing eight elementary rules of usage, ten elementary
principles of composition, "a few matters of form" and a list of
words or expressions described by its prescriptivist
authors as being commonly misused. Updated editions of the
paperback book are often required reading for American high school and college
composition classes.? It is
invaluable. I had lost my copy after a
few moves and just recently reacquired it.
It is not just must reading,
you need to try to commit as much of it to memory as possible.
The second gem is public speaking. You don?t need a book here per se (although there are some good
ones out there) ? you need practice.
How to get it? I had the luxury
of doing a great deal of it in class before having to do it in a work setting,
but if you can?t find a class, Toastmasters International is a great way to get it.
The third gem: ?How to Get Your Point Across in 30 Seconds or Less? by Milo Frank. It is an oldie but a goody. I also recommend his ?How to Run a Successful Meeting in Half the
Time?. Both books will aid in your
effective communication with those around you.
The fourth gem
unfortunately is out of print but I have found a very effective replacement in
?Listening: The Forgotten Skill: A Self-Teaching Guide? by Madelyn
Burley-Allen.
The fifth gem is MANAGEMENT & MACHIAVELLI : A Prescription for Success in Your
Business (Paperback) by Antony
Jay. This book will give you some insight into
corporate politics and is a great book for reflection on your own organization.
The sixth gem didn?t come from his class but I
have found it very valuable when having to run meetings using parliamentary
procedure. ?Roberts Rules in Plain
English? by Doris P. Zimmerman.
Lastly, try and find a mentor. If you are fortunate, you have one working
with you everyday; you just haven?t taken advantage of it yet. They don?t have to be in the same department
as you or even organization. Here is an
excellent article on finding mentors.
I hope that by pointing out some of the tools that were
placed in my toolbox early on in my career you too can benefit as you climb
your way up your career ladder.
Good luck!
Keep up with the issues and challenges that uniquely affect
public-sector IT with TechRepublic's free Government IT newsletter,
delivered each Tuesday. Automatically sign up today!
by genat
Excellent article, could not agree more!
Over and over again I have run across this problem in many
organizations - brilliant, talented tech people just can not get their
point across...
Thanks for this article!
by gmuscle
Very good points, I've found that Interpersonal Skills are key.
by jackinthebox
Nice advice for everyone.
It points out the both skills are important for career development.
by skicat
All very true. There are often discussions regarding the Education versus Experience debate or the Degree versus Certification. I believe college is not for everyone and not everyone is "management material". On that note, I have read several of the books there and they are a big help for anyone who does have aspirations beyond the trenches. The two biggest skills I see are verbal skills and social skills. If you cannot communicate your issue clearly, you will lose your audience. If all you can talk about is what your PC/server/router did that day, you need to read something other than the tech magazines and device manuals (half serious, half in jest).
An article on open source software and commercial software mixing
well? You know I'm all over it being the open source proponent
that I am. Check it out here.
A week or so ago I pointed out that a house bill on data security was
likely to get approved. Not sure if this one co-opted it but
check out this brief on senate bill S. 1789.
This article
on text messages that self destruct begs a lot of questions for use in
both the public and private arenas in areas where all communications
are to be saved. Now conversations can be had in which there is
no record of the occurence except tell tale software that does the
deleting. Would even having the software on a mobile device that
is used for conversations intended to be public/and or of record be
considered unethical or a violation of statute? Things that make
you go hmmmm.
Proposing a 27 million dollar budget package that boosts technology in
Virginia Universities, particularly in the area of modeling and
simulation has Virginia's Governor Warner in the news and the Virginia
Universities bubbling with excitement over the possibilities. Read more about it here:
I have been involved in some vigorous and refreshing discussions the last couple of days regarding the mission and purpose of IT within government, and I have settled upon a couple of ideas that are neither new or earth shaking but have some new relevance to me as a deliverer of IT services because of the stimulating discussion.
This thought plays out in a number of ways, including how you deliver your services, infrastructure, customer focus, etc. But one of the most important ways it plays out is in how you collect data and how you can slice it and dice it. Most importantly, are you collecting data that is both meaningful to the organization AND the legislative bodies that make appropriations, and are you able to present that data broken down by political district? Because, as someone once said, ?All politics is local?.
So how does this translate to data collection and dissemination? Simply put, this means being able to take your data and make it meaningful to a commissioner, legislator, board member, or the like. Often times this means breaking down data collected by some sort of meaningful boundary ? whether it is region, state, county, city, census tract, or political district ? or perhaps all of the above depending on the scope and size of your organization.
Often times, when creating data structures to meet the needs of the organization, one often forgets, not only to capture data elements that make sense regarding the target audience of the application, but also to insure that there are data elements in place that can allow you to tie the data back to one of the boundaries mentioned above. Here is an example:
An organization collecting water quality samples will obviously be concerned about collecting the precise Geographic Information Systems (GIS) coordinates of where the sample was taken. While this is well and good, for we now know where in the stream or lake or river the sample was taken, it is important to take the next step. That step is to make sure that we can tie those locations back to a boundary that can be used to make the data relevant to those that control purse strings. The more granular the boundary, the better. If you can take your data and say, "Well commissioner, our data indicates that the water quality in your district is three times as bad as those in your neighboring districts," you can perk up a politician's ears long enough for him or her to perhaps ask why and also how much and what do we need to do to fix that?
Like I said, this is neither new nor earth shattering, but sometimes it is lost among all the other noise regarding the need for data collection. Because for most government agencies, no matter how important their mission, if they can't communicate their need for funds in a way that is relevant and motivating to someone who controls or influences the purse strings, then they will be left with nothing more than continuation budgets ? or worse ? having to make do with less.
I may have mentioned this before, but I once worked with an EMS Director who was a master of manipulating his data in accordance with commissioner districts. Because of this, he was a force to be reckoned with when it came to budget hearings. He had all of his stats broken down in meaningful ways to the commissioners and could almost always combat an attempt to curb his budget. Usually with a comment like, "Certainly commissioner, we can accommodate the cuts you are recommending. Which of the 300 anticipated calls that we get from your district based on last year's statistics should we let die first because we cannot respond in a timely fashion?" Powerful stuff there.
Obviously this kind of data manipulation often involves GIS capabilities, using tools from ESRI, or now even Google. So if you aren't using these tools in your organization, you should be including them in your strategic plan. Other useful tools or data can be gotten from the Census Bureau and the U.S. Postal Service.
For IT departments, this concept is significant. The more you can do to educate and drive the organizations you support to provide information in this way, the better you will do at garnering the funds you need to operate. So, make sure you develop the capabilities in your shop and become evangelists for this way of thinking. It will not only serve your customers better, it will also help you in the long run.
Keep up with the issues and challenges that uniquely affect public-sector IT with TechRepublic's free Government IT newsletter, delivered each Tuesday. Automatically sign up today!
by j alley
While I agree with the need to gather sufficient data and provide facilities to analyze data in a large number of ways I found myself feeling insulted at the narrow parochial view promoted here. There are two strong reasons to avoid the approach to seeking funding that Ramon presents here.
Far better to use this valuable information to show the benefits of collaboration and shared services across departments and organizations. Better to free up funds for higher purposes, and to deliver integrated services to the taxpayer. Better to use the information to allow decision-makers to understand all the implications as they make difficult choices among the services to be provided and the bite to take out of taxpayers. It serves no-one's interest to provide unbalanced information that may tilt decisions in your way to the detriment of the public we serve.
by madtechgirl
Good point. We are starting a huge business intelligence and data mining project. We're starting with current state discovery so we can give the executives a realistic gap analysis when they tell us what they want. It will be intrigueing to see if anyone in the agency connects to the funding issue.
by jmgarvin
Hello future funding for Greenbranch ;-)
Actually, I'm quite excited and would love to see this happen. Excellent! I hope that the US also gets on the ball and starts teaching science and math to our kids in K-12!!! Jeez....
Note to the US public schools: Please teach the 3 R's. There is no reason to teach ID if students can't even spell it or define it. Also, why teach bother teaching science if students don't know the difference between a hypothesis and theory. Oh and math is a pretty good skill too...considering that many students can't do simple multiplication or division in their head!!!
For an IT service provider, it's often easy to forget that
there is a human/social aspect of our work. Often, the reactions of people to
our technological deployments can surprise us, because we are so focused on the
technical side and "helping business to work harder/smarter." An
interesting consequence of this fact was brought to my attention today, and it
made me have one of those "aha!" moments.
A colleague of mine happened to have the foresight to offer
up a Wiki-like tool to a group of individuals who often work together to form a
political agenda. Prior to this Wiki experiment, the group of individuals
worked on their agenda via e-mails and meetings, not unlike many of us do on a
day-to-day basis. However, it was decided that it would be an efficient and
effective use of technology to stop the e-mail carousel and the numerous
meetings to work on the agenda via a Wiki tool. Makes sense doesn't it?
All the conversations are recorded in one place and everyone
has the opportunity to comment. Furthermore, there would be greatly reduced
travel (if any) and people could comment/collaborate at anytime, day or night. What
a technology tour de force!
Proud as mother hens, the technology was rolled out to the
group of users with fanfare and high hopes. After all, this was the perfect
application of technology to aid in a process. Why would anyone disagree?
Whoa! In our zeal to provide the whole "work smarter"
shtick, we ignored the fact that we were in fact changing a complex social dynamic.
Think about it. If the normal process for hammering out any sort of outcome is
to meet face to face and exchange e-mails, there is a great deal of room to
practice the use of power. You know that in any sort of meeting, it is easy for
one, two, or a just a handful of people to control the conversation. Some
people will get their points across while others may never be heard from.
Taking things from a face-to-face process to a virtual one
means that some people who are adept at controlling meetings suddenly find
themselves with less power to influence, while those that might not have ever
had their voices heard, suddenly have a voice. In a Wiki, everyone?s voice is
the same volume.
Needless to say, as the process moved forward, we found
those that loved the idea and those who had some disdain for it. Bet you can
guess which camps they probably were members of.
Now, those that are more tech-savvy know that even in the
online world, there are ways to get your voice heard above the din, but it is
harder to do so and harder to squelch voices than in our normal conversational
activities. My guess is that as the experiment proceeds, some will become
experts at the process, but overall, I think it is a healthy exercise that will
lead to better outcomes.
But to take a moment to pause and think about how our
activities actually can and do change the social dynamics of an organization is
actually both daunting and breathtaking at the same time. We deal on a daily
basis with the basic processes of our organizations--shaping them, enhancing
them, or unfortunately, sometimes detracting from them. There are few other
functions, other than IT, that can cut across an organization and introduce
change like we can.
As someone said before, "With great power, comes great
responsibility," and we need to be cognizant of the fact that what may
seem to be a change for the better when we introduce new technologies, may in
fact have some nontechnical disadvantages that we did not anticipate. This insight
is especially important to analysts, architects, and developers.
So heading into 2006 and anticipating the rush of new
technologies appearing on what sometimes seems a per-second basis, it is
important to take a step back and remember that we work in organizations made
up of humans. Our work does have consequences--some intended and some not-- and
it is worthwhile to have a step in our planning processes to consider what
those consequences might be. Call them part of your risk management plan, if
you need a place to put that kind of thinking, but take the time to do it. It
will prove worthwhile in the long-run.
by madtechgirl
I agree, it is paramount to consider social and political ramifications. We technical types tend to see the logical benefit and we often don't understand why we come up against roadblocks. Many times it is due to power plays being undermined. A straight forward way to communicate thwarts those who rely on their personality, voice and presentation dynamics. A great tool that saves time and money often makes someone's job obsolete. There are many social and political aspects that IT should be aware of before starting a project. Then it is the leader's responsibility to know how to "market" the idea to get around those roadblocks.
Here
is a fascinating article detailing a security audit and a team of
security experts as thy performed a vulnerability
assessment--simulating an attack on a Fortune 500 company. Check
it out!
by jmgarvin
Thanks! Very interesting read and a good starting point for seeing how to Red Team!
Looking for a place to check on the latest information regarding
compliance with Federal and State regulations? Well besides
TechRepublic, which is always an excellent source of information, check
out Compliance Pipeline. I think you will find it useful.
By the time you read this it will be 2006. Depending on what predictions you have read and when you have read them, the world should have ended by now, Big Brother should be running our lives, or we should be some kind of race of Cyborgs.
Personally, I am mostly disappointed that we don't have beds that can make themselves by now. Seriously though, as I was making my short commute (thank goodness!) to work today, I thought about telecommuting.
For many years I drove over an hour to work each day and spent the better part of 4 hours on the average in traffic of some sort. In the mid to late 90's, telecommuting was born, and it was going to be the wave of the future. What happened?
Now that we have widely available broadband capability, laptops, PDAs, cell phones, Instant Messaging, Blackberrys, email, distance learning, video conferencing, collaboration tools, VPN, and terminal services, why the heck are we coming into the office?
I ask this question because, clearly, it is not technology that is keeping us from staying home. There is more to it than that. You would think that given all the purported benefits, employers would be glad to have you work at home. Let's take a look at some of them:
Sounds pretty good to me, so why the reluctance? Oh, you will hear about issues regarding insurance coverage in the home office, safety in the home office, and information security, but all these can be worked around. So there has to be something else.
The something else is the belief that if you are not sitting at your desk in your office, you can't possibly be working. It's an old-fashioned notion that if you are out of sight, you must be loafing. Many managers feel this way ? and I am willing to bet that much of the general public feels this way too. Additionally, many managers do not manage by objectives/productivity, so the only way they know how to manage you is by being able to walk up and see you "working" at your desk.
This is a shame because a large amount of government work could be done from the home, saving the government considerable amounts of tax-payer money. But in order to do so, leadership/management has to have the mindset that telework (the new word for telecommuting) is a good thing, and they have to be willing to work to put the processes and capabilities in place to allow it to happen. This can involve infrastructure issues, employee and management training, some process re-engineering, etc. But the effort can be well worth it.
Also, keep in mind that telework does not necessarily mean disowning the office completely. In fact, many teleworkers do come into the office 2 to 3 days a week. After all, there is value to face-to-face work as well. But the "office" can mean shared work spaces in a smaller building using less equipment and, more importantly, costing less to own and operate.
Yes, I understand that some jobs are more suited to this style of work than others, and you can't make someone a hamburger via a broadband connection. However, there are more jobs that suit telework than you think. Contemplate this: How many of your workers sit in an office or cube all day and their only interaction with people is via the phone or PC except when someone pokes their head into their space or they have to attend a meeting? Hmm, more than you expected isn't it?
I realize that to many senior managers, I am speaking heresy, and that embracing telework would mean the end of their organization as they know it. However, those that are a little more forward thinking might come to realize that this may be one way for government to keep their best and brightest for longer periods of time, in addition to reaping the benefits mentioned above.
Obviously, this concept is not beyond some government officials because Arizona, (http://www.teleworkarizona.com/) California, Maryland, Minnesota, North Carolina, and Oregon require state agencies to implement teleworking programs.
I suggest that you browse some of the above mentioned states' Web sites as well as these resources: The Telework Collaborative (http://www.teleworkcollaborative.com/) The Telework Coalition (http://www.telcoa.org/), and The Federal Government's Office of Personnel Management (http://www.telework.gov/documents/tw_rpt03/status-toc.asp) and see if telework can make sense in your organization.
Perhaps by 2010 we will have a bed that can make itself, in the meantime, let's try to utilize the freedom that comes with all this great technology at our disposal.
By the time you read this it will be 2006. Depending on what predictions you have read and when you have read them, the world should have ended by now, Big Brother should be running our lives, or we should be some kind of race of Cyborgs.
Personally, I am mostly disappointed that we don't have beds that can make themselves by now. Seriously though, as I was making my short commute (thank goodness!) to work today, I thought about telecommuting.
For many years I drove over an hour to work each day and spent the better part of 4 hours on the average in traffic of some sort. In the mid to late 90's, telecommuting was born, and it was going to be the wave of the future. What happened?
Now that we have widely available broadband capability, laptops, PDAs, cell phones, Instant Messaging, Blackberrys, email, distance learning, video conferencing, collaboration tools, VPN, and terminal services, why the heck are we coming into the office?
I ask this question because, clearly, it is not technology that is keeping us from staying home. There is more to it than that. You would think that given all the purported benefits, employers would be glad to have you work at home. Let's take a look at some of them:
Sounds pretty good to me, so why the reluctance? Oh, you will hear about issues regarding insurance coverage in the home office, safety in the home office, and information security, but all these can be worked around. So there has to be something else.
The something else is the belief that if you are not sitting at your desk in your office, you can't possibly be working. It's an old-fashioned notion that if you are out of sight, you must be loafing. Many managers feel this way ? and I am willing to bet that much of the general public feels this way too. Additionally, many managers do not manage by objectives/productivity, so the only way they know how to manage you is by being able to walk up and see you "working" at your desk.
This is a shame because a large amount of government work could be done from the home, saving the government considerable amounts of tax-payer money. But in order to do so, leadership/management has to have the mindset that telework (the new word for telecommuting) is a good thing, and they have to be willing to work to put the processes and capabilities in place to allow it to happen. This can involve infrastructure issues, employee and management training, some process re-engineering, etc. But the effort can be well worth it.
Also, keep in mind that telework does not necessarily mean disowning the office completely. In fact, many teleworkers do come into the office 2 to 3 days a week. After all, there is value to face-to-face work as well. But the "office" can mean shared work spaces in a smaller building using less equipment and, more importantly, costing less to own and operate.
Yes, I understand that some jobs are more suited to this style of work than others, and you can't make someone a hamburger via a broadband connection. However, there are more jobs that suit telework than you think. Contemplate this: How many of your workers sit in an office or cube all day and their only interaction with people is via the phone or PC except when someone pokes their head into their space or they have to attend a meeting? Hmm, more than you expected isn't it?
I realize that to many senior managers, I am speaking heresy, and that embracing telework would mean the end of their organization as they know it. However, those that are a little more forward thinking might come to realize that this may be one way for government to keep their best and brightest for longer periods of time, in addition to reaping the benefits mentioned above.
Obviously, this concept is not beyond some government officials because Arizona, (http://www.teleworkarizona.com/) California, Maryland, Minnesota, North Carolina, and Oregon require state agencies to implement teleworking programs.
I suggest that you browse some of the above mentioned states' Web sites as well as these resources: The Telework Collaborative (http://www.teleworkcollaborative.com/) The Telework Coalition (http://www.telcoa.org/), and The Federal Government's Office of Personnel Management (http://www.telework.gov/documents/tw_rpt03/status-toc.asp) and see if telework can make sense in your organization.
Perhaps by 2010 we will have a bed that can make itself, in the meantime, let's try to utilize the freedom that comes with all this great technology at our disposal.
by whistl3r
by dc guy
I can't believe that there is a second voice on TR extolling the virtues of telecommuting. Your focus is on the public sector, but in the private sector the potential benefits of telecommuting are just as rich and the objections to it are just as refutable.
The STATED objections fall into two categories:
Managers: "I can't tell if you're working if I can't spy on you physically." The people who say this should have tattoos on their foreheads so we can herd them into places where they do the least damage. In one sentence they've conveniently told us that they have no management skills whatsoever. They don't understand the fallacy of Authority by Measurement: You get more of what you measure. If you measure output, you get more output. If you simply measure attendance, all you get is more attendance; you don't necessarily get more work. For two or three generations, American office workers have been trained to LOOK like they're working. Computers have made this even easier.
Employees: "I need the social interaction of the workplace." This may be true, but all I can say to you is that an entire generation of younger workers is growing up with IM, cell phones, BBSs, e-mail, and chat rooms. These kids have been living with virtual companionship. If you can't adapt to their world, then you had better just step out of their way.
Notwithstanding all of this, telecommuting experiments were widespread and fabulously successful--in the early 1990s, back before we even had broadband, webcams, and NetMeeting. Both managers and employees overcame the then-substantial problems of working at home. It seemed a safe prediction that by 2005 most office workers would have moved away from urban areas--relieving the traffic, pollution, crowding, and real estate inflation problems of both the workers and the urban areas.
What went wrong? It started shortly after the 2000 elections. In corporation after corporation, employees received terse e-mails stating simply that as of a certain date the telecommuting program would be suspended, without explanation. Inquiries received the simple answer that "it wasn't working out," despite the fact that everyone throughout the company knew that it was.
Gosh, what could be wrong with telecommuting that would cause corporate leaders to squelch it and government not to use its heavy hand to reconstruct them? Higher productivity, lower turnover, lower error/defect rate, reduced absenteeism, no onsite gyms, cafeterias, and daycare centers to manage. And the social benefits: families spending more time together, children being raised by their parents, more home-cooked meals, more time for exercise, church, and education.
Vastly reduced consumption of gasoline...
Uh oh. I just answered my own question. For a moment I forgot who's running the country.
by laura taylor
It is a matter of trust. Many companies think that if they let you work from home, you'll be sitting around watching re-runs of Happy Days instead of actually working on their behalf. Personally, I tend to think this is often the case. Trusted individuals often get to work from home, but usually you have to prove that you are trustworthy first.
by madtechgirl
Telecommuting is not for everyone even if their job is such that they could perform the work at home. Many people do not have the self discipline to work at home. Home is a place to relax and unwind with many distractions. Many times the worker has the discipline but the family does not. Sometimes it is very difficult to train the family that "mommy or daddy is working, do not interrupt", sometimes it's the spouse - roommate or significant other that can't keep themselves from interrupting work. Then again there are some workers who would simply rather keep the office separate from the home.
by nees
I support telework. I'm co-leader of a virtual private charitable group which meets once a week and telecommutes the rest of the time. Requests are transmitted instantly. Feedback to those responding to needs is flash-fast and the best part is instantly virtually seeing the scope of our influence. It's fun, and we're all continuously connected. We work faster and more effectively with each other. We have complete confidence that our own needs will be met when we need it. It has speeded up our ability to be a cohesive group. With the popularity of homeschooling to avoid long daily commutes to/from a school building, telework is the way to go for families. It's the ultimate time and resource management.
by dc guy
Everyone keeps harping back to the same red herring: If I let them work at home they may slack off.
I've already stated my response to that one. If their performance drops off and doesn't return to benchmark after a reasonable time to adapt to the change, then do something about it. There are a lot of people out there who would be delighted to have the slacker's job and who would delight you with their performance.
You all seem to believe that managers can't tell whether their employees are working if they can't see them. COMPETENT managers can do that. Apparently none of you have spent a lot of time working for competent managers.
Competent managers rate their employees on how much work they get done, not how much time they spend doing it. I've got news for the incompetent managers: Your employees are slacking off at their desks. Why, right this very minute they may be reading a blog on TR instead of working. Can you tell the difference?
by msm
Everyone knows that not all jobs, nor are all workers, suited for telecommuting. In my personal experience, the killer was management who coudln't come to grips with not being able to physically "manage" a person. I worked for a couple of years as a successful telecommuter and then manager of telecommuting workers for a small but very successful consulting firm. Our workload ranged from Business Intelligence training (for which we had to show up) to web site development to Internet business strategy. Almost everyone within the company was under 30 years of age but me. I had no problem with virtual work - I typically worked MORE hours per day than I would when going into an office. The guys under me were given timelines for their projects (sure, more work for me but they needed deadlines), and we had set up a reporting structure so that all interested parties could easily keep up with what was going on with any projects.
Then the company hired in a general business manager (who was over me and all my telecommuters), who got his BA in business in 1964. He could never come to terms with the fact that we did not all go into a central office every day. He began literally harassing us all through email and by telephone, then calling "meetings" in person - we normally used NetMeeting or VoIP conference calls outside of our one-meeting-a-week, and the end result was that our productivity halved because of the drain this manager's style of "managing" put on our time - being constantly made to email or phone what we were doing every 45 minutes, made to submit daily reports of every single thing we touched during a day (even showing when we took lunch?!), and made to show up in person at an office at 3 in the afternoon for randomly called meetings killed us... two of my best programmers worked at night. I personally worked from about 6am to 3pm so I could be "done" with work when school was out, but about 70% of the time, I'd be back in my home office after dinner to "tidy things up." I averaged 10-12 hrs a day of literal work when I was working from home without interferrence generated by an old school manager. When new management took hold, instead of meeting in person once a week with the president of the company for updates, I was forced to show up at an office three or four times a week to be asked to "explain my email" or some other such idiocy. The new manager even rented a satellite office for all the telcommuters to meet.
Resentment over the drastic changes in practice, policy, and work attitude crumbled our corporate morale. One of my programmers was fired after he "missed" 10 days in a single month for chronic kidneystones, a condition we all knew he had - he never missed a deadline that I was aware of but he was "unavailable" to answer the phone or attend meetings because he couldn't drive when he was on the pain medication he was prescribed. My graphic artist was laid off because we were "taking so long to turn projects around" that suddenly cash was an issue and her work was the easiest thing to outsource or sub-contract - I bet renting that extra office had nothing to do with the cash crunch. My other programmer quit shortly thereafter, disgusted with his now 40-minute one-way office drive, three days a week. I hung around until the new manager himself, left, and the company folded. I inherited all their web hosting and web dev customers (who I still provide service for) and I've yet to ever meet any of these clients face to face. This was in June of 2001. My clients never had an issue with telecommuting and the original founder of the business never did, but boy, the middle manager literally wrecked the train.
Until the generational age of upper management shifts a little more, I think widespread telecommuting is still far, far, on the horizon, but it does work, and it works well when you have the right business model and the right people.
by wayne m.
Benefits of Informal Communication
Having gone over to the dark side (from software development to management), I recognize the benefits of informal communication that arise from having people physically colocated.
Most organizations, however, seem to put up as many roadblocks as possible to prevent informal communication. Software development staff is usually separated from the operations staff who will use the software, often times in different buildings, cities, or states. Discussions must follow the organizational hierarchy with the appropriate management levels at least involved, if not actively forwarding communications back and forth. All actions must be based on a formal, written artifact; forget about doing the obvious based on a 2-minute discussion. In environments such as this, the benefits of informal communication have been so effectively neutralized, that telecommuting appears beneficial.
Physical colocation of workers is really needed for effective software development. Unfortunately, most corporations do everything possible to ensure effective communication does not occur.
by dc guy
Well fine. Then you should continue to look for work that needs to be done on site. A whole generation of Americans is growing up into the workforce who are accustomed to virtual everything. You'd better get out of their way.
by issa.clarke
I agree with having people dedicatd to the Intranet. But I am biased being a member of an Intranet team myself. What I am curious about is what proportion of firms staff might be appropriate to designate to the Intranet.
In this world of worms, viruses, security vulnerabilities,
hardware and software non-interoperability, and just plain old malfunction, it's
a wonder sometimes that IT organizations can remember that they are service
providers.
Instead, because of the constant bombardment of threats and
malfunctions mentioned above, IT finds itself, almost by design, as IT
regulators rather than enablers, finding ways to tell the end user NO rather
than helping them find solutions to their business problems.
Stop and think about it. How many articles have you come
across recently (particularly regarding security) in which the end user is
described as a threat or a risk and measures need to be put into place to guard
against them/protect them from themselves?
This is not to say that any of what I mentioned above is
wrong, but there comes a point--when in the pursuit of a bullet-proof
system/network--that a mentality of regulator takes over the IT organization,
and it becomes more about what the user can't do rather than how we can help
the user to do something.
This then begins to permeate the culture of the organization,
and you end up with an oppressive IT organization that seems more like an
overlord than an enabler. Then the IT organization wonders why they aren't
being considered a strategic business partner! The fact of the matter is, no
one is going to want to partner with you when they hate your guts.
On the flip side, we know that securing the computing
environment and having well thought out policies and procedures is crucial to
running an effective and efficient IT organization. Please note that I said "well
thought out," and not knee-jerk or reactionary policies and procedures, which
is often the case, particularly when an IT shop is struggling to do more with
less and barely managing to keep the wheels on things. Then it is easier to
make wide-ranging, blanket policies that shut down many things for the sake of
security or operations.
The key word for this discussion is balance. By balance one
means "to be in or come into equilibrium." In that sense, it isn't
regulation or advocacy; it is the healthy balance of both.
So when setting a policy, a thoughtful process should take
place as to what the impact of the policy will be in regards to processes and
procedures and employees' work lives. I will give you an example: Many IT
organizations these days have made the blanket policy to block an employee's
access to personal e-mail via a Web browser. Therefore, access to Hotmail,
Earthlink, or Yahoo accounts is made impossible. This is done for the sake of
security.
Now I ask you, is this going too far for the sake of
security? In my opinion, the answer is yes, and I will give you my reason why.
Most governmental organizations treat the use of Web
browsing and e-mail like the telephone. Some personal use is permitted, but it
is not to be abused. Government employees surf the Web during lunch and breaks
and communicate personal business via e-mail on a fairly regular basis.
Now I personally, as a government CIO who knows that all
communications are accessible via open record laws, would prefer my
organization's employees to do their personal communications via their home ISP
using Web mail. This keeps organizational mail strictly for business while
giving the employee the legitimate ability to address personal issues via e-mail
just as they do with the telephone. With this, you have a nice clean separation
between work and personal e-mail and you can work to strictly enforce the no-personal-use
of company e-mail.
The majority of the large ISPs already employ virus scanning
within their Web mail interface and most IT organizations are employing
anti-virus software at the desktop, so the actual risk is that there is a hole
in which IT cannot control 100% of the content going into and out of the
organizational network.
Is that worth taking away the ability to use personal Web
mail and forcing personal traffic onto the corporate network? This is where
balance comes into play. If my organization is the CIA, I might feel very
justified in doing so. In fact, in their case, their corporate network and the
outside world probably meet in a very, very restricted way.
However, most of us aren't working for the CIA and keeping
state secrets from leaving the organization is not priority #1. For many of us,
balance would mean allowing access for the reason explained above.
This is only one example of probably dozens of policy
decisions that are made each year with a regulatory frame of mind, rather than
one where the needs of the end user are thoroughly considered.
Again, I am not trying to paint IT as a bad guy, but more
importantly, trying to point out that in our zeal to protect ourselves and our
organizations, one can go too far in one direction and tip the scales so far
that you create an environment that is difficult to work in. This is where IT governance
committees can play a huge part in helping to review policy to insure that all
aspects are considered before policies are put into place.
Lastly, remember that policies are not chiseled in
stone. They need to be reviewed at least
on a yearly basis to see if they are still relevant and if there have been
any new developments technologically that--if put into place--can invalidate
them.
by pmoleski
Customer service is what it is all about. Our job is to provide the services needed to allow the employees to be productive in their jobs and get the work of government done.
Setting HR policy is not what our jobs are about. Technical support for the implementing that policy is. However, we do not get away totally free on this point. In our organization we work in partnership with the HR branch that issues the policies for appropriate use of time and government resources. These guidelines apply as equally to a telephone as they do to computing resources. The policies take into account what the technology can and cannot do. I fully agree that the trick is to find the balance between implementing security and allowing a work home life balance. We have set up the policies with three categories equating roughly to okay, iffy, and not appropriate. The incidental use of government time, for things like personal email, is similar to use of the telephone for personal calls. It has to be reasonable and not in conflict of interest with your job. All of this falls into the middle category of what I call iffy or others call the grey area.
When it comes down to it I will err of the side of security at work because people have the option of using a phone or doing work from home on a computer. It is a nice to have, not a must have for them to use the company infrastructure for personal business. I personally think that the slope from incidental use to inappropriate use is a short one. If employees know that everything they do using email of any kind at work is a government record then they probably should not be using it for personal business. Before we had email no one would have used government property to send letters for personal business. Just because the electronic world makes it easier the principles of appropriate use are not any less.
Having said all the above I will come off my soapbox. Times change and so do the ways we communicate. It is not possible or I think desirable to try to ignore the Internet if we want to be a work place that is attractive to the new generation that is growing up talking to ten people at a time using instant messaging. Forget email that is for us old folks!
We allow people to access web based email. We do not allow the use of instant messaging. A great deal of emphasis is on the security appliance that does the deep packet scanning/virus/firewall/spam/spyware and everything else including the kitchen sink, to protect the front door and on the processes for keeping the desktops tops up to date with security, patches, etc as the second line of defence.
Without getting into an in-depth technical discussion of which I will for sure get things wrong beyond a high level, I do think it is possible to keep good relations with the end clients by keeping the policy ownership where it should be with the HR branch and then providing top notch technical implementation support for that policy. I fully agree that if the IT folks are viewed as setting the policy then we become the bad guys and risk becoming the negative organization you mention. I view it as a positive technical challenge for our IT security staff to find ways to stay ahead of (at least keep up with?) the bad guys but also support the work life balance mandated in our appropriate use policies.
Phil
by saintgeorge
Imagine that after 9/11, to ensure air safety, people were by default
forbidden to fly, that to do so they had to get a special permits, some
kind of passport signed by the appropriate authorities, after careful
consideration by the intervining commities, that anyone and anything
close to an airport was considered suspicious and dragged in for
interrogation.
Sounds familar? I'm not talking about the Soviet Union, but about some
of the companies and organizations to which I provide outsourced IT
services. Of course, there is something to be said about boundaries for
employees who would otherwise spend half of their working hours
chatting, playing online casino or downloading mp3s and porn. But that
has nothing to do with surrounding the area with virtual razor wire,
steel armor and machine-gun nests to kill everything that move trying
to get in or out, killing business flexibility and response time, just
to avoid the unavoidable virus or spyware...
efectively killing the business to save it.
If your looking for a sweet tool that really enhances Outlook's search
capabilities, you need to grab LookOut for Outlook for free while you
can before it is integrated into the MSN toolbar. You can get it
right here and it works with: Version 1.3 is the stable, released version
of Lookout. Works with Outlook 2000,
Outlook XP and Outlook 2003, running
on Windows 2000 or later. Requires
the Microsoft .NET Framework 1.1.
Enjoy!
If you don't provide a secure alternative, employees will try nearly
everything that pops on the market in order to IM, both within and
outside your corporate firewall. Give them what they are
clamoring for while providing the security and auditability that your
organization needs by using Novell's IM client. Read more about
it here:
If you were born between 1946 and 1964 you are part of the "baby
boom" generation. Data from the 2000 U.S. Census estimates that the group
that holds the "boomer" moniker is made up of at least 82,826,479
individuals. I sometimes feel that 82 million of them work in government.
Beginning in 2011, a shift in the labor force is going to
occur because the front edge of the boomer generation is going to turn 65. While
many are concerned about a potential labor shortage, I am mostly concerned
about a sudden and continuous brain drain from our organizations.
All around me are workers who are at or nearing retirement
depending on when they actually started working for government. Many of these
are middle and senior managers who carry with them a great deal of
institutional knowledge. I know of whole sections and departments that will be
retiring at the same time or following each other out the door continuously for
several years. If this doesn't bother you, it should. Why? Mainly because
government usually does a horrible job of cross-training and making sure that
there is more than one person responsible for a function.
It's not that government workers don't like to share
knowledge (I'm being kind here) but that government organizations typically are
not staffed with a lot of redundancy in positions, and the workers in these
positions generally wear many hats. Which means two things: One, that there is
a great breadth of knowledge contained in a single individual and two, that
person is usually too busy to document their knowledge or take the time to
share it with someone who can step in and fill their shoes. So when they go, so
does their knowledge.
As I look around organizations that I'm familiar with, I see
this as a real potential problem. It's not good to have all your "old"
hands leaving at or near the same time. But at the same time, we can't prevent
it. So in order to prevent the potential problem, we need to prepare for it.
Kind of like the Y2K problem. Proper preparation led to a potential disaster
being hardly a flash in the pan.
So what can we do to prepare? Well there are a number of
things that we can do if our organizations can wrap themselves around the fact
that there is change coming, whether they like it or not. Here are some
suggestions in no particular order:
Personally, I have to deal with this issue now. I plan on
tackling it through mentoring, cross-training, and retraining, as well as
trying to establish a new way of doing business through tools such as Wikis and
Blogs. The point is, many of us will have to start dealing with this as time
draws nearer to 2011. Yes, it is only 2006, but time flies when you are getting
old ;-) So start preparing now.
by xuriwan
I was born in 1949.
In 1945, Dr V Bush wrote: "There is a new profession of trail blazers, those who find delight in the task of establishing useful trails through the enormous mass of the common record. The inheritance from the master becomes, not only his additions to the world's record, but for his disciples the entire scaffolding by which they were erected."
From what you have written, I believe, you too are concerned such trail blazers failed to materialise in any numbers and with no scaffolding erected the 'enormous mass of the common record' remains just that, but more massive and more difficult to analyse and transfer.
I have been trying for many years to persuade people - academics, professionals, government officers and so on - to consider another Bush insight he called associative indexing. My interpretation is that old lags like me convert their experience into something reusable. Learning from computer programming techniques, the idea is to identify physical things that are important to a particular activity and arrange them by hierarchical association (rather than alphabetically, for example).
Immediate results are molecular structures of 'cells', to each of which can be added explanations, advice and so on. I have been trying this out on www.xuriwan.net and it seems it can work. My experience is in the building industry, but as buildings lead onto many other human endeavours and concerns, I think there is ample scope at least for further discussion.
by mckinnej
Disaster, or Opportunity?
While some may see the pending "changing of the guard" as a bad thing, I'm more inclined to see it as a chance for the Government to get an infusion of some much-needed fresh blood. To be polite, let's just say some government workers are resistant to change. (How many times have you heard this one: :We've done it this way for 30 years...") Old processes and technologies that the private sector has left behind years ago are still abundant in the Government. The thinning of the resistance to change may enable the Government to move forward at an unprecedented rate.
by osumiller
I have worked in IT for the military, and that brings a whole new host
of problems to the "brain drain" scenario. Recently, my
organization experienced this problem when one of the most proficient
radio maintainers I have ever seen retired. With him went
knowledge that you just can't train in a school, and people don't learn
without having a lot of experience. The voice and data
communications via radio is one sector of government communications
that is facing some of the greatest challenges with these
changes. The younger generation can make a computer work all day
long, but making radio systems work (especially the newer ones with all
the extras) is sometimes a really huge task if you don't already have a
really good idea about HOW radio communications work. With the
older generation, the knowledge is leaving, and the younger generation
just isn't learning it unless they are really special people, or they
have studied a lot of physics.
Where are these types of specialized segments going to find replacement
people/technology? There are a lot of vast and disturbing changes
coming.
by bloggr44
I was born in 1955.
After years of being the new guy, or told how smart I was for my age, I suddenly find myself less than 5 years from CSRS minimum retirement age. And, as you pointed out, I'm certainly not alone. I manage an IT department for a large Governmental organization. With a permanent staff of 4 (including myself), we manage 4,000 users and 1,500 computers located across 7500 square miles. Here's the more important information: I'm the youngest person in my department. That means we're all ready to go.
Does this worry our employer? Maybe or maybe not.
For about a dozen years, I've watched my organization manage staffing by natural selection. Positions in IS are routinely absorbed back into the collective whenever someone retires or dies. Those positions are then often reborn elsewhere (usually at headquarters or reporting to headquarters, and usually at a higher level, and usually filled by a contractor). So we get kind of a double-whammy. Not only do we lose the experience of the person who's gone. We lose the position that was, at some point in the past, approved as necessary to operations. And there are other downsides to this uncontrolled grab. We lose our career ladders, for example.
Yet the bosses decry the aging workforce at every meeting. Something has to be done, they say. But, leading by example, they fill new positions with people outside of the company, usually former contractors with single skill sets and no comprehensive idea of our environment. They come in a top grade level to be competitive with the rest of the public sector, so they're resented by others who leave them to flounder their way around.
For this aging boomer, the answers are obvious. Just as it's been done since I got into IS 20 years ago, IS will have to adapt to the realities of today's business. There is no apprentice program in corporate America today. There are few mentors. New young folks will have to come in and reinvent the wheel, taking advantage of new technologies to hopefully create a working wheel quickly - maybe even better wheels. With luck, they'll gain a little inside experience as contractors before they get hired off the street.
Could the angst have been decreased and productivity improved through a better succession plan? Yes. Will anyone see that and make substantial changes at the corporate level to support that change. I doubt it. They're way too busy feathering their own nests.
Actually, the cruelest irony of all is that many of my cohorts have been retiring and getting hired back as contractors. In some way, that seems like the way to insure a complete breakdown of the system. Not only have we destroyed our internal career paths, now we're taking away the learning opportunities for outside contractors. Who will we hire to do these jobs when even the contractor workforce is filled with boomers?
by realme
I was born in 1954. I have worked in government since 1993 and in an IT position since 1996. My experience with government tells me that one of the biggest barriers to cross-training in government is that we are not allowed to have any "overlap" with a departing employee. In other words, you can not hire until someone is actually physically gone. So, there frequently is no training, or, minimally, the "knowledge" that the departing employee has/had is not passed directly to the replacement worker. It gets there through an intermediary that has been "appointed" (on top of their regular duties) to make sure the new hire knows what he/she needs to know to get the job done. The intermediary knows just enough to get the job done but has no real experience doing it, so the wheel gets re-invented and something gets left out usually. Occassionally, someone from the organization gets the vacant position which can be a real boon to the organization, but not always, and generally it's someone from the outside that comes in. Even when the position is filled by an existing employee, there is frequently no cross-training before the old employee leaves, because they can't hire until the other person is gone. So, yes, I'm concerned about what will happen when all these "boomers" retire, myself included. Even documenting everything does not take into account the "exceptions to the rules," and something always gets left out.
by bobbypr
I?m a consultant for the IT industry and work a lot with government accounts. I see this very often at my clients and it is a situation management should pay more attention.
At first hand management should make an in depth analysis on the retiree?s tasks before he or she leaves. While there are some tasks that may look simple, you will be surprise of the many sub-tasks that some requires.
For example, I got to know an employee that for everybody her only work was doing forms data entry. While doing an analysis of her tasks, she had to evaluate each form and classify each in categories and for each category the data entry changed. The criteria she used, was something she learn from experience of her many years in the position. There was no document on how to do it. All the knowledge was on her mind.
There are other cases where a workplace has a documented workflow for a particular task, but an employee found a shortcut and it was never documented.
By making tasks analysis, and knowing how the information flows to and from that employee, and how that employee manages information, there?s a big chance to salvage that knowledge. This will be very helpful if you are planning to do a process reengineering.
Mentoring, as stated above, is also a good way of saving that knowledge, but you should be aware that:
by dc guy
"That government is best which governs least," said Founding Father Thomas Paine, and the past couple of decades of too-big-for-its-britches government have shown that this is still true.
The Boomer generation believed that government could solve all problems, and as a result we now have a deficit with twelve zeros, U.S. troops claiming to bring democracy to places that don't even have hospitals, virtually the entire world fed up with America, assets seized without due process, senior citizens removing their shoes in airports, and judges paid to prosecute people for merely annoying one another.
If the retirement of this generation brings government to a standstill, it may not be as universally lamented as the writer seems to fear. The IRS has been gridlocked for years, is anyone complaining?
Remember the little data breach that occured nearly a year ago that
possibly compromised the personal information of 163,000
Americans? Well ChoicePoint settled with the FTC for a 15 million
dollar fine. A drop in the bucket to ChoicePoint but the largest
fine in FTC history. Read the details here:
It's supposed to be out in February and I really really want to take a
serious look at this tablet/notebook. I think it will be just what the
doctor ordered for the government road warrior. Read more here:
I had a very interesting conversation with a colleague the
other day who works in a position nearly identical to mine and for an
organization that is very much like the one I work for. We spoke for nearly an
hour and after hanging up, I realized that although we shared very similar
hopes, expectations, goals and objectives, our strategies for achieving them were
going to be very different. Why? Because of our "parents."
Not our biological parents, in this case, but the often
dysfunctional branches of government that we lovingly refer to as the
legislative and executive branches of government. You can call one dad and the other mom (it doesn't matter which), but no matter what size your governmental
organization, you are a product of mom
and dad.
When mom and dad get along, and we happen to be one of their
favorite offspring, we can be showered with goodness, whether it's free-flowing
funding or loose oversight. To be one of the favored children is to be in
heaven!
However, when they don't get along, heaven help us. We can
get caught in a tug-of-war between the two branches in which the children have
to fend for themselves. Woe to you if you are one of the unfavored, left to
scramble for the crumbs available after the preferred children have received
their blessings.
The fact of the matter is, no matter how good you are or how
hard you try, much of what you can or can't do is a byproduct of the
interaction of these branches of government and the political winds that are
blowing at the time.
I know that many of the things that my colleague has
accomplished would be nothing short of a miracle if I could pull them off in my
environment, just because the political climates in which we operate are so
very different.
I say this not to be negative, but rather to remind you to
put your situation in perspective when making comparisons with similar
government organizations in other cities, counties, or states.
People like to make comparisons of cities or counties that
are "comparable". But comparable is a relative term. The fact of the
matter is, you might be part of the best darned IT shop in the nation for your
agencies relative size, except for the small matter that you have a staff of
only three and your funding is nearly non-existent. You can't compare your
situation with a "comparable" agency that has twice the employees and
plenty of funding for new initiatives.
Despite this reality, there are those (possibly including
yourself) who won't look at the particular circumstances and will fail to give
you the credit you deserve for your efforts. Therefore, we must be careful when
judging ourselves and looking at benchmarks. It can be too easy to criticize
yourself and jump to the wrong conclusions. The important thing to remember is
to do the best that you can with what you've got and try to effect the change
necessary to make things better.
Fortunately for us, our system of government ensures that
change does come every so often (sometimes too often), and the situation that we
find ourselves in now may not be the same situation months or years down the
road. If you become the favored child for awhile, be ready to step up and make
the most of the opportunity--for those times can be short lived.
So although I can't effect the same kinds of change my
colleague can at the moment, I can do my best to move my organization in the
right direction and plan for the time when the winds of political change are
more favorable--then, I will be ready.
It still amazes me that while the powers that control the
funding for IT in government want it to operate like a utility (always on, no
glitches or downtime, already there when you walk into a room), they want to
fund IT projects as one-time expenditures. As you and I know, IT is not a
one-time expenditure, but a continuous investment in resources to keep it
operating like the utility everyone expects.
So how do you go about acquiring the funds to keep
yourself operating? I have observed others' methods and tried several different
ways myself, and I thought I would throw them out to you for consideration and
possible use. There are pros and cons associated with all of them, and I will
try to mention a few for each.
The first method is what I call grab it while you
can. This method employs building everything--plus the kitchen sink and
a waste can or two--into your budget request for a particular item/project
(including the cost to operate it for several years). This is accomplished by
over buying or buying ahead for maintenance and services (like buying blocks of
hours that the vendor will carry over multiple years) or disguising operating
costs as part of the cost of a piece of equipment or software.
I personally don't care for this method and like to be up
front with my budgeting, but I have had my detailed budgets for projects
"massaged" by CFOs and budget officers to better enable them to get
funded. They knew that the time was right for a particular purchase and that
the opportunity to get funding for that type of project probably wouldn't come
around again any time soon. Y2K is a good example; the impacts of major
disasters like 9-11 or Katrina also influence project funding, as well as a
change in administration or leadership. These budget officers also knew that
there would be more flexibility in capital costs/funding that particular year
than in general revenue.
Grant funding is another way of grabbing
operating funds at the inception of a project. Obviously, getting grant funding
for a particular project can help offset current costs (especially if the
current project is already budgeted and approved) but often grants do allow for
administrative overhead in their funding. This administrative overhead can be
defined quite differently from grant to grant, as well as from one budget
office to the next, when interpreting the grant.
However, both of these methods leave you with the
eventuality of having to go back to the well to keep the IT department running.
So how do we acquire the funds to keep the wheels on? Some shops have gone to a
charge-back system--where they charge users of technology (in
other departments) a fee for service. I have seen this work through measured
services and aggregated costs that are passed on as charges. The problem with
the former is that you better be darn good at measuring--and some IT work is
hard to quantify as a charge. It also means you need to run a billing system of
some kind. An example of the latter would be a per-phone or data jack cost or
an FTE cost in which all the costs of your operation are aggregated and then
averaged out on a per unit basis. The problem with this method is that users
can end up paying for services they do not use and if you try and break those
out, it can get pretty messy, particularly when trying to justify the per-unit
charge.
One method that has been used in higher education is to
charge a technology fee. This fee is either a flat, one time-fee
per semester, year, or credit hour. Note that this is different than an
aggregated charge as described above because it is not designed to charge back
all the operations of IT. The fee is an acknowledgement that it takes dollars
to operate and improve IT operations, and the users are going to pick up part
of the tab. The national average per credit hour is somewhere between 5 and 10
dollars for those universities that charge a fee.
I have not seen this method employed in non-education
circles yet (if you have, please let me know and give details--I'm interested),
but it could have some merit in general government IT administration. I can
imagine a scenario where IT departments could charge a per-user fee that is
adjusted yearly with inflation to help offset the costs of continued
operations. This fee could be set at an amount--say $50 dollars per user--and
would be added to the budget of the IT department. These dollars would then be
added to the IT department's budget as additional funds-- not as
replacement funds for general revenue funds that they would already receive.
Yes, I realize that in the long run that there is one
pot of money and that these are all accounting games and none of this should
matter. However, the pot has to be divided and there is never enough money for
everything. How you go about making your budget requests can make a significant
difference in what you get from year to year. It is an ART not a science, and
logic plays very little into the final equation. Because IT is so often
overlooked or considered a necessary evil, it is important to ensure that we do
the best job possible come budget time. While my suggestions may or may not be
what you need to do in your environment, hopefully, they will plant some seeds
that will lend you some flexibility and creativity when approaching yours.
I've been running IT projects in the government for almost 18 years now
- and have directly experienced both of the first two funding
methods. In my particular case, what has worked best for me has
been a variation on the second method. In my experience, in the
government there is a cyclical swinging from centralized to
decentralized IT and back - and like it or not, there is often a fair
amount of empire building. When trying to get funding for a
centralized or pseudo centralized IT group - I've found that one fairly
effective method is to work fee for service but at the sub-organization
or project level. Start by figuring out what it would cost a part
of the organization (dept, division, branch, etc.) or a separate
project to provide the level of services your group provides - then
because of economies of scale, you offer those services to the
organization or project at some fraction of what it would cost them to
procure those services and resources themselves. Essentially, you
act like an outside agency or company selling its services. Each
branch, division, project, etc. kicks in funding depending on the level
of services and resources desired. Being an engineer and project
manager - sales were never my strongest area - but it has become
necessary. When improvements to the infrastructure are necessary
or desired you have to present the cost benefit analysis to each group
and let them know how those improvements will save them money, save
them time, make them more efficient, or make them more productive.
Also - in the government - project funding - particularly when the
project is funded by an outside organization or another part of the
government, is often one of the best sources of funding - but you have
to work with them early - to sell your groups services and resources
and get them to incorporate those funding requirements into their
project's budget early. An organizations budget is often tight
and moderately well defined - often times there is not much wiggle room
to reallocate funding to IT and the organization may be reluctant to do
so because it takes away from something else they want to do -- but
outside funded projects' budgets tend to be more fluid and flexible and
the funding sources may have deeper pockets.
by rourkejj
First of all, I have to confess that I have a very supportive senior management team in Schenectady County. We have taken an approach of charging back to departments based on our work order tracking system (can be combersome, however it allows me to build overhead and fringe costs into the billing rate).
What is more frustrating to me is the need for staffing resources. We continue to deliver new technologies to the 39 individual departments that we support, but have not been able to add any additional resources in 3 years. I'm still looking for the argument to add resources that works.
Sort by Trending