Social-good software only works if the team lives its values first
Seventy-eight percent of employees say they have faced misconduct at work, and 75% of them never report it. Nandini Easwar, co-founder and CTO of Speakfully and former head of software engineering at Esurance, cites that statistic and sees two problems in it, not one. For anyone who wants their technical skills to serve a social cause, a harder question follows: how do founding values become product features, data architecture and hires?
Get a three-stage path from a real problem to shared values to a team that believes in the mission
Nandini Easwar, co-founder and CTO of Speakfully, explains how to build tech products for social good. She sets out three stages: find a real problem, build values the team already practices into the product, and hire people for the mission. She uses Speakfully's work on workplace mistreatment as the running example.
“I think it could be very simple, but it needs to be very purposeful.”
“So I think it's important to recognize that, you know, these core values, you have to practice them first.”
What you will learn
Recognize the range of products that count as socially conscious tech, from awareness tools to simple everyday apps.
Apply a three-stage approach: find a real problem, align your values with the tech, then build a like-minded core team.
Translate values such as transparency and user control into features, data design and UX choices.
Write job descriptions and interviews that hire for mission, passion and energy as well as raw skill.
Evaluate whether a mission-driven company's vision truly matches yours before you apply.
Key takeaways from the speaker
As women in tech, rid the fear of building something radical!
Learn ways to lead diverse tech teams, while focusing on the root cause of what you're building
Product Innovation & Founding Principles for tech startups
Growth & Scale for tech startups
Details
Level
All levels
Format
Talk
Technical depth
Non-technical
For
Founder, People manager, Mid-career
Length
19:27
Published
July 2022
Questions this talk answers
What counts as tech for social good?
Any solution that aims for a human-centric outcome with a bigger purpose behind it, including awareness tools and simple apps like Noom or Calm. It does not have to be deep tech, but it must be purposeful.
Where should a social-good product start?
With a real problem that needs solving, often one that affects you every day, followed by asking what responsibility technologists can take to make that problem go away.
How do founding values shape the design of a product?
Easwar says the team must practice its values first. At Speakfully, employee voice, two-way communication, transparency and user control drive the features, the data architecture and the UX, including users' right to be forgotten.
How should leaders hire for a mission-driven startup?
Put the mission and the reason behind it first in the job description, rank candidates' passion and energy alongside raw skill, and use situational interviews built around the problem the mission solves.
How can job seekers tell whether a mission-driven company is right for them?
Connect your experience to the mission, then question the founders about their vision with complex scenarios to see how they think.
About this talk
Tech products, if built right, can be a powerful tool that can help drive social causes. It can be used to drive impact and purpose. It can be very satisfying when you see how your product can affect lives for the better. However, in a highly competitive tech market, this is not considered "sexy". Without the necessary investments and the right engineers, the growth can be stunted. Selling such a product is not just about appealing to the economics, but also about tapping into the moral and social mindset of your buyer. How do we envision such products from ground up and navigate the product development, growth, scale and appeal? This talk is about finding the intersection of all that and carving a path for socially aware technology.
Give users control and the right to be forgotten (91 s)
Hire for mission, passion and energy (70 s)
I'm a co-founder and CTO also of a mission-driven startup called Speakfully. I'm here to actually talk to you all about what it takes to really build a tech product or a tech solution that really has an ultimate purpose of doing social good. There are different ways of talking about it. People have used different terms. I've even heard people talk about empathy-driven tech, socially conscious tech. These are all different ways of sort of describing anything that has an ultimate good purpose. I know that Sarah York was just on a few minutes ago and she was talking about tech for good and the mission and the vision and the principles behind that is very similar. Sarah and I connected a few days ago and we talked about how we're
sort of approaching it in very similar ways. I think it's phenomenal to actually see so many conversations centered around this. I've got about 20 minutes here in front of you all and I thought that I would structure the discussion around what I think and what I think will be useful for you all is to understand what we really mean when we talk about tech for social good. And then I actually want to dive a little bit into the various stages of actually going through and building a product or being part of a team or part of an organization that actually is building something that's got this ultimate, beautiful vision. But I thought I'd also do it with a real-world good example and what better example than my own
Speakfully. So I thought that would be a great way to like dive into this and a little deeper. And feel free to like drop your questions through the chat. I can see it all and happy to take them as they come. And for those of you who are just joining, my name is Nandini Eswar. I'm the CTO co-founder of Speakfully.
And we go right in if I can move this. All right, there we go. So as I was saying, what is socially conscious tech or empathy-driven tech? There are various, like I said, terminology. And in my opinion, I think any solution that's really trying to derive this very simple but a human-centric outcome, something that has a big purpose that sits behind it, I think definitely qualifies as that. It could also be tech products or tech solutions that enable, you know, some sort of awareness about what our society is all about. What are some of the social nuances that we are having to deal with in the current climate? What are some of the movements that are going on around us? How do you be an ally towards a movement? Or how do you stand against, you know,
something that you feel is wrong against your principles? I think all of those also do qualify as socially conscious tech. It could also be tech that essentially is solving very, very simple challenges that we face every day as people, as humans itself, and also solutions that can actually make us better than what we are, make us better people, enable us to make better choices, both personally, as well as professionally, as well as socially. Great examples are, you know, apps that like Noom, for example, I use Noom for a little bit. And it talks about how you make good choices with your food when what you eat every day. So I think there are various ways that you can still, you know, ultimately have a good outcome or a good goal. And then of course, last bullet point here, I talk about
solutions that are, you know, don't really have to be very high tech or deep tech or very, you know, heavy machine learning dependent. I think it could be very simple, but it needs to be very purposeful. Things that actually enable us to do things better do solve our day to day problems. Think about great examples are calm. It's essentially a way to help you meditate, essentially a way to help you bring in some mental wellness. So the various examples, and it's lovely to actually see so many different organizations that are actually taking some of these small problems and actually trying to find really good solutions for it. And that's really actually going to be the segue into what I think is, again, going to be the process of how you go about trying to build a tech product like this. First of all,
you are always want to start with some problem that needs to be solved. And I think there are a lot of us here, there are so many women here in this conference. And we have something that comes very, very naturally to us, which is the fact that we have a very high EQ, we have emotional quotient, and we also have a lot of empathy that's just, you know, weaved into into our DNA of who we are.
And I think there's a great way for us to naturally recognize some of the problems that actually occur in the real world, because we're just very empathetic as people. I think that allows us to recognize what exists and what problem needs to be solved. It may not be something that solves for something at a larger scale. I'm not talking about, you know, the large tech giants that essentially go after big, big problem solution, problem solving capabilities at scale, building tech at scale, it doesn't have to be that we certainly need that we absolutely need those. But it doesn't have to be that it could be something that's really impacting you on a day to day basis, then think a little bit about, you know, what is it that we can do as technologists, what's the responsibility and the
ownership that we can take as tech people, tech women, and see how you can actually like get it to a place where that problem doesn't exist anymore. Ask ourselves that question. I think that's a great way of trying to approach it and think about it a little differently than what we normally do, in the non-traditional sense. The second aspect of it, I think, is really finding the core principles and figuring out what are our foundational, you know, value systems that we believe in. And how do you weave that into your daily operationalization of your tech itself? Like, how are you putting it into your tech processes? And some of this is going to start to make sense when I talk about, you know, talk about the real world example, but just sort of hear me out and understand the place that I'm going,
which is first find the problem that needs to be solved. Once you've done that, you need to make sure you're aligning yourself, your people, and your principles along with the tech solutions that you're trying to build. That's very important, you know, when you're trying to build something that actually has a good positive human impact. And then, of course, last, but definitely not the least, is really trying to build out your core team. And you need to find alignment and create an environment where you actually bring people that are very like-minded, that they can actually like thrive in an environment of innovation and actually like building new things and for the ultimate purpose of it.
So finding that alignment and finding the right people around is actually very important for us to like try to build this out. Any questions so far at all? The chat seems quiet, so I'm just going to move forward. This is basically a perfect example. And this is Speakfully and this is what we're trying to do here at Speakfully. Clearly, this is an example of a problem that's really begging to be solved. I think there's, we know the statistics out there and here's one staggering stat right in front of you. It's, you know, we know that the problem of the workplace mistreatment is huge. It's something that people are now being more aware of. People are actually being able to talk about it. But if you look at it, there's 78% of
employees actually say that they did experience some form of misconduct in the workplace. Surprised? Not at all. 78%, you know. But what really is even more chattering is the fact that 75% of that group don't even come forward to actually report it. So right here in front of us, if you read the statistic, there's a real world problem. There are two problems actually, the way I look at it. I see the first problem is the fact that people are actually being mistreated and the 78% are being mistreated. And then you have the second problem where people aren't even able to come forward and report it. So there's two very obvious problems that exist right in front of us that I think is begging to be solved. And that,
I think that makes us all better when we actually solve this. It impacts people in a positive way. So checks various boxes and all of these is what helps us actually build and create something that's tech for good, tech for social good, you know, empathetic software. And this is, this is what we're trying to do it speakfully. And I thought that's a great example of telling you how we approach the problem, recognize the problem. And then now I'll get into a bit about, you know, the founding principles and how we went about building it. Like I was saying in my earlier slide, you know, the second stage of all of this, once you've really identified the problem that needs to be solved, you're really now coming in
and figuring out what are your core principles? What are your core value systems that you believe in? What's the value proposition that you're going to be putting out in the product, in the tech solution that you're creating out? The first thing that we came up with was, yes, through our product and through our business, we're going to give employees a voice. Absolutely, that needs to be, that needs to basically be practiced even from within. Unless we practice it, unless we actually put that in and translate that into how we're building it, we're not going to really see the outcome. Because we're now talking about us placing ourselves in the shoes of the customer. And keep in mind that the customer is also your internal employees. So we have to think about giving your employees a voice. So you want to design your
product, you want to build your product through your small team inside. And allow every person, every architect, every designer, every engineer on your team, every project manager to really have an equal voice there. And as they're putting ideas forward on how to actually create this, that's when you truly create a product whose essential outcome is meeting this primary goal. The second aspect of it here is, you know, keeping in mind that communication is actually a two-way street. And here's where, you know, communication can, when I, the minute you say communication, a lot of people start to think about, you know, verbal communication or written communication. But I'm also talking about how you communicate with your customers and your employees through your tech, through your product. We're now in,
we're now right in the thick of actually building this product to solve the workplace mistreatment problem. How do you make sure that communication happens through this two-way communication happens inside of the product? When you, when you start to approach your problem solution that way, then you're going to try and build out features. You're going to be building new features inside the product that actually enable that sort of communication, that sort of two-way street. And also not to, you know, not to forget the fact that we have to really try and, you know, follow some of those principles, even within the tech team as we're building this out. A lot of us here, you know, are part of like, you know, large tech teams, and we
understand the importance of that kind of two-way conversations. So it's, it's, it really has to be very purposeful is what I'm, I guess, trying to say. The third thing that I wanted to talk about here is about, you know, how we believe in transparency. That's again, another foundational principle for us. And, and it may be, it may be similar for a lot of, a lot of you and, you know, you can all understand the need for transparency. Now, the transparency now, when you think about it with respect to the solution you're coming up with for the mistreatment problem, then you're naturally going to create avenues where whoever's interacting with the solution you're building with your employees, your, you know, the, the HR leaders, the tech leaders, whoever it is, they want to make sure
that what they see is complete, is, is through complete transparency. And you're going to naturally design your data and your architecture around those philosophies. So you're going to, because you believe in it, because you practice in it, and you see the value of that transparency, you're naturally going to be building out your product with the same philosophy, with the same principle, and that's what's going to make your product reach the, you know, reach the people that it needs to reach.
And then the other thing I also wanted to say here is the fact that, you know, think about interactions and think about your UI and your UX. As you're building stuff out, you've got to make sure that the users who are interacting with your product are always actually in control of some of those interactions. We want to be, we want to give the choice of interaction to the end user. We don't want the user to do something just because we've navigated the user experience or the UX pages to the, to the point where we want them to be, but rather we want to leave the control in the hands of the person that's actually interacting with your product. And that's where, you know, again, you're impacting
people positively. You know, we want, you know, as, as you know, as you're designing out your, say, security and your data principles, data collection principles, you know, we don't want to get caught into this whole surveillance capitalism world, right? And we want to make sure that people at the end of the day, the end users do have the right to be forgotten if they want to be. The choice is theirs.
Let's be respectful of that choice and build the product and build the tracking and the security in your solution, keeping those constructs in mind so that when it comes to it, you're respectful of the user's choice. You know, and that of course is, is what leads to making all of the good choices. So I think it's important to recognize that, you know, these core values, you have to practice them first. And that's what's going to enable you to actually build your product through the same thing. And that's what we did at Speakfully.
I'm going to move on to the next part, which is really creating the team. And I wanted to tackle it with two different aspects here. There are two angles. We have a lot of women leaders here and other men as well in the room. And they talk, you know, and, and I think we, you know, that there's one approach as a leader. And the other approach is again, for people who are actually looking to like join mission driven companies. How do you approach it? How do you find the right place? So I'll start out with, you know, the part of being the leader. We've got this huge responsibility on our shoulders, where we've got to embrace the responsibility that is being given to us. Well, let's embrace it.
Let's make sure that we recognize the fact that we are here building something important, something that actually solves a very fundamental problem positively. And once we embrace that sort of responsibility, it's our job, our job to actually highlight some of the mission values and, you know, the mission itself and the why behind the mission in the job description, put it out there. That's the first thing you want to put in your job description. So when people are trying to apply to, you know, to jobs in your company or in your team, you want them to see that first. And then you want them to apply on the basis of that foundation, that mission, and the why behind the mission. Why did you arrive at that mission? Why do you want to solve the workplace mistreatment problem, as an example?
So those are the pieces that I think needs to be highlighted. So people actually like see it and are inspired and driven by it. The other thing I would say as leaders is that, you know, let's try to force rank a candidate's passion as well as their energy, as opposed to just raw skill. You know, it's great. Yes, the raw skill is absolutely important. The intellect is important for sure.
But at the same time, let's keep in mind that we want to actually hire people for the positive energy that they bring to the table as well. And create situational interview processes, like put them in a spot, put them in a situation of what your mission is going to solve and see how they'd approach it. As a job seeker, you know, the same thing. When you see the job description that talks about the mission, see how your experience allows you to draw the parallel, draw the dots between your skill and what the mission is trying to accomplish. Probe them, push the leaders, push the founders, ask them where they're headed with their mission. Ask them what's the vision, you know, and, you know, try to like pose
very complex scenarios at them and see how they're thinking about it. And that's what's going to help you decide if this is truly about the mission. Is this something that aligns with you? And if so, then you should really absolutely go forward and apply to those roles. Got a couple of minutes. I know they're going to cut us out super quick. But last but not least, just want to talk here about at the end of the day, the bottom line. When you're doing something that's for a social positive outcome, let's not be afraid here to challenge the status quo, right? So we can take charge of the narrative. We can change the narrative.
As needed. I think there are wonderful, you know, terrific women here and people in this room, technologists in the room in this conference who absolutely have, you know, the talent as well as the interest, as well as the drive to actually build something that's so important and much needed for our society. So let's, let's inspire each other. I think that's the message I'm trying to get across, you know, over the last 20 minutes or so to make sure that we go after and try and solve some of these small, real world problems. Doesn't, let's not, we don't have to, you know, doesn't have to be rocket science.
We don't have to really solve and reach the moon on day one, but let's take small steps. But let's continue to like, you know, question, you know, what our purpose is, question the product and the tech that we're building and question the trajectory of where it's going. That's what's going to enable us to do something that's truly makes a difference. So I'm going to pause there and see if there are any questions from anyone at all, anything on the chat, please feel free to post. And if not, you know, you can always reach out to me at any time. I'm usually on LinkedIn and yeah, happy to, happy to have been here and talk to you all. Great. Thanks Zara. And thanks, Alexis.
All right. Well, thank you all. Thanks for joining. And it was a pleasure talking to you all. I will be in touch. Bye.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Article based on this talk
How do you build a tech product that does social good?
Speakfully's co-founder and CTO says it starts with a real problem, values the team already practices and people who join for the mission.
In short
Nandini Easwar, co-founder and CTO of Speakfully, argues that tech for social good does not have to be deep tech or rocket science. In her view it needs three things: a real problem, values the team practices before it builds them into the product, and people who join because they believe in the mission. Her running example is Speakfully, a platform that addresses workplace mistreatment. She shows how employee voice, two-way communication, transparency and user control shape its features, data design and hiring.
Key takeaways
As women in tech, let go of the fear of building something radical.
Learn ways to lead diverse tech teams while focusing on the root cause of what you are building.
Product innovation and founding principles for tech startups.
Growth and scale for tech startups.
What counts as socially conscious tech
Easwar opens by noting how many labels the field uses: empathy-driven tech, socially conscious tech, tech for good. Her definition is broad. It covers any solution aimed at a human-centric outcome with a larger purpose behind it, including tools that raise awareness of social movements, help people act as allies or help them make better personal, professional and social choices. She mentions Noom, which she has used to make better food choices, and Calm, which supports meditation and mental wellness.
She says the bar is not technical sophistication, and that a social-good product does not need to be heavily dependent on machine learning:
"I think it could be very simple, but it needs to be very purposeful." (3:58)
Three stages: problem, principles, people
Easwar then sets out the process she recommends. First, start with a problem that needs solving. She suggests that the empathy and emotional intelligence many women in the audience bring make it natural to spot such problems. The problem does not have to be the kind of large-scale challenge that big tech companies tackle. It can be something that affects you every day, followed by asking what responsibility and ownership technologists can take to make it disappear.
Second, define your core principles and build them into how the tech is run day to day. Third, build a core team of like-minded people who can thrive while creating something new.
"Once you've done that, you need to make sure you're aligning yourself, your people, and your principles along with the tech solutions that you're trying to build." (6:45)
Speakfully: two problems in one statistic
To make the framework concrete, Easwar turns to her own company. As she cited, 78% of employees say they have experienced some form of misconduct in the workplace, and 75% of that group do not come forward to report it. She reads this as two separate problems: people are being mistreated, and people are unable to report it.
"So there's two very obvious problems that exist right in front of us that I think is begging to be solved." (8:13)
Solving both, she argues, ticks the boxes of tech for social good, because it affects people's lives for the better.
Turning values into product decisions
This is the core of the talk. Easwar describes the founding principles behind Speakfully and how each one shapes the product.
The first is giving employees a voice. She insists this has to start inside the company, because the product's customers include the team's own employees. Every architect, designer, engineer and project manager should have an equal voice in how the product is built.
"Unless we practice it, unless we actually put that in and translate that into how we're building it, we're not going to really see the outcome." (9:39)
The second is treating communication as a two-way street. That means communicating with customers and employees through the product itself, not only in speech or writing, and building features that make two-way conversation possible. The third is transparency, which she says naturally shapes how a team designs its data and architecture, so that HR leaders, tech leaders and employees see a complete picture.
The fourth is user control over UI and UX. Easwar does not want to steer users through pages to where the company wants them. She wants the person using the product to decide how they interact with it. The same thinking applies to security and data collection: she warns against getting caught up in surveillance capitalism.
"And we want to make sure that people at the end of the day, the end users do have the right to be forgotten if they want to be. The choice is theirs." (13:56)
Hiring for the mission, and choosing a mission to join
Easwar looks at team building from two sides. For leaders, the first step is to accept the responsibility of building something important and to state the mission, and the reason behind it, at the top of every job description.
"That's the first thing you want to put in your job description." (15:29)
She also asks leaders to rank a candidate's passion and energy alongside raw skill and intellect, and to use situational interviews that place candidates inside the problem the mission is trying to solve.
For job seekers, her advice mirrors this. Connect your experience to what the mission aims to achieve. Question the founders about where they are heading and how they see the vision, and give them complex scenarios to see how they think. That, she says, shows whether the company is truly about its mission and whether it fits you.
She closes by urging the audience not to be afraid to challenge the status quo, to take charge of the narrative and to keep questioning the purpose, the product and the direction of what they build.
"We don't have to really solve and reach the moon on day one, but let's take small steps." (18:27)
Watch the talk
"Building a tech product for social good" by Nandini Easwar (about 19 minutes): https://www.womentech.net/video/building-tech-product-social-good-nandini-easwar
About the speaker
Nandini Easwar is the Co-Founder and CTO of Speakfully, where she leads the technology behind a human-centric platform that addresses workplace mistreatment, including retaliation, harassment and micro-aggression. Before Speakfully, she headed the Esurance software engineering department and served as a technical advisor to companies around the world.
Questions this talk answers
What counts as tech for social good?
Where should a social-good product start?
How do founding values shape the design of a product?
How should leaders hire for a mission-driven startup?
How can job seekers tell whether a mission-driven company is right for them?
Drafted with AI from the talk transcript. Editor review pending.
Frameworks and ideas mentioned
Surveillance capitalism
Right to be forgotten
Cite this talk
Nandini Easwar. "Building a tech product for social good." WomenTech Network, 2022. https://www.womentech.net/video/building-tech-product-social-good-nandini-easwar