- Whether to mention a pregnancy in a job interview
- A possible meeting protocol
- What are an end-user's responsibilities?
- Another take on opening PCs, or not
- Getting some process going
- Selling a more open environment to management
- Running an effective meeting
- Licensing rules for virtual machines
- The ROI of metrics
- Legal challenges to virtual machines
October 25, 2006 | Comments: (0)
Flip or fly
Dear Bob ...
I am an engineer currently employed by the federal government. The leader position, a non-federal job, for one of the biggest projects in my field is available. I helped in some of the organizational development for this new, multi-year, large scale project. Now the recruitment for the leadership position has started.
The non-federal managers asked me to suggest candidates for the leadership position. They also asked if my name would be on my recommendation list.
I have decision to make: Throw my hat in the ring, or stay put.
I have a great job. An almost perfect mix of technical and admin. Almost perfect. Some days are diamonds, some days are stones. Most people would covet my current position.
However, I am tempted by the new position. I am sure there is a 'grass is greener' aspect to this, as well as ego stroking. It is a premier position with great direction, budget, and support.
Question: What am I implicitly agreeing to if I throw my hat in the ring? Is a self-recommendation the same as an implied acceptance of a potential offer? In other words, if offered, do I have to accept the position? What are the ethical boundaries? What are the potential consequences? How do I take stock of my current position and the potential new position and go through a decision process? Even if I am reasonably happy in my current position, is it unreasonable to aspire to a premier position?
I know that 'He who hesitates is lost', but I am also aware that you should 'Look before you leap'. The new position will be decided 60 days from now. I need to get the recommendation in soon.
Usually when you ask for advice you are really looking for an accomplice. Will you help?
- Looking or hesitating
Dear Undecided ...
The very short answer to your core question - how do you make the decision - is simple: You handle it the way you'd handle a software selection effort. In other words, you list the selection criteria, which in this case are what about a job matters to you, weight the criteria, score your current job and the new opportunity according to those criteria, and choose the path that gains the higher score.
Here are some considerations to include. But first, a consideration to exclude is that some days your current job is stones rather than diamonds. Unless you think you can compute the stones/diamonds ratio for the new opportunity, figure every job has both (I'll leave alone the question of whether greener grass grows under stones or diamonds).
As you're thinking this through, ask yourself which matters more to you, security or opportunity. If security matters more, stay where you are (unless you see your current job being eliminated for one reason or another in the immediate future, that is). If opportunity matters more, evaluate how much opportunity your current position provides, and whether choosing to not pursue the big project might have an impact on how many future opportunities come your way.
Now ask yourself whether, if you don't pursue the new opportunity, you're going to start to coast. Unless you're ready for retirement and just need a few more years of income, coasting is death to a career. You need to put yourself in harm's way every so often, just to keep yourself sharp. So if your current job is risk-free, it's a sign you should consider the project lead.
Another consideration: Take a step back and look objectively at the project itself. Is it a good idea? Has it been chartered properly? Are the conditions in place that will give it a decent chance of success? Many people have been seduced by great projects, only to discover that while the concept was sound, the organization had set up the project team to fail.
You asked about whether it would be ethical to put your own name forward if you aren't certain. I don't see a problem. Putting your name in expresses interest. As is true of all other jobs, what follows is a two-way selection process. Those doing the hiring are selecting the best candidate. The candidates are all evaluating the opportunity to decide whether it's the best one for them.
Why should you be any exception? You need to make an informed decision. You have less information now than you will after you go through the process.
- Bob
Posted by Bob Lewis on October 25, 2006 04:41 AM
RATE THIS ARTICLE:
-

- COMMENTS
It depends on the mix and your situation.
How long do you have to go before retirement eligibility. Those close are putting a lifetime medical benefit worth 250K on the block...
Didn't you forget to mention that he should not recommend others in the last that he knows are not suitable for the job. It will reflect badly upon him if he is the only quality candidate. If you don't know of any others who qualify don't recommend anyone. The pitfalls of a bad recommendation is that the prospective employer will be and should be checking your recommendations to evaluate you.
Posted by: David at October 25, 2006 12:16 PMBut Bob, you neglect the most important part:
This guy is in the catbird seat: He's a federal employee, he does what he chooses, is courted by vendors and respected by his peers. If he takes this position, he becomes a contractor. The world of federal contracting, especially in IT, is considerably different from the world of being the government customer. Little things like cost, schedule, and functionality are considered in the black and white light of profit.
That said, the benefits are better. The raises are nice. But you rarely get to walk away after 40 hours on the contractor side of the street. And your accountable to more constituencies than you ever had before.
Going home again is rarely an option. The grass, shall we say, is always greener over the septic tank.
Posted by: Ronda Henning at October 25, 2006 12:24 PMDon't throw away your federal retirement unless you have some kind of private plan that will compensate for that. The way things are going, if you voluntarily leave service you will never get back in. That's a pretty big bridge to burn.
Posted by: George at October 25, 2006 02:28 PMBob's advice is good--read it over carefully and take note especially of the sentence 'which matters to you more...security or opportunity.'
Having had the opportunity to take the leadership position without having to leave a civil service position, I can say for sure that the people I used to work with, but now manage, make up most of the 'stony' days.
By all means, put your hat in the ring. It shows confidence to those non-federal managers. But keep your eyes on the prize - a federal job with all related benefits that come due in retirement is a pearl beyond price.
Posted by: Gene at October 25, 2006 06:33 PMYou "helped in some of the organizational development for this new, multi-year, large scale project." Uhh. I don't know about your agency, but for my agency (Department of the Interior) this could be a conflict of interest, and may be prohibited by law. Before you quit to give yourself this job, run it through your ethics office and solicitor's office. OTOH, if this is Department of Defense, well this is simply the way business is done, no problem. Just be sure it is well funded before hiring yourself.
All that is good advice and consider it seriously but if you still cannot make a decision use the "nickel" computer. Flip a coin (nickel) call it heads or tail (yes or no), then whatever the coin flip happens leave you - how do you feel about it.
Were you really disappointed that it said "yes" or were you happy it said "yes" and of course the same applys to "no".
Posted by: JonL at October 25, 2006 08:50 PMAnother factor to consider is your relationship to this new position if you don't get the job. It sounds like if you stayed put, you might be working with this new person? Given your role so far in organizational issues, if you don't throw your hat in the ring, would you have a chance to be part of the selection process for the leader? (If you do express interest, that virtually excludes you from the selection process.) If you don't get the position, how will you feel about working with someone who has a role you wanted? And working with others who may have been part of the selection process, who know why you weren't selected? If you know some of the key people who will be part of the selection process, since if you can have a candid albeit confidential discussion with them about how they'd see your candidacy (politicians do this all the time - float the idea of running, to see how others react)
Posted by: Allison Dolan at October 26, 2006 04:52 AMForget the retirement. Undecided asks, "What are the ethical boundaries? What are the potential consequences?" Nothing personal, but you're not the one to ask. Every federal agency has, by law, an "ethics counsellor." That's who Undecided should ask. What he's contemplating may well be illegal.
The short answer to the possible consequences is "jail time." He's a fed. He had a direct part in the development of the project. That may well be enough to disqulaify him from employment with the contractor for a period of several months to a couple of years. Soliciting a job with the contractor, or being solicited by the contractor, or contact with the contractor for other reasons, are all probable violations or law and regulation, and could land him in jail.
Granted, Undecided may already have spoken with his ethics counsellor, but the tone of his inquiry certainly doesn't read like it. If he hasn't, I hope he does so, and soon.
Another Federal Employee.
Posted by: Kim at October 26, 2006 09:40 AMReview the field and then, or also, nominate yourself? Why not? It worked for Cheney.
Posted by: Greg Mohr at November 1, 2006 02:06 AM|
Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account. Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them. Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline. ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings. Order your copies today! |
TOP STORIES
HP buys EDS for $13.9 billionCorporate software spending slows
MS targets smartphone market
SOA Software buys LogicLibrary
Phishers scamming IRS rebates
Sun to clarify JavaFX plan
MS' dev tool service packs
Developers' role shifting
MS: SP3 reboots OEMs' fault
Apple: iPhone out of stock
ADDITIONAL RESOURCES

- Virtualization: A Step by Step Approach to Success
- Dialing up Agility with Business Transformation
- 5 Things You Need to Know About Storage Virtualization

- Is your smaller organization ready for High Availability?
- Is system maintenance doing more harm than good?
- Virtual Test Lab Automation: Manage development infrastructure





