Government Technology
This is page 5 of the discussion. Read the opening post
After Hours
This is page 5 of the discussion. Read the opening post
by drfez
Ramon, that goes for every tool we use. Think of technology like this, you walk into Sears and buy a Craftsman wrench, walk out and put it on the hood of your car, does it magically fix the car? No more than fancy technology does our problems if we don't know how to use it and don't have a real understanding of the problems to be fixed. No silver bullets.
Dave Keith
by mr. tinker
This is one article I HAD TO SHARE with my kids... all 3 are older than 16 and have been raised with one adult who was always deeply involved in IT technology. The very thing I always told the kids: "Its a COMPUTER... not a toaster, so when you finally get to college you should NOT have to wake me at 3:00 am, because your PC crashed, you should know by that time how to backup and restore. 2 VERY fundamental things to learn NOW."
Allow me to step off the technology-bandstand...
by mr. tinker
ok... made a mistake there.
A person who wants to drive, is required by law to get a permit before they can be considered for a license to drive their vehicle on the road. The same SHOULD be true for driving your PC on the "Internet highway". PERIOD. I know of adults over the age of 45 who are NOW taking classes to learn to drive their spouse's cars....out of necessisty.
Conclusion: if you have the NEED/WANT to drive the Information Superhighway, than get help from qualified ADULTS not KIDS. TELL your supervisor or manager you NEED further training, or books, whatever it takes to be more productive at what's required of you. The trikle-down effect of YOUR newly found knowledge will only help you help your kids to not fall into the trappings of being able to control YOU, the parent. (VERY few people could say honestly that they've NEVER tried to pull the wool over their parents eyes.) If kids have a better "grip" on the computer than their parents, than there IS a problem... and it isn't just the kid(s)!
As a parent who's been-there-seen-it-done-that... IF YOU WANT TO LEARN, YOU'LL MAKE THE TIME TO LEARN. NO-EXCUSES. -=AND=- This is one the best examples you can set for you children.
My youngest scored a 98 on their A+ certification, and NOT because I helped... I refused!! --Telling them "your on your own, and to do the best you can." And another of mine not only doesn't care, but actually hates computers and want's nothing to do them, ever. But understands why they needed to learn all these years.
Ramon, my kids and I thank you for saying everything you did in your article. People may not like to "hear it" but I HOPE it gets said, and gets said OFTEN!!
John H.
a.k.a. Tinker
It's like there is a Kingdom of Normalized, Self-Propagating Mediocrity, firmly entrenched, most evident in Computer Skills, but also in Customer Service, Corporate Communications, and Management.
by apotheon
I'll make this short and sweet: If you're a parent, I don't give a hot damn how tired you are when you get home from work. Either you put the time, effort, and care into being a parent that being a good parent needs, or you are to blame for the problems your children have when they grow up to be menaces to society.
Mr. Padilla is right about the children of today learning current technologies when their parents do not, and that this is a relatively new phenomenon. He's wrong about the core problem behind it being a new thing, however. The current state of affairs with regard to poor parenting is not a matter of parents wearing ignorance as a badge of honor (though that is a separate problem all its own), but of parents feeling put upon when someone suggests that perhaps they should take the responsibility necessary to be good parents. Before computers and similar technologies getting away from parents who can't be arsed to actually be parents, the problem was parents who just let the television and game consoles be babysitters but wanted to blame the TV producers and game companies for their children's development into sociopathic monsters. Before that, it was the music industry that parents blamed. Before that, it was communists (who are to blame for a lot, but cannot really be blamed for bad parenting by fascists). Et cetera.
Children grow up screwed up because of their parents, not because of private industry. When you don't take a direct interest in what your children are doing, reliably demonstrate the good values and integrity you want them to have, or bother to learn about their areas of interest, you have only yourself to blame when what they do is drugs, the values they learn involve being abusive and lazy, and entertain themselves with glorified violence and depravity. Don't blame society for your failure as a parent.
. . . and don't blame Ramon Padilla for pointing out that some of you are wearing ignorance as a badge of pride, playing the "I'm tired!" card as a cop-out, and dismissing his arguments based on a wild-assed assumption that he doesn't have kids.
by grellissa
I'll have to agree with apotheon here. Parents are
responsible for raising their kids "right". They are the ones
responsible for instilling personal responsibility and some degree of
morals and manners in their children. They can't fob it off on the
schools or society in general, and then complain (if they do at all!) when their kids turn out to be sociopaths. Parenting is a full-time job for 18 or more years!
My great-grandfathers came of age in the time of horse-and-buggies. I
wouldn't be surprised if they had some problems adapting to those
newfangled horseless carriages. My grandfathers came of age with early
cars on the road, and probably had an easier time of it than their
fathers. My father rode home from the hospital in a car. Sure, growing
up with technology will mean it's easier for kids to use it than their
parents -- unlike the old folks, they're not going to be as scared and
intimidated by newer technology (nor, as blind to its usefulness). Yes,
parents need to put in a little effort to learn about new things, and not proudly
wear their badge of ignorance, while their children pick up new things
as a matter of course. And don't forget, 20 or 30 years from now there
will be some new technology (say, Star Trek style transporters) that leave tomorrow's parents (today's children) cold, while their kids naturally make use of it.
If today's children are on-line, their parents need to have some idea
of what they're getting into and how to protect them. However, it has
to be done on the basis of mutual trust and respect. Going behind their
kids' backs to snoop on their online activities is only going to prompt
the kids to try to evade such monitoring. Parents and children having a
good, open relationship where they can honestly talk about the do's and
do-not's of being online is the key to success.
by eacote55
I'd like all in this discussion to also remember that Technology builds on its base and that base is expanding exponentially now and there is so much to contend with.
I perceive a change in the workplace from my start in 1973 to now. Every company is using computers to determine maximum efficiency and forcing workers to devote all energies to the company. There is far fewer energies left by the end of the work day (and those in IT can rarely ever say when the end is). It IS harder to parent today, not making an excuse, but being reasonable, and it's only going to get harder.
I was fortunate enough to be able to spend some time this week
with Nance Guilmartin. She is an
Emmy-award winning broadcaster, author, speaker, corporate consultant, and
executive coach. Nance has a way of challenging you to become better even when
you think you are doing well in the area of communications.
I have always believed that when it came to supervision, I do
a pretty good job of making myself clear and listening to my subordinates. I
have always tried to make them feel "safe" enough to tell me anything
and let them know that my door is always open.
However, in a group discussion led by Nance, she pointed out
that no matter how "safe" we attempt to make things, our subordinates
may self-censor themselves for a variety of reasons. It could be cultural,
emotional, environmental, or some other reason, but people often manage to muffle
themselves when it comes to communicating with their managers.
The discussion then turned to workload. We often use the
expression of how much work we have "on our plate," because it is so easy
to visualize. Nance then introduced us to a concept she called a "plate
check."
A plate check is simply the process of formally reviewing what
is on your employees' "plates" and deciding if it is full, if there
is room for anything else, or if some things actually need to come off. She
then pointed out that, as a supervisor, it is our responsibility to
periodically conduct a plate check with our employees.
I wondered a moment about this, because as I mentioned above,
I have always believed that I have created a working environment in which a
subordinate had the freedom to let me know when their plate was full. In fact,
as I have moved up the corporate ladder--so to speak--and find that I have less
and less time to be hands-on with my employees, I have found myself telling
them, "It is your responsibility to tell me when your plate is full, and I
will keep piling on until you tell me to stop."
Believing that I have created a safe enough environment for
them to tell me to stop, I have assumed that they would do so. However, as our
group of senior managers sat around the room, Nance asked us to think about our
own plates. She asked if we all thought our plates were overloaded. There was a
lot of laughing and zealous agreement that indeed our plates were too full. Then
she asked if any of us had gone to our bosses (who happened to be sitting in
the room) and asked to talk about our workload. Silence. Me included. Why? For
many in the room, it probably was because none of us like to admit that we can?t do something. My colleagues are a
well-educated, driven bunch of individuals. They got to where they are today by
being the "can-do" type, and they--much like me--are overachievers. So
saying that your plate is full is not something that comes easy--at least not for
me. There may be more individual reasons mixed in as to why we had not gone to
the trouble of saying, "My plate is too full, and I cannot handle another
thing," but whatever the reasons, we haven?t done so.
Our bosses believe that they have created the same safe
environment that I have with my employees, so why hadn?t I come forward rather
than trying to do it all? This insight obviously made me question my belief
that my own subordinates would tell me when enough is enough.
I will now make it a point to regularly review my employees'
plates and have some thoughtful discussions as to what is on them. (Don?t read this as an indication that I am
not keeping track of their tasks--I do. However, if employees are managing
their time--prioritizing and meeting deadlines--and not complaining, I have
been assuming that I could add more.) I am not relieving them of their
responsibility to judge what they have on their plates, nor am I saying that
they will not have a full load at all times. But I am going to be cognizant of
how high things are piled on.
What are the consequences of not doing a plate check? Burnout.
You can take that high achiever (in fact, it is probably your star employee)
and turn them into a crispy critter over time--resulting in them leaving or
becoming less productive.
Lastly, don?t confuse this with time management or
prioritization. While it has a component of both in it, it?s more about
communication than about whether anyone knows how to manage their time or how
to prioritize. Thanks Nance, for once again pointing something out that I was
taking for granted and making me a better supervisor. Hopefully, this blog
might motivate a few others to reexamine their methods who, like me, thought we
had it down pat.
by ramesh
Hi, I really enjoyed reading the article. It is some kind of introspection which we all need to do quite regularly.
by paulaaa19
by bgoliver
Very good article. The plate check is very useful for sharing the load and/or budgeting for future resources to meet deadlines.
by careus
Great article. I think everyone can relate to the burnout comment.
Also, it seems like one should be consistent in the way they perform a plate check for their employees. If the process is formal then it should be formal for all employees. If the process is a periodic checkup done informally then it should be informal for all employees. Leaning toward the side of consistency rather than adapting to individual needs will keep everyone on the same page, hopefully. In my experience, trying to adapt to how the employee prefers to be approached tends to lead toward problems later if the culture is not an open one.
by chip
Good job. Transparency and trust go a long way to improving everyone's lives. Save's money too!
Bubba
by justin james
If one properly obeys the "four email rule" then one keeps the garbage off the plate.
There is nothing wrong with a full or even an overflowing plate. A big meal is not bad for you. It is when the meal is filled with my boss' bowel movements that I have a problem with it.
The problem is not how much people put on my plate, but the quality of the work. We have someone here who likes to have me work on projects that we are not billing for, but not tell me that we are not billing for them. He acts like they are important "make or break" projects. After shoving everything to the side and putting in the extra hours, I find out that it is not a billable project. What a waste!
So I have implmented the "four email rule." If it is not important enough for you to follow up at least 4 times on the status (I refuse to answer the first 3 emails), or simply come to my desk and ask about it, why should it be important to me? Too many people get used to causing 10 hours of work with an email that they wrote in 10 seconds. They conflate the amount of output with the difficulty of generating that output. As such, I choose to ignore them unless it is important enough for them to actually follow up on it. If it is so unimportant that they forget they made the request, why waste my time on it?
And so my plate is filled with nothing but wholesome, nutritious items that are good for me, my sanity, my company, and my career.
J.Ja
by exterminated
by exterminated
I
I just finished completing the 3rd National
Incident Management System (NIMS) compliance course required of me by my
organization, and it got me to thinking about planning in general. There are a
lot of planning processes for which we are responsible or participate in:
Disaster Recovery, Continuity of Operations, Accountability Frameworks,
Standard Operating Procedures, and NIMS to name a few.
There are templates and software, courseware and consulting
for all of this planning that is supposed to allow us to be ?ready? or to be
able to justify and measure our work product. We are repeatedly told how important
it is to ?have a plan.?
Yet, no matter how important it is, how much time is given
to you and your staff for planning purposes? I believe it is in this area that
?lip service? plays a significant role in many organizations.
The trend over the years has been to trim ?excess? employees
in the name of being lean and mean. After all, look at how ?productive? we as a
nation have become. How ?profitable? our companies are, and how ?cheaply? we
can run our government (?Look Ma! No employees! Wait, don?t dig to deep to find
that army of consultants that has replaced our ?cheaper? employees--it?s the
number on the payroll the voters look at).
We have created a situation in which a ton of planning
occurs (and no real work gets done) or employees are scrambling to get the real
work done and planning is haphazard at best. We have ?trimmed? away our
capacity for planning in the process of removing our fat.
Real preparedness is more than sitting down, creating required
document/s and filing them away-- confident in the fact that if an ?event?
happens, we will just whip out those documents and everything will be hunky
dory. Real preparedness means bringing those documents to life, testing them
frequently, updating them regularly, and living your SOP.
Our emergency responders tend to be the experts in these
areas because they live their plans out of necessity on a regular, if not day-to-day
basis. Dealing with full-fledged incidents/crises is usually not part of our
daily IT activities.
Having said all that, the plans we do come up with are worth
more than the paper they are written on, and their worth goes up with the
practice and commitment that is applied to them. Even if they are stale and in
a drawer somewhere, they are a starting point from which to begin your
response. Yes I realize that a stale plan
can cause more harm than good depending on the situation ? but it is hard to
argue that having no plan is better than not having one at all.
That is why I like the idea of NIMS. NIMS gives us a
framework to respond to an incident/event of any size, whether it is planned or
unplanned, and which can scale from a single organization to a national
response. There has been a great deal of thought that has gone into NIMS and
while none of it is IT-specific, if you go through the training, you will
repeatedly find yourself thinking about your COOPs and disaster recovery plans
and ways to improve them. In fact, it is highly recommended that organizations
update their COOPS in order to reflect NIMS concepts. If you are a Federal
Agency, you are already required to do so.
So what is NIMS exactly, other than what I have described,
and where do you find out more?
NIMS is the National Incident Management System. It was
created per President Bush?s Homeland Security Presidential Directive ? 5 which
instructed the Secretary of Homeland Security to develop and administer a
National Incident Management System.
Why is NIMS important to you as an IT professional? NIMS
provides a set of standardized organizational structures, as well as
requirements for processes, procedures and systems for interoperability as well
as a management system known as the Incident Command System (ICS). It is during
the learning of the ICS that I believe you will have many of those moments in
which you will think of ways to tweak your IT disaster response plans.
You can find out everything you wanted to know about NIMS
here:
http://www.nimsonline.com
or here: http://www.training.fema.gov/emiweb/is/is700.asp
and get online training here: http://training.fema.gov/emiweb/IS/crslist.asp
I suggest the following courses to IT professionals:
IS-1
Emergency Manager: An Orientation to the Position
IS-100
Introduction to Incident Command System, I-100
IS-200
ICS for Single Resources and Initial Action Incidents
IS-700
National Incident Management System (NIMS), An Introduction
It will take approximately 2-3 hours of your time for each,
but I think you will find the courses well worth the effort.
by chip
Great topic! I agree that planning in general is not going to get "budgeted" adequately. Plans apply business goals to assumptions (predictions) about what conditions will be in the future to develop a strategy before the condition is staring you in the face. Plans for changing conditions may (will likely) require investments today to meet those future conditions. The budgetary challenge is striking the right (optimal) balance between investing resources to meet today's conditions vs. preparing for tomorrow's. I believe this is fundamentally a leadership challenge. The balance that the New Orleans Levee boards (and Congress and Corp of Engineers) apparently decided (and they did decide, even if they chose not to decide) was to invest resources somewhere other than in preparing for a category 3 hurricane direct hit on N.O. Did they work out the numbers to gauge the catastrophic loss they were risking by not investing in preparation for a Katrina like storm? Maybe, I don't know. Have most governmental agencies asked the hard questions about what the cost of loss of IT assets (data, processing infrastructure, communications, applications) would be in the event of varying levels of catastrophe and emergency operating conditions? Have we questioned our assumptions about what (who) would still be working and who would come to our rescue in the event of a broader (regional, national) emergency? Think of the level of technical interdependency we have built our current U.S. society into. Who were the heroes after Katrina? It was the people who somehow "made it happen" by creatively putting together assets to bring up communications circuits, shift computing loads, re-direct web sites. Did they follow a script? The "script" didn't work. They jumped in after it failed. Thank God for these kinds of folks. But it shouldn't have had to happen that way. It's a leadership thing, all the way to the top I believe.
by dan.neunaber
by stanton
I just finished a bit of a whirlwind trip, during which I
was chased out of Miami by Ernesto, and thought I would share with you the
potpourri of ideas that came out of some of my recent discussions with
colleagues.
The topic I first wanted to bring to your attention came to
me as I was lifting off from Miami one day ahead of what?at the time?was a
possible category 1 hurricane. I?m sure you are thinking that I am about to
lecture on disaster recovery and preparedness, but I?m not. Well, maybe in a
sideways kind of way. I want to talk to you about insurance. LOL?that sounds
like I want to sell you some, but in
fact, many government entities are "self insured."
If those words don?t give you the heebee jeebies, they
should. Have you added up the cost of equipment in your data center lately? If
you haven?t, you should. More importantly, have you gone through the exercise
of determining what it would cost you to replace everything in your data center
at today?s prices? That is another exercise that you should perform. Then take
both of those numbers to your CFO, or Risk Manager, and ask if they are
prepared to fork out those kinds of dollars, in addition to consulting services,
to get your organization back up and running. Remind them that at the same time
you will be asking for these funds, every other department in your government
organization is most likely going to be asking for money at the same time.
And if you think FEMA is going to bail you out of the above
predicament, you better think again. Getting money FAST and FEMA usually don?t
go together in the same sentence.
I bring this up because there are local and even state
governments out there whose cash reserves, often known as ?rainy day? funds, are
woefully under funded. Thus, they would not be prepared to handle your whopping
bill up front. This leads me to suggest creating a leasing agreement with a large
vendor such as HP, IBM, or GE Capital that would provide the hardware and help
to re-create a data center in the event of a catastrophe. Anyway, it's something
for you to think about as part of your disaster planning.
On a different topic, let?s talk about CALEA. Oh you know,
the Communications Assistance for Law Enforcement Act ? everyone?s favorite
subject. I say this partly with tongue in cheek, because I think that some
local and state governments wrongly believe that they are not required to
comply with the recent FCC rulings regarding CALEA compliance. However, there
are a growing number of state and local governments who are dipping their toes
into the provision of Internet access to the general public, either through
wireless, broadband, dial up, or providing use through shared facilities.
If your organization falls in this category, you are more
than likely going to have to be CALEA compliant, particularly if you are
providing unauthenticated access to the Internet.
Now what does it mean to be CALEA compliant? Well, by the
FCC?s definition, that is clear as mud. The FCC has not clearly stated what it
means to be compliant ? they just set a date by which you have to BE compliant.
Don?t you just love it?
Many of the CIO?s that I know are sitting down with their
legal counsel now, looking at the FCC?s rulings on CALEA, and attempting to
decide if they probably will need to comply or probably won?t. If they decide
that they probably will?they are letting their CFO and administration know that
they are probably going to need a hundred thousand dollars or so to become
compliant. That way, no one gets blind sided come compliance time, which by the
way, is MAY 14, 2007.
Changing subjects again, I can?t seem to get the disaster
that happened at Bluegrass Field in Kentucky out of my mind. Having flown out
of there on COMAIR flights myself on occasion I feel lucky not to have been on
that particular flight and my prayers go out to the families of those who lost
loved ones in the crash. However, doesn?t this whole scenario sound like it
could have been prevented if the right technological solution had been in
place? You would think that with all the position finding equipment that is
available these days, that there would be a way to ensure that these types of human
errors could be avoided. Given that the FAA is strapped for controllers, one
would turn to technology as a way of making up for the shortfall in people,
don?t you think?
Lastly, I heard on the radio this morning that AT&T had
their online store hacked and people who purchased DSL equipment had their
customer information stolen, including credit card information. If this proves
to be true, I can only shake my head and mutter, ?encryption, encryption, and
encryption.?
I have been on vacation this week and found myself waxing
philosophic about how computing has evolved in our organizations over the years
and where computing is headed over the next five to ten years. I can?t remember
exactly when he said it, but John Gage?s statement, ?The Network IS the
Computer,? becomes more and more of a reality each day.
If you are old enough to remember the days before the PC,
you might recall a computing environment that was central to a particular
machine. Depending on the size of your organization, all of your computing
applications ran on this single machine or a few more like it. It was very
powerful, centrally controlled, and?except for what some people would now deem
primitive word processing and calendaring?was focused on running core business
applications. Management of this type of system was pretty straightforward and
generally highly regimented.
When the PC revolution came along, it was responding to a
computing environment that had little time for the needs of the rest of the
organization or couldn?t keep up with the demands of the core areas; people
found that they had a device on which they could do many of the things they had
always needed to do?they just had to get the data from the mainframe and
manipulate it. History has shown that this was, in fact, very empowering for
most organizations, but central IT was not quick to embrace the concept.
Soon afterwards, you had the advent of PC networking and
client-server computing, and it wasn?t too long before many organizations had
competing computing infrastructures within their organizations: one mainframe-centric,
the other, client-server. The problem with client server was it was ?messy.? It
tended to sprout up all over the organization, rather than being guided by a
central strategy; after all, it was part of the ?personal? computer revolution?and
it suffered to some degree because of the way it was created and implemented,
rather than being centrally planned.
Then came the era of control.
Many organizations looked around and realized what a mess they had created.
Mind you, it was a productive mess, but not as productive as it could have
been. Magazines featured many articles and advertisements for products and
methods of getting one's computing environment ?under control.? This went on
for some time and then the Internet burst on to the scene.
When the Internet started to become more mainstream in the
late 80?s, computing seemed to explode in organizations, and these messy networks
got bigger and bigger?and more importantly?complex. The Internet brought many
benefits but added security headaches. The difficulty of managing a network
increased due to viruses, worms, malware, bots, Trojans, and more.
The Internet phenomenon grew in the 90?s and the world didn't
end in 2000, thanks to the hard work
of IT professionals who did not panic under the pressure of tremendous hype.
At about this time, the browser-based application started to really hit the
forefront. Forget the fat client; let?s have all of development be
browser-centric. And, for the most part, it has been a good thing. It is clear
that as the tools mature, we seem to be headed inexorably to a future in which
the majority of applications will be Web-based (see the success of eBAY, PayPal,
Google, and Salesforce.com, as examples) and connectivity is almost ubiquitous.
Now, with the potential for grid computing, which is defined
as ?a collection of low cost network, storage, computing and
software elements, lashed together to do work that historically required very
expensive dedicated proprietary technologies,? we have an interesting
situation: IT?s desire to reconsolidate in order to get things back under control by moving things back to a
centralized structure where applications are delivered rather
than run on the machines they are presented on ? brings us right back where
we started.
Depending on the maturity of organizations, I see a movement
that will pick up speed over the next few years in which companies will want to
further eliminate the complexities of their IT environment by having all their
applications, including the desktop, be delivered by an applications service
provider, or by going completely thin client and becoming an ASP themselves, or
a combination of both. Other than for gaming (and I?m not so sure that the same
thing won't happen there), people may one day wonder exactly what a PC was for in
the first place.
by dawgit
by rosa1mundi
by bhunsinger
Magic words "monthly fee" In those days you are talking about, few businesses could dream about computers. Only the largest organizations had mainframes and the cost was very high, because IBM only leased machnes.
Most people buy their cars, even though there is a market for leasing.Same with furniture and appliances. Same will happen here. Everytime some large institution gets hacked. the case is made for owning and controlling your data. In places where the ben counter run things, partly I believe because they think that accelerated depreciation tabels are an accurate barometer of how long things really last, managed services will bloom. I don't see it taking over the industry. It will be hard for some of the to get off that bandwagon , of course. Anybody else know people that keep rolling over their excess milage on their leased cars? I know one guy who needs to park his new vehicle for a year to cath up!
by infinitymoo
by rich_soby
On some levels I agree, however, look at what made the PC a success - it worked on my priorities, not IT's. We will consolidate because of the increasing technology knowledge needed - Firewalls, security protocols, updates, colaboration, portals and on and on. But IT will respond as always - with their priorities first. When budgets are then cut, IT will fund itself first and as the customer support wains - the user will once again strike out on their own....and the cycle will start all over again swinging from personal to integrated corporate to personal.....ah the thing that keeps us consultants busy
by olarande
by old aussie
The comments about cycles in IT are spot on. The resemblance of the browser to the old 'green screen' is obvious, except that we typically ran 20 - 30 active users on a 19.2KBits/sec comms line with sub-second response times thanks to the distributed computing architecture of the 3270 display (launched in 1969 I think). Then along comes AJAX and the whole cycle starts around again.
by sonicbridge
The one cycle that stands out in my mind is this: our well schooled (experienced) engineers are forever striving for innovation. Their creative efforts only see daylight when the venture capitalist discovers how to profit from their processes. The end user, being the recipient of such advanced technology, in the end, is still only the consumer who pays the price of admission to this phenomenal world of computing.
by tazroth
Lately, I have been thinking about a couple of management
practices that seem (based on my experience of more than 18 years in
government) to occur more frequently in government settings and to have
significant detrimental effects on employees and the organization. The first
one is keeping underperforming employees around when they should be let go, and
the second one is promoting a good employee into management just because they
"deserve" it, whether or not they actually have adequate management
skills.
The first practice falls under the category of coddling an
employee who can?t quite cut it. Unable to let someone go, a manager keeps problem
employees around by propping them up with support systems and other people.
Why is this so bad and how do you avoid it? Here's the
situation: You hire a person to perform a function because you as a manager in
the organization have a need that must be met. Provided that you give the
person clear directions regarding the work to be performed, give them the right
tools and the power to perform the task--you should have every expectation that this person will accomplish
tasks in a timely fashion and with a level of quality that is satisfactory. If
the person cannot perform the tasks adequately and you have met your own
responsibilities toward them, should you not let them go?
If your answer is NO you are: (A) cheating yourself out of a
valuable position (few of us have ?extra? positions that we can spare these
days), (B) creating animosity amongst co-workers who are quick to notice if
someone is not pulling their load, (C) overburdening someone (you or someone
else) who has to take up the slack for this person, (D) leaving important work undone,
(E) cheating the person who is not performing by allowing them to think they
are adequate, and (F) leaving a mess for your successor to have to deal with
once you are gone.
All of these results are clearly bad things for a manager or
supervisor to deal with, yet the practice seems quite commonplace. Why? There
are probably a number of reasons--some political, some not. But I believe the
main reason is that no one likes being the bad guy or girl, and there is a
whole stigma regarding firing (oh my gosh--I said the F word!).
First and foremost, terminating an employee is unpleasant
for most supervisors. I?m not talking about layoffs--which are also unpleasant--but
specifically about firing someone due to poor performance, which seems more
personal. Obviously, it is hard on the employee--no one likes being let go;
however, it is quite burdensome on managers as well. Often they internalize the
whole process and blame themselves for the employee, or are guilt ridden because
the person has to support himself or has a family to feed, etc. Also, many
supervisors are conflict averse, and would rather let things fester than have
to deal with it.
All of the factors above and the notion, in many
organizations, that firing is always a BAD thing and should be avoided at all
costs result in a culture where poor performance is the norm and a select few
carry the entire load for a section or department.
Now that we know why this is a bad practice, let?s talk
about how to avoid doing it in the first place. First and foremost you have to
dismiss the idea that firing an employee is a bad thing. In fact, it is your obligation
as a manager to make sure that people who do not perform are let go; otherwise,
you are doing a huge disservice to yourself, the employee, their coworkers, and
the organization. As long as you have done your part in helping that employee
to be successful in the job, there should be no shame, guilt, or stigma in
doing your job.
Now, before you start saying "but?" let me add a
few things. THE ideal time to be scrutinizing an employee?s work is during
their probationary period. In most organizations, the rules for dismissal are
far more relaxed than at any other time in the employee?s career within your
organization. You need to make extra darn sure that YOU DO NOT keep them past
their probation if there is any indication that they are struggling or
marginal. I do not care how long it took you to fill the position in the first
place or whether you may lose the slot or not--you should not keep someone on
that is not cutting it during probation. Most organizations have ways of
extending the probation period should you need to do so.
Once they are past their probationary period, as you know,
things are tougher. You need to be VERY proactive and you need to document your
rear end off. For all of you out there saying that it is impossible to let
someone go once they are entrenched in government, I say baloney! It just means
you have to work much harder to get to the point of dismissal and to make it
stick. But let me tell you from first hand experience ? it is worth all the time and
effort that you have to put into it.
This is a huge subject and I could write for days about it,
but I refer you back to my blog on performance
evaluations for additional information. It is not a fun subject, but having
your employees meet their responsibilities is one of the most important things
you are obligated to do as a supervisor.
The second topic that I mentioned at the start of this piece
is the bad practice of promoting or reclassifying a person into a managerial
position in order to get them a raise. Just because a person is doing well at
their job does not necessarily make them good manager material. In fact, I have
seen this happen not because a person is considered particularly good, but
because they happen to have been around a long time. Oh I cringe even typing
that. This practice is the worst of all.
People should be promoted to a supervisor based on their
ability to perform well in a management capacity ? not just because they can do
their current task well or have seniority. Having the most seniority doesn?t
necessarily make anyone ready for management; it just means they have been
around a long time--period. In fact, they could be one of the people being
propped up by others who end up being most senior. Now isn?t that a double
whammy?
You must take great care in promotions/reclassifications
into supervisory positions. After all, these employees will be setting the tone
for their subordinates. You can quickly fill your organization with less than
stellar management, which in turn affects everything.
This is particularly important in a support service such as
IT, where poor performance and bad management can have a dramatic effect on the
rest of the organization.
So, if you are ever tempted to do either of the above--for
whatever reasons--please don?t do it. Someone will pay for it, whether it is
now or later. And if you are currently in the position of having to clean up
someone else?s mess, I channel all my strength and good will to you--you?ll
need it. But what you are doing is so very important and worth it in the long
run. Don?t give up hope and know that it is possible to succeed in the end.
by juan_llorens
by dimbulb
Good article. I wish my local managers had read this years ago before they promoted the guy that should have been fired- he's now my boss. I can only hope for retirement-his or mine.
by chip
Wise words Ramon, as usual! A few additional observations. A clear focus on the primary purpose of the organization and how success in achieving that purpose is measured will help keep everyone's individual performance in the right business context. Also, the impact of the character and work ethics of leadership in the organization can't be underestimated. It sets the tone for what performance and behavior is expected and acceptable. It also can inspire and motivate average performers to stretch to new levels of performance.
by oneoldman
On the second topic, hindsight is easy.
Being a civilian technician with military leadership experience, how do I, or anyone else, display our leadership ability to our managers to be considered for a supervisory position without being promoted to that position in the first place?
by zaferus
Great article, and I recall in a previous position how someone who wasn't there the longest but was VERY adept at his job got promoted to our department head because management knew he was the best performer we had.
Unfortunately the person got flustered easily and it was no secret he didn't have the best temper or people skills. As a programmer he was the king, but as a manager he would come storming out of his office at least three times a day (on a good day) waving his arms and loudly complaining about the latest thing he was upset about. He would openly fly off the handle in front of everyone when talking with us subordinates or yell at other department managers.
The senior manager who promoted him wouldn?t admit ever making a mistake, and to this day I believe he?s still there ? but none of us who worked under him when he was promoted are. And most of us swore we?d never work for the government again when we left (although many people also just transferred to other departments).
by timcornia
how do I, or anyone else, display our leadership ability to our managers to be considered for a supervisory position without being promoted to that position in the first place?
Good question. I have a few opinions on this. This is written with a perspective on IT shops.
One, there are formal leaders and informal leaders. Most who has worked in a group setting realizes this. Trust me on this, good managers know who the informal leaders are and those leaders are broken into two groups, the ones that are supporting managment and getting things done, and the ones who are stirring the pot. Be the one who is percieved as supporting management AND who can get others to support management.
Two, are you an employee who is percieved as being able to interface with the business-side of the house without coming across as a propeller head and who understands the business? In management, you will be spending as much time (or more) interfacing with business people, people who understand their business but not the technology to get them there. Can you adress their needs? Can you make them feel like you can get them there? Do they feel like they are interfacing on equal gruond with a collegue or are you talking down to them because you are smarter than them when it comes to technology?
Three, do you have the respect of your peers? It does not mean that they like you or that they want to go to lunch with you (although that is not a bad thing). Do they respect your work, see you as a dedicated employee who works hard, and feel that you are someone who can be trusted. If you have this respect, it can go a long way in determining how successful you can be as a supervisor should you be given the opportunity
All of us have areas we need to work on but if we have those three bases covered, I think the potential for supervisory responsibility coming our way is high.
by jeffykins
by eatdust
Good article. A lot of "wrong people" get promoted into top positions. Then realise they cannot cut it. Then start making other staff look bad and themselves look "GOOD" by creating wrong perception about those staff members to others so as to create a "SMOKE SCREEN" to top management.
by wayne m.
It looks like I have the minority opinion here, but I believe it is a management responsibility to provide for staff development and that managers need a far wider range of personnel skills beyond ignore or fire.
First, the article uses several terms synonomously that I feel are quite different. "underperforming employees" are not the same as "problem employees" who are not the same as employees who "cannot perform the tasks adequately." "Underperforming" is a relative term. In any group of people, ordered by some capability, half will always be in the bottom half. With the rate of change of technology in IT, everyone should expect to fall in the bottom half, the "underperformers", several times in a career.
"Problem employees" are usually identified by their social interactions and not their technical skills, so I do not see how having staff in the bottom half of a skill ranking implies having problem employees.
Employees who cannot perform the tasks adequately is actually a small subset of the employees who do not perform the tasks adequately. I feel that it is quite rare to come across employees who are incapable of performing a task. In these situations, it is by far more preferrable to transfer the employee rather than terminate. Showing loyalty to employees misplaced by management builds corporate spirit while firing these employees is a sure way to curtail initiative and risk taking.
Dealing with employees who do not perform tasks well is where true management skills come into play. There are a myriad of reasons and one needs to analyze the situation and address the underlyig issue. The easiest approach is for the management to deny responsibility and either ignore or fire the employee. This is a very plug and chug style of management to blindly replace parts hoping the next one will be better than the last one. Replacing a burned out fuse is no way to resolve an electrical problem and replacing a burned out employee is no way to resolving a management problem.
I'll omit discussion of promotion into management, as this response is already long enough, but the principles above apply equally as well.
Firing an employee is almost always a management failing. I am concerned that I see far too many articles extoling the value of firing staff and far too few discussing staff development and leading staff to succeed.
by shkfaizalam
by jamesrl
Lots of good comments, thought I'd try to answer Tom's question - how do I show leadership when I'm not management.
One simple road is project management. If you can manage tasks in a project, you can manage tasks in a department.
Another aspect is, how much do you contribute to your department/team more than what is laid out in your job description. In many departments, my management, knowing my wide and varied background, would seek me out and bounce ideas off of me on other issues in the department than ones I was involved in. I would not take the "not my job" tack, and I would try to help. Similarly when issues in other projects were brought up in staff meetings, I would work with the project leads or managers to try to help resolve them. I didn't do it for credit or "glory", I did it to helop the department. That in turn lead to my team trying to get me promoted. You have to be careful about it - some people will inevitably think you are a suck up, know it all or busy body. And you have to carefully chose a tone in your communications to avoid that.
Another is simply to know what the departments goals are and keep trying to help the team and your manager achieve them. Think about your grousp objectives when trying to prioritise projects or effort. Initiate projects that help meet the larger goals.
Thats just a start.
James
by bnetreader
There are lot of observations in the article and in the comments that I agree with on this topic. You should also look up information on "forced ranking". There are many business management articles (HBR) and HR information that shed light on what companies are trying to achieve. However if you don't have the managers with the skill set or aptitude to perform evaluations compentently there is not much hope in any evaluation process. The worst thing a company can ever do is coddle poorly performing managers. They can stunt teams and products and effect the entire organization. A number of high tech companies I think are in the process of finding this out the hard way. The almost unanimous conclusions (by management and HR studies) seems to be that "Firing an employee is almost always a management failing".
by jengar
I was at a conference recently where the speaker quoted
someone (unfortunately, I can?t remember who) who said that ?the best run
organizations are those which have mastered the mundane.?
That is a pretty profound statement because, if taken literally,
it means that the organization has perfected its day-to-day activities to such
a degree that it is free to focus on being agile and responsive to the forces
that affect it in a proactive way.
The path to this mastery is partially through efficient and
effective standard operating procedures (SOP). SOPs are defined as ?detailed,
written instructions to achieve uniformity of the performance of a specific
function." In other words, procedures that make sure that inputs to a
process result in the same outputs in terms of quality, quantity, consistency,
etc.
SOPs by design, should be based on the best way of doing
things in your organization, often reflecting the best practices of the
industry. Thus, we have a tie-in to methodologies such as COBIT, ITIL, and ISO.
So in general, SOPs are a good thing. However, it never
ceases to amaze me how organizations can take a desire to implement best
practices and SOPs and completely miss the boat on what they are doing and why
they are doing it.
The purpose of SOPs is to make your organization perform
better and faster, with higher quality, increased customer service, and
accountability. The SOPs ARE NOT the end product, nor are they designed to be
so rigid as to make conducting business painful. You know where I am coming
from here. I'm talking about the kind of "procedures" that are so
cumbersome and time consuming that they make you want to pull your hair out
(what?s left of it); that make work for people whose only reason to exist in
the organization is to enforce the "procedures;" that were designed so
long ago they haven't kept up with the changing organization, or for IT,
changes in technology.
I have witnessed the logistical operations of UPS and Fed Ex,
and I can tell you that these organizations have truly mastered the mundane. Their
cargo handling capability is literally a science and they have achieved mastery
not just by creating SOPs and sticking to them, but by constantly re-examining
their processes to make them more efficient, effective, and consistent. Because
of this mastery of the mundane, they have had the opportunity to come up with
creative ways to expand their respective businesses?ways that would not be
possible if they were still operating on the same set of SOPs they first
developed when they started handling packages.
Looking strictly at IT, it is important to remember that
your organization is unique and that plopping in a best practice without
considering the individual quirks of your environment is usually a bad idea. You
need to take the procedures, methodologies, and best practices that have been
hammered out by others and refine them for your own uses. You need to tailor
them for your environment ? not adhere to them as if they were gospel.
That is why I like ITIL (IT Infrastructure Library) so
much. ITIL teaches you about good practices in IT, but it is not prescriptive
in how you get there. The work in ITIL is translating the outcomes from the
Library into a methodology for your organization that will achieve the results
you are looking for.
In summary, IT, as a service-based organization needs to
master the mundane in order to have the flexibility to work with its business
units and add value. Mastering the mundane is accomplished by implementing
procedures that insure a quality output on a consistent basis. Flexibility and
agility is gained by constantly examining your procedures to insure that your
operations are purring like a kitten. IT organizations can get a head start on
those procedures that help guarantee success by adopting structures and
methodologies such as ITIL and COBIT.
But smart organizations know that they need to examine these methodologies in
order to make them fit within their environment and realities of their
organization. Pretending to do otherwise will lead you down the wrong path and
make you one of those organizations with disjointed, out-of-touch SOPs that
make it harder, not easier to do business.
Great article Ramon! I agree 100% with what you expose. In order to implement a best practice framework such as ITIL, COBIT and PMBOK, you have to describe how the principles and practices
will be applied in your organization,
by your specific roles and using your systems. You have to translate those
principles into executable processes.
I have written a set of articles about how this can be carried out, that you can find here:
Create your methodology based on a standard framework
Lucas Rodriguez Cervera
Nevant
by jamet123
Nice article. I think that this can be applied to the business also and that requires an approach to automating the mundane, perhaps using something like business rules.
JT
I read a blurb in my local paper this weekend that stated
that 70 percent of all baby boomers plan to work past retirement age. Whoa!
That?s a load off of our collective minds, right? I can breathe much easier now
knowing that the impending brain-drain is no longer a reality?let those geezers
work until they're 100!
Now that I can take my tongue out of my cheek, let's look at
the reality of the situation: Planning to work past the age of 65 and having the
ability to do so are two entirely different things. Even with the incredible
advances in medicine that we have been seeing over the years, most men, on the
average, pass to the great beyond at or about age 76 and women at 82. Now
before you get too excited and say, ?There you go, 11 more years of
productivity,? let me remind you that the years between 65 and 76 are years of
physical and mental decline and while the mind might be willing, the body may
refuse to cooperate.
So don?t bank on having all these senior people around
forever in your organization, and start some real knowledge retention management
before a crisis does occur. Is this issue not even on your organization?s radar
screen? It?s probably right up there with pandemic flu planning, as in, ?let?s
stick our heads in the sand and pretend the issue isn't there.? My friends,
both issues are real and require some planning. But let?s talk about knowledge
retention now, and some of the things we can be doing about it.
First, there are different kinds of knowledge to be
concerned about losing. Some organizational knowledge is easily quantifiable and
can be documented; some knowledge is harder to capture and transmit?we'll call
it "institutional knowledge." The area where quantifiable and
institutional knowledge meet is, perhaps, the most valuable kind of knowledge.
For the sake of this discussion, let's call it "wisdom."
The most progressive organizations are putting together mentoring
plans, redefining works hours and positions to allow people more job
flexibility, are conducting oral history projects, and more. These projects are
often driven by human resources. But what about IT? What can we do to sustain
the knowledge built up in our departments?
We have what I consider to be some of the best tools for
knowledge retention management at our fingertips. And the best part is?it's in
disguise. I?m going to let you in on this secret: these tools are business
process mapping, the implementation of IT frameworks, systems re-engineering,
and audits.
Floored? Of course not. You knew it all along. One of the
main reasons that the retirement of the baby boom generation is an issue is
that on the whole, most organizations are
lousy documenters! Now those of you dealing with Sarbanes-Oxley are
probably getting much better at it ;-)?but in general, we have a lot of
seasoned employees walking around with a great deal of knowledge in their
heads.
What better way to start gathering knowledge than to do all
of the above while the employees with the knowledge are still around?
Business process
mapping: Many organizations do not have a living document that captures
what they do and why they do it.
IT frameworks: Introducing
ITIL or COBIT as a way to formalize our business practices lends them
legitimacy, as well as makes sure that what we are doing is up to snuff.
Systems
re-engineering: How many of you are sitting on legacy applications that are
dependent on one or only a handful of individuals to keep them going? If they
all walked tomorrow, would you have to resign with them? It?s okay to raise
your hand; no one is looking and I won?t tell. The fact of the matter is that
we have far too many of these applications/systems, and the best way to spread
the knowledge is to rebuild them using today?s modern tools and techniques. This
not only inspires and refreshes your now tired and bored legacy staff, but also
excites the newer staff members who will learn from participating in the
re-crafting of important systems/applications.
Audits: Stop
cringing like that! The auditor is your F R I E N D. Because they are usually
considered to be objective, people listen to them. Even if you have been saying
the same thing to your boss for years, he may pay more attention to a
recommendation in the form of an audit finding. This can help you kick-start a
project that you've been lobbying for a long time. Once an auditor brings up a
problem, suddenly people want to ?fix? it, and that is often the start of the
money flow. Additionally, if asked why something needs to be done, you can say,
?The auditors told us to do it,? and that?s usually enough information for
them.
In summary, knowledge retention management is important for
all organizations as the baby boomers begin to near retirement. There are many
ways to retain their wisdom and knowledge, and fortunately, many of those tools
are already in your tool box.
In many ways, you can spin this like Y2K. We know the
general timeframe when the last of the baby boomers will most likely be leaving
the organization, so make your case and plan for it, just like you did for the
end of the world as we knew it. Oh, and while you're at it ? don?t forget about
the pandemic flu!
Message was edited by: The Trivia Geek
by dawgit
by kenm
Yes, those in the Federal government are sticking around - and who can blame them?
They get 26 days Annual Leave plus 13 days Sick Leave (8 weeks of leave), plus any compressed schedule/ telecommuting arrangement they may have and they only have to be at work 40 hours a week. If they work for a private firm, they may get 2 weeks vacation.
A lot are just staying for their next Step Increase - these usually take place every 3 years. Once they get it, they say, why not go for another? (To retire at an even higher pay rate.)
Some realize that they are not as, ahem, "employable" in the outside world. They have no skills or certifications to speak, and, although it is of course "illegal" in this country, may end up the victim of age discrimination if they leave the government nest at an advanced age.
by chip
I recently retired from an IT organization that had retained all manner of documentation for over 30 years, most of it in semi-organized file cabinets or network folders. The amount of documentation on everything from coding changes to report formats to special studies and service contracts was overwhelming since it was not well indexed. One of my last tasks before retiring was to get the hard copy documentation scanned, indexed, and put in a rational organization. Unfortunately retirement hit before I finished. As part of a crop of legacy staff retiring recently I was concerned that all of this information would be lost, if not physically, then due to overwhelming difficulty in being searched. Like most management issues, judgment is required to balance the use of resources between archival documentation and current operations. To the extent that current operations can incorporate efficient documentation into the ongoing work processes this chore will be reduced significantly. Sometimes it is necessary to put a proverbial "stake in the ground" implementing responsible documentation from this date forward and hope that what has been lost prior will not be show-stopping. Another option which I began to think about as I retired is to utilize retirees to organize, index, and convert to electronic format the legacy documentation. Many of these folks would love to have part-time work to supplement their retirement income and who better to put the documentation of the organization in proper order? They could even combine this role with that of organizational history writing in order to give context and perspective to otherwise dry reading. Of course, as for me, I'm busy catching up on honey-do's, organizing my own home-office which is in shambles from years of neglect and trying to become a consultant. But I'm sure there are many out there who would gladly give up their daily 3 hour coffee break swapping lies at the local restaurant to once again feel useful.
by blueknight
Yer darn tootin' we're sticking around longer... and it's not just Federal workers. I work in local government and have no plans to retire -- and it would be the same if I were still in the private sector as well. Part of the problem with many of those before us was/is that they didn't/don't stay active, either physically or mentally and thus the greater decline in physical and mental capabilities. Of course advances in medicine and better lifestyle help a lot. When I was 45-47 I ran circles around the 20 somethings in the police academy and I haven't slowed down yet. I'll be 58 next month and have no plans to retire. Why? Because I am excellent in my field and I love what I do. Besides that, I'm in excellent health and stay physically active. Once it starts costing me to come to work, I'll retire from here and go do something else until I'm ready to slow down. I won't be "kicking the bucket" before 76... fortunately I have some longevity in the family... dad just turned 92 and is doing very well and his older sister was doing great at 94 until breast cancer took her life. Mom and other family elders are doing fine as well. Heredity can be a blessing... or a curse depending on your family as well as what you do with your life. So, not to worry... I'll be around a while so y'all can pick my brain.
Ramon, you're right on about organizations being lousy documenters. They're also lousy, in most cases, about planning for such things as knowledge retention. Let's hope they get it on this one. I'm ready to do my part any time.
Go ahead and call me a geezer or whatever, I don't care... I'll be lapping you soon ;-)
by celtic0123
I would always make my information easily accessible to every one.
I wrote up step, by step descriptions on how to work on each and every program and piece of equipment I touched.
I added pictures, diagrams and 800 help lines.
My boss thought I was an idiot. He told me I was an idiot for doing the extra work.
He used my documentation.
I was told by other workers that if the information in my head, was always put on paper. They could replace me with a monkey that could read.
When I was asked to help someone, I did. Soon I was showing people, detailed portions of their jobs they had no idea how to do.
My issues started when I had asked, begged, argued then complained loudly, for information that was vital to have on hand when working alone.
I was never given that information.
Eventually, they fired me and hired that monkey that could read, but didn?t have a voice.
Age has nothing to do with the ability to do a job.
Age has nothing to do with having a disability
Age has nothing to do with job security.
But fear will stop people from writing down how they do their jobs.
I'm a tech writer and have been in this field, or worked as a newsman for the past 24 years. Documentation is first nature to me. The first thing that corporations do when they get under the gun for budget is cut the documentation staff. It is only the fear of things (think FDA) that causes big corps to resort to foolishness like hiring tech writers to document processes anyway. I am currently working a project that requires documentation in order to maintain system certification. Yippeee! At least I can expect to have a job until the contract runs out. Maybe I will have both my kids in college when that happens.
The biggest problem for tech writers is exactly fear. The people who have the knowledge Subject Matter Experts, or SMEs as we call them, are afraid that once everything they know is in a book, they are no longer in the job equation. While that may be true, it is an unwarranted fear. Documenters can only put in the barebones. We can never put in a book the years of experience a good technician has learned. Case in point: one of our former Web administrators left employ with a company I used to work for. Within days, his website crashed. Despite the documentation, it took the "company" person over a month to bring the site back up. So much for replacements parts. Think NFL replacement players, cause that's more like what you will get.
This discussion is closed to new replies.
Sort by Trending