Reinventing Nerds

Reinventing Nerds

Download on the App Store

Reinventing Nerds episodes

  • Aseem Giri: Managing Technical and Creative Personalities
    Joanie has a conversation with Aseem Giri.  Aseem has over twenty years of experience as an entrepreneur, private equity investor, and investment banker. He is also fond of art, serving as an Art Advisor and/or Finance Advisor to art-related businesses, and he hosts his own podcast, called ACHiEVE, where he interviews people about life-changing events.  Aseem has a lot of experience working with both creative and technical leaders and shares his insights in this episode.
    35 min
  • Aseem Giri: Managing Technical and Creative Personalities
    Joanie has a conversation with Aseem Giri.  Aseem has over twenty years of experience as an entrepreneur, private equity investor, and investment banker. He is also fond of art, serving as an Art Advisor and/or Finance Advisor to art-related businesses, and he hosts his own podcast, called ACHiEVE, where he interviews people about life-changing events.  Aseem has a lot of experience working with both creative and technical leaders and shares his insights in this episode.
    35 min
  • Luis Socconini: Leading Efficient Teams
    Joanie has a conversation with Luis Socconini, the Director of the Lean Six Sigma Institute and master blackbelt in Lean Six Sigma.  He is the author of several books on Lean practices and has run over 300 projects in Mexico, the United States, Spain, and South America.  He is an engineer by training and he has several certificates in quality and manufacturing from very prestigious institutions, like Harvard and MIT.  Luis tells us about how he learned to be a good leader anywhere and how to help teams work more efficiently.
    Highlights:
    Q:  Tell us your story of starting a business in Mexico and moving it to the United States?
    “I’m an industrial engineer with a master’s in quality and productivity.  One of the key factors for a business to grow is to move into different countries.  I learned that since I was learning how to be a businessman.  It was in 2006 when I started my international journey.  I started my first office in South America, in Columbia.  It was an interesting and risky adventure.  It was something I really wanted to do, so I decided to take the risk.  After that, I started an office in Spain, and later in Switzerland.  It was in 2010 when I decided to expand to the United States.  One of the reasons was because some of my clients in Mexico and South America were American companies and they were asking us, ‘Why don’t you help us in the United States?  Why don’t you have an office?’  It was an idea that my clients gave me, and I decided to take the opportunity.  In 2010, as you know, it was not an easy time.  It was an economic situation where the world was the world was really difficult.  It was an interesting journey.”
    Q: You moved your family here, right?  How was that?
    “Yes, we moved all together.  I presented this opportunity to my wife.  At first, I had to convince her.  I thought she was going to say ‘no.’  But then she said, ‘why not?  Let’s try it.’  We decided to take one year and try it and if it didn’t work out, we would move back to Mexico.  The first year was fantastic!  We learned a lot.  It was a completely different change in the way we live, the way we interact with kids, and the way we work.”
    Q: What is Lean Six Sigma?
    “Lean is a philosophy, a methodology, and a set of tools created by Toyota.  Toyota created this methodology based on the learnings they had from when Japanese companies came to the United States to learn best practices so they could improve their productivity based on the U.S. productivity after the second World War, that was eight times higher.  They took all this knowledge and converted it into a system.  It was called the Toyota Production System.  On the other hand, Six Sigma was created by Motorola.  They created it as a secret project in the 80s.  At the end of the 80s they presented it as a project to succeed in quality.  They had a lot of problems with quality.  It was in 1988 when Motorola won the Quality Award given by President Ronald Reagan.  Ronald Reagan said to Bob Allen, who was the CEO, it was incredible how you improved quality.  You have to show this to the world!  And Bob Allen said okay and they called it Six Sigma.  Together, Lean and Six Sigma became the most powerful methodology to improve quality and productivity.”
    “We can condense this into two words.  Lean Six Sigma is about speed and quality.  You need speed and quality for sales, marketing.  If you have a restaurant or hotel, you need speed and quality.  Even in decision making we need speed and quality.”
    Q: What kinds of challenges are your clients usually facing, especially in technical organizations?
    “A large number of companies are dealing with delivery time and cost, especially cost.  Individuals are also facing increasing job opportunities and increasing competition.  The typical customer we have is not delivering their products on time.  In a software company, one of the main headaches they have is they are not delivering on time...
    35 min
  • Luis Socconini: Leading Efficient Teams
    Joanie has a conversation with Luis Socconini, the Director of the Lean Six Sigma Institute and master blackbelt in Lean Six Sigma.  He is the author of several books on Lean practices and has run over 300 projects in Mexico, the United States, Spain, and South America.  He is an engineer by training and he has several certificates in quality and manufacturing from very prestigious institutions, like Harvard and MIT.  Luis tells us about how he learned to be a good leader anywhere and how to help teams work more efficiently.
    Highlights:
    Q:  Tell us your story of starting a business in Mexico and moving it to the United States?
    “I’m an industrial engineer with a master’s in quality and productivity.  One of the key factors for a business to grow is to move into different countries.  I learned that since I was learning how to be a businessman.  It was in 2006 when I started my international journey.  I started my first office in South America, in Columbia.  It was an interesting and risky adventure.  It was something I really wanted to do, so I decided to take the risk.  After that, I started an office in Spain, and later in Switzerland.  It was in 2010 when I decided to expand to the United States.  One of the reasons was because some of my clients in Mexico and South America were American companies and they were asking us, ‘Why don’t you help us in the United States?  Why don’t you have an office?’  It was an idea that my clients gave me, and I decided to take the opportunity.  In 2010, as you know, it was not an easy time.  It was an economic situation where the world was the world was really difficult.  It was an interesting journey.”
    Q: You moved your family here, right?  How was that?
    “Yes, we moved all together.  I presented this opportunity to my wife.  At first, I had to convince her.  I thought she was going to say ‘no.’  But then she said, ‘why not?  Let’s try it.’  We decided to take one year and try it and if it didn’t work out, we would move back to Mexico.  The first year was fantastic!  We learned a lot.  It was a completely different change in the way we live, the way we interact with kids, and the way we work.”
    Q: What is Lean Six Sigma?
    “Lean is a philosophy, a methodology, and a set of tools created by Toyota.  Toyota created this methodology based on the learnings they had from when Japanese companies came to the United States to learn best practices so they could improve their productivity based on the U.S. productivity after the second World War, that was eight times higher.  They took all this knowledge and converted it into a system.  It was called the Toyota Production System.  On the other hand, Six Sigma was created by Motorola.  They created it as a secret project in the 80s.  At the end of the 80s they presented it as a project to succeed in quality.  They had a lot of problems with quality.  It was in 1988 when Motorola won the Quality Award given by President Ronald Reagan.  Ronald Reagan said to Bob Allen, who was the CEO, it was incredible how you improved quality.  You have to show this to the world!  And Bob Allen said okay and they called it Six Sigma.  Together, Lean and Six Sigma became the most powerful methodology to improve quality and productivity.”
    “We can condense this into two words.  Lean Six Sigma is about speed and quality.  You need speed and quality for sales, marketing.  If you have a restaurant or hotel, you need speed and quality.  Even in decision making we need speed and quality.”
    Q: What kinds of challenges are your clients usually facing, especially in technical organizations?
    “A large number of companies are dealing with delivery time and cost, especially cost.  Individuals are also facing increasing job opportunities and increasing competition.  The typical customer we have is not delivering their products on time.  In a software company, one of the main headaches they have is they are not delivering on time...
    35 min
  • Bob Salomon: Learning Disabilities, Computers, and Communicating
    Joanie has a conversation with Bob Salomon, president of CIO Systems.  One of the coolest things about Bob is his willingness to talk about how he’s dealt with dyslexia and ADD and how that actually motivated him to get into tech. Bob also talks about how they “make IT boring” at CIO Systems.  They do IT security and support and help employees more be more productive.  In addition, Bob talks about how to network and ways to get involved in community service.
    Highlights:
    Q: Tell us your story of how having dyslexia and ADD drew you into IT work.
    “It’s been a major stumbling block and also a path for me.  I grew up in the 60s and 70s.  At the time, it wasn’t quite understood.  I did terrible in school.  I was a C-D student for most of elementary and high school.  I only got into college because, at the time, it was very easy to get into state university.  All you had to do was score a certain level on the SAT.  My SAT scores were very high and, even though my grades were very low, I automatically got into State.
    I went to Cal State Long Beach.  There it was the second time I’d ever had to touch a computer.  Back then, it was virtually impossible for the average person to get close to a computer.  There was an Apple II in the library, and I started programming on that.  One of my nerd friends, he was in the mathematics department, and he gave me an account on school mainframe, the PDP-11/70.
    There wasn’t a good word processing program at that time.  There were text programs, but you had to keep switching between modes and there was no visible cursor.  You had to remember where you were and type commands to move forward or back to a document.  So it was very cumbersome.  I actually wrote my own word processing program with a dictionary.  That’s a major accomplishment to be able to create a dictionary when you’re dyslexic.  I was actually the first person to hand in computer-generated homework for a liberal arts class.  The teacher had to go to the academic senate to get approval to accept my homework.
    They had a program for adults with learning disabilities at California State.  It was an excellent program and I was very happy to get into that.  With that support, I was able to graduate on the President’s Honor Roll.  I went from being a C student to the President’s Honor Roll.  Just by doing my work on the computer and handing it in that way made all the difference in the world.
    For so long, it was impossible to communicate by writing.  I would think of words and I would think of them phonetically and there was no easy way of looking them up in a dictionary.  I would have to think of synonyms and it was very hard to edit and I would mess up the edits.  Basically, all of my life I had a very negative view of myself because everything I did was terrible.”
    Bob’s story continues to be riveting.  To hear how he turned himself around, managed through his frustrations, and empowered himself to start his own company, as well as how he developed his people skills and how he delights customers, listen to the podcast.
    Words of Wisdom:
    It’s very common for people with ADD to run their own company.
    As an IT expert, I’ve monetized my paranoia.
    Computers are there to be tools and they need to be up and running.
    If we do it right, nothing should happen and selling nothing is sometimes a little harder than it should be.
    Shout Out:
    Brian Jackson at Sandler Training for sales training.
    Contact Bob Salomon:
    Call: 619-293-8600
    LinkedIn: https://www.linkedin.com/in/bob-salomon-675872b/
    Website: ciosys.com
    33 min
  • Bob Salomon: Learning Disabilities, Computers, and Communicating
    Joanie has a conversation with Bob Salomon, president of CIO Systems.  One of the coolest things about Bob is his willingness to talk about how he’s dealt with dyslexia and ADD and how that actually motivated him to get into tech. Bob also talks about how they “make IT boring” at CIO Systems.  They do IT security and support and help employees more be more productive.  In addition, Bob talks about how to network and ways to get involved in community service.
    Highlights:
    Q: Tell us your story of how having dyslexia and ADD drew you into IT work.
    “It’s been a major stumbling block and also a path for me.  I grew up in the 60s and 70s.  At the time, it wasn’t quite understood.  I did terrible in school.  I was a C-D student for most of elementary and high school.  I only got into college because, at the time, it was very easy to get into state university.  All you had to do was score a certain level on the SAT.  My SAT scores were very high and, even though my grades were very low, I automatically got into State.
    I went to Cal State Long Beach.  There it was the second time I’d ever had to touch a computer.  Back then, it was virtually impossible for the average person to get close to a computer.  There was an Apple II in the library, and I started programming on that.  One of my nerd friends, he was in the mathematics department, and he gave me an account on school mainframe, the PDP-11/70.
    There wasn’t a good word processing program at that time.  There were text programs, but you had to keep switching between modes and there was no visible cursor.  You had to remember where you were and type commands to move forward or back to a document.  So it was very cumbersome.  I actually wrote my own word processing program with a dictionary.  That’s a major accomplishment to be able to create a dictionary when you’re dyslexic.  I was actually the first person to hand in computer-generated homework for a liberal arts class.  The teacher had to go to the academic senate to get approval to accept my homework.
    They had a program for adults with learning disabilities at California State.  It was an excellent program and I was very happy to get into that.  With that support, I was able to graduate on the President’s Honor Roll.  I went from being a C student to the President’s Honor Roll.  Just by doing my work on the computer and handing it in that way made all the difference in the world.
    For so long, it was impossible to communicate by writing.  I would think of words and I would think of them phonetically and there was no easy way of looking them up in a dictionary.  I would have to think of synonyms and it was very hard to edit and I would mess up the edits.  Basically, all of my life I had a very negative view of myself because everything I did was terrible.”
    Bob’s story continues to be riveting.  To hear how he turned himself around, managed through his frustrations, and empowered himself to start his own company, as well as how he developed his people skills and how he delights customers, listen to the podcast.
    Words of Wisdom:
    It’s very common for people with ADD to run their own company.
    As an IT expert, I’ve monetized my paranoia.
    Computers are there to be tools and they need to be up and running.
    If we do it right, nothing should happen and selling nothing is sometimes a little harder than it should be.
    Shout Out:
    Brian Jackson at Sandler Training for sales training.
    Contact Bob Salomon:
    Call: 619-293-8600
    LinkedIn: https://www.linkedin.com/in/bob-salomon-675872b/
    Website: ciosys.com
    33 min
  • David Oates: Managing Coronavirus and Other Crises

    David Oates is a Crisis PR expert with 25 years of experience in the field. He helps organizations repair their brand’s reputation in the press and online. He can handle any Crisis PR situation and train others to do the same. As a U.S. Navy Public Affairs Officer and a corporate PR professional, he dealt with a broad range of Crisis PR issues. These include mass layoffs, large-scale accidents, product recall, inappropriate acts by executives, and more. He’s also been a key advisor for companies during the Coronavirus crisis. Do you know what to do—and what NOT to do—in these situations?  Listen to the episode.
    Highlights:
    Q: Tell us your story of how you’ve worked with nerds on PR crisis management and in what contexts.
    “I was an officer in the Navy and, in the mid-nineties, I became a PR Officer.  Crisis was just a part of the day’s activities.  As you can imagine, in the military you’re in foreign ports of call, you’re in combat situations.  There are 24-hour very heavy industrial operations, so accidents, sailors and marines behaving badly, different hot war engagements and so on.”
    “After that, I went into corporate America.  I worked largely, but not exclusively, with startups and small cap publicly traded companies.  The things that we would work on, in addition to promoting their software products, was if there were adverse news events that would occur that would get the ire of not just the press, but also of their highly trained employees that they were trying to keep.  Just as important to them were their customers and their investors.”
    “Those types of scenarios were such that when there were things they didn’t want to talk about, I had to get them prepared to talk about them—in such a way as to allay the concerns of employees, who were going to go literally across the street to the next job opportunity, and investors who were going to be reticent about getting the next round of funding closed or secured, while keeping the executive team intact, and certainly customers who were taking the risk to go with this new product in beta mode.”
    “I was also head of marketing in-house for a software company and, about 13 years ago, I went out on my own.  It’s been a great ride!”
    Q: What constitutes a Crisis PR event and who is involved, especially in technical companies?
    “When folks think about PR, and certainly Crisis PR, they naturally default to the news organizations and the general public.  That’s good to focus on, but often focusing on that is at the detriment of focusing on even more important audiences—employees, customers, partners, investors, and other stakeholders.  Notice I named employees first.”
    “There are two things to think about with employees.  First off, they are the ones who are dealing with the customers and stakeholders on a daily basis.  They are the front lines of you being able to articulate a value proposition and deliver on that.  If the employees are not told what’s going on, and are not addressed on their concerns, and are not able to be empowered with messaging to say to the other stakeholders, you’re done.  You won’t repair yourself.”
    “I don’t care what you say to a reporter or to a news organization.  If the employees don’t buy into it and are not brought in to help you through it, the story will linger.  It will then perpetuate on the blogosphere.  Google will index it.  You’ll then see negative reviews on things like Glassdoor and other tech review sites.  Blog reviews, like Mashable and TechCrunch will pick up on that and it will be a real mess.  This is most important for tech companies.”
    Listen in to hear answers to these questions too.
    What kinds of challenges do technical leaders tend to have in responding to a crisis PR event?  How do handle Coronavirus Crisis PR and other similar health situations.
    29 min
  • David Oates: Managing Coronavirus and Other Crises

    David Oates is a Crisis PR expert with 25 years of experience in the field. He helps organizations repair their brand’s reputation in the press and online. He can handle any Crisis PR situation and train others to do the same. As a U.S. Navy Public Affairs Officer and a corporate PR professional, he dealt with a broad range of Crisis PR issues. These include mass layoffs, large-scale accidents, product recall, inappropriate acts by executives, and more. He’s also been a key advisor for companies during the Coronavirus crisis. Do you know what to do—and what NOT to do—in these situations?  Listen to the episode.
    Highlights:
    Q: Tell us your story of how you’ve worked with nerds on PR crisis management and in what contexts.
    “I was an officer in the Navy and, in the mid-nineties, I became a PR Officer.  Crisis was just a part of the day’s activities.  As you can imagine, in the military you’re in foreign ports of call, you’re in combat situations.  There are 24-hour very heavy industrial operations, so accidents, sailors and marines behaving badly, different hot war engagements and so on.”
    “After that, I went into corporate America.  I worked largely, but not exclusively, with startups and small cap publicly traded companies.  The things that we would work on, in addition to promoting their software products, was if there were adverse news events that would occur that would get the ire of not just the press, but also of their highly trained employees that they were trying to keep.  Just as important to them were their customers and their investors.”
    “Those types of scenarios were such that when there were things they didn’t want to talk about, I had to get them prepared to talk about them—in such a way as to allay the concerns of employees, who were going to go literally across the street to the next job opportunity, and investors who were going to be reticent about getting the next round of funding closed or secured, while keeping the executive team intact, and certainly customers who were taking the risk to go with this new product in beta mode.”
    “I was also head of marketing in-house for a software company and, about 13 years ago, I went out on my own.  It’s been a great ride!”
    Q: What constitutes a Crisis PR event and who is involved, especially in technical companies?
    “When folks think about PR, and certainly Crisis PR, they naturally default to the news organizations and the general public.  That’s good to focus on, but often focusing on that is at the detriment of focusing on even more important audiences—employees, customers, partners, investors, and other stakeholders.  Notice I named employees first.”
    “There are two things to think about with employees.  First off, they are the ones who are dealing with the customers and stakeholders on a daily basis.  They are the front lines of you being able to articulate a value proposition and deliver on that.  If the employees are not told what’s going on, and are not addressed on their concerns, and are not able to be empowered with messaging to say to the other stakeholders, you’re done.  You won’t repair yourself.”
    “I don’t care what you say to a reporter or to a news organization.  If the employees don’t buy into it and are not brought in to help you through it, the story will linger.  It will then perpetuate on the blogosphere.  Google will index it.  You’ll then see negative reviews on things like Glassdoor and other tech review sites.  Blog reviews, like Mashable and TechCrunch will pick up on that and it will be a real mess.  This is most important for tech companies.”
    Listen in to hear answers to these questions too.
    What kinds of challenges do technical leaders tend to have in responding to a crisis PR event?  How do handle Coronavirus Crisis PR and other similar health situations.
    29 min
  • Eric Weiss: Building Products People Love

    Joanie interviews Eric Weiss, founder of Full Cycle Product Development.  Eric has led massive development projects worth billions of dollars, including the Sony Playstation 3 and Qualcomm’s $9 Billion patent licensing machine. Eric is a product technology consultant and startup advisor and the author of Build the Right Things: How to Design and Build a Product People Will Love.
    Highlights:
    Q: Tell us how you got to where you are now and how you came to write your book.
    “I’m an engineer by trade.  I’ve been writing code since I was very young, went to school for it, and started to work as a software developer.  But I really quickly learned that my passion was in product and leadership and startups and so I went and got my MBA.  I got certified to be a project manager and a Scrum Master and all this stuff.  I bridged the gap between the technology and engineering side of things and the product and business side of things.  I spent much of my career at very large tech companies driving very large engineering projects.”
    “But then I’ve had this consulting practice on the side now, for over 10 years now, working with early stage startups and growth stage startups to validate their business model, to gain traction, to raise early capital, and then ultimately scale up and grow and get acquired.  I’ve been a CTO and completely owned the delivery model.  I discovered through experience that, while I was so focused on the efficiency of my development team, and having clean and clear Agile methodologies, nothing was less efficient than working on the wrong things.  I started really heavily leaning into product management and the user experience to make sure we were focusing on the right things.  This culminated in the book.”
    Q: How do you get engineers to care about the customer experience or to see it from the customer’s perspective?  How do you understand what features your customers really need?
    “Yes, engineers love technology, but more than anything, they want to have purpose.  They want to know the work they do has meaning and impact to benefit real people.  The other thing is that engineering is a really creative endeavor.  They don’t like to be told what to do.”
    “The challenge is that too many teams are structured in a way and too many leaders lead in a way that puts engineers in this mode where they’re decoupled from the purpose of their work.  They’re not given creative freedom and they almost become beaten down and they get to where they don’t care and just want to play around with the technology because it gives them some enjoyment, but they’re disconnected from the larger picture.”  To hear Eric’s solutions to this problem and to hear answers to these other questions, listen to the episode.
    Other questions that Eric answers: How do you build effective Agile teams?  How do the people on the teams survive a “never-ending marathon” of Agile?  What common people issues do you see in the startups that you advise?
    Get a free copy of Eric’s book here.  Watch Eric’s talk on Agile First Principles here.
    Words of Wisdom:
    It’s not the velocity of our Scrums, it’s that we don’t understand our customers or ourselves well enough to know what the user experience should be.
    People are the most difficult part of building products.  Technology is very rarely the thing that holds us back.
    CEOs are an interesting bunch and have to be dealt with delicately.
    Be fearless and go out and do things.
    Contact Eric Weiss:
    Website: FullCycleProduct.com
    https://www.linkedin.com/in/ericmweiss/
    32 min
  • Eric Weiss: Building Products People Love

    Joanie interviews Eric Weiss, founder of Full Cycle Product Development.  Eric has led massive development projects worth billions of dollars, including the Sony Playstation 3 and Qualcomm’s $9 Billion patent licensing machine. Eric is a product technology consultant and startup advisor and the author of Build the Right Things: How to Design and Build a Product People Will Love.
    Highlights:
    Q: Tell us how you got to where you are now and how you came to write your book.
    “I’m an engineer by trade.  I’ve been writing code since I was very young, went to school for it, and started to work as a software developer.  But I really quickly learned that my passion was in product and leadership and startups and so I went and got my MBA.  I got certified to be a project manager and a Scrum Master and all this stuff.  I bridged the gap between the technology and engineering side of things and the product and business side of things.  I spent much of my career at very large tech companies driving very large engineering projects.”
    “But then I’ve had this consulting practice on the side now, for over 10 years now, working with early stage startups and growth stage startups to validate their business model, to gain traction, to raise early capital, and then ultimately scale up and grow and get acquired.  I’ve been a CTO and completely owned the delivery model.  I discovered through experience that, while I was so focused on the efficiency of my development team, and having clean and clear Agile methodologies, nothing was less efficient than working on the wrong things.  I started really heavily leaning into product management and the user experience to make sure we were focusing on the right things.  This culminated in the book.”
    Q: How do you get engineers to care about the customer experience or to see it from the customer’s perspective?  How do you understand what features your customers really need?
    “Yes, engineers love technology, but more than anything, they want to have purpose.  They want to know the work they do has meaning and impact to benefit real people.  The other thing is that engineering is a really creative endeavor.  They don’t like to be told what to do.”
    “The challenge is that too many teams are structured in a way and too many leaders lead in a way that puts engineers in this mode where they’re decoupled from the purpose of their work.  They’re not given creative freedom and they almost become beaten down and they get to where they don’t care and just want to play around with the technology because it gives them some enjoyment, but they’re disconnected from the larger picture.”  To hear Eric’s solutions to this problem and to hear answers to these other questions, listen to the episode.
    Other questions that Eric answers: How do you build effective Agile teams?  How do the people on the teams survive a “never-ending marathon” of Agile?  What common people issues do you see in the startups that you advise?
    Get a free copy of Eric’s book here.  Watch Eric’s talk on Agile First Principles here.
    Words of Wisdom:
    It’s not the velocity of our Scrums, it’s that we don’t understand our customers or ourselves well enough to know what the user experience should be.
    People are the most difficult part of building products.  Technology is very rarely the thing that holds us back.
    CEOs are an interesting bunch and have to be dealt with delicately.
    Be fearless and go out and do things.
    Contact Eric Weiss:
    Website: FullCycleProduct.com
    https://www.linkedin.com/in/ericmweiss/
    32 min

About Reinventing Nerds

From the publisher's feed

People Strategies for Technical People