Tag: team building

  • Scaling Effectiveness – From Individual To Team

    Scaling Effectiveness – From Individual To Team

    Whether you are an employee, entrepreneur, contractor, or other, there comes the point where you need to scale your abilities.  We can only do so much on our own.  Thus, the need for extending effectiveness arises as soon as we try to do anything of substance.  The trick is in finding ways to train others to produce a quality that is close enough to ours.

    A Specialist Problem

    It goes without saying that this problem is one faced by specialists and those in skilled positions.  If your work is measured by time put in and the quality of your work is not a factor, then you scale by adding more resources.  Thus, we can build assembly lines of low-skilled labor and scale that to create millions of products.

    In the world of business and IT, there are very few low-skill positions (if any).  There are a few positions that are low-skilled that amount to data entry, but even those often require knowledge and experience to get the job done faster or better.  Therefore, to grow our business, we need to be able to develop our people.  We need to find ways to peel off some of the skilled labor we do, convert it to something that takes less skill, and pass it on to someone else.

    An Age Old Challenge

    Good News.  There is nothing new about needing to pass on skills to others or even the next generation.  However, we do seem to forget about that as something that requires our attention.  Our days are full, and we quickly fall into the trap of being “too busy” to think about how to delegate.  We need only look back a few decades to see industries driven by apprentice programs.  These were the first way we looked into scaling our skilled labor.

    Dissect How You Work

    The first step in delegating those things that only you can do is to examine your tasks closely.  There is often some form of “finishing touch” we put on our work while most of the functions could be done by anyone.  Even a software developer can have someone else write their code.  This procedure is quite a challenge as it amounts to putting your thoughts down in a document.  Nevertheless, it can be done, and the process is an excellent insight into delegating almost any responsibility.

    I recently wrote a tutorial on how to automate almost anything.  The beautiful thing is that this process is practically the reverse.  You have a method you follow as part of delivering a product or service.  We can dissect it by reducing it to the steps we take.  There will be steps that are hard to define like “think about the problem I am solving.”  That is ok for now.  We will parse that more another time.

    Once we have the first pass of steps, there are going to be concrete actions, and probably some “magic happens here” areas where we struggle to define our process.  Those specific actions are where we move next.

    Actions Reduce Skill Requirements

    Those concrete actions are where we can most quickly scale out our process.  The operations may require some level of skill.  However, a well-defined task can be done with more ability through practice.  We may be able to perform the work faster or at a higher quality than someone else.  Fear not, that is a temporary setback.  When we pull out that step and hand it off to someone else to do the work, we will also spend the time to review and assess their work.  This is an investment in making the worker better at the task.  At some point, we will be able to have our investment pay off in a job we can reliably hand off to another.

    Once we have a task or two pulled out to hand off, we can work on adding more to that list.  This allows us to scale as others do those tasks better (through training or experience) and as we take things off of our plate.

    Scaling Effectiveness Is That Simple

    So, we define the actions we take, find some we can hand off, and then do so.  We scale by repeating the process.  Is it that simple?  Yes, the procedure is not hard at all.  It is the definition of the tasks that is often a challenge.  Do not take my word for it.  Where are you invaluable to your job?  Spend some time to find at least one task you can hand to others and see how easy it is.

  • Key Attributes of A Good Team Lead

    Key Attributes of A Good Team Lead

    A good team lead is hard to find.  Unfortunately, it is a struggle required when building a team of almost any size.  The good news is that the traits that make a good lead are easy to spot.  Once you find someone that possesses these make sure you keep them happy.

    A Good Team Lead is a Communicator

    As obvious as this may seem, it is also the most critical trait.  A Lead communicates with customers, management, and staff.  Although the Lead may want to “work” more and “meet” less, communication is always a big piece of their daily tasks.  Communication is not limited to one channel such as email, phone calls, or in person meetings.  A good lead can communicate successfully in any medium.  Communication through various means is critical to success.  Those they communicate with will utilize all of these channels.  However, written communication is the most important.  A good lead will leave a paper trail of discussions and decisions.

    They Are Comfortable in Many Roles

    A Lead is asked to take on multiple roles.  They will handle customer interaction, but also help design a solution, implement, and test.  When you have a good team lead the group works better together and stays focused.  Thus, you need to ask a broad range of questions in an interview.  Find out how the candidate thinks, test their ability to react and switch gears.  When reviewing existing staff to move into a lead role, look for people that stretch out to other groups and interact with more than their peers.

    A Good Team Lead is a Team Player

    Anyone that s placed in a leadership role will potentially focus on their career rather than the group.  A good team lead cannot fall into this trap.  They need to do the things that keep the team focused and working towards a common goal.  There is also a bit of a cheerleader aspect to such a lead.  They keep up morale and look for solutions rather than blame or excuses.

    They Are in Synch with the Customer

    The factor that might be the most important is being on the same page as the client.  A good team lead has the customer’s best interests in mind and understands their priorities.  This is a crucial piece of all the other attributes of a good Lead.  This quality helps communication, direction, and team management.  When a team lead is no the same page as the customer, the likelihood of project success goes up.  Coincidently, the frustration levels of those involved in the project good down.  Agreement between the implementors (personified by the lead) and the customers reduces overall friction and reduces the likelihood of scope drift.

    There is more to a good team lead based on particular circumstances.  However, these attributes seem to be universal in my experience with people that have excelled in the role.

     

  • Creating a Project Team – The Things to Consider

    Creating a Project Team – The Things to Consider

    Whether you have resources on hand or are building from scratch, a good project team requires planning.  We always want to create a team that is more than a collection of the members.  Luckily, the history of good and bad teams gives us some keys to success.

    Communication

    As we see with project failure reasons, communication is important.  A good team will not only communicate among themselves, but there also should be someone that can share with others.  This role may fall to the leader or manager, but a team that does not have someone to be “the voice” of the team will struggle.  This person may be a good writer, speaker, or presenter; the point is communication.  A team that cannot interact within and without is doomed to failure.  Lack of communication is a common source of project issues.

    Complementary Skills

    We often hear about groups and organizations with “too many chiefs” that struggle to be effective.  In fact, this concept applies to nearly any role.  The members of a project team should complement each other in their skills rather than all be the same.  For example, we have mentioned communication, and there are also design, planning, implementation, and testing areas of skills that should be possessed by the team.  A team full of communicators is not very useful if they do not have a mix of the other skills.  In particular, find a leader/motivator and then there is no need for another one.  Some skills are useful in multiple team members (e.g. testing, implementation).  However, many skills should only exist with one member (or a small percentage) to avoid conflicts.  Even two superb leaders can butt heads over an issue and thus negate each other’s skills.

    A Project Team of Old and New

    Everyone loves a good process and set of best practices.  The problem is that those tried and true approaches do not always work.  It takes a new pair of eyes to see where innovation and improvement can be made.  Thus, find a mix of project team members that are veterans and those that are newer to the focus of the project.  The veterans can help jump start the team with their experience and knowledge of how to approach the solution.  The neophytes can learn from the veterans while asking questions in case there is a better way to get the job done.

    Define Roles Clearly

    When a team is built, there are often roles that members are assigned.  These roles should be clearly noted and not assumed.  In particular, do this for the positions where you only want a member, or two focused on that aspect.  Assuming that everyone knows who should do what on a team often leads to confusion.  It can cause minor problems like slowing the team down or even be the source of crippling internal conflicts.  Remember that everyone on a team should have a role or roles, and they should be clear on what theirs are.