Friday, December 26, 2014

December 26, 2014: A Few Steps Away From the Office

We all hear about work-life balance.  In the last few years, with the advent of ubiquitous laptops and smartphones, the more accurate phrase is work-life integration.  Both intrude on each other.  Some days you'll be at the office until 8.  Some days you'll leave the office at 3 for a parent teach conference or take 3 hours in the middle of the day to have tires installed.  

This post is not about work-life integration.   Take a few steps away from the office.  Separate yourself from your work.  

This Christmas I was able to spend Christmas in person with my teenage son with a visit from my brother and video chat with the rest of my family.  It was such a different experience.  We did not get a tree.  We bought some poinsettias, and put one in the middle of the living room with Christmas lights in it.  The gifts went there, of course.  We woke up late, and after our Christmas morning gift thing, we played video games together.  Our current favorite is Crash Team Racing, a game from 1999 on the original Play Station that we play on the PS3 now.  

In the afternoon, we put a ham in the oven and then took a nap.  Then we made doughnuts.  Real doughnuts.  You make the dough, then let it raise for an hour.  Then you form it into doughnuts and let it raise for another hour.  Then you put them in 375 deg oil for 1 minute per side, and put them on paper plates with paper towels.  Then you add the glaze.  They are crunchy, and when still warm they are amazing.  Unlike Krispy Kreme or Dunkin, the dough isn't very sweet.  I had 4.  

As I sat there, a chunk of warm ham in one hand, a warm glazed doughnut in the other and my son across the table from me, I felt that Jack London-Herman Melville-Ernest Hemingway feeling.  You know it.  "This is life," I said to my son.  The feeling would have found place in a king's hall with a tankard of ale in a fantasy novel, on the open sea with a Viking.  And it found me in my cozy dining room with my son, eating our fresh pastries and plotting how we'd blow each other up with missiles while racing.

To be sure, I have had many years of enjoyable work.  Sometimes even joyous work.  My chosen career path, however, is not primal.  And it's good to get to that primal place sometimes.  So I suppose cooking is primal for me.  What is primal for you?  When do you feel like you can look up at the sky and shout, "THIS IS LIFE!"?  Do you know?  When was the last time you did it?  

How soon will you do it again?

Wednesday, December 24, 2014

December 24, 2014: Your Executive and You

It's Christmas Eve!  Just to be contrary, I took yesterday off from the blog and instead will cover a somewhat esoteric topic, I think: the work life of an executive.

The news (and office scuttlebutt) often make the work life of an executive sound easy and fun: you travel, meet people, get paid well, and sometimes the company will even pay you when they fire you.  The reality is different.

Yes, you travel (you miss your kids' soccer games).  Yes, you meet people (and if they are customers and don't like you, it could sink your business).  Yes, you get paid well.  No different reality for that one, that part is true.  Most executives don't get golden parachutes.  They are often given the chance to resign instead of be fired.  Executives are married to the company.  They have 16,000 things (my favorite number to convey limitlessness) going on at the same time.  People call them at all hours of the day and night, and they have to be available for emergency phone conferences 24/7.  Romantic dinner with your spouse?  Customer emergency in Singapore!  Saturday morning soccer game with your buddies?  HR needs you in a disciplinary action meeting! Leave your cell phone at home when you go on vacation?  I don't think so!

The reality of an executive's work life is that she has a huge set of responsibilities, and there is no possible way she will know every thing going on in her operation.  The VP has meetings all day long - budget strategy sessions, revenue opportunity meetings, IT project updates, customer escalations, personnel disciplinary meetings, operation status updates, training planning, you name it, it's part of the executive's portfolio of responsibilities.  Most of the day is spent going from meeting to meeting and making decisions based on snippets of data.

Even though you and your team spend all day every day on a certain project, the exec doesn't have an hour to hear all of the important things you're doing.  She has 10 other people with projects to talk about today.  Yours is probably not the most important one.  But the exec will try to make you feel like it is.  That is also part of the job description.

Given this reality, executives have fundamental bandwidth issues.  They gather a trusted cadre of lieutenants who receive, filter, and pass along important information.  These lieutenants know what words like "risky" and "potential" and "troublesome" mean to the executive.  Some are more risk-averse than others.  Each has his own areas of expertise and areas of ignorance.  Some will admit ignorance, some will fake competence or deny ignorance.  They must trust the team to give them good information.

When the exec goes out into the company to speak with the likes of you, she may not realize that you don't know what "risky" means to her.  If you use that word casually because it's not a hot-button for you but it is to her, you may get a sudden case of executive attention.

Or if the executive is in a project status update meeting and sees something she doesn't understand (why would the Toledo office be so far behind in training?), she may ask a question to the presenter.  Because the exec knows she doesn't know everything that's going on, a random audit is a simple way to keep people on their toes.  She'll ask a question.  It could be anywhere, about anything.  Sometimes she's only curious.  Sometimes she's concerned.  Her close circle will be able to tell which it is.  The purpose is just to keep everyone on their toes and prepared for such questions.

If such a question comes down to you, your best bet to answer it is usually not to give the executive a call.  Your best bet is usually to call one of the exec's close circle, ask some questions to clarify what the concern is.  The Toledo office is behind in training.  Is the executive concerned that the management team is not leading that effort?  Concerned that the training quality is perceived so low that the team doesn't prioritize it?  That the IT system that delivers the training has been unreliable lately, and maybe the team can't get the training?  You know the answer, of course.  But you don't know the question.  So you call the person who does have 30 minutes to talk to you about a specific issue, understand why you are being asked the question, and then you can prepare a reply.

The most important thing to realize about your executive team is this: they are all humans.  They all have 24 hours in a day.  They are usually pretty smart.  And they are fallible.  And ignorant about large swaths of your company's detailed operations.  So when you interact with them, prepare yourself to speak in a condensed form, get right to the point, ask for any help you need, and let them go!  Hopefully they have other issues that are more pressing than yours, and you can get their help to get your job done.

Thursday, December 18, 2014

December 18, 2014: Survivial of a Common Worst Case Scenario

On the last blog, we discussed success and how it may be defined in the workplace.  Your homework from that post was to list up the ways your work could be considered a failure even though these criteria are not listed on your goals and objectives.  Obviously, death, injury, tornadoes and bankruptcy are true worst-case scenarios.  For our purposes on the topic, however, worst-case simply means a situation with a potentially large negative impact to your career.

Faced with what many would consider a worst-case scenario, what can you do?  In many cases, as you look through your list, the answer might be 'nothing'.  Nobody can do everything perfectly.  The modern business climate does not afford anyone the time or money to fix every gap or meet every need.  We are all forced to prioritize.  First we have to decide what must be done vs what should be done.  Then we have to go through the list of what must be done to decide what needs attention on a given day.

Many of my worst-case scenarios were completely out of my control.  I may have noticed something that I want to fix, like a training gap.  If someone from headquarters does a thorough audit, they would find that my team is far behind in training.  If I've noticed the problem but haven't been able to free people up to attend training, all I can offer is the lame, "I noticed this already, but haven't been able to send people."  Which is just as weak an excuse as it sounds.  What the other party hears is, "I know about this, but I don't care enough to take action."

As an individual, you are limited in your power.  Particularly as a front-line supervisor, your options to respond directly to such critiques from headquarters are limited.  If you are able to address an issue yourself, you should of course do it.  If you are powerless to do it (say that you need to sway the opinion of an executive), you must find someone who is not powerless to do it.

Wait, what?  In these cases, networking is key to success.  If you do not know the executive well, you need to be friends with someone who is or who can effectively advocate for your cause.  To a certain extent, this is playing office politics.  In another way, it is a simple recognition of the human condition.  How is that the case?

Executives (and everyone else with an axe to grind) are people.  People have a limited amount of time and patience.  If an executive sees a report and doesn't like something, he may ask a question.  Maybe he's just curious.  Maybe he thinks it's really a problem.  In any case, the executive probably does not have time to hear your valid reasoning.  We'll discuss why this is the case in a later post.  So what you need is someone the executive knows and trusts who does have the time to discuss the issue with you and can take it to the executive and influence his opinion.

There are a few ways this can happen.  Let's assume your contact is part of the executive's common circle of coworkers: they see each other on a regular basis, and have friendly relations.  Your contact could ask the exec about the issue, and find out if it's curiosity or concern that prompted the question.  She could vouch for you to the executive, something simple like, "I know Mike, and he has a good plan to address this."  Or (and this is more difficult) she could follow a completely different line of questioning: "Why are you concerned about this?"  Maybe the executive is not concerned about the training gap per se, but he sees it as an example of letting things fall through the cracks.  Perhaps your contact would suggest a different report that shows all of the objectives that are being accomplished.  Or perhaps the executive is right.  Lastly, and most effectively, you can take the added attention as an opportunity to ask for help.

Yes, added executive attention is often a positive thing.  In the training gap scenario, you may not have enough people to complete necessary business if you send some away to training.  So you can ask for backfill while your people are out.  Certainly you should have asked for it before, but remember, this is a worst-case scenario.  When you receive unexpected negative/scrutinizing attention, make it into a positive whenever you can.  Think yourself into a solutions-based mindset and come up with reasonable solutions that the executive could provide to help solve the problem.

We'll explore this topic some more in the coming weeks.

Tuesday, December 16, 2014

December 16, 2014: How Can You Recognize Success?

Do you know success when you see it in others?  Do you know it when you see it in yourself?  Do you know when others see it in you?

These are all questions we have to answer.  If we have to answer "no" to any of them, we owe it to ourselves and our coworkers to find out how.

In many organizations, the obvious measure of success is a person's review score.  4/5 might be a great review, 153 out of 200 might be a great review.  Whatever your organization's system is, you should have a good idea of what constitutes a successful review score.

But take a moment: what things are going in in your office that are essential to perceived success but are not on your review?  In one organization, the new management team led an effort to improve the company's performance to a level that previous management teams had said was impossible.  They use that word: impossible.  But the new team did it in about a year.

The company was more profitable than ever before, customers were happier than ever before, and the company suddenly had the opportunity to take market share from its rivals.  Everything looks good, right?  This is what success looks like.  By every single measure on every person's company goals, the company was rocking.  The executive team flew out from headquarters to congratulate the team for such an achievement, they distributed awards, they met with the customer to shake hands and tell each other how great each other was.

6 weeks later, this same team, the one that had achieved the impossible, was under threat for their jobs for something that was not on their performance reviews.  No one would have guess it just a few months prior.  The team was shocked.  After all this work and success and recognition, how is it that perception could change so dramatically?  The team's performance had not changed since all the good things had happened.

For reading today's blog, you have earned a homework assignment: take 5 minutes and write down all the the negative things that could happen in your workplace.  Everything that might reflect your work in some way, no matter how remote.  Is there a report that someone could interpret to mean something that isn't correct?  Is there an individual that upper management has their eye on that maybe you should have taken corrective action with?  Is there a gap in your team's training that you haven't addressed?  What would a highly critical visitor from the home office think of your operation, and would such a visitor be able to tell the home office executive who sent her that all is well?

We'll spend the next few posts exploring these hypotheticals and what your options are surrounding them.

Friday, December 5, 2014

Blog is on hiatus for a few days

A few days of extraordinary events prevents me from publishing for a few days.  I'll be back by December 10.

Tuesday, December 2, 2014

December 2, 2014: A performance review for a high performer with a significant flaw

Let's suppose an employee on your design team is a great designer.  She is easy to get along with, works hard, and is very competent.  She hates to do any paper work.  Her expense reports are months late, her weekly project reports are late or don't come in, etc.  You know the drill.  Her goals and objectives are weighted heavily to her design work, and the entire admin side is about 15%.  She has earned high ratings for everything except admin.  Her poor admin, however, has drawn attention from your 2nd line manager, the VP for operations.

By the numbers, her review should be about 4.5 out of 5.  You feel like she should get a 2.8 as a wake up call because of this one area of poor performance.  But the numbers don't justify it.  Referencing our analogy from yesterday, her fuel pump gave out.  How do you write and deliver this review?

The first thing you do is do the review by the numbers.  It's not right to change the goals to gerrymander the result to the number you want it to be.  When you do it by the numbers, she ends up at 4.5  Given her total performance compared to her peers (who aren't as good at design work but do take care of their admin), the 4.5 does seem high.  The review then needs a second pass.  Is there a teamwork goal?  You are part of the team, and her poor performance in this one area made your work more difficult.  That one can come down a notch.  Is there something on delivering projects in a timely fashion?  If the admin can be considered part of the project, then this can also come down a notch.  In the end, although you only have 1 specific goal for admin, admin work influences many other aspects of a person's performance.

In the end, she gets a 3.8 instead of the 4.5.  This is still well above average.  The review is very repetitive, referencing these same failings in instance after instance.  You have plenty of positive feedback for her, but you need to make sure she understands how you perceive her total performance.

You meet for your one on one, and you can tell from her face that she's not pleased with the score.  You ask why, and she asks, "What else could I have better?  I thought I was really on top of it this period."

You start to go through the form (it's a long one), and you point out the places where admin brought her total score down.  You tell her that you took the time to do the review without admin impact, and the result was a 4.5.  "When you don't prioritize key business processes, it hurts you over all your goals.  If you have done your admin well, I would have been happy to give you a 4.5."  You complement her on the other aspects of her job.  Thankfully, because she is a good performer, she can take the bad news.

It is clear from the feedback from your VP, however, that a 3.8 is not much of a punishment.  She is still rated higher than all but 1 of her peers despite the headaches from the finance department with her expense reports.  The work for this employee isn't changing for the next review period.  The content of her goals shouldn't change.  In this case, it is worth it to increase the weight for her admin for the next review period.  You explain your plan to the VP, and it makes sense to him.  He is concerned, but trusts you.

At the goal setting session, you explain the need for admin to increase as a percentage of total score, and your employee understands.  She's not happy because admin is only 10% of her time, but now it's 30% of her review.  She understands that the purpose is to focus on it so she'll do it.

You have other options, of course: disciplinary action, move to another department, change job duties, decrease the admin burden.  But she is good in her current role as long as she fixes this little thing.  There is no reason she can't or won't.  You now have to follow up and help her be successful.

Just about every employee has an Achilles heel: poor emotional control, low work quality, tardiness, late work, making promises that he can't keep, etc.  The review process allows both you and the employee to put these weaknesses under the bright lights, examine them, and take some action.  If done properly, it will deepen the trust in your relationship and enable a partnership for improvement for both of you.

Monday, December 1, 2014

December 1, 2014: Ubiquitous Goals

I hope your Thanksgiving and the long weekend went well.  It was nice to take a little break from the blog; at the same time (or 4 days later), it's nice to get back to it.

It is nearing the end of the year.  For some companies, it's time for annual reviews.  In honor of one of management's least loved essential functions, the next few days we'll discuss performance reviews.

In most large companies, the Board decides the direction of the company with input from the company's top executives.  Those executives' goals might read: "increase stock price by 3% per quarter" or something similarly overarching.  At the level of the VP, that 3% share price increase goal might mean a 6.5% market share increase for Widget Zebra.  Below the VP, that market share increase goal might mean the manufacturing line has to find a 15% cost reduction so the sales team can decrease price without sacrificing margin.  The 15% cost reduction goal, when taken to the operations level, might mean reduction in overtime.  It might mean lowering product defect levels.

In the perfect world, every goal on your review can be rolled up the line to the people leading your organization.  It's commonly called "goal cascading", because as the goal descends each layer of management, it is spread out a bit to show a level of detail that is actionable at that level.

We don't live in a perfect world.

The vast majority of management professionals are 1st line managers: the people who supervise the people who are making widgets, writing programs, giving medical care, serving coffee, selling cars, etc.  Many of these peoples' goals will be things that simply don't change, no matter what the executives' goals are: employee safety, paperwork accuracy and timeliness, producing a certain amount of work, training, and a few smaller categories.  One could argue that without these ubiquitous goals, the company would not be able to achieve its share price increase.  Over the long term, that may be correct.  In the larger scope, however, these are things that just have to happen for the business to run.

If we consider the business to be a car, these ubiquitous goals are like the fuel pump.  If you want your car to go faster, you change the exhaust.  You add a turbo charger.  You increase engine displacement to increase horsepower.  The fuel pump?  You just leave that there.  It doesn't need to be improved; it just has to work.  without it, nothing else matters.  An organization that cannot achieve success with these quotidian goals is unlikely to achieve a more specific (increase share price 3%) goal.

How much of your review (and those of your team) should be based on these fundamental goals?  Views vary widely on this, and there is not a single correct answer.  Let's look at a couple of them.

Safety is #1 at your company, right?  So safety should be the most heavily weighted goal.  No?   Not where you work?  I have been lucky to be exposed to an extremely safe work environment for a very long time.  Safety goals ranged from 5-15% in weight, with the expectation that everyone would work safely and that an avoidable incident would weigh negatively but a perfectly clean safety record for the period would result in a "met target" rating.  Similar for admin.  Timesheets, regular reports, work logs, request for quotes, invoicing, all of these could fall in a single category.  In my industry, these kinds of ubiquitous goals usually roll up to about 20%.

The other 80% will be composed of larger, customer-visible goals, internal team goals, and employee development goals.  We'll discuss each of these as we consider goal setting.

How much is the appropriate weight for these ubiquitous goals in your team?  It may be different if you are managing a call center vs a graphic design department vs a restaurant vs a warehouse vs an elementary school.  Take a few minutes to write them out - all the things that a customer won't see or notice, and that won't get anybody a company award, but has to be done anyway, just as a matter of course.  Also take a moment to think on what you are managing with these ubiquitous goals: you are managing the company owners' resources.  How much of that focus should enter into this calculation?

Tuesday, November 25, 2014

November 25, 2014: So you are a manager. What do you manage?

When a person becomes an engineer, she knows what she is engineering.  She is an industrial engineer, a mechanical engineer, an electrical engineer, a chemical engineer.  Many (possibly most) managers do not have a degree in management.  So you're an architect who is a manager, or a graphic artist or teacher who is a manager.  What do you manage?  What does the word even mean?

To answer the question, we have to step back from the situation at hand and consider your workplace.  Look around you.  Is the computer on the desk yours?  Do the people on your team work for you?  Do their paychecks come from your bank account?  What, in your immediate work environment, belongs to you?  A quick inventory of mine shows a desk drawer full of fun size Snickers and some pictures of my family on the cubicle wall.  That's all.  And yet I'm a manager.

So who owns the things I'm managing?  My company does.  But can a company own itself?  No.  Every company is owned, in the end, by people.  These people are called shareholders if the company is public, owners or investors if it is private.  These people own the company, and by extension, "my" work computer, the employment of "my" team, "my" cubicle, "my" company car.

Now, what am I managing?  I am managing the resources of the company's owners.  My job, then, is to manage these resources (they could be paintbrushes or software experts or race cars or teddy bears) on behalf of the owners.  Why do they entrust me with their money and resources?  Because they believe I can provide a return on their investment because of my expertise.  That's my value-add.

Managers (every single one of us) are not managing teams or projects or anything else that we touch every day.  We are managing the company owners' resources.  It is our responsibility to do our best to return value to them - that is what they pay us for, after all.  A hedge fund manager is very close to this idea.  Is the manager of your local TGI Friday's aware of it?

It is important to note that company owners don't always know what they want.  Do they want to show growth quarter-over-quarter?  Year-over-year?  Are they in it for the long term?  The answers to these questions will come through the executive management team and trickle down. I worked at a wholly-owned US subsidiary of a Japanese company that was part of a huge conglomerate.  To trace ownership back to a person, I'd need to trace my management chain up 4 levels to the CEO, then to the board of directors of the Japanese company, then to the board of directors of the conglomerate, and then back to millions and millions of shareholders.

Somewhere along the line, the message came to the US subsidiary that we needed to make our revenue projections every fiscal half.  My team was an integral part of recognizing revenue for my company: we did the last $100K worth of work that allowed the company to recognize $20M in revenue.  So my job as a manager was to get my technical team the resources they needed to move their work forward so the company could recognize revenue on time and meet shareholder expectations.

This longer and wider view of the manager's role is vital to planning and successfully executing our jobs as managers.  Should I send my lead person out for training if the training may not pay off for a year?  Or should I manage for the short term, and keep him available for today's work?  Even if I have approval to hire another person for my team, is that in the best interests of the company's shareholders?  Or will it be a waste of their money?  I have found that keeping these questions in mind helps me to avoid making decisions that will cause pain later.  If I see a reduction in force coming, and someone transfers out of my team, I won't replace him even if I have authorization.  I'll inform my boss of what I am doing and why, and then when the RIF comes, I will need to make 1 less very hard decision.  In the mean time, I've saved the shareholders money.  If it looks like we're going to be engaged with a certain customer for a long time, I'll invest a year of being very tight with manpower so I can send them to training and reap the benefits of that training long term.

So take a few minutes to write down the goals your company's owners want you to achieve.  If you don't know, as your supervisor.  If she doesn't know, ask someone else.  Someone has to know, and the more people who do know, the better your company will operate.

Monday, November 24, 2014

November 24, 2014: Slow Week at the Office?

You have arrived at the office, the Monday of Thanksgiving week.  You have a lot to do, I know.  You always do.  But it seems like every stakeholder, every decision maker is gone this whole week, and normally smooth business processes, you know, will stall until next week.

So you have time at the half-empty office to fill.  What to fill it with?

First, you know that anything you do can't rely on anyone else to complete the task.  No approvals, no help with an IT system (although that department is most likely to have good coverage), nothing that will directly impact anyone outside your team.  What can you do that will positively impact your team, both up and down the management chain?  Here are some suggestions.

1) Build a tool to increase your knowledge and understanding of the business.  You get reports on your unit's performance through SAP or Crystal Reports or some other form of business intelligence.  But they don't tell you exactly what you want to know.  So build a tool that gets you the information you need.  I have seen managers build tools that model how busy each type of equipment is in a factory so they could forecast future periodic maintenance activity, or a financial tool that let him modify the number of people in his contract to maximize profitability without killing functionality, or a tool that tracks performance reviews for the team along with their raises to assess if he was really doing a good job at "paying for performance" like he was supposed to.  These are something you might show your boss at some point, but they key thing here is that they will help you to understand your operation better, and that will improve your performance.

2) Do some analysis to share with your team about their performance.  Perhaps you will do an COGS analysis and break it out by category, do a little drilling to see what potential savings are there.  You could share your analysis with your team to see what ideas they have about improving that metric.  Or perhaps your company is in a tough competitive market, and you can do some research on the competition.  Again, you can share this with your team at a later date and solicit their input on how they can impact your company's performance.

3) Learn something!  Always wanted to know how those Excel nerds write VBA?  You can, too!  It's not that hard, and Microsoft has free lessons online.  You local library or your college library almost certainly has access to business articles and research journals.  Do some reading on a topic that you are curious about.

4) Get ahead on an upcoming project.  Performance reviews due by the end of the year?  A budget due Dec 12?  Annual strategic plan due by Jan 15?  Get started now.  Even an outline is something.  If you take some solid first steps now and need to step away for a week, you will likely be surprised at how quickly it falls together when you come back to it.  The subconscious will work on this kind of stuff in the background; the results can be amazing.

5) Spend 1:1 time with the members of your team that are available this week.  They are probably having a slow week as well.  Do some coaching, get to know them better, see how you can help them and then follow up.

You already have a list 100 miles long of things that need to be done yesterday.  We all do.  A week like this one can let you get a little bit ahead.  Don't miss the opportunity.

Thursday, November 20, 2014

November 21, 2014: It's Time to Make a Decision

This is part 7 of a 7-part series on the hiring process.

Who screens the resumes?  Who sets up the conference room?  Who calls the candidates to arrange for interview times?  How long is the interview?  What questions will each person ask?  Will there be a skills test?  Who is in the conference room?  Is everyone in the room a decision-maker, or does 1 person get to make the call?  If it's a cross-departmental team, can a person not in the relevant department have a real impact on the decision?

A million questions, each with its own answer.  Many companies assign HR to be directly in the selection process, either as recruiters looking for candidates, or screening candidates.  HR may make or find a vendor to provide a recruiting training.  Most companies will have a single person screen candidates.  The final interview will most likely be a panel interview.

The best panel interviews have the following qualities:
1) All of the interviewers want to be there
2) All of the interviewers either have a lot of experience interviewing together or they have discussed roles and expectations before the interview starts
3) The decision-makers know in advance who they are
4) ANY decision-maker can veto a candidate for any legal reason
5) The panel has agreed on a set of questions to ask
6) The panel has a high degree of trust in each other

When a candidate leaves the room, the hiring manager (who may be the direct supervisor of the candidate or the supervisors boss) owns the conversation.  She will first do a quick survey.  Usually the panel will know just by body language about an obvious dud.  For the candidates that bear consideration, the hiring manager first has to assess the team's opinion on this central question: can the candidate do the job?

If the answer is yes, then the only question left is, "Is this the person we want to do this job?"  #4 above is the key to making this a useful discussion.  As we discussed in the first post in this series, the decision to hire someone is a momentous decision for a company.  Even if you do it 10 times a year, each one has large fiscal and performance impacts on your organization.

That you have a panel is the most important thing.  The second most important thing is #4 above: the veto power.  Maybe that one person picked up on something that no one else did.  Maybe that one person is wrong.  But what if he's right?

In a panel interview several years ago, we interviewed someone we had known for years.  We knew for a fact he could do the job.  At a previous company, he had reported to a member of the interview panel.  He presented himself well in the interview.  He was obviously capable.  There were questions about his personal behavior and interpersonal relations that stemmed from a few of our previous experiences with the individual at his previous company.  But if we had not known him from then, he would have been a solid candidate.

I was not in favor and said so.  Another manager said the same thing.  But we both also said to the other individual in the room, "If you want him anyway, go ahead."  We hired the guy.  In 6 months, we had fired the guy.  All of our predictions about how it would roll out came true.  In other cases, we have had a single individual veto a candidate.  The person just said, "I didn't like how he said..." and that was it.  We moved on to the next candidate.

Is this fair to the candidates?  Maybe not.  But that's not the hiring manager's responsibility.  The hiring manager is responsible to get the best person for the company, period.  The company provides parameters, the manager finds the best person she can to fit those parameters.  Once someone is trusted enough to be on an interview panel, she is trusted enough to wield a veto.

The best panels are also decisive. If the screening process is done well, there will be 5 or so final candidates to interview.  In the best situations, the panel will tell the hiring manager, "We like these 2-3 candidates.  Your choice for which one you pick."  The panel is then done, the hiring moves forward.

During the process, a good manager will take notes.  Why did I choose this person to interview and not this one?  Why did I choose to hire this person and not this one?  What did I notice during this interview?  Once you hire someone, watch her performance.  Should the interview have given you clues?  When you make a bad hiring decision, and we all do, good notes from the hiring process will help you to not repeat the same mistake.

Wednesday, November 19, 2014

November 20, 2014: Weighing Other Factors

This is part 6 of a 7-part series on the hiring process.

So far, we have discussed education, experience, attitude, and fit as they relate to the hiring process.  These are all essential aspects of any hiring decision.  There are some other aspects that are not relevant in every decision.  This post is by no means exhaustive, it only seeks to bring up some things that may be relevant so that when you are faced with a hiring decision you can ask yourself the right questions.

Reasonable accommodation.  The law requires that employers make reasonable accommodations for employees that meet certain criteria.  If the job you have is a desk job and the applicant is in a wheelchair, it is easy to make a few changes in the cubicle furniture to make that work.  If the employee is a Muslim, it is usually easy to provide an opportunity for the employee to pray at certain times during the day.  If the employee is a Christian whose religious beliefs preclude working on Sundays and you run a 24 x 7 operation and the opening you have requires work on Sundays, you are in a gray area.  You may have a bona fide occupational qualification (BFOQ in court rulings) the means you don't have to make that accommodation.

It is important, then, to discuss work schedule and work environment and ask the candidate if she is willing and able to do the job as described.

Pay.  No employee wants to take a pay cut.  And those who are savvy at all know that there is wiggle room in your initial offer.  Get a sense of where the employee was at his last position, and what he's expecting you to offer.  If the 2 sides simply can't meet, don't waste your time.  If he's asking for $45/hr and your approved pay range tops out at $30/hr, put the number on the table before he leaves.  Don't waste your time negotiating if the 2 sides won't be able to agree.  Generally, the company will have a fixed COGS for all employees' labor of a certain grade or a certain employment type.  In budgetary terms, it does not matter to the company if you're paying someone $31/hr or $33/hr as long as those pay levels are both in the approved pay grade.  When a candidate comes back and wants a higher pay rate, it's usually a small amount ($1-$2/hr), and the company doesn't really care.  Your decision is that if you pay someone a certain amount, it is likely that someone experienced on your team is making less.  Word will get out, and certain members of the team will feel slighted.  That's why the decision is important - it comes back to fit, essentially.

Ability to work OT.  Almost every candidate will tell you she will work whatever hours are required to get the job done.  A very good candidate will tell you that she has to leave on time to pick her children up from day care but can come back after she gets them home to her husband.  Some people are really attached only to work.  There really isn't a good or bad answer to this question, unless you know that you'll require a lot of OT or the schedule doesn't have a lot of flex in it.

Long-term career plans.  A common question is, "Where do you want to be in 5 years?"  You can assess a candidate's career path by his actions to date and his trajectory at the moment.  If you are hiring for a technical writer who wants to be in management, but the individual hasn't done any management training, it tells you something about the candidate.  Each person's story is unique, and it's worth a couple minutes in an interview to get a sense of where the candidate would like to end up.

Personal appearance.  Jewelry choice, clothing choice and condition, hair style, fingernail length, etc: these each tell a story.  While going Sherlock Holmes on a candidate is living on the edge, you can tell a person's eye for detail by how they look.  You can get a subtle sense of if the person is there to work or is there to be noticed by how he looks as well.  Is the candidate comfortable in the interview clothing?  If not, maybe this is a one-time act.  I don't read too much into this as an interviewer, but when I interview for a new position, I always dress carefully.  The shirt should be dry-cleaned so it's pressed nicely.  Pants have creases, belt matches the shoes, shoes are shined, etc.

First impressions are hard to overcome.  If you are not a tattoo-oriented person (I am not inked, and don't understand the attraction), be aware that competence can be hidden.  Recognize your first impression for what it is, and except for the obvious and objective things it tells you ("this person has ear gauges" is objective) do your best to understand the person beneath the first impression.  It is true that taller people make more money and are more likely to be promoted.  Attractive people (women and men) are also more likely to get paid more.  Don't be the manager that hires someone because he is attractive.  Be the manager that finds competence and desire inside the person across the table from you.

And there are a million more things you can watch for and ask about.  Be holistic in your approach.  As you gain experience with hiring, you will notice which decisions were good ones, and which were bad.  If you are careful, you'll learn from your hiring mistakes and not repeat them.

Tuesday, November 18, 2014

November 18, 2014: The Slippery Slope of Fit

This is part 5 of a 7-part series on the hiring process.

Your candidate has met your qualifications, has the experience you want, and shows the right attitude.  Actually, 3 of the 10 people you interviewed meet these criteria.  What would differentiate between them?

The concept of fit is poorly defined and often discussed.  It is essentially the answer to this question: When the individual joins the team, will his ability to interact with the team hinder or help the team?  There are 2 main schools of thought on fit.  One is that all team members should be alike to reduce friction.  The other is that each team needs to have certain capabilities, and adding a new team member should add another capability or enhance a capability that already exists.  Like a pair of jeans is not all denim, you need people who are the stitching, the buttons, the zipper, the rivets, to make a complete team.

There are managers who prefer to have their teams not question them.  To them, a team player is a person who does what he is told, period.  These managers usually prefer homogeneous teams.  There is a value and stability to it.  In some cases, where the objective is to maintain the status quo, this is perfectly appropriate.  It is dangerous, of course, because things do change, and if your people can't talk to you about it, you'll be managing into a vacuum.  Most businesses that are successful in the long term can not manage to the status quo.  Thus, most teams who attempt to do so will find they are not successful in the long run.

Other managers prefer a little bit of rivalry, a little bit of diversity in the team.  It provides a livelier team dynamic, and it's easier to manage a team with a little diversity because everyone gets a good feel for where he fits.

Other managers prefer a lot of diversity, the more the better.  It is an open secret that many many more engineers are male than female.  Or that fashion designers tend to be women or gay men.  Or that trades such as carpentry and plumbing are dominated by men.  My teams have been engineering teams, and I would usually receive 1 resume out of 60 or so that were from a female candidate.

I am obviously of the type that prefers a wide diversity in the workplace.  If a female candidate meets my qualification minimum, I'll interview her.  One team I managed ranged in age from early 60s to early 20s in age, very diverse in ethnic background, and we even had a little gender diversity.  That team gelled more and got along better than any homogeneous team I have ever seen.  There are all sorts of reasons why, a good topic for another time.

Now, back to our question of fit.  What kind of team do you need?  Will your team be tasked with doing the exact same thing day after day?  Is there a personality profile that all very successful employees have who do that job?  Does your team have set of tasks they must be able to complete, but not know from day to day what they will find?  What personality types might do best in that circumstance?  Or is your team completely self-directed, creating something out of nothing, and must improvise as a matter of course?

The more your team has to improvise, the more diversity you need in your team to be successful.  It's not optional.  If you hire people with all the same skill sets (in this finite world we live in, nobody can do everything) and they have to improvise, you will miss the creativity and leaps forward that you get with a diverse workforce.

There are many aspects of fit that used to be common 40 years ago but are no longer legal.  You can not make a hiring decision based on a person's race, gender, age (if over 40), national origin, etc.  You probably know the list already.  It is easy and dangerous to start speaking in code about these things where "energy" = youth, and "good speaker" = talks like a white person.  Do not get sucked into that trap.  There lies danger both of the legal and functional kind.  So, once you put all of these illegal and immoral things off the table, what are you left with to determine fit?

You have energy.  I once hired a white-haired man with 35 years of work experience who was switching careers.  He had more enthusiasm for the job that most of the people we interviewed.  He was qualified, energetic, and understood that he would be starting on the bottom.

You have attitude.  The person who sells himself as being dependable (but it sounds like he's plodding along) vs the person who sells himself as being a problem-solver where nothing is ever good enough.  You may need some plodders, some people who lack ambition or ability beyond the role you are currently hiring for.  You may need to bring some people into the team who have ambition or are potential leadership candidates later.

You have speaking choices.  Is the candidate happy?  Does she make a joke or two during the interview?  Is the person going to have fun bantering with the team?  Is the person, conversely, going to waste a large portion of the day bantering with the team?  Does the candidate answer questions coherently?  Does she use profanity?  Is that a plus or a minus for your work environment?

The question of fit is a tricky one.  You first have to know what kind of team you are building.  Once you have a vision of that, then hire the person for the team you want, not the team you have.  As people roll in and out of your team, you will eventually end up with people you chose.  So choose your new people to make your team into the juggernaut it can be, with an appropriately diverse set of skills and abilities.

Monday, November 17, 2014

November 17, 2014: Attitude

This is part 4 of a 7-part series on the hiring process.

By the time a candidate walks through your door for an interview, she has passed at least 2 tests already: qualification and experience.  There may be others - a skills test for a administrative assistance, data entry operator, electronics theory.  The list of possibilities is endless, but every candidate will have passed those two tests.

Every interviewer has her own list of things she wants to find in an interview.  Some interviewers want to see how the candidate deals with pressure.  Some want to test the candidate to see if her skills are what her resume claims they are.  Some want to simply fit the job requirements to a candidate's skills and move on.

Of all the things that may become apparent in an interview, attitude is the single most important thing.  As long as the candidate passes the initial screens for qualifications and experience, attitude almost always determines the rest.  If a candidate is simply unable to communicate well, or is slovenly, or in some other way shows that he has unable to function to the position's social requirements, he will fail.  But those kinds of failures are infrequent.  Attitude drives the decision in most cases.

You've heard the adage "Attitude determines altitude"?  Yes, it's cliche.  And it is also true to a certain extent.

Attitude is key because attitude determines potential.  In a previous post I wrote about how I would much rather have someone with a longer learning curve and higher potential than a short learning curve and lower potential.  How does attitude determine potential?  What qualities does an attitude of success have?

1) Willingness to take risks.  Educated, reasonable risks.  If a person does not take risks, he will never achieve greatness in anything.
2) Drive to succeed.  In your business, "success" can be anything.  Sales performance, quality artistic output, great industrial design, delivering all packages on time without damage.  Whatever it is, the individual has to be internally motivated to succeed.
3) Engagement.  The candidate must be interested and engaged in your endeavor, whatever it happens to be.  Candidates should always have some questions for you.  The best employee ever to be on my team was extraordinarily engaged.  If there was something he didn't understand, he'd ask until he did understand.  When I gave him an assignment, he'd bring me a proposal of hoe he would accomplish it and ask for my input.  I'd give him suggestions, we'd go back and forth, and then he'd go away and finish it.  And then he'd ask for something else to do.
4) Team-centered thought process.  There are many very smart people in the world.  Not all of them are willing to do what must be done to accomplish the job.  I knew a manager once who was working on a large project.  It became clear that the project was under-resourced.  No additional resources were available for this highly specific task.  So he put on his boots and got to work, turning wrenches and wrapping parts, doing what he could to help.

I place very little value on a "good soldier" attitude.  Employees who are very obedient are also unwilling to take a risk.  Risk is required to grow, and companies that don't grow, die.  An obedient employee is unlikely to tell me when I'm wrong.

These attitudinal traits are all leadership traits.  When you filter for these traits in particular, you run the risk of having 8 people on a team who all want to be a team lead.  Some will relish the competition and being surrounded by competence.  Some will realize that their chances for a leadership role may take a while to develop, and they will leave.  Hiring this kind of person may increase your attrition rate.  It will also deepen your potential leadership pool, drive your team to a completely different level of performance, and allow you to achieve far more than the bare minimum a less-motivated team will achieve.

Attitude determines potential in one simple mechanism: a positive, results-driven attitude leads the individual to learn and grow.  Anyone lacking a positive results-driven attitude will only ever be able to what he is trained to do, as opposed to what he is capable of doing.  And wouldn't you rather have someone who is achieving everything she is capable of instead of only what you have told her to do?


Friday, November 14, 2014

November 14, 2014: The Value of Experience

This is part 3 of  a 7-part series on the hiring process.

Let's take a moment to think about John.  John barely finished college, but he got a good degree when he did so.  He got his start in an entry-level position, and was trouble from the moment he walked in the door.  He complained a lot, did not follow through on his commitments, and he seemed to have started looking for a new place of employment the moment he walked in the door.  His performance when he was being productive was great; it was the intangibles that he lacked.  In about a year, it was clear to him that his supervisor was not enamored of him any more, and he made good on his threat to find another job.

The next place John landed found a similar situation.  John had a little experience, which was good, but his personal behavior was still less than optimal.  After 2 years, this position ended in the same way.

John goes looking for his 3rd position.  He meets all of your requirements: a degree in cupcake theory and evolution, 3 years of experience using that degree at competitor companies.  By the qualifications benchmark, he is an instant and perfect fit.  He interviews well: he is smart, charming, competent.

You have no idea about his poor work history, and no way of finding out.  How much value do you put on his work experience?

In many cases, a hiring manager will lean heavily on industry experience.  Most of my involvement in hiring has come in the way of hiring individual contributors.  After making dozens of hiring decisions and noting how they worked out, my experience tells me that work experience makes very little difference.  Here's why.

1) Just because another company made a decision to hire someone doesn't mean I should accept their decision.  They may have made a bad hiring decision.  Or the candidate could have been the prior manager's nephew.  The simple fact that someone was employed before is not in itself a qualification.
2) No matter how skilled the candidate, there will be a learning curve as she adjusts to a new company, new customers, and the new company's specific business processes.  This learning curve may be shortened by someone with relevant experience, but not eliminated.
3) For the right candidate, investing a year in training can pay off hugely.  Do I want an experienced person who has a 3-month learning curve but a 1-year career ceiling?  Or do I want someone fresh with a 1-year learning curve and a 10-year career ceiling?  For almost every hiring need I have seen, the individual with a 10-year career ceiling is the better bet.

Is experience important?  Sure.  Someone who has done a specific job for a long period of time is probably competent at that job.  Experience, however, is just a starting place.  The individual will come into your company with a set amount of it.  The individual has her entire career ahead of her, though.  Most of her experience will come as part of your company, and certainly her experience in your company is going to be more relevant and helpful than her experience somewhere else.

Evaluating experience, however, must come with an evaluation of the individual's future potential and contribution.  I will gladly hire someone with high potential and little experience over someone with high experience and little potential for growth.  I don't recommend this for every hiring situation that every manager will ever see.  It is important, however, that all hiring managers put proper value on potential vs experience.  Whatever you choose will have a lasting impact on your company.

Wednesday, November 12, 2014

November 12, 2014: The Value of Education and Qualification

This is part 2 of a 7-part series on hiring.

A job posting will nearly always have a set of criteria a person needs to meet to be qualified for the job.  The implication is obvious: if a person does not meet all of the criteria, the person is not able to do the job.  In practice, however, qualifications also include some nice-to-haves as well.

Does a manager of engineers need to have an engineering degree?  Or does he need a management degree?  Don't say he needs both degrees, because there aren't nearly enough people with both degrees to fill all engineering management positions.  Many of those people, obviously, are doing a fine job without one or the other (or both) of these degrees.

The qualifications argument also has another implicit assumption: that the institution that provided the qualification did so in a way to ensure that the individual actually learned the concepts and can apply them.  How many high school graduates do you know who have trouble reading?  Or college graduates who can't write well?  It is safe to assume that there are marketing grads who can't market, design grads who can't design, and MBAs who can't work their way through a balance sheet.

So what, then, is the value of education and qualification to a potential hire?  Setting out a list of requirements or qualifications has the following benefits:
1) It narrows your candidate pool.  When the list of requirements is steep, you may get fewer applicants for your opening.  I know one tech company who lists "a bachelor's degree" as the only qualification for engineering or management positions.  This widens their candidate pool, which has certain benefits.
2) Long-standing requirements for a team of people will mean that, over time, the skills of each member of your team will compliment each other.
3) A set of qualifications gives the candidate a specific lexicon that may be important.  Does your candidate need to know about ROI and gross margin?  Or should she know about spherical aberration and astigmatism?  Or Lean 6 Sigma?  Or the interaction of covalent bonds in a protein?
4) It shows the candidate understands the value of learning and was able to stick it out.  To me, this is the key to education.  A person who has finished a degree shows that he understands the long game, is willing to invest in his own future, and carries through to the end.

Those are it - there are people without engineering degrees who can engineer, people lacking business degrees who can business, people with no formal education in teaching who can teach.  We all know people who display competence outside of their area of formal education.

When you are making your hiring decision (but hopefully before you even post the job), you need to decide which things are requirements (qualifications).  The bar for setting a requirement is high: if the person does not have the requirement, she is not able to do the job.

When you interview a candidate for a technical position, it is important to probe a bit.  Have someone in the room who is a subject matter expert on your requirements.  I once interviewed a potential engineer who claimed to speak Japanese.  Impressive for someone wanting to join a Japanese company.  So I started speaking Japanese to him.  He looked at me in shock (I don't look Japanese), and said (in English), "I only know a little."  He didn't make the cut.  His engineering skills were fine, but his honesty was questionable, a risk we did not need to take.

We have to rely on qualifications and education more as we consider candidates without much in the way of work history.  These become less relevant the further along the individual is in his career.  A person with a degree in marketing but a career in equipment maintenance might be a better fit for a maintenance position than a marketing position.

In summary, qualifications tell you something about a person; not nearly enough, certainly.  So give qualifications some serious weight and consideration, but don't let that be your deciding factor.




Monday, November 10, 2014

November 11, 2014: The Critical Decision to Offer Employment

This is part 1 of a 7-part series on the hiring process.

As a manager, there are few decisions that impact your team's performance more than who you choose to put on your team.  Ponder that for a moment: every single thing your team accomplishes is dependent on someone (you or another manager) deciding to offer employment to those team members.

The ramifications of the decision are enormous: remember that problem employee, who was just competent enough to not get fired?  Or the employee who did the work of 2 of her peers with better quality?  Or the employee that was late just often enough that you had to choose whether to follow policy or let it ride, and either way was painful?  Whether a good decision or a bad one, the decision to offer someone employment is nearly impossible to rescind until it's too late.

What are the bad consequences of a poor hiring decision?  Let's assume that you made a reasonable mistake, not a disastrous one.  You're more competent than to make a disastrous hiring decision, aren't you?  Of course you are.  Your new employee fits the job description - he is qualified for the job with requisite experience and education.  You find that he never hears something right the first time.  At first, you put it down to you and he adjusting your communication styles, and maybe they don't match.  Then you hear from a team member that she is having the same issue with him.  Okay, you think, he's not a good communicator.  Then he finishes his training process, and you task him with something solo.  Something simple and important, to build his confidence.  He messes it up, and someone else has to fix it after bringing you in to assist.

The employee is earnest and apologetic.   He wants to get better.  You can envision this scenario, no?  I have seen in personally.  I realized about 2 months after hiring an employee that I had made a mistake.  He did not have the seriousness about the work that he needed, and his actions, while not egregious, were not acceptable, either.  My company required documentation, a performance improvement plan, and a period of time for the employee to fix his poor work habits.  3 months later, we finished the process and terminated the employee.

In the mean time, my company had paid him nearly 6 months in pay for his training and early work effort.  My team had paid the opportunity cost of not being able to train someone competent (senior staff members were wasting their time training the new employee instead of training someone who would stay).  I assigned him to work short-term with a closely aligned team, and they were unable to trust him to complete tasks correctly, so it cost them time to fix his mistakes or to do the work of the extra guy on the team who wouldn't pull his own weight.  Cost to the company?  Close to $100,000 when you include travel costs, pay, benefits, and time that senior people spent to train him.

A good hiring decision, however, shows up very quickly.  Good new employees ask questions, provide innovative solutions to nagging problems, and look for ways to contribute.  They do consistent, good work.  They make everyone around them perform better as well.

Training on making hiring decisions is hard to come by.  Good training on the topic may not exist.  I have never seen any.  So how does a person learn how to make this critical decision well?  The hiring manager (or the new employee's immediate supervisor) has to consider 5 things:

    1. Qualifications/education
    2. Skills
    3. Experience
    4. Attitude
    5. Fit  

We'll discuss each of these in the next few posts.

Sunday, November 9, 2014

November 10, 2014: Looking for Lessons in All the Right Places

Imagine yourself as 13 year-old middle school student.  You were assigned to read To Kill a Mockingbird and write a short book report.  The report is due tomorrow, and you don't even know who Boo is.  You go to your mother in a panic.  "Mom, I have a report due tomorrow and I can't get it done!  I'm going to flunk!"  Your mother sees your panic and decides to relieve it.

"Don't worry about it, dear," she says.  "I'll write it for you."  You thank her and go to bed.  When you wake up, there is a nicely printed book report with your name on it.  You turn it in, and get a good grade.

What did you learn from the experience?  I asked this question to a group of teenagers recently.  "Nothing" was the first response.  I challenged that answer.  "Why do you say that?" I asked.

"Because you didn't read the book, so you didn't learn anything."

"You learned that you got a good grade," another one piped in.  A boy in the group raised his hand.

Ed is usually the quietest person in the room.  I turned to him.  "Yes, Ed?"

"You learned that if you don't do it, your mother will do it for you."

None of the answers were wrong.  They all made sense.  But the rightest answer was Ed's.  It was an unintended lesson on the part of the parent, who intended to impart that she loved her kid.  These unintended lessons are often the most important.

We give unintended lessons all the time.  If a peer refuses to compromise in a reasonable way, and we cave in to keep the peace, we have taught a lesson both to ourselves and the other party.  We have taught her that we don't believe in our position enough to fight for it.  If our supervisor demands we do it his way and no other way, despite the existence of a viable and obviously superior solution, our supervisor has taught us that he cares more about obedience than performance.  And we have learned that following is better than thinking.

These are all unintended lessons, and you may have noticed that they all share a similar trait: while the intended lessons are specific (the issue that we cave in on, the direction we got from our boss), the unintended lessons are global and affect the quality, quantity, and type of our work in a holistic way.

A few years ago I hit a thorny patch at work; I was stressed to paralysis and didn't know what to do.  I started to set aside time during my work week to reflect.  What things happened this week that I didn't like?  Why did they go that way?  What did I learn from the experience in a holistic way?  What did I teach someone else about me through the experience?  What do I need to do in the future to unteach an unintended lesson?  This practice helps me keep stock of where I am, uncovers the hidden stressors in the office, and helps me to plan for the future.

What unintended lessons are people in your life teaching you?  What are you teaching them?  If you ask and reflect carefully, patiently, and openly, you may be surprised at the answers you find.

Friday, November 7, 2014

November 7, 2014: Using Power vs Pressure in the Workplace

Today I was working with a concrete saw.  My brother's house is under renovation, and today I was helping by running the concrete saw across his 20' long patio.  We're going to remove it and add a french drain to keep the basement a little drier.  The saw was a nice one - a Hilte, gas-powered, outfitted by our local home improvement store with a brand-new diamond blade.  I had never cut concrete before.

As with any saw, the power supplied by the motor is not infinite.  It also cut more or less quickly depending on how quickly the blade was spinning.  When I pushed it along, the blade had to cut more material all at once, it slowed at first, and then stopped.  Then I had to back off and go for the same section again.  When I kept the blade spinning very quickly (lots of motor power) and applied little pressure, the saw went much more quickly.

The lesson can be illustrated in the following situation:

I have 3 people on my engineering team: A is very good with interpreting data but bad at putting all the screws in all the right places when he is working on equipment.  B is great with physical detail, but terrible with data analysis that is not visible on the machine in front of him.  C is mediocre at both.  I have a serious new problem with a piece of equipment and all 3 engineers are up to their elbows already with previously assigned tasks.  I know there's a problem because a graph tells me something is wrong.  I don't know what.

In this situation, it is obvious that A is the right person for the job.  But I'm in a hurry.  How do I increase the chances that the problem will be fixed in a timely manner?  I can apply pressure by standing over A and telling her over and over again how important the problem is.  Or I can apply power to A by asking what she needs from the rest of the team and giving it to her.  In most cases, I will get a better (=faster, more accurate) result by giving A the resources she needs.  Power.

With my saw, power showed up in increased blade spinning speed.  I had to let it rev to its maximum RPM, and then I could get the most out of it.  If I applied pressure, the blade slowed and stopped, and I accomplished nothing.

There are many ways of thinking about power and pressure in team environments.  Power can come in the form of budget approval for a consultant to provide training, or a project sponsor clearing a way to modify a business process to make something easier to do.  Pressure can come as peer pressure to do something a certain way, emphasizing a deadline, or micromanaging a situation or employee.

I am naturally a power manager, not a pressure manager.  Pressure is certainly needed at times (a timely and appropriate termination can improve a team's morale and up its internal motivation, for instance), but many managers overuse it.  Take a few moments to think about situations where you had to change the dynamic of how your team tackled a problem: did you apply pressure to the individuals responsible?   Did you apply power to them?  How did they respond?  Was it the response you wanted?

It's a fine line to walk, one out of many judgment calls that managers have to make daily.  Knowing which side you are on can help you to understand when it might be better to take a different tack and possibly get a different outcome.

Tuesday, August 12, 2014

August 12, 2014 - a Brief Update

Hello, legions of readers!

The blog has been silent for a few months.  The main reason is this: somewhere in there, I lost my employment.  Like most honest and competent employees, my life revolves around my work to a certain extent.  Plus, the primary activity I've been engaged in is a job search.  For many reasons, one of which is the likelihood that a future employer finds this blog and reads it, it seemed wise to keep quiet.

But life has moved on despite my lack of time spent recording its twists and turns.  So here are a few neat things and thoughts from the last few months.

 We had the first real poison ivy incident in June.  Looks like Christian is not immune.  This was really uncomfortable and unpleasant for him, we all felt bad for him.

Libby learned how to play Canasta as well.  She has won and lost, both with a sweet grace.
 I have continued my hikes on the Appalachian Trail.  I'll spare you the hundreds of photos I've taken, and just share this train station in Pawling, NY.  You can get on a train at Grand Central Station with your hiking gear on, and step off the train here, where the trail crosses the train tracks.  I've currently completed the NY section from Rt 9 near Garrison up to the CT border.  My goal before the end of the year is to complete the trail in CT, NY, and NJ.  There's maybe 50 miles left in CT, 20 in NY, and I don't know about NJ.  Haven't started that section yet.

In Pawling, there is a large boggy area, and this boardwalk takes you over it.  The boardwalk gets a little wider at one point, and there are 2 Adirondack chairs that face each others.  One is labeled Maine, the other Georgia.  I chuckled when I saw them: it was almost a physical pun.

The photos below are from a visit to Six Flags.  We bought season passes in February, and finally used them a few times.  That's it for this update.  More to come later.




Tuesday, May 20, 2014

May 20, 2014 - A quick word on marriage equality

I've mentioned this before, but I'm against bans on same-sex marriage.  While I do believe that God intended for men and women to marry, that's my personal religious belief.  One of the fundamental tenets of my church is that "We claim the privilege of worshiping Almighty God according to the dictates of our own conscience, and allow all men the same privilege, let them worship how, where, or what they may."  It is not a stretch to extend the right of worship to consenting moral questions; indeed, it seems natural and appropriate to me.

Despite my church's disapproval of legal same-sex marriage, I have not yet heard any church leaders address this apparent contradiction.

My second reason for being against bans on same-sex marriage is more selfish: we ought to be spending our time and energy on something more important!  Like drug prevention, pregnancy prevention, adoption, income inequality, anything!  The portion of the population that needs marriage equality is small, and has very little impact on those of us who already have the right to marry who we choose.  So give it to them, and let's move on already!

In that light, I just want to mention that I'm happy to be living in this moment of history.  Oregon struck down a state constitutional ban on same-sex marriage yesterday, and Pennsylvania did so today.  By that count, 19 states now have marriage equality on the books.  There are stays in some states (Fed courts are striking down state laws), but so far all 19 fed courts have struck down similar laws.  None has ruled the other way.  Soon this battle will be behind us, and we can focus on more important issues.

Sunday, May 18, 2014

May 18, 2014 - Family time!

My parents first came to town nearly a month ago.  They went away for a few weeks and came back.  Now we get them for a week, and then they go home.

We've had some fun times, so here is a photo selection of recent goodness:

Went with Libby and Jake to Philly for a day.  A photo of Liberty with the Liberty Bell, and both of them getting a carriage ride.  We had camped in PA, spent a day in Hershey, camped again, then hit Philly and drove home that night.


Jake at Penn's Landing in Philly.  Camden NJ is across the Delaware River.

In April, I got to ordain Christian as a Deacon in the church, and the next week I baptized Jacob.  Lots of good stuff happening here this month.  This is just after Jake's baptism.

 On May 1, I saw my first ever MLB game, Yankees vs the Mariners.  I went with 2 local guys (Yankee fans), 1 guy from Canada (impartial) and me (Mariners if I have to choose).  Mariners win, 4-2.  Yankee stadium is beautiful, comfortable, and the weather was perfect.  Lovely evening, had a great time.

Spring means all kinds of things around here - flowers, leafy variegated plants that I can't name, and the drive ins open up.  Our first this year was a date night for a reliable franchise: the latest installment in the Muppets.  Muppets: Most Wanted was hilarious.  A good time for all.

And of course, the pool opens.  This is our first time for the kids swimming this year.  We had some pros come out to winterize last year, and I was very careful to open the pool with minimal intrusion of debris.  It was comparatively easy to open this year - 8-10 hours of pumping out the pool cover with a pool cover pump, reassembly of the filter/pump housing, and some chemical stabilization, and we were most of the way there.  I still had to backwash 10 times or something, but now it's beautiful.  I couldn't be happier with how it's turned out so far.

 Mother's Day this year was simple.  Katrina and Aria got back from a trip to DC late Saturday night, we went to church.  We got home, I took the kids out to the pool while Katrina napped, and then Aria helped the other kids QUIETLY make cookies.  Lovely afternoon.


 I've been back on the AT a little this month.  This causeway is in the forest near Lake Canopus.  The dogwood tree is in our pool area.





On May 9, I got to go with Aria to a choral festival.  Her choir performed a few pieces, and then it started to sprinkle on the way to Six Flags.  So Aria decided we should go to the Palisades Mall instead.  We bowled at Lucky Strike, walked around, picked up some things we needed, and headed home to see Libby and Jake's talent show performance.  The performance went from 7-10pm (!).  Luckily, they were near the beginning, and we left at intermission.

 We've been working through Spring Cleanup the last couple weeks as well.  Christian discovered a Robin's nest in the pool area.

This afternoon, us men took a hike.  We went to Fahnestock State Park, and parked outside the gate.  It was closed.  So we locked the cars and walked in.  The trail we wanted leads from the cafe/restroom area at the beach and heads toward the Appalachian Trail.  The view at the top was great, and we had a nice hike together.  A lovely, relaxing afternoon.  Christian has been camping with my dad and brother before, but this might have been Jake's first time.  I need to get that boy in the woods more often.

Thursday, May 1, 2014

May 1, 2014 - A quick update

The natural environment at my house is fascinating.  It is May 1, and just yesterday I saw the first green leaves opening up on the trees in our driveway.  And we have buds on the large shrub in our turnaround as well.

In other news, our house is marginally quieter.  We have had my parents and Katrina's parents in and out of the house for the past 3 weeks, and they are all gone for now.  Katrina's parents flew home yesterday, and mine are in Tennessee for a week.  They're coming back next Thursday, will stay for the weekend, and then drive home.

During that timeframe, Christian has received the Aaronic Priesthood and serves as a deacon in the ward.  Jacob received baptism.  Much Uno and Skip-Bo was played, tickling ensued, birthday cakes were eaten, movies watched, and fun had.  Now it's back to the grindstone - school, homework, and activities galore.

For the next couple days, our family's plan looks like this: tonight, I'm going to see my first MLB game ever.  The Yankees are playing the Mariners.  Tomorrow night, Katrina is out on a girls night.  Saturday I'm driving to the Manhattan Temple with Aria, Christian, and a bunch of other teenagers.  Saturday night we're going to hit the Drive In.  I don't know if we're going to take everyone to see Muppets Most Wanted and Captain America 2, or Katrina and I will go see Amazing Spiderman 2 and another one on a date.

More musings later.  Now I must work.