The Basic Art of Front Line Management

The Basic Art of Front Line Management

Posted by

The life line of delivery is flawless execution. Meaning, every delivery team has to have flawless execution day in and day out. This battle is won and lost in the trenches. These trenches are run by the first (sometimes referred to as front) line managers/leads. The success and failure of any project depends on how well the entire management has helped FLMs to four areas of their work. Plan, People, Process and Projects.

In this article we talk about some important aspects to consider in each area to become a successful FLM.


1.       Plan: Without Planning/Training these people most companies have failed in execution and if not in execution they have failed in scaling the organization:


a.       The plan for your team should be in-line with your customers plan for the project. You should feel free to ask the goals of every project. What is the Key Result Area (KRA) for the project? What is the Key Performance Indicator (KPI) for the project? What is the Service Level Agreement (SLA) for the project? What are the business impacts of not hitting the SLA and why the customer/management is setting these objective SLAs.


b.      Based on this understanding you will need to come up with your own plans for your team and your people. This plan should be broken down into plans for the month, week and day and should help achieve the company annual plan.


2.      People: FLMs by nature are the best technical people that have been made into FLMs because they are good at their technology and not because their leadership skills. Given this, most FLMs are not the best of people managers. You as an FLM need to be trained in people management. It is critical for your success. While HR or hiring can hire the best it is critical that there you take ownership and have the mindset to help people. It is as simple as that. If you are kind to your people they will be kind to you. You as an FLM should be the ones training your people with close supervision from other management team members.


a.       Mindset: The most important aspect of being a leader or FLM is to have the right mindset. Remember you can never be lazy or negative about anything. Your entire team is looking up to you. If you say anything negative or get lazy or hide from your responsibility your team will not respect you and will never take anything you say seriously. Being an FLM does not mean that you will try and fight management for your team. While this looks good on the short run it is doomed. Make sure you work with your management to help your team. Be honest, humble, and hungry. Things will take care of themselves.


b.      Review: You must have a monthly KRA review with each employee.


c.       Have a daily feedback if required with each employee.


d.      Ask if they have understood you. Have the team member repeat what they are supposed to do at the beginning of the day.


e.      Find out how their day has been at least once every three days. Know your team members personal life. That IS your business.


f.        Create a second in line within your team: Will they be able to handle your job if you are on vacation without bothering your manager? That is the only question you have to ask when training them.

g.      Remember your customer is also a person. Here is how every customer thinks. No matter which company, country or type of work, the mindset of the customer is always the same.


i.  The Customer is looking to get ahead in his or her career by managing your project well: Companies are structured in a way that when an employees career grows, the company grows. This is news to be excited about. The first rule with customers, know what makes them succeed. It is your job description to help them get further in their career and help improve their company’s Return On Investment (ROI). This will help you and your career in the end.


ii.      The customer is NOT out to get you: The customer actually wants you and your team to succeed. Because when you do they look good. When things are not going right for you and your team the customer is NOT out to get you. They are out try to understand only three things:


a.      Do you have a plan to fix the problem? And if this fix is a permanent fix?


b.      Do you know when you will be back out of the problem?


c.      If you need their help to solve the problem and how they should position the news or issue/problem with their team. Understand these points before talking to your customers (Internal or External). Find out the person behind the voice. This is critical for your success as well as their success


3.       Process: The FLMs need to be provided structure and a method to run their daily operations and drill. Without this they will perform whatever seems best. Some of the critical processes to follow are:


a.       Morning Operating Rhythm (OR): Create a morning OR for your team. Go through this with your management and then make sure that you go through your operating rhythm without fail. Also create an Insurance dashboard for youself.


b.      Daily Scrum: pend 15 minutes to understand the task for the entire team. Make sure that everyone is told what needs to be done


c.       Talk to your team: Most of the time the individual contributors need to be verbally explained what needs to be done every day even if the information is written in requirements or process documents


d.      Define the goal to the team: For example if you are going to be testing 100 items with an intent to find out as many bugs as possible tell the team that they have to get to a goal of creating at least 5 bugs each. But make sure you let them know that they have to stick to the test script.


e.      NEVER jump steps: When explaining things to people never jump steps. It is critical that you make sure that your team also understands that they don’t jump steps. Jumping steps is a sure way of getting things wrong.


f.        Review: Tell them when you are going to review and what you are going review at the beginning of the day. Continuing with the QA example, tell your team that you are going to QA every bug that is reported. If you working on operations or development let your team members know that you are going to do a sample QA of the work done by everyone in the team. Before you QA, THINK!!!! “What is your goal?” “What is the customer going to look at when they see our work?” Then QA the work. 99% of the errors that will come from your team will come from the lack of understanding of the fact that they don’t look at their own work from the end users perspective. Out of these errors 90% of the errors is going to be caused because your team members have jumped steps or trying to take short cuts. Yes even the so called human errors are caused because someone got too cocky about the work they are doing and got careless.


g.       Questions from the team: You have to explain the work at the beginning of the day. Encourage your team members to ask questions. The best way to make sure that your team does not ask questions is to make sure that you NEVER yell at a person that asks questions. When people ask questions, please make sure that you don’t just answer it. Make sure that you ask more questions to test if they have understood the process completely.


h.     Timing of your reviews: Again, the operative word is ‘THINK’. Don’t review the work of your team at the end of the day. Review a sample of everyone’s work after they go through the first pass. Then again, when they are half hour from lunch and then again one hour before the end of the day. This will ensure that the work that they are doing can be corrected during the day and not at the end.


i.         End of Day (OR): Before you send your daily update into your dashboard or your email to your customer/management make sure that you have reviewed all the numbers that you are sending. The simple way of making sure that the numbers are correct is to review the numbers backward from the email or the dashboard as a customer would. Your sample tests at least one or two should come from this message or dashboard to make sure that you are doing what your customer will do when they review this information. Again the operative word is ‘THINK’ customers!


j.        Highlights for the day: Collect all questions and make sure that you put this into the knowledge base of your team. Make sure that you check with your management in your weekly call about where to store this information. Again, don’t assume, ask!


4.       Projects:


a.       Timely delivery: now the timely delivery KRA for your project. Make sure that your team knows about this number every day.


b.      Quality Delivery: now the quality delivery KRA and SLA for your project. Make sure that you mention it to your team every day as a part of the daily operating rhythm and also put it up on the Insurance dashboard.


c.       Understand the RYG for your project: When to raise your project from G to Y and Y to R and back

d.      When you in trouble (You will be from time to time) make sure that you:


i.      Create a plan with your management on how you going to fix the problem for now and a preventive measure for the future.


ii.      Confirm on when you will be back on track


iii.      Confirm to the customer/management on the dashboard on what the plan is and when you will be able to get back on track. Also communicate if you need them to communicate anything specific to their customers


iv.      When communicating, make sure that you are proactive. If you ever get into a situation when the customer or your management or your employee follows up with you for information then you will always have a tough conversation.


In all these is a common thread. You have to have consistency of purpose (Rule 22) in everything that you do. You have to move from being a manager to a leader (Rule 11).


Follow these guidelines and your will come out ahead in every project and in your career!


Leave a Reply

Your email address will not be published.