
Definitely, Maybe Agile
Definitely, Maybe Agile
Flow States in Remote Teams with Steven Puri
In this episode of Definitely, Maybe Agile, hosts Peter Maddison and David Sharrock welcome Steven Puri, Founder and CEO of The Sukha Company. Drawing from his unique background spanning Hollywood film production and tech startups, Steven shares fascinating insights about achieving flow states in remote and hybrid work environments.
Steven's journey from IBM software engineer to Hollywood executive (where he helped manage franchises like Die Hard and Wolverine at studios including DreamWorks and 20th Century Fox) provides a refreshing perspective on team productivity and creative collaboration. He explains how the film industry has long mastered the transitions between remote, hybrid, and in-person work—knowledge that proved invaluable when the pandemic forced tech teams into distributed environments.
The conversation explores the neuroscience of creativity, practical leadership approaches to foster flow states, and how Steven's experiences led him to create a platform specifically designed to help remote workers overcome procrastination while maintaining wellbeing. This is one not to miss!
Key Takeaways:
- Leaders can create environments where flow happens - Establishing boundaries like protected focus time (e.g., 9 AM to noon) allows team members to accomplish meaningful work before daily meetings begin.
- The "two-problem" approach to creativity - Having more than one challenge to work on simultaneously can unlock creative solutions, as your subconscious mind works on one problem while you actively engage with another.
- Remote work requires different "colors on your palette" - Different work modes (remote, hybrid, in-office) excel at different tasks, with in-person collaboration being particularly valuable for creative ideation and whiteboarding sessions.
Books Mentioned:
- "Flow" by Mihaly Csikszentmihalyi - https://www.goodreads.com/es/book/show/66354.Flow
- "The Net and the Butterfly" by Olivia Fox - https://www.goodreads.com/book/show/30024684-the-net-and-the-butterfly
- "Atomic Habits" by James Clear - https://www.goodreads.com/book/show/40121378-atomic-habits
Peter (0:04): Welcome to Definitely Maybe Agile, the podcast where Peter Maddison and David Sharrock discuss the complexities of adopting new ways of working at scale. Hello and welcome! It's great to be here again. Dave and I are joined today by Steven Puri, and I'm looking forward to welcoming him on the show. Steven, would you like to introduce yourself?
Steven (0:23): Absolutely! Thank you guys for having me. I'm the founder and CEO of Sukka Company, and we help people focus—especially in remote or hybrid situations. Tech teams as well as writers and designers, that sort of thing.
Peter (0:37): That's awesome, and you've got a very interesting background as well.
Steven (0:40): I know what you're alluding to! So I spent between one and two decades making films. I was executive vice president over on the DreamWorks lot, I was a vice president at 20th Century Fox, so I ran franchises there like the Die Hard franchise, Wolverine franchise, a bunch of stuff like that. Yes, I spent a bunch of time in film and a bunch of time in tech.
Dave (1:01): That sounds like one of those conversations where we could just get sidetracked and explore all of the different franchises and where they go, and I'm sure there are great stories there.
Steven (1:10): There's some crazy stuff. We'll see which ones we can fit in there.
Dave (1:14): Maybe let's just try and pull back into... well, you mentioned remote work, and when Peter and I typically talk about remote work, we're usually talking about post-pandemic development teams that always used to be in person, now suddenly working in a remote context. But you came to remote work from a different angle. I mean, I know you've got tech in your realm of experience, but I think you came into understanding remote work and putting things together from a different perspective.
Steven (1:43): Probably different than most of your guests, and I hope this is interesting for your audience, because I am the son of two IBM engineers. Dad was a hardware engineer—chip design, basically CPUs, logic chips—and mom was a software engineer. So my first job was actually at IBM as a junior software engineer because I was a Watson scholar. But I went to Los Angeles and went to university at USC, which has a big cinema school. So I happened to be kind of maybe a code monkey trying to figure out what to do with my life, and a lot of friends were naturally aspiring writers and directors and filmmakers—you know, you're around in your dorm and all that.
I was in LA when film went digital, and that little Venn diagram of people who could speak engineering AND people who are personable enough to understand how to speak to a director was very small. But I was in that little intersection, so my career took off. I was like, "Sure!" Life just handed me this. Out of school I started doing that and got super lucky. Let's be honest—you can work as hard as you want, you can be as clever as you want, but sometimes there's a luck element, and I had a lot of it. So I'm going to say it right up front.
I happened to produce the digital effects, the CG effects, for Independence Day, and we won the Academy Award for the visual effects on that movie. So a rising tide lifts all boats. I was there, started my first company, which was a CG company. This is back when Silicon Graphics was a powerful name in that business, right? So we raised about 15 million, built that company, sold it a couple of years later in my late twenties, and there's about a 6X multiple on the return. I was like, "Wow, this is easy!" Not knowing everything I know now, but... it's not easy.
And then, having worked so much with film, I got into film. Now, here's the answer to your question with that context. Working in film, I was like, "I want to learn how to produce a film. I want to eventually become a senior executive of a studio and help make movies." There were a lot of things I learned that when I got back into tech about 10 years ago, I was like, "Wow, some of the things here that are just evolving have actually been part of film for a long time."
I'll give you a very concrete example. In film, for decades, it starts remote.
Steven (3:48): It's writers alone in their home on their little MacBooks, going to a coffee shop and writing, doing it with their buddy. Hopefully at some point you get something done. You go and have lunches with producers, go to a restaurant for dinner, and you're trying to sell your wares. Maybe one of those ideas gets traction. A little money comes in.
Steven (4:07): You set up a production office. One or two days a week, you have meetings in the office with production designers and line producers and location scouts trying to find where to shoot this thing. And then it's that hybrid thing. Then you are on set—$125,000 a day, everyone's there all day, all night for several months of principal photography, right? And then it goes back to hybrid with picture editors, sound editors, foley artists working here and there.
Steven (4:32): Then it goes back to basically remote. And through each stage of that, you learn as a producer or as a studio executive: How do you lead that? How do you inspire teams through that when you're not seeing each other until it's like... well, you see someone, then you're sick of each other on set, no one's slept, you've been sleeping under your desks practically, that sort of thing. And you learn also how to be an individual contributor in those situations.
Steven (4:55): So that was what was really interesting to me, because when I got back into tech after I left Fox—I wanted to have more agency over what I built. I didn't want to be just the guy making the next Die Hard movie, which, admittedly, is fun from the outside, but from the inside it's just soap. That's how it is. It's soap. We market it next spring, this comes out at Christmas, we know how it works. And that was something that really helped me, because both companies I set up were completely remote, and how those techniques could be applied to say, "Oh, you know what, here are things that help." And going into the pandemic, that for a lot of people was a huge shock to the system. For me it was like, "Oh, this is like this era," and that's what I thought was really fun and interesting.
Dave (5:34): As you're describing that, Steven, one of the things that strikes me is... so again, Peter and I have discussed this challenge many times—one of the drivers for bringing people back into the office is the impact on innovation.
Dave (5:49): Remote work had... because there's lots of great things that came out of remote work in tech over the last few years. But an area of concern for a lot of organizations is: what's the impact on innovation? You're describing a hugely creative industry that has overcome remote work versus innovation. So how does that happen? Is it driven by the leadership? Is it context?
Steven (6:17): Let me say this before I answer that. There are some problems that are hiring problems, and if your reason for believing RTO is the only way to go because you don't trust anyone's working, that can't be solved with any amount of leadership, any amount of... it's just you hired the wrong people. And, as you know, hire slowly, fire quickly. It's just, period. So let's assume we're talking about teams where the right people are there, but they need to be led properly. Fair?
The metaphor that I draw about what you just said is: for many companies, on their color palette they had oranges and reds and yellows, and with the forced move into remote work, it was like suddenly blue was a very important color in 2020, 2021, right? Which meant you could paint lakes and blue skies. Suddenly you had more colors to paint with. I do think very much that remote, hybrid, return to office, or in-office in-person—these are a spectrum of colors and they're all good at certain things.
I'll give you some examples that I learned in film. I have never been on a Zoom or Teams or Google Meet or anything where I felt that the creative collaboration—the thing of like, "Oh well, what should happen next in the UI?" or "Dave and Peter, in the third act, meet the dragon, what should happen?"—I've never felt the same way I felt like actually vibing in the room, whether you're around a whiteboard or you're at a coffee shop, whatever. There is something human about just feeling each other's energy, being like, "No, remember, Peter had in his bag the sword," and there's just something about being... It's not the same as staring at a little three-by-five of you. So I think that's one of the things we have to acknowledge. These are different tools. This is a screwdriver, that's a hammer.
Now I'll mention a different but related concept around that, which was something that I found about leading creative teams, was taught to me when I was 20. I was working—again, this is my first footsteps into film.
Steven (8:11): I was at an ad agency that did trailers for movies, run by two guys, super smart. One of them to this day is a friend of mine. So I had gotten in there when I was a senior in college and worked really hard, and I was running the writer-director department. So in other words, when we got movies in—largely from Warner's and Buena Vista Disney—we would assign them to say, "Oh, you know, this is a perfect rom-com. Dave does this really well. Oh, Peter writes action trailers, we'll give it to him." So I would be the guy who would assign these, right?
Steven (8:39): So the guy who ran the company—one of the two guys—comes in. This guy Jeff, he always calls me Stevie. He's like, "Stevie, you know Bart?" And I was like, "Bart the runner? The guy in the vault that delivers tapes and films and stuff around Hollywood?" "Yeah, nice guy, man." He's like, "Have you ever given him a trailer?"
Steven (8:54): I was like, "Bart? You mean the guy who runs the tapes around Hollywood?" He's like, "Yeah, yeah, yeah." I was like, "Jeff, you run—you own the company. Done, I'll find something for him. You got it," right?
Steven (9:09): So I found like a B title from Warner's that had a long due date, like we had a month to do the trailer. So if he in a week or two was like, "I don't know what to do," I could give it to Peter or Dave and they'd be like... So how's Bart doing? I was like, "Dude, he's never written a movie trailer before. I sent him home with a B title two nights ago. I'll check in with him on Monday. I don't want to stress the guy out." He goes, "Okay, fair enough, fair enough. So what else did you give him, Jeff?" "He's never written a trailer before—I gave him this one movie." He goes, "Stevie, it's about the other thing."
Steven (9:39): "You got to understand this about creativity." I was like, "What do you mean?" He goes, "If you don't give him another movie to obsess over in the back of his mind, that actually does the cool... You're like chocolate and peanut butter. It's never going to have that time to do it because you don't have the great idea about the thing you're staring at." He's like, "If you want him to have a great idea, give him another movie and watch how he's going to have that idea." He's like, "Have you ever noticed like you're driving and you're showering, you're washing the dishes? You have the thought." He's like, "Know that. Whenever you're leading creative teams, you can't just stare at one problem." My entire career in film proved him right, my career in tech. I just watched that happen over and over, and I was like, I was lucky at 20 years old that he came in my office and basically handed me this lesson.
Dave (10:25): That's a great one. So just literally more than one problem, basically.
Steven (10:32): Yeah, and there's a great book about this on the neuroscience of this, called "The Net and the Butterfly" by Olivia Fox, and it talks about the executive network and the default mode network and how you kind of need to occupy the adult brain for the baby brain to go, "I have that crazy idea." Peter, you were about to say something. You were just about to say something.
Peter (10:48): Oh yeah, I was just thinking I've seen the similar concept to why, if you're stuck on a problem, get up and go for a walk. Do you guys do that? Do you get up and go for walks when you're stuck?
Steven (10:57): Yeah, I get stuck a lot. I do a lot of walking.
Peter (10:59): Yeah, yeah, I do too.
Steven (11:03): I live right here in Austin. We have blocks. I couldn't do this in New York, I couldn't do this when I was in LA, but here in Austin I can go out and walk around the block and be like, "Oh, suddenly my brain is refreshed and I have a new perspective on the problem."
Dave (11:15): I'm going to ask you at some point to tell us a little bit about the company and the product that you have around that.
Dave (11:21): But there's an element there on the creativity that very quickly leads us to this whole idea of flow and just how to get the brain—and you're already beginning to touch on this—how to work with our brains so that we're actually setting ourselves up for success. And what's interesting in an agile context is one of the conversations I'll often have is how accidentally or on purpose—and you know nowadays it's been 20 plus years, so it's almost certainly been on purpose, by design, but the reality is probably partially accidentally and partially on purpose—a lot of the ways of agile working is about working with our brains so that we're actually able to bring the best piece to the table. So you just touched on this idea of multiple problems, of getting out and having our adult brain work and our baby brain come in with the right ideas. What are the other aspects around flow? What have you noticed as these key things that really influence a team to be able to get into that state of flow?
Steven (12:27): Okay, I will share with you things I learned, both my personal experience. Also, there are some very smart people who have written about this. So I'm going to acknowledge a lot of what I'm saying is not like I invented it, just I read it, tried it. It's true, and my wife also came up as a PM, so I've watched her career and her lead teams as she's risen up. So one thing is to respect flow, which I noticed you said several times. That is a core foundation of what I built.
Steven (12:54): The thing that I learned more than anything in the past six years of working with remote workers and trying to help people work is that you have to respect—there's certain boundaries and it is... One good example is flow is not something you switch on and off in 20 minutes. You don't get into a deep work state, a flow state. Mikhaly Csikszentmihalyi has written a lot on this, and Cal Newport—I mean a lot of people have written smart stuff on this. But if you have a team where you're like, "Hey, we are agile, we are iterative. How do we transform the world through our agile methodologies?" you also need to recognize: hey, if I need someone to actually do deep work, it's a block where they are not going to be bugged. For example, when you're working in my platform and you go into a session, you can enable it will put your Slack in do not disturb. So it'll say, "Hey, I'm in a flow session," so it's just like you can leave a message. I won't get a notification and I'm probably out for two hours, but I will see you. I'm not ignoring you. Same with Discord. It's just one of those like, let me help you create that quiet space, you can do something valuable. And that is very different than pair programming, very different than working through... you're going through grooming the backlog or anything like that. Those are team efforts. So I think it's the respect of both.
Steven (14:16): For example, in the last company I ran, we blocked out nine to noon, so we didn't even do our daily standup until people had had time, without people talking to each other and jockeying for position and meeting. You had quiet time to do something meaningful and then report in. "Hey, man, I got all this stuff done and it felt really nice to be able to say, before the day got crazy I actually accomplished something meaningful. Here it is. Oh, I got blocked here. I need help with this," or what the usual standup kind of stuff. Things like that. There are many principles there and I don't want to belabor this because now we don't have hours, but there... or do we have hours? Do we have hours?
Peter (15:05): No, I'm waiting for... It depends on how many questions Peter asks, until Peter slaps down.
He's like... something that we talk about a lot as well, and this idea of trying to block off time, trying to time box things, to say we're going to spend the morning working on this when we're brightest, when our energy is at the highest. We want to be spending that time when we're focused on that creative work, when we're really able to get deep into it. Do you guys have calendar links like Calendly or something like that?
Steven (15:26): Yep.
Peter (15:27): Do you block your focus time so that no one can book in that window?
Peter (15:31): Yes, it only lets you book very specific times of the week.
Steven (15:35): Fantastic! Dave, same?
Dave (15:37): Same again. That's cool. That's a great way to show yourself respect.
Steven (15:41): It's an interesting one, because the one that I don't do is blocking lunch, which is... I don't know if that's the British thing—lunch is a sandwich at the desk and therefore it's not a big thing, or something else, but it's just one of those points that I always go, "I really should block the hour of lunch off," but never have done.
Peter (15:59): Mine, I think, comes from working across time zones, which is an interesting piece around remote work—it's difficult to block lunch because it might shift. I might be in the way of what is actually a very productive working time for somebody else who wants to get hold of me.
Steven (16:15): The challenges of distributed teams. This is exactly true, but the advantage—you can hire global talent, right?
Dave (16:22): Yeah, I mean that one's a really... So I've got a small team, but one of the interesting things is the diversity of the team, just in terms of different cultural backgrounds. Many different things coming together is one of the things that is most interesting, I think, around the availability of global talent at this point, right?
Steven (16:45): Lots of diversity. We have iPhone people and Android people. It's crazy. We're on the same team, but they don't text one another. We have a translator!
Dave (16:57): Now, you mentioned something... when you're talking about innovation, you're talking about teams working together, and when we touched on flow, it sounded like you're describing that as a state which is really an individual, you know, cutting out distractions and working on their own. How do you see flow on teams? Is there some sort of Venn diagram where there's a crossover?
Steven (17:18): I see a respect for flow on teams, right, but I haven't... as soon as you get two people together, like we mentioned, like pair programming or something like that, it can be very productive, but it's not quite the same as the experience.
Steven (17:33): I don't know if you guys—I'm sure you have had this where you look up and two or three hours have gone by and you're like, "Didn't even look at the clock, didn't even go to the bathroom, but wow, I can push this, I'm ready to make a commit, like this whole thing is ready to view," and you just lost track of time. I've never had that with another person, because there's always some interaction layer that stops that, but maybe someone does. I can't say that I'm the end-all be-all about that. Maybe someone does get in flow with other people, like I know when you talk about... there's that famous Picasso thing about, you know, he stayed up all night. He's like, "I forgot to go to the bathroom, I didn't think to eat, but you know, here's Guernica, by the way. What do you think? It's pretty good," right? And then...
But you have the Michael Jordan quote about "It's just me and a ball." So I feel like it always does reduce down to like everything collapses and you're like, "This is the one important thing," whether it's your IDE, whether it's your Figma, whether you know... it's Jira Flow, and Jira I'm not sure I'm clear.
Dave (18:40): That one, that's definitely one to watch out for.
Steven (18:42): That's expert level, man. You're beyond Scrum Master—Jedi!
Peter (18:50): One of the pieces you touched on earlier that may tie into that is when we talk about bandwidth, when we talk about when people come together for the deep knowledge work, the standing in front of a whiteboard with somebody else collaborating on something you can both visually see is by far the highest level of communication bandwidth you can have, because you're both visualizing, you're communicating, you're able to be and see the other person's body language and how they react to things, which is much, much harder to do over an interface like this.
Dave (19:21): Yeah.
Peter (19:22): You miss out...
Steven (19:23): Apple Vision Pro or something?
Peter (19:25): Yeah, you miss out... Apple Vision Pro or something.
Steven (19:27): Yeah, not sure about that one.
Peter (19:29): Yeah, I haven't quite bought into that one as an idea yet.
Steven (19:32): Do you know what they cost after the tariffs? You could buy a Hyundai for less!
Peter (19:39): They were expensive to start with, but yes.
Steven (19:42): Sorry, back to you. I digress.
Peter (19:47): It's very true. There's a piece around all of that flow as a community. I started with a good friend of mine here a few years back called Flow Collective, where we actually spend a lot of time talking about flow, but a lot of the time we're talking about flow in the sense of how work flows through an organization. There's a lot of roots in Deming and lots of roots in thinking about how do organizations operate as a whole and thinking about systems and that flow through the organizational system, which of course all comes down to the individual ultimately. But the nature of flow and the way it's used is a little different.
Steven (20:29): Yeah, and you know, Mihaly Csikszentmihalyi, his book—he talked about flow. He's like, "I named it this because it feels like at a certain point you're on the river and it carries you, it increases your momentum because you're being carried by the flow of the river." And yeah, things do flow through organizations, and it's a related concept.
Dave (20:49): It's interesting how there's an overlap there, right? The flow through an organization, through ideas, go through the organization, and so on. There's a desire somewhere to get the people who are in that flow state to contribute to that flow in some way, and there's always the talk of things like 10X developers and things like this, these sort of superhuman people who can deliver something like above and beyond what anybody else can get to. That it really actually isn't built into the flow that Peter's describing, which we look to in organizations. They seem to be... there's overlap, but there isn't... if I'm getting it right, Peter, would you add anything to that?
Peter (21:27): I think it ties into the adage of the parts of the system have to be able to work together as a whole. It's that analogy whereas if you, for example, if I take the best engine out of a Ferrari and I take the best wheels off a Porsche and I take the best framework for a Lotus and I put them all together, no guarantee the car will even run. I can't put all these different pieces together and expect the thing to work well. Even though they're all the best of the best individually, they're not necessarily going to come together and work as a whole. So there is a piece where to create a team and an organization that works well together, it's not just about the strengths of the individuals, it's about how do we work together as a team.
Steven (22:10): Yes, and hopefully you do have leaders that both inspire but also technically know how to structure the work of the team and coordinate them. Something that you brought up a moment ago I'd love to pick up on—when you're talking about 10X engineers... A good friend of mine was one of the first iOS engineers. If you ever hear that story about the six guys that Steve Jobs put in the windowless office to write the first apps before he unveiled the iPhone? Alan wrote Remote, the very first app ever made. He wrote Books, the iBooks thing. He wrote some of these, right? And he is truly one of those guys. It's just like, "Hold on, hold my beer," you know, and comes back and it's like, "Oh wow, we had a team of 18 people who were going to do that next week and you did it over lunch." It's just like that thing, right?
Steven (22:53): And what's interesting is he—I noticed with him he has a flow practice that is very similar to things that I've seen in film. I'll be very specific. So Alan, for example, up in Mill Valley, has his own little studio with beautiful screens in his garage, right? Beneath his garage, in the little valley that they're in and away from the kids, away from his wife, goes out there certain time of day, certain light, the whole thing. It's like that's his workstation and it is something where in the middle of the day it doesn't quite work right, or even with a child it doesn't quite work right.
Steven (23:27): And I'll tell you what's funny is the guys that I had created that company, Centropolis, with back in my 20s, the director and producer of the movie, they had a similar thing about writing, where there was a house that they rented down in Puerto Vallarta, Mexico, where they would write their scripts, and it just had that magical thing for them. Bad cell service, bad internet, the whole thing, just this cloistered thing, the way they like the light in the morning, help them write in the morning, this whole thing. So when they were going to write the next movie after Independence Day, they called their assistant and were like, "Oh, rent us the house. We're going to go to our place, to our workstation work," and the house had already been rented for the... It was like, "We have to deliver this movie, we can't write it this way. Oh, my God, what are we going to do?"
Steven (24:13): And Roland, the director, called his attorney and said, "I need you to buy the house. Just figure out how to do this. By Monday I need you to have bought that house in Puerto Vallarta," and he did, and that's where they just kept writing and it was that important to them that in a sense, their workstation was there, and there is something about the way our minds mentally align with the light and the room and the thing and the hopefully lack of clutter.
Peter (24:42): There's a piece out of one of my favorite books, "Atomic Habits" by James Clear, where he talks about associating both physical space with where you're working. So if you're, for example, if you spend all of your day in front of a screen answering emails and working communicating with people, but then you need to go do something creative, perhaps get up and go to a different place in the house where the lighting's different, where the seats are different, where you're in a different environment, and do the creative work there instead.
Steven (25:11): So true.
Dave (25:12): As you're describing that, Steven, I'm just thinking about as a leader working with remote teams, but also working with people who are so productive in a flow state. What's... as a leader, how do you kind of work with it, rather than like you're either just fingers crossed, hoping they'll get the flow state when the deadlines are approaching, or is there something else that a leader is going to do to empower people to get there?
Steven (25:38): I'll tell you this. What I've noticed is that leaders can make room. They can keep the lane free to go, "Hey, you know what? For example, my company nine to noon, no one's going to bug anybody." You can create space. But it's usually peer-to-peer that that kind of practice spreads, where it is like one dev talking to another dev being like, "Hey, man, you're my young Padawan, whatever. Let me tell you how this works." The same way you learn about rubber ducking and you learn about pair programming, things like that. Same thing.
Steven (26:06): In my platform, the three biggest cohorts are devs, designers and writers, because they all have communities, they talk to each other, they share. "This is the tool that I'm using. This is the thing I learned. This is the post on the new LLM you have to hear about." And they all have knowledge work to do, like everyone in my platform is basically college educated, over 30, money, with post-grad degrees, and they have a respected flow practice. They're like, "I block out this time because their leadership says this is how we move the company forward. It is not meetings all day long." Nobody in business development, no sales people, use my platform. This is not the platform for people who are on Zoom all day long.
Dave (26:49): You also didn't say leaders and managers as a cohort, which is interesting.
Steven (26:58): You're managing up or you're managing down.
Peter (27:00): It's one of the pieces of advice that I give as a coach to leaders that if you have those conversations, position them to one end of the day, like don't try... don't hold them at the middle of the day and the middle of the morning is worse.
Steven (27:18): Yeah, just kill the flow. It's completely agreed. Yes, what else can I answer for you?
Dave (27:22): Well, I can keep exploring. There's just some very interesting conversations as we're looking at...
Dave (27:27): Maybe I'll just extend on the piece there and then I'm sure Peter's going to come in with a stopwatch at some point—
Peter (27:33): Oh yeah!
Dave (27:34): —but so I'm just thinking about the conversations that we often have with technology teams, non-technology teams but helping them sort of empower and get as much off of the leader's plate or the manager's plate and actually empowering the teams to go away and do things, and one of the big pieces is about managing work, and this was something that is, I think, underpinning the push to get people back in the office. Part of it is "I don't know what people are doing." I can't see them, I can't tell what's going on. So, whether it's work management tools and we touched on Jira and things like this—what other things do you see as a leader who maybe wants people to be working in a hybrid way or remote and so on? However, they have that feeling in their gut that says, "But I don't know what they're doing." How do you address that? What have you seen?
Steven (28:30): We talked about one of those things first, which is, if you don't hire properly, it's very hard to fix. I mean it's better to say, "You know what, this doesn't feel like the right company for you or the right environment for you. Let me help you move on," right? So there's absolutely that. If you were having a gut feeling of like, "Hey, man, Peter's killing it and Dave, I don't really know what..." probably yeah, you're right and you didn't hire correctly. The other part of that is the value alignment, like does that person have values that align with the mission of the company? If you believe climate change is a big thing, if you believe... did you seek out this company because they do that? "Oh, we are making electric vehicles or batteries or vehicles, or we're doing wind energy." Is there a thing where it's just like we inspire Dave because our values, our mission, aligns with your values? And if it's not, if it's something where it's like actually Dave is all about windsurfing and... I'll tell you this is a mistake that I made in my previous companies—really great designer, like very talented dude, but in Hawaii, and really really was focused that point in time on surfing and even though he had like two or three kids. I was like, "Oh, this is a serious family guy, like he's at that place in his life where he's just..." No, there was definitely a sense of like, "You know what? I bet the surf was good this morning. That's why the designs aren't done," and that sadly led to that conversation of like, "I just don't feel this is a fit. This is a small team dude. We can't have anyone who's not pulling their weight," plus. So I guess in that sense it was a hiring thing. I had misjudged who it was and good guy, but just his values were not aligned with what we do, which is, I believe, passionately. I want to give people the ability to work anywhere, to focus, to feel like they're doing the thing they're meant to do. They're great at it. It feels really good.
One of my members said to me this, which summed up everything that we do. I was bugging him. I was like, "Give me some feedback from the outside, outside the bubble, what do you like about the platform?" And at the end of like eight or 10 minutes of chatting and me to kind of learn, I was like, "You know what? It was really nice. Thank you for taking the time to chat. It's really helpful just to hear from our members, what's up."
Steven (30:41): And he said, "The question you wanted to ask you didn't ask. I'll tell you the question you should have asked me." And I was like, "That's a pretty bold way to phrase it and I'm probably a little too diplomatic to say that, but yeah, what would be the answer to that?" He said, "At three o'clock I can be playing with my kids, or at six o'clock I can be like, 'Where the hell did the day go?'" He said, "The difference is: did I open Sukka in the morning? I pay you so I can be playing with my kids at three." Got it, thank you.
Steven (31:17): And that lives in my head—permanent real estate—ever since he said it, that that is ultimately what we do. We give you the tools to do something great and have a healthy balance where you're performing, you know you're doing the thing you're meant to do and you also are like, "I'm healthy, I'm spending the time with my kids if you've got them, your husband, your wife, your boyfriend, your hobby, whatever it is, knowing this is the life I was meant to lead."
Dave (31:42): You probably need to say just a little bit about the company as well. I was thinking that.
Peter (31:47): I was thinking, if we're going to wrap this up, what is the company?
Steven (31:53): So what we built is really built on the foundation of what Mihaly Csikszentmihalyi wrote with "Flow." We talked about Newport and Clear. There are a lot of smart people in this thing. If you read a dozen of the top books, they boil down to four or five key principles. They all have their own lexicon, they have their own examples, their own books you all have to buy for $25. So there's a commonality to that.
And what we thought is how do you put these together in such a way you can help people get into a flow state—that time, that two or three hours in the day where you go, "I'm going to do the most important work of the day now and have me a force multiplier." So we built a really simple app—I'd like to think it's somewhat elegantly simple—that has a smart assistant that helps you get over the problems that might stop you, the problems that I hear about for five, six years all the time. Some of them are very obvious on their face. For example, the number one thing I hear from people is, "Hey, man, I get ready to go, I get ready to start in the morning and I procrastinate." Okay, well, why do you procrastinate? "Well, sometimes I look at my task list and I know what's assigned to be a Linear, Asana. It's just... well, I'm not really sure." And then I know I've got meetings to do.
So we have a smart assistant that looks at what you have to do and says, "You know what? Let's be realistic. You're going to get three things done today. Let's choose the three most important things that have to get done," and then looks at them and says, "Hey, by the way, I know you're a writer. He's like, 'Write a book.' You're not going to get that done today. That is not granular enough for you to have a win. How about we make that 'Outline your first chapter'? Okay, can you do that in, let's say, 45 minutes?" And then you look at your task list, you go, "Oh, yeah, I can tell you my first chapter. I've kind of thought about that when I'm driving. I know what I'm going to do there. Oh, the second, I've got to go fix that bug. I have a suspicion where the bug is and the..." Yeah, I can do that, and it gets you going.
Steven (34:00): And there's beautiful music. We have like a thousand hours of flow music, all scientific research by the best practice—60 to 90 beats per minute, non-vocal, melodic, certain key signatures. There's binaural. If you have headphones, you're into binaural, we have binaural playlists. If you like nature... One of our sound engineers was in Kathmandu, recorded two hours of rain in the Himalayas. We threw it in there. It's super popular. So now we have streams in Japan. We have the surf in Cyprus if you want to listen to that. We've got all sorts of nature sounds around the world. I think Emerald Lake or Banff Lake or Victoria, one of those Canadian lakes with birds around the lake, all sorts of things.
There are Pomodoro timers, healthy breaks, because, yes, you can find your own rhythm. Maybe it's 25 and 5, for me it's 55 and 5. I always find after 25 minutes I'm in the middle of a thought. So there are timers just to go, "Hey man, you know you haven't gotten up for an hour. Why don't you get up and go downstairs and get a glass of water?" Or if you want to do a stretching exercise, here's a two minute stretching exercise. You have time to go for a walk. So we try to build a lot of these things in of saying, "How can we give you a beautiful environment with music, a smart assistant to help you, timers, healthy breaks and a score?"
Steven (35:01): At the end you can sort of see like, "How did I do? Oh, this is where I was opening YouTube to check that video on the React thing. But then I saw the political video and then I saw the one about..." You could see it and you, hopefully you learn. So feedback is also an important part, as you know, flow from his book. So that's what I do. We make a simple app. It runs in your browser and it's a fun community. You can see other people in their... social facility. Excuse me, social facilitation is an important part of flow for some people. Just knowing that it's like, "Why do you go to coffee shop and work?" Because sometimes it's nice feeling the energy of other people, even if you don't chat with them. It's just like all in it together.
Peter (35:42): That's what I do and it's free to try, and they can find it at...
Steven (35:48): Yeah, no, it is free to try. I just wanted people to... everything that I learned in the past two companies and then this company. I wanted people to be able to benefit if it helps them. We have, by the way, this is my most proud statistic metric—we're going to call it KPI—our month over month paid retention: 96%. The people who find us and get into flow, it's a daily habit. It's like, "Why would I work for six hours if I can focus for three?" So that's really nice. And our number one source of traffic is referral.
Dave (36:20): It's just literally Peter going to Dave, "Dude, try this." I was going to say I'm going to go find that Kathmandu in the rain, because I live in Vancouver. I was gonna say I can record a lot of rain for you.
Peter (36:33): I do think we have to go. Yeah, it has been fun, thank you guys for having me. Well, so thank you for coming. It's been a pleasure. We normally wrap up these conversations with three key points, and since there's three of us, we each get to nominate one. So I'm going to say, hey Steven, what's your favorite point to take away from the conversation today?
Steven (37:04): That leaders in technical organizations can create the environment where flow happens.
Dave (37:11): I like that. I'm going to refer back to one of the first stories Steven shared, which was the adding something to somebody's plate and adding a second thing to somebody's plate, so they've got that... the adult brain and the baby brain working together.
Steven (37:31): The other thing lesson from Jeff Kellman. There you go.
Peter (37:35): Now you see, for me, that was the one I was going to pick too because I thought that was a good story. Good to know. It is a good story. I think actually what you're doing and what your company's doing is quite fascinating. I'm certainly going to give it a try myself, so I think that's a good point to bring home, and so thank you again, Steven, and thank you, Dave, as always.
Steven (37:59): Thanks everyone for listening.
Dave (38:01): Thanks again, Steven. Until next time.
Peter (38:04): You've been listening to Definitely Maybe Agile, the podcast where your hosts, Peter Maddison and David Sharrock, focus on the art and science of digital agile and DevOps at scale.