Month: March 2023

Part 6 of Team Building. Winding our way through a broken system

As I look back at part 5 and wonder if hiring is important enough for two posts, yes and no. This second part about hiring is about finding the right person in what is called a ‘fit’ interview.  But it is also something you can do with your current team.  The notion that one type of intelligence is slowly being rectified.  IQ, the common measure of intelligence is the most common, recently there is the finding that EQ, or emotional intelligence has become mainstream.  But what doesn’t show up on resumes or watching them interact?  Unfortunately, I am not sure there is a name for it. 

Let us look at a sports analogy.  When my daughter is playing hockey we spend a fair amount of time at practices and of course games.  Kids when they are young really only wanted to play games.  Coaches kept saying the way to get better was practicing.  The kids would be put through a set of drills, often the same ones each practice.  My daughter played had specific practices for her as she played goalie. The coach started with the same drills.  Buidling muscle memory so that in a game it would be second nature. 

What most people who don’t know my family very well didn’t see half of it.  The whole family often went to open skates, Ariel did what is called ‘Stick time’ with her friends.  In the winters I put up a backyard ice rink.  At open skates she would race around with her friends playing tag, chasing teammates etc. All of this was fun, free time and unstructured play without a coach telling them what to do. The ability to try things, something you can’t do when a coach is watching.   

Delightful story Larry, can you get to the point? Please?  It is something I see happening first with youth sports and seemed to carry over to education.  The notion that structure is everything and the overload that everything has to follow a plan based on some research to build the perfect education.  But is it?  If everyone got the same lectures jammed into them what really differentiates one student from the other?  There needs to be something outside the classroom that adds to the education.  

So how do you interview to decide what outside and life education someone has? As I said it is not on the resume? This again takes practice, but its looking for things that are on the resume or possibly removed. Some summer jobs or volunteering could lead to experiences that teach skills that are not in a book or classrooms. Anytime someone was in any customer service industry like food service, retail etc. ask about what they learned about people doing those jobs. For those who played teamed and individual sports ask how far they went, what coaches the like or didn’t like. Your goal it to understand if the person fits within your team culture, or in some cases can enhance the team culture.  

This post is part about interviewing, but it is also part about the over structure that our society has brought on our kids. With the goal that only certain schools will define your kid’s success there is an overwhelming push to have too much organization in sports as well as education. I may write a future post about the challenges of this, but your job running a team is finding the cog for your wheel.  

This opinion is mine, and mine only, my current or former employers have nothing to do with it. I do not write for any financial gain, I do not take advertising and any product company listed was not done for payment. But if you do like what I write you can donate to the charity I support (with my wife who passed away in 2017) Morgan Stanley’s Children’s Hospital or donate to your favorite charity. I pay to host my site out of my own pocket, my intention is to keep it free.  I do read all feedback, I mostly wont post any of them 

This Blog is a labor of love, and was originally going to be a book.  With the advent of being able to publish yourself on the web I chose this path.  I will write many of these and not worry too much about grammar or spelling (I will try to come back later and fix it) but focus on content.  I apologize in advance for my ADD as often topics may flip.  I hope one day to turn this into a book and or a podcast, but for now it will remain a blog. 

Team Building Part 5… Hiring..

Hiring is Fifth on your list? Yeah, it is mainly most of the time, people run a team already, or just took over a team etc. and very few will be starting from nothing. Hiring is important, particularly important, but if you do not know how to run a team hiring will not solve it. 

How many times you heard the following: 

  • Hire People Smarter than you. 
  • Hire Someone in your blind spot 
  • Hire Diverse candidates 
  • Hire people who are willing to learn (not what they know)  
  • Hire candidates for the role you have 
  • Hire the best candidate whether they fit your role, then find a place for them later 
  • Use the try to buy (consulting to convert)  
  • Use the ‘why is a manhole cover is round’ (or other problem-solving question)  
  • You need a minimum of X number of interviews before you know a candidate is good. 
  • You need to see a minimum number of candidates before you can pick one (or just compare the ones you get)  
  • Hire someone from the best schools 

I think I could just have a list of 100, start a poll and see what my readers have done, but just use those are some thoughts.

What if I said there is no ‘right’ answer and also there is no ‘wrong’ answer to any of the ideas above? Looking at the list, at different points in my career I have leveraged one or more of them. I have hired some great people, and also have hired some duds (If you never hired a dud, I doubt you hired a bunch of people.) The one thing I did do is learn from each hire, the questions to ask, the things to look at and how to evaluate to get the right candidate for my team.

I could end the blog here, but I doubt most can just rely on ‘learning’ by making mistakes. The hiring starts well before the interview, why again the first four parts were about the team not the hiring. Once you have created the culture for the team now the challenge is ‘writing’ the job description needs to reflect the culture not just the job. Your job description cannot just be ‘I need a Java developer to help build a trading app for so and so company. The required skill sets are Java, database etc..’ That will not get the right people saying ‘hmmm, that sounds awesome,’ Again, my team built tools to help file corporate taxes, and no one in kindergarten ever said, ‘I want to write tax software when I get older.’ The JD needs to show the culture, the experience, and the challenge that your team excels at.  

Next (now this is what I wish) the resume did not have name, address, or anything on it. I would like to read it without any kind of prejudice (try to remove cognitive bias.). Something in the resume needs to stand out, something other than a list of ‘what they did.’ A story, a why that connects with your that will ‘fit’ your culture. This is something that as a reader of resume’s you get better at with practice (Maybe I should create a class in this) 

Lastly, as said in the interview, with all the different theories on questioning for interviews, the key is to be consistent across everyone you hire. But one interview must be for ‘fit’ for the team. The line of questioning will be about the culture of past employment, or even things like college professors that got them excited. A question that sheds light on culture is describing the toughest problem you ran into, and how you got it resolved. What you are listening for are things like ‘I got help from….’ or ‘my team and I’ these are signals that they know how to work in a team environment. A good follow up question is, ‘what is the hardest problem someone asked you to help them out with?’ And see what they did to help.  

But Wait there is more…. after you chose to hire someone, you need to document this, answer the ‘why did we hire this person?’ ‘What did we ask them?’ ‘What did they reply?’ and ‘what led us to believe this would be a great candidate for us?’ I can honestly say I always did this, but its a practice that once in place does allow you to reflect easier. Yes, a retrospective. These notes should be reviewed yearly as part of your review with that employee. See how they are progressing and were the things that you saw in the interview correct, and the ones incorrect what do you need to change in your interview process.

This is longer than I wanted it to be (as of now) so part 6 will be part 2 of hiring….  

This opinion is mine, and mine only, my current or former employers have nothing to do with it. I do not write for any financial gain; I do not take advertising and any product company listed was not done for payment. But if you do like what I write you can donate to the charity I support (with my wife who passed away in 2017) Morgan Stanley’s Children’s Hospital or donate to your favorite charity. I pay to host my site out of my own pocket, my intention is to keep it free.  I do read all feedback; I mostly wont post any of them 

This Blog is a labor of love and was originally going to be a book.  With the advent of being able to publish yourself on the web I chose this path.  I will write many of these and not worry too much about grammar or spelling (I will try to come back later and fix it) but focus on content.  I apologize in advance for my ADD as often topics may flip.  I hope one day to turn this into a book and or a podcast, but for now it will remain a blog.   

Team Building Part 4…. Team Goals

At the beginning of the year Teams set goals. Sport analogies make the most sense so I will use them again. In hockey, it is to win the Stanley Cup and in American Football it is to win the Lombardi Trophy. For some teams who the previous year the goal may not be as high, it could be simply to make the playoffs. Working in Technology it is often to do ‘project x’ or complete ‘project y,’ in sales (which I did as part of Tech consulting) it was sell X amount or bring in Y number of clients.  

The above fit ‘SMART’ (as we spoke about in Part 3) and I should just stop here, and presto we have magically created goals for the new year, and our team will successfully get them done. Well not so fast. Digging deeper and understanding a lofty goal like winning a championship has massive downside. In sports, only one team brings home the trophy each year, and thus the other 30 or so teams ‘failed.’ So, if your team does not reach goals, complete projects on time, bring in revenue etc., is it a failure? 

The first thing companies do wrong is do reviews only with individuals. In many cases the ‘manager’ or a team gets the team goal, and on his review when they do not get there, he is asked the reason etc. Now I have been on the ‘why didn’t you reach your goal’ (or the why I did,) I will use analogy not from sports, but for people who invest, when they have good year and their portfolio rises, it’s always ‘I am a great stock picker’ and when their portfolio crashes, it was ‘There are some outside forces’ like the SP500 is down, we are in a recessions. To me, when reviews are done like this, we put our managers in that same situation. Let him gloat how great he is when he succeeds and find all the outside issues when they do not. 

Team goals are just that, we should savor victory as a team, and share the disappointment in the loss. No company I have worked for, not any other I have read about has this notion of end of year team reviews. Companies do reward teams with lucites, cash etc. when hitting some ‘completion’ mark, or hit sales goals etc. But the review is missing, and more important digging into the why is lost. 

The second thing is that reviews are done and really managed ‘Annually.’ As bonus cycles, raises, promotions etc. Management needs some way to judge and compare so the process is set up this way. And as stated the process is done mostly one on one with people, not teams. Can you really review once a year and summarize twelve months of work for anyone or any team? And does not this scale well, how many individuals can you review, understand their impact for their year and give honest assessments.  

Software development teams who follow agile practices often do retrospectives. These are regularly scheduled (every two weeks or so) meetings to chat not about status, but about the process of development. Many create lists of what we should be doing more of what to stop doing, and other ideas to improve how the project is built. These even fall short, as they are momentary, and trying to look at a brief period, and once a quarter a 10,000-foot view should be done. A review on the retrospectives, looking at things like ‘why doesn’t anyone address the big issues.’ or is the retrospective helping us hit the goal. This goes back to the fact, it is hard to admit that there is something wrong, it is outside our control. 

And lastly, we look at failure completely wrong. Failure is not something we know how to deal with. I have told the story about the difference between college and the real world, using the example that if you made a three-legged table in college, the professor what give you an ‘A’ for proving you cannot build a three-legged table. In the real world you would get fired for not producing a product that could sell. But failures have some root cause behind it, and for teams to get better they need not look at a failure as a problem, but one of an experience.  

Failures should be something we look at as we understand what we did does not work, and have built the necessary tools, training, reminders to improve the team. Everyone talks about ‘getting’ better, and no great person made zero mistakes. Why are we not celebrating the failures, and using them to make the team better? Why in management meetings do we demo/talk only about projects that succeeded, the successful architecture etc. Each of those projects had mini-failures, things they did wrong and corrected. And instead of teaching the rest of the organization and other teams how to get past those failures, we show the ‘success’ and the chance to repeat those failures persists. We need to present failures, and the lessons learned, and reinforcement so they are not made again.  

Though I make this sound easy, at the start of 2023 I am planning to redo how I run my team and try to fix some of the above. Funny, I knew these problems existed and I complained about them in the 90s. But writing this blog has made me rethink how to address them. I will let you know how they work out.  So on my to do list is to create a structure where I have recurring team meetings where we address goal changes (to be pushed down to individual goals) and create a culture where failures are brought forward as a learning experience.

This opinion is mine, and mine only, my current or former employers have nothing to do with it. I do not write for any financial gain, I do not take advertising and any product company listed was not done for payment. But if you do like what I write you can donate to the charity I support (with my wife who passed away in 2017) Morgan Stanley’s Children’s Hospital or donate to your favorite charity. I pay to host my site out of my own pocket, my intention is to keep it free.  I do read all feedback, I mostly wont post any of them

This Blog is a labor of love, and was originally going to be a book.  With the advent of being able to publish yourself on the web I chose this path.  I will write many of these and not worry too much about grammar or spelling (I will try to come back later and fix it) but focus on content.  I apologize in advance for my ADD as often topics may flip.  I hope one day to turn this into a book and or a podcast, but for now it will remain a blog.

Team Building Part 3 (Don’t be SMART)

Ok, I will admit it I went for a clickbait title. And no one fell for it. It
is that time of the year where organizations are starting Goal setting for the
year. There are different ways of doing this: Pushing Goals where the
management tell you what your goals, Pulling Goals where the employees come upwith them and managers then nod their heads politely and agree, and the
Combo-platter where both have input. There is absolutely nothing wrong with
either of these methods for creating goals.

To write the goals they tell you to use the SMART method. Created
in 1981 on the surface it sounds logical. The mnemonic is for Specific,
Measurable, Achievable, Relevant and Time-bound. All incredibly useful for
creating goals. But, after a one-on-one meeting and the goals are decided is
where it fails. Your new year’s resolutions can be created the same way and how
many of them have you every completed?

So, what is wrong with goals? Nothing is wrong with goals; you should have
them. What is wrong is that it that the process mostly ends there. [Actually,
based on feedback I get I can go into why goals should be at a team level not
at individual level as part 4] What makes teams succeed at hitting goals, what
makes individual good at hitting goals is not having them. Having a goal is
just that, a target to aim for.

What I would like the next step to be is finding a ‘system’ to achieve your
goal. In fact, most people have done this without thinking about it. Have you
ever created flash cards to quiz yourself about a topic in school? Have you
ever written something over and over to memorize it? Have you done math
problems 100s of times till you got it write. These are ‘practices’ that help
you achieve a goal. Now those systems are documented, a system you create for
your team/individual goal may need to be created.

If you set a goal to lose weight as a New Year’s resolution, the next step must
be what diet are you going to be on, what workout to do and steps. Some of the
most successful people who get fit schedule their workouts on their calendar,
plan their meals, do shopping and pre-make meals and stick to it. This system
is more effective than just having a goal.

What is the system will allow you for your team to hit their goals is
something as a leader you need to solve. In the Agile development world, it
starts with something called Sprint Zero, where the team comes up with
processes, ceremonies, interactions etc. for how the team works. Getting this
setup early is a must, everyone must be on the same page. This should be a team
activity with everyone involved in giving feedback.

As part of the process there needs to be a check to see if the system is
working. In Agile this is called a retrospective. This is where the team has to
take a look at the plan it setup and determine if it is helping reach the goal.
Make changes to the system, see if they work, if not undo. Do not be afraid to
make a mistake! It is ok to try something and fail but understand what went wrong.

A sports analogy gets thrown in. During a season, and often during a game
coaches make changes. Whether it is the players on the field, strategy, mindset
etc. Even when winning a coach can still see things that are not working perfectly,
they still may find something to tweak.

If the system is working well, apply it to other goals. The better you get
at your system the easier it is to achieve goals. And as stated before, just
because something is working does not mean it cannot be improved! Another link
to sports, often teams hire coaches that were successful, and part of the
reasoning is the coach will bring his or her ‘system.’ Companies do this with
successful managers up to C-level executives. No one is hired because they
‘create’ SMART goals, people are hired because they reach them.

So, it is ok to have SMART goals, but being SMART does not get you to reach
them. Having a system, constantly improving the system is what drives
successful teams.

This opinion is mine, and mine only, my current or former employers have nothing to do with it. I do not write for any financial gain, I do not take advertising and any product company listed was not done for payment. But if you do like what I write you can donate to the charity I support (with my wife who passed away in 2017) Morgan Stanley’s Children’s Hospital or donate to your favorite charity. I pay to host my site out of my own pocket, my intention is to keep it free.  I do read all feedback, I mostly wont post any of them

This Blog is a labor of love, and was originally going to be a book.  With the advent of being able to publish yourself on the web I chose this path.  I will write many of these and not worry too much about grammar or spelling (I will try to come back later and fix it) but focus on content.  I apologize in advance for my ADD as often topics may flip.  I hope one day to turn this into a book and or a podcast, but for now it will remain a blog.

© 2024 LrAu

Theme by Anders NorenUp ↑