Tag Archives: engineers

Alex Balazs: The Benefits of Inclusive Leadership



Joanie interviews Alex Balazs, Senior Vice President and Chief Architect at Intuit.  Alex shares the story of his transformation from being a quiet engineer to becoming a communicative leader.  He also shares his insights on inclusion and describes how he is supportive of women in tech.  Being inclusive is key for Alex and he shares why.  He is also on the Board of Lead Inclusively, Inc., a company that helps companies be more inclusive.  We cover a lot in this episode, so be sure to listen to the end.

Highlights:

Q: Tell us the story of how you came to work at Intuit.

“I was born in Ohio and was raised in the Midwest. I always had this feeling that I needed to expand my horizons.  Post graduate, I moved to Northern California and worked for Carl Zeiss.  My first professional program language was Assembly.  I went to work for a startup in Boston and it didn’t work out, but a mentor from Carl Zeiss had just bought a small startup called Intuit and invited me to interview.  I started at Intuit in 1999.”

Q: How did you branch out of being a quiet engineer?

“I was a total introvert growing up.  I was always confident in my personal ability but didn’t know how to communicate.  There was a dissonance between what I felt I could say and what I felt was coming out of my mouth.  And it led me to not say things.  I was afraid I would say something stupid.  I felt the need to be the smartest person in the room and if I didn’t feel I was then I didn’t say anything.”

“There were a couple of events in my early Intuit career where my leadership moved on.  This was the leadership that was responsible for communicating to the rest of Intuit and figuring out which projects we should be working on.  When they all left, I said, ‘Now what am I supposed to do?’  I felt really sorry for myself.  I was afraid. I was angry.  I was upset.  And suddenly I just said, ‘This is an opportunity for me, and I don’t know how I’m going to do it, but I’m going to transform myself into someone who can communicate.’  Through that process I learned that I had to start putting myself out there.”

“The last part of the transformation for me was the transformation from hoping I was the smartest person in the room to expecting I was the dumbest person in the room.”

Q: How does surrounding yourself with people who are smarter than you improve your leadership?

“I do think as you get into leadership roles, it is the only way to be successful.  I’ve seen leaders who’ve tried to be leaders and the smartest person in the room, and it doesn’t work.  Smart people don’t want to work for you.  Smart people with ideas don’t want to speak up.  As an engineer, your job is to assert and to take up space.  I realized as a leader, my job is to create space so that other people can step into that space.”

“And when I did that, the notion of introvert/extrovert became a misnomer.  It wasn’t necessarily about me becoming an extrovert.  It was about me bringing in diverse thought and viewpoints from everyone, including many engineers who are introverts.”

To hear Alex’s tips on how to bring in introverts, how he is inclusive of all diverse people, and how he supports women in tech, listen to the episode.

Words of Wisdom:

“Think of three concentric circles: your comfort zone, your learning zone, and your panic zone.  The only way to make your comfort zone bigger is to get into your learning zone.”

“Surround yourself with people who are smarter than you.”

“I don’t know how a company can survive without being diverse.”

“Working for tech companies, we actually have privilege.”

Contact Alex Balazs:

LinkedIn: https://www.linkedin.com/in/alexgbalazs/

Twitter: @alexgbalazs


Vidya Dinamani: Connecting with Product Managers



Joanie interviews Vidya Dinamani, founder of Product Rebels.  Vidya uses her impressive experience in product management to teach others how to do it.  She calls herself a fully qualified nerd, having started her career coding, with a physics degree in her pocket.  Vidya is quite articulate and has really nailed how developers and product managers can work together successfully.  She doesn’t go with the canned messages, but rather has her own that will no doubt resonate with you.

Highlights:

Q: What kinds of nerds do you work with?

“I have been very lucky to work with some really awesome nerds, some really smart people. I worked at Intuit for ten years. Intuit attracts great people—engineers, designers, researchers, product managers.  There really isn’t a dud among them. At Mitchell, I worked with product design teams.  I’ve worked with and coached hundreds of product managers.  We always extend to working with engineers as well.  You can’t have one without the other; it’s symbiotic.”

Q: What do you mean by product management and design being like a marriage?

“Think about it.  You spend more time together than you probably do with your spouse.  It’s like a marriage whether you like it or not.  When I think about a great relationship, a great marriage, I think about having someone on your side, someone who’s got your back.”

Q: What kind of challenges tend to arise in this relationship from the product management perspective?

“A product manager is the representative of the customer at the table.  People who are good product managers take that very seriously.  They take the solutions to make sure they really work for the customer.  When you get deep into your customer’s shoes and see the solutions, you jump into the ‘how.’”

“We’re all problem solvers, as nerds.  This is why we do what we do. We often throw solutions at problems.  That gets us into trouble when we don’t step back.  You’ve got to think about a problem in a way that whether you and your elegant product existed or not, the customer still has the problem.  That’s really hard to do.”

Q: How do you help customers understand they may not know what their problem is?

“A lot of time, asking the customer what they want isn’t the way to do it.  You have to watch the customer in their natural habitat.  You turn these observations into fully formed sentences.  Then the magic of product management happens.  You get “ahas.”  You create hypotheses.  Product managers spend a lot of time testing their hypotheses and then go to the engineers when they’ve figured out the problem. Then they talk through solutions.”

Q: How does trust break down between development and product management?

“It can feel like high-level business speak to say, ‘we’re all on the same team.’  It can feel like something different when you’re trying to get a product out.  The developer is trying to get the best, most elegant solution.  The trust breaks down when they’re being told what to do.  When the trust breaks down, the product manager feels like the only thing to do is to tell them exactly what to do.”

Q: How do you reduce barriers to trust?

“I like decision matrices.  I invite you into my world, but I am the decision-maker.  When it’s my world, I make the decision.  When it’s your world, I can contribute, but the engineer makes the decision.”

To hear more about respecting boundaries, setting roles, and trusting others, and much much more, listen to the episode.

Words of Wisdom:

“Share the pen.”

“You’ve got to be okay with others being wrong and turn it into a learning mindset.”

“You’ve got to be bold to try things you’re going to be surprised with.”

“Ask ‘why’ next time in a meeting.”

Contact Vidya Dinamani:

Website: productrebels.com

Email: vidya@productrebels.com

Twitter: @vdinamani