jump to navigation

Create a Skills Inventory to measure overall strengths & weaknesses April 22, 2008

Posted by Darth Sidious in Business Management, Managing Employees.
1 comment so far

Say you’re in a team that specializes in using the Force to electrocute captured rebels, or run a Network Engineering team. When it comes to hiring your instinct is to focus on the obvious and primary skill of the team.

Need to fill in an electrocutioner position? Then you’re probably looking for someone who’s learned how to channel the powers of the Force into electricty. Need to fill in a Network engineer position? You probably are looking for a hardcore networking/router/firewall guy.

But look beyond the obvious and evaluate the skill sets that the team has as a whole, and identify where you are weak, and where you’re strong at. Sure it’s great to add even more firepower to what you’re already strong at, but don’t let that lead you into becoming unbalanced skills wise.

What skills you need depends on your long term staffing plan, which is related to your long term department/company/empire goals. If you want to grow, what skills will you need in the future? Growth is only possible if you have people will the right skills and personalities to achieve it.

Hiring ONLY for your needs of today is great if you never want to progress beyond today. We’re not saying ignore the needs of today, there are short term needs and they’re important, but keep the future in mind.

To assist you in this, put together a skills inventory list. It’s just a simple table of all skills needed by today and in the future, along with your staff and how strong they are in those skills. It will help you highlight where you’re really strong at, and where the weaknesses lie. So, you’re hiring strategy should try to fill in for those areas where you are vulnerable. E.g:


Category

Skill

Importance

Darth Sidious

Darth Vader

Darth Maul

The Force

Electrocuting

High

10

4

0

The Force

Psychokenetic

Med

10

10

4

Management

Empire Planning

High

10

7

3

Six Sigma

How many sick days should a healthy employee need? February 27, 2008

Posted by Darth Sidious in Managing Employees.
add a comment

2 per year. The flu only hits once a year – and worst case you’ll get hit with a fever, the peak of which lasts for only a day.

Parents however will have kids who get sick all the time, and use up sicks day for that.

So what is sick enough? Well a 102F fever or more is. Anything else, the employee can work at home if they need to. Otherwise coughing, upset stomachs, back pain, and all that… please, get back to work.

That’s why the Sith believe in the PTO system. You get a lump sum # of days, use it however you want. Otherwise allocated sick time gets abused.

Ingredients to Successful Teams – Trust February 8, 2008

Posted by Darth Sidious in Leadership, Managing Employees.
add a comment

There has to be trust between team members, and trust between staff and their manager. Without it information won’t flow properly, productivity will suffer as people go into Chess mode trying to out maneuver who they view as their “opponent”, protectionism sets in and information becomes well guarded keys to job security,  etc…

Trust comes through honesty. Being able to openly say what you have to say in a constructive manner,  being able to voice opinions without fear of reprisal, and being able to admit to ones mistakes.

Trust also needs to be earned; but the nice thing is that most people are initially willing to give the benefit of the doubt and afford another individual a high degree of trust.

Trust is also easily lost and extremely difficult to  earn back once that occurs. If a person trusts someone and that trust is compromised, it will take an enormous amount of effort to regain that trust as now the shields are up, precedence has been set, and that person will always be suspicious of that someone again. Fool me once, shame on you, fool me twice, shame on me…

Darth Sidious

The Cancerous Employee February 7, 2008

Posted by Darth Sidious in Employee Types, Managing Employees.
add a comment

The Cancerous employee doesn’t have Cancer, they ARE Cancer. They affect whatever is around them in a bad way – and overtime the cancer spreads outwards. As the tumor grows what would be healthy productive employees eventually become demotivated by the Cancerous employees around them.

Like real Cancer, the Cancerous employee is difficult to remove. They become entrenched in the organization through other people, technology, and subject matter expertise.

Getting rid of the Cancerous employee is just as challenging as real Cancer – you have to localize where the Cancer is and hit it hard, and chances are you’re going to affect good tissue (e.g. departments and teams in this case). Cancer doesn’t go down easily, it infects in as many places as possible, and it’s difficult to know where all those areas are and know if you truly eradicated all those areas.

Characteristics

  • Negative attitude.
  • Usually doesn’t collaborate with the team.
  • Hoards information.
  • Actively (even if subconsciously) demotivates others.
  • Chronically complains.
  • Sees only the negative side of any situation.
  • Unable to admit to ones mistakes.
  • Extremely resistant to change, new ideas, etc…
  • Emotionally unstable.
  • Has few allies in the team.
  • Complains about others weaknesses, even when they share the same weakness (this is because they believe that the rest of the team exists to serve them).

Recommendation

  • Like with real Cancer, you have to bite the bullet and get rid of the disease – it only can get worse.
  • Isolate him/her so that the collateral damage is minimized.
  • Cover your bases in all the areas that the person is involved in.
  • Have an extremely well thought out contingency plan in case this person leaves before you are ready.
  • Have an extremely well thought out plan to remove this person.

Darth Sidious

Should you manage your employees’ career? January 20, 2008

Posted by Tariq Ahmed in Managing Employees.
1 comment so far

Everyone knows the adage that “if you aren’t promoted in 2 years, you should find another position”. They also say the fastest way to gain salary increases and titles, is to change companies every 2 years. This of course applies to the employees who are highly motivated and have career goals. Not all employees are like this, many are quite happy to stay in the same position for decades.

The situation:

  • You’re a highly motivated professional and have been excelling in you position. You are a superstar.
  • You haven’t been prompted in 2 years and the company is content with you in your current position.
  • You’ve received small inflation based pay raises.
  • You don’t see a career path/room to be promoted in the current department/organization.
  • Your next job may be your manager’s position.

In this situation, if you’re itching for a large pay increase, direct reports or that “Senior” moniker in your title, what choice do you have? If you discuss it with your manager, you may just confirm what you already know, that there isn’t a new viable position available for you. It will also create an uncomfortable atmosphere at work, if your manager thinks your looking for a new position and will be leaving soon. On the flip side, your manager may value you, and work to give you what you want.

Now that the foundation is set, how should you as a manager handle this situation? Should you care to actively be concerned about your superstars leaving? How do you answer these questions?

  • Who is a superstar and highly valued?
  • Which superstars are highly motivated to move-up?
  • What if your organization doesn’t have available positions?
  • Do you consider your superstars as numbers, and do not concern yourself with their careers, but just with what they can do for you today?

There are 2 schools of thought on this: Have a visible career progression path for all positions. In this case, the company is active in managing career paths and retaining superstars. The other option is no policy/action from management and let the chips fall where they may. In a large and profitable company, managing careers is possible, in a smaller company; it’s very difficult. Concrete solutions? I encourage discussion on this topic.

darthvader.jpg

Identify the Owner January 1, 2008

Posted by Darth Sidious in Managing Employees, Project Management.
1 comment so far

You’ve heard the saying, “Too many Sith Lords in the Command Ship”, I think you earthlings have a similar saying of “too many chefs in the kitchen”.

Collaboration is great, and should be a natural part of your organization’s culture – but issues and confusion will arise if owners of areas aren’t clearly defined.

Whether it’s fighting a crisis, issue resolution, routine tasks, domain areas, to projects – there has to be ONE owner. Otherwise it’s unclear where information ultimately needs to flow up to, and what the chain of decision making needs to be.

Is your technical staff on-call? What if that pager goes off, but it’s not in that persons particular area of ownership or expertise? The person on-call is the owner – the owner of the alert, and they have the power to rope in the subject matter experts needed, and/or the owners of such areas. Ultimately the resolution of that alert is theirs.

On a Project, there has to be a single-owner. Don’t confuse this with sponsors and supporters of the project. The owner of the project is ultimately responsible for getting the project done.

Do you have a Database team? There has to be someone who owns the maintenance plans, data architecture, schema design, database change policy and processes, etc… It doesn’t mean they have to come up with all the ideas, and all of it could be the result of the team collaborating on what the best practices need to be. And it doesn’t mean they have to do all the work. But the owner is responsible for making sure that that collaboration occurs, gets documented, and somehow enforced.

When fighting a business crisis or a technical one – make sure the owner is clearly defined. Otherwise people are going to naturally float decisions up their management chain, it won’t be clear whose making the decisions in the first place – so you get this decision confusion that results in latency as everyone tries to sync up on who decided what.

Darth Sidious

Productive vs Active December 24, 2007

Posted by Darth Sidious in Managing Employees, Project Management.
1 comment so far

Now and then I’ll see military units such as squadrons of Storm Troopers scrambling around suspect rebel planets, or see our Software Development staff feverishly coding to make the UI look cooler.

But here’s a question that I pose to Executives, Management, and Product Managers – is such staff being productive, or merely active?

Frantic Work May Feel Productive, but is it?

To feel productive often people go into a frantic work pace, they’re motivated to get things done, and they want to bring value to the organization and themselves. But just because they’re moving quickly, firing off a ton of emails, defragging hard drives, whipping rebel prisoners, and experimenting with some new tools doesn’t mean they’re being productive.

This sort of activity should be allowed, the reason people do it is it’s a way to mentally recharge. Reasons may very, but for example they might have come off off a long and intellectually intense project, or when dealing with a particularly complex problem they need to walk away from it and focus on something else for a bit so that they can come back to it with a fresh perspective, and emotionally it helps them recharge (being able to innovate with new technologies, or tackling some no brainer tasks to feel they got a lot done, etc…).

The Difference

But, from a people management perspective this type of activity needs to be controlled as it might not be productive. The difference is productive activity is prioritized work; it’s an established effort that is aligned with the organizations mission and stated goals, has time allocated for it, and should also be line item on a person’s performance plan.

Allow It – But Control It

So, stick to the 80/20 rule here – make sure that the productive time for your people is at 80% or greater. If innovation is important in your organization – make it part of your mission and state goals, that way your allocating the time for it.

Darth Sidious

Motivating Technical Employees November 20, 2007

Posted by Darth Sidious in Managing Employees.
2 comments

Technical staff are an odd bunch; their mentality, view on life, and history are uniquely different than most other career people. One of the major differences is that technical people are into technology because they love it, and many have been doing it all their life – being able to get paid to do is just a huge bonus (though getting them to link that desire to focus on projects related to the goals of the business can be a challenge).

Similarly with the Sith, from a very young age sithlings discover the nature of the force and take an interest in it throughout their whole life.

Versus other careers like accountants, and storm troopers. No one at 10 years old is doing accounting or storm trooping. You can pretend maybe, but technical staff and the Sith are doing it FOR REAL at early ages.

Although the Empire is hailed for its ability wield great powers with the dark side of the force, we’re mostly successful as a result of our technical staff who create and support our EMS (Empire Management System) using technologies like Adobe Flex (currently version 982), and Coldfusion (version 1021).

So what motivates programmers, network engineers, and the like? Here’s a few that we’ve found that work, but would like to hear your thoughts as well.

  • Free Sith Cola, Mountain Sith, Empire Bull, Empire Star, and other caffeinated drinks.
  • Free Coffee.
  • Free snacks. The unhealthier the better apparently (donuts, cupcakes, cookies, chocolate, trail mix, space mix, etc…).
  • Free food (e.g. Pizza Fridays).
  • Support for their personal initiatives (efforts with user groups, blogs, etc…).
  • Gift cards for Sithbucks.
  • Public recognition (awards, certificates, trophies, etc…).
  • Sending them to conferences.
  • Exclusivity of technical stuff. E.g. rewarding best performing tech staff with bigger monitors, more monitors, latest versions of software, etc… Visible stuff that makes them feel superior to others.
  • Financial rewards (stock options, bonuses). However long term things like 401K matching are viewed as good, they have little impact on motivation.

Darth Sidious

Employees Abusing Sick Days November 4, 2007

Posted by Tariq Ahmed in Managing Employees.
10 comments

Studies have shown that when a company offers paid sick days, employees will use 85% of the sick days, regardless of how many are offered. Following that trend, you may have noticed a strange virus that only inflicts your staff on Fridays or Mondays. Common sense dictates that if your company offers a “use it or lose it” policy, chances are employees are going to use them.

Many companies keep vacation & sick days separate, with the argument that if they were combined, you’d have to pay for all the days, vs. sick days that hopefully won’t be completely used by everyone in the company. Many other companies are going the other route by combining vacation and sick days into 1 PTO pool. The PTO pool doesn’t have to equal vacation time + the sick days your currently offering, but a happy medium based on actual usage perhaps. Regardless of the #, since it will be less than the previous total pool, you can expect some grumbling amongst the ranks.

The Sith feel the benefits are well worth it:

  1. Employees will no longer have to lie to their manager about their Friday flu.
  2. Other employees who are working hard won’t feel resentment to the employees that abuse sick days.
  3. Productivity will be much more predictable and organized as PTO time will be planned vs. employees scrambling to use up sick time during key times.
  4. Your employees health will miraculously improve.

darthvader.jpg


11/12/07: As a follow-up CNN.com coincidentally has a non-scientific poll asking users if they’ve abused sick time. and 60% are saying they do. THAT’s SAD! And the type people who would even read CNN are probably more affluent/progressive types of folks (vs the general population).
CNN Poll on Sick Time Abuse

Performance Review Tip October 25, 2007

Posted by Tariq Ahmed in Managing Employees.
1 comment so far

When giving a performance review there may be times when weaknesses, poor scores or other negative feedback has to be discussed.  When these situations come up, keep them at a high level, and just expect the employee to listen.  Do not have expectations of solving them in the initial sitting.  Schedule a follow-up meeting 2 weeks from the original review where the negative feedback can be more openly discussed and a plan can be formulated to deal with it.

Why time is needed:  when an employee hears negative feedback, they may become defensive for obvious reasons.  Most people need time to let the negative feedback sink in.  They need to allow their emotions to go from surprise/defensiveness to serious thought and then acceptance. Time, thought, discussions and peer-feedback will help a person cope with the negative feedback   After time has passed they will be more willing to accept the negative feedback and see it as an opportunity to grow.  Hopefully by the 2nd meeting they will prepare their own plan to address the issues.

darthvader.jpg