Tag: cxo

Talent Development with One-Page Profiles

An idea from a book can transform your life, either by giving you a new perspective on an old idea or by giving you a brand new perspective on something brand new. One such idea is worth the time and money invested in a book.

One of the ideas that shaped my approach to talent development came from Jack Welch’s Straight from the Gut book nearly two decades ago. This idea has helped me develop my team members.

Welch suggests managers create one-page profiles for each member of their team. The top of the page should have the person’s name, a photo, and a grid assessing their potential and performance. Performance measures a person’s contribution to a project, while potential measures their competency. It’s critical to look at both. If someone lacks potential, they should be improved or fired. If an employee has potential but is underperforming, they may require coaching and training.

Below the grid, list the individual’s strengths and weaknesses. You can add accomplishments, teamwork skills, and other relevant factors in free-form text. Update this one-page plan every year to track progress.

Managers must evaluate where each team member falls on this grid and give them feedback and training plans.

I’ve been using this method for my team members since I read the book. I’m forced to evaluate everyone’s abilities and performance. The method helps identify the root cause of someone’s struggle-be it emotional issues, misunderstandings, or personal concerns-and opens up a dialogue. Knowing team members’ abilities in detail helps me grow them.

If you manage a team, try it. You and your team will benefit from it.

Embodying company values

A lot of companies have vision statements and say their cultures are based on values. They might even hang those vision statements in the office. Many of these values are so generic that they can be used by any company. Even companies with very specific mission statements and principles might have trouble articulating these values, let alone living them every day.

Amazon, however, comes across differently. They’re known for their leadership principles. When candidates apply, they’re tested on how well they adhere to these principles. I coached a candidate to get into Amazon, so I know how rigorous the hiring process is in validating leadership experience. I’ve often wondered if these principles just exist on paper or if they’re actually part of the culture. I got my answer recently.

As a CTO, I come across sales leaders and sales-support leaders from numerous organizations, both large and small. Compared to others, my partnership with Amazon stands out. Two people I interacted with from Amazon Web Services (AWS) exemplified customer obsession, a core Amazon leadership principle — Anisha and Sanjeev.

Let me give you couple of examples.

Few months back I got an email from Anisha, introducing herself as an account manager, my initial instinct was to dismiss it. I often receive similar messages from various partners, and more often than not, their goal is simply to sell more services rather than genuinely helping me. Typically, when I inquire about specific services, I’m directed towards documentation that I’ve already read. Despite this, I decided to reply back to Anisha due to our substantial dealings with AWS.

I replied with two requests:
• Information on AWS’s new ML services
• How these services can help our developers as well as our customers

To my surprise, within 15 minutes Anisha responded with an offer to call me or set up a demo session with her technical team. Impressed by her helpful and immediate response, I provided her with my phone number, and she promptly called me to discuss how her team could assist us. Note that this was without any sales pitch.

Eager to explore two issues—how our employees could use ML models and what we could do for our customers using ML—she scheduled a meeting with a technical architect, Sanjeev. He agreed to conduct a session on enhancing developer productivity through ML and addressed the questions of my tech team for nearly an hour. I have never seen my team members so enthusiastic in any training sessions. That would’ve been the perfect moment to sell us Code Whisperer licences, but Anisha generously offered free licenses for three months so we could test the service ourselves.

Curious about their other offerings, I inquired about additional services we could utilize. Both Sanjeev and Anisha explained different services that we could use for solving a problem we were trying to solve for one of our customer. Once the problem and scope was clear, without hesitation, Sanjeev offered to build a proof of concept (POC) for us. However, I insisted that as a services company, we should be the ones to build it and asked for his assistance instead. For the next four weeks, Sanjeev dedicated himself to weekly calls, discussing the intricacies of the problem we aimed to solve, our approach, and the services required.

By the end of that POC period, we had successfully completed it and presented it to our customer – who was delighted with the outcome. Throughout the entire four-week process, there was never a sales pitch; their focus was solely on helping us build what we needed for our client.

Sometimes it felt like we were their only customers, even though I know that is not true. Whenever I expressed my gratitude, Anisha replied, “customer obsession is ingrained into us.” Both of them manifested customer obsession – a key leadership principle at Amazon. Anisha even nominated our solution for an AWS award. We won.

It’s refreshing to see employees embody and live by company values. After nearly half a year working with them, I’m still amazed by their unwavering commitment to customer satisfaction. I’m curious how Amazon instills leadership principles.

Only honest feedback fuels growth

You must get feedback to grow in your career. But we Indians often avoid giving honest feedback. I was lucky to have a mentor who gave me brutally honest feedback. Once, I joked about how scary it was to hear his feedback. Something he said really stuck with me: If I care about your growth, I’ll give you feedback. If I don’t, I’ll stay quiet.

If you want your team or mentees to grow, give them honest, specific feedback on what they’re doing right and what needs improvement. If you don’t, you’ll limit their growth because they’ll keep making the same mistakes. They might never see these mistakes unless they discover them through self-reflection, which can take a long time.

Give someone honest, timely feedback if you care about their growth. That’s the only way you can fuel their growth.

Errors of commission and omission are joined at the hip

If you try to minimize Errors of Commission, you will end up with Errors of Omission. And if you try to minimize Errors of Omission, you will end up with Errors of Commission

Vikas gives three examples of how these two errors are interlinked.

If you attend all phone calls, it’s an error of commission and you will end up wasting your time attending spam calls. If you avoid all calls from unknown numbers you might miss an important call – probably a family member or friend calling from an unknown number or from the passport office informing you of status of your passport application (happened to me).

Both errors have a cost and it is impossible to avoid them. So what could be a strategy?

Vikas provides Jeff Bezos as an example. Amazon committed an error of commission to develop Fire Phone which flopped. It had a cost.

But that mindset of better to make errors of commission than errors of omission is the same mindset that led Amazon to launch Kindle, AWS, Prime and so many other services.

Avoiding errors of omission is safe. Just don’t do stupid things. But as Ken Robinson shared in his TED Talk:

If you’re not prepared to be wrong, you’ll never come up with anything original

Jeff Bezos himself writes:

As a company grows, everything needs to scale, including the size of your failed experiments.

Another reason not to avoid errors of omission. You can’t analyse those mistakes. Your errors of omission are invisible. As Buffet wrote in his “Letters to shareholders” in 1992,

Typically, our most egregious mistakes fall in the omission, rather than the commission, category. That may spare Charlie and me some embarrassment, since you don’t see these errors

Do we have to live with this conundrum? Can we resolve it? As Vikas asks,

How can you want the upside of innovation but not the downside?

Vikas goes on to decipher a framework from Amazon’s play book.

cut down on projects that are not working out and double down on those that are working. Those that work out tend to payoff exponentially!

I follow this in stock market investing. I have a framework to analyse companies. Since I have fixed amount of money to invest, I have to allocate capital correctly. I have no crystal ball to look into the future.

I buy all the stocks that fit the framework. After that, I wait a year. I validate my hypothesis. If a stock is working, I double down and accumulate as much as I can. I get rid of stocks that don’t perform according to my hypothesis.

So I commit both errors of omission and commission with significant stress on commission.

I’ve done the same with my career. It’s been a long path for me being a people manager, consultant, startup founder, and software architect. I’ve taken as many chances as I can. Afterward, I pushed and doubled down on whatever worked and I loved, which led to a fulfilling career.

In summary:

  • Both errors of commission and omission has costs
  • Choose to commit errors of commission within a framework of hypothesis and validation
  • Double down on what works

Mercenaries, misfits, and missionaries in an organization

There are three kinds of employees in any organisation – mercenaries, misfits, and missionaries

The mercenaries are transactional. Most of the time they are great at what the company wants them to do, but they’re only in it for the money. If another company offers them a little more, they’ll switch. There’s only one thing they love and are loyal to – money.

There will always be misfits in an organization, no matter what management does. Misfits may come in as misfits or evolve into one. When there is an urgent need, hiring a misfit might be the only option, even if the management knows that the person is a misfit. There are times when existing employees become misfits. A company might change direction as it grows, or a person’s personal situation might change and they become misfits.

Lastly, there are missionaries. They not only bring passion and competence to work, but also rally teams to accomplish impossible missions winning awards and appreciation for the team. They can go out there and find the best talent.

Treating all three equally is a huge mistake.

Missionaries don’t always demand privileges. Failing to appreciate them and not taking care of them well would be deadly. They’re proactive and have agency, so they have valuable connections outside the company. It’s easy for them to get a job. The only reason they haven’t moved on is because they still believe in their mission.

Every company needs mercenaries. You can’t eliminate them. You’ve got to manage them. They know what they’re worth and will demand money and privileges. You have to engage them on their terms and satisfy them because they have skills and competence.

Get rid of the misfits as soon as possible. Your company culture will deteriorate if you’re complacent in dealing with the misfits. They’ll breed and bring more misfits.


This post was inspired by one of my favorite books, Blue Sweater. Jacqueline Novogratz, the author says in the book, “it is said that three kinds of people come to Africa: missionaries, mercenaries, and misfits.”