With four weeks left in 2019 it’s time to start your new years goal setting. Unless you have a bias-for-action, which you should — if you’re a founder.
Four weeks is enough time to define and test some hypothesis around the business that you’ve been noodling since January 2019. Let’s get together and turn thoughts into deeds. I’m putting together a workshop series to drive your “idea stage” startup to “early stage” before January 1st, 2020.
As a group, we’ll help you determine the Who, What, and Why of your product and provide an operational plan and the tactics you need to validate your hypothesis before the end of the year. Register to attend each week individually.
The content will build over the course of the month, you will be assigned homework in advance and the in-person time will be a group review to ask and answer questions. The goal is to create a cohort of new founders who can peer mentor each other. I will bring different experts in to cover the content from the homeworks. Want to know more? Sign-up below.
One of the hardest things for senior managers to maintain Situational Awareness across their entire organization. Ego and averaging often obscure the reporting up through your hierarchy.
Mid-level managers don’t ask for help because they don’t see how their team’s problems are impacting the organization as a whole. This lack of reporting or “the blame game” can hide the root causes of cross-functional problems.
Whenever I face uncertainty, I collect and visualize data to gain a deeper understanding of the problem.
Capturing Data Efficiently
Every week, managers are required to report their individual team members “stress load” in a shared google sheet. In aggregate, over-time, this Employee Heatmap data becomes immensely valuable in understanding your teams’ performance.
This quick report (~2 minutes for a team of 5) allows both you and your managers to visually see changes in employees status across your entire organization. This insight allows you both to determine where to focus your analysis and assistance as leader.
The Employee Heatmap is built on a quantitative value that we call “Stress Load”. “Stress Load” is defined as Workload + Familyload.
As a Human-First leader, I view my employees capacity as the combination of two things. The 8-hours they spend on the clock and the issues they’re facing during the 16-hours a day that I don’t pay them for.
My managers collect these data points during their monthly 1-on-1s with their direct reports. They adjust the monthly self-reported “stress load” number based on their direct observation when reporting it in the management review weekly.
What is Workload?
Workload in the Employee Heatmap is quantified on a scale of 1-10. 1 being almost completely unsaturated to the point of boredom and 10 being complete saturation at an unsustainable pace. 4-6 is the Goldilocks Zone.
Depending on your team composition, you may regularly see 6-7 . Challenging workloads tend to keep Type-A employees more engaged and therefore might not be a negative indicator. Sustained values in the 8-10 range usually indicate an underlying issue that needs attention.
I encourage my managers to restate the number and ask “What does that mean to you?”. If the self-reported number is out of the Goldilocks Zone for that employee, I instruct them to ask “Why do you feel this way?” It’s important that the direct manager understands what is driving the stress level of their employee’s workload numbers.
Qualitative reasons often drive higher workload numbers. Employees doing work that they don’t enjoy or having to work with someone they dislike is more often the culprit than being overwhelmed by volume. Managers tend to be better at recognizing tasking issues than rooting out qualitative drivers.
My astute friend Mike Canzoneri solves this problem by breaking down his version of this process into 3 values: Workload Emotional, Workload Quantity, Family Load.
What is Family Load?
Family Load is also measured on a scale of 1-10. 1 being almost completely stress-free to the point of boredom and 10 being overwhelming stress that detracts from the employees quality of life.
We respect our employees’ privacy as a cultural value at my company. Managers are instructed to not ask for the “Why?” with this number. If their employees volunteer the information, they are told to keep it in confidence. This qualitative input can help the manager to bias the monthly number appropriately for the weekly reporting as the employees life-situation continues to develop.
Long Term Value of the Employee Heatmap
If you graph the data in the Employee Heatmap, you can start to determine leading and trailing indicators as well as recurring trends in your team’s functioning.
I’ve used this data to make staffing plans, deconflict teams before they were in a negative feedback loop, and change how we schedule work. It’s pound-for-pound the most powerful tool in my personal management toolbox. I highly encourage you to try it, modify it, and share the results.
Questions of the Day
What’s your favorite tool for managing your employees? Do you have any other tricks for keeping a pulse on in-direct reports?
Donald Knuth was specifically talking about algorithms in computer software, but the lesson applies broadly to product development, startups, and self-improvement.
Perfection is the Enemy of Progress
Wikipedias worth of man-hours have been spent building features that the customer never requested and rarely use. Companies have spent millions on inventory to achieve economies of scale on products that crater in the market. They should have shipped first and asked questions later.
Stop futzing around and ship it! Premature optimization is often procrastination in disguise. If you’re “making it better” before someone has used it, you’re letting fear of judgement keep you from learning.
Don’t worry about scaling, don’t worry about “nice to have”, just start! Start going to the gym, spearhead a new process at work, ask someone to buy your barely functional prototype. Even if you fail, you’ll be at the same place as if you were still planning; the only difference is, you’ll have a data point from the real world. Now you can adjust, incrementally better, then ship it again.
Questions of the Day
What aspect of your life should you be shipping instead of optimizing? Is there a feature in your product or startup that’s a good idea but you haven’t had a customer ask for it yet? Tell me about the time you sunk days of oyur life into solving a problem that didn’t exist.