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:
    399: thoughtbot Boost with Joshua Clayton Oct 28, 2021
    Show notes

    Chad interviews Managing Director at thoughtbot, Joshua Clayton, about what a Managing Director at thoughtbot does, what makes Boost at thoughtbot different than other teams, and the belief in integrated teams of designers and developers company-wide. Empathize with Your Customer by Josh Clayton thoughtbot Boost Follow thoughtbot on Twitter or LinkedIn Follow Josh on LinkedIn or Twitter Check out Josh's website Become a Sponsor of Giant Robots! Transcript: 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 Josh Clayton, Managing Director of the thoughtbot Boost team. Hey, I know that company. Welcome, Josh. JOSH: Hey, Chad. How are you? CHAD: All right. I'm back to the show I think. I didn't get a chance to look up the last episode you're in, but it was probably hundreds of episodes ago now. JOSH: Yeah, it's got to have been a while. CHAD: [laughs] Speaking of a while, you recently…now time is all messed up for me, but I know that you have been at thoughtbot for a long time. How long has it been? JOSH: It was 12 years in August. CHAD: It's been a wonderful 12 years, Josh. JOSH: I agree. I agree. CHAD: [laughs] JOSH: It's been fun. CHAD: So in that time, you have had a few different roles. But you've been a Managing Director for a while now. JOSH: Yeah, I think that's...let's see. It was seven and a half years for the Boston team. And then it's 10 and a half months with Boost. CHAD: So your background is as a developer. And you, like a lot of people who have a background as developers at thoughtbot, myself included, still do development on a fairly regular basis. What does the Managing Director job at thoughtbot actually do? JOSH: What don't we do [laughter] is maybe a better question. Effectively, we're running that team's business. So it involves some amount of software consulting. It involves software sales. It involves managing the profitability of the team. There are marketing functions, and, I don't know, anything and everything, hiring-related things. We opened up and recently filled our Development Director position, which was open for a couple of months over the summer. We've just opened up a Design Director position. So it's everything. [laughs] It's everything it feels like. CHAD: At the beginning of this year, we did an episode about the changes that we had made at thoughtbot to reorganize the teams around rather than geographic studios around the types of work that we would do on that team. And that's how the Boost team was created. So in that episode, we gave people an overview. But I'd love to hear in your own words, what makes Boost at thoughtbot different than the other teams, and what do you focus on? JOSH: So what makes Boost different? I think one of the drivers, one of the motivators, is to embed alongside existing product teams, engineering, and design teams, and help them get better, help them grow as well as ship features and fix bugs. So I think that the way that I position it is if there's an existing product that's deployed, people are using it day in and day out. Hopefully, it's been battle-tested. There are probably some funky areas of the code. Those are the codebases that we're operating in. It might be a team of two people; it might be a team of 200 people. But there is an existing product and an existing team. They're looking for our support to help make it better. CHAD: One of the things I love about Boost and the changes that we've made, especially relative to Boost, is that at thoughtbot, we really believe in integrated teams of designers and developers. And a big part of what we've always done has been to be a complete product design and development team that brings new products to market, big and small. And because we were one of the first consulting companies in the world to switch to Ruby on Rails and because of that deep experience with Rails, and scaling, and working on existing products, we had a significant number of customers who engaged us for development for that expertise, and to help them scale, and grow, and hire, and implement best practices or solve problems that they were having in their existing codebase or on their existing team. And even though that was a significant part of our business, it was always something that seemed that we maybe even didn't really want to be doing it, or it was on the periphery of our marketing and positioning. And I was super excited when we officially created this team because it allowed us to acknowledge that this was a significant part of what we do, a significant part of our revenue, and to have a team of people that opted into doing this kind of work who would not only love the kind of work but want to even grow it and do more of it. And we haven't really had that for this kind of work. We've had individuals wanting to do it but not at an organizational level in an organization that supports it. That was more of a statement than a question, but reaction? JOSH: [laughs] I think you're spot on. It's always been interesting to me to hear that it's...obviously, at thoughtbot, we have been building MVPs and working with a lot of different types of companies over the years and helping them launch products. But I think that the type of work that I and, ideally, obviously, other people on the Boost team enjoy working on is existing platforms and working alongside existing teams. We talk about legacy systems, and I think they get a bad rap. And it's like, no, it's battle-tested. CHAD: [chuckles] JOSH: The business has proven its viability. It is still around years later. Conway's law applies in all of the stuff. Again, there are gnarly aspects of the code. But I think that's what the folks on the Boost team enjoy being challenged by is problems where these things are larger systems. They've been around for a while, and they do get pretty gnarly. CHAD: I think one of the things that held us back in the past is that it is a skill set, and it's an experience. And you are going to be on an MVP project where you're doing design and development, going from concept to launching of a new idea, usually in a matter of weeks, working directly with a founder or a team of co-founders. And then you rotate on to this significantly larger project with maybe an engineering team of tens or dozens or hundreds of other developers on it. It's a very different skill set, and you have very different challenges in that environment. And when you're constantly switching between those different kinds of projects, you can't necessarily get better at it. And that's one of the other things that I think is helping us be more successful. JOSH: I remember one of the teammates had joined the kick-off call with me at the Boost inception that very first meeting. And it was Joël. And Joël had asked pretty straightforwardly, "What is the expectation in terms of project rotations?" Because I think historically across the company, we'd aimed to do two to four-month engagements before we'd rotate folks. And I told him point-blank it's going to be six months to a year probably. And I don't think it necessarily shocked him or other folks on the team. But I think when you're going into existing codebases and working alongside existing teams, there is inherently politics at play and complexities at play where it might take you being a new developer on a team six weeks, maybe longer before you actually feel comfortable and confident navigating the codebase and knowing where you can have and make an impact. And so, I think some of the shifts there have been particularly interesting to watch the types of consulting conversations that we have within the team just because it is a different beast, I think than building and launching products. CHAD: So let's get into a little bit of detail about the kinds of projects we're doing in Boost to the extent that we can give specific examples and maybe more importantly and relevant to the audience, what are the things that we see? What are the common challenges that we see as products grow and evolve, as teams grow and evolve? What do you think one of the most common challenges that people have is? JOSH: As teams grow and evolve, I think a lot of teams run into onboarding issues and general knowledge sharing. I think when you start a small team, and you're two, three, maybe five engineers, it's pretty easy for everyone to keep probably the entirety or the majority of that domain in their head at any one time. As you work to scale a team...there's a client of ours right now where they're effectively doubling every...I don't know what the time period is, but they're growing very, very rapidly. And the feedback that some of our team have provided to them is it's really hard, and there are very much knowledge silos. And they're working through, okay? How do we tease this out? How do we share this context so that you don't have a couple of folks that are effectively blocking every single other member of the team? And so that's one of the core areas that hangs up our team and other teams. [chuckles] Our clients bring us on, and a lot of times, it's like we're rip-roaring and ready to go. And it's like, I need information from a bunch of people, and the processes aren't in place such that we can be as effective as we would want to be given the nature of work that we're doing. CHAD: I think that's a straightforward problem, and it's a good example...I don't want to make this an hour-long thoughtbot commercial. But I'll just point blank say one of the reasons why sometimes working with us is positive for clients is it's really easy to have a certain pain around your onboarding process or company, even just simple things like how long it takes to get a new person a computer or to ramp them up on their existing team. If you're just hiring an employee, it's easy to ignore the cost of that. JOSH: Yes. CHAD: But when you're bringing on thoughtbot and we have a specific start date, and it's a certain cost, and those kinds of things, it can really expose the pain that is already happening but was just being ignored and provide the impetus to actually fix the problem. JOSH: One of the things that we try to set out to do on the first day for any project is to open up a pull request to the codebase, whether it's an improvement to the onboarding like the README for the repository or whatever it might be. Ideally, we are finding ways to contribute on day one. And sometimes, that's frankly not realistic for individual contributors doing it from their own machines. But oftentimes, we'll know that going in. And as we onboard new folks and things like that, we'll say, okay, well, day one is going to be your pair programming over Tuple or some other tool so that you are able to engage and interact with a team and work on the code, even if there's still a bit of a lag between GitHub access and everything else that's the base of onboarding steps. CHAD: So another common one that people bring us on to help with is scaling challenges in terms of the actual product itself, maybe that's performance or other scaling challenges. I'm working on a project now where that was how we first got involved. The service was failing, and it was only getting worse under the increasing scale. So, what are some tips that you have for how to effectively solve some of those problems while not bringing everything else that you need to accomplish to a screeching halt? JOSH: At the end of the day, you can't fix something that you don't know is broken. Or you might have a hunch in terms of, oh, I know this page or this set of pages are slow. I think so much of what we see is teams come in, and they're like, "We don't have New Relic setup." We don't have an instrumentation setup. So they can't measure anything. And so it's like, I know this page takes three or four seconds to paint, but I don't know why. And I don't know how to fix it. It's like, okay, well, the first thing that we need to do is set up some amount of performance monitoring and application tracking just to get a sense of what that's like. There is a potential customer who had reached out back in January of this year. So this was weeks into Boost's inception. And they said, "Listen, we've got some performance-related issues. We don't really know what to do, but we know the application is really, really slow on these couple of pages." It's like, "Are you using New Relic, or Scout, or anything like that?" They're like, "No." It's like, okay, that's the first thing that you need to do. And they came back about a month ago and were like, okay, "Here's the access to all of this data. Now we're ready to go," and it's like, "Yes!" They probably didn't need to wait for that long. But it really speaks to that in order to address some of the performance-related stuff; we need to have some sense of what is going on and where. I know Steph over on The Bike Shed Podcast had talked to Nate Berkopec. And she had floated one of the questions I had had. And he basically schooled me on that podcast and reiterated it really is ultimately about measuring so much of what we're doing. CHAD: Yeah. One of the things, especially for teams that are having a problem but feel like they don't know what to do it's tough when it's actually the case. But the reality is a lot of times; there’s actually very low-hanging fruit that it's just no one has the time or experience to actually identify that. And putting some monitoring in place combined with actually taking the time to look through it, especially if it's the first time you ever hit scaling problems...There's either a missing database in that index or some N+1 queries, and fortunately, once you identify that kind of problem, it's usually fairly quick to fix as well. It's a different thing when there's maybe fundamental architecture things that are causing your app to have scaling problems. But it's very unlikely that those are the first problems you're ever experiencing. The first problems you're ever going to experience if your app is running slow are going to be things happening at the database level or missing an index or something like that. And it's very unlikely that significant architecture changes need to be put in place in order to fix the first scaling problems that any product usually has. JOSH: That wasn't the type, or at least I think when we got brought on, and you were working on your most recent clients, we were well beyond...maybe we weren't, maybe I'm misrepresenting or misremembering, but it feels like we were well beyond some of the low hanging fruit. CHAD: Yeah, there was a batch of low-hanging fruit. One of the things if you're working on a product that is scaling super rapidly, what can happen is that the low-hanging fruit masks the other problems that are happening there because it all happened too quickly, all at the same time. And that was the case on this project. So it went from having hundreds of people using it to millions of people using it in the span of a month. And so there was low-hanging fruit. But removing the low-hanging fruit didn't make the app suddenly work again; it just made it so that we could look at the metrics and say,…

    Full show notes at the publisher

    398: Education 2.0 with Victoria Ransom of Prisma Oct 21, 2021
    Show notes

    Chad interviews Co-Founder and CEO, Victoria Ranson of Prisma. Prisma is a stealth-mode education startup on a mission to reimagine the way children are educated. Their mission is to create a generation capable of solving the world's biggest problems by creating and running a comprehensive virtual learning program for kids in grades 4-8 that is very unlike any other traditional homeschooling program you've ever heard of. Prisma's Website Follow Prisma on Twitter or Facebook Follow Victoria on LinkedIn Follow Co-Founder, President, and Victoria's husband Alan Chuard on Twitter For more info, email info@joinprisma.com Become a Sponsor of Giant Robots! Transcript: 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 Victoria Ransom, founder, and CEO of Prisma. Victoria, thanks for joining me on the show. VICTORIA: Hi, thanks for having me. CHAD: So, Victoria, before we jump into this great product that you have, why don't you tell people what Prisma really is. VICTORIA: Sure. Prisma is a very comprehensive educational program for kids who are learning from home or from anywhere in the world. It is not at all like traditional homeschooling because we provide kids with a very social experience. Kids are part of a cohort where they're meeting live with other kids every single day and collaborating with them on projects, and learning from each other, and discussing. And we provide coaches who are there every step of the way with the kids, providing them with rich feedback, helping to bring out the best in them, providing really engaging, live learning experiences. So it’s not traditional homeschooling, although it has a lot of the really great benefits of that with the flexibility and the ability to learn from wherever you are. But we're equally not like typical online schooling, which I would say has tended to be more of an approach of taking traditional school and bringing it online. So there's still a concept of lectures, and grades, and textbooks. They may be electronic in nature, but they still resemble textbooks. The Prisma curriculum is very different. It's rooted in learning through doing and project-based learning, and applying learning to the real world, and allowing kids a lot of choice. So they're ideally always learning through the lens of something that interests them and allowing them to go at their own pace. So a lot of the best practices from some of the most innovative bricks and mortar schools we're bringing to an online environment. And then, of course, we're very different from bricks and mortar schools because it is a virtual program where kids can learn from anywhere. So we think it's a new approach to education that is really uniquely flexible, really prepares kids. We're very focused on preparing kids for the kind of world they're going to live in. The world is always changing rapidly. But I think this generation of kids is going to experience a future that's unlike anything we've ever seen in terms of the level of shift and change, AI being one of the reasons. If you look at studies that look at the future of work, I think some studies we've read say 65% of today's elementary school kids will work in jobs that are yet to be invented. So, how do you prepare kids for that kind of future? And so, we're very focused on giving kids the holistic skills and the mindset that they will need to thrive in that kind of world. So yeah, that is Prisma in a very long nutshell. CHAD: [chuckles] Obviously, I think we'd be remiss if we didn't talk about the context of where we're in, which is kids just went through a year or more where a lot of kids were remote for school. And did Prisma exist before the pandemic? VICTORIA: It did in our minds very much so [chuckles] but not in reality. So Prisma arose out of our own personal needs. So my husband and I are the founders of Prisma. We've actually been entrepreneurs for most of our careers. After successfully selling a company to Google a few years ago, we said whatever we do next in our lives; we want it to be something that has the potential to have a large positive impact on society and on the world. And then struggled to figure out what that should look like because there are a lot of things that need solving in the world. But we have three children, and as they approached school age, it really caused us to do a deep dive into how do we want to educate our kids? What do we think is the best approach to education? And from that, we started to formulate a vision by looking at all kinds of different schooling models, from homeschooling to micro-schooling to innovative bricks and mortar schooling. We developed a picture for how we wanted to educate our kids. But that really inspired us to create something that could be accessible to many more kids than just our own kids. And so we had a good 18 months to 2 years of researching, ideating, thinking about the pros and cons of a virtual model. And then along came COVID, and at that point, we said, you know what? There's never been a better time to test out an innovative new approach to schooling, especially one that was always going to be home-based from the get-go. And so let's start ideating and dreaming about this, and let's just put it into action see how it goes. So it was born during COVID, but the roots of Prisma very much predate COVID. CHAD: So, what was the actual timing there from when you decided to do something? When was that to you had the first students? VICTORIA: Yeah, that was a whirlwind. [laughs] CHAD: I can imagine. VICTORIA: Yeah. So really, it was late March, I think of 2020, when we said, "We've just got to do this. The world is telling us to do this." To when we had our first kids in the door was early September. So between basically the beginning of April to the beginning of September, we incorporated, we refined our vision. The good news is we had a vision, and it was mapped out. We hired a curriculum team, hired coaches, created a website, found our first families, all of that. And we launched Prisma very clearly with the families saying, "This is a pilot. We're trying something new here. Let's see how this goes." And we actually told the families, "Look, we're going to definitely run this until the end of December, the end of the year. And if it's not going really, really well, then we will suggest you go and do something better." But it went great. It's not to say our model is perfect. And we believe very much in constant improvement and constant iteration. But in terms of kids loving school at a time, the national narrative was that kids were hating school, and they were falling behind, and parents were finding distance learning a disaster; we had kids that were loving school more than they ever had. And we surveyed kids, and that's why we know that. Parents were extremely happy. Everything was pointing to the fact that we really had found something unique that was really working. And so it turned from a pilot into something that we're now putting all the building blocks in place to be able to scale more broadly. CHAD: School is a big thing, a big concept, and a very important one. Working so quickly in the midst of a pandemic, you know, launching any product is as much an art and finding what those first features need to be. How did you identify what that is and make sure you had something that was viable but that you could get done on time? VICTORIA: I think that came down to...because obviously, our product is our curriculum and our model. We have a software development team and a product development team. And they are building the tools that we'll need to run our model. But when we first launched, we were piecing together different tools that already existed. So the initial product really was the curriculum and our model of education and the tools that we pieced together to make it work. And I think the reason we were able to be successful is that we did a lot of groundwork in saying, what really matters? What is our perspective on what is the goal of this educational model? We got clear on that. What do we think are the values or approaches that really are critical to achieving that goal? And then using that as our Northstar. So to be more concrete, we were really clear about two things in terms of why we were developing this model. One was we really wanted kids to love learning. We think they should love learning because learning is amazing, and it's exciting. And every kid is born with an innate desire to learn. And that if you want to bring the best out in kids, you want them to be excited about what they're learning. So kids loving learning was a very strong Northstar for us. And the second was what I already talked about before is developing an educational model that will really give kids the skills and mindsets they will need to really thrive in what is an exciting but uncertain future. And so that was the Northstar of why are we doing this. From that, we developed a clear perspective on okay; if we want kids to love learning, how do we do that? And so it was things like making sure that kids have choice so they can apply their learning to things that really excite them, making sure learning is applied to the real world, so kids are never saying, "Why the heck do I need this?" Making sure that learning is hands-on as possible because we think kids just get more out of it, and learn more, and enjoy it more if they can really be hands-on and project-based. Making sure...I won't go through them all, but we have our sort of core curriculum values, making sure learning is happening in a community-supportive community. And then the other thing we're really clear on is okay, what are these overarching skills or mindsets that we think are critical to succeeding in adulthood? And it was things like systems thinking and problem-solving, having a designer's mindset, which is this concept of being comfortable with iterating, and getting feedback, and putting yourself in someone else's shoes, being an excellent communicator and collaborator. Again, I won't go through them all. But we were just really clear. I think we had a really strong foundation of why do we exist and what is our approach here? And that enabled us to then be really clear about things like, okay, we're not going to throw the kitchen sink in terms of everything that kids need to learn, no. We're more focused on overarching skills than checking the box on 1,000 different science standards that kids might need to go through. So yeah, as you said, I think whenever you launch a product or a company, being able to narrow down because you can't offer everything you want to offer, being able to narrow down to what really matters is important. And I feel like we did a pretty good job with that. CHAD: Awesome. What was the makeup of the initial team? You mentioned you and your husband. How did you split the responsibilities between you two, and then who else was involved? VICTORIA: So my husband and I have been co-founders of several companies. And it's worked really well because we have very different skill sets. My husband has much more of a product mind. He's much more detail-oriented. And he has a real eye for design and user experiences and also a creative marketing mind. So that gives you a sense of where he tends to focus. And I've tended to focus more on people management and operationalizing businesses, being more that external spokesperson. And so that's how we have split. He's doing more of the software development and product marketing and marketing side of Prisma. And I'm more involved in the day-to-day running of the program. Our first two very, very critical hires were curriculum developers, and Prisma would not be what it is today if we hadn't hired the two people that we hired. And they really balanced each other well because we hired Kristen, who had really deep experience in education. She had at a pretty young age founded her own charter school very successfully and just had such super deep experience in education, teaching, teaching teachers, training teachers, managing her own school. And then we had Emily, who came from a really non-traditional background. She'd actually come up through the theater world, had done a degree at Harvard School of Education. And they actually had some good experience with working with professors at Harvard in innovative ways to assess, also, computer science education. And she's got a very out-of-the-box way of thinking. And between the two of those, it was a really great combination for us to turn what was a vision of a curriculum that Alain and I had created into something actually concrete. And then the other critical hires were our first coaches. Again, we got super lucky in hiring just really fantastic coaches. And we've now realized hiring great coaches is a very fundamental part of what we do. And in fact, it will be one of our scaling challenges, I think. But again, we got really lucky with our coaches. And then, over time, we've hired operations people and product people. But I think that initial magic of the curriculum team and the coaching team was really important. We wouldn't be where we are today if we hadn't have hired those people, I think. CHAD: Did you bring on the two curriculum team members full-time right away? VICTORIA: We intended to, I think, when we were still incorporating the business. And all of this was happening in such a rush that I think we technically had to bring them on as contractors. But it was intended as a full-time role. Having said that, our hiring process asked them to sketch out in a fairly in-depth way or at least to sketch out in-depth pieces of what the ultimate Prisma curriculum would look like. So we did have a chance, I think, to test them out fairly well before we committed. CHAD: So did you take investment to start Prisma, or did you self-fund it? VICTORIA: We have self-funded. We're super lucky to be in the position to be able to do that, and we are continuing to self-fund. We had a ton of interest from venture capitalists; I think partly because we're somewhat proven entrepreneurs with other successes. And then also, because there was just suddenly a big spotlight on education and the belief that education might really shift. But we have not taken funding because...it doesn't mean we won't ever. But we're very focused on being mission-first. And we're also very focused on growing carefully and thoughtfully. We think in the long run, we'll be far more successful if we really grow conservatively, at least initially, until we really feel like we've refined this and we know how to keep a really high level of quality and customer satisfaction while scaling. And I think our concern is that sometimes when you take outside capital that that capital might not be as patient. It might really push to grow faster than what we think might be the best approach. So thus far, we're just in the lucky position where we haven't had to take outside capital. CHAD: I assume that you're on a traditional school schedule based on what you said about starting in September. VICTORIA: We kind of are actually, which is funny because our initial vision for Prisma was to have it be year-round. And I think our families have been super open to so many innovative things. But the idea of having a summer break seems to be something that families don't want to give up on. CHAD: [laughs] VICTORIA: So I think our u…

    Full show notes at the publisher

    397: Driven By Fulfillment with Natalie Nzeyimana of Harbour Oct 14, 2021
    Show notes

    At harbour.today, Natalie Nzeyimana and her team are helping people build holistic resilience. On this episode, she and Chad talk about building the app at the beginning of the pandemic when she witnessed herself and others feeling like they were close to drowning and feeling really unmoored. Harbour is a space for people to anchor themselves, find clarity, and set sail. The community offers one-to-one coaching, workshops, a course, and a daily check-in tool. harbour.today Instagram Twitter Lunchclub Become a Sponsor of Giant Robots! Transcript: 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 today, I'm joined by the founder of Harbour, Natalie Nzeyimana. So, Natalie, thanks for joining me. NATALIE: Thanks for having me on. CHAD: So tell me a little bit about what Harbour is. NATALIE: Sure. Harbour is a space for people to anchor self, find clarity, and set sail. We offer one-to-one coaching, workshops, a course, and a daily check-in tool. Harbour was built at the beginning of the pandemic when I witnessed within myself, and the people I knew who I'd worked with, friends, family, just a lot of us felt like we were close to drowning and feeling really unmoored. And so, it began as a course to think about the ways we could use holistic strategies to anchor ourselves and set sail. And from then, from November 2020 to now, it's become a product. CHAD: You started in November. And I know we first met in London a while ago. You were teaching yourself to code working on an education product if I remember right. And we got together at Google Space there and paired for a little bit. Did you code Harbour yourself? NATALIE: It feels like another lifetime. CHAD: [laughs] NATALIE: I think life before the pandemic and life after the pandemic; there’s a real line there. I've done quite a bit of the coding myself. However, I've also used a lot of no-code solutions to create MVPs. They've been amazing at helping me scale, helping me test out ideas incredibly quickly. And so one of the interesting things about juggling doing client work, and then also building the back end, and building the module, and then building the design work, and thinking about content juggling all of these different pieces, is that equation of do I invest time in HTML, or do I invest time in machine learning that's going to help me scale? And making all of those intricate decisions has been really, really interesting because, of course, I want to make everything myself. But these no-code solutions have enabled me to test hypotheses so much faster so that I can save time in the long run. CHAD: Well, tell us a little bit more about what the product is today and what you went through to get to this point. NATALIE: Sure. So initially, I just posted on LinkedIn to see who would want to join the course. I had a really simple Squarespace page, and then that evolved into a Typeform which I would use with clients to help them track progress and checking in with their chakras every day. And so, the way that Harbour works is that we do an energy review based on the seven in-body chakras. And so, for anyone who might be unfamiliar with this terminology, the chakras are...well, there are different schools of thought on this. They are a system for either focusing during meditation depending on where you sit in terms of your feelings towards energy bodies. They are a subtle body energy system of themselves. And what I find incredibly helpful for those chakras is that they help people map their energy in a way that I haven't found anything else does effectively. So starting from the root chakra, which is the base of your spine, you can ask yourself, am I feeling safe? Am I feeling grounded? Am I feeling as though my material needs are met? Traveling up towards your reproductive area, you've got the sacral chakra which governs your sense of feeling as though you can desire the things that you desire in the world, feeling as though you are sensual. You're able to experience pleasure. You're able to be creative and playful. And then up to the solar plexus, which is around your navel area, governs the sense of personal power, empowerment, will, feeling as though you're able to go after your goals with chutzpah and energy. And then moving into the heart chakra, which governs this idea of do I feel as though I'm open to receiving and giving love freely? And the throat, do I feel as though I'm an open conduit for the truth of who I am? Do I feel as though I'm able to express myself fully in the world? And then into the third eye, which governs your intuition. Do I feel as though I'm able to trust my intuitive leads and to move with grace and ease, trusting and able to go with the flow? And then finally, we have the crown chakra, which governs do I feel open to receiving divine wisdom? Do I feel as though I'm in this world on my own and there's nothing but pure materiality? Or do I feel open to receiving what some people might call God or Allah or the Tao? Whatever your orientation is, do I feel open towards receiving that kind of wisdom? What's really beautiful about the chakras is that they've been used by ancient Chinese, ancient Egyptians, Tibetans, Sikhs, multiple traditions, and indigenous systems. And so there's kind of this lovely thread of people around the world thinking about how energy moves through our minds, bodies, and spirits. But that's quite a lot. So we just ask seven questions every day. CHAD: So I have to admit I was not...and my first exposure to this is this conversation. So is this something that you have been aware of and practicing prior to working on Harbour, or is it something that you found which then led you to the creation? NATALIE: Definitely the latter, the latter. So I went through a pretty gnarly, dark night of the soul and just had this huge existential crisis of wondering what am I here to do? Why am I here? What's my purpose in life? I don't know if other people might resonate with this, but kind of feeling that you make these huge or not so huge career goals, and then you reach them, and you still feel like something's missing. And in my quest to understand what that missing piece might be, I came across chakras, and I found it incredibly helpful. I think people who do yoga might be aware of this because they often come up to yoga. Physical movement is often a way of realigning and balancing the chakras. So there are specific movements or specific asanas that you can do to balance out your root chakra or balance out your Sacral Chakra, which is great because it's kind of like all of these different hacks you can do to bring your mind, body, and spirit back in line. And that's why I think I loved it because when I encountered a lot of other systems or other approaches, it just all felt a bit ephemeral and like I couldn't grasp it. But there was something about chakras that really spoke to the budding engineer within me because I was like, wait, you can just hack yourself into alignment? This is great. [chuckles] CHAD: So this is something you do daily. NATALIE: Well, something I try to do daily. [chuckles] CHAD: Okay. I meant, is this something one does daily? [chuckles] NATALIE: Yeah. Ideally, yes. Because it's like anything else that we do, if you want to maintain a certain level of well-being or perhaps a certain level of fluency, let's say, for example, in a language whether that's a programming language or the spoken language, you need to practice it every day. And so, with chakras and aligning one's mind, body, and spirit, it feels as though the stakes are slightly higher when we're in the middle of a pandemic, and there's so much uncertainty, and all of our lives have kind of been exposed to so much change. But yes, daily is optimal. Daily is, at least at Harbour, the bare minimum. What are some things that you do every day to balance your mind, body, and spirit? You may be aligning your chakras without quite realizing that you are. CHAD: Yeah. So I run every day. And I've often described that as that's my meditation. So I find that that really does wonders for reducing my overall stress. I do it in the morning before starting my day. And so, I think it really sets the foundation on which the rest of the day is built for me. And it wasn't until I made the commitment to do it every day. And now I run long distance enough where I need to take a rest day once a week. But when I made the commitment to do it every day, it really did change my relationship with running. NATALIE: That's so interesting. I was thinking about Kazuo Ishiguro's what I think about when I'm running or something along those lines. He's written this great book. And I know several people who run and have spoken of its incredible meditative qualities. And I think that's a wonderful way of connecting with yourself or creating space to connect with yourself. I also wanted to touch upon something that I know that we tend to move towards or perhaps even a dichotomy: do we meditate to relieve stress, or do we meditate to get closer to our divinity? And so one of the things at Harbour that we try to do is we try to help folks shift from meditating to relieve stress to meditating to connect with one's divinity, and that way, the stress doesn't become as prominent a factor for which meditation is there to alleviate. CHAD: What do you mean by divinity in this case? NATALIE: Yeah, great question. Very controversial. [laughs] I mean, it's 2021, and the least cool thing you could possibly do in an engineering environment is talk about God and the divine. I think there is a really interesting choice point we're at as a collective where there is an increased awareness of consciousness. So there's a lot of language in at least the tech community, from my experience, whether you've got things like Burning Man or just a lot of products and offerings out there, which are there to raise your consciousness. One of the really tricky things about raising your consciousness...and in the chakra system, we do that through something that's called a kundalini awakening, which is where your consciousness does raise from the root chakra all the way to the crown. As your consciousness raises through the chakras, coming from the Indian tradition, what happens is your life force, your consciousness moves through your chakras, and each chakra it touches upon triggers a mini awakening. So, for example, as your life force is moving through your root chakra, anything that may have happened in your childhood, anytime that you may have experienced any aspect of material instability, let's say you lost your job or you had a partnership fall apart, or any time where you felt like your world completely crumbled, that will likely be triggered when you're going through that mini awakening in that root chakra. I mentioned divinity because it feels as though there are two paths we can go down. We can either go down the path of I am raising my consciousness. I am the master of my own destiny. I know what I am here to do in life, and I'm in control of my own awakening. Or we can go down another path which is far trickier, which is sort of saying, "At every point in every day, I choose to surrender to the wisdom that is far beyond me. And I'm going to trust the signals and the science that I receive that they are aligned with my highest good." One of these paths is more egoic, and the other one is more surrendered. That's not to say that we don't need an ego. But the ego can get into really tricky territory when you're doing this kind of alignment and awakening work, and it can really do a lot of harm. And I don't say that through judgment. I say that because I've been through the wringer with a lot of ego deaths. And so, one of the safest ways to mitigate that risk of the ego taking over is to surrender to something that is far more wise than you. Perhaps you don't resonate with the idea that there is only one creator, and that's fine. But perhaps just from a logical point of view, it does seem to make more sense to surrender to the fact that there's something that knows more than I do at any moment. CHAD: So this is some really big stuff. NATALIE: Oh yeah. CHAD: Before we get much further into it, I think for listeners who want to learn more or are interested in what they're hearing and want to give it a try, where do they do that? Where do they find Harbour? And what is it going to look like? NATALIE: Sure. So you can follow us at harbour.today online on our website also on Instagram. And I'd love to invite your listeners to try out our 30-day trial, where if you complete 30 days of your chakra daily check-in, you'll receive access to our platform with activities, reading prompts, and also different course materials for free for a whole year. And I know I'm probably giving this away to a lot of people because all the engineers I know are very disciplined, [laughs] and they'll do this 30-day streak like it's a GitHub streak. CHAD: [laughs] NATALIE: So I'm shooting myself in the foot a little bit. But I'm really keen to offer folks who are asking these questions who are thinking about what am I here to do? Is there more? How do I engage with literature that could help me ask these questions more deeply within myself? And the daily check-in and the learning platform is a really simple way to do that. CHAD: Great. That's great. I hope folks check it out. So, in addition to the daily check-in, you just gave some hints on what is actually on the platform. There are reading prompts and those sorts of things. Is there more than that as well available? NATALIE: Definitely. So we are launching a monthly course on October 6th, and then the next one will be in January when we come back from the break called Organic Cycles. And the purpose of this course is to help people who are thinking about launching something. So you may have a side project that you're thinking about launching or perhaps a hobby that you feel like you want to take up, or maybe you even want to become an entrepreneur full time. But you're a little bit overwhelmed by what might be involved by that. And so at Harbour, we're real big believers in cyclic, iterative, sustainable growth. And so, we use the moon cycle for our sprints. We use it for measuring our tasks. And in Organic Cycles, you will learn about the moon. You'll follow the Moon Phases. And let's say, for example, you want to start a new business selling socks. [laughs] On the new moon on October the sixth, you will join us, and you will tell us all about your sock business. And we'll listen, and we'll make a plan as other people in the cosmic plan. In the first quarter, we'll start thinking a little bit about why do you love socks so much? Where does that come from? And what are the small steps we can make together to help you grow your sock business within this moon cycle? Which is, of course, 28 days. On the full moon, we'll celebrate all the progress that you've made with your sock business. And together, we'll figure out the next steps. In the last quarter, we'll think about hmm, what were the experiments making the sock business so far that worked really well? What are the ones that didn't? Which ones would you like to take into the next cycle? And on the next new moon, we'll start all over again. And so it's very similar to an agile workflow, except you're learning about the moon. And the reason why I bel…

    Full show notes at the publisher

    396: Product Roadmaps Aren’t Dead; They Smell Oct 07, 2021
    Show notes

    Lindsey and Chad talk about product roadmaps. Are they dead? Lindsey and Chad think they just smell. We also say an emotional goodbye to Lindsey as she moves on to new adventures. We miss you! Buffer Transparent Product Roadmap Become a Sponsor of Giant Robots! Transcript: LINDSEY: 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, Lindsey Christensen. CHAD: And I'm your other host, Chad Pytel. LINDSEY: And today we're going to talk about product roadmaps. CHAD: Product roadmaps. [laughs] LINDSEY: Whoa. This is the topic. I feel like recently I've seen some thought pieces that product roadmaps are dead. So I'm curious if you think product roadmaps are dead. CHAD: No, I don't think that they're dead, but I want to make the distinction too. I've never believed in a public product roadmap because I think that sets you up for just disappointing everyone involved, your customer, yourselves. And I think that there's a balance to be struck there. Saying that product roadmaps don't have a place, to me, in my mind, is like saying planning, having plans doesn't have a place and that just doesn't ring true to me. I think you should plan out what you're going to be working on. But I'm sure we'll get more into it. I also believe things about not having big backlogs and not doing too much planning and that kind of thing. So it depends on what you mean by a product roadmap. LINDSEY: Well, yeah. I think that therein lies the issue. You can do it well, and you can also [laughs] run it into the ground. But you mentioned having it public and that being a bad idea. And I think at the core of product roadmaps is communication and alignment and getting all of your stakeholders on the same page about what you're building and why. So to me, I would think those stakeholders are the leadership team of the company, if this is a product company and product is the main business driver, the leadership of the company, the product team, of course, and engineering, sales, and marketing as well. Am I missing others? Clients, customers. CHAD: Right. Customers. LINDSEY: How do you feel about it? Does that count as the externally facing do not reveal? CHAD: Oh yeah, it does for me. So we've all seen the companies that say that they're going to do something and then in a best-case scenario, that becomes a deadline which was arbitrarily made in the first place that everyone is stressing out over, that sales is potentially making promises that are either going to need to be broken or are going to need to be super stressed over. And then in a worst-case scenario, you end up not delivering on that roadmap as you essentially promised. And you actually end up with disappointed customers. LINDSEY: So you would recommend not telling the customers about future features. CHAD: Yeah. I think there's a balance to be struck there. So certainly, if you know that you're working on something now like actively working on something and a customer were to ask you about that thing directly, I might say, "Yeah, we're working on that now, and we're excited about getting it out to you." But I have only [chuckles] ever been a part of when a team is saying, "Q3 of next year, six months, nine months down the road, this specific feature is going to make it to customers." That's a real recipe, in my experience, a real recipe for lots of people being either really disappointed in that not happening or really working unsustainably in order to hit that in the first place. It's really hard to plan software that far in advance. We just had the CEO of Dragon Innovation on the podcast. And I think that even then, you have to be careful with hardware, but at least with hardware or other kinds of businesses, it's a little bit easier to say, "Our goal is to have this incorporated in the product, or whatever, in the next revision of the hardware. And we expect to do that two years from now," or something like that. That's a little bit easier to put a bow around, I think. LINDSEY: Yeah. I was a part of a software company that got acquired by a hardware company. And all of a sudden, we were wrapped into these 5 to 10-year product roadmaps that were blowing all of our minds [laughs] and a very different fit than how we were used to working. CHAD: Yeah. It's worth noting that there are some companies that essentially go so far as to publish a Trello board of their roadmap. I don't know which ones they are. [chuckles] I have to find them. But even then, they're not necessarily making hard promises. And if you're committed to being transparent and publishing some roadmap to the public, the ways that I've seen it done best are working in themes. So you say, "Two quarters from now, our focus is going to be on reporting," or something like that. That is a little bit...because you're not making specific promises. You're just establishing a theme of what your focus is going to be on for that time. You can imagine you can still get yourself into a position where customers are putting all their hopes and dreams on what that's going to look like, and maybe your support staff or salespeople or whatever start to make promises about what's going to be delivered in that time. And then again, a bunch of people end up disappointed. LINDSEY: Yeah. I've also seen what I think to be the most successful roadmaps be based around themes. And I think it’s also…again, going back to that, the fact that it's, in addition, to actually delivering product and delivering good product, it's helping align your internal team around what you're doing. So to rally your whole team or your whole company around reporting is the next big thing that we're working on, and this is why. This is what we've heard from users, from our research. And this is the direction we're going in and then actually getting everyone working towards reporting in their own ways. Marketing can be working on content around reporting. Hopefully, sales is seeding the idea of maybe not promising around reporting as well. And that also really appeals to me as a marketer and as someone who's thinking often about how do we get folks moving in the same direction, speaking the same language and creating some momentum around something that can differentiate us, get people excited about what we're doing? Then hopefully, it's also strategically valuable to the company adding a new feature or entirely a new product. You're expanding your offering and maybe even your market reach. Who do you think are the most important folks within the company to be driving the product roadmap? Who owns the product roadmap? CHAD: Well, [laughs] so if you have a company that has a roadmap...I'm getting distracted by the premise here. Let's just come back to that a bit. Momentum is key. You used the word momentum. And if you're feeling the need to plan things out or to gain a sense of clarity on your team about what's going to be done, and what's important, and you need to do a long-term roadmap in order to do that, that to me does point to it's sort of a smell. That's what we do when there's a code problem. We say it's a code smell. It points to if you had a team that was continually delivering value to your customers, to your users, and that you had a team where when sales, or marketing, or someone learned something about what will be valuable to customers and it's validated that it's valuable, and it gets put into the design and development process, and it comes out relatively soon, there's no need for a product roadmap. Or I should say people don't feel the need for a product roadmap as much because they have high confidence that user needs are going to be met in a tight feedback cycle and that there's not a loss of momentum. And things going into the system are coming out in a week, two weeks, three weeks. Even four weeks, you can maintain that sense of momentum of we understood that this was important. We validated that it was. It went into the system, and it came out the other side, and it's in the hands of users. It's only when that starts to break down that stakeholders start to say, "We need to plan. We need a roadmap," because they lack the confidence that putting things into the system they're going to see them come out the other side in a way that maintains momentum. LINDSEY: Does that depend on the size of the company? CHAD: Well, ideally, even companies of large size are able to do that, but we all know that that's difficult. It may be that most companies just can't do that. And when that's the case, you have that breakdown. You have that lack of confidence. You have a system where you aren't putting things in and quickly seeing them come out the other side. And so that's where something like a product roadmap you start to say we need that in place. And I think that that's why it often happens as teams get bigger and as companies get more complex. LINDSEY: Interesting. So product roadmaps are not dead, but roadmap can be a smell. CHAD: Yes. [chuckles] Yeah, that's what I would say. That's my opinion. LINDSEY: Who owns that smell? CHAD: So now to get back to who owns the product roadmap, if your customers aren't the ones driving what's on the roadmap, then something is fundamentally broken. At the end of the day, the real owners of the product roadmap, even though they probably shouldn't see it, are the users, the customers. But I don't think that's the question you were asking. Who decides what's on the roadmap? It's got to be the people who are closest to hearing customers and who have the vision for what the product is supposed to be. So that will often be the company leadership, the CEO, the chief product officer, something like that combined with people who are talking with customers. LINDSEY: So on the opposite end of the spectrum, if it's a big company, maybe it's a little bit harder to operate without the roadmap. If you're a really small and young company, let's say, and you already have a roadmap, is that too much? CHAD: Well, this is a podcast, so we can have opinions. I would say [laughs] growth opinion, high-level position, yeah, you should probably not have that roadmap. Now the devil is in the details. What is the roadmap? Is it high-level themes? Is it I'm building this idea, and I'm a visionary about what this product is going to be, and I've laid out in broad strokes...we've done an initial version, a minimum viable product, and we have a vision for where we're going over the next year or two? There's a way to do that which doesn't then convert into this rigid product roadmap. And I think that that's what people who say product roadmaps are dead and you shouldn't be doing them; that’s what they're pushing against is that really rigid expectation setting system where promises get made and then broken. LINDSEY: Right and promising especially deadlines far out into the future. CHAD: And they also understand or believe that if you have a product roadmap, it potentially puts you in a position where you stop listening to customers because you say, "In six months, this is the thing that we're going to be working on." And then you get there, and you just work on it, and you deliver it without having learned along the way that the next most important thing might be something completely different. And so that's another risk with product roadmaps is you start working to the roadmap instead of working to what your users are telling you. So at that company, I'm not surprised to hear that it was a 5-year, 10-year thing, and then it's based off of a thing, Was it really concrete, or was it more sort of vision stuff? LINDSEY: It was very concrete, I would say. CHAD: Yeah. [laughs] LINDSEY: And it's interesting because a lot of it was around trying to be first to market with cutting edge technologies. And on the hardware side, there was also R&D and multiple scientific teams working on specific things. And actually, to get more concrete, I think I can share without giving specifics. So it was 3D printing, and there's like an arms race in 3D printing to be able to print with new materials. So there are multiple teams working on trying to figure out how to print with new materials. And then we had these really long-term product roadmaps that were like by this year; we’re going to have gone to market with it and using that as a way to stay ahead of the competition basically. CHAD: I can imagine that from a business perspective, you're looking at that situation, and you say...and this is true both in science and in software. But from a business perspective, it's saying, "If we don't have this deadline in place, then we have a research project that's just going to go on. We need this timeline, this deadline to hold everyone accountable to what a goal is and to make sure that we're bringing new products to market in that timeframe." And then the scientists are probably saying, "We have no idea. It's completely arbitrary. We think that we could do this, but what happens when we don't? What happens when we don't have something?" A lot of times, I make an analogy between science and even software development and art because it is a creative process. It's all in our heads, and we're just coming up with it. You can say, "I need to have the book," or "I need to have this painting finished by this time." But it's very difficult to then ensure that that is actually going to happen at the creative level of saying, "I'm proud of this work, or it's good." It's hard to do that. LINDSEY: Yeah, and I think there was an element too of either we will figure it out, or we will acquire whoever figures it out. And then there's a separate team that's off trying to suss out who's figuring it out and what are they willing to be bought for? [laughs] CHAD: Right. And maybe from a business perspective, a lot of that makes sense. And you have to balance all of those things in order to try to be successful from a business perspective. LINDSEY: Yeah. It's interesting on the hardware side, too, especially as you do get closer to actually launching. It can be very waterfall-esque working towards launch because there are so many dependencies in order to get the thing built and shipped and launched on time. CHAD: I found a Quora thread about companies that have made their roadmap public. LINDSEY: Did any do it successfully? CHAD: [laughs] LINDSEY: I've only seen nightmare stories. Like, let this be a lesson. Here's a company that made their roadmap public, and within weeks they were disappointing people. [laughs] CHAD: I think that it's tempting, you know, and I think we should just do it. Part of the benefit of not having a roadmap that people say is that it allows not only the flexibility for what you're going to do to change based on what you learn. But the other is it offers you the opportunity to surprise and delight customers. And it allows you not to say, "This thing is six months away," but to say, "Here it is now." And one of the best examples of that that I think we're all familiar with is Apple. Apple doesn't typically pre-announce products that far in advance. And they're even a hardware company. They're clearly working on things yea…

    Full show notes at the publisher

    395: Energy, Perspective, Priorities, and Intention with Jen Dary of Plucky Sep 30, 2021
    Show notes

    Chad talks to Leadership Coach and Founder of Plucky, Jen Dary, about working with individuals and companies to create healthy dynamics at work. In fact, Plucky just released a new product that aids in doing just that! Manager Weeklies are notebooks designed to help leaders intentionally set up their weeks and track progress. It includes tips and tricks, including useful 1:1 tools. Each notebook is designed to last one quarter. Follow Jen Dary on Twitter or LinkedIn Plucky Manager Weeklies info & order link Newsletter: beplucky.com/newsletter Become a Sponsor of Giant Robots! Transcript: 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 Jen Dary, founder of Plucky. Jen, welcome back to the podcast. JEN: Thank you. My third time. Three time's a charm. I feel very lucky. CHAD: There aren't many people who have been on the podcast as guests three or more times. So you're in an ever-increasing select group of returning guests. JEN: Thank you. I feel like it's maybe because the Tokyo Olympics have just started, but I feel competitive and ready to take on this third session. CHAD: [laughs] So the last time you were on was October 28th, 2019 is when the episode came out. JEN: Millennia ago. CHAD: Not quite two years ago, but yeah, also a millennia ago. And that was Episode 342 so if people want to go back and take a listen to that. And then before that, you were on Episode 270, which I actually don't even know the date of. It was even longer. So welcome back. You are celebrating the eighth anniversary of Plucky. JEN: I know. I don't really think of it in these ways because I don't have an MBA, or I didn't come from a business background or anything. But definitely when I hit five years, I feel like my husband said something about that. He was like, "Honey, you should be really proud. Not a lot of businesses make it five years." And that was not really on my mind. But now that Plucky is eight, I feel like oh man, I'm just so happy to talk about how businesses evolve and how what you thought it was going to be in year one was different than year three, was different than year five, and of course, it's different than year eight. So we're eight years in, but nothing's the same, and everything's the same. I'm sure you've experienced that too. CHAD: It was actually the eighth year going into the ninth year mark that we at thoughtbot started to make big changes. And it was that idea of coming up on a decade. It started to feel like, wow, there's real momentum here. And instead of thinking about what the next year looks like, what does the next decade look like? And are we the kind of company that is going to last 20 years? And that put us in a different mindset. And I started to think about the impact we were having and the legacy that we would have. And was it big enough for the size of the company that we had? JEN: How old is thoughtbot right now? CHAD: We just celebrated our 18th anniversary. JEN: Oh my gosh. All right. Well, maybe at the very end, you can give me your best wisdom for the ninth year. [laughter] CHAD: Oh jeez. Okay. [chuckles] JEN: No presh, but tuck that in the back of your brain. CHAD: Yeah, get some sleep. That's my best advice. JEN: [laughs] Great. CHAD: That would be great. We can come back to that. JEN: Cool. CHAD: So obviously, it's been a big two years since we last talked. I'm sure a lot has progressed in Plucky. How have things changed? JEN: Well, what's funny is that the two years spread that we're talking about or 18 months or whatever it is, for the most part, overlaps with COVID so far. So by the end of 2019, things were cooking, and everything is good. And even, personally speaking, my youngest son would be entering kindergarten in the fall of 2020. Again, as a business owner, a mom, all those things I was sort of at the end of 2019 hot, so good. And then I was anticipating 2020 to be continued pretty much the same as is. Like, we would keep training managers. I would keep traveling. All that would get easier because the kids are getting bigger, then my kid would go to kindergarten. And I was also finishing a book about...I can't remember if we talked about this before, but I was really sick in 2016. I had a brain tumor diagnosis, and I'm okay now. It was benign. I had this memoir that was eh, I don't know, maybe two-thirds done. All that was the plan for 2020, Chad. And I'm sure this is shocking news to you, but none of it happened, including freaking kindergarten, obviously in person. So on the business side of things, I kept everything stable as best as I could. So coaching kept going because coaching has always been remote. We have some products, and we kept shipping those out as best we could. At the very beginning of COVID, when everybody thought it was this three, four-week hiatus from real life, I recorded a story every day. Because I was like, what can I do for all the world that's working? So I recorded a storytime for Plucky with my kids. And I put it out on social media so that working parents could have another 15 minutes of distraction for their kids. That's how cute I was back then. [laughter] After one month of that, I was like, I need somebody to read stories to my kids. Yikes. CHAD: Yeah. [laughs] JEN: So the big thing that changed was that our manager trainings in person obviously I had to cancel those. So I transitioned from in-person to virtual events, and that has continued. And as of this recording, end of July, I was thinking that our November event this year…it's the 20th cohort of So Now You're a Manager. I was going to have it in person. And just last week, I pulled the plug on that. And I was like, no, we're going to stay virtual a little bit longer because I don't know how to predict what the hell is coming. So again, that sort of stabilizing, right? Like, okay, well, now I know how to do the virtual. That will be the stable choice this year, which is weird to say, but true. CHAD: Yeah. So you just gave a great organic listing of the things that Plucky does, and a big part of that was that in-person So Now You're a Manager training, which, if people remember from the previous episodes, new managers at thoughtbot have attended over the years. It's a really great training for people who become managers. So what was transitioning that to remote like? Because you'd only ever done it in person before, right? JEN: Yeah, totally. The first 11 cohorts were in person, and then we got to 12, and that was supposed to happen in March in Atlanta. We canceled that, and it wasn't until June that we had the 12th, and that was the first virtual one. And to say that I needed to go through stages of grief is probably pretty accurate. [chuckles] My energy in person is so a thing, like a tool of mine and just pulling people together, and making safe space for conversations and all that jazz. So I was like, what the hell is that going to be like on Zoom? And meanwhile, remember I'm watching my first grader go through the shenanigans of Zoom for the end of that year. And I'm like, oh my God, how am I possibly going to get grown-ups on this and paying attention and not being distracted? So a couple of things, I will say number one is I definitely interviewed four or five people in the industry who are good at virtual events, and I tried to get their deepest wisdom about it. The second thing is that I made the cohorts smaller. So in person, we have around 20 to 22 max, and in virtual, we do 10 to 12 max. And so that got a lot smaller. Also, instead of being two days back to back, I broke it into three half days which is just a different ask. And I wasn't sure if people would bite at that. I tried to mimic it after how some people do an MBA on the side. So then they go to work, and they practice the stuff they're learning at the MBA. And so that has been my thought like, okay, you'll be with me basically for a month. We'll have three half days together, usually on a Friday. And then you're practicing in the meantime. So between the times I see you, you're improving your listening skills. You're coming back with anecdotes about hires or tough conversations or whatever. So I won't say that's like a silver lining, but it's just a different beast. And the first day I did it, I mean, I'm telling you, I was on the bathroom floor on my knees like, don't let the internet go out. CHAD: [laughs] JEN: I was so scared. I don't know why looking back. I'm in tech, but I'm not technical. It's my husband who helps me set up a monitor and whatnot. Oh God, I was so nervous. And I just thought, shit, this is the thing I can't problem-solve. If the internet goes out, I don't know what to do, but if someone's upset, I can help them. So it just brought all of my skills in a different environment. And now I feel pretty good about it. I don't know if you found this with your distributed company overall, but I have worked very hard to make sure that it's a blend, of course, this digital experience, but also I use the mail. I use snail mail a lot. So attendees get a packet before we begin. They get a gift at the end, a graduation gift. And yeah, I feel like I've learned a lot about how to have a hand-in-hand experience of digital as well as a physical object that they can touch to make that experience more than just a screen. CHAD: Yeah, I think that's important. How did changing the format, reducing the class size, what business ramifications were there for that? JEN: Well, it's way less money. [chuckles] CHAD: Right. Okay, sorry. JEN: No. Oh my God. I want to be very real about these things, especially for people starting their businesses. It's way less money. And also if you think about it, everybody had already bought tickets to Atlanta, and then they had already started buying tickets to...I can't remember what the next one was going to be, New York, I think. So for a lot of the year, everything was, I'll say, comped, but that's not really what's going on. All of a sudden, the amount of seats that I thought I was selling for the year got reduced in about half, and much of that were already pre-bought tickets. So, as a line item, that was way lower. I also think I got...man, I haven't really said this transparently to anybody before, but I'll say it here. I got really scared about what to charge. Do you charge the same thing virtually than you do in person? And so I lowered it, I would say for a year. I lowered it by a couple of hundred dollars for each ticket because I didn't know what the market wanted. And also, I didn't know, oh God, were businesses closing? Were people getting prof dev budgets? Everybody was frozen for a good while. So I'm lucky that now today I'm back up to the same price that it had been before, but it's not as much income per event. And the other thing I'll say which affects money…but again, I want to be transparent for other folks who think about or currently run businesses. One great thing to come out of some of the social unrest of last year is that we now have an equity scholarship for So Now You're a Manager. So in every cohort, be that virtually or in person, I always reserve a seat for someone who's coming from an underrepresented group, so people apply. And that is something that I very happily said I will eat the cost of that ticket because it's important to me to have different voices in the room. And that has been a total awesome thing this year. That just started in January of 2021, but that's something really great that came out of last year. CHAD: Yeah. What did you find that customers wanted, and did it change over time? Was there an appetite for it to be remote, or was there resistance to it? JEN: I think at first people were overwhelmed and didn't want it. That's why I held it from March until June until I thought people were ready. I can tell you categorically that I've had the lowest percentage of parents attend of all time because, let's be real, who wants another kind of obligation? Or also, parents during this time, especially with young children, were not in that growth space necessarily for work because there was so much to keep afloat. So other than the three half days, I also have this optional hour that I throw in just if people can come; there’s this extra exercise that didn't fit in from the original curriculum. And I don't think I've had one parent, maybe one, come across all those cohorts that have been virtual to that. So the optional stuff I see parents opting out of. That said, I saw more folks who maybe either live alone or maybe have a roommate but who are pre-family or some people won't have families but someone who was socially like, "It was so hard and tiring last year." And that sort of swung back around towards the summer and end of summer. I saw much more interest there because I think people were really lonely. CHAD: Yeah. And I also think, at least for me personally and for thoughtbot, that was when the thinking definitely shifted that this wasn't going to be going away anytime soon. And so we came to terms with that and started to then make much more long-term plans and permanent changes. JEN: I think it was also in the...I want to say like early fall when Twitter announced they'd be remote. Like, they have an office, but they wouldn't oblige anyone to ever come back again. And whenever that decision was made, there were a couple of other companies...At that point, I was still living in the Bay Area, and there were a couple of other companies that made similar suggestions. And so again, to your point, there was a revisioning of what the next phase was like or at least what to expect. And so, I think people weren't holding out to go back to normal. It was like, what's the new normal? CHAD: Yeah. So when we first shut down offices and went remote, we were giving updates every two weeks, and then it changed to every month. And then it would be like, "There's really no change. We're going to give another update in April." And then April was, "We'll give another update in May." And when it came to June, we just said, "We're planning on being in this mode for at least the end of the year. Let's start all acting and make this sustainable." So that is when our thinking changed too. JEN: Did you feel like with your CEOness and business responsibility over there...what kept you grounded for all that thing? Because obviously every time you make that announcement or regardless of whether that's in person or just...I don't even know– retention or whatever it is. It feels like you're just building strategy on freaking quicksand. CHAD: It wasn't easy. You feel responsible for everybody's well-being, both financially and everything else. And so the lack of stability…you want to provide it in an unstable world. You want to say, "Well, at least you shouldn't have to worry about this. Let’s provide…" but it was impossible to do. And I'm much more comfortable with uncertainty. I think there's a spectrum of comfortableness with uncertainty, and I'm pretty far on one end of it, and even I was struggling. Same thing with like I'm very much on the spectrum of not having to worry about anxiety or anything like that, and even I was feeling it. And so I was just like...at one point I said to I think it was Diana or wha…

    Full show notes at the publisher

    394: Creating a Remote Culture That Thrives May 27, 2021
    Show notes

    Chad and Lindsey talk about how the pandemic has changed "normal" remote work and how thoughtbot has dealt with the transition from being majoritively in-person to fully remote, plus the impact it's had on both employees and clients. Become a Sponsor of Giant Robots! Transcript: 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. LINDSEY: And I’m your other host, Lindsey Christensen. We’re back. Chad, I've only seen you pixelated for over a year now. CHAD: I know. LINDSEY: Can you believe it? CHAD: It's hard to believe. I haven't seen anybody that I work with [laughs] not pixelated for over a year now. LINDSEY: It seems normal now. CHAD: Yeah, it seems normal, except when you think about it, and you realize how long it's been. We're going to talk about remote work today, and I think that that's something to keep in mind, which is what we're doing now isn't normal remote work. We can make the best of it and that kind of thing, but it's obviously different than normal remote work when you can actually have a social life outside of work and meet people and get together in person to kick off new projects or to be like, “Let's have a retreat or whatever.” So right off the top, we should acknowledge that we're not in this normal period, and this isn't necessarily normal remote work. LINDSEY: Right. Which is a good thing, I guess, or the optimist in me says remote work can be way better than it is right now because this is quarantining work. [chuckles] CHAD: Right. So for those who don't know, thoughtbot made the decision to go remote-first work from anywhere. And we touched on it in the previous two episodes a little bit, and that's what we're going to be talking about today. And I think that that's one of the things that made us confident in the direction was that things aren't great now, but they're certainly not bad. And the majority of the team felt good about what was happening now, even given all of the downsides. It gave us the confidence to look ahead and say, “Can this be even better, and will it be okay?” And I think that's part of what gave us the confidence to move forward. LINDSEY: I saw this interesting stat, and this was actually from a while ago, last July 2020. Gartner did a survey of company leaders, and 80% plan to allow employees to work remotely, at least part of the time after the pandemic, and 47% will allow people to work full-time from home, which is even a bigger percentage than I anticipated. But I think it speaks to the major change that everyone's seeing. We've all learned that remote work can work. I saw another stat that was, I think, no companies are reporting a reduction in productivity because of remote work, and in 27% of cases, companies feel like they're being even more productive. CHAD: We didn't not do this before because we didn't think it would be productive on a day-to-day basis or that we didn't believe in the ability to work remotely working. There were a couple of important points that caused us to choose the direction we did; the first one being we went through a period of time where we were a hybrid remote or about half the team was remote, and the other half was working in an office in Boston. And it felt hard and mediocre and something we couldn't -- It wasn't worth the amount of effort we would need to invest in making that work well. It just didn't seem worth it. And so we made the decision to -- And I think this is the way thoughtbot works like we've got to make intentional decisions in a lot of things that we do and half measures don't really satisfy us over the long-term. And so there was this feeling back then of we either need to decide to go completely remote, or we need to all be in person. And because we work locally with clients, that pushed us in the direction of well, we really like working with local clients face-to-face. We like how that feels, and it feels like something that's going to be enjoyable and fulfilling, and sustainable over the long term. So let's commit to that. And I think that that's one of the reasons why we've been successful in this transition is because, at the same time, we no longer had the client constraints of clients asking us to be in person with them or wanting to work with them in person, that was just completely off the table. LINDSEY: That's interesting. I think I hadn't really fully thought about that element which was need or perceived need from the client to be side-by-side with us. CHAD: Yeah. Once that was off the table, it allowed us to be freed up to make an independent decision, probably more confident in that decision because going through a period where we could show clients that it could work, I'm more confident now that when clients can be in person again, that they will be more open to working with us remotely. And I'm sure some portion of them won't be, but we'll find other clients in that time period. [laughter] LINDSEY: I think another thing that helped us in that transition was we weren't fully remote, but we were remote in a lot of regards. So we had six different studios around the world who collaborated together, worked on the same projects and the same teams. And we had a really good starting point for how we collaborated online, whether that's in actual video meetings or doing asynchronous work or project management all the way through to client work. Not everyone was in the city of the client that they were collaborating with. CHAD: Yeah. And all of the corporate team, the operations, marketing, all that stuff was already really a distributed team. It was primarily the design and development that fell back on being in person the most often. LINDSEY: And I would say we also had a pretty flexible work from home policy too. So if folks felt like they were going to be more productive from home a certain day or were having a delivery or whatever those life things are, we trust that they know what's best for them and best for the client and allow folks to make decisions about where they're working. CHAD: The way that we worded it before was that temporary remote working was always okay. And that could be I'm going somewhere for two months; even that was okay. And the opposite of that is what we said wasn't okay, which wasn’t permanently remote. And the big difference now is that we said permanently remote is okay. And walking back through the transition, this was something that has been an ongoing conversation at thoughtbot for a while. It was pretty early on in the pandemic that we said that people needed to start to move out of the places that we had studios. And I think that that was the first important step that we took as a company to make sure that we were supporting everybody in what they needed to do for life reasons saying, “If you need to move outside of a place where you would normally be based, do it. We'll continue to support that.” And then about 20 people, [laughs] a little less than 100 moved over the course of the next six months or so. And once that happened, that's a pretty significant portion of the team no longer being based where we have offices, and that sort of sealed the deal. LINDSEY: I didn't know that number. CHAD: I think it's less than 20. I think it's like 17 or something like that. LINDSEY: So it probably works out to about 20% moved to where there weren't offices. And do you have an idea how far spread out everyone is now? CHAD: I think most people who moved significantly moved to be closer to family or back where they were originally from. I think that was the driving factor. So it's places like Texas, different parts of Texas, Arizona, that kind of thing. And then people bought houses to get out of the city and that kind of thing as well, particularly New York City was -- I think a lot of the people in New York City are the ones who moved as well. LINDSEY: So, how would you describe our remote structure now? CHAD: I think there are a couple of important things like, we're specifically calling it work from anywhere, not work from home. Obviously, we all need to be in our homes now, but long-term, there's no reason why if the home isn't comfortable for somebody that they will work somewhere else, and anywhere also means geography. And we're not even completely shutting the door on eventually having small co-working spaces or small offices where people can get together and work in person. It's just not what we have right now and not what we're specifically planning on in the short term. So I think that's the base level when I think about the important parts of the structure is what are we actually saying, or what are we actually doing? And then the next important aspect we took into account was okay; one of the things that influenced the way that we were working before, which was a local team working with primarily other people in your office was it's pretty annoying, and it does affect productivity to be waiting significantly across time zones for people that you're supposed to be collaborating with. And so we ended up splitting the company by time zone into what we’re calling Launch Pad 1 and Launch Pad 2. And Launch Pad 1 is all of the Americas, and Launch Pad 2 two is Europe, Middle East, and Africa. It's interesting because that's actually only about three maybe four times zones different at the extremes. All of the Americas, when you do it out, it's a lot of time zones. It's ten timezones, but the reality is we don't have anybody in Hawaii or Alaska yet, so we're okay with that.[chuckles] But it's something that may need to be revisited in the future if we really start to hire people remotely in those extremes of the time zone. LINDSEY: So the geographies are really time zone-based, which is an interesting note. And then I'm sure some folks are also interested in logistics, especially now that you're heading up operations. What does that mean, or what are the big hurdles when you do have people spread across countries, let alone states? CHAD: So let's break it down in terms of employment stuff, and then we'll talk about operations like how we run things. We're not leading the charge in this. Other companies have done it before. And so we're taking a lot of cues from companies like GitLab and Buffer about how they do things. We've had international employees for a little while off, and on or international team members, I should say. And what we've historically leaned on for that is having them as independent contractors. And it's pretty common for them to create their own company that they're then using, and they're working within, and they're paying local taxes, and they're invoicing us for the time. And in a lot of countries, their laws are conducive to that. But strictly speaking, it's not okay to do that in every country. And if you were to get audited and someone were to look at the relationship you have with that person and their laws are similar to the U.S., they might declare that person an employee, and you're responsible for the taxes and everything, not them. Operating at the size we are, to be perfectly honest, at the size, we are with a handful of people, it’s a gray area. Like, some places it's okay, some places it's not quite okay, but it's only a handful of people and everything. You can get away with that without doing a lot of research into each specific country, whether it's okay or not, particularly if you make it the responsibility of the people, and you set up contractor agreements, and you set things up that way. So that's a pretty common way of operating. But as you start to grow and formalize it more and the numbers of people that you're working with as international contractors increases, the pressure is going to mount to say, “We have to get out of this gray area; otherwise, some country or someone could get in trouble,” not even us, but potentially the team member. If they were to get audited and it's not quite up to snuff, they could be held for some employment taxes or something like that. So we want to avoid that. We don't want to create a burden on people. And so there's really two ways of going about it; one is to create local entities in each of the countries where you want to hire somebody. So you create your own local company. That company employs them and pays the local taxes and employment taxes, and all that stuff and everything is fully set up and official, and we've done that before. We did that in Sweden when we had the studio in Stockholm, and that's how we work in the UK. The overhead of doing that is really high, especially --It’s okay when we were in Sweden and the UK and the U.S. But as we look ahead and we say, “We're going to have ten then maybe 20 in different countries,” the overhead of that is really high. So the alternative is to work with a company that does that for you. So there are companies they're called PEOs professional employment organizations or international PEOs. And what they do is they create companies in all of the countries that they want to operate in, and then they employ the people as real full employees there. And they do all the books, and they pay all the taxes and everything. And they make sure that everything is done correctly for each individual country. And then they invoice you for the employee's salary, the taxes, and then an administration fee. And it's typically on the order of $250 to $600 a month per person. And so that's the direction we're going to go in as we expand this and we do it. That's the direction we'll go in because we've been through what it's like to create that overhead of the individual entities in each country. And it might make sense if we were saying we're going to open an office or hire significantly in this one country and build a whole team of 20 people in one country, but that's not what we were planning on doing. We may only have one or two people in each of the countries that we end up hiring someone in. So it doesn't make sense to have that overhead. And there are a few different companies out there, and not to plug them, we're not using them yet, but the interesting one that's on my radar is remote.com which was started by the person at GitLab that did this all for them and learned a ton about it and then left GitLab and started remote.com as a way to make that more accessible and modern for other companies. A lot of the other companies that do this tend to be very large, and they've been around for a long time, which typically means things aren't really done online so much; it's a lot of paper. And remote.com it's a website you sign up for. You could just enter the people in, and things happen automatically. And so that's why that's on my radar. LINDSEY: They're probably getting a lot of business these days. CHAD: Yes. And they have a lot of countries that they're expanding to over the next year or so. LINDSEY: How many countries do we have people in now? CHAD: That's a good question. I don't know [laughs] United States, UK, and Uruguay right now. I think those are the only ones. But we have two people who are moving, one to Canada, one to Austria. So those are the next two that are on the horizon. And we're actively hiring, so we just opened a bunch of positions. And I know that a lot of people applying to t…

    Full show notes at the publisher

    393: Reaffirming Values and Taking thoughtbot Remote May 20, 2021
    Show notes

    Chad and Lindsey take listeners behind the scenes and go deep into the nitty-gritty of recent thoughtbot company changes driven by the pandemic and the organization's need (and desire!) to go fully remote – all while reaffirming and revisiting the organization's values, mission, and purpose as part of the process. Become a Sponsor of Giant Robots! Transcript: CHAD PYTEL: 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. LINDSEY CHRISTENSEN: And I'm your other host, Lindsey Christensen. And we're back. Thanks for tuning in. CHAD: We've missed you. LINDSEY: Yes. We’ve been kind of busy. CHAD: We've been busy, and we knew we were going to take a break after the last season. We didn't necessarily know for quite how long, and then a whole bunch of stuff happened, which we're going to tell you about today. From the last episode, you heard about the change to the thoughtbot CEO, and we alluded to some changes that we've made to the company. And we're going to talk about those today. LINDSEY: Yeah. And in true thoughtbot Giant Robots fashion, we’ll go behind the scenes and give you the nitty-gritty of why things happened and how it's going because it's all really interesting. CHAD: Yeah. I think on the surface, it's really easy to think about how maybe these changes have been entirely driven by the need to go remote or the desire to go remote. And the reality was that's an important part of it, but it really was so much more than that. Some of these changes that we've made are ones we've been talking about for a long time. And it wasn't until almost a year of operating in a different way that we said, “We need to make some of these changes in order to accommodate remote and working from anywhere.” And we fell back on a lot of other problems we needed to solve along the way. LINDSEY: So we actually decided to break out remote work into its own episode, which will be the next episode. And I'm sure it's going to come up today, but it's a whole other area of changes and focus, whereas some of the reorg changes that we just underwent solved a lot or are trying to solve a number of challenges that we've been working on over the years. So I guess to start off, before we reorganized, how did we function? And that was largely geographically based. CHAD: Yeah. And the geographic basis means that we had a studio in a city, and in that studio, we offered the complete thoughtbot services. And that was driven by this idea back in 2012 when we started to expand. Prior to that, we really held the company to less than 30 people. And we were primarily a group of people all in one location working together, and we were all of what thoughtbot was. And we really liked that. We liked the structure. But people wanted to move and live somewhere else. And our purpose is that we believe that there's a better way to work. And we want to share it with as many people as possible, although we've revised that purpose now as part of this process. And so I really remember the day we were having a company meeting, and someone stood up and said, “If we really believe we have a better way to work, why are we not trying to bring it to more people? Why are we losing these great team members only because they want to live somewhere else?” But we also really liked the small, close-knit team of people who worked closely together on client work. We had done some client projects that were split across teams and across time zones and that kind of stuff. And it just didn't feel as good as we wanted it to feel, especially because it was hybrid. And so we said, “We know exactly what a great thoughtbot looks like. Instead of trying to expand what that great thoughtbot looks like, let's try to replicate it instead.” And so when someone wanted to move to a new city, we said, “That’s great.” We looked at the market in the city that they were moving to and said, “Let's grow another thoughtbot around them and use that as the starting point for a new thoughtbot studio that would be a full design and development team that offers and works with all the different kinds of clients that we work with.” And that was the model which brought us to being in six cities in the UK and in the U.S. and about 100 people working with a whole bunch of clients every year across those. But for the individual person working at thoughtbot, individual designer or developer, it felt very much like thoughtbot had always felt, which was you were working with a team of three or four other people directly on that client. Oftentimes, the client would be in the same city as you. And when we could meet face-to-face with people, they'd be working in our office, and we'd be working really closely with them. LINDSEY: Another interesting element of that structure was the marketing, and community was also very locally based, so engaging in and hosting local meetups. Actually, all of our offices -- We had offices, first of all, in amazing locations in all of these tech hub cities, and all the offices additionally had space for specifically events and community type of activities. And we thought a lot about nurturing local community, creating local partnerships. Obviously, we're thinking a lot about the hiring pool, and nurturing potential future hires in those cities as well. CHAD: Yeah, and that's what we had done in Boston where we got started, and it's very fulfilling to be part of your local community. And we wanted to embrace that as we grew. And for a good while, it worked pretty well. We were certainly able to grow quickly once we decided to do it. A lot of people who listened to the podcast a long time will recognize that we actually at one point had ten cities, some of which were pretty established and other ones which we were expanding into. And we learned a lot along the way about how much harder it is to build a local business than we originally were anticipating it would be. One of the things that we learned, and I've talked about this on the podcast in the past, is that with our reputation in the design and development community, we could often go into a major city and have a great first year because there was a lot of pent up demand for people who wanted to work with us, work at the company and as our clients. And that really led us astray in the beginning because we would go into -- We were expanding in three or four cities in the same year, and they were all super successful. So we were hiring teams to do all the work that we had. What we weren't doing was all the legwork we needed to do to build a sustainable local business. And so after the first batch of clients or the first batch and a half of clients we were done working with, we didn't have a sustainable pipeline of new local clients coming in. And so we learned a lot about how much we actually need to do when going into a new city to not only have that great first year but to have a great fifth year. And so we had a few failures where we had to close some studios just because we couldn't afford to operate them profitably, and that was pretty painful. I forget the episode numbers where we talked about it in the past, but we have. You can go back and listen to it. We can link them in the show notes. LINDSEY: In addition to having the designers and the developers in the local studios, at least in recent years, we also had the structure that each city studio had a managing director. And a lot of those managing directors actually came from design and development themselves, but they were in charge of everything local including, and especially the sale, so finding new clients, onboarding them, the actual profitability of their studio, hiring. And again, as you mentioned, that was across all kinds of clients, all kinds of projects, but primarily locally based. CHAD: And once we realized what it was going to take to build local businesses and make them successful, we refined that managing director position a lot. It wasn't one that we necessarily had in every studio, and so adding it or, in some cases, making the difficult decision to swap out the person in that with someone. Now that we understood what was necessary, making sure that someone in that position actually wanted that job and could do it. And that has been the journey we've been on; I would say for the past three or four years of making those changes, figuring it out so that when it was working well, each of the studios could work really well. And we've made a lot of progress with that. But one of the problems we had, so we have all the individual studios, and then we have the corporate-level people which are myself and you, marketing people, operations supporting all of the studios. And one of the things that we've struggled with over the years is being consistently profitable as we've grown or primarily operating break-even, which historically we were very comfortable doing because the whole leadership and shareholder of thoughtbot and ownership all worked here. We care a lot about paying people as much as we can possibly do and having the greatest benefits we possibly can while staying sustainable. And so it wasn't an issue. We're not running the company to generate lots of profits that then go to some investors or shareholders. So operating breakeven wasn't historically a problem, where it started to become a problem is as we grew and grew, the numbers became large enough that when things didn't go like we were expecting and we were managing to break even, then we would be very unprofitable very quickly if something didn't go the way that we were expecting, and it started to put the company at risk. So we started to focus more on profitability. And one of the things that was hurting profitability is that we were maintaining these small teams with offices, and just the overhead of a small team across many different geographies added overhead, which made it harder to be profitable because we needed to do everything in each individual location. LINDSEY: Right. So now, really getting into those big challenges that were pressuring us to rethink how we operate, profitability and margin was a big one, which once you look at the breakdown in the numbers, the overhead of having the different studios was one. I think that also bleeds into the MDs have really challenging positions. They're responsible for a lot: they're responsible for the happiness and fulfillment of their teams; they're doing business development; they're doing client management; they're in charge of their entire revenue sheet. So that was another area that I think over time, we were consistently looking at; how do we improve this role? How do we make it so that folks can be successful here? CHAD: Well, you can imagine, too, that designers and developers at thoughtbot we were seeing a similar thing, which is in a lot of ways, thoughtbot is modeled around me and other early developers. And I would often tell people I really like a lot of variety. I like to be working on one client and have huge scaling problems and challenges that we’re working at and growing their business to a whole nother level. And I like rotating off of that. And I then like working with a startup where we’re building the first version of the product. And for some people, no doubt that is exciting and challenging but worth it. And same thing on the sales side for managing directors, like being able to know how to effectively communicate and sell to the needs of each of those different kinds of projects. It's totally doable, but it adds to a lot of effort and angst being spent on just always trying to do everything, both on the development side and the managing director side, and it's hard. And that was one of the challenges that we were hearing either explicitly, or in a lot of cases, I don't think people realized it was happening. Everyone at thoughtbot is amazing and is great and very high execution level and all that stuff. And when you start getting challenges or feedback about poor performance from a great performer, you start to question why is that? What's going on? And it's an unrealistic expectation to have someone work in as part of a large enterprise for six months and then next week have them working on a brand new startup MVP that's got to go to production in six weeks and necessarily expect them to on a dime be able to change their approach to managing that product and making sure that it's successful. And like you said, we want to put people in a position where they can be as successful as possible in everything that they do and having good people spin their wheels even if it's not a performance problem -- if there's a level of interest or excitement for one kind of client over another, we have a system of collecting feedback about what you want to work on and rating the incoming projects. But the primary determinator for what project you work on was which one was starting at the time your other project was ending; that was the primary determiner. So people effectively had no choice about the kind of project that they would work on. And that was a common complaint that we heard from people is that lack of control. LINDSEY: And even though it wasn't supposed to happen, I think people did have reputations for a specialty, and the managing directors or whoever was staffing a project would seek out certain folks for certain projects. So even though we'd like to think of everyone as being able to handle any kind of project, and at a basic level, they could for sure, people with specialties were sought out for things. So that was already happening organically. CHAD: And related but even going deeper on it, when we're maintaining small groups of people that are a complete replica of everything that is thoughtbot, and it's a group of 9 to 25 people, that ability to specialize or to have a career path that extends -- The company you're a part of feels like a 20-person company, and in a 20-person company, there's naturally not going to be tons of room for a big career ladder and lots of advancement or specialization. You will trend towards having a team of people that are more generalized and less hierarchical. LINDSEY: Were there any other big challenges that come to mind for you when we were going into, like, let's revisit how we're structured? CHAD: Well, there was one that touched on all of what we just talked about, and that was design and thoughtbot. And this is one thing that's super interesting. And I think I've talked about it on the show before. But we started from day one as a design and development company. We've always done design, and we've always had people on staff that did it. And one of the things that happened, though, is being the first consulting company in the world to switch to Ruby on Rails and being a big contributor to that community, and building a reputation through our open-source and through our blog and everything on the development side, that part of the business has grown. The development team is much larger than the design team. And a lot of people in the world view thoughtbot as oh, they're a Rails development company and really it wasn’t -- What we've always talked about is Rails is in service of the products that we want to design and build and creating great products. And so design has consistently been a challenge over the years as the reputation there isn't as big as on the development side. And so what we saw in the individual studios were each individual studio needed to have a certain number of des…

    Full show notes at the publisher

    392: Better Together with New CEO of thoughtbot, Diana Bald May 13, 2021
    Show notes

    Chad is joined by Diana Bald, the new CEO of thoughtbot, to discuss her background, the organizational changes to the leadership of the company, and the reasoning behind them. Diana on Twitter Become a Sponsor of Giant Robots! Transcript: CHAD PYTEL: 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 today, I'm joined by the new CEO of thoughtbot, Diana Bald. Thanks for joining me, Diana. DIANA BALD: Hi, Chad. This is so fun. This is so exciting. I've only done one podcast before this, so I'm excited. CHAD: Well, don't worry. You can still be CEO of thoughtbot even if you're not a podcaster. [laughter] DIANA: Okay, that's great to know. CHAD: So it's been several months now. So I want to go back and talk about how we arrived here. But I'm curious, how are you feeling now? What does it feel like? DIANA: It feels great. I think I'm getting more and more comfortable every day, which is amazing. And I think the year has gotten off to a great start, so that's helping me feel more comfortable as well. So far, so good. CHAD: So for folks who are listening, I'm sure they're wondering who are you? [chuckles] Let's give the audience a little peek into your background and how you arrived at thoughtbot, and the role you originally had. DIANA: Great. How far back do you want me to go? CHAD: As far as back as you're comfortable. DIANA: Okay. I actually was really interested in technology at a younger age. I put myself through undergrad and grad school while I was doing tech roles. I trained lawyers on how to move from the analog world into the digital world. That was one of my very first jobs at a law firm. And then, shortly after that, I did webmaster work when I was putting myself through MBA school. It was a very different world than it is now. This is way back when the internet was really just kicking off; it was 1998 to 2001, around that time. When I graduated from MBA school, I was recruited into Univision into their leadership pipeline, which was very much focused on business development. But my very first project there was web integration, integrating the univision.com with their TV and radio. That was when I started to move away from technology. I was there for ten years. I had a variety of different roles, a really fun job. I got to experience a lot of different roles, lived in a lot of different cities. I spent a lot of time in Philadelphia, where I actually launched a television station in Spanish, which was really fun. And then I came to New York. After Univision, I spent four years in the advertising and marketing world. I spent two years with IPG at ID Media, which was a direct marketing agency. And then two years at MDC Partners at an agency called TargetCast, which later became Assembly, which was more media buying and planning. And then, when I left there, I went to Liberty Mutual for three years. And at Liberty Mutual, I fell back in love with technology. I missed it. I was doing a lot of strategic partnership opportunities with really interesting companies that were doing brand new business models and disrupting insurance, and there was a lot of exposure to telematics and IoT. And it was just calling me back, and I was like, I got to get back to tech. And somehow, I don't recall exactly how, but I found you. You and I chatted, and then I fell in love with thoughtbot [chuckles], and then after that, the rest is history. CHAD: You joined us as the Managing Director of the New York City studio. I want to say that was a position we were advertising for, and you applied to it. DIANA: Yeah. CHAD: And one of the things that really stood out when I first met you and as we've got to know each other and work together is the variety of experience that you had because I've only ever done what I do, which has its own strengths. So the fact that I started freelancing web design and development in high school and have continued to do that now for 25 years is a strength, but it's also, aside from the jobs I had as a dishwasher or the checkout person at the grocery store, this is literally all I've done. And the variety of experience you have not only helps thoughtbot be better, but I also think it positions you well for our business. In consulting, you need to be unflappable in a lot of circumstances, and I think you're good at that. You're good at maintaining an even keel and talking with customers and dealing with difficult situations and that kind of thing. DIANA: In some ways, I'm envious that you have been able to stick with development the entire time; that’s really, really cool. But in other ways, I can see what you're talking about because I do feel like I have had a variety of roles and seen a lot of different situations. And every one of these situations has had their challenges. And they've all been generalist roles where I've dealt with clients, and then those clients had challenges in their respective industries. So I've really learned a lot about keeping things in perspective, if you will, more so than people who are in a role for a particular time and see that aspect of it. I'm seeing things from a bird's eye view much more often because maybe I've seen the situation in the past only it was in this industry, or I've seen this situation in the past, but it had these characters. And it's like I can carry that knowledge over to thoughtbot, which has been really helpful. CHAD: So the managing director role, I think I've described it on the show before, and it’s sort of the CEO of the individual studio. That’s the way that it works. You oversaw the individual studio, and you were responsible for business development and the whole P&L of the studio, the whole business. Going back to first joining thoughtbot, what was a surprise to you? DIANA: How comfortable I felt. [chuckles] I felt like, oh, I'm home. I felt like, oh, there you are. I've been looking for you all my life kind of feeling. I don't know how to explain it. It just felt really good. Like, okay, these are problems. I like these problems. Or this is really joyful. I felt like I was actually in my element for probably the first time in my career, although I've had some jobs where I felt pretty much in my comfort zone, but thoughtbot took it to a totally new level. And I don't know if it's thoughtbot, or the role, or the combination of the two, or maybe it's me where I am now in my life and just having had all these different jobs and experiences. Maybe it's all the above. CHAD: One of the interesting things that's been a journey for thoughtbot not only just with you but with several people is up until a few years ago, we hadn't, aside from some office managers or people operations, we hadn't had people in direct client-facing roles who are not designers and developers. And it comes from a place of fear and skepticism about that, historically for us, for me personally. And I don't think I was wrong per se; I was just misguided. And I've learned over the years that when you're afraid of something, there can be some truth in what you're afraid of, but you should let that fear guide you into making good decisions and not let it hold you back from doing anything. And that's what we were doing: we were so afraid of what adding non-designers and developers to the consulting side of the business would mean for us as designers and developers that we didn't do it at all, instead of trying to find people who would be a great fit, who would be great advocates for us, a great fit for the company. And once we figured out the recipe for doing that, I feel like not only did it make thoughtbot better and stronger on the business side, but it made thoughtbot better overall. One of the things we strive for is an inclusive, diverse environment, and that doesn't just mean the obvious things. It also means having different perspectives and experiences that a group can bring to the table that makes the results better and more enjoyable, and more fulfilling to work in. And I think that you've been successful in bringing that to the company, and it felt good and not only you but the other people that we've added in the managing director roles. And that kind of thing that brings that different experience and different skill sets to the table has made thoughtbot better, I think. So, thank you. DIANA: Thank you for letting us bring it to the table; not every place lets us do that. But you've set up a culture, to your credit, that I think brings the best out in people. And I think you've enabled that to happen, so thank you right back. [chuckles] CHAD: There's another angle to that, which has been on my mind, which is what we were doing in the past was basically forcing designers and developers to do some of those things and potentially setting them up to fail because it wasn't a strength, or it wasn't an area that they were actually interested in. They were just doing it out of love for thoughtbot or wanting to see us succeed. When you put people in a position where they're going to struggle or where they're going to not succeed, that's doing nobody a favor as well. And so that's in part been on my mind because as we've been reorganizing the company and everything, I think that's part of the lens at which we're looking at it: what can we do to make things easier to make us more successful as a team and as individuals in our day-to-day work, too? DIANA: I think that there's a lot there. I feel like in every designer; there is a business person because they're breaking things down. They're deconstructing constantly, and they're asking tons of questions that business people just naturally ask. And then developers are super creative, and they're problem solvers, and they do the same thing. I feel like it's a combination of art and science. Everybody's got their science part of it, the developers, designers, even people like me with a business development background. But then when you do enough of that thing, and you're meshed with the people who bring a complementary skill, then you're able to do the art side of it together that you wouldn't get solo, for instance. If you just put a bunch of business development people in a room together, it's very different than when you mix them up with a designer who brings that side of thinking and a developer who brings their thinking. I think together we're better than siloed. CHAD: So when it came to the actual transition and having you step into the role of CEO and move into the COO role, and I want to be relatively honest that it wasn't some grand plan that I executed over a period of a long time. And if that had been the case, I think we would have gone about it a little bit differently and certainly with more transparency for the rest of the thoughtbot team. For the listeners, the path there was that Matt Jankowski, a long-time COO and member of the leadership team at thoughtbot, was getting ready to move on. And that wasn't the only thing that was changing. Obviously, 2020 was a big year; it was a difficult year. And so the combination of all of those things and me looking at what does the leadership team at thoughtbot look like going forward? Who is going to fill Matt's responsibilities? That kind of thing, and really breaking down those roles and responsibilities and coming to the conclusion that the CEO role and particularly business development are inherently coupled at the company right now and that we have a lot of things we need to do in front of us and who is the best person to be able to do that? And feeling like it might not be me. And the things that I was going to be taking over from Matt operationally were in and of themselves a significant area. I love thoughtbot. I love helping it work better and being close to the client work. And now that we've built an incredible team of managing directors, that was another thing that was on my mind that I've built that team. I'm really proud of that team, and it's an awesome team. But who's going to be the better mentor and leader for that team going forward now that we've got a team of experienced people who are slightly different than just designers and developers and who have different needs and jobs? And again, the best person for that might not be me. And so those were all the thoughts that were going through my head. And then things came together really quickly. DIANA: Yeah, they sure did. [laughter] They sure did turn around and come together really quickly. First, I have a lot of admiration for you, in particular, like the way that you're able to take a step back and look at things objectively and not let ego get in the way of things because that's a big deal. Not everybody is able to do that, Chad. And I've worked at a lot of places, as we talked about, and I've seen ego get in the way. And I've seen ego get in the way in a bad way. It's not always a friend. Sometimes it could be a friend, sometimes it's a very powerful friend to have, but sometimes ego can hurt. And so there's a lot of wisdom to that. And in terms of the speed at which things came together, yes, I agree; I think that's a reflection of the times we're living in. We're in a time where things can change on a dime, and we just have to be able to pivot and be able to reassess the landscape, see what we have to do, make the necessary modifications and then go. And I'm really proud of both of us and the team of the managing directors and everyone at thoughtbot for our ability to quickly adjust and do what we had to do during the really crazy year that 2020 was. CHAD: I spent the majority of 2020 in intense survival mode. And so it wasn't until we were through that period that I realized how much it had affected me, whether it be in burnout ways but also in terms of realizing that we were going to survive. At the end of March, early April, it was the most difficult time. We saw a good portion of our business…new projects were starting, people doing new things. At the end of March, early April, a lot of that new stuff got completely put on hold as the whole world recalibrated. And so we saw a significant decrease in revenue in those months, and we didn't know where it was going to go. So we were very proactive about redoing our numbers and making sure that we weren't going to go out of business and didn't go out of business. And once we were able to do that and to stabilize things, we still needed to spend a significant amount of effort for the rest of the year, working really hard to make sure that we made things less bad. And that was pretty difficult. But my main point or my takeaway from the year and part of what has led to this transition is the realization that I don't really have any plans to go anywhere per se, but rather than be like, oh, I need to keep my position forever, it's more we're coming up on the 20-year mark of thoughtbot. When we came up on the 10-year mark of thoughtbot, we asked ourselves the question, “Okay, it's ten years. We're not really going anywhere. What do the next ten years look like?” And so, as we continue to move forward as a company, I think the horizon tends to expand. And it's like, okay, we're coming up on 20 years. What do the next 20 years look like? So, I don't really have any plans to go anywhere, but am I going to be doing this and the same thing in the same way for another 20 years? Probably…

    Full show notes at the publisher

    Values - ShearShare Dec 21, 2020
    Show notes

    Chad and Lindsey talk with Courtney & Tye Caldwell, Co-founders of ShearShare, discussing culture-fit with new hires, incorporating values into brand-thinking, fostering relationships, and planning for 2021.

    • Please take a minute to help guide our next season with your thoughtful feedback on our Giant Robots listener survey.
      Thanks!

    • This episode is sponsored by HelloFresh
      Enter code ROBOTS80 to get a total of $80 off, including free shipping!

    • ShearShare
    • ShearShare on Instagram

    Become a Sponsor of Giant Robots!

    Special Guest: ShearShare.

    Sponsored By:

    • HelloFresh : Get a total of $80 off, including free shipping! Promo Code: ROBOTS80

    Support Giant Robots Smashing Into Other Giant Robots


    Values - Teikametrics Nov 30, 2020
    Show notes

    Chad and Lindsey talk with Alasdair McLean-Foreman, CEO & Founder of Teikametrics, discussing the intermingling importance of mission, vision, and values.

    Please take a minute to help guide our next season with your thoughtful feedback on our Giant Robots listener survey.
    Thanks!

    • Teikametrics
    • Blitzscaling- Reid Hoffman
    • Jeff Weiner - CS183 at Stanford
    • Dunbar's number
    • Previous Netflix Culture Deck
    • Alasdair on LinkedIn

    Become a Sponsor of Giant Robots!

    Special Guest: Teikametrics.

    Support Giant Robots Smashing Into Other Giant Robots


    Previous 1 23 24 25 26 27 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