The Mumbling Manager
This is page 2 of the discussion. Read the opening post
After Hours
This is page 2 of the discussion. Read the opening post
I had just about decided that appreciation from management went the way of the zoot suit and the defined benefit pension plan, at least in the production support area. Project team members here seem to get plenty of recognition and rewards, but the sacrifices of those of us who then have the keep their systems running and compliant 24/7 into eternity are largely unnoticed and unrewarded. I hear these same comments from other production support people in my organization, so I think it is wider than a quirk of my direct management. I don't really expect end users to appreciate the effort it takes to resolve some of their situations, so thanks from them can be especially sweet, but as for management, the attitude seems to be that turnover is low, so everything must be fine down on the cube farm, whose dwellers should take their paychecks and be thankful. Don't misunderstand, I am thankful to have a decent paycheck; it would just be nice to have the hope that exceptional effort and dedication will be appreciated. It is hard to stay motivated to grind it out quarter after quarter, year after year, when the only people who recognize the sacrifices and effort are other poor sods in the same sad situation. (And before you ask, yes, I have in fact in so many words told my manager that my life revolves around meeting certain quarterly deadlines here. The response? Oh- well, that's a shame, it shouldn't have to be that way.)
Major changes in my life occurred this
week. I'll bore you with the details later as there's a topic I
would like to address. I'm sure that comes as a surprise to everyone
given the amount of bandwidth my blogs consume. Addressing topics,
sometimes very strange ones, pretty much defines what I do.
A few years ago I wrote two articles
for Tech Republic on the consultant's role. One suggested
?invisible? consulting in which the consultant provided support
and knowledge to the existing team. The other suggested ?visible
consulting? in which the consultant acts as a champion and change
agent to enable work the client needs. Both came from a consultant's
point of view to describe boundaries around our activities. Neither
spoke at all about the responsibility of the company hiring the
consultant or the importance of proper oversight/review.
No matter how much money we spend on
them, or how well they try to do, consultants are in the end just
people. They try, with varying degrees of dedication, to do the job
as they understand it. Sometimes they succeed. Often times they
fail, just as anyone would, but we choose to cover it up due to our
organizational commitment (expressed in monetary terms) to whatever
project they worked on.
These reviews take on two distinct
forms, depending upon what we hired the consultants to do. If we
hired them to provide skills and services we simply do not have the
internal resources to produce, we must review their work for
suitability and sustainability. If we hired them to do things we
already know but cannot get the time to do, we need to review their
work for correctness and supportability. Finally, if we hired them
to review the work of our own teams we need to review their work for
applicability and actionability.
At first glance that all looks like
management speak for ?review their work?. Honestly, if people
would review a vendor's work more often we'd all be better off. Yet
I'm actually trying to say something about metrics here, so let's
dive in a bit.
When we hire in consultants who, in
theory, can do something we cannot we have to review their work.
Yet, how can we do so? We don't know what they know. We do not have
the experience they have, or the abilities they gained exploring a
specific technology over and over again. In this case we can review
their work by judging whether we can first use it to accomplish our
goals and second whether we can maintain whatever they created
without further intervention. In order to do the first we have to
know exactly what we wanted them to accomplish. In order to do the
second we have to know what we have the time and knowledge to do;
time is not a consultant's concern but knowledge and knowledge
transfer is.
Similarly, when we hire a consultant to
review the work of our own people, we have to measure that output
somehow. It's comforting to get a nice, well formatted report;
that's in fact what most of these engagements seem to produce.
Although these deliverables fulfill various ritual functions, they
only take on meaning in the business world when we can actually act
on them. This means the information the review provides must first
apply to our situation either now or in the immediate future. It
also means the review must provide some concrete actions we can take
to improve, or at least stabilize, our situation.
Finally, and most easily dealt with, we
have the situation where we hire a consultant to perform a task we
know how to do but do not have the resources to address. In this
case we need to take the time to perform a review (architectural for
infrastructure, code for development) using our standard procedures.
We have a responsibility in this case to be both through and fair; we
should also let the consultant know ahead of time what metrics we
will use to measure his success. On one hand this is fair; on the
other it ensures the consultant will know what's expected of him so
he has a hope of delivering it.
More information about the changes in
my life after I have a chance to absorb them.
I spent today trying to explain what I
do to people who really do want to get it. I spent hours discussing
it, trying to make the esoteric world of design priorities, pattern
matching, data mining, and envisioning seem not only interesting but
effective and practical as well. Interesting I can handle; I love my
job. Effective and practical, though, that's another story.
At first I spent a lot of time talking
about everyone's favorite topics: the abilities. You've run into
them in trade magazines, bad books on IT management, and dark street
corners. Manageability, action-ability, supportability,
sustainability, reliability...the list seems endless. After mugging
a people a few times with them, though, I started to wonder if they
meant anything. Looking into my victims' glazed eyes, I assumed not.
It's an easy trap to fall into. We
toss those words around so casually sometimes, it's sometimes hard to
remember they don't mean anything. Perhaps I should rephrase,
slightly. The words still mean something in and of themselves. But
we've misused and abused them so much over the last few decades in IT
they have become almost meaningless buzz.
Take manageability, a watchword in IT
circles these days, as an example. Now, on one hand it means
something relatively specific when we get to talking about the
ability to access management functions in a variety of formats, apply
and control security models, and analyze data related to the
somethings behavior. On the other hand it's been used so many times,
for so many things, that the idea of manageability earns a deep
belly-laugh whenever we bring it up in IT circles. How could it not?
Everything under the sun, including some nightmare inducing control
schemes, ?enhance enterprise manageability?.
Availability isn't much better. We've
all heard the story about how a user thinks the ATM is unavailable
when a deposit envelope isn't available, even though every system
monitor says the ATM should happily accept a deposit. At the same
time, we all know from our own experience that our perception of
availability comes first and foremost from the system under our
charge. If we work on the network, we check it first. If we work
with servers, we check them first. If we work with applications,
business logic, databases....whatever we work on, that's what our
vision focuses on.
So, I faced the challenge of explaining
these things without making people's eyes glaze over. I haven't made
it the whole way there yet, but I came to two realizations which
might help.
The first is that most of what we think
of as -abilities truly exist as processes not as states. A system is
not ?manageable?, certain negative experiences not withstanding,
nor is it really ?available?. What happens is that if all of the
aspects of a given process line up, we perceive that function as a
state. So, we perceive the system as available when all of the
aspects making up the system's process functions execute the desired
result. We perceive it as manageable when it either fits into our
existing procedures or we can build a management process to create
what we need.
The second is that someone needs to
have his head out of the silos so he can understand the big picture.
You can call this person your architect, your lead, your senior, or
just the guy you feed pizza and cola though the slot in the door.
Someone has to see the whole board; otherwise our approaches fragment
and we start to pursue system states rather than the fundamental
processes able to create the impression of a state.
I need to spend more time with this
idea, I think. It's fundamental to both ITIL and several IT
architecture frameworks, so maybe I can borrow some language from
them.
This week was decidedly odd. I spent
it driving around, getting lost in various places I used to know, and
getting lost. I spent one glorious afternoon completely out of my
mind, effectively, lost in an area I once knew so well I could almost
walk down the streets blindfolded. Sixteen years of change, combined
with some deterioration in my interior map, put me into a fugue from
which I've only now fully recovered. It's been literally years since
anything similar happened to me.
Or had it? In retrospect, it was just
a stress-exaggerated version of what we all feel when we sit down in
a changed situation. We rely extensively on our mental ?map? of
the world; when that map does not match with what really exists
things get ugly fast. We go though a period of confusion, then
frustration that what we think is so is not so, then move on to
either denial or relearning so the map can change.
It's this seemingly unstable map which
makes IT so difficult as a career. As professionals we live, and
must thrive, on change. Bugs crop up, causing incidents while we try
to discover workarounds. Patches come out, sometimes fixing the
bugs, more often adding a few new wrinkles to the system as well.
New products, approaches, and clients come and go, each with unique
demands.
Probably the worst examples of this
particular problem, for me anyway, come up when I pick up a new
version of a product I've not worked with for a while. The better I
knew the product, the worse the experience feels. Things don't work
the way I expect. Buttons shift around; menu items change or
disappear. It took me about an hour, for example, to work out how to
make some changes to a WISE package. I'd done it dozens of times in
the past, but two versions back from the tool I end up using. What I
wanted to do wasn't even hard ? I just kept going about it in the
wrong way.
Most infrastructure people I know can
move quickly from the frustration stage to the rebuilding stage.
It's something we find enjoyable, actually, which certainly makes
life easier for us. But each time we have to relearn something it
takes a toll. The more we push it, the more things we touch on, the
more stressful things become. The harder we try to keep up with all
of the changes the less energy we have for other things, like our
lives. The more we try to maintain a clear focus on multiple
technologies, the more difficult it becomes to keep them all separate
and functional in our heads.
The stress builds up over time. If you
have to shift rapidly between multiple, quickly changing products you
wear down quickly. If you work with a single product, or a small set
of intimately related code-bases, you learn more about a particular
product and encounter the need to radically change your mental map
less. I suspect, but cannot prove, that this tendency helps to
reinforce the silo approach so common in IT shops all over the world.
Managing that stress in ourselves is
hard enough. I know when I really dig into something I get surly and
difficult to deal with. My wife even comments on it form time to
time. But as leaders we have another challenge entirely: managing
the stress of others as they try to get the business' job done. Note
that it's not always our team's job; often we find ourselves
wrestling with problems in infrastructure which have little or
nothing to do with us in the end.
Hummm. Helping others to manage their
own stress brings us full circle to my comments about fugue states
earlier. Allowing people to push themselves to the breaking point
does little good for anyone. It breaks down the individual's
productivity. It shatters the team's focus. Ultimately, it leads to
an inability to deliver very, very common in the world of IT.
by jack-m
So, here I sit in my home office. It's
been a strange two weeks, not made any less confusing by my family
being out in Oregon. I, like many people I know, function a great
deal better when I have my wife and son somewhere near by. They are,
after all, a large part of why I do what I do rather than go off and
sit on a mountain somewhere instead of a chair. The other part is
that I enjoy what I do, though circumstances make such feelings hard
to hold onto.
That I'm posting from my home office
should tell you that I'm back looking for work again. There are a
lot of different ways to spin why this happened. The truth, no
matter how you slice it, boils down to the situation did not work out
well for anyone. I did what I could. They did what they could. We
didn't met in the middle anywhere, so it became wise to move on. So
we did.
Now I find myself in the middle of yet
another large project, started just like any other IT project (in the
middle) with limited resources, almost no time before the deadline,
and uncertain functional needs. So fundamentally it's a question of
applying what I know about organization and communication to achieve
a goal without stepping over one of my two fixed boundaries.
Somehow, this seems familiar...
Like any good project, this one becomes
more complicated as I interact with my clients mostly unknown needs
(at this point, anyway) but also by my various stakeholders and
advisors. One of the stakeholders is two years old, so it's a bit
difficult for him to articulate what he wants from the situation.
Another hasn't even been born yet, but would probably like a stable
situation by February so he/she can command our absolute attention
for a few months. Still others, who've known me all my life, want to
help if they can understand what I need and why.
I've also got a good bit of market
research to do. Assessing what your clients want is, in fact, the
first part of any good project plan. Unfortunately, I really only
have one product to use in this particular effort, myself. I am what
I am, warts and all. I have specific skills and experience which may
or may not assist others in the accomplishment of their goals.
On a personal level I think my skills
bring value to those who let me use them. Over the years, many folks
have agreed. Others want my head on a stick. But communicating that
value to others, especially when I sometimes speak in tongues.
That's part of why I like to write, really. I think on my feet
reasonably well but it can take a bit of work to explain what I see
in a way others can follow. My tendency to use holographic analysis
techniques doesn't make that translation any easier, as they let me
pluck the right answer out of seemingly thin air.
In order to get everything organized I
spent a good portion of last week building my plan, working on a
market analysis, and creating iterative artifacts to keep track of my
progress. The fugue I talked about last week didn't help much; in
fact there are still dozens of loose ends I need to deal with.
Collecting those loose ends will probably take most of this week,
then I should be caught up.
Well, at least until my wife and son
come home. Then I'll let everything else go for a few days while I
catch up with them. Frankly, that's probably the best use of my time
I can imagine. Like all projects this one will end, but the
environment in which I thrive needs to be re-established or I'll
never have the strength to take on another challenge. And that will
not do at all.
Wisdom is always valuable, no matter
how late it comes. It's an old saying and something I try to
remember every day. It's also probably one of the most important
things you can learn about project management, or in my case job
searching. It's never to late to reconsider your course, never to
late to reassess, and never to late to make the right decision even
if you know you will pay a price for doing so.
Practically, this belief means I took
part of this week to step back and assess what I want. Not ?what I
want? in a cosmic sense ? I've know that for years ? but what I
want from a job in the short, medium, and long term. Such
understanding doesn't always lead to happiness but it does give me a
foundation from which to work from while performing my search, going
to interviews, and asking for people to do me the favor of putting in
a kind word at an opportune moment.
If my job search were a project we
would call this ?envisioning? and immediately hand it off to
someone to write up a vision statement. We would then carefully
enshrine the document in a suitable cylindrical container and get
about the business at hand. Since this is my life, though, I'd
rather not have it end up in a dump somewhere.
Besides, a clear vision helps me not
with the how or the what of the activities but the why. Too many IT
project vision statements include statements in the following form:
?we will install X product in Y time frame to meet Z objective.?
That's not a vision statement or even a project charter ? its a
statement of what needs doing and by what date. It strips power from
those who do the work by reducing them to puppets dancing to
another's will. ?Here you go! Your vision is to make whatever we
tell you to make, regardless of how much sense it makes, and no we
won't ask you how long it will take!?
Back on target, though, I decided to
divide my vision into three time-horizons. This is one of my most
common tricks for understanding a situation; it helps me to keep
things in perspective. It also reduces complexity by allowing me to
remove factors from consideration. Highly complex analysis takes a
good bit of time and, frankly, leads to a kind of paralysis I cannot
currently afford.
So, with those thoughts in mind I
played one final card. Pride aside, I know I work better when I work
with people whom I know and trust. So I spent time chatting with
friends and family about, well, stuff. We talked about perspective
on the past and what the future might hold. We talked about what
they thought were my better abilities and what they thought I should
avoid. Probably the most interesting discussions centered around
what I seemed happiest doing; not what I was happiest doing, since
only I could know that, but what those who know me best thought as
they watched me move though various career stages.
The results both enlightened and
encouraged me. My short-term vision involves a lot of work on things
only marginally related to the job search - finishing up some books,
getting a photo shoot for a martial arts book I've written, and
various bits of personal business. Working on those will help to
revitalize me and stave off the fugue state I mentioned in my other
posts. The medium and long term visions will take more work, though
I'm still on track for both of them. It's important, especially in
times of change, to realize your own goals still lie within your
reach.
Vision statements, like relationships,
are profoundly personal things. I wonder sometimes if that is why we
do them so badly in business; its easier and less exposing to write
the usual trash rather than say something meaningful.
by superemg
The title is misspelled!
Thanks! That was embarrassing.
I spent last week pondering the esoterica of career management and role
matching. Although I find such things a great deal of fun, they do not
meet the short-term goal of finding me a job sometime before year's end.
Addressing that challenge involves putting theory into practice. In this
case, it means getting organized so that I didn't accidentally double or
triple (or more) submit to a job via network contacts, recruiters,
professional associations, and things as prosaic as job boards.
I spent a few minutes this morning envisioning what a good tool set
would look like. The tool set would contain ways of threading email and
voice conversations together, build calendar entries from suggested
appointment times, keep track of who was connected into which
organizations, and allow me to aggregate leads in a timely fashion. In
an ideal world it would be entirely graphical, so my poor picture-driven
mind could handle the data. It would also update information from the
various job sites, each of which relies on its own internal database to
record your information.
To further constrain the search, I have both limited time and very
limited resources. After all, I'm not here to develop software (though
there seems to be a market here) but rather to find a job myself. So,
let's fix the software budget at under $50 total and fix the time to
less than one week of development or training.
So, in formal language I have:
Time fixed at less than one week
of invested effort ? I have to meet my basic needs in that time or
the project fails
Resources fixed at one person (me)
and under $50 for expenses ? I really cannot get anyone else to do
the job and I don't have much more money.
Functions which would take a
concerted development effort to build ? looks like a nice product
if it existed.
With two-sides of the iron triangle fixed, I decided to cut down on my
functional requirements. What did I absolutely need, what fell into the
nice to have category, and what could I really live without.
In the ?need to have? category come threaded conversations and the
ability to track which jobs I've applied to, who either networked me
into that job or will act as a referral, the contact information to
follow up on the lead, and the lead's status. Without these I cannot
adequately execute on my current task.
The ?nice to have? category includes the automatic event generation,
lead aggregation, the ability to thread together multiple conversation
types, and updating from various sites automatically.
The ?live without? category came to include my favorite features.
Graphical interfaces of the mind-map variety have never been overly
popular. Normalizing the data from the various websites would also
probably have to wait for me to hire a developer with my non-existent
venture capital.
So, what to do?
For me, for now at least, the answer looks like Google. They have both
mail and an integrated calendar; the later includes a nice map feature
which helps me to keep track of where I need to go. I also built a
workbook on Google Spreadsheets using the company name as the key on one
page and contact name as the key on another ? it's no database but when
I get around to it I'll import it into OpenOffice. Establishing a good
set of keys and table structure will save me time later on. As an added
benefit the Google elements all come with built-in collaboration, a
definite plus which I didn't initially anticipate.
For graphical mapping I pulled down FreeMind; it's not perfect but it's
definitely a good place to start. If I can figure out how to integrate
it into Google (or into a back-end database) I may be cooking with fire.
Assuming, that is, I can do it by the end of the week while taking care
of everything else and not going over budget.
I spent last week pondering the esoterica of career management and role
matching. Although I find such things a great deal of fun, they do not
meet the short-term goal of finding me a job sometime before year's end.
Addressing that challenge involves putting theory into practice. In this
case, it means getting organized so that I didn't accidentally double or
triple (or more) submit to a job via network contacts, recruiters,
professional associations, and things as prosaic as job boards.
I spent a few minutes this morning envisioning what a good tool set
would look like. The tool set would contain ways of threading email and
voice conversations together, build calendar entries from suggested
appointment times, keep track of who was connected into which
organizations, and allow me to aggregate leads in a timely fashion. In
an ideal world it would be entirely graphical, so my poor picture-driven
mind could handle the data. It would also update information from the
various job sites, each of which relies on its own internal database to
record your information.
To further constrain the search, I have both limited time and very
limited resources. After all, I'm not here to develop software (though
there seems to be a market here) but rather to find a job myself. So,
let's fix the software budget at under $50 total and fix the time to
less than one week of development or training.
So, in formal language I have:
With two-sides of the iron triangle fixed, I decided to cut down on my
functional requirements. What did I absolutely need, what fell into the
nice to have category, and what could I really live without.
In the ?need to have? category come threaded conversations and the
ability to track which jobs I've applied to, who either networked me
into that job or will act as a referral, the contact information to
follow up on the lead, and the lead's status. Without these I cannot
adequately execute on my current task.
The ?nice to have? category includes the automatic event generation,
lead aggregation, the ability to thread together multiple conversation
types, and updating from various sites automatically.
The ?live without? category came to include my favorite features.
Graphical interfaces of the mind-map variety have never been overly
popular. Normalizing the data from the various websites would also
probably have to wait for me to hire a developer with my non-existent
venture capital.
So, what to do?
For me, for now at least, the answer looks like Google. They have both
mail and an integrated calendar; the later includes a nice map feature
which helps me to keep track of where I need to go. I also built a
workbook on Google Spreadsheets using the company name as the key on one
page and contact name as the key on another ? it's no database but when
I get around to it I'll import it into OpenOffice. Establishing a good
set of keys and table structure will save me time later on. As an added
benefit the Google elements all come with built-in collaboration, a
definite plus which I didn't initially anticipate.
For graphical mapping I pulled down FreeMind; it's not perfect but it's
definitely a good place to start. If I can figure out how to integrate
it into Google (or into a back-end database) I may be cooking with fire.
Assuming, that is, I can do it by the end of the week while taking care
of everything else and not going over budget.
by wayne m.
Focus on the priorities, network and get resumes out now.
There are two mistakes one can make in sending out resumes. One can send out multiple resumes for the same job or one can fail to send out a resume for a particular job. There is little added cost personally to sending out multiple resumes and that cost will probably be less than the budgeted $50. There is little risk in sending out duplicate resumes; a company is unlikely to cancel an interview because it receives a second copy of of one's resume. There may even be minor benefit; the recruiter may be in a poor frame of mind when reading the first copy, however, this benefit is so slight that it probably does not justify actively sending duplicate copies. The costs of not submitting a resume due to a mistaken belief that it is a duplicate can potentially be quite high. Many companies actually expect different copies of resumes for similar job opending. One is much better off ocassionally sending duplicate resumes than failing to submit any.
Get in touch with old collegues now. Don't beat around the bush, tell them you are searching for a job. Contact a head hunter. Actively search through all of the online job sites, including local ones, such as the newspaper. Yes, sign up for the notification services, but first read through all openings for at least the past month. Time is of the essence because the daily cost of revenue not realized is the highest expense when unemployed.
by jamesrl
The shotgun and the rifle.....
I was laid off in late 2002, when the market was pretty rough. I would go to my outplacement service and saw many former colleagues who were in the same position.
Frankly I think you are overthinking it. You are focusing on the tools, and not the result, the how and not the "what". Some very successful people don't use any tools for this other than their brains.
Start with this idea; Get a blank piece of paper, and sketch out in point form, your ideal job. What would it look like?
Then think about and sketch out the charecteristics of the kind of company that might have that job or need to have that job.
For that job, you want to use a rifle. You want a targeted campaign to find the companies that have that job or that need that skillset.
I recommend using a shotgun as well. That means getting your name out there. You can build a contact list and continue to build a network of people who are on the look out for your opportunity. There are services out there that will put your resume in the email boxes of every head hunter in a geographic area. Thats one approach, and for the cost, not a bad one. But you can't follow up with every one. So use your network of friends and acquaintences to understand who the best headhunters are that worth the time to follow up with a personal call. Shotgun and rifle.
The same applies to applying to jobs online. Apply to everything thats a reasonable fit, but target the best fit for extra followups. Prioritize or you will chase your tail alot.
The same applies to networking leads.....etc.
If you don't belong to a job hunting club, join one. I had a lot of support and help from my peers, and there were some useful workshops.
You will after a time recognize situations where you spot jobs that more than one headhunter is working on, or is posted once by the firm and once by the headhunter.
Have a great resume before you apply anywhere, I had greatly improved success after I attended a resume workshop and modernized my resume.
I wish you luck - feel free to peer mail me. I'm also a manager and I review resumes and interview people so I am happy to provide feedback for you.
James
I spent another week networking. The
activity does not come naturally to me. Well, that's not entirely
true. I get comfortable instant messaging and emailing the people I
know rather than calling them up or going out to lunch. There is a
seductive ease in tossing off an email and adding a check to your
list. It feels remarkably like accomplishment. Unfortunately email
functions a great deal like UDP ? if you don't receive a reply
there's no way to know if the other person actually interacted with
your message.
At work I control the urge with the old
standby MWA ? Management by Walking Around. Nothing breaks the
IM/email shackles like getting out of the cube and speaking with
folks. I generally make it a habit to make both a morning and an
afternoon loop though the office, just to keep on top of what's going
on.
A reasonable loop becomes more complex
when I'm networking. I do not live in a densely populated metroplex,
so going for a walk would involve 30 to 40 miles a day. Frankly I
just don't walk that fast. It feels intrusive to call people more
than once or twice a week. I cannot afford to do lunch more than
twice a week with a pregnant wife and two-year old son at home. That
leaves the phone, with it's rapidly vanishing pool of minutes. A
cell-phone plan intended for low volume household conversations lacks
the capacity to deal with two professional job-searches.
Networking events and interviews help
since they give me a set time to get out and interact with others.
It gets me up and interacting with others, a definite plus in the
world of easy impersonal communication I inhabit. Unfortunately it
takes time to get such things scheduled, though I aim for at least
two each week. These will get more complicated to juggle when my
wife's search really picks up.
Snail mail gets a
workout too. I realize it's retro, but a heartfelt ?Thank You?
note still strikes me as appropriate and respectful. Acknowledging the time people
give to you, especially in the activity-filled world we live in, is
always the right thing to do.
Which brings me back to
the comfortable mediums of email and instant messaging. They
certainly count as activity even if they do not quite have the
results I might like. They also do serve a valuable purpose,
providing rapid asynchronous communication with people who probably
want to help but need to do so in their own time.
So, I decided to adopt one of my old
tricks to stomp out email activity. When I decide email provides the
appropriate medium for the communication I open the communication
task on my list when I send the email. I only close the task when I
hear back from the other person. This prevents me from thinking of
the task as ?complete? when it really just began. It also gives
me a handy list of outstanding communications to track.
Communication is, after all, the stuff
of life in business and in job searching. I suspect it's that way in
the rest of our lives as well though do not tell anyone I admitted
that.
by jack-m
Communication is definitely the stuff of life, and it does give one a feeling of accomplishment to make that check mark on my to do list after I've fired off an email. In my job search I've found that while I get a feeling of satisfaction checking off any item it's not nearly as satisfying, or, I think, as effective as a phone call or the ideal, a face to face meeting, if only to convey info.
Emails and IM's are here to stay but in a job search as an employer I want to see what I'm buying and as a potential employee I want to see what I'm getting into.
Both emails and IM's have their place and God knows it's too late to do without them in this technoage but nothing will replace the old fashioned "search" in job search.
I'm not much of a Monday sort of
person. It's an important day, I'll give it that, but after a nice
weekend with my son I'm inclined to take it easy. Keeping up with a
two-year old is hard work. Working from home with said son running
around makes Mondays even harder. When I'm out of the house the
change in surroundings helps to reset my mental state. At home, I'm
still in the same frame of mind at the start the day.
This Monday set itself apart from the
usual run-of-the-mill by starting off at a gallop. A storm of emails
and calls forced me to move quickly, shooting off responses and
explanations at a blistering pace. Meanwhile some family business
finally came to fruition and I worked out a better explanation for
one of the methods I use in holographic analysis.
In this environment I had to find the
stillness required for action by balancing four basic competing
forces:
The financial press created by the
business of having a family
The psychological pull to assist
my wife and child while still having to work
The intellectual stretching
required to track all of the ideas and communication threads flying
around
The emotional oscillation caused
by my own hopes and fears as I reviewed various opportunities
Now, I could just repress one or more
aspects of my personality so I could focus on one thing at a time.
Focus is one of the most important aspects of the disciplines I
practice; with that one thing you can move mountains. However, I
know from practical experience that repression leads to greater
problems over time. It's also somewhat addictive, since it allows
you to generate great activity without necessarily addressing the
things throwing you off balance.
In order to deal with the situation I
deployed one of my favorite tricks; making a cup of tea. Yes, tea.
Let me explain.
When it comes to a drink of choice, I
know a lot of people like coffee. The caffeine helps us to get over
our near chronic sleep deprivation. For historical reasons it's
also the drink of choice in work related social situations (from way
back when, when beer was about the only thing you could drink without
getting sick). That said, I'm a tea man.
Why tea? It is the flavor? The aroma?
The fact I sometimes have very high blood pressure and don't like to
take medications? The availability of herbal preparations which
generally make an appearance in island intoxicants? All of those
mean something, I guess, but the reason is really much more
practical.
Tea is about ritual. You prepare the
water in particular, idiosyncratic way. You select a tea, place it
in your tea bag/ball/tripod. When the water is ready, you decant it.
Then you wait while the tea steeps; nothing can change the need to
wait but you can decide how long you wait based on your tea selection
and preferences. When the moment arrives you strain the tea into a
cup (or two) and then move forward.
Rituals allow us to both create order
and return to focus. In this case, the time-honored elements of
making tea allow me to focus in on something simple while my
subconscious chews away at how to organize everything else. That
focus calms me, which in turn allows me to use the answers I come up
with during the ?down time? to greater effect.
I choose tea as my ritual for a lot of
personal reasons; that's what makes it effective.
Now if you will excuse me, I need to go
brew a pot. I have some things to not think about.
Just like that, a situation changes.
One moment you are unemployed, looking for work and communicating
with an ever widening network. Then you have a job and need to
report to work on Monday. Everything you wanted to do ?soon? now
needs to finish by, oh, Sunday evening at the latest.
When I first started my job search, I
performed a little project management exercise using the iron
triangle to do tool selection. At the time it felt like a bit of a
waste; after all, I need to be out there networking more than I
needed to plot out database table structures. It takes a balance of
activity and work to keep moving in most situations, though, and a
bit of early work helped to keep me sane.
Now that work pays off. Over the last
month I've collaborated with over one hundred people in this search.
Each provided me with unique insights, opportunities, and assistance.
Each gave freely of their own time in an effort to help me receive
employment. Now I should let them know the fruit of everyone's
involvement. This communication could have been extremely
complicated, especially if I wanted to customize each message.
Fortunately, though, my tools allow me to track people's involvement
and the connections they brought to the table. What could have
become a nearly impossible task is instead a pleasure.
My job search was a small project.
However, the same effect manifests in projects large and small.
Small organizational steps early on keep things from falling apart
later on. A few minutes or hours spent on a seemingly trivial bit of
organization allow you to do something unexpected at the end. In
this case, it let me communicate clearly with the people who helped
me. On a project, it can prevent you from missing key elements or
important but quiet events as they occur.
I'll post more on Monday. Until then,
it's onward and upward and all that.
by jorgeevic
by a1
So, today I started a new position. It
was a bit of an anticlimax compared to finding out I'm going to have
a daughter in February, but still a lot of fun. Both experiences,
though, reminded me of the absolute importance of taking care of the
little details. After all, starting a new job or having a new child
enter your life both look far, far to overwhelming to honestly take
on as a whole.
Both, though, really break down into
hundreds of interlocking small steps. Take the starting the new job
as an example. It's a big step. I'm walking into a new situation,
filled with new people, new products, and unknown challenges. For
someone without a car (like me), I have to work out new bus routes,
not to mention prepare as well as I can based on the information I
have, polish my shoes since my son decided they needed a long bath,
and talk my white cats out of using my coats as a sleeping mat after
my son unhooks the hangers. That's all before I arrive at the
work-site. Add to that all the standard logistical challenges
associated with starting up, the social challenges of a new
environment, and the intellectual challenges of understanding how
others put together a complex system and it could seem overwhelming.
Standard wisdom would suggest breaking
it all apart into a task list and then doing each item in order of
dependency. This is not a bad approach when you have something you
can wrap your arms around and do though your own effort in reasonably
short order. Starting a new job, for example, fits neatly into this
model. You start at point A, work out the simple critical path to
point B, then execute until you complete. Like magic, taking each of
the small steps ends up with you reporting on time (or in my
preferred scenario a little early) to your first day of employment.
The same approach doesn't always work
in project management or in life, though. Both generally involve
more than a limited set of actions over a short time horizon.
Instead they involve dozens of interested parties, each one with
their own needs, over a long period of time. Sometimes the goals
change. Other times, the circumstances around what you want to
accomplish change so completely the goal becomes meaningless.
Rarely, things stay stable enough for you to know where you will end
up.
So, do we just give up on task lists
and critical paths? Do we take to the streets in wild (well, wild
for project managers) revelry? Do we just accept our fate as cogs in
the vast machine, awaiting our next opportunity to writhe under the
crushing wheels of fate?
Nah. You see, all good project
managers I've ever worked with or trained have a gift. They can see,
or feel, or otherwise break apart complex outcomes into multiple
branching critical paths. More importantly, they can discern which
paths carry high priority, which ones need attending to, and which
ones they can safely ignore with minimal repercussions. Sometimes
that later comes back to haunt us, when we estimate wrong, but that's
the price we pay for prioritizing.
The trick is to not lose focus on the
little things as you move forward. To take a mundane example, its
all well and good to know you need to polish your shoes, but knowing
and doing are two different things. And if your son hides the shoe
polish, you've just added a new task to your ever growing list.
I'll talk more about new people and new
things on Friday.
It's the end of the month already. My,
time flies. I should write something introspective and
retrospective, summing up my brief exposure to the job hunting
market. I'll probably write something like that in my journal,
assuming I'm awake for it. Instead, today I want to loop back to
suggest a simple method for envisioning your project in multiple
dimensions.
Now, we bound projects in the iron
triangle (time, resources, scope/function) and generally involve
challenges ranging along contractual, financial, logistical, human
resource, political, and technical dimensions. I know there's more,
but I'm trying to be brief. We coordinate all of these elements into
a single ?project plan? and one or more integrated time lines.
It's that later part I would like to
address. I don't know about you, but I can get a little focused on
one dimension of a project when I stay on it for too long. That's
good, in that I learn a lot about a particular bit of the puzzle.
If, for example, I'm head down on financial spreadsheets for a few
weeks, I'm likely to know more about it than anyone else. That's
bad, though, in that I lose track of all of the other dimensions of
the project. Focusing on the finances can, for example, lead me to
neglect to update the political time line as we move forward.
Recognizing this failing in myself, I
use the following tricks to get back in touch with the big picture:
Sort your project issues and risk
lists ? No, not by severity, probability, or current mitigation
status. Sort them by dimension, looking at them in terms of what
you've identified and when you did it. For added interest, apply a
different time line (say a financial time line to the political
risks) and look for the patterns.
These tricks help me to rebuild my
mental map of the situation and reset my focus where it needs to be.
Obviously there are dozens, if not hundreds, more approaches ? I'm
fond of using various mind mapping approaches as well.
Fast, faster, fastest. This would be
the approach we have to take sometimes; paring down our methods and
our intentions so that we achieve the greatest possible results in
the shortest possible time frame. This kind of delivery looks good
even though we cannot sustain it for long. All that paperwork does
have a use, even if its not in the immediate delivery of a specific
service.
When paring down, I take a page from
?The Demon Haunted World: Science as a Candle in the Dark? by
Carl Sagan. It's a good read, and a good bit more accessible than
the weighty tomes which inspired it. It also, unlike the later
texts, contains a number of purely practical techniques for dealing
with the extraneous stuff the world throws at us. In this case, an
envelope.
The idea is simple. Take a small sheet
of paper (I use 4x6 note cards). Take a look at whatever strange and
complex problem presents itself. In my life, the problems mostly
have to deal with negotiating constrains in time, resources, and
scope while maintaining adequate focus on people, process, and
technology. Solve whatever problem you have in the space provided.
If you cannot, odds are good you don't have an answer yet.
For example, today I built a critical
path for a deployment project on a napkin. The small space forced me
to focus in on real, tangible milestones. Since I write in pen, it
forced me to ponder exactly what I put, where, and why. The first
unholy mess of a path suggested I probably needed to do some more
thinking. The second, on the back of co-worker's napkin which I
snatched when he turned away, looked like it might work.
This is not a communication technique.
Yes, project management's first, last, and strongest contributions
usually revolve around communication. Rather, this quick sanity
check provides us with a tool for checking our own reasoning before
we go out and make fools of ourselves.
You can, though, use this trick to
refine a message before sending it. We've all composed those long,
rambling emails which just go on, and on, and on without delivering
any real message. The next time you find yourself about to hit
?send? on a message taking up more than one screen, stop. Haul
out an envelope and see if you can express your idea to yourself in a
little more succinct fashion.
Oh, and one other thing. If you have a
chance, set aside your envelope for a day or two, then go back to it.
Ideas which seem brilliant and clear in the heat of the moment
sometimes grow a little fuzzy with some sober reflection.
This discussion is closed to new replies.
Sort by Trending