122 replies
Monday and I have a longstanding disagreement going back some twenty-five years now. Monday wants me to focus, get things done, and pay attention. Personally, I want to continue on with my Sunday routine of pondering my navel, doing chores, and maybe playing around. As a kid this match mostly consisted of me goofing off in class. As an individual contributor, it resulted in many a Monday of not being quite as productive as I possibly could be. Now that I'm a manager, though, the disagreement can lead to others being just as unfocused as I can be.
These days I spend Monday morning reconnecting with my team and attending to scheduling. The reconnecting part, if not easy for an introvert like me, mostly involves following up on conversation threads I started earlier. Scheduling, though, takes a lot out of me. It's not that I don't like to manage time. In fact, it probably says something not entirely good about me that I find it fun. However, scheduling time for a team involves more than just time management. It's a weird intersection between politics, time management, incident assessment, and mentoring that I find a constant effort to juggle. Worse, I have to redo it every week just to keep up.
What, exactly, do I mean by that? Well...it goes something like this.
When I do time management for myself, I focus in on my priorities, the urgency applied to specific tasks by the environment, and whatever communications or political needs seem pressing at the moment. This allows me to build and sustain momentum within a limited context. It also gives me the tools to see projects though to rapid completion.
Scheduling for a team takes a great deal more work though. The basic of time management (priority, urgency, and control over the schedule) become a great deal more problematic. For example, I often have to sacrifice control over the schedule as part of a horse-trade for more resources or to get a particularly noxious function taken out of a project scope. Each time I trade something, though, I lose more and more control over the schedule; yet if I don't perform the trades then the team as a whole gets stuck without the resources they need or trying to pull together projects with impossible scopes.
So, politics and the associated horse-trading take up a huge portion of my scheduling time. Once I get that arranged, I might be able to apply some basic time-boxing to my team's tasks. Or not; just as often we have to deal with a random array of incidents related to our various applications. Whether it makes sense to strap your highly paid, highly skilled technical teams to answering file and print questions isn't really an issue; we have to do it so we try to do it as professionally as possible. Sometimes those incidents also include the elements of patterns we need to pay attention to; teasing those out falls to us leader-types, assuming we get the time between meetings.
Incidents bump project work aside; current problems seem to have higher priority than even the most important future plan. When it looks like we will not hit a date I have to go back into horse-trading, but this time in the opposite direction. I take on new functions or shed resources in an attempt to get more time to account for the failure to build wiggle room into the project plans.
None of that, though, accounts for the biggest variable of them all ? team mentoring. Now, I'm blessed with a team that is more technically astute than I am. They work hard to keep ahead, sharpen their skills, and really enjoy the mixture of creative and effort driven work associated with technical jobs. That's all to the good. However, like most technical teams they do not like to communicate with others. They do not always pay attention to the negotiations and horse-trading, nor do they really care about the constant ebb and flow of office politics. Combine that with an environment which deliberately foreshortens their time horizons (they work in about a 3 month window) and you've got a recipe for constant disaster.
At the end of a good week we've done enough to pull ahead a bit though trading, creativity, and effort. Bad weeks, though, see us fall further and further behind as we surrender control over our time to others in exchange for things we need to, ironically, get work done for them. I'm still debating whether to be amused or confused about that last point.
So, today I wrestled with time. I'll let you know which of us won on Friday.
I started the week with some fine intentions. Get ahead, keep on the plan, and let people have their victories so I could get what I wanted as well. Win/Win isn't just a principle; it's a trading strategy for those of us who wield little influence, power, or authority to get what we need to protect those that we serve.
Unfortunately my plan did not survive first contact with the week. By the end of a very late Tuesday I found myself wrestling with a very different sort of logistical problem. We had a system down, a system we think is fairly important to the business. It was, in all likelihood, going to stay down for some time. Not only did we have technical problems with it, which we did and probably still do to some extent, but it's not well liked at the site where it went down. Given its history there I can hardly blame the site; I've met more stable things gibbering to themselves in the late night corners of really bad conventions.
So, what to do? By the time I found out about the problem we were six hours into troubleshooting it. I could tell it would consume my entire team if I let it. If that happened, though, all of our projects for the next six weeks would fall out of wack. We've got a lot going on. However, it was also obvious to me that we needed both more information and, frankly, more hands. The problem here is, though, that I'm not the leader. I'm a leader, certainly. I'm even, in theory, the technical leader responsible for the line of service overall. But I'm young in the company, unknown to most of the players, and note the previous comment about Win/Win trading strategies.
In a management textbook or one of those fun guides to how to be a better manager I would have known exactly what to do. In reality, though, I did what everyone else does: made a snap decision, somewhat half-baked, and adjusted as I went along. The eventual results remain a complete mystery to me. How much of my minor amounts of influence did I expend? How many enemies did I make? We'll see...
Anyway, I sacrificed planning and trading for listening, suggesting, and watching as events unfolded. I provided resources, such as I had. I argued against descending into activity for the sake of activity, though it strikes me that it was only at the end that I clearly laid out that argument. A team of people, maybe the right people but sometimes not, swirled in and out of the picture. The actual leader stepped out in front to coordinate activity and try to find a real answer. Whether his approach worked or not I cannot say; we did eventually get to the root cause and resolve it though.
Resolving the root cause didn't clear everything up, though. In fact, we didn't trace though the system as well as we should have. When we brought it back up, there were errors in the data caused by the original problems that brought the system down. Now, we don't have a lot of people in house who know a lot about the system. However, I do know enough to question the vendors about tracing things end to end. Why didn't I, then?
By that time, I had decided to fade back and just provide support. One of the hardest lessons I've learned over the years is that it's more dangerous to split leadership than it is to follow a leader into a place you are not entirely sure is right. I might have been able to use charisma and force of will to pull part of the team in another direction. It would have split our efforts, though, and almost certainly would permanently alienate an ally that I both need and respect.
Should I have played the councilor instead? Should I have fought, tooth and nail, for more time to pull together information? Should I have brought in additional resources and be damned with the decisions being made by the various important players? Maybe. Maybe not. I'm sure I'll wake up some night in the near future with the perfect gameplan.
As it is, at the end of the third day my team had, in professional form, gone on their merry way without me. They knew what needed doing and did it, professionally and well. We restored the system to a functional state though we have some process pieces to work out. I even managed to give way enough to get the things that I really wanted, even if I don't have the resources to deliver on them just yet.
I'll work on that second bit next week.
by sriramna
Your strategy IMO is as good as any if you have a competent and motivated team. I have found under the circumstances that you sometimes need to nudge things in the right direction, or resolve an impasse, and the trick is to identify and act on these situations.
by tonyschramm
Amen to the strategy employed, and the results showed it to be very effective! In my career, I have seen so many managers who feel compelled to minutely control every aspect, to the point where everyone is afraid to act on their professional instincts, and progress (resolution) ceases. To me, the true professional manager is the one who recognizes and relies on the skill sets of the technical talent that he or she employs, and who allows them to utilize those skills, adding gentle nudges and minor course corrections along the way.
by jcritch
Awesome job, the system was down and you controlled the events. We always have a post event meeting to discuss what needs to occur if this ever happens again, what down time procedures should be tweaked, or put in place, and most of all what support the vendor can provide upfront, during and after the event. Now is a great time to champion the end users around your team to help develop a clear game plan the next time a event similliar to this occurs..
Another day, another trip. Another week potentially out of touch with the horse-trading and politics of home base.
Travel is a regular part of the job for any IT person in a multi-site organization. Sure, we say we want to avoid it. I have a 22 month old son who I delight in seeing every day, so I really do. But the truth of the matter is that we cannot do everything remotely. Sure, we want to. It would be nice to sit in our cubes all day, every day, and never be bothered by the ugly realities of field work.
If we choose that, though, we lose track of important things. Things like what our clients actually do all day or why we do our jobs in the first place. We lose track of the drivers motivating the site IT groups needs, of the pressures they work under, and of the urgencies they face.
Losing track of these things makes us less effective. Just to start off with, it makes us forget that our job isn't bits and bytes; it?s the delivery of services (if not customer service) to the people who face the customers. Just as importantly, though, it also hamstrings us when it comes to negotiating. If I don't know what my counterpart really wants, what capabilities he has, and what timeframes he needs to respond in then I cannot create a winning transaction for him. If I cannot create a win for him, then he has almost no reason at all to give way on the things I really need.
I'll natter on a bit more tomorrow about this week's plan. For now, I have an upgrade to interfere with.
In theory I'm on vacation right now. I say in theory, as I've got a heck of a lot to get done this weekend for business and for a house I no longer live in. Sometimes I wonder if I'm paying kharma off at a vastly accelerated rate.
Anyway, today I wanted to talk about the events of the week. Well, that's not entirely true; I want to talk about the emotions, causes, and situations underlying those events. If I talk about the event's themselves I'll probably say too much about things people would rather I not say in public.
The week started out as well as any week of travel does. My senior and I went out to a site to do an install. We hooked up with the functional support, the on-site IT, and the consultant hired in to do the application migration. We had a plan. We had the tools. We had the talent.
Unfortunately we also had a complete disaster. Okay, that's an overstatement. The users experienced an unrelated downtime in the middle of the second day of our 4 hour install. We managed, though a lot of hard work, to prevent them from feeling any of the heat we encountered. However, by the end of it all we were worn out. Three days straight of work without sleep will do that to you.
Looking back over it, I have to ask myself why I allowed it to happen. Individually each of the decisions was the right one. At the moment we made each choice, it was the most logical step forward. Looking back over my notes I can honestly say I would make the same decisions all over again, given the same information and team skill set.
The overall result even turned out okay, though we have a number of follow-up items to resolve. The system is up, patient safety was not compromised, and the users like most of the new features.
However, I have a nagging feeling that I pushed my team to hard. We didn't have to stay up for two days; this system frankly isn't that important. If it didn't get upgraded, we could have just rescheduled. Similarly, we didn't HAVE to kill ourselves that second night trying to get the preferred software distribution method to work. We could have fallen back and punted with the old method, which is what we ended up doing at 3:30am.
So...did I drive the team to hard? Maybe. I wanted to get it done, yes, because my team needs to do 5 FTEs of work with 4 bodies, not including the 2 FTEs of management and operations we need. When a schedule slips it hits everything, hard.
I also wanted to prove a point to someone in our organization. This person constantly complains that we do not meet our deadlines and that we don't give work associated with his group sufficient priority. So, I wanted to prove that we do care, even about little things like this application.
There's also the issue of the political acceptance of the new software distribution solution. It's not well liked, even though it's worked well for just about everything we've tried it on. No one, including us, has a choice in the matter anyway; with the desktop image in the shape it's in we absolutely need a medium-term virtualization solution while we get the desktops back into shape.
I suspect it's the lack of options which makes it so unpopular. People like to think they have options; executives and would-be executives like to think they have control. To manage yourself into a satiation where the environment dictates direction rather than you dictating the environment doesn't make anyone happy.
In the end we got it done. We got the protection we needed, for the most part, and I stifled the attacks on my team in a meeting. I'll pay for that; using interaction tricks to control a situation did not make the person being controlled any happier. I lack the political influence or authority to stop her from chewing me up eventually. It's just a matter of time and hopefully pulling enough together before that day comes.
On a happier note I did get to two days working with our field staff. With luck, I proved myself enough to be invited back. Connecting with the field staff and their executive management can only help me in the long run; fundamentally they sit closer to the client than I do.
Last, and certainly not least, I realized something about healthcare IT. Generally in IT we are pretty close to the only reality in the business. We do things with discrete beginnings, middles, and ends. We actually get motion and results, which leads to some very strange warping of the political landscape.
In healthcare, though, we do the least "real" activity imaginable. Or at least we did, until our tools started to show up at patient bedsides. Now we suddenly find ourselves in the patient care business, rather than taking care of the back office.
I'm going to have to think about that some more. It's possible, even likely, that I can wring something useful from it.
Back to weeding. It's going to be a long weekend.
Insert comment text here
Wow, deja vu all over again. You probably wouldn't be an IT professional if you weren't trying to do too much with too little. It's life in the world of IT. Of course there will be those out there who say, just plan better. Yes, planning always helps, but in my experience, stuf happens. It's always nice to have a good mix of people, with different skills, who can work together well in stressful situations.
Having folks outside of IT watching you is always fun (well sometimes fun). They can get a glimpse of what you go through, how you need to be an expert in what you do, but also almost be an expert in what They Do. A good IT person is a rare breed. Probably smart enough to do almost anything, but humble and with a servant's mentality to do what they do. When folks have their computer doing exactly what it should be, they are just satisfied. When it doesn't do exactly what they want, they are extremely disgruntled (and often you are the source of their disgruntability). When's the last time someone called to say, "you're doing one heck of a job!" Hopefully once in a while.
Anyway, go back to your weeding. You love it man, don't ever change. God bless, Another IT Maniac.
by junk83501
Have a good day Daniel
Well, I'm back in the apartment. I would say "back home", given that my wife and son live here but it still doesn't feel quite like home. The house I worked on all weekend, the house where I brought my son home from the hospital and wrote my last book, still feels like home to me. Maybe someday I'll feel the same about this place.
My view on my new job fits right in with the feeling of "almost but not quite home". People are, for the most part, friendly enough. My team and I do good work. Heck, I even managed to assist the team working on bringing back up one of our major systems - that they wanted to do the work I had already scheduled for this week just made it easier to give them the victory.
Feelings of confusion and newness aside, though, we loaded this week with enough activity to drown a small horse. I have team members working on upgrading servers, building document sharing Sharepoint sites, coordinating the department support queue, and producing a cluster-frack load of documentation. That later falls mostly on my plate; I'd rather spend my "productive" time writing about what we will need to do in the future than mucking up things in the present.
I suspect the production of documents doesn't help anything. Our organization sits squarely in the "rapport-based" category, even though its far too large to actually support direct one-to-one communication in any useful form. The people with power, authority, and/or influence have little use for clear process documentation. They would rather fly from one situation to another, trading favors and reinforcing influence networks. It feels a bit like working for the government, only without a clear chain of command or anyone willing to put their foot down long enough to get things done.
Though, frankly, that later comment's not fair. People do put their feet down. All the time, in fact. The problem is we, collectively, do it on whatever hot button topic occupies our attention at the moment. Over the years the organization developed some rather remarkable incident response methods - some good, some not so good. However, the really important change from a chaotic small shop to a working process-based midsized shop will require more from us than just good incident control.
Now, if I were a capable man I would trade and trade and trade until I finally got enough markers pulled together to get a champion for process change. Were I a thoughtful man I might try to introduce artifacts and tools from various operational methods, seeing what I can get to stick and what I need to let go of for now. Were I a diligent man I might try to show how information-based capacity planning give us the ability to predict or even prevent operational problems.
My team will have a couple of good opportunities to do all three this week. Hopefully they can make some headway.
My team and I got to explore the joys
of chaos in action this week. On one side we had a brand new system
slowly spinning apart. On another, a project suffering from one of
those cursed implementations we all like to talk about over beer as
the ?worst installation I ever worked on?. Meanwhile several
other problems dogged our heels until we finally got rid of them.
All in all, a normal week at the office.
Of interest to me, though, was my own
reaction to the whole mess. My thoughts always turn inward in times
of stress; I learned a long time ago that I cannot control others
actions or reactions, only my own. It's wisdom of a sort, though not
always terribly useful.
The question of where to put my focus
dominated the first part of every day. What, exactly, did I need to
focus on to produce the right tactical outcome? Which of the many
things spinning out of control did I want to get hold of first, which
could wait, and which would just have to go on without me? How would
I choose and what measures would I use to determine when I needed to
intervene?
This was, I'll admit, a fairly
cold-blooded way to go about it. Getting flustered, though it would
convince some of my erstwhile allies of my sincerity, wouldn't
accomplish everything that needed done. Additionally I have a highly
trained resistance to wasteful motion. I'd rather wait, watch, and
then take the shortest path to where I want to go rather than be seen
to move, especially to little purpose.
Anyway, I decided to sacrifice some
tactical outcomes for purely strategic goals. A less airy way of
saying that reads as I divided the work among my team members, worked
with them to keep them focused and get them resources or answers, and
kept my fumbling hands to myself. That last bit took a good deal of
self control; it was tempting to jump in and try to help even when I
had no clue what needed to be done.
This approach meant some things didn't
happen on time. Other times, I wasn't involved with on-the-spot
decisions that I wanted to have a say in. Heck, a few things fell
though the cracks and I may have accidentally thrown someone I
respect under a bus. If I did, I'll have to go beg forgiveness next
week.
You know what though? The things that
got done late were done very well; the issues with their completion
were logistical rather than technical. That means they land squarely
back on my plate. The team member who made the decision made it
EXACTLY as I would have, for the same reasons, and using the same
principles of engagement. In other words, I succeeded as a leader
even if my personal desire for control nibbled away at my heart.
And those things falling though the
cracks? They are, uniformly, things I've kept on my own plate for
too long. Things where I wanted to prove my use and worth by helping
the process along. Things I assessed and planned but failed to pass
on to my team for review and implementation. In other words, things
I tried to individually contribute rather than create though a team.
I know better. In many cases the key
to successful leadership lies in letting go. Grandstands and heroic
actions mean less than creating a balanced environment for the team
to thrive. But, darn it, I'm like almost everyone else. I entered
leadership by proving how much I could accomplish on my own. Letting
go of things, even when its time, hurts more than I want to admit
sometimes.
So, here I sit, with a plate full of
slightly spoiled process pieces. Do I let them go? Clean them up?
Just kind of spruce them up a bit and serve them for lunch next week?
I'll have to figure out what to do
later. For now, I'm tired but reasonably satisfied. The team did
well. Individually they acted with integrity and wisdom. As a group
we accomplished, if not everything we wanted to accomplish, then what
was needful given the tactical circumstances we encountered.
My own reaction to all of these
circumstances continues to amuse me. You see, I'm still. At the end
of every day I feel tired but quiet.
This week the chaos didn't touch me;
we'll have to see how that goes next week.
by ricklw
by catshev
Its funny how as techs, the toughest thing for many of us is NOT doing something. I had a boss once who ordered me to write down 3 things I did regularly, create a plan to train, and prove that I ACTUALLY delegated those 3 things. It was hard, particularly in places where I "invented" the procedure. I felt such a sense of ownership, it was hard to let go. Still, many years later, something I struggle with! It is a battle worth fighting with ourselves, for the growth of our teams, and our own sanity!
Nice post, I really enjoyed reading it!
Well, like the previous posters, I went exactly the same road from technical excellence to management / leadership. And although what you're telling is the way to go, I wonder where do you extract your satisfaction from once you let go of the things you loved the most? Sure, you may answer from leadership, or from people management or even from performance management of individual team members -- working with each and every one of them and helping them kick ass. Paving their road to performance and accomplishment.
Sure, this sounds trully nice. But what about your OWN satisfaction? What about those things that made you tick, for which you woke up in the morning and hurried to work even on Mondays?
I think we all have to go through a serious and sometimes painful transition. And for me at least this proved to be anything but a simple task.
by robin_conway
Reading this made me smile. You're moving from being a manager to being a leader. Taking your hands off a project and providing guidance, knocking down barriers, and sorting out the "need vs. want" that come with every project is a sign that you understand what you personally need to do to make your team successful. That is what managing and leading are about.
Releasing the inner geek and filling the role of guru is no easy matter. The question I ask at the end of every project is not whether the project ran on time, or delivered each and every piece as planned but "did we make a difference and are things better now than they were before?" Certainly there are absolute things that need to be done from a business perspective - making sure money is coming in, making sure that parts pieces and services are aligned, and making sure people are safe - but personal satisfaction and actualization come when you know you've made a difference and the business results show up in improved performance, market share, and satisfaction. Knowing what needs to be done to achieve each of those is what distinguishes managers from leaders. You've made the first great leap into the chasm and now understand that you aren't going to plummet into the bowels of project Hell as long as you are doing the things you need to do to build and coach a team or teams that are able to fill the basic business needs and understand that there is more to project life than a schedule, features, and release - it is about making things better - be that measured in market share, revenue, lower cost or simply being recognized as the place to beat (and work!) in your industry segment.
by michael
Two quick thoughts:
1) Winston Churchill may have said it best - "Perfectionism spells Paralysis."
2) Perhaps even a greater philosophy that relates to this excellent post is the following: Success is figuring out how to do more with less.
by wrlang
In most cases your team will mimic your reaction to a situation to give that situation its proper priority and attention. So you can affect your teams reaction by controlling your own reaction. In most cases you want your team to react as you do, with calm controlled actions and the appropriate amount of urgency.
There are a tremendous number of task masters and project managers out there who also have people working for them. With maturity comes the ability to let your people put their creativity to work taking over the processes you've created and enhancing those processes. Providing guidance is advising an employee what may go wrong and why, and then letting them use their creativity to find the answers. If you continure to hold onto the process and tell employees how they should do things, you will lose the most important ones - the ones with creativity.
Few employees are zombies that need to be told what to do and how to do it every minute of every day. If you find that you have a pack of zombies, you need to seriously consider yourself as the possible problem and review your maturity level and management style.
Too many managers/people fail to understand that there is more than one way to get something done. Not doing things your way doesn't mean its not getting done the right way.
For what its worth.
I remember a
distant time when I used Mondays for planning purposes. In that
golden age I spent the morning working on my plans, visited with my
various colleagues, and got ahead of the situation. Sometimes we
even took some moments for levity before things went spiraling out of
control.
Ah, those halcyon
days of youth, all of four weeks ago.
Today got consumed
not with useful work but with sitting in meetings watching yet
another train wreck play out. People got amped up with heroics this
weekend; always a bad way to start out the ?beginning? of the
work week. I got drawn into it as well. I didn't do well, honestly,
since the first I heard of it involved taking my best analyst and
sitting him doing a procedure job best suited to a temporary
technical resource. The conversations went downhill from there.
I spent the time
between meetings working on a variety of little process pieces which
fell though the cracks over the last few months. Some of it I'm
happy with. Some of it will need reworking tomorrow or the next day
as time allows. Quite a bit of it I didn't get a chance to explore
to any depth at all, but getting it moving seems more important than
getting it all right at the moment.
The lines between
activity, transformation, and work always seem a bit unclear. They
become even more unclear as life, politics, and that annoying thing
called relationship management meander into the puzzle. Once you
start layering on the complexities caused by technical
troubleshooting, the reinforcement of bad or maladaptive behaviors by
organizational foolishness, and the desire to maintain the status quo
it becomes almost impossible to sort out which is what.
All that said,
though, the blurry terms I allude to above do help me to organize my
day. Each category provides me with a ?bucket? into which to
initially lump the activity headed towards my team.
Activity, for
example, includes all those actions we undertake for the sole purpose
of creating the appearance of motion. A classic example, one I'm
sure most people can relate to, is the overly detailed work breakdown
structure masquerading as a project plan. Yes, its possible to
create incredibly complicated WBSs for nearly any activity. However,
people rarely follow such detailed plans. Instead they build a
simple critical path, execute it, then move on with their lives. The
act of creating the plan is activity; it may be activity in response
to a corporate mandate but its still time spent creating an illusion
of motion rather than doing something.
Meanwhile
transformation involves seemingly fruitless time spent working with
others to get them involved, interested in, and eventually a part of
a completely different way of working. Transformation, or at least
the work of it, involves as much transformation of yourself as it
does others. You have to let go of your conception of what should be
and instead become it...a strange way of saying, I suppose, that you
have to believe in and create the environment you want to live in.
Your own actions, though, cannot change the world. You have to get
others to believe as well, a particularly thankless task which often
ends in disaster.
Finally we get to
work, one of my favorite subjects. It always seems so simple at
first. You do X and get Y result. Unfortunately most tasks in the
IT world don't fall into that simple pattern. In fact, if you spend
a little time looking at it, you can find five work patterns (or
?queues?), making the measurement of work particularly
problematic. Or just down right annoying, when you want to
distinguish say reactive work from activity undertaken to meet an
assigned but not meaningful deadline.
Fortunately I
managed to help the team organize for the week before getting dragged
down into chaos and activity. We have the usual list of tasks on our
plate, none of them ?save the world? important but some valuable
enough to mean something. If I've done my job the team will be up to
it's eyebrows in work before Tuesday morning comes; if not we'll get
bogged down again in activity.
More later. I
have some thoughts on transformation to chase down.
Another week down.
I've barely managed to keep my head above the waves of meetings.
The team accomplished a fair number of important tasks; for the most
part they did it with only minimal direction from me. That's a good
thing, mostly, though I suspect my not knowing whether I would be in
the office on any given day didn't make things any easier.
I'm pondering
changing the way I plan things out, at least in the short term. As a
general rule I use sliding logistical windows, critical paths, and
the assumption that each individual can accomplish his goals within
the time frame he gives me. I communicate what seem like appropriate
details (success/failure, milestones achieved/missed, and change data
mostly) in a timely fashion. I do not always go into all of the
details of what piece is where, when, and why unless it seems
important.
Some environments
rely on role-based communications in which each role produces
communications output in a specific format for use by the next role.
Others rely entirely on individual rapport, built up over a number of
years, in which each person formats his communication and approach
not based on what he does but rather on his relationship with each
person. Most organizations work somewhere between the two extremes,
allowing you to build rapport with your peers and immediate superiors
and using role-based (formal) communications with others.
My planning
tactics pretty much rely on an organization sitting between the two
extremes. I'm open with everyone, about everything, but I do not
always fill in all the details. I'm used to the idea that an
executive wants decision-making information, a manager wants metric
information, and a leader wants to have a chat. I look forward to
interacting with my peers to build rapport across the organization
and to smoothing out confusion within the formal communications
structure via proper processing of procedural artifacts.
The further
towards one extreme or the other the organization falls, the less
effective my approaches become. When an organization's executives
hold meetings to decide the technical details of a project and make
their decisions along rapport lines rather than role-based
discussions, I have little to contribute. More importantly, what I
can contribute doesn't really resonate with the people making
decisions, since it doesn't fit into the world they created.
It also leaves me
a bit adrift. Frankly I like sliding logistical windows; I enjoy the
give and take of working with my peers to guide our teams towards the
solution to knotty technical problems. I get a thrill out of working
with a diverse team of people to create solutions meeting both a
company's strategic goals and the end users' various needs.
My current work,
though, tends more towards heroics and brute force than the kind of
high-speed chess matches I favor. People of all ranks go charging
up their hills, ignoring the huge amount of incredibly dull but
important work waiting for someone to pick it up. The environment
goes untuned because, frankly, tuning and spending months tweaking
small values for an isolated marginal gain (no matter that the
overall effect of several hundred such tweaks is huge) does not
interest them.
Now I'm getting
maudlin, I suppose. I've seen this all before. About half of the
organizations I've assisted tend towards the individual hero model.
Most even inculcate it in their processes, lauding or at least
rewarding those who create additional chaos just so they can prove
their worth. Personally I'd rather fade away into the background,
quietly making things better one tweak at a time. The chaos of my
current environment comes from too much of the former and far to
little of the later.
Sometimes I wonder
if people really understand just how much we make the world we live
in. I doubt it; imagining ourselves as the creators of our world
implies a responsibility both for how it works and for its future
people rarely want to take on.
But, once you see
it, how can you turn away?
Mondays are good
for melodrama. Everyone's rested up from the weekend and filled with
good intentions. Sometimes people even come up with good ideas after
a few hours away from their keyboards. My own team, for example, had
some excellent points to make about things we need to accomplish.
So, either they came up with them over the weekend or I finally
slowed down enough over the weekend to really listen to them today.
Probably, given the nature of the world, a little bit of both.
It's the ?a
little bit of both? really struck home with me today. When people
get to moving fast, and pushing hard, we tend to focus in on one or
two things we believe to be important. These key issues become the
sole things we work on, regardless of everything else going on around
us. We work at them until we resolve them, then feel honest surprise
when the overarching problems do not go away.
In reality a lot
of problems (rather than incidents) in IT stem from multiple causes.
Most real, reoccurring problems involve some process pieces, personal
issues, misapplied or incorrectly configured technology, along with
some good old fashioned bad luck we didn't notice at the time. It
all kind of lurks around in the background until some relatively
random event creates an incident bringing all of the related causes
to the surface. Sorting out what's really going on, though, can take
a lot of work and a level head.
Right now, for
example, we've just finished work on an incident which disrupted
service for almost five days last week. Everyone involved struggled
with the system; we eventually fell back and punted rather than keep
fighting with it. The workaround did stabilize the situation for
now. With luck it will keep things mostly stable while we figure the
rest of it out.
Everyone's focus
currently rests with the effort we went though. Yes, we did not
communicate as well as we could have. Yes, our teams did not always
share information in an actionable way. It also took us a while to
figure out a good workaround.
My interest, and
where I've asked my team to focus in on this week, falls squarely on
the problems the incident exposed. The lack of technical planning,
environmental consistency, and practical methods for troubleshooting
just start the list. Far more fascinating was how the incident
displayed preconceptions and fractures in the lines of
authority/responsibility surrounding the technology in question.
These are long standing architectural and systemic issues no one can
solve quickly. Seeing them in action, though, renewed my commitment
to initiating slow change.
Meanwhile, in
another forum, the same problems played themselves out during our
preparations to restart a project plagued by technical glitches. It
made for interesting listening, even though I mostly stayed out of
it. I'm still questioning that decision, but if after working with
the project manager, my senior on the project, and a half dozen other
folks we couldn't win the battles that mattered I probably need to
find another job. Fortunately we got what we needed in terms of
scheduling; everything else was a sacrifice we happily made. Tying
my senior up for two more weeks wreaks havoc with my scheduling, but
I want to make this work for a lot of reasons.
That doesn't mean,
though, that the team isn't feeling the heat from having the senior
out of action for this long. I've pushed an assessment job down onto
one of my intermediates; he's a good guy and very talented. But its
his first serious assessment and its not something he's ready for.
That said, he'll do a hell of a job with some help and coaching. I
just have to somehow get the time to do that coaching while still
making it to all of my meetings.
The same problems
also came to a head over on another team's plate this afternoon.
Generally that's something which causes me to offer my sympathy. In
this case, though, it directly impacts all of my projects and my
currently deployed systems. The other team's work is good but I have
to question whether we've lost sight of the core technical problems
they want to address. More importantly, if we have lost sight of
those problems what can I, as an outsider and not a well liked one at
that, do about it?
So, it's the usual
mix of negotiations and scheduling planned for the week plus a heavy dose of coaching for everyone involved. Including, I
hope, me. I'm going to try to get in touch with one of my mentors to
discuss some issues that came up last week.
Well, its been a
busy week. We learned a few things, stuck to the plan as much as we
could, and went out with a bang. Fortunately no one got seriously
injured in the process, though I had to drop my pride in a bucket
again. And again. And again. They tell me it's good for me.
You see, we had
several issues arise this week. The fact that the issues themselves
arose doesn't come as a shock to anyone; life as an IT person tends
to involve incidents of varying magnitudes. However, the concept in
my last blog came into play heavily.
Incidents bring
issues to our attention which we then address first though
workarounds and then though problem analysis and resolution. You
find this method, described different ways, in all kinds of customer
service and operations approaches. What they don't talk about is the
catalyzing effects of incidents on the general systemic problems
Let's follow the
logic. Many incidents begin as random events. You load patches
you've loaded a dozen times before and the server bombs out. You try
to install software on a server image already in production on fifty
servers and the installation generates a run-time error. A user
calls in because a Windows server's print spooler decided to stop
working.
The repercussions
of the event, though, play out within the context created by history.
The server which bombed out may be part of an ongoing dispute
between two departments, a dispute raging over half a decade
regarding the importance of a system which accidentally became both
mission critical and without a business continuance plan.
Resolving the
incident by working around the issue requires good technical skills.
You need to be levelheaded, determined, and willing to take some
risks. You need to know when to wait, when to gather information,
and when to plunge forward knowing you might not have THE ANSWER but
that you have an answer which might work. Mastering those skills
takes quite enough time and patience from anyone.
Now add to that
the understandable panic of people caught without a business
continuance plan. So now the business has stopped, enterprise-wide.
The blame gets laid at your feet, not to mention the heat you
personally feel because, despite what others may think, IT folks
generally want to do a good job. We don't like taking down systems,
especially after our test showed we wouldn't.
Now add on top of
the previous two points that the system, due to political
compromises, never performed well. Your leadership knew it was going
to go down disastrously at some point. It went down twice a week in
a modestly controlled fashion before four months of tuning brought it
into an almost stable configuration. So now a fractured management
team must face their worst nightmare; they gambled and lost. Big
time. How they respond will tell you a lot about who they are and
why they do what they do.
Just to put a pin
in it, make it so the system drops on the evening before another
system is about to re-pilot after being down for a month for repairs.
The system that dropped is in the same group as the other system, so
in the end the same managers become ultimately responsible.
It's not that all
of our hard-won technical skills mean jack. It's just that, in the
anatomy of a disaster, the actual technical incident only modestly
affects the events as they unfold. We can resolve the incident,
create workarounds for the issues exposed, and resolve the problems
yet still lose the war. An incident may close in a matter of hours,
yet it will reverberate for months as structural issues play
themselves out.
So, what do we do?
As a leader I try to keep the non-technical elements of the disaster
off my team's plate. As a manager, accidental or otherwise, I try to
keep the team focused on activities leading to greater operational
stability. As an IT architect with training in risk mitigation and
system design I feel deep and abiding pain every time I look at the
way the organization chose to deploy some systems and support others.
That last is just pride, though, and does not belong in the role I
currently play.
Thus back to my
comment about swallowing pride. I don't make decisions; I just try
to keep people from getting destroyed by the choices they make.
Sometimes my team can pull it off. Other times we've got too much to
do and not enough time to follow though with the basic mantra of
incident to issue to problem I laid out above. Without each part of
the team playing their part we really cannot do it.
But no one wants
to hear about the problems. It's all just ?excuses?. The user
community does need help and they need it now.
Ah, Monday's going
to be great fun.
I hate falling
sick. I hate being sick. I hate going to work, realizing I need to
spend quality time with my bathroom, and coming home. I hate
dropping all of my work off onto my team...
...oh, wait. My
primary work supposedly revolves around assisting my team in
organizing their time. Doesn't it? Or have I fallen into that old
trap of trying to do too much as an ?individual contributor?,
proving my worth by doing rather than helping.
It's hard to tell
when you are on the right path. As a rule I try to pass tasks from
me to my team; I act kind of like a task collector, moving though the
environment and pilling up work, which I then hand off to more
capable people to accomplish. When a task comes up suddenly,
especially a busywork task I don't want disrupting my team's work, I
take it on my own plate and get it done as fast as possible.
Today, for
example, I meandered into work early to help with some reboots. I
don't like asking my team to come in before 6AM as a rule and I
thought I would be at my desk most of the day, baring meetings.
Besides, I may be rusty but I can handle remote rebooting an NT
server. Shutdown.exe is an old and dear friend.
Should I have
given that task to, say, the department on-call person? Probably.
He is paid to come in to deal with that kind of thing. But the
servers were my responsibility. I wanted to get some planning work
done before the day started. Yada. Yada. Yada....there's always a
reason, always a noble intent behind taking on more activity rather
than doing my work.
Being sick
actually helped me. It forced me to let go of a lot of excess tasks
I horded up. My team can handle them, mostly better than I can, so
long as I define them properly. Doing just that took most of the
morning. Apparently I horded a bit more work than I thought I had.
Now they've
dispersed, though, and I might actually be able to do my job of
planning and assessing the operational and project needs of my team's
lines of service. After I get back from spending more quality time
in the bathroom.
by th7711
It is not easy to judge how many jobs should be delegated to next level. Only ?good? manager can do it right. (I have to admit that I am not the one.) However, we ought to keep this in mind and try to do it everyday, every time. You cann't be success unless you have started your first step.
On the other hand, you should able to aware any potential problem and step in at the right time before it is too late.
by th7711
It is not easy to judge how many jobs should be delegated to next level. Only ?good? manager can do it right. (I have to admit that I am not the one.) However, we ought to keep this in mind and try to do it everyday, every time. You cann't be success unless you have started your first step.
On the other hand, you should able to aware any potential problem and step in at the right time before it is too late.
by th7711
It is not easy to judge how many jobs should be delegated to next level. Only ?good? manager can do it right. (I have to admit that I am not the one.) However, we ought to keep this in mind and try to do it everyday, every time. You cann't be success unless you have started your first step.
On the other hand, you should able to aware any potential problem and step in at the right time before it is too late.
by ivy clark
My team leader does this to me, and I hate it when he's not around. I also hate not being able to provide the answers I need to (during his absence), as I do not have any idea as to what's happening. It makes me look silly and helpless in front of my users.
It's also difficult for your colleagues to take on tasks you have been hoarding when you're away, if they have not been kept in the loop regarding the tasks and procedures involved. Being able to pass on tasks while you're around helps ensure things run smoothly when you're not. So, you're really helping yourself - unless you want to remain available and accountable even when you're on that special holiday...
by saleemi
Not letting go of work is also one of the main we always think our team
members are not mature enough to handle sepcial tasks. Where as in fact
they do specially when you are physically away. I know of people who
always assigned their task to others and tried to stay away from
involving in minute details, these people later moved one to be
promoted and appriciated. The team we have is at our cost when
executives see us the count the team too.
by ivy clark
by centeno
add another scenario....
you're the CIO (call it whatever you want), but also the helpdesk, the hardware repair guy, and almost everything that blinks or as a button falls in your desk.
In Portugal we're used to be "smartasses", and we play all the jobs, on contrary of being experts in a field. I don't yet know if its a better or worse aproach, but i can tell you that all my users pass by the problem of having a very small situation taking 3 ou 4 times more time to be solved.
hoo, and planning doesn't play any role where. I've millions of plans (snort, hylafax,...) in my head, but that stupid HP930c had gone out of paper again! let me go and put some paper on it, because the guy from the telecom is arriving for the negotiation the new site where oppening. (300Km away!!)
by clangl
This really hits home for me. I have recently resigned from my position as a Director of IT and one of the reasons was along these. My current boss wants to be in the middle of everything. I never thought about it but I do it myself as well. The other problem with not delgating is that you are setting up your entire department to be just like you.
This really hits home!!!
by clangl
This really hits home for me. I have recently resigned from my position as a Director of IT and one of the reasons was along these. My current boss wants to be in the middle of everything. I never thought about it but I do it myself as well. The other problem with not delgating is that you are setting up your entire department to be just like you.
This really hits home!!!
You do not work on a fire rescue, the systems should run 24 X 7 365 days a year not you. I worked on the same way and same philosophy you wrote and I gave it up. It is not a change management question, it is about a person me or yourself and our own emotions and anxieties it is hard to change our own behavior.
I changed step by step, understanding the emotions and planning, taking one action after the other, teaching my team to organize theirselves and improving their planning using Outlook or Notes. I worked so hard figuring out better ways on delegating and supervising and I wrote about it at Facilitating Teamwork chapter in the book Managing your Business with Outlook For Dummies. Read it and maybe will help you one way or the other.
MarceloThalenberg
This week actually
turned out fairly well for the team. They knew what they had to do.
They adapted when operational problems manifested themselves as
system wide incidents. Three out of four tracked incidents back to
their core technical issues and addressed them with the quiet
intensity I so adore. No muss, no fuss; just solid work performed in
the background. The fourth closed up a project then dived right into
a knotty analysis complex without a moment's complaint. Pretty much
what I've come to expect from these gentlemen.
With my team doing
a bang up job, though, I'm given leisure to ponder other things.
Well, with my team doing well and me on my back most of the time from
being sick, otherwise I should be out there doing something. What I
ended up pondering this week was the difference between what I think
IT should act like and how I often see it done.
A few years back I
wrote two articles for Tech Republic about two ?styles? of
consulting: the visible and the invisible. Visible consultants, in
effect, use their position to promote necessary activities.
Invisible consultants support their hosts, providing knowledge and
service to those who need it. The first style might be best
characterized by the statement ?I'm here to help?; the second by
?How can I help you today??
These ideas
translate reasonably well into the operational and project world I
find myself in these days. On one hand you have individuals who want
nothing more than for their whatever to save the day. They strive,
seek, and never yield. On the other hand you have folks who want
everything to work so well that, frankly, no one ever knows their
names.
Before I go too
much further let me say something right up front. I know no one
actually adheres perfectly to one style or the other. Everyone comes
down somewhere in the gray area and their position along the spectrum
changes they do.
Now, caveat
inserted, lets get on with the show.
At the furthest
extreme those who hold to the concept of ?visible? operations
want their involvement with business critical systems known from one
end of the organization to another. They want people to understand
just how valuable IT has become. They seek out highly visible
activities, work hard to get the word out, and frequently develop
reputations as organizational champions.
This approach does
have a lot of attractions. To start off with, it's a lot easier to
demonstrate value when you have some major victories to point at.
Having saved the organization some seven digit number in dollars
makes a powerful argument for your continued employment. The more
you are seen to do, the more people believe you can do. It's also
kind of a rush; knowing you and your team can stave off the flood
makes some of the really unpleasant parts of the job endurable.
On the flip side
we have the invisible approach. At the furthest extreme you come to
the proverbial system administrator sitting in his dark cubicle. No
one dares approach him, for fear he will cut off their access to the
network. Yet his long hours and constant vigilance protect the
organization from problems most people do not even know exist. Less
extreme versions of this approach lead to people working quietly on
processes or building management tools to automate complex and
repetitive tasks.
This approach,
frankly, involves a heck of a lot less stress than the first one.
The invisible folks want the system to just run and take the steps to
make that happen. They get in front of issues before they become
crises (see the blog a few posts back about that) and do a good job
keeping the environment documented.
Either approach
creates an unbalanced environment when left unchecked. The visible
folks charge from one activity to another, leaving a host of half
finished systems in their wake. They manage crises with methods a
firehouse might envy while simultaneously ignoring the risks piling
up all around them. Meanwhile the invisible folks resist change and,
if left to their own devices, auger in projects with whatifs.
The trick, I
think, lies in building teams and departments with an appropriate
balance of approaches. This doesn't necessarily mean balancing
personality types, though that's another way to think of it. If you
have a strong, visible team leader balance him with a senior who
would rather no one knew what floor the IT department was on. If
your department manager likes to take an invisible approach help him
by giving him a team lead who wants the world to know just how much
the IT department saved the company this year.
The danger lies
when you create, by accident or design, large concentrations of a
single approach. Two conflicting styles prod each other into motion
and keep themselves in check; a monolith just reinforces itself. A
critical mass of visible actors, or visible actors in a direct
reporting relationship, can very quickly reach their extreme
behavior, spinning the solution wheel until a massive operational
problem distracts them. A similar group of invisible actors tends to
quietly vanish, perhaps never to be seen again. That's alright for a
year or two but they will eventually become out of date, potentially
even a burden to the organization.
Personality
conflicts increase the dangers of matched styles in direct reporting
relationships. Two introverts who take on a visible style can find
themselves at loggerheads in a matter of minutes over approach and
intent. Two extroverts seeking invisible IT sometimes end up
undercutting one another as they struggle over priorities and
alliances.
So, what does this
have to do with my team? Well...not much just yet. It's a bit of
analysis I hope to transform into another view of the activity data I
have. Eventually, when I have enough views, a hologram will emerge.
Once that happens I can, perhaps, make some real decisions.
by stryker08
First off I would like to say great article, I work at a college IT department(Internship) and I can completely relate to what you are saying about the difference in styles. I am partnered with an extroverted person and we motivate each other/keep things going as I am introverted. I must say that I am particular to the invisible approach but working at this college the visible approach seems to pop up more often then not. It's great for the department but I often find that users will seek me out and refuse/dislike talking to my colleagues about their problems.
I am also an RA at my college and they cover the differences in personalities/working with a variety of people in depth during our training sessions. It's always interesting to notice the little things people do/how they behave when put in a given situation to determine which type they are. They don't even know they are doing it most of the time, which leads me to ask, can people really change who they are? Or do they simply modify their behavior/condition themselves to a different response?
Today I sat and
thought. I only had a handful of meetings today, so I actually took
the time to work with my team, get things moving for the week, and
even finish some of my own analysis tasks. It's hard, sometimes, to
cram all of the thinking I have to manage into a day. Which seems, I
suppose, kind of a lame thing to whine about.
However, the idea
does lead me into a far more interesting topic: how creative thought
works in an reaction dedicated environment. Creating actionable
information out of raw operational data takes a lot of sitting and
thinking. It's the kind of task you have to pick up, ponder, put
down, go get some tea, go off, pick back up, ponder, try some things
out, find they don't work, ponder, etc, ad nauseam. Meanwhile an
reactive environment emphasizes rapid response to issues, hopefully
before the escalate into disasters. The tasks come in and go out at
a fearsome rate, usually with hastily constructed workaround wrapped
around them.
Now, I don't know
about anyone else, but I have trouble really digging into a creative
analysis when I have to react to incidents ten or more times a day.
Incident resolution is all about the quick fix; you have to get the
user up and running as fast as humanly possible without breaking
anything else. Creative analysis is about the steady application of
thought to isolate and ferret out the problems causing the issues
uncovered by incidents; it takes huge amounts of time for potentially
very little gain.
In my case,
though, I'm not just worried about my own psychological hang-ups.
I'm pondering how my team works and what I can do to help them
achieve greater throughput. My job isn't just about doing; it's
about making sure my team knows what needs to happen and can actually
do their jobs.
Recently I've
taken on kind of a ?sorter? role, as I've mentioned earlier. I
organize the serious issues and dole them out to the appropriate
resources. This approach works reasonably well for keeping the fires
at bay, but does little to further stabilize the environment. To do
that I need to get my team focused in on the problems, working in a
creative rather than reactive mode, and building serious resolutions.
I don't know if I
can do it with my entire team though. Just to start off with, they
worked in a purely reactive environment for years before I arrived.
Reactive activity is addictive; not only does it give you an
adrenalin rush but it also stops you from having to plan out your
next activities. It shortens your time horizon to the next major
disaster and you can just kind of coast from day to day without
really pushing your own limits.
More importantly,
I cannot change the environment. I need to build strength, either in
my team or in another team, to absorb some of the reactive work while
we reach out to resolve problems. Culturally that will pose us with
a major challenge. Politically I don't have the resources to pull it
off. Practically...well, that's a different story. I think I have
the support of my peers in pulling together a much stronger response
than our previous approach.
Unfortunately the
change will not solve my immediate problem. I will still have to
sacrifice some of my team to reactive work every week. There's
enough of it that it could consume two FTEs if I let it. Right now I
divide that into one FTE and two halves, with the remaining halves
devoted to creative activities and project work. That drives the
team members stuck in that half-way role insane, though, and I'm not
sure what to do about it.
I'll probably feel
better once I get my senior resource back. He's off on vacation this
week, after spending the last seven weeks being eaten up by a
project. I need some backup on all of this analysis work. I'm
decent at it most days but it takes too long to get though it all.
We got more done on Friday last week (when he stopped by the office
to idle away the last day before vacation) than I got done all the
previous week.
Which makes me
wonder if I'm pursuing this all wrong. Maybe the answer is not to
worry about shielding the team members but to make sure they work on
creative problems in teams. Hummm...if it works for snipers it might
work for us.
Or not. Something
else to ponder, I guess.
by problemsolversolutionseeker
I just turned down a rather prestigious job where I would be working with a good friend of mine because I knew that I would be working in an entirely reactive situation. My friend was a bit incredulous. Your post appeared at a good time for me.
I would like to add that some of these people that you think are being reactive only are being creative in other matters that are costing your company productive time anyway. So, yes, you have resource issues, but if you present the creative issue properly, I think you would find that you would more productivity out of the same resources. That is, you would merely be changing the focus of their creative activities.
Hope this make sense.
by rahammers
Our lives are are filled with too many meetings however this type of issue may require yet another one. What has been successful for us in the past is a root cause annaylsis meeting. In this meeting the problems of the week are quickly reviewed and categorized. If the "system" issue cannot be determined in the meeting the most appropriate resource is tasked with getting to the main issue and working on a resolution. This seems to work for the minor and annoying issues.
In my opinion, major issues requiring an immediate fix are easier to deal with and success has been found with the exact opposite approach. By standard operation procedure we have predetermined that 30 minutes is the acceptable time to look for a resolution. All hands work on the problem and try to assertain a corrective measure to fix the system problem. Once that 30 minutes is up, we take a 10 minute time out to review the situation and then split into two groups. One trying to correct the system issue, the other into trying to implement a work around thus commencing with restoral of services. Should the work around be implemented to satisfy users, the issue then goes to the root cause annaylsys stage described in the beginning.
In the interest of full disclosure I must point out that I work in the field of Networking - switches, routers and such. Much less of an art than programming.
by justin james
I worked at a help desk/network monitoring department for some time. It was a completely reactive environment. The phone rings or an alarm goes off, and you took action. If the phone was not ringing or the networks were fine, you were sitting doing nothing. Yet, I managed to get an extreme amount of creative, proactive, non-reactive work done. The secret is mutlitasking. Let's face it, 95% of the help desk phone calls are old hat that require zero thought on the part of someone taking the call. The hard drive is dead, the a wipe/reload is needed, they just need to reboot, they have caps lock on, etc. Or whatever the common issues are for you. I was able to write code to help the department out, run reports to see where our common pain points were, write training manuals, etc. All while on the phone with customers. It was quite a trick (and sometimes it was a bit embarassing, telling the customer about the hard drive RMA process because you are writing about it, when you are walking them through some network troubleshooting). But overall, it was quite possible. I was able to troubleshoot networks on my terminal while troubleshooting tape drives over the phone while writing internal Knowledge Base articles. If you are not very good at multitasking, this obviously isn' for you (of course, it's great practice!). But if you are, this is the only way to do it.
In a reactive environment, management has optimized the workforce to smithereens, taking a zillion statistics and "rightsizing" to the point where the hold time is always 10 seconds less than the contract specifies as a maximum, and making sure that everyone spends their entire shift on the phone. But the employee who is able to generate those KB articles, or analyse incidents to find common problems to pass back to Engineering, or who can do two tasks at once, or is available to assist other workers via IM/email while handling incidents etc. is the employee who gets the raises and promotions. I know, because I got raise after raise and promotions came very quickly for me in that environment, mainly due to that ability to multitask and produce needed, creative work in addition to handling the reactive work well.
J.Ja
by ctcarroll
Psychological perspective - disguise deep probing by using reactive techniques. Use an Ishikawa/Fishbone/Cause-and-effect diagram with your folks so they are "doing something" and not just "contemplating their collective navels" (from their perspective).
Look at it as training. Probing deeper into the environment almost always results in new insights and facts which will be valuable when in "reactive" mode. - The 5 why's - The fuse blew - Why? Too much pull on the circuit - Why? Been adding too many devices to same circuit - Why are we adding devices to an overloaded circuit? Because we haven't a clue that it is overloaded - Why? We never load balance - Why? It isn't in the budget or on the schedule. Okay, says the wiseguy; just replace the blown fuse and save all this time. That is fine so long as we don't get a tough-guy fuse which refuses to blow and eventually results in a fire which takes out the entire floor/wing.
Reduce the "underlying risk" in the environment. Base it on a risk management assessment of what might cause the most serious problems/threaten safety.
The first thing I would do is look at the personnality types inthe group. There are some people that thrive on the ER scenario where quick decisions and temporary solutions are the goal. They avoid looking at deeper issues and time horizons beyond now. It may be counter productive to try to get them involved in root cause analysis. I have seen some true crisis junkies that do not know how to do preventive work and were not able to handle problems until they reached the full blown forest fire stage.
Tasks switching kills productivity. There is a mental wind down off the last task and a mental ramp up on the new one. Those people that have been identified (either by you or volunteered) as enjoying the deep dive investigation that looks at the whole system, should have 1, 2 or 3 complete days each week (whatever you can spare) allocated to this work. To keep it contained, make sure they report back to the group on what they are doing and what they have found out.
If the organization does nto value this and only rewards the fire fighters, then it becomes tricky.
Good Luck
Mike Crocker
The week turned
out reasonably well from a process and project standpoint. We got a
number of things done which will make things easier in the next work
cycle. The team handled another week involving major outages
reasonably well. I pondered a lot of things which probably don't
matter much, but also helped clarify a few things. We also worked to
correct a badly broken support process and extended the scope of our
short-term alerting efforts.
I also started,
very slowly, to move my team though the gap between the now and my
long-term vision for their activity. I mentioned in my blog this
Monday about the difficulties I saw integrating the creative and
reactive work types and some thoughts on using teams to help
reinforce behavior patterns. I've decided to alter my long-term
plans to include the paired structure. Which raises the question:
what do I mean by long-term?
Many people think
and plan in only one time frame, usually called ?now?. What
cannot be done immediately falls to the wayside, eventually vanishing
entirely. This actually makes things like project planning a great
deal of fun, since people don't really have any fundamental belief in
what they put on the plans.
In my world,
though, every solution and plan involves three distinct time frames.
The first frame deals with immediate actions taken to work around an
issue. The second builds upon those solutions while bringing in
additional analysis and design elements. The third encompasses the
desired end results, which oddly enough rarely take on a truly
technical form.
The first, or
short-term, time frame usually extends from the immediate moment to
roughly one month out. This is what most people consider the now;
what they can do immediately or in the very near future to resolve a
problem or complete a project. It's an easy time frame to work with.
We can step up, do something, and see an immediate result. These
results, though, generally don't last for very long unless we expend
effort to sustain them. More importantly, its hard to build up
successful iterative change when working exclusively in the
short-term time frame. Planning exclusively in the now leaves you
skipping around, depositing work here and there.
The second, or
medium-term, time frame usually extends from one month to roughly six
months or 2 business quarters. Medium term planning is, really, what
most people consider ?long-term? when they really sit down and
plan. It's about the maximum distance at which most people can plan
out a concrete set of steps to reach specific goals The longer time
period means you can spend more time working on things, creating
changes, and driving forward initiatives requiring more than just the
buy-in of a small group. It also gives the team more time to analyze
a situation before acting, always a plus when dealing with problems
rather than issues. Under most circumstances, though, it also leaves
you kind of confused about what you need to do right now. The
?medium-term? window also slides quite easily, leaving the team
in a state where they don't know what to do next.
The third, or
long-term, time frame extends a over a year or more. The long-term
frame is the realm of vision and priority, where the leader
establishes what he thinks the environment should look like. It's
easy to get lost here, though. One can spend endless hours writing
vision documents or analyzing to determine exactly the right
?long-term strategy?. This time doesn't exactly go to waste but
without solid short and medium term plans it's not entirely useful
either.
The trick seems to
be to ?peel? your short-term plans out of the medium-term plans,
while making sure the medium-term plan's goals stay in sync with the
long-term plan. Easy to say, hard to do. I've personally found
writing it down in circles helps though...I have this vision of three
balls (one small, one medium, one large) with the small one pushing
the other two along.
My concrete
example for this week involved bringing people together to solve a
service outage. The plan served my short-term goal of getting the
system back up. It served my medium-term goals of building
competence within my team and creating additional systemic knowledge
regarding one of my core systems. It also played into my long-term
goal of slowly, carefully, rebuilding the social fabric of the larger
team I work in. Fortunately it also played into one of the resources
medium-term personal plans; the other one I'm not so sure about.
The question for
me, now, involves translating these ideas into a more effective
solution for my major conundrum. I have a long-term goal (and plan)
to restart the operational life-cycle at my current employer. Doing
so will meet up with a lot of resistance; I have to find a way around
it.
by gill
This is so very true. However, there are many people who would struggle to define the 'now' as up to more than the end of this week.
by antbee
Well, you would think I could avoid
getting into trouble on the Monday of a holiday week. It's not like
there was anyone in the office. Fully half of my team wasn't in; the
other half could have gotten on fine without me. Everyone wanted to
talk about their July 4th plans more than they wanted to hear about
yet another IT thing which might or might not affect them in the long
run.
If I possessed any sense whatsoever I
would have talked about the same thing. Instead I pointed at the
elephant not once, not twice, but three times in a row. People will
not thank me for it; more likely one or more of them will want my
head on a platter. Blame, after all, is both easy and fun. Better
yet, the screaming and hair-pulling distracts us from the real
problems.
Every organization has their elephants.
You know them well; those massive problems no one wants to talk
about, ever, under any circumstances. Some elephants lurk in the
middle of meetings but don't make too much trouble so long as
everyone knows where they sit. Others, though, lay in wait and try
to run you over when you least expect it. The elephant in my current
organization is of the later sort.
Now, being new to the organization, I
don't always know when to keep my mouth shut. I'm also inclined to
say what I think and back it up with data, theory, and practical
examples. None of this endears me to those who like their elephant
just the way it is, thank you very much. It also has a tendency to
leave me without any markers, as they get consumed when the elephant
defends itself.
So, the question becomes, what the heck
do I do with the elephant? It's too big for my team to wrestle down.
It's results leave my reactive team members so battered that they
can barely find the time to work on other things. My sole
non-reactive team member, my senior, will not come back from medical
leave for at least three weeks. I do not have the authority or the
power to deal with it personally, though I'm slowly making some
progress on shutting it out of my direct area.
Looking for allies will prove
problematic as well. Elephants come into being for a reason; someone
or multiple someones find them useful. They remain in the
environment because it supports them. They grow and become, well,
elephants though a long combination of neglect, politics, and
influence peddling. All that means the organization as a whole and
the individuals in the organization possess a pretty high level of
commitment to their ?little? pet.
Anyone I turn to for help will likely,
at some point, turn on me. Any ally I build for this effort will
eventually have to cash in their chips rather than go on yet another
elephant hunt. That's assuming I can find someone with the political
will and the influence to even start.
So. I have an elephant crashing though
my network. There's not a thing I can do about it other than apply
the techniques I know and do the best I can to not let things get
completely out of control. My team's completely tied up this week
trying to keep things afloat, so I'll have to figure out how to do
this with a team of influence rather than one of authority or mutual
respect.
On a more positive note, we have taken
another short-term step towards implementing teamed approaches to
problem solving. Right now, I'm acting as the second part of most of
the ?in team? pairs. When we have to reach outside the team,
I've decided to keep my people involved rather than allowing the work
to pass completely out of our hands.
I'll let you know how that turns out.
by w0und3d
I do feel your pain. I work at a Higher Educational institution and we have several elephants that stare you in the face always. One major positive that has been happening is that our executive management has discovered the importance of Governance. Being outside of the USA and being an educational institute we do not have that many critical standards to comply with like SOX, but none the less we have to exercise good governance. Since the executive management adopted a governance framework, and realised that they can be held directly responsible for ignoring risks or not taking reasonable steps to manage risks, it has really helped us (IT Dept). (I am still waiting to use a Risk Acceptance document - they do not want to acknowledge the risk, they must put their name on paper declaring it)
It does not cull all the elephants, but at least they are getting smaller and more manageable. It is difficult to change a culture of any environment and it usually takes about 12 - 24 months, to change a mind set...so all the best, with your elephant(s).
by problemsolversolutionseeker
OK, I cannot resist posting here.
I know several people that are good at laying low, and are quite successful. But it sounds like your personality is similar to mine - some would say you are paranoid, but I prefer to say cognizant, aware.
Focus on your job, be true to yourself! You know, stuff your parents would say.
Build your network! Think bigger than your job - you are building an external network also. Quite often, elephants have very little external networks. When (if) you move on, or when others move on, your network will have grown, minus the elephant(s).
More importantly, they cannot be persuaded to admit to the facts that they don't want to see. They WANT their elephant because they get a sense of importance from pointing out elephants that "no one else can see". What they don't want to see is that everyone else can tell it's really a mouse, not a elephant, because everyone else is seeing ALL the facts, not just a select subset.
So, before you call something an elephant, check and make doubly sure you're not really pointing out a mouse...
Steve G.
by gardoglee
Those darned elephants! First they sit around intimidating most of the room while cozying up to a few close friends, and then one day they turn ugly and stomp all over everything.
Being one of those completely clueless individuals who compulsively points at the elephant du jour, I know the sort of trouble you are reaping. Sure, days, weeks, months or years later when the elephant has finally been eased out of the room, you will have the warm feeling (if you haven't already been fired) of knowing that you helped point out the problem. You'd better enjoy that warm feeling, because by the time the problem has been solved, no one will remember that you were part of the solution. Instead, you will be associated with some vague memory, and most likely blamed as the one who first invited the elephant to come visit.
Jerry Harvey refers to this species as The Abilene Paradox. That doesn't help you evict the elephant, nor to salvage your lost markers, but at least his comical example might give you a laugh. I recommend the video tape. In the meantime, you might consider maintaining and strengthening a fence to keep the elephant in the neighbor's yard while you build a documentation trail of how much elephant feeding is costing. Elephants always go berserk eventually, and come crashing through into plain view where no one can pretend to ignore them. The only thing which will help you at that point is to have a well armored and defensible explanation of why someone else made it impossible for you to solve the problem. Otherwise, that will be the very person or group which will be transforming the elephant into an albatross to hang around your neck.
by prosncons
Call me an elephant huntress who finds a way to crush the elephants one way or another. I welcome chg, as it breeds opportunities to grow. Also, it quickly spotlights the weak and comfort-zone lovers...or 'mouse' lovers...that find stepping outside of the box to be like asking them to jump off a bridge. It quickly clarifies the players and the type of players.
It may sound strange following that comment, but "collaboration" is key. Determine the strong, those like you, and collaborate. Many times with those you are most unlikely to collaborate with, and the best of them are at the mid and top management levels...call it a professional growth experience and a means to get the solid backing to make the best and right things happen.
On another note.....The blessing in disguise....I'll step out on the limb and say thanks be to SOX compliance...why?...Who is going to refuse compliance? In the last org I worked, SOX quickly became my sidearm and it was the best elephant crusher weapon to come my way. Hey, nothing works better to get all the top dogs' attention and cooperation than laying out and weighing the 'pros n cons' .....hmmmm...let's see....get fined mega $$$ and possibly get closed down...or...absorb the cost of equipment, time, and resources to make these chgs that ultimately make our business compliant, stronger, faster, with increased flexibility to grow the business and to evolve and scale systems; thus creating an improved competitive edge,...and, well heck, we finally get the budget increase for IT to become better trained and to upgrade systems to the leading edge technology that will eliminate the ignored elephants currently breeding under our noses...
Last thought on this....if no one with the power to crush the elephants steps up, I would take it as a sign and lesson learned, then begin to look for a new org that thrives on chg, innovation, flexibility, and wants to be in business and lead the market for a long time to come. It's not for everyone, but that is my perspective and experience...a bull in the china shop, if you will.
Good hunting and crushing to you!by jmgarvin
First let me respond to Bluemoonsalior (aka Steve G)
I know several people like you. They seem to positively delight in pointing out elephants. Problem is, they're usually wrong. Oh yes, they do have facts to back them up - but they only see the few facts that support their view of the elephant. They specifically ignore the majority of the facts that clearly show their elephant is really a mouse.
Wow, just wow...Pointing out elephants is usually political suicide. You've just lost any political clout you may have had and even better, you'll gain enemies in the process. Nobody that I know delights in pointing out elephants.
Either you work in a place where you have no elephants (I hightly doubt this), or you try to hide those elephants under a rug and when you get called out, you make it look like a mouse.
More importantly, they cannot be persuaded to admit to the facts that they don't want to see. They WANT their elephant because they get a sense of importance from pointing out elephants that "no one else can see". What they don't want to see is that everyone else can tell it's really a mouse, not a elephant, because everyone else is seeing ALL the facts, not just a select subset.
No one else wants to point it out (usually). The problem with elephant spotting is that (one or all of these becomes true):
A) You get labled a negative nelly, even if you propose a workable, economic, and robust solution
B) You lose political clout for a LONG time.
C) You are the "outcast" that doesn't get told about the real elephants
So, before you call something an elephant, check and make doubly sure you're not really pointing out a mouse...
What a snide comment. You must work in an ivory tower, because the reality is there are usually herds of elephants running around IT shops.
I'm in the same boat with you. I've sat through numerous meetings getting the stink eye because I'd bring up problems (we had a portal deployment and I mentioned that we didn't have enough bandwidth and our DMZ wasn't ready for that kind of traffic...ya...that went well) As for dealing with the elephant. I suggest you clearly define what the elepant is and possible solutions to the elephant. You should also make sure to have your financial ducks in a row, 'cause they are gonna ask. Also make sure your solution is somewhat scalable because that elephant might be bigger than you think. Also be ready to fight for a LONG time. Some managers choose to ignore the elephant because they think it will make them "look bad." The reality is that if it was removed, they'd look better than ever. Try to hedge everything in a positive way and be a salesman.
Good luck!
by jmgarvin
First let me respond to Bluemoonsalior (aka Steve G)
I know several people like you. They seem to positively delight in pointing out elephants. Problem is, they're usually wrong. Oh yes, they do have facts to back them up - but they only see the few facts that support their view of the elephant. They specifically ignore the majority of the facts that clearly show their elephant is really a mouse.
Wow, just wow...Pointing out elephants is usually political suicide. You've just lost any political clout you may have had and even better, you'll gain enemies in the process. Nobody that I know delights in pointing out elephants.
Either you work in a place where you have no elephants (I hightly doubt this), or you try to hide those elephants under a rug and when you get called out, you make it look like a mouse.
More importantly, they cannot be persuaded to admit to the facts that they don't want to see. They WANT their elephant because they get a sense of importance from pointing out elephants that "no one else can see". What they don't want to see is that everyone else can tell it's really a mouse, not a elephant, because everyone else is seeing ALL the facts, not just a select subset.
No one else wants to point it out (usually). The problem with elephant spotting is that (one or all of these becomes true):
A) You get labled a negative nelly, even if you propose a workable, economic, and robust solution
B) You lose political clout for a LONG time.
C) You are the "outcast" that doesn't get told about the real elephants
So, before you call something an elephant, check and make doubly sure you're not really pointing out a mouse...
What a snide comment. You must work in an ivory tower, because the reality is there are usually herds of elephants running around IT shops.
by jsorrells
I got Elephants! Lots of them. I pointed out one herd and just about got my head bit off. Well at least I still have a job. What is my elephant you ask? Generic user accounts like accounting, and you know what makes it really bad the password is the same.
So for the guy who thinks that elephants are mice, you need to do some real soul searching because the idiots I work with think I am nuts for wanting to get rid of about 20 user accounts that are in use by about 600 users and all of them have the same problem, username and password are the same. Now if anyone here says that isn't a problem they are nuckin' futs.
I am soo glad to see this as it makes me feel better about the elephants here.
by abc098
Fortunately most of you are very lucky. I'm just a tiny person in the place I work. Like some of the user who give a comment in here, I work in an education sector in a development country. Academician tends to like elephant. More over, some manager in this country is not like you. They tend to "cover" the elephant with lots of VVIP features so that top-management would see that the elephant is quite useful, though the students who actually paid our salary does not think so. But just like any leader in my country, they often said that the "customer" (aka students) have to learn by difficulty. They have to embraced the elephant as part of their education.
So, what can I do. I'm also like Shannon, like to "shout" my opinion on the elephants in the first few years of me working here. Unfortunately, many people does not like my way of "shouting" or maybe they don't like the elephants to be fix at all so that it would eventually become mouse.
Now I was considered as a monkey, somebody who just keep on shouting. I worked based on fact, not assumption. Just because the elephant was used by big corp such as NASA does not mean it should be compatible with other product in other organization.
So, maybe somebody, Shannon maybe could give me some light on how I can solve this problem. Don't asked me to change their culture. I have tried that for the past 3 years and I can say only 5-10% of them changed. What culture, you may asked. The culture of preventing, the culture of giving the best. It is just on the mouth, but not practical. Why because the top management wanted to see we do our job physically. For them, there is no such thing as solving problem, remotely. You have to come over to the office to fix the problem regardless whether it can be solve remote or not. So what the use of having SSH ? What the use of planning to purchase VPN ? Maybe I should just blocked remote SSH, because there is no use at all.
So, this week I set out on an elephant
hunt. I didn't mean to; it just kind of happened. My team got
beaten up, again, by situations created by the elephant and its
various attendants. I just snapped after watching it happen yet
again. The good news there involves another new manager who decided
to try to go after a different part of the elephant. Between the two
of us, we almost accomplished something. The bad news involves some seriously complicated politics, a handful of potential
new sometimes allies, and a couple of team members who have good
reason to seriously challenge my sanity.
It's that last part that gave me pause.
Team building is a long-term process. Changing the principles by
which a team develops and maintains its approaches takes even longer.
Accomplishing organizational change though suggestion, taking
mentoring moments, and gentle pressure takes bloody near forever.
I am not a patient man. Knowing that
team-building, principle change, and organizational evolution though
influence take time does not make it chafe any less. Nor does it
help when I see things that I could, with a bit more power and a bit
less need to cajole, just change for the better. That frustration
sometimes leaks into my body language when I deal with my coworkers
and various layers above me in the management chain. Unfortunately
it also comes across as slightly erratic behavior to my team.
Sometimes my behavior is erratic. I'm
not perfect; no one is. Sometimes I get distracted. Other times I
get focused on something I should probably let slide down to the
team. Heck, occasionally I'm just addled for the day and do
something boneheaded.
That admitted, though, there is also a
method to my madness. Every group forms behavioral norms. Every
team creates unspoken rules about who will do what work, when, how,
and why. These norms become, over time, accepted to the point where
no one even questions their existence. In effect they become chains
on the team's productivity and ability to deliver service, chains the
people involved with the team cannot see.
One of my first tasks as a would-be
team leader is always to analyze those group norms. More
importantly, I assessed the degree to which each of my team members
had absorbed the less functional norms. The assessment took all of
two weeks; deciding what to do with it took a lot longer. Frankly,
I'm still making up a bit of the ?what to do with it? part up as
I go along.
However, I'm also constantly working
and interacting with my team in ways that operate just outside of the
non-functional norms. Not, I hope, too far outside least I scare
them off. But just far enough that it challenges them to think about
their assumptions, goals, and intentions towards what they think of
as their work.
Let's take a concrete example. I'm
trying to help one of my team members demonstrate his analytical
skills. Some of this help comes in what you would think of as
?typical? analytical assignments: find out why X happens,
discover the root cause of Y. Other bits of it, though, take on a
form he is still grappling with ? seemingly mundane little tasks
which fit into a larger overall scheme. These later tasks seem
pretty frustrating to him, as I seem to drop them off at completely
random intervals. To some extent I do, but there's also a method to
the madness. I want him to stop, think, and assess the overall
picture before just accepting the task. I also want him to start
looking at things in that sideways way that distinguishes a great
analyst from a decent IT guy.
Sometimes the approach backfires;
people do not always like to be challenged. It's hard, sometimes, to
know when to keep pushing people and when to back off. That later
idea rarely sits well with me, as I personally like to push myself as
hard as I can then shove it that last bit to total meltdown.
Fortunately I have friends and an occasional bout of sanity to keep
me alive.
On balance I find this approach works
reasonably well most of the time, though. I don't take it too far
and I try to keep things light. The combination of ignoring norms
and humor, though, does give me a bit of a reputation as a nut-case.
Which is, if you think about it, probably all to the good.
So, one one hand I'm trying to build
strength in my team by making them slowly challenge the way things
were done. On the other I'm every so carefully building up bits and
pieces of alliances to hopefully get an elephant hunt going. On the
gripping hand, I've still got to go chasing down the rabbit holes
left by an incredible number of incidents every day.
Still, I can honestly say its been a
good week. We'll see what next week brings.
by bork blatt
Elephants, territory, and change
Why do people hang on to their beloved elephant so tight? Even when it's obvious that sorting out the elephant would be good for the company?
I work for a company that (among other things IT) does custom software development. I have been involved in enough projects that I have seen some interesting trends. Users are often hostile towards new software. I have seen them try to sabotage an installation by feeding in bizarre data to break the system, then reporting to their supervisors that "the system doesn't work" and it is "garbage".
The elephant in these cases is almost always lots of information "islands". Each department has a different filing system, their own set of little Excel spreadsheets (sometimes Access applications), and their own way of doing things. Senior management want to consolidate all of this into a single system so that information can be shared, workflow monitored, and reporting easily done over most of the business. Why is there so much resistance to solving this problem?
This is so common that I have come to expect it and strategise around it. I believe there are some common stumbling blocks for people when anyone tries to improve a business process, fix an entrenched problem, or cut out something unnecessary.
- Resistance to Change. This is the most obvious and common problem. People (myself included) don't like certain types of change. The more uncertainty caused by the change, the more work required to adapt to the change, the less people will like it. Anything that redefines a well established role for someone is also likely to draw heavy fire. This can be alleviated by good change management - letting people affected by the change participate in decision making, pointing out the benefits of the change for them personally, etc.
- Dislike of monitoring and controls. Anyone who has basically been working (or not so much) without any interference like monitoring, making their own Excel spreadsheets etc, are not going to like a company-wide system that they have to adapt to and potentially be monitored by. They enjoyed the freedom of doing things their own way, even if that meant bad communication with other departments, everyone having their own way of doing things, and difficulties getting information to senior management because of bad information management. There is in my experience little that can be done to get people to warm up to this idea, and only senior management who are committed to implementing the software so the whole company can benefit from having one system, can overcome the hostility from users protecting their "way of life".
- Techno-illiteracy. Many senior staff who have been doing a particular job for years using paper based systems with minimal computer interaction fear computers and don't want to learn how to use them. They will use any excuse to try an prevent the system from being used in their department. Only good, patient trainers can help here, and they will need to be prepared for much abuse and anger until the staff get used to the system and appreciate the benefits. This can take years.
- Fear of losing their job. This is quite a big one. Any time you find an unnecessary process (or one that can be stremlined) and it makes up a large part of someone's work, they will not want it solved for fear that they will become expendable. In short-sighted companies where the mission is to cut costs by reducing staff whenever possible, even if they are valuable and loyal, this fear is very real. However, in a good company, if you can point out to this person that leaving out this process gives them an opportunity to do more meaningful work (maybe even get promoted) they will be much more open to the idea.
Managing any kind of change requires good people skills. I have been in enough corporate environments to know that many times, emplyees' fears are justified, because of short-sighted management. People's fears need to be allayed. You need to show them a vision of the future where they can play a meaningful role. You need to involve them as far as possible in decisions that will affect them and you will gain their trust, and release them to give much of themselves to the company.
Wow. That turned out much longer than I planned.
by kovachevg
PREDICTABILITY
Reading this blog reminded me of when I was young and impulsive, when I couldn't resist writing a line of code just to try something of marginal importance. But somewhere along the way, I changed.
If some of you think that perdictability does not play well with challenging employees to behave like "great analysts", try this for a change. You can introduce predictability even in fairly unpredictable processes. For example, ?f you tell your co-workers that every Friday they will be brainstorming a problem or will be analyzing a challenging business process, by the third week you will notice the reaction and the creative approach that each has chosen to follow.
Then comes the second phase - guidance. Just because everyone invented a way to cope with a situation does not mean the project manager should leave them to their own devices. Spend some time with each of your subordinates, find out how they prepared for this challenge, select the most useful steps and resources and combine them with your expertise and/or research, and finally, make those available to the team.Like it or not, employee respect toward a manager is tied to his helping hand - the hand that helps just enough and does not make you feel like a moron.
How you present best practices is also important. Try to organize them in relevant groups and advance one group at a time. This will avoid information overload and will speed up the uptake. Slightly increase the "voltage" every time.
Remember that your authority should be built on your ability to lead people. In this case, leadership comes through prior knowledge and analysis of a difficult problem. Set an example and watch them follow.
So we just described predictability in an unpredictable context.
Do NOT try to manage idiosyncrasies. Inevitably, there will be deviants but that's OK as long as they accomplish the results you've set forth. You just need your bases covered. If an employee does not realize he or she can perform a task with the efficiency of your methodology, or that of some other optimal approach, let them struggle a bit. They will see for themselves that there are screwdrivers and screws that match them, and until they start to find quickly the magic fit, they will stay late after work.
The author of the blog is quite attached to his job - an endless suffering for everyone who falls in love with a particular activity (Shakespeare comes to mind again). He should know that ingenious solutions are not bound to everyday activities. Nor are such solutions a prerogative for every business analyst. My advice to him is to prime for the decent analysts who are open to embrace other analysts' best practices and tool sets. For most of them greatness will be sure to follow.
Monday came and went. I'm told that's
a good thing.
Our team meeting was bitter-sweet. On
one hand we got to go over everything going on and the activities
immediate ramifications within our environment. On the other, it
underscored my senior resource's need to take extended leave for
medical reasons. I divvied out his work today, something which made
me step sit back a bit. I had counted, even hoped, that he would
have a chance to work on these things.
I don't think it will come as a shock
to anyone that my current team came with baggage. Every team does,
even the ones you build from the ground up. Each individual member
of a team comes with ?baggage?; the group as a whole builds up
even more. Heck, if you pick one person out of a crowd, isolate him
from his support mechanisms, and beat him up with reactive work,
you've pretty much created a whole heaping truckload of baggage on
demand.
The question for me now is, what do I
do with it? Tempting as it might be to say ?suck it up,
buttercup?, that's neither fair nor right. What I just referred to
as baggage represents the accumulated emotion, energy, adaptation,
and hopes of professionals who honestly did the best they could with
what they felt they had to work with.
So, where do we start with the
unloading process? Julius Caesar had it easy. He could dump the
Legion's baggage by the side of the road. I don't have that option.
As a leader I need to help these folks not only hold their legitimate
grievances at bay but also set aside the issues arisen out of their
situation. As a manager I have to establish clear boundaries, unless
I'm violating some crusty bit of history for a reason, and those
boundaries do not always fall where my team would like them to.
Legitimate grievances strike me as the
most difficult part of the equation. It's one thing to sit and
listen to someone vent. It's another to sit and listen to them
rattle on and on about how they would like to do things. When they
complain about things you know are wrong, though, and that you know
inappropriately impact their lives, what do you say? What do you do
when you share their trouble and the sense of powerlessness which
comes with it?
I can offer platitudes. I can listen,
though that rarely helps people in IT. Most of the people worth
hiring are either thinkers or actors; they don't like to sit around
waiting for other people to solve their problems. I can agree with
them and turn them lose, knowing they will fail, knowing that they
know I know they will fail...
I've never found the solutions above
terribly effective, despite the recommendations of managers and
management books alike. The ?solution? involving turning the
problem around doesn't always work well either, since they know we
will not implement the changes they come up with. Or rather, I
should say the changes may not make it very far in the organization;
I'm generally inclined to give just about anything a try.
What I am trying, though, is refocusing
people away from the issues and towards the people, process, and
technology problems endemic to the environment. It's easy to say ?I
can solve this set of incidents by resolving this known issue?.
Heck, it's even true. The question, though, is how do we address the
problem underlying the issue? How do we make it so that each stage
of the situation (incident, issue, and problem) all receive their due
diligence? Who is responsible for each stage, who is responsible for
the oversight, and who makes sure the problem resolutions actually
resolve the problems rather than create more?
This also leads me to another question
? where does my responsibility for helping people unload their
baggage stop? At what point do I have the right, the gall, or the
power to just say ?you know, do your job? and make it stick? AT
what point does playing by the rules of the situation become as much
baggage as anything else?
Ah well. More questions than answers
this time. I'm told that's a normal phase. At some point the
numbing will set in and I'll become a much less worried person.
I'll let you know if I come up with
anything brilliant between now and Friday.
Another week up, another week down.
Sometimes I feel like we're in a nightmarish form of bowling league.
We start the week off with a huge stack of pins; I keep rolling the
ball down the lane. Sometimes I hit. Sometimes I miss. Most of the
time we get about half the pins down before the next rack hits. Now
I've got a forest of pins and not enough room to roll the ball.
Maybe that image got twisted around
itself. Anyway, we had a pretty good week. The team got a lot done.
We pulled off a handful of minor miracles. We built some good
solutions and came up with some testing plans to isolate several
major environmental problems. I also failed to migrate a server due
to a modest networking problem, though I have neither control over
the switches nor the willingness to hack them.
Now, I'm going to reveal something
about my communication style here. We refers to my team. We do
things well, though hardly flawlessly. We work hard, stay mostly
focused, and even have some fun along the way.
I, on the other hand, make a lot of
mistakes. I'm responsible for most of the things which go wrong.
Production network team deleted during a server move. My
responsibility. Backup software not configured properly on the
server. My apologies to Operations for not taking care of it.
Database doesn't install on the standard server image, adding days to
an otherwise simple project. I made an error in judgment somewhere
along the way.
In a team, success belongs to those who
do the work. It's their thoughts and skills which drive
accomplishment. They invest the time, solve the problems, and think
sideways around the incidents to discover the issues and identify the
underlying problems. When a project turns out well, it's because the
team as a whole pitched in to succeed.
They rightly deserve public praise and
support.
In a team, failure belongs to the
leader. I have no control at all, sometimes, but I remain
responsible for the results. It's not that I ignore or reward the
errors; honest errors are addressed and problems of understanding or
training receive due redress. When it comes down to it, though, it's
my job to make sure it gets done right and my failure when it does
not. There's always another person I could have talked to, another
stone I could have asked the team to look under.
This approach represents a variation on
the whole ?praise in public, punish in private? approach most of
us use to one extent or another. However, the ?I/We? statement
splits its focus in terms of what it's trying to accomplish. On one
hand I'm trying to preserve both my team's and the extend team's
face. On the other, I'm trying to condition myself to accept the
responsibility which comes with the authority to set other's
priorities.
Sometimes it works. Sometimes it
doesn't. I'm not always as mature as I would like to be, as wise as
I think I should be, or as strong as I need to be. Such is, I guess,
life.
Anyway. Another week down. I'll post
more on Monday after I get my bearings.
by a.mahdi
I am a firm believer of blaming self first. One has to bear the responsibility when in a leader position. But depending on the circumstances this may not always hold true. One can not expect too much from the PM when there is no infrastructure to support the project. You work with what you've got. I think it is wiser to look for the root cause of the problems rather than accepting the blame for all the problems readily.
Ali
I agree wholeheartedly with Ali. His response is excellent.
Your understanding of the role of the Team Leader is also excellent. Perhaps additional "root cause" training would help you, too. Perhaps your team could benefit from an occasional "team building" exercise. Only you can make this call.
by the old man
Could not have said it Better!
Have you ever had one of those
conversations where you wanted to take someone by the ears, turn them
around, point them at the smoking wreckage they call an
infrastructure, and say ?LOOK, for crying out loud?? Have you
ever done it, had them look you dead in the eye, and say ?But it's
working other places, so all this theory is pointless??
A few years ago I wrote an article
about how people never fail in IT. We can always redefine what it
means to succeed so that everyone looks good. It's part of the charm
of what we do; metrics for success change so easily. A few words
here, a handshake there, and the greatest disasters get recorded as
shining successes. The nightmares of support, the exhausted staff,
and the over funded, under trained and performing departments just
get overlooked.
At some point the pain gets good to
people. They start to like it. As I mentioned in my blog on trying
to hunt the elephant in the room no one will talk about, the way
things are serve many purposes. In my immediate case it means I do
not have to do much to get by. Just take my licks, do as I'm ordered
even when it's wrong, and collect a paycheck. Every once in a while
one of the Powers that Be will throw me a bone to prove they want an
architecture.
Business also seems to thrive, despite
our mishaps and trials. They get their jobs done around outages,
horrid response times, and occasional outright stupidity on our parts
leading to major events crashing out multiple sites. They accept, or
at least pay for, an organization exhausted past the point of even
analyzing the incoming data to stop the pain.
The magic of redefining success is at
work here. We've defined success as either surviving another day or
getting a system up, and damn whatever happens to the support
afterwards. Its wrong. It's nearly impossible to keep up for any
length of time. It allows people to display their talents and skills
as they keep the place running and it definitely lets people show
just how hard they work for the money they make. Whether we work
anything like smart rather than hard doesn't really matter at the end
of the day, it seems.
I've mentioned many times that pride is
my downfall. I'm a proud man, driven by both a desire to excel and a
determination to serve. I push myself constantly in work, in play,
and in life. I push my teams to excel, to think sideways, to grapple
with the twin snakes that climb into their cradle and throttle them
before lunch. Ahem...
The point is that I have trouble just
sitting back, even when the environment defines success as just doing
what we are told. I know what environments where you do it right
look like. I know what happens when people know how things work, why
they work, and why they break. I have, many times, tasted the
satisfaction of creating and maintaining dial-tone IT, watched it
reduce staffing levels, held the tactical pieces to enable strategic
agility, and felt the quiet pride of a job well done but unknown.
Frankly, I like those experiences better than the constant struggle,
the sudden discovery of failure in ?turn-key? systems, and the
chaos surrounding things you just shove in without any understanding
of either their architecture or how they fit into the bigger
technical picture.
So, I've set my team to doing what's
right. We'll get in trouble for it, I'm sure. The people who assure
me in one meeting they will support ?doing it right? will
double-cross me in another in the name of expedience. That's just
business. So long as my team keeps moving methodically forward,
stabilizing one little bit of it at a time, I'll go forth and do my
little bit.
Heck, maybe at some point I can show
the customers they really can expect more. If that happens, though,
the definition of success will change...and that will put me back
squarely in the sights of those who profit from the current
environment.
Onward and upward. The team has a lot
of clean-up work to do. Hopefully we can get it done before another
distraction shows up on the horizon.
by gardoglee
I know a business analyst who once told me what they use for a definition of 'hitting bottom' in drug abuse therapy. He said you don't hit bottom until things are getting worse faster than you can redefine what is the worst you can tolerate. When you start out, you think that the worst is something like spending money on drugs which you should be using to pay the mortgage. Later, it is when you ahve no money at all. Still later, it is when you vow you will never actually steal money for drugs. At some point you get to the real bottom. hopefully, it is before you discover the real bottom is death.
The sort of accomodation of pragmatic reality which you describe is a less tragic example of the same sort of adaptation. The signposts we pass along the way on our trip down include refusing to ever cover up an unpleasant truth, refusing to lie to a supervisor or customer, refusing to send along a piece of work we know is defective, or refusing to blame an innocent party to get out from under the blame. We each do have our real limit of what is intolerable, but it is a very rare person who sticks by the idealistic definition they had when they started their career. Unfortunately, that sort of firmly prinicpled person who we would like to see rise to the top of the organization tends instead to end up unemployed.
You are certainly right that you will get in trouble for trying to do what is right. I wish you luck in surviving long enough to accomplish some right, and thoroughly respect you for your efforts. I haven't yet become cynical enough to simply think you are a fool to even try, although I work with a lot of good people who have been beaten down that far. Keep up the good work, and good luck.
by not_it_john
I sympathize with your situation, and hope you're successful in your attempts to do what's right. I have one problem with your article. "The people who assure
me in one meeting they will support ?doing it right? will
double-cross me in another in the name of expedience. That's just
business." It's not business; it's lying, and backstabbing, and hypocrisy. These things might be a part of some businesses, but they're not "business."
I used to work in a huge telco, where that sort of thing was commonplace. One day a new, straight-out-of-college manager told me about some new scummy "something" that was happening. I said, "Angie, get out of this company. You've only been here a few months; go to work somewhere else, where they don't do things like that." She just smiled and said, "All businesses are like that."
Businesses are like that only because so many people are willing to say, "That's just business." I'm not suggesting you openly rebel, although it sounds like you're sort of doing that anyway. I'm just saying, don't accept it. Do what you have to do to survive, but if you accept the idea that business is about screwing somebody else, then it's only a matter of time before you're one of them.
Good luck.
Last Friday's entry will come late. In
fact, it will show up on Wednesday. Sorry about that; I ended up
flying to Colorado, working on my house out there, then driving back.
Something about all that took the wind out of
my sails. Still, it's a good entry containing juicy stuff about dealing with the demons of the past and other
dramatic statements.
Fortunately this Monday passed with a
lot less drama than last week. At least, it passed with less surface
sound and fury. The actual impact of today's decisions, especially
if we carry them forward, promise to be profound. Like all profound
things, though, they take a bit of getting used to. Some people
might not even notice them at first, but will instead sense a change
of pace they do not quite comprehend.
Yesterday, you see, we let go of a dream.
Our leader had the wisdom to, subtly, point the way to another
possible dream, but I doubt it will make much difference at first.
It never really does.
I make no apologies for both leading
and acting as a member of highly technical teams. As such, our
professional dreams tend to focus on implementing particular
solutions chosen from the ?solution wheel? to address
architectural functions or business problems. Given my own
background I find the architectural bits far more exciting than
dreary business logic, though I can see the appeal of helping people
resolve their work related issues.
The dream we let go of was no
exception. It was, in fact, a very sexy solution to the rather dirty
business of getting access to client business logic in a health care
environment. Fighting with old applications, shoddy code, and
?standard? equipment that fell out of the manufacturing cycle
years ago doesn't always lend itself to technically sexy solutions.
When one comes along, its easy to fall in love with it. And fall
hard for this one we did, though pain and travail the likes of which
only a dreamer could love.
Unfortunately, that travail proved the
dream's downfall. It's one thing to champion a technology which only
beats up our own group. We can take a little pain, or even a lot for
a short period of time, to bring an important new technology into the
environment. It's another entirely to deal pain to the rest of the
organization with limited or no return and very little end in sight.
This becomes especially true when we fight incident after incident,
resolve issue after issue, without solving the fundamental problems
the dream introduces.
So, it falls onto the leader's
shoulders to finally make a decision. When do we draw the line?
When do we stop supporting something we want so badly we can taste
it? When do we spin the wheel of solutions again to find a better
resolution to whichever architectural function we need to address
this quarter?
You have to start with data.
Information about the number of incidents is a start but hardly tells
you the story. You have to dig into it, discover which issues fueled
those incidents, how quickly we could produce know issue statements
and work around, and finally how those issues tracked back to
fundamental problems. How much of our work was self-inflicted ?
i.e. The result of our efforts to support the solution rather than
address the architectural function? How much of our clients' time
and the business logic side of the house's resources did we waste
trying to keep our chose solution up?
From there, its time to set some
metrics and make the unpopular calls. How much is too much? How
much pain do you inflict? Given what we do for other teams, its
reasonable to expect the business logic groups to help us out but
when does it shift from asking for support to throwing them under the
bus in the name of our goals? All architectural changes involve a
good bit of pain and suffering though problems, but when do you
decide it's one step forward and two steps back?
Finally, and least popularly, when do
you re-prioritize the effort? When do you decide the resources,
time, and energy expended were all for nothing? How do you convince
others, especially those who bled to make the dream a reality, that
its time to move on?
That last question keeps me up at night
sometimes. Data isn't sufficient; being right does not make the
emotional and financial commitments go away. It doesn't resolve the
political issues created by supporting a solution you ultimately had
to abandon, or the sense of frustration from the allied teams as they
watch their time investments slip away.
It's a tough call. I wish I could have
eased the way to making it.
We'll just have to see what happens
next.
Last week was a good week. We got a lot done. We stabilized a system that was causing major problems. We identified and addressed some key problems, which will in turn slowly ramp down the incidents we face on a daily basis. We also got our rear-ends kicked by a hack in a server we didn't know about. It took us two days to bring a critical system back into a stable configuration because someone five years ago came up with a clever work around and didn't bother to tell anyone.
I have a confession to make. I hate hacks. I hate the little tricks people pull with software to ?get it to run properly?. I've used them, worked them out myself, even looked the other way when, in a crunch, my teams deployed a system held together by them. But I still hate them with a burning passion.
It's not that I don't appreciate a good solution to a puzzle. Honestly, I like the little thrill in my heart when I come up with a sneaky way around something stupid software does. I enjoy seeing the servers go up, providing stable service to my customers. I like finding the answer. Heck, I like seeing other people find the answer and letting them prove just how smart they are.
Those thrills and the status we gain from proving our intelligence do not match the price we pay later on, though. Information technology management isn't about what happens today. Not really. Other than a handful of situations, today is mostly ancient history. We have to keep our eyes focused on what happens one, three, and five years down the road. What happens to that cool little hack when we apply a patch that breaks it? What happens when we move on, leaving behind an environment running on hundreds of little things no one knows about? What happens when one of our systems breaks and we are laying in a hospital bed, watching the pretty pink elephants and hitting the morphine button?
Every hack, every undocumented tweak to make the system keep running, becomes a liability later on. The right way to do things often takes a lot longer than the short cut. It's dull and plodding compared to the light-footed approach of ?just get it working?. Frankly, I find it constraining at times myself, especially when I'm in a huge crunch to get something done.
The challenge as a manager comes in when I try to work out when, where, and how much to interfere. There exists a fine line between trying to get things done the right way and obstructing the team's progress in dealing with known or unknown issues. When people get into a groove they really don't want to stop. When the fire's coming down, goals must be met, and the ?world will end if we don't get it done today?, then pesky things like documentation and planning go out the window. We make it work. That's what we do.
I also know once I implement something the odds turn against my bothering to document it. It's not, despite what some people say, a mental defect. Like most of the people I've met in infrastructure work, I like solving problems. I move on once I solve a problem. Heck, in two weeks I might not even remember how I solved it. Goodness knows, there's enough new problems to keep me busy; even if I remember I will not take the time to document.
So..when to push and when to not? For me it depends the individual involved and the work. I don't push for documentation about the creative problemsolving process itself, though I like documentation about the end results. Any time we get involved with communicating with outside groups, though, I work with the technician to get good, effective communication out into the field. When we get involved with various director and executive levels I try to get my managers and executives involved; it's their job, after all.
I'll let you know on Friday how this week turned out. It's gotten interesting, what with most of the team out sick.
Last week was a good week. We got a lot done. We stabilized a system that was causing major problems. We identified and addressed some key problems, which will in turn slowly ramp down the incidents we face on a daily basis. We also got our rear-ends kicked by a hack in a server we didn't know about. It took us two days to bring a critical system back into a stable configuration because someone five years ago came up with a clever work around and didn't bother to tell anyone.
I have a confession to make. I hate hacks. I hate the little tricks people pull with software to ?get it to run properly?. I've used them, worked them out myself, even looked the other way when, in a crunch, my teams deployed a system held together by them. But I still hate them with a burning passion.
It's not that I don't appreciate a good solution to a puzzle. Honestly, I like the little thrill in my heart when I come up with a sneaky way around something stupid software does. I enjoy seeing the servers go up, providing stable service to my customers. I like finding the answer. Heck, I like seeing other people find the answer and letting them prove just how smart they are.
Those thrills and the status we gain from proving our intelligence do not match the price we pay later on, though. Information technology management isn't about what happens today. Not really. Other than a handful of situations, today is mostly ancient history. We have to keep our eyes focused on what happens one, three, and five years down the road. What happens to that cool little hack when we apply a patch that breaks it? What happens when we move on, leaving behind an environment running on hundreds of little things no one knows about? What happens when one of our systems breaks and we are laying in a hospital bed, watching the pretty pink elephants and hitting the morphine button?
Every hack, every undocumented tweak to make the system keep running, becomes a liability later on. The right way to do things often takes a lot longer than the short cut. It's dull and plodding compared to the light-footed approach of ?just get it working?. Frankly, I find it constraining at times myself, especially when I'm in a huge crunch to get something done.
The challenge as a manager comes in when I try to work out when, where, and how much to interfere. There exists a fine line between trying to get things done the right way and obstructing the team's progress in dealing with known or unknown issues. When people get into a groove they really don't want to stop. When the fire's coming down, goals must be met, and the ?world will end if we don't get it done today?, then pesky things like documentation and planning go out the window. We make it work. That's what we do.
I also know once I implement something the odds turn against my bothering to document it. It's not, despite what some people say, a mental defect. Like most of the people I've met in infrastructure work, I like solving problems. I move on once I solve a problem. Heck, in two weeks I might not even remember how I solved it. Goodness knows, there's enough new problems to keep me busy; even if I remember I will not take the time to document.
So..when to push and when to not? For me it depends the individual involved and the work. I don't push for documentation about the creative problem solving process itself, though I like documentation about the end results. Any time we get involved with communicating with outside groups, though, I work with the technician to get good, effective communication out into the field. When we get involved with various director and executive levels I try to get my managers and executives involved; it's their job, after all.
I'll let you know on Friday how this week turned out. It's gotten interesting, what with most of the team out sick.
If you have a chance to participate in
HPs ITIL simulation, take it. If you do not see one in your near
future, find a reason to schedule one. It's great fun. A complete
and total bloodbath at first, of course, but still great fun.
At first glance the whole idea seems
pretty goofy. You and a group of your closest work acquaintances
organize yourselves into a system support team for a Formula 1 racing
team. You try to keep the IT systems running over a 25 minute race,
passing information and solving problems as quickly as possible.
When a system goes down the affected cars lose speed; the slower your
cars go the less money your team earns at the end of the race. A
ticking counter shows you just how much money you will earn if the
race were to end at that moment. Your race team also scores points;
if you win the most points over five races you claim the championship
(and the adulation of children everywhere).
The first race is pretty much a blood
bath. People assume their familiar roles, doing what they always do.
Your organizations failings stand out in sharp relief, especially
every little turf battle or bit of chaotic interaction. Oh, and
concepts like priority, urgency, impact, and even just basic
information sharing go straight out the window. No one has any idea
what's going on, and it's all good fun.
After that you get to step back and
assess how you did. It starts out pretty ugly, naturally; no one
really understood what we were trying to accomplish. Everyone held
onto information they had, not out of any negative designs but simply
because it never occurred to them others would care. Meanwhile we
all complained about the problem solving team, who never seemed to
get anything done. Mind you, I was ON the problem solving team and I
agreed with the assessment. Of course, I also knew half the time we
couldn't figure out what to work on, let alone if there were any
problems for us to address.
Over the next few races they introduce
ITIL concepts. If you do not know ITIL, it's a good chance to get an
overview. If you do know ITIL, it's a fun recap of stuff you already
know, with a chance to show people how these things work without
having to change your entire organization. By the end of the
simulation you should have a humming, information passing machine
churning out solutions at a rapid rate.
I suspect it really shocks folks to
discover how much people infrastructure it takes to support just a
few problem solvers. We tend to think of all IT people as ?problem
solvers?, each with our own areas of expertise and skill. The
reality is, though, that a mass of problem solvers attacking things
independantly cannot generate anywhere near the output of a small
group supported by a people and process architecture prioritizing
their activities, feeding them the right information, and keeping
everyone else off their backs while they do their jobs.
The converse is also true. It takes
relatively few problem solvers, technical folks, and architects to
support even a complex organization plagued by real-time faults if
you communicate clearly, have adequate status tracking, and some
means of deciding when you need help. That first part, though, takes
a lot out of most people.
Anyway. Take the ITIL Simulation. If
nothing else, it will show you exactly how people think...always a
good thing to know as you prepare for the next wave of business
conflicts.
by charlie
Thanks,
Charlie
by pak-rat
BMC has an excellent as well. If you can get your key IT leaders and Non IT Business leaders in the sessions so much can be learned that will support future ITIL efforts.
Have you ever gotten to the end of a
month and not known what you accomplished? I'm not referring to all
the tasks which came and went; my pile of those looks as large as
anyone's. Instead I'm considering what, if anything, really changed
because of all my efforts? What principles did I realize in my
actions; which things will we remember ten years from now?
That last one hurts when I think about
it in terms of IT. Ten years ago CD jukeboxes were the wave of the
future. Ten years ago I put in servers which, if anyone even
remembers them, will now get the title of ?junk?. Never mind
they served up more mail, faster, than the honking huge servers we
use now days; the past rots quickly in our profession.
I sometimes wonder if disconnection
from our past feeds the present chaos. We have very little to anchor
us; few standards of long standing, little in the way of a business
culture beyond the cult of intelligence, and almost no real
appreciation for the long cycles of life and business which sweep us
along. It makes us frantic to prove something, anything, right now
rather than holding back, holding on, and waiting for the right
moment to move.
The cult of intelligence provides us
all with a lot of ego boosts but does little to stabilize our
relationships or point us towards priorities generating lasting and
worthwhile effects. My own month is littered with cases in point;
I've solved dozens of little problems over the last month, some of
them quite intricate. They scored me a fair number of points in the
geek hierarchy but none of them matter in the long run. Someone else
could have solved them, probably just as fast or faster. More
importantly they didn't make the environment better, just restored
the status quo.
Looking at the status quo gives me my
best insight into what I did, or did not, accomplish this month. My
team continues to do well despite my whining. We have some long term
issues to work out, but after six months the foundation of a
functional team occasionally emerges from the chaos. We still don't
always click properly, but I actually caught them sharing work and
ideas the other day. It's a trend we will continue though
problem-solving teams, task sharing, and hopefully some architectural
training here ?real soon now?.
We have also made some very modest
progress on the architecture. I introduced basic priority based
design about two months ago; we just went though our first design
phase using it. I don't think anyone understood the words coming out
of my mouth, or knew what the impact of the choices they made would
be, but at least we tried. It may catch on; it may not. We'll just
have to keep working on it.
Meanwhile, I ?lost? two team
members last week to an ad hoc task-force dedicated to eliminating
one of my most pressing problems. They addressed the root cause of
roughly half the incidents filling my team's queue. We'll see if
their changes really overcame the problem. If they did, we will
implement them house-wide. Now that would mark a major change for us
all. Something else will rise up to fill the void, naturally, but
such things happen in IT. We'll burn that bridge when we get to it.
So, a good month or a bad month? I'll
have to think about it in ten years.
I suspect it comes as no surprise to
anyone that my team did pretty much everything I hoped for this week.
Some people tell me that's because I have low expectations. As a
general rule, though, I suspect it's more because I tell them what I
want and stay out of their way while they do what needs doing. It's
an odd concept for some folks but it works for me.
Their focus on what needs doing gave me
time to think about some other things. Like, for example, when did
naked aggression and even borderline assault become normal business
practices? When did we all appear, collectively, to say ?You know,
it's ok for us to behave in a way which would make our third grade
teachers give us a swift swat in the pants??
I do not want to bemoan the loss of
some mythical golden age of business when men wore nice suits and
spoke politely; women dressed well, and children ate their broccoli
without complaint. Nor am I claiming to not participate; I act as
badly as everyone else at times. Yet, stepping back, what can I do
as a leader and what should I do as a recipient and participant in
the problem to effect a solution?
First I have to define my terms. What
I'm talking about here breaks down into two parts. One one level we
have a lot of attempts at social intimidation: displays of power over
others, threats, outright rudeness, and more logical fallacies than I
can shake a stick out. On another level we have raw animal
aggression: shouting, violation of personal space, staring contests,
and behavior best referred to by its old name of ?looming?,
though I think current fashion tends to call it presence.
Personally I give people the benefit of
the doubt when it comes to physical aggression. People generally
don't realize how close they stand, how loudly they shout, and when
they engage in staring contests. When the adrenalin gets pumping,
which it sometimes does in meetings or discussions, many people lose
control of their physical presence. Those who don't generally get
promoted to leadership positions, but that's a whole different story.
It's only after repeated, blatant examples that I start to suspect
the person honestly intends to bully me.
Social intimidation requires very
careful consideration before I give it a pass, though. I'm
absolutely certain some people do it unconsciously. For most people,
though, it takes a lot of work to arrange and seize the circumstances
allowing for social intimidation, so I tend to believe these
behaviors stem from adaptation to the environment. Somewhere,
somehow, a leader allowed these behaviors to take root and flourish.
He allowed them to succeed, knowing they were short term approaches
incapable of producing either lasting change or lasting affect.
Understanding the problem, though,
doesn't necessarily get me any closer to a solution. I cannot
control the behavior of others. As amusing as it might be in the
movies, I honestly don't think I would want to. I have enough
problems dealing with my responsibility for my own actions and those
of my team; I don't think I could deal with controlling others for
any length of time.
Anyway. Response is, always, divided
into two parts as well. In the first part you deal expressly with
tactics, or how you deal with the immediate situation. In the second
you deal with strategy, or how you intend to resolve the
circumstances so the situation never occurs in the first place. Any
response containing just one element will inevitably fail in the long
run.
Strategically I'm focused on making the
behaviors irrelevant. Not punishing them, or making them costly, but
completely irrelevant to the circumstances in which we work. Once
the behavior becomes something outside of the system, rather than a
part of it, it will either cease or the individuals engaged in it
will find another place where they can lord it over everyone.
Tactically I focus on stillness. This
doesn't come as a surprise to anyone who knows me. I choose to not
react, refocus the confrontation on the business at hand, or simply
walk away. I suspect others see that later as submitting or a sign
of submission. Really, though, I'm more focused on getting what
needs doing done than I am on playing games with other people's
emotions and their lives. If walking away defuses the situation and
allows work to get done I'll do it, happily. My ego and my
masculinity source in things other than my workplace dominance.
Much to ponder there is. Think about
it over the week, I will.
by abdul.jussab
So to cut a very long story short....when you are confronted you ignore it and think of ways to make people avoid confronting you again, except you have described it as strategy and tactics and tried to sound philosophical about it....goood effort!
by ladyv21st
Lay out ways to deal with aggression is one thing, public awareness of civic standard reaching the grass roots, not only among the middle class- is the most quintessential task to strenghten America democracy while aligning world democracy. Individual self-fulfillment (not self centerness), the reevaluation of traditions, etc... For example, the enrooted the fittest survivor concept is twisted when we see in daily life bullies then lies afterward, office loyalty put in wrong place and forego the truth... Just a penny thought, thanks for tacking the itchy thorny topic. Lady V
by bee jay
Excellent topic. I'm often stunned by stories I hear of workplace antics and even more stunned by what people are willing to let slide. I think your post does an excellent job at reminding people to remain calm when such situations arise and not get dragged down. I would add being forthright and honest when communication gets difficult. People can argue all they want, but they cannot argue with simple truth, it's a great way to avoid continued bickering. Lastly before walking away from someone who is behaving like a 3 year old, I would let them know that I am walking away because their behavior is unacceptable and am willing to revisit the discussion once they've composed themselves. Letting a coworker humiliate themselves is almost as bad as being the target of their humiliation.
by peteru136
Understand the sitution by changing the context... perhaps an encounter in the street or a non-physical instance of road-rage. Aggression in the workplace is just as serious. The workplace is not outside any laws or customs... so in the UK, for example, it's very easy for an aggressive colleague to cross the boundary of legality and commit an offence of 'threatening words and behaviour' - a form of assault. You wouldn' stand for this on the street, and neither should anyone in the workplace. After all, we're only talking about work...
by sjohnson175
My word! In 10 years I can't recally seeing anything I would consider physically aggressive in the workplace. Biting comments, sure but nothing like what the author describes.
Perhaps it's because I'm in the South and we just don't do things that way down here.
by justin james
"Perhaps it's because I'm in the South and we just don't do things that way down here."
Ahh, nothing like people who bought into that "Southern manners" lie. I have worked in New York City & New Jersey, and I have worked in the South. People in the South are far more aggessive than people in the Northeast. I have had co-workers stretch back to punch me, watched co-workers get into fistfights (while still on a call!), watch people in the workplace get so close to someone that the other person backpedalled until they hit a wall, and still could not get any space. Are people in the Northeast "rude"? Sure. They tell you what they think and talk like a DeNiro film. But at least you know where they stand. Around here, they smile in your face and buy you lunch while putting the knife in your back.
But that is neither here nor there.
The laws that a previous poster mentioned are not unique to the UK. Even in the United States, the moment I make a threatening gesture such as pulling a fist back to hit someone, I have commited "assault." If my fist actually hits that person, the charge has now been elevated again. It is not that there are no laws against this kind of behavior, it is that it is tolerated at the workforce. I am baffled why, especially in the currently weak employment ecology, any employer would bother having an employee around who physically intimidates their co-workers. It is not like there are not a dozen people lining up for good jobs at the moment.
Another concern I would have, if there is a lot of threatening behaviors at a workplace, how many people are coming into work under the influence or have substance abuse problems? It is quite well known that substance abuse (as well as being under the influence) can cause aggressive behavior. People talk way too loud, practically shouting? Maybe they're stoned or drunk. Are people being very aggressive, eager to challenge anyone and everyone to a boxing match? Could be any number of things. If I was in a workplace with a lot of highly aggressive people who were turning minor disagreements into complete chaos, with threatening and/or aggressive behavior, I would definitely be checking out the substance abuse angle. Sure, "hey Jim, you know, you act a bit crazy sometimes. You don't mind if I ask you a few questions about your methamphetimine habit, do you?" may not go over too well. But you mind want to learn a bit more about the signs of possible use and invetigate.
J.Ja
by devans00
by gilsbugs
If you think about it, this aggression, need to control coincides with the me generation. I'm not implying that a one specific generation is actually to blame but rather a general timeline when this attitude began to surface. The media, ad agencies and even the army, feed this to an impressionable group and they swallowed the hook. "An Army of ONE", how many times have you seen that displayed along with a couple for a clothing ad with the female/male with a look of indeference. Quietly manipulate the public but in this case it has turned a rather large number of people into loud arguementative group, just like you would find in many sitcoms. The wife yealling at the husband, the mother yealling at the sun and the grandparents at each other, apply it to any sitcom.
I guess, we'll have to wait until sitcoms, become more civil to teach the easily molded public into "nice people"..............
by mckeerfd
I think you might have noticed a general trend in buiziness as a whole , the sad truth is that management is becoming more and more beligerant , with many employment laws either vauge or weak , and or just plainly written up so thaat an employer has a very unfair advantage , many take clear advantage of the situation and develope delusions of god-hood.
The truth is there are very few choices we have in the work place as to how to deal with this type of behaviour on the part of employers they are as I see it the following:
1.File a law suite (if the situation warrants and provided you can afford to do so.) many of us simply cannot afford the expense so they get away with it.
2.Quit your job with the employer... preferably with out notice , because after all it's a way to punish bad employment practices ,I belive if more of us did this they might get the point sooner or later. I might remind you to find another job first though.
3.File a greivance with your Union if you have one, it's possible you might resolve the situation that way.
4. write your congressman , or woman if they have a good track record in the area of employment relations , sadly i dont put much hope in them after all they are in the pockets of big buizness in a major way...... dont belive that? look around you.
by freebear
Well, work place aggression is surely everywhere, but I do not think it is just the workplace. It is in the grocery store, in Walmart and yes, on the highway. You, I think, have chosen to deal with it in a way that may actually work. I am positive your employees appreciate it once they really see what you are trying to do. Hell, I appreciate it!
Having been the victim of assault because I pulled out into traffic - the fellow actually followed me into a gas station parking lot! I have a theory about societal aggression in the States. As the local, state, and Federal authorities regulate more and more aspects of our lives, what we control is very little. You cannot even move into a nice neigborhood without having all kinds of covenants on how and what you can do with your property. While I realize the very good reasons for such, I am beginning to see the pile of rules I have to deal with in my life as a burden that is no longer worth what I supposedly get for it...an orderly society.
The aggression you see is nothing more than a reaction to less and less control of our daily lives. Also, I can think of no more aggressive act than an executive who seeks to outsource the jobs of people who are working to support their families. The executive thinks he is being clever...the employee sees it as an attack on his ability to feed his children by someone who has all the things he would like to have and is just greedy. Well, says the exec,business is business! I am pretty sure the insurgents in any country who are fighting because they have not been able to feed their families would say, Hey, it is just business.
Take Walmart for example. Anyone who has seen the pattern Walmart used to go into a county knows they either read the Art of War or Sam knew its principals instinctively. Either way, Walmart has kicked retail ass. Problem is, Walmart practically GUTS the local economy. The poor and lower middle class cannot resist the lower prices and it squeezes out what used to be called the merchant class. Sure, it is nice for the poor to save money this week on groceries but is is not helping them for the long haul nor it is good for the local economy because, regardless of Walmart's PR, the profits are not fed back into the local economy.
Some of you may think that I have gotten way off track with this post. I invite you to think about it at length. American society is imploding with a loss of faith that ihave been unable to find precedent for. Aggression in the workplace is simply a symptom.
by lesliedelia
I've worked for some incredibly arrogant, hostile folks - all executives. I've been told that I can diffuse situations well, which I suppose is a good skill to possess. Experience has been a good teacher - I now know to ask during interviews if a company has a policy against a hostile work environment. I also don't hesitate to be someone else's champion when I see aggression. You can say anything you need to say, if you say it the right way.
by lesliedelia
I've worked for some incredibly arrogant, hostile folks - all executives. I've been told that I can diffuse situations well, which I suppose is a good skill to possess. Experience has been a good teacher - I now know to ask during interviews if a company has a policy against a hostile work environment. I also don't hesitate to be someone else's champion when I see aggression. You can say anything you need to say, if you say it the right way.
by mnpundit
ummm, it seems like you have a hard time communicating with people. i'm glad you balance a weakness with a good default behavior.
personally, I enjoy being t technical lead and I enjoy going out, finding possible solutions and then passing the "best hopes" to team members to work out the details.
honestly, I don't think it's a bad thing to "stay in the way" as long as you are technically competent to do so.
such behavior is part of software development models such as the "water fall" model and, as far as I'm concerned, a good way to test understanding of requirements and suitability of work.
if workers get upset about this sort of management, I just tell them things like "this is part of testing" and things work out.
the problem is that, if you cast such behavior in a negative light, you can't use it to get things done.
change your attitude towards the behavior and, more than likely, you can use it to get things done.
by mnpundit
"change your attitude towards the behavior and, more than likely, you can use it to get things done."
an example of this might be when I was a student teacher. those who had trouble with math often had behavior problems.
I typically had three options:
1) "walk away" and let the student fall through the cracks;
2) send the kid to be disciplined-- kid gets further behind and behavior gets worse;
3) figure out how to help the kid help themself.
only step "3" provided "long term benefits." however, analyzing weaknesses and providing paths to success is difficult when you have 175 students a day!
if I chose your path, I would simply pass problems on to someone else. in the business world, that means, perhaps, becoming uncompetitive.
by ctos
I would like to point out one other item that I know is missing: Internal Customer Relations. I am having and issue with a customer, mainly the fill-in secretary, who took it upon herself to make decisions on my abilities and making sure I am paid. She doesnt seem to know or understand the fact that I am also "a customer" for the large company she is working for. She is playing the bully game, guilt game, and the turn the focus on my services/supply.
I think anyone that has this sort of "personality" or lack of "rules" should be reported and made to attend Customer Relations courses. Then put what they hear into play in their workplace performance, or shown the door.
Over time, I have been bullied/abused/used by family, friends, bosses, co-workers and supervisors to name a few. And not one of them ever heard or cared about Internal Customers/Relations. Not one cared that what they were doing was a behaviour problem; not one cared how they made me feel. They just did it and it was considered okay in their eyes. No one stood up to them, no one took the time to say no... I think it is time for us to start saying NO, sending them for training (or else) to get their behaviours back "in order". Why should all of us "nice People types" have to allow or stand for this unexceptable behaviour? We dont. Sandra
by eleanor
People are aggressive because the behavior is usually rewarded. Remember the "squeaky wheel gets the grease?" Most people, when confronted with aggression, either back down or cave in, because the alternative is to escalate. It takes courage to face down a red-faced screaming man (who is usually larger) spitting in your face. Most of the time it isn't worth it.
by mindilator9
by wilkelley7
These are games I play.
Simply stepping in close enough to voilate the personal space of your opponent is a low level or body language form of intimidation. If your opponent steps back or away from you, you have achieved the advantage. Not a word ever needs to be spoken.
Ever come up to a service counter and have the service person ignore you? Start looking over the counter and pick up the first thing you see pen or pencil doesn't matter you'll get thier attention.
Too many words. Could have finished shorter. Well, in my opinion, you have to expect this as the industry follows such an agressive trend (until the breakpoint of course).
Relax until then. Bye.
by rl boston
Are employees who possess some shred of professionalism, not to mention maturity, so difficult to find you feel you must tolerate this behavior? If you have no alternative but to deal with the situation perhaps you could ask a third grade teacher how they handle their students?
I am currently looking for employment and I am aware of appropriate behavior in the workplace. Do you think this might harm my prospects?
Monday came. Monday went. My team's
back up to two people this week, though they both have other
priorities at the moment. Which is, oddly enough, okay with me; I
agreed to reassign their time since the problem they now get to to
address caused the vast majority of our support calls. The team
might as well get a chance to do something about it, rather than just
let it beat them up.
In order to maximize our throughput,
though, I have to get organized. So I spent a goodly portion of last
week rebuilding our activity calendar, a six to eight week critical
path style document outlining what's going on, who needs to do what,
and when we want it completed (or at least mostly closed down). It
gives my team a good overview of what's coming up, lets me keep
things on track, and even helps the teams which interface with mine
understand what, and where, my priorities are. It's not a straight
jacket, though, just a snapshot of what we think will happen.
It occurred to me, though, that I might
want to check our actual throughput against my plans. So I pulled up
the last four activity calendars and compared what we've done against
what we accomplished. The first one had more activities than you
could shake a stick at. It was jam packed with action oriented
phrases, stretch goals, and more than a few idle pipe-dreams. The
next few toned down a bit, while my current one is busy but doesn't
have quite the same feel of ?we can do anything!?
So, did I just give up? Did I decide
we couldn't do anything in a reasonable time-frame?
No and no. I did not give up and I
certainly do not think my team contains a bunch of slackers who
accomplish nothing in a day. In fact, some people joke that my team
is the ?hard work vertical?. It's not entirely untrue; we have a
lot to do and are short staffed to boot. Plus I do ask a lot from my
team. As a general rule they deliver, something which constantly
amazes me.
The change stems from something else.
You see, I long ago learned something which seems to elude the
writers of management text books. It's not a big truth but rather
one of those little obvious things which makes everything else work
better. Most of us even know it. We just don't talk about it too
much because no one wants to admit it.
Here it is. Not everyone is a
superstar. Most of us, myself included in fact, work hard and try to
enjoy what we do. It takes us time to figure things out. We need
help at times. Occasionally we can spend whole weeks working on
something which someone else, somewhere else, solved in fifteen
minutes. Sometimes, when we look at a new technology, it really just
doesn't make any sense whatsoever for the first few months.
By itself this truth doesn't mean much.
We all know most teams contain a goodly number of B players, some
over-hyped A players, and some C players we keep around as trade
goods. But when I combine it with my activity calendars and
planning, I get to something kind of interesting.
Looking over the progression of my
calendars, I can see my own learning curve with my team. At first I
built the activities without much understanding of what my team could
and could not do. Over the weeks and months I learned who could
process which tasks faster, who could solve what kinds of problems,
and who I needed to lay off of for a bit.
Building the activity calendars also
helps us keep prioritized. We all have way too much to do in any
given month. We cannot do it all. What we can do, though, is figure
out what will have the greatest impact and direct our work in that
direction. So long as we hit the high impact items, the rest of it
will probably fall into place.
Speaking of, its time to get back to
working on the next activity calendar. I want it to be ready next
month when things start to get back to normal.
by wayne m.
Consider Scrum
I think you could make life easier for you and your team by using Scrum ("Agile Project Management with Scrum" by Ken Schwaber, "Agile Software Devleopment with Scrum" by Ken Schwaber and Mike Beedle).
First, you need to simplify your activity calendar. It is too complex to update. Go with a spreadsheet listing Task, Priority, and Time to Complete or even go to a three ring binder with a page dedicated to each task. This makes it easy to add, remove, and reprioritize tasks.
Second, rather than assigning tasks to your team, let them select the tasks from the prioritized list. You may need to encourage some of your less aggressive team members to take on tasks requiring newer skills and not to accept all of the grunt tasks that other team members do not want to do. Let each team member determine the appropriate tasking level for himself. Scrum recommends this planning on a monthly basis.
Third, have daily 10-minute status meetings. If anyone is stuck on a task, it will quickly become evident when he cannot report daily progress or has a backlog of blocking issues. It also sets the stage for someone else to provide recommendations or guidance.
It may be possible to do more by doing less. Step back and let the team take on the planning responsibility and focus on completing items rather than having nice looking to do lists.
So, this week I got hit by a truck.
Oddly enough, that's not only a metaphor; on the way to work I got
smacked in the small of the back by an SUV. Fortunately I'm
reasonably bouncy, so I just ended up sitting on the truck's hood
until the driver stopped. The more metaphorical trucks which hit me
this week may prove a bit more problematic to address. Or not, I'm
not sure yet.
That is the nature, I think, of shock.
You are not sure where to go or what to do. You turn, look, plan,
think, execute, all in the space of a breath. You hope the result is
what you anticipated. Sometimes things turn out at you planned.
Other times, not so much.
However, the real test is not in
whether or not the shock occurs but rather what we choose to do about
it. We all get caught flat-footed from time to time. We all get
frustrated, make mistakes, or don't fit into a given situation.
These moments tend to linger on in a closed environment, poisoning
everything we do.
When the truck hit me I bounced up,
kicking my legs out and letting the force carry me up. Doing so
stopped me from falling under the truck. It also redirected the
shock of contact through my back and waist, preserving my bones and
knees. I ended up sore but not injured; bowed but not broken.
My reaction to the metaphorical trucks
is still playing out, right now, as I write this. I have very few
options opened before me, but perhaps I can come up with something
new. Something innovative, quite, and wise which will allow this too
to pass without doing any more damage to me.
It's hard for an IT person to let
things pass, to let go. We are problem solvers and dreamers, makers
and changers. To let go involves releasing that central facet of our
business, the thing which differentiates us from the line workers and
the people who remain forever content in the sticky web formed by
simply being rather than living.
Okay, that's a bit overly romantic. I
suspect my mind isn't as focused as it needs to be. However, it
contains within its purple prose an element of truth. We do what we
do, I do what I do, IT does what it does, to create positive change.
We strive always and forever to achieve the nirvana called
?dial-tone?, where our systems simply work and we fade away into
the background, out of sight and out of mind.
On a more positive note, the team did
well this week. We finished up some nagging issues, continued to
work on nagging problems, and uncovered yet another metaphorical
viper in the pit. With any luck we'll chop that things head off
before all hell breaks lose again.
Onward and upward and all that.
This week my team changed directions a bit; we will now work much more closely with our two counterpart teams in our efforts to get things done. That is, frankly, for the best. Although I'm proud of the team's activity and professionalism we really will function better as part of a greater, more stable group. The process shouldn't take long either.
This weekend, though, I spent some time thinking about the topic of romance in IT work. No, not romance in the sense of windswept heather moors or dewy-eyed glances at members of the opposite sex, though I'm sure that's a popular topic too. Rather, I'm thinking of romance in its older definition, as in the romance of flight or the romance of travel. The idea that something can have a mysterious fascination or appeal, something strangely beautiful about it and that could well be a good thing.
We don't talk much about it, but it's always there, just at the edge of what we think about. It's easy to get bogged down in the frustrations of everyday work, in the long painful hours and the agony we inflict on one another in our attempts to prove whatever. It's elusive, sometimes, especially when we have systems crashing around us and no way to bring them back to life save shear force of will.
You can hear it, a little bit, in the conversations we have when things quiet down. In those rare moments when we share what's really going on in our heads or share the stories which really stuck with us. You can see it in the eyes of those who have gone though the tunnel and into the whatever which lies beyond, the place where they see the systems in their mind's eye and know with bone deep certainty born of wisdom rather than knowledge what must be done.
IT people, at least those of us in infrastructure, don't talk about it much. We don't talk about how much joy we feel in solving the problems, in the slow migration from instability to invisibility, in the exploration and optimization of an existing system or the installation of a new one. On the rare occasions we broach it at all, it's to claim we are simply too hard headed and pragmatic for such drivel. What really matters, we say, is what we do now to solve a problem placed before us.
We laugh at leaders who try to kindle the romance for us again. At least, we laugh in their faces. In my own heart, though, I rejoice when I work with a leader who realizes what we do matters. I may pull up my technician's mask, but in truth I'm glad someone, somewhere, has a clue. I know from talking to others they feel the same way, though sometimes it takes pulling fingernails to get them to admit it.
Unfortunately there's a problem with romance. It's a quality which occurs naturally, an intersection of experience and participant we as leaders cannot create. It occurs spontaneously when we both open ourselves to it and the circumstances occur in which it can flower. The emotion, the experience may last for only a few moments then vanish again until the next intersection occurs.
Naturally occurring emotions arising spontaneously out of circumstances and a particular mindset seem like a pretty unstable leadership tool. How can we, as leaders, ?make? someone feel something? How can we show our followers the romance of what we do or let them know we understand when they do not? Should we even try, especially in today's management heavy environment? Do we have any hope of recalling what it means to have a vocation, to believe in what we do, in a world where people think fear makes a better motivator than hope? One where management textbooks tell you such pearls of wisdom as ?time is a commodity? and ?the decision to hire or train is a buy or build decision?.
I'll write something more practical next time, I swear.
So, we came to the end of another week
and I'm forced to ask the question: what is practical? Why are we do
focused on delivering or solving the immediate need at the expense of
the future? Why do we burn ourselves and our environments into the
ground rather than spending the time and effort it takes to do it
right the first time.
Oh, I know. I've heard all the
arguments, more times than I can count. ?We have to do it this way
because of the mistakes in our past?, we say. ?We have to make
it happen now, and worry about what's right sometime later, or
everything will fall apart.? Doesn't anyone, ever, notice that the
more you do that the more effort you have to spend, year after year,
until finally the total cost it takes you to support your efforts
simply isnt' worth it any more?
That said, it seems to me we rarely, if
ever, have any idea of what it means to STOP. Yes, I meant to
capitalize that word. The amount of effort I've seen pouring down
dead ends, unstable situations, and yes bad data structures is simply
phenomenal. My current employer is by no means the worst of what
I've seen, though in my darker moments I may mumble otherwise.
Stopping requires more than just
knowledge. Anyone can learn how to do it, if they just spend a few
hours reading most technical blogs or any operational methodology.
It requires an act of will, a choice to stop moving and reconsider,
even under the pressure of others to act. Action is, in and of
itself, almost a religious mantra for some organizations; it's hard
to resist the siren's call for long.
As leaders we choose to either foster
that will in our followers or crush it. We foster it by listening to
dissention, supporting the decision to stop in the face of chaos, and
bringing teams together to listen or understand. We crush it by
trying to act as the focal point for all elements of an activity,
thereby stripping our followers of their choices. We can also crush
them by refusing to stop ourselves, by driving forward over the
bodies of those who ?stand in our way?.
What is the consequence of stopping?
What happens when we decide to pull back, to place a barrier along a
mad course? What happens when we choose stillness over motion and
focus over the wild flailing we so often call activity?
It's hard to say. On the rare
occasions I've gotten support for stopping it generally turns out
well. Taking a breath to reassess allowed us to remove problems from
our path, problems we would otherwise have to deal with as incidents
over and over again. It gave us the opportunity to catch our breaths
and reset our minds, allowing us to see what was in front of us
rather than just charging forward. That in turn allowed us to change
plans, reorganize work, and achieve some truly exciting results.
The question, though, is when can an
organization support the ability to stop? What elements must exist
in the organization for it to allow its employees the ability to say
?you know, this is nuts, let's chart another course?? What
elements of leadership need to exist, what levels of selflessness or
selfishness, what political strength or weakness?
I'm not sure I have any answers yet,
though it feels a lot like I have more questions. I suspect the
asking of questions will go on for some time though ? it's kind of
what I'm doing right now in my life. And in my other writing as
well; it's a way of thinking I find refreshing after the doldrums we
call work.
Another Monday. Goodness they seem to come fast these days. The team leapt out the gate in record time; I barely caught up with them before they got to work. It was almost like they felt eager to get on with it all. Which is a good thing, given how much we have to do.
The day also started out well for me personally, as a valued customer gave me some good feedback and a few words of appreciation for my efforts. The feedback will allow me to carry forward with some things I'm concerned about. The appreciation, though, gave me the lift I needed to start catching up with my team. Mind you they were already far ahead of me...
Appreciation comes in many useful forms. The simplest, and most commonly encountered, comes in the form of straight praise. ?Good job? and ?Great work? don't mean much in today's environment, but people still get a little thrill from hearing them. In order to be effective, though, these simple tools have to connect to some kind of achievement. Otherwise, they feel a lot like giving a gold star to someone just for showing up. Personally I use these to mark the little achievements we strive for every day, especially when the team gets something done which will avert rather than solve a disaster.
A more complex form of appreciation comes cloaked in two little words ?thank you.?. If ?good job? serves to acknowledge work, ?thank you? acknowledges the person doing the activity. Its a personal statement of your recognition of another's effort. It is most effective when coupled with a sacrifice on the part of the actor; an action or expenditure of time above and beyond the call of duty. The ?thank you? indicates that you saw the sacrifice, understood it, and appreciate it even if it was not personally for you, but rather for the team or the greater goal. In my own life I try to thank those who sacrifice for me, even if it is expected of them for some reason. After all, a sacrifice is still a sacrifice even if our jobs require it.
A still more complex form of appreciation requires us to take the measure of the person we communicate with. We must assess his impact on his environment, what interests him, and the choices he makes to realize those interests. Then we can comment on his efforts within the context of what is important to him, relating those activities to the overall goals of the business. This allows the individual to feel appreciated as a unique part of the organization, with a unique contribution, regardless of where he sits. I'm not very good at this type of appreciation yet myself, though I recognize it in the better leaders I've worked with.
The most important thing about acknowledgment, though, is that it must be sincere. You must honestly think the person did a good job, truly appreciate their sacrifice, and believe that no matter how off they seem from you their contribution is important. You must focus your attention, at the expense of your own time and energy, on the other person for a period of time. Intent counts for more than technique in this case; an awkward yet real acknowledgment means more than a well-practiced but unfelt one.
It's this lack of sincerity which makes acknowledgment difficult in most companies. People get conditioned to expect falseness. They become cynical and bitter, so much so that even honest acknowledgments sometimes fall flat on their face.
Oddly enough, this same factor makes it difficult to accept an honest acknowledgment. You forget what it's like, so only later in the day or week do you realize what just happened. Either that or you turn it, and its ability to motivate you, aside out of fear you might once again expose yourself to an emotionally dangerous situation.
I know I'm in that boat myself some days.
Trending After Hours posts
Sort by Trending