Note: This article is written for web publication and summarizes the leadership lessons, hiring ideas, and startup culture takeaways connected to SaaStr Podcast #165 featuring Harry Glaser, founder and CEO of Periscope Data.
Introduction: Diversity Is Not a Poster on the Office Wall
Building a diverse team sounds simple until a founder has to do it on a Tuesday afternoon while also fixing churn, hiring salespeople, calming investors, debugging product strategy, and wondering why the office cold brew vanished before lunch. That is why SaaStr Podcast #165 with Harry Glaser remains useful for startup leaders: it treats diversity not as a slogan, but as an operating system.
Harry Glaser, founder and CEO of Periscope Data, spoke with SaaStr about the real work behind creating well-rounded teams in SaaS. Periscope Data was known for helping companies transform business data into actionable analytics, and its growth story gives the discussion extra weight. The company raised significant venture funding, served hundreds of customers, and later became part of Sisense, a major business intelligence and analytics company. In other words, this was not a theoretical chat from a mountaintop. It was advice from someone who had actually built, hired, scaled, and wrestled with the messy human side of a fast-growing startup.
The central lesson is refreshingly practical: diverse teams do not appear because a founder “cares about diversity.” They appear when leaders redesign the company’s habits, pipelines, interviews, scorecards, culture, and accountability systems. Good intentions are a nice appetizer. Process is the meal.
Who Is Harry Glaser and Why Does His View Matter?
Harry Glaser co-founded Periscope Data, a company built around analytics-as-code and data-driven decision-making. Before Periscope, he worked as a product manager at Google, where experimentation, metrics, and user behavior were part of daily life. That background matters because Glaser’s approach to team building is not soft and fuzzy in the vague “let’s all hold hands near a whiteboard” sense. It is structured, measurable, and grounded in how companies actually grow.
Periscope Data operated in a competitive SaaS market where talent quality could make or break the company. Analytics products require engineers, data professionals, product thinkers, customer-facing teams, marketers, and managers who can communicate clearly across functions. In that kind of environment, a one-note team is dangerous. If everyone has the same background, the same network, the same assumptions, and the same blind spots, the company may move fastbut sometimes straight into a wall.
That is why the SaaStr Podcast #165 topic still resonates: building diverse teams is not charity. It is strategy. In SaaS, where products serve customers across industries, regions, roles, and company sizes, diversity of perspective helps teams understand more problems, challenge weak assumptions, and build products that work outside the founders’ personal bubble.
The Big Idea: Diverse Teams Need Systems, Not Speeches
A common startup mistake is treating diversity like a recruiting campaign instead of a company design problem. Founders may say, “We want a diverse team,” then continue hiring from the same schools, asking the same friends for referrals, writing the same narrow job descriptions, and running the same unstructured interviews. Then they act shocked when the candidate pool looks exactly like the current team. That is not a mystery. That is math wearing a hoodie.
Glaser’s lesson can be summarized this way: if you want different outcomes, you need different inputs. The first step is not to blame the market or claim that diverse candidates are impossible to find. The first step is to examine the system. Where do candidates come from? Who screens resumes? What criteria matter? Who gets interviewed? Who makes the final call? Which behaviors are rewarded after hiring? Where do people stall in promotion paths?
When companies ask these questions honestly, they often discover that their hiring process was built for speed and familiarity, not fairness and excellence. The goal is not to lower the bar. The goal is to define the bar clearly enough that more qualified people can reach it.
Step 1: Admit the Current Team Is the Starting Point, Not the Finish Line
Many SaaS startups begin with a small founding group that looks fairly similar. That can happen because founders hire people they already know, and early networks are often narrow. The problem is not that the first five people share a background. The problem is pretending that pattern should scale to the next 50, 150, or 500 employees.
A founder building truly diverse teams must start with a basic audit. Look at the current organization by department, level, manager, function, and candidate source. A company may appear diverse overall while leadership remains homogeneous. Or engineering may lack gender diversity while customer success has a much broader mix. Averages can hide problems like a magician hiding a rabbit, except the rabbit is your promotion pipeline.
This audit should be handled carefully and legally, especially in the United States, where employers must comply with equal employment opportunity rules. The practical point is simple: understand your baseline. You cannot improve what you refuse to measure.
Step 2: Expand the Candidate Pipeline Before You Need It
One of the most useful hiring lessons from the SaaS world is that pipeline quality determines hiring quality. If every open role is filled through the same three referral networks, the company will likely reproduce itself. Referrals can be powerful, but they can also create an echo chamber with snacks.
To build a stronger pipeline, startups should source from multiple channels: professional communities, bootcamps, historically underrepresented talent networks, universities beyond the usual elite list, industry groups, returnship programs, open-source communities, and internal employee referrals with deliberate outreach guidelines. The key is to begin before panic hiring starts. When a company waits until “we needed this person yesterday,” it usually falls back on speed, familiarity, and bias.
Job descriptions also deserve attention. Overloaded requirements can discourage strong candidates who do not check every box. Phrases like “rockstar,” “ninja,” or “must thrive in a high-pressure, no-excuses environment” may sound exciting to a founder but signal chaos to many applicants. A better job post separates true must-haves from nice-to-haves, explains the impact of the role, and uses plain language. Clear beats clever. Candidates should not need a decoder ring to understand whether they qualify.
Step 3: Replace “Culture Fit” With “Culture Add”
“Culture fit” may be one of the most dangerous phrases in startup hiring. Sometimes it means shared values, which is useful. But too often it means, “Would I enjoy sitting next to this person on a long flight?” That is not a hiring criterion. That is a travel preference.
Truly diverse teams require a shift from culture fit to culture add. Instead of asking whether a candidate resembles the existing team, ask what perspective, skill, customer understanding, communication style, or problem-solving method they add. A sales leader from a nontraditional background may understand a customer segment the company has ignored. A product manager who has worked in regulated industries may prevent avoidable enterprise mistakes. A data scientist with strong storytelling skills may help executives actually use the numbers instead of admiring dashboards like museum art.
This does not mean hiring people who reject the company’s values. It means defining values in behavioral terms. For example, “customer obsession” can mean listening deeply, following up quickly, and using evidence to improve the product. It should not mean “laughs at the same jokes as the founders.”
Step 4: Structure Interviews Like a Product Experiment
Unstructured interviews feel natural, but they often reward confidence, similarity, and personal chemistry. A founder may walk away thinking, “Great candidate, we really clicked,” when the actual signal was that both people enjoy the same productivity podcast and complain about airport Wi-Fi with equal passion.
Structured interviews help reduce this problem. Every candidate for the same role should be assessed against the same core competencies. Interviewers should ask consistent questions, use scorecards, write feedback before group discussion, and separate evidence from impressions. For example, “candidate explained a customer retention analysis using cohort data” is useful. “Candidate had executive energy” is vague enough to mean almost anything, including “wore a blazer.”
For SaaS roles, useful competencies might include customer empathy, analytical reasoning, product judgment, technical depth, written communication, collaboration, and ownership. The company should define what strong, average, and weak evidence looks like for each. This approach does not make hiring robotic. It makes hiring fairer, clearer, and less dependent on whoever had the loudest opinion in the debrief.
Step 5: Build Diverse Interview Panels Without Turning People Into Symbols
Diverse interview panels can improve perspective, but they must be handled thoughtfully. Companies should not repeatedly burden the same employees from underrepresented groups with every interview just to make the process “look inclusive.” That creates invisible labor and, frankly, it is a fast way to make your best people wonder whether they were hired for their expertise or their calendar availability.
A better approach is to train a broad set of interviewers, rotate responsibilities fairly, and ensure that all panelists know exactly what they are evaluating. Interviewers should not all ask the same questions. One person may evaluate technical depth, another communication, another customer problem-solving, and another leadership behaviors. The goal is not theater. The goal is better signal.
Step 6: Make Inclusion a Daily Management Practice
Hiring diverse talent is only half the work. Keeping, growing, and promoting that talent is where companies prove whether they meant it. A startup can recruit brilliantly and still lose people if meetings are dominated by the same voices, promotions happen through backchannels, feedback is uneven, or managers avoid difficult conversations.
Inclusive leadership is practical. It means creating psychological safety so people can ask questions, admit mistakes, challenge assumptions, and offer ideas without being punished socially or professionally. It means managers notice who is interrupted, who receives stretch assignments, who gets credit, and who is quietly doing glue work that keeps the company functioning but never appears in performance reviews.
For SaaS companies, inclusion also improves decision-making. Customer success may see churn risks before product does. Sales may notice messaging confusion before marketing does. Data teams may catch adoption patterns that executives miss. A culture where only the highest-ranking person speaks freely wastes intelligence the company already paid for. That is not leadership. That is leaving money on the table and then scheduling a meeting to ask where the money went.
Step 7: Use Data, But Do Not Hide Behind It
Glaser’s background in data makes this point especially relevant. Data can help leaders spot patterns in hiring, promotions, attrition, compensation, and employee engagement. But data should support judgment, not replace it. A dashboard can show that a certain group leaves faster than others; it cannot, by itself, fix a manager who gives vague feedback or a promotion process that rewards self-promotion over impact.
Startups should track hiring funnel data by stage: applicants, recruiter screens, hiring manager screens, technical assessments, final interviews, offers, acceptances, and retention. If underrepresented candidates enter the funnel but disappear after one particular stage, investigate that stage. Maybe the assessment is unrelated to the job. Maybe interviewers are inconsistent. Maybe scheduling delays cause great candidates to accept other offers. The data points to smoke; leaders still need to find the fire.
Step 8: Connect Diversity to Customer Understanding
In SaaS, diverse teams are especially valuable because customers are diverse. A product built only from one viewpoint may miss accessibility needs, workflow differences, regional expectations, industry language, procurement concerns, or buyer motivations. When a company moves upmarket, as Periscope Data discussed in the SaaStr episode, this becomes even more important. Enterprise customers often involve many stakeholders: technical users, business leaders, security teams, finance, legal, operations, and executive sponsors.
A team with broader experience is more likely to anticipate these needs. A customer success manager who has worked in large enterprises may understand procurement delays. An engineer with accessibility knowledge may improve product usability. A marketer with international experience may avoid messaging that works in San Francisco but lands awkwardly elsewhere. Diversity is not decorative; it improves the company’s ability to see the market clearly.
Common Mistakes Founders Make When Building Diverse Teams
Mistake 1: Starting Too Late
Many founders wait until the company is already 80 employees before worrying about diversity. By then, patterns are harder to change. Early employees become managers, managers shape culture, and culture shapes who succeeds. Start early, even when the team is tiny.
Mistake 2: Confusing Intent With Impact
A founder may genuinely believe they are fair. That does not mean the system is fair. Good people can run biased processes. The mature response is not defensiveness; it is curiosity.
Mistake 3: Treating Diversity as HR’s Job
HR can coordinate programs, but founders and executives must own outcomes. Hiring managers write job requirements, choose interviewers, make decisions, and set team norms. If leadership delegates inclusion completely, the company will notice.
Mistake 4: Focusing on Hiring but Ignoring Promotions
A company can hire diverse junior employees and still build a homogeneous leadership team if advancement is unclear. Promotion criteria should be documented, calibrated, and communicated. People should not need secret knowledge to grow.
Mistake 5: Building a Beautiful Dashboard and Doing Nothing
Metrics are useful only when paired with action. If the data shows a leaky pipeline, fix the leak. Do not admire it quarterly.
A Practical Framework for Startup Leaders
Here is a simple framework inspired by the themes of SaaStr Podcast #165 and modern inclusive hiring practices:
1. Diagnose
Understand your current team, hiring funnel, interview process, compensation structure, promotion paths, and attrition patterns. Look for bottlenecks and inconsistencies.
2. Design
Create clearer job descriptions, structured interviews, evaluation scorecards, sourcing plans, and inclusive onboarding processes. Design the system before urgent hiring begins.
3. Train
Train managers and interviewers on fair evaluation, feedback quality, inclusive meeting habits, and legal hiring standards. Do not assume smart people automatically know how to hire well.
4. Measure
Track funnel health, offer acceptance, employee engagement, promotion velocity, and retention. Use data to identify patterns, not to shame teams.
5. Improve
Review what is working, fix what is not, and repeat. Diversity and inclusion are not one-time projects. They are operating disciplines.
Why This Matters More as SaaS Companies Scale
At the earliest stage, a startup can survive on founder energy, a clever product, and heroic effort. As it scales, heroics become a liability. The company needs repeatable systems: sales process, customer success playbooks, engineering practices, product discovery, onboarding, management training, and leadership development. Diverse team building belongs in that same category.
The larger the company becomes, the more expensive bad habits become. A vague hiring process may seem harmless at 10 employees. At 200, it can shape entire departments. A noisy meeting culture may seem quirky at seed stage. At Series C, it can silence the exact people who understand customer risk. A referral-heavy hiring model may feel efficient early on. Later, it can narrow the company’s talent pool just when the business needs range.
Harry Glaser’s SaaStr conversation is powerful because it points founders toward operational maturity. Building diverse teams is not about perfection. It is about taking responsibility for the conditions that produce better hiring, better decisions, and better workplaces.
Experience-Based Reflections: What Building Truly Diverse Teams Looks Like in Real Life
In real startup life, building diverse teams rarely feels like a grand leadership speech. It feels like rewriting a job post for the fourth time because the first version accidentally asked for eight years of experience in a tool that has existed for five. It feels like telling a hiring manager, “No, we are not moving this candidate forward just because they remind you of yourself at 25.” It feels like slowing down a debrief so every interviewer provides evidence before the most senior person accidentally turns the meeting into a courtroom drama.
One practical experience many growing teams encounter is the “urgent hire” trap. A department is overwhelmed, everyone is tired, and the hiring manager wants someone fast. In that moment, the company is tempted to hire the familiar candidate: same background, same network, same style, same quick approval. Sometimes that person is great. But when every urgent hire follows the same pattern, the company quietly builds sameness into its foundation. The better practice is to prepare talent pipelines before desperation arrives. A calm hiring process is usually a fairer hiring process.
Another real-world lesson is that inclusion shows up in tiny moments. Who gets invited to brainstorm early? Who is asked to present to executives? Who gets interrupted? Who receives specific feedback versus vague encouragement? Who is described as “high potential,” and who is described as “reliable”? These small labels compound. Over time, they shape careers. A manager who wants a truly diverse team must pay attention to the informal economy of opportunity.
There is also an important lesson about onboarding. Companies often celebrate diverse hiring wins, then drop new employees into confusing systems. That is like inviting someone to dinner and hiding all the forks. Strong onboarding explains how decisions are made, what success looks like, where documentation lives, how feedback works, and which meetings matter. New hires should not need to decode the company through hallway anthropology.
One of the most powerful practices is making expectations visible. For example, a startup can create role scorecards that explain what good performance looks like at each level. This helps everyone, but it especially helps employees who do not already know the unwritten rules of the company or industry. Transparency reduces guesswork. Guesswork often benefits insiders.
Founders should also remember that diverse teams may feel less comfortable at first. That is not a bad sign. Homogeneous teams can move quickly because people assume agreement. Diverse teams may ask more questions, challenge definitions, and surface risks earlier. This can feel slower in the moment, but it often prevents expensive mistakes. The goal is not frictionless agreement; the goal is productive disagreement.
Finally, the best leaders treat diversity as part of company excellence. They do not separate it from product quality, customer empathy, sales effectiveness, or data-driven management. They ask: Are we hiring from the best possible pool? Are we evaluating people fairly? Are we creating conditions where different perspectives improve the work? Are we promoting people based on clear evidence? Are we building a company that can serve a broad market because it understands a broad market?
That is the practical spirit of SaaStr Podcast #165. Harry Glaser’s message is not “be diverse because it sounds nice.” It is “build the kind of company where talent is found, assessed, supported, and promoted with intention.” For SaaS founders, that is not just a moral idea. It is a competitive advantage with a calendar invite.
Conclusion: Diverse Teams Are Built One Decision at a Time
SaaStr Podcast #165 featuring Harry Glaser remains a valuable guide because it turns a big, sometimes vague topic into concrete leadership work. Building truly diverse teams requires better sourcing, clearer job descriptions, structured interviews, inclusive management, fair promotion systems, psychological safety, and consistent measurement. It also requires humility from founders who are willing to admit that their current process may not be producing the best possible team.
The most important takeaway is this: diversity is not a side project. It is part of how great SaaS companies hire, learn, sell, build, and scale. A team with broader perspectives can understand more customers, challenge more assumptions, and create stronger products. But representation alone is not enough. Diverse teams thrive when leaders build systems where people are heard, evaluated fairly, and given real opportunities to grow.
For founders, the work starts now. Not after the next funding round. Not after the next executive hire. Not after the company magically becomes less busy, which in startup terms means approximately never. Start with the next job description, the next interview loop, the next promotion discussion, and the next meeting where someone new has something valuable to say. That is how truly diverse teams are built: one deliberate decision at a time.
