TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Software How-To

    Giant Robots Smashing Into Other Giant Robots

    A podcast about the design, development, and business of great software. Each week thoughtbot is joined by the people who build and nurture the products we love.

    Advertise
    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    479: Wistia with Brendan Schwartz Jun 15, 2023
    Show notes

    Brendan Schwartz is the Co-Founder and CTO of Wistia, software that makes it easy to find, engage, and grow your audience with video. Victoria talks to Brendan about the latest updates on the platform, interesting problems he found that Wistia was able to remove and help his team get to speed and velocity, and the personal value that drives his decision-making. Wista Follow Wistia on Twitter or LinkedIn. Follow Brendan Schwartz on LinkedIn, Twitter, or visit his website. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Brendan Schwartz, Co-Founder and CTO of Wistia, software that makes it easy to find, engage, and grow your audience with video. Brendan, thank you for joining us. BRENDAN: Thanks so much for having me. VICTORIA: And I believe this will be your third time, at least, on the Giant Robots Podcast, right? BRENDAN: Yes, I think this is my third appearance. Thank you for having me back. VICTORIA: Yes. BRENDAN: Is there anything I receive? What is it when you host SNL in a [crosstalk 00:39]. VICTORIA: You get a jacket. BRENDAN: A jacket, yeah. VICTORIA: Yeah, we should. BRENDAN: [laughs] VICTORIA: We should do a Giant Robots jacket or something from returned guests. I love it. So it's been great to follow along your journey here. So, for those who don't know, like, what is Wistia? And I'll say, just a precursor, that thoughtbot is a client of Wistia. So we use it ourselves. But why don't you just give us a little bit about what is the product and what makes it different? BRENDAN: Sure. And thank you so much for being a customer all these years. You kind of hit it at the top, but we help businesses of all sizes thrive with video. And so we serve mostly marketers. To dive a little bit into the history of the business, we'll be around seven...is that right? 17 years. It sounds like a long time when I say it out loud, [laughs] 17 years this June. And, for most of our history, we were, I'd say, a video-hosting platform for marketers. So if you want to put video on your website, track who's watching it, how they're watching it, and integrate that data with your other marketing systems, that was our focus and what we did. And over, I'd say, the past two years, we've brought in that focus to help businesses with all aspects of their video marketing from creating video...We recently introduced a live video product for webinars and for live events last fall. We just launched last week, which I'm very excited about native video recording in the Wistia platform. So you can record your webcam and your screen. And there's also a very simple video editor in the platform, which has been really powerful for folks to make small adjustments to content or to atomize content, take out highlights or sections of things, and to be able to publish them to their audiences. VICTORIA: Thank you for providing that context. And I'm curious if there were any, like, environmental or market forces that pushed you in that direction with the latest updates on the platform. BRENDAN: So, like I mentioned, we...in a large part, our success came (We're a relatively small team.) it came from being focused. And so for, you know, that decade or more, there were a lot of things that we had heard from the market or from customers. Like, live video was an obvious one we had been asked for a really long time. When will Wistia do live? When will Wistia do live? And, you know, our approach to that is we want to be really good and excellent at the things that we do and be focused. And I think that has served us well over the time that we've existed. And some of that came out of; I'd say, the really early days of the company where...it's funny, [laughs] we've always built Wistia, you know, sometimes we say in the shadow of YouTube, so YouTube and seeing YouTube. My co-founder was the first person who showed me YouTube in 2005, I think it was, and that was part of the inspiration to start Wistia. We are both really into video. And we saw that and having video be more accessible on the web, we knew was something that was going to change the world. There was a question...this sounds kind of dated nowadays to say, but there was a question if you were starting a business, you know, let’s say, in 2006 or 2007 or '8, right? What are you going to do when Google enters your space? [laughs] It was a funny one for us to answer because we said...well, I forgot when YouTube was bought by Google. It was maybe in 2006 or something like that. Like, Google is already in our space, and it's free. So that was always an interesting challenge. And the way that we were successful there [laughs]...obviously, YouTube is at a much larger scale [laughs] and level of success than Wistia is. But to the extent we have a business at all against a very well-known and free competitor from those early days, it was being really focused on our customers and keeping the product footprint fairly small. Our business changed a lot during the pandemic. There were some obvious things, right? Video was used a lot more. So existing customers had a lot more usage. We saw an influx of customers, people who maybe were late to adopt video in their organization, and then that became a much obvious way that people could reach their audiences and grow. So that was something of a tailwind for us. And then it also forced us to kind of take a step back and look at the market in general with clear eyes. It was a funny moment, I think, for me and my co-founder because in the years leading up to that, you know, it had been like 12,13 years of doing Wistia, and it felt like we had solved a lot of problems in the product. We were still building new things, but they were for the most mature part of our audience or the most advanced marketers, which was pretty fun. But it felt like a lot of the problems had been solved. We were always, like, is the product done? Is the product complete? And when we took a step back and looked at the market, what we had found was that we had kind of just, like, got ourselves into this, you know, more mature corner of the market. But in a large part, because of COVID, so many businesses, existing and new businesses, were very new to video and were using video in new ways. And people who had been using video, their solutions to do that were super fragmented. You'd have one product that is providing...[laughs] You might have a different product you're using for internal meetings, video meetings, and that's different than a live event product, that's different than a webinar product, that's different than where you might publish your videos or host your videos, which is different than how you'd, like, analyze your performance. And as video became more important to organizations, that fragmentation of the solutions was something that was super painful. And we had heard from a lot of people who were Wistia customers and people who were not...having this as an all-in-one platform was something that they really desired, which I was also kind of, you know, we were, like, cynical about a little bit, right? Because if [laughs] you're in the world of product, it's like you can ask, you know, if you had a magic wand, what would you want? And someone says, "Oh, I want it all in one. And if you could just do everything for me, that would be so great." You know, it's hard to say, is that what people really want? And what gave us more confidence at that was, correct, is when we started digging into some of the details and hearing about existing workflows that existed that marketers have to deal with, including ourselves. We do a lot of content marketing. A lot of the really interesting things you could do in a product that is all in one it opens up new opportunities. And you could just imagine...you've hosted a webinar before. Almost always, it's the best practice that you host a webinar; after you're finished, you probably have a good marketing asset there. You should publish it to your website. You usually need to do some light editing. Maybe you're going to take off the Q&A before you publish it. And you put it on your website. And then, a while later, you're like, was this effective? Did it work? And then you have to, you know, probably have a spreadsheet somewhere. You have to go into the tool used to host the webinar to figure out who was watching it and [laughs] who registered. Did they attend? And then where's the data for how it performed on your website? How many people watched it? Did you get subscribers if you were, you know, had an email gate on that content? It's cumbersome, and it's a mess. And then, you know, the most motivated people who are well-resourced have the time to do that and analyze the performance. But then a lot of marketers who are on smaller teams they just don't have time to do that, which means a lot of content gets under-utilized or under-marketed. So a lot of evidence and motivation to change what we were doing and expand the product footprint. So that had us make a big investment in our product design and engineering teams, and we almost...we doubled them in about 18 months. And then that kind of set us on this journey that we started maybe two years ago to greatly expand what we're doing. VICTORIA: Well, that's great. So just to play that back, staying close and focused on your customers almost had you to a point of being stable with your product until COVID happened. And you have this increased demand for video that opened it up to almost have Wistia be like a startup again and create a whole new feature branch, right? BRENDAN: Yeah, that's exactly right. And that was really fun and motivating. I mean, we...that early-stage energy and not having all the answers to things where stuff is a little bit, you know, less-researched, and it's faster paced is something that I really like. That was a big shift for the company. So there was some, I don't know, I think we had some self-doubt a little bit if I'm honest, of, you know, when you've been so focused for so long. Like, can we do this? Like, will we be able to create something really good with this expanded footprint, and what resources that take? And is it going to take shifting the culture and mindset of the team, like, in ourselves? But, I don't know, that's kind of why I started the [laughs] business in the first, like, the adventure and not knowing what's next is very appealing. So that's been the fun part of it. VICTORIA: And how did you go about shifting that mindset? Or even what was the moment where you realized that you needed to go after this shift? And how did you start lobbying everyone around you to get on board? BRENDAN: A lot of those customer interviews and market interviews, we worked with an outside firm. We worked with Boston Consulting Group, who was a really great partner. We have obviously worked with folks outside. We hadn't worked with somebody; I'd say, at that scale in terms of kind of, like, tie-in with our company strategy today. But that was really helpful to have a partner, especially to push us. We got to something different than we had been doing, I mean, not dramatically so. But it was expanding what we were doing. So that was really helpful. It helped...that put some structure around it to what we had, and the whole company knew this was happening and was along for the ride. So I'd say the communication and getting to a clear strategy was something we did pretty well, and telling that story internally. I'd say where we didn't do as well [laughs] and were maybe late to make some decisions is how the culture would need to change to support that strategy. Again, like I said, we've doubled the product design and engineering teams. That is now feeling in a pretty good spot, but that was a lot of growth for us. And was, I'd say, pretty messy along the way. So the beginning, I'd say, was clear, and I think communicated well. And then I feel like in the middle it was, I don't know, a big mess where we got maybe a year in, and we're like, wow, we have this new strategy, but we really haven't executed much on it. Some of these things we're building are taking a lot longer than we thought. Our velocity doesn't feel great. Like, maybe we didn't plan some of this stuff out. Like, we've hired a lot of people, but, like, are they productive yet? And so, yeah, I think we were in a pretty [laughs] tough spot maybe last summer. We were a year into this strategic shift, but it didn't feel like we were really moving against it as much as we had hoped. VICTORIA: It makes sense that it would take some time to change strategic direction and then get to that high-velocity point that you would expect. Were there other blockers that you found you were able to remove to get the team back up to that high velocity on delivering features for clients? BRENDAN: [laughs] Well, it's funny that you say that. I wish; I mean, that is pretty obvious, I think, and obvious in retrospect. But, for some reason, when you're in this, or when we were in this, you're impatient, and you want it faster. And I think probably [laughs] having some clear expectations would have made the ride a little smoother along the way for this. I feel like I have to remind myself of this pretty frequently. I mean, Wistia is not big. We're 180 people or so but certainly bigger than...I can think back to various other sizes. Doing that strategic shift it takes time for leadership, let's say, or me to shift my mindset about some of those things. And then once you've changed your mind, you kind of... it's easy, or at least for me, to discount the time it took and all the information it took to lead to that, which needs to cascade through an organization. And so that's where some of that impatience...or just the piece you said about, yeah, it makes sense that this would take time. I was like -- VICTORIA: [laughs] [inaudible 11:56] BRENDAN: [laughter] You're like, once you've got it, you're like, wow, this is so exciting. Let's go. Let's go. And everybody is like, what are you talking about? VICTORIA: Yeah. My background has been in, like, Federal IT consulting. So you're used to kind of the pace of things being a little slower. And I think people forget that as an organization gets to any amount of size, that kind of bureaucracy tends to creep in. And, like you're saying, the information just needs to cascade down throughout everybody. I think my original question was, were there any blockers or interesting problems you found that you were able to remove and help your team get to that speed or velocity you really wanted? BRENDAN: Yeah, there were a lot. I think most of them and most of the hardest ones to move centered around cultural change, and they weren't necessarily so clear at the onset. And so, you know, one thing that kind of partway into the strategy change that became clear is, and you had said it, it's like going from, you know, basically thinking of ourselves as being in a late stage or more mature market to being in an early-stage environment. And the type of culture that, you know, succeeds in those worlds is different. One thing that we've learned along the way at Wistia that we have employed and I think been successful with is this concept that when you update your strategy as a company, you should be thoughtful and, like, make conscious updates t…

    Full show notes at the publisher

    478: Senga with Agnes Malatinszky Jun 08, 2023
    Show notes

    Agnes Malatinszky is the Founder of Senga, which takes care of back-office administrative needs for freelancers, contractors, and solopreneurs. Victoria and Will interview Agnes about the thoughtbot Incubator program and what led Agnes to choose to apply, what the demands on her time were like, how it worked, and how she feels now that she's at the end of the program. Senga Follow Agnes Malatinszky on LinkedIn or Twitter. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: WILL: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Will Larry. VICTORIA: I'm your other host, Victoria Guido. And with me today is Agnes Malatinszky, Founder of Senga, providing back-end support for freelancers. Agnes, thank you for joining me. AGNES: Hey, it's a pleasure to be here. VICTORIA: You are the first graduate of thoughtbot's incubator program, and I'm really excited to dive into that with you today. So, before we get started in talking about the incubator program, let's just start with what fun thing do you have going on this week? AGNES: I'm based in Washington, D.C., and it's a beautiful time of year here. Early summer, late spring is gorgeous. So I'm excited because my family and I are actually headed out to Harpers Ferry this weekend for a little hike. So I'm looking forward to that. WILL: So, what is...when you say a hike, can you explain it to anybody that's outside of the D.C. area? AGNES: It's just a beautiful area in West Virginia. And we're going to take our dog and my daughter out there and get some fresh air and walk around. There's a little historic town there as well that's really interesting to explore. WILL: That sounds fun. VICTORIA: Yeah. I've been to Harpers Ferry to go floating, like, on the river. AGNES: Yes. VICTORIA: Where you float down the river in inner tubes and drink beverages. [laughter] There's also...there's rock climbing in Harpers Ferry too, which is sometimes closed for bird nesting. So it is really beautiful. AGNES: Ooh, I didn't know that. That's really cool. We'll keep an eye out for that. WILL: Yes. For anybody that doesn't know, Victoria is an amazing rock climber. I have a lot of respect for her because I don't know if I could do it. [laughter] VICTORIA: You could definitely do it. The next thoughtbot trip that we're on, we'll go rock climbing, Will. I'm confident in your skills. You could do it. Yes, I'm a big rock climber and rock-climbing advocate, so I'll talk about it forever if you let me. WILL: [laughs] VICTORIA: And I'm actually going to go rock climbing this weekend and get outside myself. And we're going up to Mammoth, California. And we're going to do a half-climbing, half-ski trip. WILL: Ooh. VICTORIA: So that's going to be fun for Memorial Day weekend, so...What about you, Will? What do you have going on fun this week? WILL: Yeah. So you said skiing. VICTORIA: Yes. So Mammoth got the most snow in the country this year. When we were there in February, they'd already had, like, 10 feet of snow. And then they got another foot of snow while we were there, so they're going to have snow through August, at least. WILL: August. Wow. Here in South Florida, the lowest we got was 50. So snow, I don't even know what you're talking about. [laughs] Yeah, so you asked what I'm going to do. Last week was a big week for us because my boys they turned four years old and one year old. And we took them to Disney and had a blast. Anybody who's been to Disney knows it's a trip. It could be a lot, especially it was very hot there too. So I think this weekend we're just going to take it easy. We're just going to relax and just enjoy it. VICTORIA: Trip of a lifetime for them, I'm sure. WILL: Yes, they loved it. VICTORIA: We have Disneyland over here in California. I have been to Disney World in Florida. But I still haven't been to Disneyland since I've been here, [laughs] which I think some people would judge me for. AGNES: You know what? I haven't been to either. I hold it against my parents forever. [laughter] Although my family is not a big fan of crowds, so I think that's why. WILL: Yes, if you're not a fan of crowds, Disney is not the place, especially now. I've heard around September is probably the best time to go. So we're going to try that out during that time too. AGNES: Ooh, protip. You heard it here first. WILL: Yes. [laughs] VICTORIA: September, Disneyland, Florida sounds very warm to me. [laughs] But yeah, we're actually going to go to Mexico with thoughtbot as a team meetup in September, which is also going to be pretty warm, I think. [laughs] But it'll be fun. Well, that's lovely. I love getting to hear a little bit about your lives before we dig into your business. Agnes, I'm super excited to hear about Senga. But maybe start with just a little bit about your background before you started. AGNES: I had been thinking about starting my own business for a while. I am an immigrant, and I come from an entrepreneurial family. Actually, my mom ran her own translation business back in Hungary, and now she's a really successful artist. So, you know, I had support from them and my husband as well to sort of try out something new. But, in my last role, I was actually Chief Operating Officer at an EdTech company that had scaled to serve over 80% of U.S. schools during the pandemic. And I was at that company for about five years and had seen the full arc of, you know, startup to a mature organization. So I was ready to take on a new challenge and to learn something new. WILL: You mentioned that your mom was an entrepreneur. And my dad was an entrepreneur, also. He had his own electric and HVAC business, and I learned so much from him. Is there anything that you can just, like, ooh, I learned this and this from my mom as a kid, looking at your mom being an entrepreneur? AGNES: I mean, she is just a, you know, fix-it person in every sense of the word. So she will fix an electric outlet. She will fix something with her business. WILL: [laughs] AGNES: She's just, like, really good at getting her hands dirty and being really scrappy. And I think that's a really important skill to have, you know, especially in a startup, and especially when you're starting out and still on your own. VICTORIA: So, what did your parents say when you told them you were going to start out on your own and build your own company? AGNES: They were really encouraging. They, you know, they keep up with all my LinkedIn posts, and they read everything I publish. So they're just very supportive and the best cheerleaders I could possibly hope for. [laughs] WILL: Did stepping out and starting your business did anything scare you in that area? AGNES: Oh my gosh, every day, something new. It's all just uncertainty and risk at this point. You know, I'm very, very early in my startup journey, so literally every question about the business I have to test. I have to find answers for. And that ranges everything from, you know, business formation to, you know, the nuts and bolts of getting the business organized and setting up financials, and the legal structure for the company, to figuring out what the product is going to be. So all this uncertainty is definitely a little bit nerve-racking. VICTORIA: And I'm wondering, what about your past experience as a Chief Operations Officer led you to want to build a product like Senga? AGNES: So being a Chief Operating Officer, I think one of the things that I really learned was that in order for a business to be really successful, and for people working at that company to be really successful, they have to have the organization's support to do what they do best. You know, what I used to tell my operations team was that you know, we were really the plumbers of the organization, making sure that everything ran smoothly behind the scenes. So, actually, that was one of the inspirations for Senga, for my current company, this idea that freelancers and independent workers don't have that support. They don't necessarily have somebody helping them with HR, and with financials, and with legal stuff, and with everything else that goes into running a business, whether you're a business of 1 or a business of 100. And that's really where I wanted to come in and, you know, support independent workers. VICTORIA: One follow-up question for Agnes on your experience in the COO role. I believe your team also had a lot of background in the freelancing world. So you had people you could ask questions to and start to understand that market. Is that right? AGNES: Yeah. Like a lot of businesses, I guess we had, you know, freelancers and contract workers that we relied on. And that's increasingly true for most companies now, I would say. There's specialized roles. There is seasonal roles that you don't necessarily hire full-time employees for but that are perfect for somebody, you know, on a temporary basis or somebody with more specialized skills. So you're exactly right; being able to tap into that network and having had experience working with freelancers and contractors was really helpful coming into the incubator and having people to tap for interviews and for input. VICTORIA: Great. And then, what is the thoughtbot incubator, which we've mentioned a few times already? It is for a non-technical founding team with a business idea that involves a web or a mobile app. It's an eight-week program that helps you get the proof points you need in order to move forward with confidence. So I'm curious, Agnes, what led you to choose the thoughtbot incubator Program as something you wanted to apply to? AGNES: I mean, it's exactly what you named. So this incubator program was really a perfect launching pad for me. It's designed for non-technical founders, like myself, to get their own dedicated team of product and dev experts to, you know, like, hone customer discovery practice, create a product strategy, run proof of concept experiments. And, you know, these were exactly the areas where I lacked skills and expertise the most. So I had actually looked at other incubators and even some venture studios before, but those models were not as good of a fit for me. I was really excited to find and to be able to join thoughtbot's incubator program. MID-ROLL AD: Now that you have funding, it’s time to design, build and ship the most impactful MVP that wows customers now and can scale in the future. thoughtbot Lift Off brings you the most reliable cross-functional team of product experts to mitigate risk and set you up for long-term success. As your trusted, experienced technical partner, we’ll help launch your new product and guide you into a future-forward business that takes advantage of today’s new technologies and agile best practices. Make the right decisions for tomorrow, today. Get in touch at: thoughtbot.com/liftoff. WILL: What was the original idea behind Senga? AGNES: The idea that I came into the incubator with and then the pain points that we honed in on during the incubator, and then the long-term vision for the company are all kind of a little bit different. So I'll zoom out first to the sort of 30,000-foot view of this. So, coming into the incubator, I had been reading and researching a lot about some macro trends that I think are really interesting, and these are trends that many of us are keeping an eye on. So they're nothing revolutionary, but I think they're going to create some really interesting problems to solve in the next couple of years. So the first one is the rise of independent workers, or contractors, or freelancers. I'm kind of going to use these terms interchangeably. In recent years, the number of independent workers has shot up like crazy. There are already over 65 million independent workers in the U.S., and this number is growing by about 25% annually. And then, add to this that economic downturns tend to grow this number even more. You know, this makes up about a third of the workforce in the U.S. already, and it's growing. The second thing is that you know, the fact that early-career folks, especially Gen Z, really like the independence and autonomy that comes with this type of work. Over half of Gen Z already freelance, and the majority want to make independent work their career. In other words, they explicitly do not want to work for a company in the traditional sense. And then, third, there's kind of a mishmash of factors that I'll lump into one bullet that additionally drive up this type of work, which is that, increasingly, jobs are going to be skills-based, not degree-based, and all work, even white-collar work, will become more modular. Both tech advances and even, I think, novel organizational structures are going to make it possible for people to hyper-specialize and to plug into different organizations at different times, and, you know, even simultaneously to perform that specialized work. So take all this together, and what I'm really seeing is that the current market offerings serving freelancers and contractors are not nearly enough to meet all their needs, which is driving huge inefficiency. The types of companies that cater to this segment now or, you know, there's mature marketplaces like Upwork, and Fiverr, and some earlier-stage companies that do, you know, more workflow and back office. But I'm not seeing a comprehensive solution, and that's driving like I said, a lot of inefficiency. So, ultimately, being a freelancer is still really hard. Only about 50% of a freelancer's time is spent on billable work. And so this is what I really want to solve. VICTORIA: And did anything change through the incubator process? AGNES: So the biggest thing I found during the incubator was actually a really good entry point into this market. So startup wisdom says that you have to narrow down your product to a super tight segment that has a very strong, like, yes to your product. So, during the course of the eight weeks that I did the incubator, we did a ton of interviews, and I was really on the lookout for big spikes and pain points that repeated for a specific niche of freelancers. And that's exactly what we ended up finding. There's lots of nuance to this, but generally speaking, people new to freelancing and those that are just looking to get started need help getting started in a more manageable way and then setting up good practices that will serve them in the long run. WILL: You mentioned those practices that helps them set them up in the long run. Are you talking about mostly the operation, so, like, anything that's non-billable for a client? AGNES: Exactly, yeah. So that's kind of how I think about the work is anything that's billable and then anything that's non-billable. So that includes client management, client communication, marketing themselves, finding, you know, new work, so drumming up new business, all the back-office financials, back-office legal and admin stuff. All these other things that traditionally would be, you know, done by, you know, an operations team at a big company, but, for freelancers, they have to do it themselves. WILL: Yeah, I love that idea because my spouse she dipped her toe into the freelance world. And I felt like the operations kind of overcame everything else. And so it almost felt like the operations was taking over the job. But it's one of those things I feel like we didn't really think through of how much work that that…

    Full show notes at the publisher

    477: 20th Anniversary Episode Jun 01, 2023
    Show notes

    Chad joins cohosts Victoria and Will to talk about thoughtbot's 20th birthday! 🤖🎉 In this episode, you'll find the 411 on the thoughtbot mascot, "Ralph," taking the company fully remote, and our company values and how we believe products should be designed and built! Follow Chad Pytel on LinkedIn, Twitter, or visit his website. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: Hey there. It's your host Victoria. And I'm here today with Dawn Delatte and Jordyn Bonds from our Ignite team. We are thrilled to announce the summer 2023 session of our new incubator program. If you have a business idea that involves a web or mobile app, we encourage you to apply for our 8-week program. We'll help you validate the market opportunity, experiment with messaging and product ideas, and move forward with confidence towards an MVP. Learn more and apply at tbot.io/incubator. Dawn and Jordyn, thank you for joining and sharing the news with me today. JORDYN: Thanks for having us. DAWN: Yeah, glad to be here. VICTORIA: So, tell me a little bit more about the incubator program. This will be your second session, right? JORDYN: Indeed. We are just now wrapping up the first session. We had a really great 8 weeks, and we're excited to do it again. VICTORIA: Wonderful. And I think we're going to have the person from your program on a Giant Robots episode soon. JORDYN: Wonderful. VICTORIA: Maybe you can give us a little preview. What were some of your main takeaways from this first round? JORDYN: You know, as ever with early-stage work, it's about identifying your best early adopter market and user persona, and then learning as much as you possibly can about them to inform a roadmap to a product. VICTORIA: What made you decide to start this incubator program this year with thoughtbot? DAWN: We had been doing work with early-stage products and founders, as well as some innovation leads or research and development leads in existing organizations. We had been applying a lot of these processes, like the customer discovery process, Product Design Sprint process to validate new product ideas. And we've been doing that for a really long time. And we've also been noodling on this idea of exploring how we might offer value even sooner to clients that are maybe pre-software product idea. Like many of the initiatives at thoughtbot, it was a little bit experimental for us. We decided to sort of dig into better understanding that market, and seeing how the expertise that we had could be applied in the earlier stage. It's also been a great opportunity for our team to learn and grow. We had Jordyn join our team as Director of Product Strategy. Their experience with having worked at startups and being an early-stage startup founder has been so wonderful for our team to engage with and learn from. And we've been able to offer that value to clients as well. VICTORIA: I love that. So it's for people who have identified a problem, and they think they can come up with a software solution. But they're not quite at the point of being ready to actually build something yet. Is that right? DAWN: Yeah. We've always championed the idea of doing your due diligence around validating the right thing to build. And so that's been a part of the process at thoughtbot for a really long time. But it's always been sort of in the context of building your MVP. So this is going slightly earlier with that idea and saying, what's the next right step for this business? It's really about understanding if there is a market and product opportunity, and then moving into exploring what that opportunity looks like. And then validating that and doing that through user research, and talking to customers, and applying early product and business strategy thinking to the process. VICTORIA: Great. So that probably sets you up for really building the right thing, keeping your overall investment costs lower because you're not wasting time building the wrong thing. And setting you up for that due diligence when you go to investors to say, here's how well I vetted out my idea. Here's the rigor that I applied to building the MVP. JORDYN: Exactly. It's not just about convincing external stakeholders, so that's a key part. You know, maybe it's investors, maybe it's new team members you're looking to hire after the program. It could be anyone. But it's also about convincing yourself. Really, walking down the path of pursuing a startup is not a small undertaking. And we just want to make sure folks are starting with their best foot forward. You know, like Dawn said, let's build the right thing. Let's figure out what that thing is, and then we can think about how to build it right. That's a little quote from a book I really enjoy, by the way. I cannot take credit for that. [laughs] There's this really great book about early-stage validation called The Right It by Alberto Savoia. He was an engineer at Google, started a couple of startups himself, failed in some ways, failed to validate a market opportunity before marching off into building something. And the pain of that caused him to write this book about how to quickly and cheaply validate some market opportunity, market assumptions you might have when you're first starting out. The way he frames that is let's figure out if it's the right it before we build it right. And I just love that book, and I love that framing. You know, if you don't have a market for what you're building, or if they don't understand that they have the pain point you're solving for, it doesn't matter what you build. You got to do that first. And that's really what the focus of this incubator program is. It's that phase of work. Is there a there there? Is there something worth the hard, arduous path of building some software? Is there something there worth walking that path for before you start walking it? VICTORIA: Right. I love that. Well, thank you both so much for coming on and sharing a little bit more about the program. I'm super excited to see what comes out of the first round, and then who gets selected for the second round. So I'm happy to help promote. Any other final takeaways for our listeners today? DAWN: If this sounds intriguing to you, maybe you're at the stage where you're thinking about this process, I definitely encourage people to follow along. We're trying to share as much as we can about this process and this journey for us and our founders. So you can follow along on our blog, on LinkedIn. We're doing a LinkedIn live weekly with the founder in the program. We'll continue to do that with the next founders. And we're really trying to build a community and extend the community, you know, that thoughtbot has built with early-stage founders, so please join us. We'd love to have you. VICTORIA: Wonderful. That's amazing. Thank you both so much. INTRO MUSIC: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. WILL: And I'm your host, Will Larry. And with us today is our other host, Chad Pytel, the CEO of thoughtbot. Which, we're celebrating 20 years of business this year. Chad, welcome. CHAD: Oh, it's good to have the tables turned on me. And I'm looking forward to the discussion today. VICTORIA: Great. We have a whole set of questions, some of which come from other employees within thoughtbot. So we're really excited to dig into it today. Why don't we start with thoughtbot's iconic logo, the Ralph bot, and the little red robot that everyone knows thoughtbot for? And we call him Ralph within thoughtbot. So, how did Ralph come to be? Where does his design come from? And how did that become part of the company mascot? CHAD: I'm happy to tell the story. But I have a question for both of you: have you ever heard me call the robot Ralph? WILL: [laughs] No. VICTORIA: I don't think I've ever heard you refer to the robot. WILL: [laughs] VICTORIA: So, if you did call it, I don't know what you would call it. WILL: Oh, who started that? [laughs] CHAD: It was someone who was at the company, Matt Jankowski. WILL: [laughs] VICTORIA: Ah, I see. CHAD: I actually don't like the name. I think it's a terrible name for the robot. [laughs] I don't understand why the robot has to be gendered at all. And so I've never said that that's the robot's name. You know, when you're CEO, you have to pick your battles. WILL: [laughs] Yes. CHAD: Yeah. So that's the unofficial name of the robot, I think. And Matt started calling it that because Matt's a big fan of coming up with names for things. And yeah, so, at some point, he started calling it that. And it sort of stuck as people joined the company and just sort of assumed that that's what the robot's called. We didn't start with this logo. Logo has always been a robot. But the thing we started with was an illustration based off of a tin robot that I think either one of us had or that we saw a picture of. Another Matt, who is one of the founders of the company, sketched it. He was a designer as well as a developer. And we used it for a few years. But what we learned over the course of it as we gained more exposure is that, actually, it's a really common tin toy robot. And you can find a lot of other art and illustration and uses of it in stock photography and everything. Which at first was good because then we could get a bunch of stock photography, and it was our logo. But then we realized, ooh, this is not something that we really own or have control over. So we started to think about creating our own robot logo from scratch. Since we're a design firm, and I think it's notoriously hard to design things for yourself, we actually went to another agency that we were friends with and hired them to work with us to create the logo. And I have to say I was probably the worst client ever. WILL: [laughs] CHAD: Because I was asking...I had a particular vision in mind for this idea of, like, a powerful robot. And we kept on doing sketches, after sketch, after sketch, and it was really hard. We couldn't arrive at something that seemed powerful, that didn't seem aggressive. The logo at the time was a 3D representation of the robot. And it was really hard to also make a new 3D robot that looked powerful but not aggressive. And we just banged our heads against that for a long time. I think it was a couple of months. Until one day, I just said, you know what? We're not going to do it. Let's just stop trying to do this. [chuckles] Let's just do the simplest 2D representation of a robot that we can think of. And just going back to the drawing board starting over, we arrived at the logo we have today. Now we have to deal with the fact that it looks a lot like the Android logo. [laughter] But that's the, I guess, the story of the robot. WILL: So, first off, scratching the name Ralph. [laughs] CHAD: No, no, you can use it. I just think it's funny. WILL: Definitely. Second thing is Chad is not a good client when working with designers. No, I'm just joking. [laughs] CHAD: No, it's totally true. WILL: [laughs] CHAD: You know, when we have strong opinions that are mostly preferences, that leads to people being bad clients. [laughter] Because there was no reasoning behind, you know, the preferences. It was just what I had in my head. And so it wasn't until I let that go that we were able to arrive at something usable. WILL: [laughs] That's awesome. So, was the robot a passion for you, or was it just a toy that one of the founders, employees had, and that's where you went with it, how you got your inspiration? CHAD: The name thoughtbot with the bot on the end comes from...because before we started thoughtbot, we did a lot of Java development as a group, same people I went to school with them. We did projects together. And we would follow the pattern where you sort of have an object and then a manager object or a service object. And it was a common naming pattern. If you have orders or customers, then the service object might be called order manager or customer manager. And, in our code, we tended to not do that and instead do bots. So we would have order bot over orders, customer bot over customers. So, when we were brainstorming names for the company, we naturally tended to put bot on the end because that was our typical naming convention in the projects we were doing together. And so there wasn't anything particular about robots that we cared about at all. [laughter] It was that naming convention, which then extended to, okay, well, it's the thoughtbot. And so it should be a robot with thoughts on it or thought lines or something like that. That's where it came from. VICTORIA: I love to hear that. I'm learning so much myself I didn't know before even as a thoughtbot employee. WILL: [laughs] VICTORIA: It's been 20 years since you started the business. I want to start...or go back in time. So, if you could go back and give yourself, the younger version of you 20 years ago, some advice, what would you say? CHAD: I've gotten similar versions of this question on different shows. My answer for the last several years has been pretty consistent. So I'll give that one, and then I think I have another one too. The thing that I didn't realize at the time that I think I would be better for and the company would be better for I had a big blind spot in terms of I started thoughtbot with friends. We were the same age. We were all five White guys in our 20s, just out of school. That was the people that I was doing projects with; that was the people I was surrounded by in school. And it was a big blind spot. And, if I could go back in time, I would try to open my eyes to the fact that that was the case. And I think that I would be a lot better for it. And I think the company would be a lot better for having started with a more diverse team from the beginning because it makes us worse when you don't start off that way. It's harder and harder to correct it the longer it goes on. And so that would be something that I would go back and try to tell myself. Look at what you're doing. You don't realize now, but it is important. WILL: So, because we started talking about this at Summit a month ago, and it was amazing to hear that you're saying that because, at the same time, we're at this all-staff event, and we're able to see how diverse our team is and stuff like that. How has the journey been increasing the diversity of the team? Like, I look at our team photo, and it's just amazing to see the diversity in every level, especially in leadership, the diversity in leadership. And I know we haven't, quote, unquote, "arrived." So, how has that journey been? And what does it look like in the future? CHAD: Yeah, I mean, we've clearly made a lot of progress on this. It is better and easier now than it was in the early days because nobody wants to be the first. Nobody wants to be the first woman on the team. No one wants to be the first person of color on the team. You don't know when you're coming into an organization like that, whether it's the kind of place for you or whether you're going to run into problems. And so now that we've made some progress, that in and of itself makes it easier to continue on the journey. But when we were just getting started on that, we really needed to do a lot to intentionally fix it wi…

    Full show notes at the publisher

    476: OpenSauced with Brian Douglas May 25, 2023
    Show notes

    Brian Douglas is the CEO of OpenSauced which helps enterprises discover the best engineers in Open Source. Victoria and Will talk to Brian about meeting as many developers as possible, setting goals, and keeping himself accountable, and what makes a successful open source project. OpenSauced Follow OpenSauced on Twitter, GitHub, Instagram, YouTube, Discord, and Dev.to. Follow Brian Douglas on LinkedIn, Twitter, or visit his website. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: Hey there. It's your host Victoria. And I'm here today with Dawn Delatte and Jordyn Bonds from our Ignite team. We are thrilled to announce the summer 2023 session of our new incubator program. If you have a business idea that involves a web or mobile app, we encourage you to apply for our 8-week program. We'll help you validate the market opportunity, experiment with messaging and product ideas, and move forward with confidence towards an MVP. Learn more and apply at tbot.io/incubator. Dawn and Jordyn, thank you for joining and sharing the news with me today. JORDYN: Thanks for having us. DAWN: Yeah, glad to be here. VICTORIA: So, tell me a little bit more about the incubator program. This will be your second session, right? JORDYN: Indeed. We are just now wrapping up the first session. We had a really great 8 weeks, and we're excited to do it again. VICTORIA: Wonderful. And I think we're going to have the person from your program on a Giant Robots episode soon. JORDYN: Wonderful. VICTORIA: Maybe you can give us a little preview. What were some of your main takeaways from this first round? JORDYN: You know, as ever with early-stage work, it's about identifying your best early adopter market and user persona, and then learning as much as you possibly can about them to inform a roadmap to a product. VICTORIA: What made you decide to start this incubator program this year with thoughtbot? DAWN: We had been doing work with early-stage products and founders, as well as some innovation leads or research and development leads in existing organizations. We had been applying a lot of these processes, like the customer discovery process, Product Design Sprint process to validate new product ideas. And we've been doing that for a really long time. And we've also been noodling on this idea of exploring how we might offer value even sooner to clients that are maybe pre-software product idea. Like many of the initiatives at thoughtbot, it was a little bit experimental for us. We decided to sort of dig into better understanding that market, and seeing how the expertise that we had could be applied in the earlier stage. It's also been a great opportunity for our team to learn and grow. We had Jordyn join our team as Director of Product Strategy. Their experience with having worked at startups and being an early-stage startup founder has been so wonderful for our team to engage with and learn from. And we've been able to offer that value to clients as well. VICTORIA: I love that. So it's for people who have identified a problem, and they think they can come up with a software solution. But they're not quite at the point of being ready to actually build something yet. Is that right? DAWN: Yeah. We've always championed the idea of doing your due diligence around validating the right thing to build. And so that's been a part of the process at thoughtbot for a really long time. But it's always been sort of in the context of building your MVP. So this is going slightly earlier with that idea and saying, what's the next right step for this business? It's really about understanding if there is a market and product opportunity, and then moving into exploring what that opportunity looks like. And then validating that and doing that through user research, and talking to customers, and applying early product and business strategy thinking to the process. VICTORIA: Great. So that probably sets you up for really building the right thing, keeping your overall investment costs lower because you're not wasting time building the wrong thing. And setting you up for that due diligence when you go to investors to say, here's how well I vetted out my idea. Here's the rigor that I applied to building the MVP. JORDYN: Exactly. It's not just about convincing external stakeholders, so that's a key part. You know, maybe it's investors, maybe it's new team members you're looking to hire after the program. It could be anyone. But it's also about convincing yourself. Really, walking down the path of pursuing a startup is not a small undertaking. And we just want to make sure folks are starting with their best foot forward. You know, like Dawn said, let's build the right thing. Let's figure out what that thing is, and then we can think about how to build it right. That's a little quote from a book I really enjoy, by the way. I cannot take credit for that. [laughs] There's this really great book about early-stage validation called The Right It by Alberto Savoia. He was an engineer at Google, started a couple of startups himself, failed in some ways, failed to validate a market opportunity before marching off into building something. And the pain of that caused him to write this book about how to quickly and cheaply validate some market opportunity, market assumptions you might have when you're first starting out. The way he frames that is let's figure out if it's the right it before we build it right. And I just love that book, and I love that framing. You know, if you don't have a market for what you're building, or if they don't understand that they have the pain point you're solving for, it doesn't matter what you build. You got to do that first. And that's really what the focus of this incubator program is. It's that phase of work. Is there a there there? Is there something worth the hard, arduous path of building some software? Is there something there worth walking that path for before you start walking it? VICTORIA: Right. I love that. Well, thank you both so much for coming on and sharing a little bit more about the program. I'm super excited to see what comes out of the first round, and then who gets selected for the second round. So I'm happy to help promote. Any other final takeaways for our listeners today? DAWN: If this sounds intriguing to you, maybe you're at the stage where you're thinking about this process, I definitely encourage people to follow along. We're trying to share as much as we can about this process and this journey for us and our founders. So you can follow along on our blog, on LinkedIn. We're doing a LinkedIn live weekly with the founder in the program. We'll continue to do that with the next founders. And we're really trying to build a community and extend the community, you know, that thoughtbot has built with early-stage founders, so please join us. We'd love to have you. VICTORIA: Wonderful. That's amazing. Thank you both so much. INTRO MUSIC: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. WILL: And I'm your host, Will WILL. And with us today is Brian Douglas, CEO of OpenSauced, helping enterprises discover best engineers in open source. Brian, thank you for joining us today. BRIAN: My pleasure. Thanks for inviting me on the podcast. VICTORIA: Just tell us a little bit more about OpenSauced. BRIAN: Yeah, it's opensauced.pizza is the URL. So I always point that out because it's easy to found. WILL: I love it. BRIAN: And OpenSauced is a platform for engineers to find their next contributions and enterprises to discover the best engineers doing open-source, so... VICTORIA: Right. So maybe tell me what led you to start this company? BRIAN: Yeah, that's a great question. Actually, if you don't mind, I'll start further back. I graduated college in 2008 during the financial crisis with a finance degree. And what I learned pretty quickly is, like, if you don't know anybody in finance, it's a little hard to get a job in a bad market. So I took a sales role instead, mainly because I just wanted to learn. I was very much introverted. I wanted to learn how to talk to people, and have conversation, and communicate. So I did that four years and then got my MBA. And then started learning how to code while building an app, which is...I mentioned before we hit record I learned about this podcast around that time, which is, like, very serendipitous to be on this podcast years later. But, fast forward, OpenSauced, like, because of the whole networking aspect of how I got my job in sales and how I was able to do sales when I learned how to engineer, I knew the connection to open source, or how I learned how to code was, like, a wealth of information. So I made it my career goal to meet as many developers as possible. And then, I was working at this company called Netlify. I was employee number three there. And my role was to basically be a front-end engineer, but where I was actually getting more adoption to the product by doing open source. Like, every time I'd do an open-source contribution, I'd add a Netlify deploy preview manually in my PR. And that would give the maintainer enough juice to review the PR sooner. And I was doing a lot of open-source contribution at the time. So I wanted to build a tool to maintain, like, all the PRs I had opened in-flight that I needed to respond back to or...because back in, like, 2016, notifications on GitHub they weren't the greatest. WILL: [laughs] BRIAN: So I built a tool just to keep up to date on what I had opened and how I can communicate back with the maintainer. And saw a need...actually, I didn't see the need. I used this thing myself, and then in 2020, I started live streaming myself, building more features on top of this, like, CRM tool, and had a few people ask, "Hey, can you add a login to this? I'd love to use this, too, with my own database and stuff like that." So I did that. I added login. And I say database, like, we actually originally started with no database. We used GitHub Issues as a tracking mechanism for tracking repos and conversations. We've since moved away from that because, now, obviously, GitHub's got way more advanced in how notifications work. But the sort of ethos of the project still lives today, and what we have in the open-source platform. So that's, like, the long tale of how we got to where we are today. And then, I spoke at GitHub Universe on OpenSauced back in 2017. And from that talk, I had GitHub employees reach out to me and ask me to work at GitHub. So I accepted, and I worked at GitHub for almost five years, sort of putting OpenSauced to the side up until last year, decided to go ahead and pursue it again. And at that point, decided to make it a company. VICTORIA: What a cool story. There are so many things in there that I want to follow up on. I'm sure, Will, you also are like -- [laughs] WILL: [laughs] Yes. VICTORIA: I have so many questions. [laughs] WILL: Wow, that's amazing just hearing the story from you [laughs] got a four-year degree in finance, 2008 happened, no job, very hard to get a job because of who you know. And then you go and changed directions to start learning to code. And I love how it's kind of guided your path to where you are here right now. Like, who knows? But would you have been the CEO of OpenSauced if 2008 would have never happened? So it's amazing to see it. So, I guess, because I love the idea of OpenSauced...because I am that developer that wants to get into open source, but it is hard. It is hard to find the issues that you can work on. It's hard to get into the community to do that. So, if you can just explain to me a little bit more as from there, and we can do it from the enterprise portion later. But, as far as a user: a developer, what does it look like for me to use OpenSauced as a developer? BRIAN: Yeah, yeah. And that's a great question, too, as well. It's funny how serendipitous the story is today, but when I was living it, it was like, oh, man, I'm never going to get a job. [laughter] Or I'm never going to learn how to code. And I think anybody listening who might be where I was ten years ago, I just want to preface, like, your story is like a guided path through experiences. And every experience is like an opportunity for that sort of one piece of, like, the sort of stepping stone to move on to, like, CEO of whatever your next startup is or senior engineer, or staff engineer, whatever it is. But, to answer your question, Will, we built a Discord, and the Discord itself is how we sort of discovered this sort of onboard ramp into open source. So today, if you sign up to OpenSauced, again, opensauced.pizza, you connect to your GitHub account, and you get on-boarded into a flow to ask a couple questions. So, like, what languages are you interested in? And then, what time zone are you in? And the reason for those two things is, one because we're going to do recommendations for projects pretty soon. Everything is open source, so you can literally see the issues that are open about recommendations; happy to take contributions and feedback on it. And then time zone is because communication is pretty key. So, like, if someone is not awake when I see their PR, I have an expectation of, like, cool, I'll write a response, and I'll wait for them to wake up and respond back to that. So the goal there is there's a lot of projects on GitHub, like, 372 million repos is the number off the top of my head. They literally announce this stuff, and they share the data. But of those repos, only 225,000 have more than five contributors. Understanding what you're looking to accomplish first out of doing open source to either share knowledge, or gain knowledge, to get exposure, to get a job, or just to enhance your current job by go try something that's not in the roadmap of what you're working on. Eventually, we'll start asking those questions around, like, what type of contributor that you want to be, so we can start recommending those types of projects. But I mentioned that 225,000 repo number because there are a lot of projects that don't have five contributors that could use their second contributor, or third, fourth. And my recommendation is always find up-and-coming, like, growth-stage projects. A lot of people want to contribute to React. You had mentioned you did React, Will. That's a really big lift to go contribute upstream to a project maintained and supported by millions of enterprises around the world. But there are tons of projects that go trending every week that have no documentation, that have no README, that have no structure and are just getting off the ground. Like, those are the best projects that we try to showcase. So, like, that's hot.opensauced.pizza is our sort of up-and-coming project list. And the way that works is like projects that are trending based on our open-source community; we surface those there. There's a lot of work we have to do on that project. That was, like, a Hack Week project we did a couple of years ago as a community. But the basis of that is they're looking to build our recommendation engine off that. So, step one is find a project that is welcoming, that needs some work done, and then find the path in. So the path usually is going to be your CONTRIBUTING.md, which is like established projects will have this. But if you don't find a CONTRIBUTING.md, but you find a p…

    Full show notes at the publisher

    475: Designing Data Governance From the Ground Up with Lauren Maffeo May 18, 2023
    Show notes

    Lauren Maffeo is the author of Designing Data Governance from the Ground Up. Victoria talks to Lauren about human-centered design work, data stewardship and governance, and writing a book anybody can use regardless of industry or team size. Designing Data Governance from the Ground Up Follow Lauren Maffeo on LinkedIn or Twitter. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: Hey there. It's your host Victoria. And I'm here today with Dawn Delatte and Jordyn Bonds from our Ignite team. We are thrilled to announce the summer 2023 session of our new incubator program. If you have a business idea that involves a web or mobile app, we encourage you to apply for our 8-week program. We'll help you validate the market opportunity, experiment with messaging and product ideas, and move forward with confidence towards an MVP. Learn more and apply at tbot.io/incubator. Dawn and Jordyn, thank you for joining and sharing the news with me today. JORDYN: Thanks for having us. DAWN: Yeah, glad to be here. VICTORIA: So, tell me a little bit more about the incubator program. This will be your second session, right? JORDYN: Indeed. We are just now wrapping up the first session. We had a really great 8 weeks, and we're excited to do it again. VICTORIA: Wonderful. And I think we're going to have the person from your program on a Giant Robots episode soon. JORDYN: Wonderful. VICTORIA: Maybe you can give us a little preview. What were some of your main takeaways from this first round? JORDYN: You know, as ever with early-stage work, it's about identifying your best early adopter market and user persona, and then learning as much as you possibly can about them to inform a roadmap to a product. VICTORIA: What made you decide to start this incubator program this year with thoughtbot? DAWN: We had been doing work with early-stage products and founders, as well as some innovation leads or research and development leads in existing organizations. We had been applying a lot of these processes, like the customer discovery process, Product Design Sprint process to validate new product ideas. And we've been doing that for a really long time. And we've also been noodling on this idea of exploring how we might offer value even sooner to clients that are maybe pre-software product idea. Like many of the initiatives at thoughtbot, it was a little bit experimental for us. We decided to sort of dig into better understanding that market, and seeing how the expertise that we had could be applied in the earlier stage. It's also been a great opportunity for our team to learn and grow. We had Jordyn join our team as Director of Product Strategy. Their experience with having worked at startups and being an early-stage startup founder has been so wonderful for our team to engage with and learn from. And we've been able to offer that value to clients as well. VICTORIA: I love that. So it's for people who have identified a problem, and they think they can come up with a software solution. But they're not quite at the point of being ready to actually build something yet. Is that right? DAWN: Yeah. We've always championed the idea of doing your due diligence around validating the right thing to build. And so that's been a part of the process at thoughtbot for a really long time. But it's always been sort of in the context of building your MVP. So this is going slightly earlier with that idea and saying, what's the next right step for this business? It's really about understanding if there is a market and product opportunity, and then moving into exploring what that opportunity looks like. And then validating that and doing that through user research, and talking to customers, and applying early product and business strategy thinking to the process. VICTORIA: Great. So that probably sets you up for really building the right thing, keeping your overall investment costs lower because you're not wasting time building the wrong thing. And setting you up for that due diligence when you go to investors to say, here's how well I vetted out my idea. Here's the rigor that I applied to building the MVP. JORDYN: Exactly. It's not just about convincing external stakeholders, so that's a key part. You know, maybe it's investors, maybe it's new team members you're looking to hire after the program. It could be anyone. But it's also about convincing yourself. Really, walking down the path of pursuing a startup is not a small undertaking. And we just want to make sure folks are starting with their best foot forward. You know, like Dawn said, let's build the right thing. Let's figure out what that thing is, and then we can think about how to build it right. That's a little quote from a book I really enjoy, by the way. I cannot take credit for that. [laughs] There's this really great book about early-stage validation called The Right It by Alberto Savoia. He was an engineer at Google, started a couple of startups himself, failed in some ways, failed to validate a market opportunity before marching off into building something. And the pain of that caused him to write this book about how to quickly and cheaply validate some market opportunity, market assumptions you might have when you're first starting out. The way he frames that is let's figure out if it's the right it before we build it right. And I just love that book, and I love that framing. You know, if you don't have a market for what you're building, or if they don't understand that they have the pain point you're solving for, it doesn't matter what you build. You got to do that first. And that's really what the focus of this incubator program is. It's that phase of work. Is there a there there? Is there something worth the hard, arduous path of building some software? Is there something there worth walking that path for before you start walking it? VICTORIA: Right. I love that. Well, thank you both so much for coming on and sharing a little bit more about the program. I'm super excited to see what comes out of the first round, and then who gets selected for the second round. So I'm happy to help promote. Any other final takeaways for our listeners today? DAWN: If this sounds intriguing to you, maybe you're at the stage where you're thinking about this process, I definitely encourage people to follow along. We're trying to share as much as we can about this process and this journey for us and our founders. So you can follow along on our blog, on LinkedIn. We're doing a LinkedIn live weekly with the founder in the program. We'll continue to do that with the next founders. And we're really trying to build a community and extend the community, you know, that thoughtbot has built with early-stage founders, so please join us. We'd love to have you. VICTORIA: Wonderful. That's amazing. Thank you both so much. INTRO MUSIC: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Lauren Maffeo, Author of Designing Data Governance from the Ground Up. Lauren, thank you for joining us. LAUREN: Thanks so much for having me, Victoria. I'm excited to be here. VICTORIA: Wonderful. I'm excited to dive right into this topic. But first, maybe just tell me what led you to start writing this book? LAUREN: I was first inspired to write this book by my clients, actually. I was working as a service designer at Steampunk, which is a human-centered design firm serving the federal government. I still do work for Steampunk. And a few years ago, I was working with a client who had a very large database containing millions of unique data points going back several centuries. And I realized throughout the course of my discovery process, which is a big part of human-centered design work, that most of their processes for managing the data in this database were purely manual. There was no DevSecOps integrated into their workflows. These workflows often included several people and took up to a week to complete. And this was an organization that had many data points, as mentioned, in its purview. They also had a large team to manage the data in various ways. But they still really struggled with an overall lack of processes. And really, more importantly, they lacked quality standards for data, which they could then automate throughout their production processes. I realized that even when organizations exist to have data in their purview and to share it with their users, that doesn't necessarily mean that they actually have governance principles that they abide by. And so that led me to really consider, more broadly, the bigger challenges that we see with technology like AI, machine learning, large language models. We know now that there is a big risk of bias within these technologies themselves due to the data. And when I dug deeper, first as a research analyst at Gartner and then as a service designer at Steampunk, I realized that the big challenge that makes this a reality is lack of governance. It's not having the quality standards for deciding how data is fit for use. It's not categorizing your data according to the top domains in your organization that produce data. It's lack of clear ownership regarding who owns which data sets and who is able to make decisions about data. It's not having things like a data destruction policy, which shows people how long you hold on to data for. So that knowledge and seeing firsthand how many organizations struggle with that lack of governance that's what inspired me to write the book itself. And I wanted to write it from the lens of a service designer. I have my own bias towards that, given that I am a practicing service designer. But I do believe that data governance when approached through a design thinking lens, can yield stronger results than if it is that top-down IT approach that many organizations use today unsuccessfully. VICTORIA: So let me play that back a little bit. So, in your experience, organizations that struggle to make the most out of their data have an issue with defining the authority and who has that authority to make decisions, and you refer to that as governance. So that when it comes down to it, if you're building things and you want to say, is this ethical? Is this right? Is this secure? Is it private enough? Someone needs to be responsible [laughs] for answering that. And I love that you're bringing this human-centered design approach into it. LAUREN: Yeah, that's exactly right. And I would say that ownership is a big part of data governance. It is one of the most crucial parts. I have a chapter in my book on data stewards, what they are, the roles they play, and how to select them and get them on board with your data governance vision. The main thing I want to emphasize about data stewardship is that it is not just the technical members of your team. Data scientists, data architects, and engineers can all be exceptional data stewards, especially because they work with the data day in and day out. The challenge I see is that these people typically are not very close to the data, and so they don't have that context for what different data points mean. They might not know offhand what the definitions per data piece are. They might not know the format that the data originates in. That's information that people in non-technical roles tend to possess. And so, data stewardship and governance is not about turning your sales director into a data engineer or having them build ETL pipelines. But it is about having the people who know that data best be in positions where they're able to make decisions about it, to define it, to decide which pieces of metadata are attached to each piece of data. And then those standards are what get automated throughout the DevSecOps process to make better life cycles that produce better-quality data faster, at speed with fewer resources. VICTORIA: So, when we talk about authority, what we really mean is, like, who has enough context to make smart decisions? LAUREN: Who has enough context and also enough expertise? I think a big mistake that we as an industry have made with data management is that we have given the responsibility for all data in an organization to one team, sometimes one person. So, typically, what we've done in the past is we've seen all data in an organization managed by IT. They, as a department, make top-down decisions about who has access to which data, what data definitions exist, where the data catalog lives, if it exists in an organization at all. And that creates a lot of blockers for people if you always have to go through one team or person to get permission to use data. And then, on top of that, the IT team doesn't have the context that your subject matter experts do about the data in their respective divisions. And so it really is about expanding the idea of who owns data and who is in a position of authority to make decisions about it by collaborating across silos. This is very challenging work to do. But I would actually say that for smaller organizations, they might lack the resources in, time, and money, and people to do data governance at scale. But what they can do is start embedding data governance as a core principle into the fabric of their organizations. And ultimately, I think that will power them for success in a way that larger organizations were not able to because there is a lot of technical debt out there when it comes to bad data. And one way to avoid that in the future or to at least mitigate it is to establish data governance standards early on. VICTORIA: Talk me through what your approach would be if you were working with an organization who wants to build-in this into the fabric of how they work. What would be your first steps in engaging with them and identifying where they have needs in part of that discovery process? LAUREN: In human-centered design, the discovery process occurs very early in a project. This is where you are working hand in hand with your client to figure out what their core needs are and how you can help them solve those core needs. And this is important to do because it's not always obvious what those needs are. You might get a contract to work on something very specific, whether it's designing the user interface of a database or it's migrating a website. Those are technical challenges to solve. And those are typically the reason why you get contracted to work with your client. But you still have to do quite a bit of work to figure out what the real ask is there and what is causing the need for them to have hired you in the first place. And so, the first thing I would do if I was walking a client through this is I would start by asking who the most technical senior lead in the organization is. And I would ask how they are managing data today. I think it's really important, to be honest about the state of data in your organization today. The work that we do designing data governance is very forward-thinking in a lot of ways, but you need a foundation to build upon. And I think people need to be honest about the state of that foundation in their organization. So the first thing I would do is find that most-senior data leader who is responsible for making decisions about data and owns the data strategy because that person is tasked with figuring out how to use data in a way that is going to benefit the business writ large. And so, data governance is a big part of what they are tasked to do. And so, in the first instance, what I would do…

    Full show notes at the publisher

    474: Freelance Producer, Podcaster, Actor, Motion Capture & Performance Capture Performer Jasper (William) Cartwright May 11, 2023
    Show notes

    Jasper (William) Cartwright is a Freelance Producer, Podcaster, Actor, and Motion Capture & Performance Capture Performer. Chad talks to Jasper about his podcast Three Black Halflings, which is committed to discussing diversity and inclusion within fantasy, sci-fi, and nerdy culture from the perspective of three people of color, what it's like to be in the space, and why representation is super important. Follow Jasper (William) Cartwright on LinkedIn or Twitter. Check out his website at jasperwcartwright.com. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: Hey there. It's your host Victoria. And I'm here today with Dawn Delatte and Jordyn Bonds from our Ignite team. We are thrilled to announce the summer 2023 session of our new incubator program. If you have a business idea that involves a web or mobile app, we encourage you to apply for our 8-week program. We'll help you validate the market opportunity, experiment with messaging and product ideas, and move forward with confidence towards an MVP. Learn more and apply at tbot.io/incubator. Dawn and Jordyn, thank you for joining and sharing the news with me today. JORDYN: Thanks for having us. DAWN: Yeah, glad to be here. VICTORIA: So, tell me a little bit more about the incubator program. This will be your second session, right? JORDYN: Indeed. We are just now wrapping up the first session. We had a really great 8 weeks, and we're excited to do it again. VICTORIA: Wonderful. And I think we're going to have the person from your program on a Giant Robots episode soon. JORDYN: Wonderful. VICTORIA: Maybe you can give us a little preview. What were some of your main takeaways from this first round? JORDYN: You know, as ever with early-stage work, it's about identifying your best early adopter market and user persona, and then learning as much as you possibly can about them to inform a roadmap to a product. VICTORIA: What made you decide to start this incubator program this year with thoughtbot? DAWN: We had been doing work with early-stage products and founders, as well as some innovation leads or research and development leads in existing organizations. We had been applying a lot of these processes, like the customer discovery process, Product Design Sprint process to validate new product ideas. And we've been doing that for a really long time. And we've also been noodling on this idea of exploring how we might offer value even sooner to clients that are maybe pre-software product idea. Like many of the initiatives at thoughtbot, it was a little bit experimental for us. We decided to sort of dig into better understanding that market, and seeing how the expertise that we had could be applied in the earlier stage. It's also been a great opportunity for our team to learn and grow. We had Jordyn join our team as Director of Product Strategy. Their experience with having worked at startups and being an early-stage startup founder has been so wonderful for our team to engage with and learn from. And we've been able to offer that value to clients as well. VICTORIA: I love that. So it's for people who have identified a problem, and they think they can come up with a software solution. But they're not quite at the point of being ready to actually build something yet. Is that right? DAWN: Yeah. We've always championed the idea of doing your due diligence around validating the right thing to build. And so that's been a part of the process at thoughtbot for a really long time. But it's always been sort of in the context of building your MVP. So this is going slightly earlier with that idea and saying, what's the next right step for this business? It's really about understanding if there is a market and product opportunity, and then moving into exploring what that opportunity looks like. And then validating that and doing that through user research, and talking to customers, and applying early product and business strategy thinking to the process. VICTORIA: Great. So that probably sets you up for really building the right thing, keeping your overall investment costs lower because you're not wasting time building the wrong thing. And setting you up for that due diligence when you go to investors to say, here's how well I vetted out my idea. Here's the rigor that I applied to building the MVP. JORDYN: Exactly. It's not just about convincing external stakeholders, so that's a key part. You know, maybe it's investors, maybe it's new team members you're looking to hire after the program. It could be anyone. But it's also about convincing yourself. Really, walking down the path of pursuing a startup is not a small undertaking. And we just want to make sure folks are starting with their best foot forward. You know, like Dawn said, let's build the right thing. Let's figure out what that thing is, and then we can think about how to build it right. That's a little quote from a book I really enjoy, by the way. I cannot take credit for that. [laughs] There's this really great book about early-stage validation called The Right It by Alberto Savoia. He was an engineer at Google, started a couple of startups himself, failed in some ways, failed to validate a market opportunity before marching off into building something. And the pain of that caused him to write this book about how to quickly and cheaply validate some market opportunity, market assumptions you might have when you're first starting out. The way he frames that is let's figure out if it's the right it before we build it right. And I just love that book, and I love that framing. You know, if you don't have a market for what you're building, or if they don't understand that they have the pain point you're solving for, it doesn't matter what you build. You got to do that first. And that's really what the focus of this incubator program is. It's that phase of work. Is there a there there? Is there something worth the hard, arduous path of building some software? Is there something there worth walking that path for before you start walking it? VICTORIA: Right. I love that. Well, thank you both so much for coming on and sharing a little bit more about the program. I'm super excited to see what comes out of the first round, and then who gets selected for the second round. So I'm happy to help promote. Any other final takeaways for our listeners today? DAWN: If this sounds intriguing to you, maybe you're at the stage where you're thinking about this process, I definitely encourage people to follow along. We're trying to share as much as we can about this process and this journey for us and our founders. So you can follow along on our blog, on LinkedIn. We're doing a LinkedIn live weekly with the founder in the program. We'll continue to do that with the next founders. And we're really trying to build a community and extend the community, you know, that thoughtbot has built with early-stage founders, so please join us. We'd love to have you. VICTORIA: Wonderful. That's amazing. Thank you both so much. INTRO MUSIC: CHAD: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Chad Pytel. And with me today is Jasper William-Cartwright, Game Master for hire, Actor, Creative Consultant, Podcaster, Co-Host of The Performance Capture Podcast, and Co-Host of one of my favorite podcasts, Three Black Halflings. Jasper, thank you so much for joining me. JASPER: Hey, no, thank you so much for having me. And, man, with that intro, I almost feel... CHAD: [laughs] JASPER: I almost felt...I was like, oh, I feel cool. Those are some fun things. [laughs] CHAD: I almost started with a Heeello robots. JASPER: [laughs] CHAD: But it doesn't really have the alliteration that hello Halflings does, so... JASPER: Sure. I don't even know how the hello Halfling started. Like, I'm going to have to go back and listen to some of the earlier episodes again because I genuinely have no idea how it happened. And now it's gotten to a point where it's unyieldy. Every episode, I feel like I have to get a little bit further and a little bit higher. And I'm like, this can't be good for people's ears, so, [laughs] yeah. CHAD: So I know what the show is, but in your own words, what is the Three Black Halflings Podcast? JASPER: The Three Black Halflings Podcast is a show which is committed to talking about diversity and inclusion within fantasy and sci-fi, and sort of anything that nerdy culture touches, we try to cover it from the perspective of three people of color, what it's like to be in the space, and why representation is super important. CHAD: I want to talk about the origin of the show and how you got started. But I was introducing someone to the show previously because I try to tell everybody I can about the show. [laughter] I've noticed in the beginning when you started, there was a lot of low-hanging fruit, like, we can dive into this stuff and educate people. And over time, you've introduced actual play where you're playing Dungeons & Dragons on the show. And I think it's changed a little bit, and it's still great. But I always also recommend people go back to the beginning. And I think a lot of the episodes are sort of timeless. They're not about the news of the day. They're diving into particular topics and discussing either the impact or the problems that they have or how to play them better. JASPER: Yeah, definitely. I think you're absolutely right. It's been a weird thing where because we've become more popular and we're kind of more in tune with the TTRPG space; I think that typically what has happened for us is that we've spent less time really digging around for, you know, what's some stuff... all the things that we can explore. And we're a lot more kind of like, what's the beat of the moment? If that makes sense. And I think that's why we haven't done as many episodes like that. And also, just because we...I just think that the audience is changing. And the way that people consume our content is changing. It tends to go in cycles for us where we'll do a batch of very topical episodes then we'll do more really nitty gritty kind of game design episodes. And so I think a lot of it does depend on the sort of moment, what's going on. There are still a bunch of episodes that we have planned. And obviously, we have the Halfling University series which is coming out currently, which is a more retrospective look back on poignant things throughout the history of nerd [inaudible 3:11] and nerd culture. So I like to think there's a good variety on there. CHAD: Obviously the show, especially I think when it started, had a very heavy focus on Dungeons & Dragons, which I love. People who know me [laughs] know that I love Dungeons & Dragons. JASPER: [laughs] CHAD: And I've been playing it for a long time. And as someone playing it since I was a teenager, I didn't realize until I got older and learned a lot more...and certainly, the show went a long way to sort of educating me about how not only the origins of some of the tropes of fantasy and Dungeons & Dragons but just in general how to have inclusive play. When you're playing with a group of people, and to bring it back to a non-Dungeons & Dragons specific thing, this is true, I think, in any group of people. When you're surrounded by a group of people who look the same as you, are from the same area, have the same experiences, you don't realize what's missing from that table, and that's true in our companies, and it's true around a TTRPG table too. JASPER: Yeah, I completely agree. And I think that's the same for a lot of us. I remember doing a big post after I'd been doing the show for about six months, and it was just like, I was very open when I started the show that a lot of what I wanted to talk about I wanted it to be a safe space for me to explore some of these things. Because I grew up in a very White middle-class area, and therefore I had a lot of the blind spots that I would see my friends of color call out my White friends for or whatever it may be. And so I was like, okay, it's time for me to educate myself. And I wanted to do it in a safe space, in a place where I could learn from great people. Obviously, we had other co-hosts of the show who are fantastic people, but we had things like sensitivity consultants and people like that come on. I always like to shout out James Mendez Hodes, who, if you ever want to do a bit of a deep dive into fantasy...and you said, Chad, the historical basis for some of the stuff that we use, and he wrote some really incredible stuff. And so a lot of it was about me trying to educate myself as well and kind of put in that work. I thought there was a value there in doing it in an open forum in sort of saying, hey, I'm a person of color, and I'm also trying to figure this out, you know what I mean? CHAD: Mm-hmm. JASPER: Because I think that a lot of the time, the barrier for anyone who doesn't belong to a minority group is like, oh, man, I don't want to burden someone else with my own understanding of this thing, and I don't want to ask the wrong questions. Or maybe I don't even know where to begin in educating myself. And so there was something about the three of us and me particularly kind of being very open about the fact that we were learning about this too and that there might be things that...mistakes or things might slightly be out of place but that we have that openness and willingness to learn. And I think that in today's internet culture where everyone is so kind of reaction-based, it just felt important to me that we had a space where we could sit in and talk about stuff and really be open with each other in a way that we knew we'd all be able to shake hands and be like, cool, that was a good session or whatever [laughs] it was today, and not be like, I hate you, you know what I mean? Because someone had made a mistake, or misspoke, or something like that. And I think you're absolutely right. It's something I've started to do a bit more of recently, which is doing diversity and inclusion talks and coaching for companies because I think a lot of the lessons that I've learned through doing this show, especially around things like language and how you set up a work environment to suit people of color and more generally, minorities, it's a slightly continuous pursuit in the sense that you always have to be kind of open and learning. And I think also it provides a...what I think is best about it is that it provides such richness to your work environment. We always say on Three Black Halflings that we want you to take these things and use them to enhance your game. Like you're saying, if you have the same people with the same experiences all the time and that's all you ever hear, then, of course, you're going to get a pretty one-sided experience. And then, if you expand that out to include people from halfway across the world who have a very different experience, they're going to see things differently. And I can almost guarantee there'll be a problem that you and your team have been stuck on for like months, and someone from a different perspective will come in and be like, boom, there's the problem, or that's how we get around it because they have a different frame of reference to you. And so I always try to...it sounds really a…

    Full show notes at the publisher

    473: Noula with Noelle Acosta May 04, 2023
    Show notes

    Noelle Acosta is Founder and CEO of Noula Health, a data-driven platform that uses personalized hormonal health data to deliver tailored care. Victoria talks to Noelle about helping patients with uteruses to better understand their bodies by providing them with hormonal health data that's unique to them and providing them with individualized care they deserve at their fingertips through a virtual app. Noula Follow Noula on LinkedIn or Twitter. Follow Noelle Acosta on LinkedIn or Twitter. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Noelle Acosta, Founder and CEO of Noula Health, a data-driven platform that uses personalized hormonal health data to deliver tailored care. Noelle, thank you for joining me. NOELLE: Thank you so much for having me, Victoria. It's a pleasure to be here. VICTORIA: Wonderful. I'm excited to learn more about your product today that you're building. Can you just tell me a little bit more about it? NOELLE: Yeah, absolutely. Well, I feel like, [chuckles] one, you could work here. You did a phenomenal job of sharing what Noula is. But here at Noula, we are a virtual care platform that really empowers women and patients with uteruses to better understand their bodies by providing them with hormonal health data that's unique to them. Based on that information, we're able to provide them with the individualized, tailored care that they deserve at their fingertips through a virtual app. VICTORIA: Wonderful. And I'm wondering what led you to think I need to make this company. What happened in your life where you decided this needs to exist in the world? NOELLE: Really it stems from my own personal brush with an undiagnosed chronic condition where I truly was the one in five women who felt dismissed, denied, and ignored in the traditional healthcare settings. And that is really something that's actually unified us all as a team here at Noula. We have the shared frustration in terms of the gaps that we experienced overall; not one, two of our health journeys looked alike. And so during this time, I found myself really just kind of banging my head against a wall where I had these ongoing symptoms that disrupted every aspect of my life, not just my physical health, but it became really very much an emotional roller coaster as well. Because despite having access to care and wonderful employer-sponsored health insurance, I was finding that my doctors were essentially brushing me off, attributing it to stress. And it really led to me kind of just having this inner monologue and questioning myself as, like, is this in my head? Maybe it is stress-related. This doesn't feel normal. Should this be normal? And so I, just like 70% of millennials, turned to Google as my medical companion. I lost trust in healthcare settings and just turned to do research around what could be possibly causing the symptoms in my overall health. And I just refused to believe that this was my sense of normalcy. And through my own research, I started finding things like my ethnicity and my environment could have an impact in the symptoms that I was experiencing. I was dealing with chronic pelvic pain, irregular periods to the point where I was actually menstruating for seven months straight. I had horrible migraines. And so I just really turned to these medical journals to try to figure out and uncover what my body was telling me. And so, based on that research, I finally went back to the doctor demanding an ultrasound, where they ended up finding over 40 abnormal follicles and cysts on my ovaries. And even at that point, my treatment plan was a Band-Aid fix. And so, ultimately, I really felt like the system fundamentally failed me. This Band-Aid fix was essentially, hey, we'll put back your former birth control method and call us when you're ready to have a baby, and we'll figure it out then. And so, to this day, I actually haven't received any additional care, guidance from any clinician despite being in and out of the doctor's office with the symptoms. And so I ended up being diagnosed with a condition called PCOS. Again, from my own research, I learned that Mexican women with PCOS, so yours truly, we have the most severe phenotype that puts us at the highest risk for other complications that are beyond just reproductive health. It increases my risk for diabetes. It increases my risk for hypertension. And these are ultimately very costly to my health. And I was just frustrated. I thought, why am I learning about this through my own research versus the doctor's office, where it really felt like a one size fits all approach to care? And so, based on my experience, I started talking to more and more women. And I found that I wasn't alone with this shared frustration. We see that 80% of people who menstruate suffer from hormonal imbalances. And more often than not, women are juggling with more than two chronic conditions at a time. And so it's truly something that I felt as a patient that we were missing to feel empowered in our health and actually feel seen and heard. And then, when I actually spoke to clinicians as well, they felt that they weren't set up to care for their patients in the way that they wanted to care for them. VICTORIA: And I'm wondering how those women and the people you talked to started to inform the roadmap for the product that you were going to build. NOELLE: Yeah, yeah, absolutely. I mean, truly, the voice of those members, and these patients are the center of our lighthouse in terms of how we shape our product roadmap ahead. And so, ultimately, it really came down to us initially doing customer discovery. So I was really surprised to see how many people were willing to talk about their experiences navigating their health as a woman or a person with a uterus. And that was really telling in itself because I've heard from folks where they had to pay others with gift cards to have this conversation about how they might navigate certain workflows as it might relate to the products they're building. But naturally, these folks wanted to talk about their experiences. So we kind of tackled this in a couple of parts, one, I was going out into my own network, reaching out to friends of friends, posting in Nextdoor Facebook groups, really asking for 15 minutes of people's times to learn about their experience. And within two weeks, I had almost 100 customer discovery calls booked where these women were wanting to talk about their frustration and what they wished they had in terms of the care that they wanted. And so that was point A, like, okay, I think we're onto something. Our gaps in our experiences are shared across the board. And this is the pain that not only I experienced, or the Noula team has experienced, but that hundreds of women have experienced. The other piece, too, is, believe it or not, you know, we're constantly doing customer discovery as an early-stage company. But when we launched our beta, we launched with an initial hypothesis. But we saw that what our members were coming in for more aligns with their hormone health than what we initially thought, where we thought majority of folks would be coming to us at a family building stage. And then even [laughs] truly through social media, our TikTok channel alone when we lead with these persona stories it helps drive this just natural virality to it. And daily, we have folks reaching out to us asking if what they're experiencing is normal or what they should do. And so they're coming to us because we really fill this very prevalent gap in care today. VICTORIA: It must be really reassuring on a personal level and also on a business level that you found a problem that you can really help and make a difference with. NOELLE: Yeah, absolutely. I mean, it's frustrating that we are all bonded and unified by this experience. But ultimately, we'll continue to use the voice of our members as our guiding light to shape our roadmap ahead. And actually, that's what you see today with Noula. We took the learnings from the beta. We took the conversations that we've had with so many members and just women and folks outside of Noula to really shape what you see today. VICTORIA: That's wonderful. And you already mentioned one surprise that you found in your customer discovery process. I wonder if you could even tell me a little bit more about any hypothesis you had that you found from research; the outcome was quite different, and that changed your business strategy. NOELLE: Yeah, yeah, absolutely. So we have always seen ourselves as truly being this co-piloted partner for women in their healthcare journeys for life. But when initially launching our beta, we thought our niche today is going to be folks navigating family planning, so people who are looking to start a family in the near future, actively trying to conceive, pregnant, or recently postpartum. So we built a beta around that. And it was very low-code. This is before I had any technical talent [chuckles] on our team and essentially no money. And so, we built this low-code/no-code beta and launched it. We brought on about 100 folks to this closed beta. And with that, we built the product with that hypothesis in mind that we're going to be targeting specific stages. But what ultimately happened is as we were onboarding the 100 users, we found over...with each onboarded user, we started to see the scale tip where all of a sudden, 80% of those users very much had a story that mirrored my own experience with health. They were coming to us because they suspected that they had a hormonal imbalance or these unexplained symptoms that they didn't know what was causing them. Several of them had been diagnosed with conditions like PCOS, endometriosis, or fibroids. Many of them were dealing with unexplained period pain and irregular menstruation. And so we started to scratch our heads to be like, oh, wow. Okay, so these folks are actually coming to us for a different reason than we had [chuckles] initially anticipated. They're using the product differently. And also, they are far more engaged than our initial hypothesized users, which were pregnant people. And so while we have been able to really create a product that is able to adapt with these users over time, we found that that messaging and creation of a safe space for those users was incredibly important, and we wanted to lean into that. VICTORIA: That's really cool. And maybe talk more about creating that safe space in dealing with healthcare data. Were there any special considerations you had to bring into building your tech stack with those really delicate elements? NOELLE: Yeah, yeah. I mean, ultimately, safety and security of their data and honoring that privacy. We will never sell any data whatsoever. And I know that was a concern for many and still is since we've seen in the news this has been happening with other apps and stuff where they're selling user health data to social media sites. So honoring and protecting that privacy, first and foremost. The other piece is we had to also empower our care team to support our members in the best way that they can with the information that they had about their unique health. And so, unfortunately, our members were coming to us at such an emotionally turmoil time in their lives that they wanted answers. They were frustrated. They were saying, "Why is this happening to me?" We had to really ensure that we could be that empathetic ally for them, empower them with information, and really arm them with tools to use inside and outside of the clinic to get the answers that they deserve. VICTORIA: Right, and I see that. So on your site, there's a quiz you can take about your symptoms, and then you can sign up for what's ultimately going to be a home test kit. Is that right? NOELLE: Yes, yes. So users are able to sign up for Noula at no cost to you. So you can start free tracking your symptoms, and these symptom trackers are going to be customized to you. So based on... similar to the quiz that you mentioned, you'll be able to answer questions about what you're experiencing, what your goals are. And Noula will make recommendations of what to track within the app itself. You can then track your symptoms that you select over time and get this customized snapshot to build this true picture of your health. You can then continue to add on to that snapshot of your health through that home hormone test. So you don't necessarily need to purchase the test if you don't want to. But you have the ability to test your hormones to get a clearer picture of your baseline hormonal health. And we're able to really help arm you with that information about your body. And then, from there, beyond just that information from that data set, you have access to empathetic coaching from medical experts. All of our care coaches are registered nurses. So you do have that expert at your fingertips who's there to really steer and guide you every step of the way. And that was something that I actually felt was missing from my own experience when navigating my own symptoms pre-Noula. I found myself running these tests [chuckles] on my own, like ordering tests online trying to figure out what was going on. And just kind of hit this wall where I said to myself, I don't know how to interpret these. I don't know what to do with these. I don't know how to talk to my doctor about this. What do I do? VICTORIA: That's so interesting. And I heard you mentioned empathy a few times and how important that is. Would you say that's one of your core values that you bring into founding a company like this? NOELLE: Oh yeah, absolutely, absolutely. So I actually studied to become a doula. And so some of the pillars that we were trained in were really supporting our clients in these four primary pillars: ensuring that we can support them with physical support, emotional support, informational support, and advocacy. So really, those four pillars together have really steered us to create this foundation of empathetic care. And so that is truly integral to our brand and who we are, how we deliver that care, and also in such an inclusive and culturally competent way. VICTORIA: It sounds really important what you mentioned; building an app requires a lot of trust to be able to give you your data and trust that the results that you're getting are helpful. So I really love that that's a part of your core value that you bring to the organization too. NOELLE: Yeah, I think it was something that was really important to us from the very beginning, especially because we are a BIPOC and queer-co-founded company. It's rare that we see ourselves in the ecosystem, not just as founders [chuckles] but even just in how care is designed for us. So we wanted to ensure that we were creating this space where everyone can see themselves. And it's been so reassuring to hear from members and even just folks who find Noula on their own that they finally feel like they're seen and heard as an individual with Noula. VICTORIA: Well, that might be the answer to my next question, which is what keeps you going, and what's the wind in your sails that keeps you pressing forward with this? NOELLE: [chuckles] It's definitely that I think being able to hear from our members how Noula has helped change their life, even it is just a little bit where they feel more confident, where they feel supported, and they don't feel alone means everything to us. And the ot…

    Full show notes at the publisher

    472: Interlock Capital with Neal Bloom Apr 27, 2023
    Show notes

    Neal Bloom is a Managing Partner at Interlock Capital, a community of founders, investors, and subject matter experts. Victoria talks to Neal about what he finds attractive about startups and companies he's excited about, out of all the pitches he receives, how many he gets to say yes to, and when working with a team, what he uses to manage information and contacts for investors. Interlock Capital Follow Interlock Capital on LinkedIn, or Twitter. Follow Neal Bloom on LinkedIn or Twitter. Check out his website and blog! Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Neal Bloom, Managing Partner at Interlock Capital, a community of founders, investors, and subject matter experts. Neal, thank you for joining us. NEAL: Hey, thanks for having me. It's so great to be here with you. VICTORIA: Fantastic. I'm excited to finally get a chance to talk with you. I met you at an investor hike that you organize once a month. NEAL: A founders' hike, yeah. I get up nice and early on the first Wednesday of each month in Torrey Pines in San Diego. And we hike up and down the hill with ocean views. It's not a bad day. VICTORIA: It's a great way to start the morning, I think, and to meet other people, other builders of products in technology. So tell me more about your work at Interlock Capital. NEAL: Sure. It really kind of organically happened that I became an investor, but not planned at all. I have an aerospace background then built my own edtech and talent tech marketplace. I call it the LinkedIn for students is really what we built as our first startup called Portfolium. We sold it, and I got really into startup communities, especially because of some people who helped me with my first startup. I want to be a part of building an even better ecosystem for others. And that turned into a podcast, a blog, an event series. And once I had the capital from my exit, turned into angel investing as well, too, and really just found that as I got to know people over time, the more and more I got to know them, the more certain ones stood out that said, wow, I don't just want to help them for the good of it. I also just want to be along for the ride. And I started writing checks to other founders. So that was the beginning of my investor journey about five years ago. And over COVID, a whole bunch of other later-stage experience operators, either founder-level or executives at tech companies, said, "I want to learn to do this. Can I do it alongside you?" And we created Interlock Capital as an investment syndicate. A group of us can share and utilize our brainpower, our time, and our capital to help companies. It's kind of our focus. So that's why we call it a community because it's not just kind of a one-way pitch us, and we'll write you a check. It's very much get to know the people, find the exact right domain experts who have subject matter expertise, who've been there and done that before. If they like the company and they want to personally invest, then we go to the greater group and say, "Hey, everyone, who wants to join this deal specifically?" So 18 investments later from Interlock Capital, we now also have an investment fund. So now we write two checks into every company. We do our syndicated style, pass the hat, if you will, "Hey, everyone, anyone want to invest in just this deal?" And then match it from our fund. And we're writing between $300,000 to $500,000 checks into early-stage software or/and software plus hardware companies. VICTORIA: What an incredible journey. And I love that it's led you to creating a community as part of what you do as an investment capital group. What do you find interesting about these startups and these companies that you want to be interested in? NEAL: Part of it is how much you learn about yourself, to be honest. I get to meet three to five new founders a day in a variety of ways, whether it's straight Zoom and pitch, or grab a coffee, or see them on a hike. We're kind of constantly introducing ourselves to each other. There's a bit of learning about how to size someone up to a certain regard. So you're kind of building this inner algorithm of how to top-prank people and their ideas. That's one interesting way that I never thought I would be doing professionally. There's a lot that we say versus what we do, and that's a data point that I have to keep track of because I get pitched amazing ideas that will literally change the world for so much better. And you get really excited about it, and you get invested in it. And I call it founder love. You fall in love with these founders specifically and almost say, "I don't even care what you're working on. I just want to work more with you. How do we do it?" So there's a lot of that. So there are some dating aspects [laughs] in terms of founder dating, like getting to know people. There's the determining how do we date towards marriage? Meaning, I'll write you a check, and I'm along for the ride for the next ten years. And then there's the kind of relationship maintenance which is okay; I wrote the check, now what? Where can I be helpful to the company? How can I anticipate their needs so that they have to think one more thing of how to satisfy me? It's quite the opposite way around. I'm trying not to be a barrier. I'm trying to work for them while they're sleeping. So yeah, it's really interesting the kind of the relationship aspect that goes into getting to know and helping founders take their ideas and turn it into reality. VICTORIA: That's very cool. And I have talked to people who have met you and talked to your company and just how supportive and helpful you all are even if you choose not to invest. So I think that's a really valuable resource for people. And I wonder, do you think it's something unique about the San Diego community in particular that is exciting right now? NEAL: I think so. I think San Diego specifically has always had this culture of give-before-you-get mentality, and so we kind of lead with that. There are a lot of people moving here. And you could choose many places that could be great, like LA versus San Diego, and there's a certain kind of person that chooses here versus somewhere else. And what I have found is there's a certain kind of give-before-you-get cultural mentality here that somehow people register pretty quickly and come with. And so that's an underlying greatness about us here. There's also because of the great environment we live in, by the beach, healthy lifestyle. I think we choose to work on things that maybe are also satisfying, just like our personal lives, meaning we work on things that matter, that are going to change the world, that are life-changing. That's not to say that we don't need certain other kinds of technology. I'm sure at some point, we felt we needed Twitter, and maybe we don't feel like that now. [laughs] But here, it feels like everyone's working on very impactful things, and I think that's really special to think about. Some examples of that is we've got an interesting subset of the SaaS world in nonprofit tech. So GoFundMe was founded in San Diego. They have since acquired three other nonprofit tech SaaS companies in San Diego, like Classy. So that's kind of interesting. You've got people who want to build a business that services nonprofits, and now they're all under one roof. So yeah, I think there is something special. We can dive deeper into some of the other sub-industries or categories that are interesting here, too, if you're interested. VICTORIA: Well, I could talk about San Diego all day. NEAL: [laughs] VICTORIA: Because I'm a fairly new resident, and I'm in love with it, obviously. [laughs] But let's talk more about products that can change the world. Like, what's one that you're really excited about that you've heard recently? NEAL: Ooh. I would start a little high level in certain categories that I'm really liking. I like things I'm seeing in the infrastructure space right now, meaning, you know, whether it's pipes and our water utilities, and I would include that in energy and EV, you know, kind of a mobility piece. There's even the commercial side of mobility, so trucking and freight. That whole infrastructure layer is really interesting to me right now. A certain company that, full disclosure, we invested in recently is a company called EarthGrid. They have a product that is boring holes tunnel-wise underground, but they're using just electricity and air, so plasma. And it's fascinating. They can bore holes 100 times the norm right now. They don't need to potentially trench, meaning they don't need to cut above the surface. They can just dig for miles straight underneath the ground, so they can go under things with that. And really a lot of the expensive pieces, closing lanes on freeways or highways to put fiber in or plumbing and all that. So it's really interesting to see that. Now, one element is the technology is interesting. But they have a plan to actually own their own tunnels that go across the entire United States. So they don't just want to be a device that they're going to sell to everyone. They want to actually own their own utility that has major tunnels across the United States. So that's fascinating to me because that's like think big, think exponential around that. So that's one area that's kind of fascinating to me. VICTORIA: That's super interesting, and thinking about the impact it can have on making power more secure for more people, things like that. There are just so many problems to solve, and so many are people trying to solve them. [laughs] - NEAL: Yeah, exactly. And they have a clean tech angle in that there are a lot of different ways to dig and tunnel that includes chemicals, and so their big thing is to not do that. Some of their background is installing these kinds of lines in the EV space for solar panels. So they have a big kind of clean and sustainability focus there. And our infrastructure is aging big time. We've got 100-year-old bridges and pipes and other things that it's really interesting to see the government put money into. And so that is another aspect, a business model, per se of infrastructure. You have the government putting billions, if not trillions, into upgrading our infrastructure, which as an investor, I like to hear that there's free capital out there in forms of non-dilutive funding to help these along, and that's existed for hundreds of years. Cars and oil industry got these kinds of subsidies, and then the EV and solar panels. So that's a good area that I like to look in as well is where is there additional large-scale funding to help these products really get to market? VICTORIA: That makes sense. And so you're meeting three to five founders a day, and you're watching where the funding is available. And out of all the pitches that you receive, how many do you really get to say yes to? NEAL: Oh, it's small, I mean, one to two a month if that would be a lot, and those could take a few months to work through. The best way for us to invest is to get to know the people for as long as possible. So I kind of mentioned that relationship aspect. I want to see how people operate. I want to see how they build product. I want to see how they get to know their customer and iterate and bring that back into design thinking. And so that's a big piece is getting to know and see the people do the things that they're saying. Man, there are so many companies that I like on paper, whether it's oh my God, amazing team, or, oh, cool, the product. Yes, love that idea. And then you have to look at everything together, the timing, the valuation that they want, the team. Has this team been there, done that before? So there are a lot of elements that go into it. Like I mentioned, you have this founder love where you fall in love with the people, and maybe the rest doesn't work out or vice versa. But yeah, I think each investor comes at it differently. So my area because I built two tech companies that were talent tech-related, meaning connecting people for opportunities; my investing style is very team and talent and recruitment-focused, meaning what are the superpowers of the founders? Are they aware of their weaknesses and their strengths? Have they filled in those gaps by finding co-founders that are complementary and opposites? And then my partner, Al Bsharah, he is a super product guy, and he wants to break the product and see, how can you break it? What are they thinking product roadmap-wise? That's his first go-to. And so, for us, we're super complementary in that regard. So we will assess the same company in very different ways and then come together and say, "Let's share our scores, share our rank. Where do you think this company sits at in all these different areas and boxes?" And so that's a great way, that complementary skill sets as investors. We utilize those strengths together. So yeah, it's hard for a founder to know that. A founder who's building a product, the person on the other side of the screen, they're meeting me. They're not going to know my algorithm. They're not going to know what I value more than something else. So there's this whole dance. I wish it didn't have to be that way, but it is a dance. It's a negotiation. And that's why I build a community because I'd really rather take the gloves off and get to know people when they're not raising capital, when they really are just inspired by innovation and by customers, and they're just excited, and they're building product. That's the time I want to get to know them and see how they iterate before the capital question comes in. Because when it's capital, it tends to feel a little transactional, and that's just not the name of the game per se. VICTORIA: It makes sense. And I'm curious, working with your partner who has a specialty in product, has there ever been a big surprise that he presented with you that you would never have thought of without that product perspective? NEAL: Oh yeah, absolutely. I think there are many times now where either the company is really touting a specific piece of their product, whether it's a certain kind of technology that as a non-product builder either I think, wow, that's unique. That's special; that's novel. And I go to my partner, who really is an automation expert in terms of product building, and boom, can whip it out in a second and say, "I could that with Zapier," or now ChatGPT. So I think there are those elements that are good checkpoints of putting too much...maybe I get too excited about uniqueness or a novelty of a product. And then there's the opposite. There's the team undersells their product, and really they're touting, hey, we have a background in this industry. So we're going to go build because we know how to get into that industry. Our uniqueness is go-to-market, so they think. And it turns out, hey, you're really underselling the product here. There's something special about your vision system here or your data set that you're using to build your ML model. So I've seen a variety of both of those. I think we'r…

    Full show notes at the publisher

    471: Blossm with Brian Feretic Apr 20, 2023
    Show notes

    Brian Feretic is the Founder of Blossm, a community marketplace to buy, sell, and trade plants. Victoria talks to Brian about how coming up with the concept happened, getting started in a very scrappy way and then filling in gaps, and opening up the app to have full marketplace functionality with buying, selling, and trading capabilities. Blossm Follow Blossm on LinkedIn, Twitter, Instagram, Facebook or TikTok. Follow Brian Feretic on LinkedIn. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido or Tori. And with me today is Brian Feretic, Founder of Blossm, a community marketplace to buy, sell, and trade plants. Brian, thank you for joining us. BRIAN: Hey, it's great to be here, Tori. VICTORIA: Great. I'm excited to hear more about Blossm. Why don't you just tell me a little bit more about the concept? BRIAN: The concept actually happened at the end of 2019, and I'd already been a plant enthusiast for a couple of years. I was actually just going on my way to surf in my town of Ocean Beach, San Diego, and I stopped by this garage sale. And when I came back to pay my neighbor, I brought this rubber plant that are propagated just as a neighborly gift. She flipped out. She was ecstatic. She's like, "Oh my God, I'm such a huge plant person. Thank you so much. Why don't you come into my backyard, and I'll give you a plant tour, and you can pick something out." And what was cool about this was it wasn't just like a simple exchange. It was like this hour-long interaction with someone that lived four blocks from me that happened to be this big plant nerd like me. And I got her whole story. She went through all these different species I didn't know about. And then, she helped me pick one out, which I still have to this day. It's this crassula succulent. When I was walking home with my new plant, I was like, oh wow, I got to go download the app for this. I would have never known this person that lives four houses away was a big plant person like me. And when I got home, I searched the App Store. I did a Google search. I just couldn't find what I was looking for, which was basically this plant-swapping plant-connecting platform where I could find fellow plant nerds in my neighborhood. And so that kind of set me off on this path. I did some more research and decided...I was like, you know what? I'm going to commit to this and make this happen for myself and for my community. VICTORIA: Well, what do you think makes someone a plant person [laughs] or like a...how did you describe yourself? A plant nerd? What sets that user apart? BRIAN: We'll say it's like on a spectrum where people can shift along the spectrum. But I'd say when people start treating their plants more than objects and more what they are. They are these living things. They're beautiful. They bring people joy. I find it therapeutic to take care of them. And then the beautiful thing about it is that these plants grow, and you can propagate them and share them with your friends. And I think that is a critical aspect of this whole plant person thing. VICTORIA: So the plants have become a little more like pets, and you can grow them in a way that creates a community around your friendship and your local area. BRIAN: Yeah, exactly. That was actually the early signal about this whole plant world is that I saw people creating plant-dedicated Instagram accounts as if it was your dog or cat. And that was something that I realized this is a different type of person. This is a very passionate person willing to, like, they're so proud of their plant babies, we call them. [laughter] VICTORIA: Right. And it's funny, you say, plant babies. When I think of people I know who I would consider plant people, they do talk to their plants like their babies. They're like, "Oh, it's so cute." [laughs] Or they're like, "Oh, he's not feeling so well." So I think that's great. And so you started to do some research into this community, into this group. What surprised you about your early findings? BRIAN: This was actually something that I didn't realize until I dug deeper was that I thought that it was only going to be a local thing. People wanted to experience what I did with Sondra, who's the neighbor I swapped with, this in-person connection, swapping, checking each other's gardens out and houseplants. But I learned very quickly that people ship plants to each other not only within your own state but across the country, and this is global. And I was just like, how do people ship plants? Turns out I do it all the time, almost weekly now, for years. That aspect was critical to realize, all right; this plant community doesn't necessarily have to be bound by physical in-person distance. It can connect online, and people share all over via shipping. VICTORIA: That's really cool. So you decided that there's a whole international community. So is that when you decided to really start building something like an application to help people? BRIAN: I remember just throwing this idea out to a lot of different friends, like, various backgrounds. And I was like, "Hey, what do you think of this idea about connecting people through this shared love?" And there is not one person who thought it was a terrible idea. And then I remember talking about it with a roommate at the time, and basically the same thing. I was like, "Hey, man, imagine people connecting through the shared passion. Who knows? Maybe even love can blossom." And he was like, "Dude, that's what you should call it." I was like, oh, that's a great name. It's about three and a half years now, and it's stuck ever since. VICTORIA: I love that, [laughter] about sharing love, and how the name came about, and just starting with your friends and people you knew and bouncing ideas off of them. But your background is not specifically in technology. So what about your background applied? And what did you have to learn new to take along this journey? BRIAN: So my whole career, I've been involved within the science sector. I actually moved to San Diego to pursue graduate school in neuroscience. I was very curious about kind of full neural networks and how those contribute to behavior. Actually, the Ph.D. program I wanted to get into at UCSD, there's a specific lab doing this really cool research with this new innovative imaging technique. And I applied twice, and I didn't get in. And so I went into biotech. But I would say probably two things helped me. I realize now going through this entrepreneur path, things that helped train me for this, was definitely a graduate school where you're pretty much broke the whole time. My lab didn't have too much funding, so you had to be really resourceful and creative to figure stuff out with minimal resources. And that's perfectly summed up the last couple of years, just like figuring stuff out. We have no money. How do we get awareness of our product when we can't spend, you know, we don't have ad spend or marketing budget? And it just kind of requires you to get creative and think outside the box and just really think, all right, what do I do here? And I came up with some hacky-type strategies that have been very effective. [laughs] VICTORIA: Well, very cool. It sounds like you found your team now to start working with you on this in a very scrappy way. So how did you fill in those gaps, maybe in your knowledge or your background on how to get this done by the people that you grew around you? BRIAN: For me, it wasn't too difficult. Well, one, my background. I was very naive with tech at the time and just programming in general. So my first task, I laid out three options. It was like, one, I can learn how to code. I dabbled in it for a week, and I was like, man, there's no way. [laughter] Two, I was like, I can outsource it, maybe somewhat cheaply, but I don't want to spend all my savings on it. But more, I knew that, you know, say you come out of MVP product, the product always is growing, adapting, evolving, or you encounter bugs. And I could just see how full of friction the process would be if I had to, like, all right, we have found a bug, send the contract out. They have to accept the contract. And I just knew progress would be too slow to operate in that fashion. And the third option was, like, find a technical co-founder and pursue this dream with, you know, a buddy. I was like, all right, who do I know that is in the computer stuff? And that was my thought. And my first guy I pitched it to was a friend I went to college with at Bucknell University. And he was like, I think, "This is a good idea." But he's like, "I'm going to retire probably in five years, and this is going to be a very lengthy thing." He's like, "I'm not interested." The second guy was extremely down for it, but it turns out he didn't know how to do any mobile app development. He uses a consultant. [laughs] And so the third and who I ended up working with was my surfing and climbing buddy Nick Mitchell. I just knew he did computer-type stuff. I pitched him the idea, and he was like, "What's up with this plant thing?" VICTORIA: [laughs] BRIAN: And I was like, "Oh, dude, this is a rapidly growing market. I know the ins and outs really well. I know this audience. I'm one of them." He wasn't sold until he heard an NPR piece talking about the houseplant boom. And then his father sent him an article from the New York Times saying how millennials are embracing houseplants and driving this new houseplant market. And so I think this was maybe end of December, now in 2019. And he hit me up, and of course, he's like, "Oh, dude, I want in. Let's do it." But I also wanted to make sure I knew he could actually do what was the task at hand. [laughter] So I had my other first friend vet his GitHub and stuff just to make sure. [laughs] VICTORIA: Oh, cool. [laughs] BRIAN: And he was like, "Yeah, you know, he looks good. Worth a shot." And it turns out Nick is excellent. He did all the front end, back end. He built this whole app basically from scratch. It's pretty amazing what he's capable of. So I got it right on the third try. [laughs] VICTORIA: That's funny. And I'm not surprised it came from networking in the climbing community, either. BRIAN: Right. There's a lot of smart...definitely a lot of smart people in the climbing community. And those are like my closest friends now. So it was kind of cool to find someone in that place. VICTORIA: And I've been climbing with friends before, and you're talking about work or whatever. And they're like, "Oh, yeah, I'm also like an Azure architect," [laughs] like some specific skill that's related to what you need. And I think it's a similar cultural mindset of people you want to be working with too. Maybe that's just me. So, okay, so you found your partner. You had someone who had all the skills that you needed to make this happen. How long did it take until you really had something you were proud of? BRIAN: So, for me, I was laid off in August of 2019. I was working at Celgene, and they got acquired by Bristol Myers Squibb for like 72 billion, so massive merger. And I was kind of getting over the field. And so I was already basically unemployed. Nick, when we started actually working together in...we'll just call it January 2020. We started working on it casually, and then the pandemic happened. And then he got laid off. And he did about a three-month stint before he got another job at ServiceNow. But within those three months, he really cranked out like a full MVP. And then I had about probably at least 60 or 70 people I knew beta test the product for feedback and just initial thoughts. And so that was like a very critical time where we were all locked down. We have this cool idea. Let's just crank this out. So we had an MVP pretty quick. And then we actually launched it in June 2020. And I was already very stoked about the product. As long as it did its core thing, which is connecting people through this shared love, I knew it was like a proper test, a good enough test to see if this is a worthy endeavor. VICTORIA: That's really cool. So was there any surprising feedback that you got from that initial beta testing? BRIAN: Yeah. [laughs] So the initial concept was essentially like a Tinder for plants. [laughter] And I was just thinking about this idea, like, if people could just swipe on plants they've uploaded, and then if both people liked a particular plant and they swiped on each other, and they matched, it would open up a chat that would connect them. And it took the...one of the issues with bartering, in general, is people are like, "Oh, I'd love to swap that with you." And they're like, "Oh, what do you want to swap? What do you have?" And a lot of times, people don't align with what they have and what they want to swap. So I figured that would get this kind of friction out of there, but still, the core was connecting people. And then, very quickly, people found it fun. And this is still a feature right now on Blossm, which we've moved to the homepage. And it got a lot of engagement and interactions on it. But one of the simple changes was like, all right, maybe this is not the optimal way to present these plants people are uploading. Nick actually drew a lot of inspiration from OfferUp. And he was like, "Oh, this is very simple. This is a very clean way to present these things." So we started getting inspiration from OfferUp, and we changed that kind of swipe card functionality just to a scrollable grid. And that was a great insight on his part, and some of that has been core to the product from that point on. VICTORIA: That's so cool. So I can just go in the app and see a whole list of plants that people are willing to trade. BRIAN: Right. Actually, I would say another thing that happened very early on, too, was, once again, bartering is not the most efficient way to exchange things with each other. And within weeks, we're seeing people being like, "Oh, well, what do you want to swap?" And then people are like, "Oh, well, I don't want to swap for that. I already have that." And then other people are like, "Hey, I don't want to swap anything. I just want to buy it." And then other people are like, "Hey, I don't have anything. but how do I get stuff for you?" So right away, we opened it up to full marketplace kind of functionality with buying, selling, and trading. And we didn't have necessarily any payment system to facilitate that. We would just connect people. And then they would use Venmo, or Paypal, or Cash App, or things like that. VICTORIA: That makes sense. MID-ROLL AD: Now that you have funding, it's time to design, build, and ship the most impactful MVP that wows customers now and can scale in the future. thoughtbot Liftoff brings you the most reliable cross-functional team of product experts to mitigate risk and set you up for long-term success. As your trusted, experienced technical partner, we'll help launch your new product and guide you into a future-forward business that takes advantage of today's new technologies and agile best practices. Make the right decisions for tomorrow today. Get in touch at thoughtbot.com/liftoff. VICTORIA…

    Full show notes at the publisher

    470: CTO Excellence in 100 Days with Etienne de Bruin Apr 13, 2023
    Show notes

    Etienne de Bruin is Founder of 7CTOs and Author of CTO Excellence in 100 Days. Victoria talks to Etienne about his book, founding 7CTOs, and keeping your technology sustainable by inspiring and motivating technology teams and people to work together and build complex systems. CTO Excellence in 100 Days 7CTOs Follow 7CTOs on Twitter, Instagram, Facebook or YouTube. Follow Etienne de Bruin on LinkedIn or Twitter. Follow thoughtbot on Twitter or LinkedIn. Become a Sponsor of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Etienne de Bruin, Founder of 7CTOs and Author of CTO Excellence in 100 Days. Etienne, thank you for joining me. ETIENNE: My pleasure, Victoria. Thanks for having me. VICTORIA: You're welcome. I'm excited to talk with you today. I hear that you recently published your book. Is it today actually the day it came out? ETIENNE: Today is the day. The book was finished about; I would say, three months ago. So I have had great anticipation now for many, many months. And you caught me on the day, so I feel like today is my birthday. VICTORIA: [laughs] Well, I feel honored that you chose us as your first stop [laughs] in your marketing push for your book. So tell me, what in your experience led you to begin writing this? ETIENNE: Well, as you mentioned, I founded 7CTOs. I think it's about ten years ago now. I myself am a CTO type. I've had a career of basically being born to code in South Africa, which took me to Stellenbosch University in South Africa. I then joined a startup that took me to Germany and then landed in the U.S. in San Diego. And my whole journey has been a progression from individual contributor and really having great coding skills through the messiness and the intricacies of building startups, contributing to startups, and ultimately being in the role of CTO in startups. And what led me to founding 7CTOs was just a realization that I didn't have the support I needed. I felt like I was going to many meetups, which was mostly oriented towards coding and sort of different new technology stacks and frameworks, or I was going to cocktail hours with vendors who were trying to sell you something. And I really felt the need to just be with my people so that I could, in a safe, and consistent, and accountable way, share the challenges that I was experiencing. It was really from this place of founding 7CTOs, talking to hundreds of...I've probably spoken to thousands of CTOs by now. I've also placed people. I've connected people. I've seen people join companies because of connections I've made. And one of the things I saw that really bothered me was finding a great company in search of a CTO reaching out to me, talking to me about the role, me finding or through my network connecting them with a great CTO, only to find that a few months later either the relationship fizzles or even worse, the person did not succeed at the new company. And I just felt like you can have two people, a great founder, and great CTO, individually wonderful people, ostensibly well-suited to work with each other, but then make some basic mistakes that then lead towards not the desired outcome. And so I was really torn whether I should put some thoughts into a book or into some blog posts about what I think the first 100 days should look like in a fledgling relationship. And that's ultimately how the book was born. So long, long, long, long answer, Victoria. But that's where it all started. VICTORIA: No, that's great. I try to ask deep questions that get full answers back. [laughs] ETIENNE: You nailed it. VICTORIA: So I appreciate that context, yeah. So you talk about how to be successful in those first 100 days, which is critical to joining a new leadership team. What are some common mistakes that you mention that a CTO might make? And on the reverse side, what are some wins you could do early on to build trust? ETIENNE: I think a common mistake that I see is a bit of an identity issue. The CTO joins an organization and is eager to deliver value, and I think that that value is oftentimes misplaced. And what I mean by that is you hit the ground running thinking that there's all this stuff that you have to deliver in order to prove that you can make an impact, to prove that you were the right choice. And I think there's an innate desire to impress your new employer, which I don't think is limited to the role of CTO. But I think for the CTO, this looks like some technical achievements and impact, problem-solving. And I think what I like to see is the first 100 days being used to slow down a little bit, to listen, to be curious, to be open to building relationships, to have a longer view on what exactly is the system that you're joining. And I think to a fault; sometimes people will ignore the system they're joining and just start delivering value. And I think that that can often be misinterpreted or misunderstood. And then, if that is misunderstood in the first few months, then that really sets a tone for the rest of the tenure that I think puts the CTO on the back foot to deliver at a pace that maybe is unsustainable, so... VICTORIA: I love that you said staying curious because I think what you can see is a tendency for, I don't know, what I've seen; maybe you've seen this too. [chuckle] But some people have a problem that they solved in a past situation, and they think that that is now the solution to every problem that they come into in a new organization, and maybe it is. But I think dealing in complex systems, having curiosity as to why decisions were made in a certain way can lead you to a better understanding of the business if that resonates with you at all. ETIENNE: Yeah, I love that you said that. I'm a huge fan and student of complex systems. And so you just spoke my love language. VICTORIA: [laughs] ETIENNE: But that's exactly what happens. And I think that sometimes the debilitater of powerful and impactful people is the problem that you observe is maybe tainted by what you saw in the past. It might be a similar challenge, a similar problem. But what you solved in the past was part of a completely different system, different entities, different relationships. And I think that by nature because the CTO is used to solving thousands and thousands of problems, there may be a bit of complacency around what is it exactly that I'm observing is the challenge here? Why exactly was I hired? What exactly does success look like for them, for the people that hired me, for the system that I've come into? And I think the tendency is to ignore all of those questions and focus on how do I feed my own need to feel valued and start solving problems in sort of a whack-a-mole style? And I have found, even in my own experience, that there are some seriously unintended consequences that can arise from solving people's problems for them in ways that they are not used to, or they don't understand, or in some places just fully disagree with. And I think if you are not patient and take sort of 100 full days to just chill out and really enjoy learning about the system that you're joining, I think you're setting yourself up to fail or to at least be very unhappy. VICTORIA: Right, setting yourself up for some fun conflicts [laughs] to solve if you come out right out the gate. And I think maybe, too, the first 100 days the chilling out and learning, you also have time to build empathy and build trust with people so that when you do bring up suggestions, they're maybe a little more willing to listen, right? ETIENNE: Yes. And I think it's not uncommon to say, "Oh, well, I'm going to onboard myself. It's going to take some time before I show value." And I think there is a general sense that when the executive joins a company that, it's going to take some time. But I think that the temptation to jump into fiery situations is great, great in a bad way. It's a great temptation. And my book and my approach suggests that you take a step back and focus on a completely different area of the company, which is its people and its systems, and what success looks like for those people before you start jumping in and asserting your way of doing things. VICTORIA: And you mentioned a question that I was going to ask, like, what does success look like? Or say you're a CEO, and you're trying to hire a CTO; what does success look like? What kind of value do you think people should expect from someone in a CTO role? ETIENNE: Fundamentally, I think I might not be swimming in the mainstream on this topic. I don't believe that the CTO is a technical role first. I believe that the CTO is the Chief Technology Officer but is primarily a business role. And by that, I mean being a member of the C-suite, you are tasked, just like all the other members of the C-suite, to grow a company in a sustainable way. And whatever that middle letter is, is your domain and your expertise, and that's cool. But that T is surrounded by a C and an O, which in most cases has a fiduciary responsibility to the organization. But also, first and foremost, you are a first-class member of the C-suite. And so my book talks about this, but you are there to join in with the executive leadership team and to help that team towards success. And so what that looks like for me is you are wrestling on what the targets are for the company. You participate fully in that. You then allocate a budget. In other words, you allocate cost towards how you can achieve those revenue goals. And then, with that budget as CTO, you then are budgeting towards a team that you believe can get the technology implemented that will ultimately produce the revenue. So think about revenue target, technology budget, technology people. Now, these are all in the C-suite. These are just entries on a P&L. These are entries on the balance sheet. These are things that ultimately are abstracted towards company growth and company success. So with that, the CTO then turns into someone who wrestles with the tech teams, like, what are we going to implement? What ideas are consistent with our company principles and our vision? What does innovation look like? How do we inspire people to join our organization to do so? That, to me, is a fundamental role for the CTO, to inspire people to join the organization but also to be someone who implements and ideates on that journey. So I think a CTO succeeds when there is revenue growth, and that is due to budget being spent in an effective way to attract amazing people to ultimately build technology that is sustainable that then feeds into tech revenue that ultimately helps the company achieve its goals. VICTORIA: That's great. Yeah, I like that you said sustainable and the importance of people and how that relates to keeping your technology sustainable. And I'm curious if you could share more about what practices a CTO could bring to a new organization to facilitate that inspiration and to really motivate technology teams and people to work together and build these systems. ETIENNE: I think that speaks to my earlier answer, which is the investment in people and investment in understanding the systems that exist. So whether you are a CTO, that is the first time a company ever scales and grows into having that role being created, which, you know, most tech startups these days will have the role of CTO allocated and available. The important thing to understand for you as someone stepping into that role is that your teams have a construct. They have an impression. They have an image, either of your predecessor at that company or their experiences with leadership and technology at their previous companies. And I think it's extremely important to understand how you're being seen as a leader in the company and as CTO and that that vision of what people have of you is not necessarily based on your actions, your reputation, your good mornings in the mornings and your good evenings in the evenings. It really is based on people's constructs about what their experience has been of a CTO in their career, or like I said, the previous CTO, your predecessor. And so I think that it's critical as you step into this role that you take the time to bring that change to show people your ways, to show people what is important to you in a way that's not a bull in a china shop. But when you break stuff, and you come in, and you announce your presence, and you assert the new way of doing things, I think that that is met with suspicion and concern most of the time. And so I think if you can show people in the little things that you care about them, you're listening to them, you're curious about the system they're operating inside of, I think that that sets you up to then come in with the big ideas later on. But again, the emphasis being later on, past the 100 days. I talk about this in the book where introducing your tech strategy, introducing your way of doing things really comes a lot later in the 100 days than is maybe the preconceived notion. VICTORIA: And you also mentioned a few times what the CTO should be doing and a lot of great questions that you ask, like, what does success look like? How do we build this together? And finding ways to maybe generate more ideas than just what you would come up with with your team, you're more powerful. ETIENNE: Yes. And I think tag teaming on to that is a lot of times...and this is actually really a confounding thing that I've come across, which is the C-suite won't always understand what the role of CTO actually is. And teams won't always fully understand what the role of CTO is. When you talk about a CMO, or a CRO, or a CFO, I think you can generally understand what they're supposed to be doing. That isn't always clear for the CTO. And it's amazing how many times I have gotten the question, well, we knew we needed someone to help us with the tech, but we don't really know what it is that you do, or what you should be doing, or what success looks like. I think not making the assumption that people know what you're there to do is a form of showing some respect and humility. And this is why always when I'm in executive meetings, when I'm in stand-ups, or I'm in some sort of an architecture meeting, I will almost without fail I will say, "As the role of CTO, this is what I bring to the meeting," or "This is what the role of CTO would be looking for as an outcome of this conversation." Or "As the role of CTO, it is my job to ensure that our development capacity increases," to just never assume that people know what it is that you're there to do but to show them, I think, the respect and the courtesy that the role of CTO has a certain place in whatever meeting or brainstorm session is going on. VICTORIA: I think that makes sense, too, because I could see, you know, especially you mentioned with people who maybe have had past experiences with CTOs that are not the most positive. If you bring up an idea in a meeting, everyone thinks, well, that's the solution. That's what the CTO wants. And it might not. Everyone might not feel comfortable, like, without you caveating; this is why I'm bringing this up. You know, we're here to brainstorm and not for me to just tell you what to do. [laughs] ETIENNE: Yes, yes. And that's why I will often...honestly, this might be a real tip for people listening. But I will actively divorce who I am from the role that I'm in. And it enables me to have difficult conversations. It enab…

    Full show notes at the publisher

    Previous 1 15 16 17 18 19 64 Next

    Related Podcasts

    Know How… (Video)

    1

    Know How… (Video) Education
    JavaScript Jabber

    2

    JavaScript Jabber Education
    Programming Throwdown

    3

    Programming Throwdown Software How-To
    Software Engineering Radio – the podcast for professional software developers

    4

    Software Engineering Radio – the podcast for professional software developers Software How-To
    The Changelog: Software Development, Open Source

    5

    The Changelog: Software Development, Open Source How To
    Coding Blocks

    6

    Coding Blocks Software How-To
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights