One of the best team-building exercises that I have participated in was as a Board Member for the Children’s Hospital Foundation of Wisconsin. We were going down a path that led to a decision on whether or not to invest $150M in a new addition. The CEO at the time, Jon Vice, wisely determined that strong teams were needed for each committee in order to thoroughly vet the idea from every possible perspective.
The process started by being given a book to read (“Now, Discover Your Strengths” by Marcus Buckingham & Donald O. Clifton, Ph.D.), and then completing the “Strengthsfinder” assessment using a code provided in the book. The goal was to understand gaps in perception (how you view yourself vs. how others view you) so that you could truly understand your own strengths and weaknesses. Then, teams were created with people having complementary skills to help eliminate weaknesses from the overall team perspective. The results were impressive.
Over my career, I have been involved in many team-building exercises and events – some of which provide useful insights, but most failed to pull the findings together in a way that was concrete, had context, and offered actionable recommendations. Key areas that consistently omitted were around Organizational Culture, Organizational Politics, and Leadership. Those three areas have a significant impact on value creation vis-à-vis team effectiveness and commitment.
When I had my consulting company we had a small core team of business and technology consultants and would leverage subcontractors and an outsourcing company to allow us to take on more concurrent projects as well as larger, more complex projects. This approach worked for three reasons:
- We had developed a High-Performance Culture that was based on:
- Purpose: A common vision of success, and understanding of why that mattered, and an understanding of specifically how that was defined and measured.
- Ownership: Taking responsibility for something and being accountable for the outcome. This included responsibility for the extended team of contractors. Standardized procedures helped ensure consistency and make it easier for each person to accept responsibility for “their team.”
- Trust: Everyone understood that they not only needed to trust and support each other but in order to be effective and responsive the others would need to trust their judgment. If there was a concern we would focus on the context and process improvements to understand what happened and implement changes based on lessons learned. Personal attacks were avoided for the good of the entire team.
- Empowerment: Everyone understood that there was risk associated with decision making, while at the same time realizing that delaying an important decision could be costly and create more risk. Therefore, it was incumbent upon each member to make good decisions as needed and then communicate changes to the rest of the team.
- Clear and Open Communication: People on the team were very transparent and honest. When there was an issue they would attempt to resolve it first with that person, and then escalating if the two people could not reach an agreement and decided to seek the consensus of the team. Everything was out in the open and done in the spirit of being constructive and collaborating. Divisiveness is the antithesis of this tenet.
People who were not a good fit would quickly wash out, so our core team consisted of trusted experts. There was a friendly competition that helped raise the bar for the entire team, but when needed the other team members became a safety net for each other.
We were all focused on the same goal, and everyone realized that the only way to be successful was to work together for the success of the team. Win or lose, we did it together. The strength of our team created tremendous value – internally and for our customers that we sustained for several years. That value included innovation, higher levels of profitability, and an extremely high success rate.
This approach can work at a Business Unit or Department level but is most effective when it starts at the top. When employees see the leaders of their company behaving in this manner it provides the model and sets expectations for everyone under them. If there is dysfunction within an organization it often starts at the top – by promoting or accepting behaviors that do not benefit the whole of the organization. But, with a strong and positive organizational culture, the value of strong teams is multiplied and becomes an incredible competitive advantage.
My wife has a Nissan Maxima and loves her car. Over the past 9 months there has been a persistent but seemingly random problem where the radio is used for a few minutes while the car is off and then the battery dies when she goes to start the car. This has happened more than a dozen times over the past 3 1/2 years, and it has been seen by two dealerships a for a total of three times recently with no success – the most recent visit being one day before this problem occurred.
Saturday morning I was running errands when my wife called and let me know that this problem happened again (second time this week and she was very frustrated). I was pretty excited because this time the problem occurred at home, not at some parking lot like usual, so I had the luxury of time to try to make a root cause determination. I’m somewhat mechanical but certainly no professional, so I followed my own consulting advice and contacted a professional.
Dave T. is a mechanical guru, and has an uncanny ability to offer sage advice with only a modicum of information. He is an incredibly busy guy, but is always willing to spend a few minutes and give helpful advice. It helps that he is a great guy, but it also helps him generate business (leads and referrals). It is an approach that helps create a constant backlog of work and very loyal clientele, which is good business.
I called Dave, described the problem, mentioned what I had read on various forums (i.e., similar electrical problems observed after some arbitrary mileage). Next, I mentioned that this had just been to the dealership and they did not find anything wrong. Dave laughed, stated that, “There is a 99%+ likelihood that alternator is bad, and possibly both the alternator and battery.” He sounded very confident.
There was a pause, and then he asked, “What’s more likely – that there is some completely random problem that only happens when your wife is out and your son stays in the car and listens to music for a few minutes, which by the way only happens to Maximas after X number of miles, or that there are issues with the alternators where they tend to fail after a certain amount of use, which causes them not to charge the battery properly and leads to a condition where there is not enough of a charge to start the car?”
When Dave explained it like that I felt kind of stupid, consoled only by the fact that other professional mechanics had not resolved the problem before me. He then added, “Anything that would be able to drain a battery within a few minutes would be noticeable. It would start a fire or melt wires, and smoke or smell as a result. You haven’t seen or smelled anything like that, have you?”
I described my plan to troubleshoot the problem, and Dave suggested that in addition I test the alternator and the specific gravity of the individual battery cells. So, in less than five minutes into that call I had a plan and was off and running.
Yesterday afternoon I spent several hours using a very methodical approach to troubleshooting, documenting everything with pictures and videos to help me recall both details and sequence if needed. Sure enough, Dave’s knowledge and intuition led to the correct conclusion.
I gave him a call to thank him, and while talking I wondered aloud why the dealership could not figure this out? Dave replied, “It’s not that they couldn’t have done what you did, but instead they focused on the symptoms you described. The mechanic probably sat there for 10-15 minutes with the lights and radio on while the car was off. After that the car started so they assumed that everything was fine. I listened to what you said, ignored the randomness and speculation, and honed-in on the problem. The fact that this happened again so soon also made sense because now your battery was run down from the testing performed by the dealership.” He added, “In my business I get paid for results, so I can’t get away with taking the easy way out.”
I’m big on lessons learned, wanting to make the most of each and every experience because I have learned that skills and knowledge are often very transferrable. As I thought about this I realized that Dave’s analysis was the perfect practical application of Occam’s razor. It’s a skill that is very helpful as a Consultant, but more importantly, it is something that can help when problem solving in any line of work.
As a young boy, I was “that kid” who would take everything apart, often leaving a formerly functional alarm clock in a hundred pieces in a shoe box. I loved figuring out how things worked, and how components worked together as a system. When I was 10, I spent one winter completely disassembling and reassembling my Suzuki TM75 motorcycle in my bedroom (my parents must have had so much more patience and understanding than I do as a parent). It was rebuilt by spring and ran like a champ. Beginners luck?
By then I was hooked – I enjoyed working with my hands and fixing things. That was a great skill to have while growing up as it provided income and led to the first company I started at age 18. There was always a fair degree of trial and error involved with learning, but experience and experimentation led to simplification and standardization. That became the hallmark to the programs I wrote, and later the application systems that I designed and developed. It is a trait that has served me well over the years.
Today I still enjoy doing many things myself, especially if I can spend a little bit of time and save hundreds of dollars (which I usually invest in more tools). Finding examples and tutorials on YouTube is usually pretty easy, and after watching a few videos for reference the task is generally easy. There is also a sense of satisfaction to a job well done. And most of all, it is a great distraction to everything else going on that keeps your mind racing at 100 mph.
My wife’s 2011 Nissan Maxima needed a Cabin Air Filter, and instead of paying $80 again to have this done I decided to do it myself. I purchased the filter for $15 and was ready to go. This shouldn’t take more than 5 or 10 minutes. I went to YouTube to find a video but no luck. Then, I started searching various forums for guidance. There were a lot of posts complaining about the cost of replacement, but not much about how to do the work. I finally found a post that showed where the filter door was. I could already feel that sense of accomplishment that I was expecting to have in the next few minutes.
But fate, and apparently a few sadistic Nissan Engineers had other ideas. First, you needed to be a contortionist in order to reach the filter once the door was removed. Then, the old filter was nearly impossible to remove. And then once the old filter was removed I realized that the length of the filter entry slot was approximately 50% of the length of the filter. Man, what a horrible design!
A few fruitless Google searches later I was more intent than ever on making this work. I tried several things and ultimately found a way to fold the filter where it was small enough to get through the door and would fully open once released. A few minutes later I was finally savoring my victory over that hellish filter.
This experience made me recall “the old days.” Back in 1989 I was working for a marketing company as a Systems Analyst and was given the project to create the “Mitsubishi Bucks” salesperson incentive program. Salespeople would earn points for sales, and could later redeem those points on Mitsubishi Electronics products. It was a very popular and successful incentive program.
Creating the forms and reports was straight forward enough, but tracking the points presented a problem. I finally thought about how a banking system would work (remember, no Internet and few books on the topic, so this was reinventing the wheel) and designed my own. It was very exciting and rock solid. Statements could be reproduced at any point in time, and there was an audit trail for all activity.
Next, I needed to create validation processes and a fraud detection system for incoming data. That was rock solid as well, but instead of being a good thing it turned out to be a real headache and cause of frustration.
Salespeople would not always provide complete information, might have sloppy penmanship, or would do other things that were odd but legitimate. Despite that, they expected immediate rewards and having their submissions rejected apparently created more frustration than incentive.
So, I was instructed to turn the dial way back. I let everyone know that while this would minimize rejections it would also increase the potential for fraud, and created a few reports to identify potentially fraudulent activity. It was amazing how creative people could be when trying to cheat the system, as well as how you could identify patterns to more quickly identify that type of activity. By the third month the system was trouble free.
It was a great learning experience from beginning to end. Best of all, it ran for several years once I left – something I know because every month I was still receiving the sample mailing with the new sales promotions and “Spiffs” (sales incentives). This reflection also made me wonder how many things are not being created or improved today because it is too easy to follow an existing template.
We used to align fields and columns in byte order to minimize record size, overload operators, etc. in order to maximize space utilization and maximize performance. Code was optimized for maximum efficiency because memory was scarce and processors slow. Profiling and benchmarking programs brought you to the next level of performance. In a nutshell, you were forced to really understand and become proficient with the technology used out of necessity. Today those concepts have become somewhat of a lost art.
There are many upsides to easy.
- My team sells more and closes deals faster because we make it easy for our customers to buy, implement, and start receiving value on the software we sell.
- Hobbyists like myself are able to accomplish many tasks after watching a short video or two.
- People are willing to try things that they may not have if getting started would not have been so easy.
But, there may also be downsides relative to innovation and continuous improvement simply because easy is often good enough.
What will the impact be to human behavior once Artificial Intelligence (AI) becomes a reality and is in everyday use? It would be great to look ahead 25, 50, or 100 years and see the full impact of emerging technologies, but my guess is that I will see many of the effects in my own lifetime.
I have recently been investigating and visiting universities with my eldest daughter, who is currently a Senior in High School. Last week we visited Stanford University (an amazing experience) and then we spent a week in Northern California on vacation. After being home for a day and a half I am currently in Texas for a week of team meetings and training.
The first night of a trip I seldom sleep, so I was listening to the song, “Don’t let it bring you down” by Annie Lennox, which is a cover of a Neil Young song. That led to a Youtube search for the original Neil Young version, which led to me listening to the song “Old Man” – a favorite song of mine for over 30 years. That led to some reflection which ultimately led to this post.
The reason that I mention this is because it is an example of the tangential thought process (which is generally viewed as a negative trait) that occurs naturally for me. It is something that helps me “connect the dots” faster and more naturally. It is part of the non-linear thinking associated with ADHD (again, something generally viewed as negative). The interesting thing is that in order to fit in and be successful with ADHD you tend to develop logical systems for focus and consistency. For me personally, that has many positive benefits – such as creating repeatable processes and automation.
The combination of linear and non-linear thinking can really fuel creativity. The downside is that it can take quite a while for others to see the potential of your ideas, which can be extremely frustrating. But, you learn to communicate better and deal with the fact that ideas can be difficult to grasp. The upside is that you tend to create relationships with other innovators because they tend to think like you do so you become relatable and interesting to them. The world is a strange place.
It is funny how there are several points in your life when you have an epiphany and things suddenly make complete sense. That causes you to realize how much time and effort could have been saved if you had only been able to figure something out sooner. As a parent I am always trying to identify and create learning shortcuts for my children so that they can reach those points much sooner than I did.
I started this post thinking that I would document as many of those lessons as possible to serve as a future reminder and possibly help others. Instead, I decided to post a few things that I view as foundational truisms in life that could help foster that personal growth process. So, here goes…
- Always work hard to be the best, but never let yourself believe that you are the best. Even if you truly are, it will be short lived as there are always people out there doing everything that they can to be the best. Ultimately, that is a good thing. You need to have enough of an ego to test the limits of things, but not one that is so big that it alienates or marginalizes those around you.
- Learn from everything you do – good and bad. Continuous improvement is so important. By focusing on this you constantly challenge yourself to try new things and find better (i.e., more effective, more efficient, and more consistent) ways to do things.
- Realize that the difference between a brilliant and a stupid idea is often perspective. Years ago I taught technical courses, and occasionally someone would describe something they did that just seemed strange or wrong. But, if you took the time to ask questions and try to understand why they did what they did you would often identify the brilliance in that approach. It is something that is both exciting and humbling.
- Incorporating new approaches or the best practices of others into your own proven methods and processes is part of continuous improvement, but it only works if you are able to set aside your ego and keep an open mind.
- Believe in yourself, even when others don’t share that belief. Remain open to feedback and constructive criticism as a way to learn and improve, but never give up on yourself. There is a huge but sometimes subtle difference between confidence and arrogance, and that line is often drawn at the point where you can accept that you might be wrong, or that there might be a better way to do something. Become the person that people like working with, and not the person that they avoid or want to see fail.
- Surround yourself with the best people that you can find. Look for people with diverse backgrounds and complementary skills. The best teams that I have ever been involved with consisted of high achievers who constantly raised the bar for each other while simultaneously creating a safety net for their teammates. The team grew and did amazing things because everyone was both very competitive and very supportive of each other.
- Keep notes or a journal because good ideas are often fleeting and hard to recall. And remember, good ideas can come from anywhere so keep track of the suggestions of others and make sure that attribute those ideas to the proper source.
- Try to make a difference in the world. Try to leave everything your “touch” (job, relationship, project, whatever) in a better state that before you were there. Helping others improve and leading by example are two simple ways of making a difference.
- Accept that failure is a natural obstacle on your path to success. You are not trying hard enough if you never fail. But, you are also not trying hard enough if you fail too often. That is very subjective, and honest introspection is your best gauge. Be accountable, accept responsibility, document the lessons learned, and move on.
- Dream big, and use that as motivation to learn new things. While I was funding medical research efforts I spent time learning about genetics, genomics, and biology. That expanded to interests in nanotechnology, artificial intelligence, machine learning, neural networks and interfaces such as natural language and non-verbal / emotional. Someday I hope to tie these together in a way that could help cure a disease (Arthritis) and improve the quality of life for millions of people. Will that ever happen? I don’t know, but I do know that if I don’t try it will never happen because of anything that I did.
- Focus on the positive, not the negative. Creativity is stifled in environments where fear and blame rule.
- Never hesitate to apologize when you are wrong. This is a sign of strength, not weakness.
- And above all else, honesty and integrity should be the foundation for everything you do and are.
Hopefully, this will help my children become the best people possible, and ideally early-on in their lives. I was 30 years old before I feel that I really had a clue about a lot of these things. Until that point I was somewhat selfish and focused on winning. Winning and success are good things, but they are better when done the right way.
I learned many valuable lessons over the course of the 8+ years that I owned my consulting business. Many were positive, a few were negative, but all were educational. These lessons shaped my perceptions about and approaches to business, and have served me well. This post will just be the first of many on the topic.
My lessons learned covered many topics: How to structure the business; Business Goals; Risk; Growth Initiatives and Investment; Employees and Benefits; Developing a High-Performance Culture; Marketing and Selling; Hiring and Firing; Bringing in Experts; Partners and Contractors; The need to let go; Exit Strategies and more.
In my case these lessons learned were compounded by efforts to start a franchise for the consulting system we developed, and then our expansion to the UK with all of the challenges associated with international business.
It’s amazing how more significant those lessons are (or at least feel) when the money is coming out of or going into “your own pocket.” Similar decisions at larger companies are generally easier, and (unfortunately) often made without the same degree of due diligence. Having more “skin in the game” does make a difference when it comes to decision making and risk.
Businesses are usually started because someone is presented with a wonderful opportunity, or because they feel they have a great idea that will sell, or because they feel that they can make more money doing the same work on their own. Let me start by telling you that the last reason is usually the worst reason to start a business. There is a lot of work to running a business, a lot of risk, and many expenses that most people never consider.
I started my business because of a great opportunity. There were differences of opinion about growth at the small business I was working for at the time, and this provided me with the opportunity to move in a direction that I was more interested in (shift away from technical consulting and move towards business / management consulting). Luckily I had a customer (and now good friend) who believed in my potential and the value that I could bring to his business. He provided both the launch pad and safety net (via three month initial contract) that I needed to embark on this endeavor. For me the most important lesson learned is to start a business for the right reasons.
More to come. And, if you have questions in the meantime just leave a comment and I will reply. Below are some of the statistics on Entrepreneurship that can be pretty enlightening:
In consulting and in business there is a tendency to believe that if you show someone how to find that proverbial “pot of gold at the end of the rainbow” that they will be motivated to do so. Seasoned professionals will tend to ask, “What problem are you trying to solve?” to understand if there is a real opportunity or not. If you are unable to quickly, clearly and concisely articulate both the problem and why this helps solve that problem it is often game over then and there (N.B. It pays to be prepared). But, having the right answer is not a guarantee of moving forward.
Unfortunately, sometimes a mere pot of gold just isn’t enough to motivate. Sometimes it takes something different, and usually something personal. It’s more, “What’s in this for me?” No, I am not talking about bribes, kickbacks or anything illegal or unethical. This is about finding out what is really important to the decision maker and in what priority, and then demonstrating that the proposed solution will bring them closer to achieving their personal goals.
Case in point. Several years ago I was trying to sell a packaged Business Intelligence (BI) system developed on our database platform to customers most likely to have a need. Qualification performed – check. Interested – check. Proof of value – check. Quick ROI – check. Close the deal – not so fast…
This application was a set of dashboards with 150-200 predefined KPIs (key performance indicators). The premise was that you could quickly tailor and deploy the new BI system with little risk (finding and validating the data needed was available to support the KPI was the biggest risk, but one that could be identified up-front) and about half the cost of what a similar typical implementation would cost. Who wouldn’t want one?
I spent several days onsite with the prospect, identified areas of concern and opportunity, and used their own data to quantify the potential benefit. Before the end of the week I was able to show the potential to get an 8x ROI in the first year. Remember, this was estimated using their data – not figures that I just created. Being somewhat conservative I suggested that even half that amount would be a big success. Look – we found the pot of gold!
Despite this the deal never closed. This company had a lot of money, and this CIO had a huge budget. Saving $500K+ would be nice but was not essential. What I learned later was that this person was pushing forward an initiative of his own that was highly visible. This new system had the potential to become a distraction and he did not need that. Had I been able to make this determination sooner I could have easily repositioned it to be in alignment with his agenda.
For example, the focus of the system could have shifted from financial savings to project and risk management for his higher priority initiative. The KPIs could be on earned value, scheduling, and deliverables. This probably would have sold as it would have been far more appealing to this CIO and supported what was important to him (i.e., his prize if he wins). The additional financial savings initially identified would just be the icing on the cake, to be applied at a later time.
There were several lessons learned on this effort. In this instance I was focused on my own personal pot of gold (based on logic and common sense), rather than on my customer’s priorities and prize for winning. That mistake cost me this deal, but is one I have not made since – helping me win many other deals.