Fast Time To Market
In the early 1990s, lateralworks conducted an extensive multi-company study involving over 500 people who worked on fast-to-market projects in Silicon Valley. Since then, they have worked with hundreds of teams to accelerate the delivery of new technology products to market. The research continues today to keep the best practices current.
This podcast series will share many of the practices that teams use to deliver the right product to the market at the right time.
Fast Time To Market
Creating an innovation culture
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
This podcast investigates the innovation paradox, which involves balancing the free generation of creative concepts with the necessity of rigorous evaluation. Successful companies like Google, Amazon, and Pixar thrive by prioritizing psychological safety, ensuring that early-stage ideas receive support before they face intense scrutiny. This specific sequencing of encouragement and critique prevents promising projects from being discarded prematurely and encourages employees to continue sharing their thoughts. Leaders are encouraged to view innovation as a sustained cultural habit rather than a rare event, utilizing structured rituals and management protection to foster growth. Ultimately, establishing an environment where risk-taking is rewarded and feedback is constructive serves to both drive business results and improve employee retention.
Welcome back to the FTTM Podcast, your guide to getting the right product to the market at the right time. This week, we are going to focus on FTTM planning, how to execute to achieve right time.
SPEAKER_01Aaron Powell I am so excited for this one. It's such a critical topic.
SPEAKER_00It really is. And just to set the stage for you listening, when we say FTTM, we mean fast time to market.
SPEAKER_01Right, which is basically the holy grail for any business, right?
SPEAKER_00Absolutely. But before we get into the actual mechanics of that, I want you to imagine a kind of crazy scenario. Aaron Powell Okay.
SPEAKER_01Lay it on me.
SPEAKER_00So imagine you are in a hospital and you find out that the highest-rated, most prestigious medical team in the entire building, like the absolute best doctors. Trevor Burrus, Jr.
SPEAKER_01The ones you'd want doing your surgery. Trevor Burrus, Jr.
SPEAKER_00Exactly, the dream team. Imagine you find out that they actually have the highest rate of recorded medical errors in the whole hospital.
SPEAKER_01Aaron Powell I mean, that sounds completely terrifying.
SPEAKER_00Aaron Powell It does, right? It sounds like a total paradox.
SPEAKER_01Aaron Powell Yeah, it really does.
SPEAKER_00Aaron Powell Well, today we're going to explore why that exact, completely counterintuitive scenario holds the actual secret to the fastest product launches in the corporate world.
SPEAKER_01Aaron Powell And it's just one of the most fascinating paradoxes in modern management, honestly.
SPEAKER_00Aaron Powell It really is. So we're doing a deep dive into this massive roadblock to innovation. Aaron Powell Right.
SPEAKER_01Because the goal today is to unpack how the best leaders navigate this stuff.
SPEAKER_00Aaron Powell Based on the lateral works research, of course.
SPEAKER_01Aaron Ross Powell Exactly. We want to look at how you can create an environment where radical new ideas are encouraged and eventually stress-tested to their absolute limits.
SPEAKER_00Aaron Powell But without that testing, just immediately killing the idea on day one.
SPEAKER_01Aaron Powell Which happens way too often.
SPEAKER_00Way too often. So think about FTTM. Fast time to market. You have a brilliant, world-changing product, right? Or maybe just a highly efficient one. Aaron Powell Yeah.
SPEAKER_01And you need it in the hands of your customers yesterday.
SPEAKER_00Right. But getting to that finish line requires a level of organizational care that is, frankly, incredibly rare.
SPEAKER_01It's super rare.
SPEAKER_00Aaron Powell I like to think about it like gardening. So you plant a seed, and a few days later, a really fragile, tiny little green sprout pokes out of the dirt.
SPEAKER_01Okay, I see where you're going with this.
SPEAKER_00Your first instinct shouldn't be to, you know, grab that sprout and yank on it just to see if the root system can survive a hurricane.
SPEAKER_01No, of course not. You just rip it out of the ground.
SPEAKER_00Exactly. You don't test the plant that way. You just murder it.
SPEAKER_01Right. You have to nurture it first. Yeah. Give it water, sunlight.
SPEAKER_00Yeah. And then only when it actually has a strong foundation do you expose it to the harsh elements.
SPEAKER_01Aaron Ross Powell I mean, that analogy perfectly frames the core issue we see in the lateral works research.
SPEAKER_00It really does. Because to achieve fast time to market with the right product, we first have to understand why so many right products never even see the light of day.
SPEAKER_01Aaron Powell Yeah. The graveyard of dead ideas.
SPEAKER_00Exactly. Let's do an autopsy on a dead idea. What does the lateral works research say is the cause of death?
SPEAKER_01Aaron Powell Well, it's almost never a lack of creativity from the team. Like that's not the problem.
SPEAKER_00Aaron Powell Interesting. So what is it?
SPEAKER_01Ideas die because organizational environments are just inherently hostile to fragile early stage concepts. They're built to reject them.
SPEAKER_00Aaron Powell But what does that hostility actually look like in real life? Because I mean most managers aren't whiting up saying, I'm gonna go crush a fragile idea today.
SPEAKER_01No, no, it's much more insidious than that. It looks like a totally standard Tuesday morning status meeting.
SPEAKER_00Okay, paint the picture for us.
SPEAKER_01So someone brings up a half-baked, maybe slightly weird idea for a new product feature. Trevor Burrus, Jr.
SPEAKER_00Just a sprout of an idea.
SPEAKER_01Right. And instantly the finance lead asks for a three-year revenue projection.
SPEAKER_00Aaron Ross Powell Oh man, classic.
SPEAKER_01Yeah. Then the engineering lead points out that it doesn't align with the current tech stack. The legal team chimes in with vague compliance concerns.
SPEAKER_00Aaron Powell Just piling on the constraints.
SPEAKER_01Aaron Ross Powell Exactly. And all of those constraints are necessary eventually, but when they arrive at the sprout stage, it's a two-fold disaster.
SPEAKER_00Aaron Ross Powell Well, the first part of that disaster is obvious, right? The promising idea is just dead.
SPEAKER_01Aaron Powell Completely dead.
SPEAKER_00Aaron Powell The company loses a potentially massive revenue stream because they demanded a literal spreadsheet for something that was basically just a sketch on a napkin.
SPEAKER_01Aaron Powell Right. But it's the second part of the disaster that really destroys companies over the long term.
SPEAKER_00Aaron Powell The cultural toll.
SPEAKER_01Yeah. When employees watch that happen, when they see a colleague just get grilled over fragile concept, they develop what psychologists call learned helplessness.
SPEAKER_00Aaron Ross Powell Learned helplessness. I mean if I'm a leader trying to drive fast time to market, that phrase is my worst nightmare.
SPEAKER_01Oh, it should be. Because it means after having their ideas repeatedly crushed by this premature scrutiny, your team fundamentally rewires how they operate.
SPEAKER_00They just give up.
SPEAKER_01Pretty much. They learn that the path of least resistance, the best way to survive and get promoted, is just to keep their heads down.
SPEAKER_00So they stop looking for solutions altogether.
SPEAKER_01Exactly. They just wait for explicit instructions. They only execute what is specifically demanded of them. The personal risk of proposing something new is just too high.
SPEAKER_00Wow. So the compounding organizational toll here isn't just that one lost product. It's total organizational stagnation.
SPEAKER_01Aaron Powell Precisely. You foster this environment of learned helplessness.
SPEAKER_00And the really talented, highly creative people who generated those ideas in the first place, they're going to update their resumes.
SPEAKER_01Oh, they're out the door. Yeah. They will go find a company that actually wants their brain power.
SPEAKER_00Aaron Powell Leading you with the people who are perfectly fine just taking orders, you've basically degraded your entire culture of initiative.
SPEAKER_01Aaron Powell And this whole dynamic brings us to what the lateral works best practices define as the innovation paradox.
SPEAKER_00Aaron Ross Powell The innovation paradox. Let's break that down for the listener.
SPEAKER_01Aaron Ross Powell So it's this fundamental structural tension in business, the absolute rigor required for flawless execution, like operational discipline, predictability, eliminating uncertainty. Trevor Burrus, Jr.
SPEAKER_00Right. All the stuff you need to run a successful business.
SPEAKER_01Yeah. But that exact rigor is actively lethal to innovation.
SPEAKER_00Aaron Powell Because innovation requires the exact opposite.
SPEAKER_01Exactly. It requires exploration, a really high tolerance for ambiguity, and you have to be willing to spend time and money on a concept way before you can prove its financial value.
SPEAKER_00Now I have to push back on this a little bit.
SPEAKER_01Go for it.
SPEAKER_00Because if you're listening right now and you run a division, your bonus is probably tied to that rigor. That discipline is what keeps the business profitable.
SPEAKER_01That's a very fair point.
SPEAKER_00Right. Like you can't just have highly paid engineers wandering aimlessly through the woods hoping they trip over a good idea. Tolerating ambiguity sounds great, but in reality, isn't that just throwing money down the drain?
SPEAKER_01Well, that's the exact trap, and that's why we call it a paradox. But the solution to a paradox isn't to just pick one side and abandon the other.
SPEAKER_00Okay, so you don't just lower the bar.
SPEAKER_01No, definitely not. The leader's job isn't to abandon rigor or profitability. You solve the paradox through sequencing.
SPEAKER_00Sequencing, meaning the order in which things happen.
SPEAKER_01Aaron Powell Exactly. You have to coexist with ambiguity by strictly ordering the process. Space to breed comes first, rigor comes second.
SPEAKER_00Ah, I see. So you intentionally structure the environment to protect the idea while it's still fragile.
SPEAKER_01Yes. And then only when it has enough form do you subject it to the most brutal, rigorous stress testing your company can handle.
SPEAKER_00Aaron Powell Okay, so if the core of this paradox is the fear of bringing those fragile ideas forward to begin with, how do we actually eliminate that fear?
SPEAKER_01Aaron Ross Powell That is the million-dollar question.
SPEAKER_00Aaron Powell Like, do we have hard data on this, or is this just theoretical management philosophy?
SPEAKER_01Aaron Powell We have incredibly hard data. And it actually takes us right back to that hospital scenario you mentioned at the start.
SPEAKER_00Oh, right. The counterintuitive hospital discovery. Let's get into that.
SPEAKER_01Aaron Powell So we have to look at the foundational academic research on psychological safety, specifically the groundbreaking work of Amy Edmondson from Harvard Business School.
SPEAKER_00Aaron Powell Amy Edmondson. Yeah, psychological safety is a term that gets thrown around so much on LinkedIn these days, and honestly, usually incorrectly.
SPEAKER_01Yeah, it's become a bit of a buzzword, unfortunately.
SPEAKER_00Aaron Powell So let's ground it for everyone. Based on Edmondson's research, psychological safety is a shared belief within a team that taking an interpersonal risk won't result in punishment.
SPEAKER_01Right. Meaning you can ask a seemingly stupid question or admit you made a mistake.
SPEAKER_00Or voice a totally half-baked idea. Or even raise a concern about a project that everyone else in the room seems to love.
SPEAKER_01Exactly. And Edmondson discovered the impact of this almost by accident back in the late 1990s.
SPEAKER_00When she was studying medical errors in hospitals?
SPEAKER_01Yes. And she started with a very logical hypothesis. Teams with better leaders, better training, and better relationships would make fewer errors.
SPEAKER_00Which, I mean, makes perfect sense. Better doctors should mean fewer mistakes.
SPEAKER_01Right. But the data came back completely backwards.
SPEAKER_00This is the crazy part.
SPEAKER_01The teams with the absolute highest performance ratings from the hospital administrators were actually reporting significantly more errors than the lower performing teams.
SPEAKER_00Which just blew her mind, right?
SPEAKER_01She was totally baffled. But when she dug into the qualitative data, the actual interviews, she realized the high performing teams weren't actually making more mistakes. They were just reporting them. Exactly. They were simply reporting them. Oh wow. The mechanics of it are just fascinating. In the high performing wards, if a nurse accidentally gave the wrong dosage of a pretty harmless medication, they would immediately flag it.
SPEAKER_00But we wouldn't hide it.
SPEAKER_01No. The team would gather, discuss what led to the mix-up, like maybe the labels on two different vials looked too similar, and they would fix the underlying systemic issue.
SPEAKER_00Because they felt psychologically safe enough to surface the error without fear of being fired or getting humiliated by the attending physician.
SPEAKER_01Exactly. Which means the teams with low psychological safety, the unsafe teams, were actively burying their mistakes.
SPEAKER_00Right. If they gave the wrong medication and the patient didn't immediately code, they just swept it under the rug.
SPEAKER_01Because they were terrified of the hierarchy.
SPEAKER_00Wow. And if you bury the small problems, you can never fix the underlying systemic flaws, which inevitably leads to catastrophic failures down the line.
SPEAKER_01Precisely. Now, if you're wondering if this applies to the corporate world, the Lateral Works research points to a massive internal study by a major tech company in 2012.
SPEAKER_00Oh yeah. They wanted to know the secret to building the perfect team.
SPEAKER_01Aaron Powell Right. And the scale of this study was wild. They didn't just survey a dozen people.
SPEAKER_00No, they analyzed 180 different teams across their global operations. They looked at over 250 different attributes.
SPEAKER_01Aaron Powell They analyzed personality types, educational backgrounds, how long people had been at the company.
SPEAKER_00Even whether they socialized outside of work, right? Right. And the budgets they had. They were hunting for this magic algorithm of team composition.
SPEAKER_01And they assumed the best teams would be the ones with the highest concentration of individual geniuses. Like put all the smartest people in a room and you win.
SPEAKER_00But the result was definitive.
SPEAKER_01Very definitive. Yeah. Psychological safety was the absolute strongest predictor of team performance. It outranked literally everything else.
SPEAKER_00That's incredible.
SPEAKER_01It didn't matter if a team was made up of average engineers or brilliant PhDs. If the average team had high psychological safety, they consistently outperformed the team of geniuses who lacked it.
SPEAKER_00Because the geniuses were too busy of protecting their egos and avoiding interpersonal risk to actually innovate.
SPEAKER_01Exactly. They were playing defense.
SPEAKER_00But I do want to pause here and clarify something crucial. Because I think a lot of leaders misunderstand this concept. Psychological safety does not mean just being nice.
SPEAKER_01It absolutely does not. And honestly, that is the most dangerous misinterpretation of the research.
SPEAKER_00Aaron Powell Right. It's not about lowering your standards or removing accountability. It's not a drum circle where everybody gets a participation trophy.
SPEAKER_01Aaron Powell Not at all. A psychologically safe environment is actually one where candor is so intensely normalized that people can have incredibly hard, uncomfortable conversations.
SPEAKER_00Aaron Powell To visualize this, the Lateral Works best practices break team dynamics down into different zones. And the one we all want to reach is the learning zone.
SPEAKER_01Aaron Powell The learning zone, yes. This is the intersection of high psychological safety and high accountability. Aaron Powell So it's both. Exactly. This is where teams take intelligent risks. They speak candidly, they debate fiercely, and they deliver exceptional results.
SPEAKER_00Aaron Powell And then the opposite of that, which I think a lot of companies accidentally build when they try to force fast time to market, is the anxiety zone.
SPEAKER_01Aaron Powell Right. The anxiety zone is low psychological safety combined with high accountability.
SPEAKER_00Aaron Powell In the anxiety zone, the pressure to deliver is immense, but the safety to make mistakes is basically zero.
SPEAKER_01Aaron Powell Yeah. Team members fear punishment, they hide their concerns, and the actual rate of learning and innovation just plummets because everyone is just trying to survive.
SPEAKER_00Aaron Powell The best way to think about the difference between these two zones is to look at professional sports or like gymnastics.
SPEAKER_01Oh, I love this analogy.
SPEAKER_00The anxiety zone isn't just a minefield. It's a tightrope suspended a thousand feet in the air without a net. You are held to a very high standard of accountability you have to walk the rope.
SPEAKER_01Right. You still have to perform.
SPEAKER_00But you are so hyper-focused on not falling to your death that you stick to the absolute safest, most basic routine possible.
SPEAKER_01You're definitely not trying anything new.
SPEAKER_00Never. You will never, ever attempt a new flip or a creative maneuver because the cost of failing is fatal.
SPEAKER_01That is exactly the mechanism.
SPEAKER_00The learning zone, on the other hand, simply puts a massive, highly secure net underneath that tightrope. You are still expected to perform at a world-class level. The accountability is still there.
SPEAKER_01But because the net exists, you have the psychological freedom to try the triple backflip.
SPEAKER_00Exactly. If you fall, you bounce back up and try again. The net doesn't lower the standard. It actually enables the highest level of performance.
SPEAKER_01So the practical question for any leader listening is how do you actually build the net? How do you practically move your teams from the anxiety zone into the learning zone?
SPEAKER_00Right. What are the actual steps?
SPEAKER_01Well, one approach highlighted in the Lateral Works research is the structural institutionalization of free time.
SPEAKER_00Oh, this is a famous one. We are talking about the percentage time concept.
SPEAKER_01Yes. There was a major search engine company that became incredibly famous in the early 2000s for this policy.
SPEAKER_00Aaron Powell Where employees were explicitly encouraged to spend 20% of their paid working hours exploring projects they personally believed would benefit the company.
SPEAKER_01Regardless of their actual job description.
SPEAKER_00Right. But what's really interesting is that while that tech company popularized it for the digital age, the historical roots of this practice are actually much older.
SPEAKER_01Yeah, it goes back to a 15% time culture developed like a massive material science company.
SPEAKER_00Aaron Powell Which originated during the intense pressures of World War II, right?
SPEAKER_01Trevor Burrus Exactly. Scientists were given discretionary time away from their primary military contracts to just experiment with synthetic alternatives.
SPEAKER_00And it was that exact 15% unstructured time that eventually led a scientist in the 1950s to invent the adhesive that gave us the ubiquitous office sticky note.
SPEAKER_01Aaron Powell Which is just an incredible origin story.
SPEAKER_00It really is. But looking back at that major search engine company with the 20% time, the outcomes weren't just cute office supplies. The unstructured time led to company reshaping innovations.
SPEAKER_01Massive outcomes. We are talking about the core architecture for their ad revenue engine, which drove billions in profit.
SPEAKER_00And a massive news aggregator that a single engineer started building as a side project to improve information flow right after 9-11.
SPEAKER_01Yeah. And the autocomplete feature that literally anticipates what you're typing into a search bar.
SPEAKER_00None of these came from top-down executive mandates. They all bubbled up from that 20% unstructured time.
SPEAKER_01But, and this is a big but, we have to look at the reality of execution.
SPEAKER_00The tensions of execution.
SPEAKER_01Right. As that search engine company matured, went public, and faced the relentless pressure of quarterly earnings calls, the reality of the 20% time began to warp.
SPEAKER_00Because the demands of daily execution just increased.
SPEAKER_01Exactly. Eventually, employees started jokingly referring to it as 120% time.
SPEAKER_00Ah. Because the company wasn't actually taking 20% of their workload away.
SPEAKER_01No. They were essentially saying you still have to hit 100% of your KPIs, and if you want to innovate, you can do that on your nights and weekends.
SPEAKER_00Which completely defeats the purpose.
SPEAKER_01It does. Internal reports eventually revealed that only about 10% of their engineers were actually utilizing the program with any consistency.
SPEAKER_00Wow, only 10%.
SPEAKER_01Yeah. It stopped being a universal company policy and just became this localized cultural quirk, entirely dependent on whether your specific middle manager was willing to give you the breathing room.
SPEAKER_00So as a listener trying to apply this to their own FTTM planning, what is the takeaway here? If the literal logistical math of 20% time failed for 90% of the company, should we just write the whole concept off?
SPEAKER_01No, absolutely not. The takeaway is understanding what the time actually represented.
SPEAKER_00Okay, unpack that.
SPEAKER_01Aaron Powell The literal logistical math wasn't the primary driver of the innovation. It was the cultural signal of decentralized trust. Aaron Powell A cultural signal. Right. By formalizing a policy that explicitly stated employees could and should explore ideas outside their strict job descriptions, leadership sent an unmistakable message.
SPEAKER_00Aaron Powell The message being we trust your intellect, and we know that we, the executives, don't have a monopoly on good ideas.
SPEAKER_01Aaron Powell Exactly. So even if an engineer never actually took a Friday off to work on a side project, just knowing that they were allowed to completely shifted their psychological safety.
SPEAKER_00That makes total sense. It's the explicit permission that matters.
SPEAKER_01Yes. However, the cautionary tale is that a cultural signal requires active, aggressive protection from the very top.
SPEAKER_00Because if senior leaders don't actively protect that space and adjust workloads to accommodate it, the short-term pressures of corporate survival will always crush it.
SPEAKER_01Always. And then the permission to innovate just becomes empty corporate jargon.
SPEAKER_00Let's pivot to a different approach then, because I can hear managers listening to this right now thinking there is no way I can give my team 20% of their time back. I'm already understaffed and missing deadlines.
SPEAKER_01Which is the reality for most people.
SPEAKER_00Right. So if you can't protect the time, the lateral works best practices outline another method. You strictly structure the method of ideation to protect the idea itself.
SPEAKER_01This is such a brilliant workaround for highly constrained environments. And one of the most powerful examples comes from a massive global e-commerce giant.
SPEAKER_00Yeah, they don't just ask for ideas. They force a very specific, rigid structure called the working backwards process.
SPEAKER_01Aaron Powell I'm obsessed with the mechanics of this.
SPEAKER_00It's so cool. So if a team at this company wants to pitch a new product, they cannot write code. They cannot build a prototype. They can't even make a PowerPoint presentation.
SPEAKER_01Right. None of that.
SPEAKER_00The very first thing they have to do is write a mock press release and an FAQ document dating it as if the product is launching today.
SPEAKER_01The psychology behind this is profound because it intentionally separates the act of creation from the act of evaluation.
SPEAKER_00Which is exactly what we were talking about earlier with the sequencing.
SPEAKER_01Exactly. When you sit down to write a press release, you are forced to write from the perspective of the customer. Why is this amazing? What specific problem does it solve? Why would anyone care?
SPEAKER_00You're forcing the team to live entirely in the learning zone for the duration of that draft. They get to dream big about the ideal state without the finance guy in the back of the room yelling about server costs.
SPEAKER_01That's exactly it. By separating the creative, expansive act of imagining the solution from the analytical, restrictive questions of feasibility, you let that little sprout grow a few inches.
SPEAKER_00But then the friction eventually comes, right? During the review of that document.
SPEAKER_01Well, absolutely. It is completely normal in this company for a team to write 10, 20, even 30 drafts of a single press release.
SPEAKER_0030 drafts.
SPEAKER_01Yeah, they will sit in a room for an hour debating a single sentence in the mock FAQ.
SPEAKER_00Because if the press release is boring or if the FAQ reveals a massive flaw in the customer experience, you kill the project right there.
SPEAKER_01Right then and there.
SPEAKER_00It's like forcing an author to write the glowing backcover blurb of a novel before they are allowed to write chapter one. If you read the blurb and realize the plot is terrible, you just save them a year of typing.
SPEAKER_01That's a perfect way to look at it. And crucially, in this culture, discovering that an idea fails during the paper phase is actually celebrated.
SPEAKER_00Wait, celebrated. Really?
SPEAKER_01Yes. It is not viewed as a failure of the team. It is a massive success of the system.
SPEAKER_00Aaron Powell Ah, because they succeeded in killing a bad idea when it only cost a few dozen hours of writing rather than tens of millions of dollars in software development.
SPEAKER_01Exactly. And this gets to the heart of the velocity of decisions required for FTTM. The Lateral Works research points out a mental framework this company uses to categorize risk.
SPEAKER_00Right, the type one versus type two decisions framework.
SPEAKER_01Yes. Type one decisions are highly consequential and practically irreversible. Think of them like walking through a heavy door that instantly locks behind you.
SPEAKER_00Like if you launch a brand new hardware device that's a type one decision, the supply chain is set, the money is spent.
SPEAKER_01Exactly. Those decisions require incredibly slow, careful, heavy deliberation.
SPEAKER_00But type two decisions are entirely reversible. They are low risk.
SPEAKER_01Right. You walk through the door, look around the room, and if you realize you made a mistake, you just turn around and walk back out.
SPEAKER_00So the brilliance of the working backwards framework is that it empowers teams to treat the terrifying process of innovation not as a massive bet the company type one decision.
SPEAKER_01But as a series of fast, reversible type two experiments.
SPEAKER_00Drafting a press release is a type two decision. Debating an FAQ is a type two decision. You are exploring the room without locking the door.
SPEAKER_01Exactly. It's a structured safe space.
SPEAKER_00Okay, so we've covered how to capture the idea and protect it in its infancy. But eventually, you do have to subject it to the rigor. You have to review it.
SPEAKER_01You do.
SPEAKER_00So how do you bring the hammer down and stress test the concept without the creator feeling personally attacked and retreating right back into that anxiety zone?
SPEAKER_01Aaron Ross Powell Well, to understand this, we look at a radical model of peer review used by one of the most successful renowned animation studios in history.
SPEAKER_00Okay, let's talk about that.
SPEAKER_01When they have a film in development, the director has to present storyboards and early reels to a specific reviewing body made up of their trusted peers.
SPEAKER_00Like other directors, writers, and animators.
SPEAKER_01Right. And to make this work, the studio instituted two non-negotiable rules.
SPEAKER_00Rule number one, no authority. This one honestly blew my mind.
SPEAKER_01It's radical. The reviewing committee can diagnose problems. They can point out that the second act drags, or a character's motivation doesn't make sense, or a joke just isn't landing.
SPEAKER_00But they absolutely cannot prescribe solutions and they cannot mandate changes. The director of the film maintains total 100% control over the project.
SPEAKER_01Which naturally leads to rule number two: candid but constructive feedback.
SPEAKER_00Candid but constructive.
SPEAKER_01Yes. The feedback must focus entirely on the work itself, actively separating the ego of the creator from the flaws of the project.
SPEAKER_00So the language used in the room is critical.
SPEAKER_01Exactly. It is never you are failing to tell a good story. It is this specific sequence lacks emotional resonance.
SPEAKER_00And to insulate the creator's ego even further, the studio actively normalizes the rough start.
SPEAKER_01Yes, this is key.
SPEAKER_00They have an explicit, loudly broadcasted philosophy that all of their projects, every single one of their billion-dollar blockbuster movies, start out terribly.
SPEAKER_01By explicitly stating that early work is supposed to be flawed, messy, and broken, they completely remove the stigma of presenting imperfect ideas.
SPEAKER_00You don't have to get defensive about a bad first draft because the culture dictates that first drafts are inherently bad.
SPEAKER_01Exactly. And we know that this isn't just a magical cultural anomaly tied to this one specific studio, because there is a real-world case study of this exact model being transplanted.
SPEAKER_00Oh, right. When the leaders of this animation studio were brought in to revitalize a failing legacy animation studio that had been producing duds for years.
SPEAKER_01Right. And they didn't just fire all the animators, they changed the structure. Trevor Burrus, Jr.
SPEAKER_00They eliminated the executive mandates, they transplanted this exact peer review model, they rebuilt the psychological safety, and they gave creative control back to the directors.
SPEAKER_01And the result was an immediate string of massive blockbuster hits from the legacy studio. It proves this is a highly replicable structural solution.
SPEAKER_00Aaron Powell But hold on, I have to stop and ask the obvious question here.
SPEAKER_01Sure, go ahead.
SPEAKER_00If the reviewing committee has no actual authority to force a change, what stops a stubborn director from just ignoring everyone, crossing their arms, and making a terrible movie anyway?
SPEAKER_01It's a fair question.
SPEAKER_00Like why wouldn't they just say, thanks for the feedback, but I'm doing it my way, and sink the company's money?
SPEAKER_01That is the crucial tension of the model. And it is exactly where the high accountability aspect of a learning zone comes into play.
SPEAKER_00Okay, explain that.
SPEAKER_01You aren't just giving them total freedom and walking away. You are building an environment where the trust and the shared intense commitment to excellence compel the creator to listen.
SPEAKER_00It's peer pressure, essentially, but the most positive, constructive version of it imaginable.
SPEAKER_01Exactly. When a group of incredibly talented peers, people whose work you deeply respect, people who you know want you to succeed, look you in the eye and say, this scene is not working. You listen.
SPEAKER_00The accountability isn't forced downward by a hierarchical mandate. It's driven laterally by mutual respect.
SPEAKER_01Right. It is much harder to ignore the brilliant peers you respect than it is to ignore an executive you think is out of touch.
SPEAKER_00That makes total sense. Okay, we've talked about billion-dollar tech innovations and massive Hollywood movies. Those are inherently creative fields. But what if I am a listener who runs a factory floor or a logistics hub? What about everyday operational fast time to market? Does this concept of psychological safety apply to blue-collar execution?
SPEAKER_01It absolutely does, and it manifests as the compound interest of microinnovations.
SPEAKER_00Aaron Powell Microinnovations. I like that phrase.
SPEAKER_01Yeah. The lateral works research highlights a global automaker that operates with a deeply embedded philosophy of continuous daily improvement.
SPEAKER_00Aaron Powell So they don't rely on periodic top-down efficiency initiatives where expensive consultants come in, change everything, and leave.
SPEAKER_01Exactly. They rely entirely on the daily observations of their frontline workers.
SPEAKER_00Aaron Powell And their metric for this is just staggering. They have had an employee suggestion system running continuously for over 70 years.
SPEAKER_01Aaron Powell And they implement roughly 90% of the ideas their employees submit.
SPEAKER_00Aaron Powell 90 percent. I mean, if you run a suggestion box in a typical corporate office, you are leveled to implement five percent.
SPEAKER_01Aaron Powell Right. But the reason the number is so high is that the automaker fundamentally values participation over magnitude. They aren't just looking for million-dollar ideas.
SPEAKER_00The Lateral Works best practices highlight a brilliant specific example of this philosophy in action, right?
SPEAKER_01Aaron Ross Powell Yes, the tour guide example. So there's a plant tour guide who walks the catwalks above the assembly line every day.
SPEAKER_00And she was annoyed that whenever she had to stop to explain something to a tour group, she had to set her heavy bag on the somewhat dirty floor.
SPEAKER_01Right. So she submitted a suggestion install inexpensive little hooks on the catwalk rails so she can hang her bag.
SPEAKER_00Now I want listeners to picture taking that suggestion to a traditional corporate finance committee.
SPEAKER_01Oh, they would laugh you out of the room.
SPEAKER_00A bag hook has zero financial return on investment. It does not speed up the assembly line, it does not reduce material waste, it does not save the company a single cent.
SPEAKER_01In a strict ROI-driven environment, that idea is rejected instantly.
SPEAKER_00But this automaker approved it and implemented it immediately.
SPEAKER_01And we have to unpack the mechanics of why they implemented it, because it is entirely about the psychology of contribution.
SPEAKER_00If a company rejects small ideas because they lack an immediate, measurable return on investment, they actively kill the habit of contribution.
SPEAKER_01Exactly. They are sending a very clear cultural signal. Your ideas are only valuable to us if they immediately generate cash.
SPEAKER_00But by implementing the bag hook, the automaker sent the opposite signal. We value you, we value your comfort, and most importantly, we value the process of you identifying a problem and proposing a solution.
SPEAKER_01It really is compound interest. The bag hook itself is just a penny in the bank. It doesn't matter.
SPEAKER_00But building the habit of looking for improvements makes the whole company rich over time.
SPEAKER_01Exactly. Yeah. Because if that tour guide is positively reinforced and conditioned to constantly scan her environment for problems and solutions, eventually she's going to notice a safety hazard. Trevor Burrus, Jr.
SPEAKER_00Or an efficiency bottleneck on the line. That does save the company millions of dollars. But if you shut her down over the bag hook, she never speaks up about the safety hazard.
SPEAKER_01That is the exact mechanism. Now, the next frontier of FTTM planning is asking what happens when an organization takes this internal culture of continuous safe contribution and turns it outward directly toward the customer.
SPEAKER_00This is where it gets incredibly strategic. The Lateral Works research details a major semiconductor company. They make the complex chips that power our devices.
SPEAKER_01Right. And they realized that their traditional one-to-one customer support model was simply too slow.
SPEAKER_00Where a customer calls a rep, the rep asks an engineer, and the rep calls the customer back. It was a massive bottleneck in their time to market.
SPEAKER_01So they completely shifted their model. They built a massive online community platform to connect over 60,000 design engineers, their end customers, directly with the internal product developers who are making the next generation chips.
SPEAKER_00Now, the technological aspect of building a forum is easy. The real story is the internal administrative hurdles they had to overcome.
SPEAKER_01Oh, it was a massive internal battle. To make this work, the leadership had to convince over 40 different division leaders to allow their absolute best, most expensive engineers to spend precious working hours answering public questions on a forum.
SPEAKER_00Just think about the level of trust that requires from management. You are letting your engineers speak publicly, unscripted, directly to the market.
SPEAKER_01It's terrifying for most companies.
SPEAKER_00You are trusting that open, unvarnished dialogue, even if a customer points out a flaw in a ship or an engineer admits they don't have an immediate answer, will ultimately strengthen the relationship with the customer.
SPEAKER_01Most companies are terrified of unscripted external communication.
SPEAKER_00And perhaps the most difficult hurdle of all was protecting the space once it actually became successful.
SPEAKER_01Yes. The leadership team had to actively fight the immense urge to monetize the platform.
SPEAKER_00Let's pause on that because the temptation must have been agonizing. Put yourself in the shoes of a C-suite executive at the semiconductor company. The pressure from the sales and marketing departments to plaster that form with ads, to push sales materials, to turn every interaction into a lead generation funnel would just be overwhelming.
SPEAKER_01Completely overwhelming.
SPEAKER_00How do you actively look at that and say, no, we are not going to advertise to them?
SPEAKER_01It requires an incredible amount of discipline and a long-term strategic view. They recognized that they had to keep the platform a strict marketing-free zone to protect its core credibility.
SPEAKER_00Because if the external engineers using the platform ever felt they were being corralled into a sales funnel, the psychological safety of the community would instantly collapse.
SPEAKER_01Exactly. The authentic peer-to-peer sharing of technical problems would just stop overnight.
SPEAKER_00But by resisting the short-term sugar rush of monetization, they built a deeply trusted strategic asset that drove massive long-term customer retention and brand loyalty.
SPEAKER_01Okay, so we have covered a massive amount of ground here today. We've looked at search engines, e-commerce giants, animation studios, auto manufacturers, and semiconductor communities.
SPEAKER_00Let's distill all of these lateral work's best practices into a practical blueprint. Because when you look at all these highly successful companies, a clear pattern emerges for leaders trying to execute FTTM planning.
SPEAKER_01Right. The five principles for leaders. First, you absolutely have to understand that sequence matters. Encouragement must precede scrutiny.
SPEAKER_00You have to let the idea take a breath and gain some structure before you hit it with the heavy evaluation metrics.
SPEAKER_01Second, you must structurally separate the idea from the evaluation. Let your people advocate for their vision without feeling judged.
SPEAKER_00Whether you use tools like a mock press release or a non-authoritative peer review, you have to create a procedural buffer between the creator's ego and the project's flaws.
SPEAKER_01Third, make feedback a ritual, not a surprise. If a team is constantly looking over their shoulder, waiting for an executive ambush, they are in the anxiety zone.
SPEAKER_00But if they know exactly when, where, and how an idea will be reviewed, predictable feedback eliminates that ambush anxiety. They can prepare for it objectively.
SPEAKER_01Fourth, and this is absolutely critical for the executives listening, you must protect the space from above. Leadership has to defend the innovation process from short-term pressures.
SPEAKER_00Whether that means fiercely protecting discretionary time or keeping a community forum free of marketing, the space for fragile ideas will collapse if leaders don't actively guard it against the relentless demands of the current quarter.
SPEAKER_01And finally, principle number five, reward the process, not just the outcome. You have to respect the pivot and the failure.
SPEAKER_00If a team develops an idea, stress tests it, and ultimately kills it because they discover a fatal flaw, that is a massive success of the system. Celebrate the team for discovering the flaw early, and they will bring you another better idea tomorrow.
SPEAKER_01To make this incredibly concrete, let's look at a hypothetical project many of our listeners are probably working on or managing right now. Let's call it the Fire Zone Project.
SPEAKER_00Okay, the Fire Zone Project. For those who aren't in the weeds on this, Fire Zone represents that highly complex multi-departmental initiative sitting on your desk. It is an ambitious idea, but it is currently unproven.
SPEAKER_01Right. If you have a Firezone project, that is exactly the kind of concept that needs to be run to ground and refined rather than evaluated against final state criteria on day one.
SPEAKER_00You have to let the team discover where Firezone breaks and where it shines in order to build that innovation muscle.
SPEAKER_01Because if your very first question to the team is, what is the guaranteed three-year ROI of Firezone, you will kill it before you even know what it actually is.
SPEAKER_00And as we conclude this analysis, we have to recognize that the ultimate stakes here go far beyond the success or failure of any single project like Firezone.
SPEAKER_01Aaron Powell You have to connect this culture of innovation directly to the strategic retention of your best people.
SPEAKER_00Because the simple reality is that when talented driven people feel their ideas are constantly unwelcome, when they feel unsafe to speak up, they leave.
SPEAKER_01They absolutely leave.
SPEAKER_00That is the ultimate takeaway. The ROI of psychological safety isn't just about the cool new products you might eventually launch. It's a fundamental defensive strategy to keep your absolute best people from walking out the door.
SPEAKER_01The cost of recruiting, hiring, and training a replacement for a highly skilled, creative employee completely dwarfs the cost of creating a safe environment or funding a few early stage experiments that don't pan out.
SPEAKER_00True FTTM execution, getting the right product to market at the right time requires the operational bravery to let rough ideas breathe before you test them.
SPEAKER_01It is entirely about sequence, safety, and structured, rigorous feedback.
SPEAKER_00I want to leave you, the listener, with a final slightly provocative thought to mull over as you look at your own teams.
SPEAKER_01Oh, I love a good provocative thought.
SPEAKER_00We've spent this entire time talking about the dangers of the anxiety zone and the absolute necessity of building a net of psychological safety. But what happens when a culture gets too comfortable?
SPEAKER_01Interesting.
SPEAKER_00Is it possible to over-index on psychological safety and completely forget the high accountability piece of the equation? Could you accidentally build a culture where no one wants to hurt anyone's feelings, critical feedback entirely disappears, and terrible products accidentally launch simply because everyone was just too nice to point out the obvious flaws?
SPEAKER_01That is a real risk.
SPEAKER_00How do you keep the operational edge razor sharp while keeping the environment safe? It's something to think about. Thanks for listening. Make sure to tune in next week where we will dive deeper into key practices of FTTM teams.
