The Unicorn Project by Gene Kim

Title: The Unicorn Project: A Novel about Developers, Digital Disruption, and Thriving in the Age of Data
Author: Gene Kim
Year: 2019
Pages: 352

In a world where “digital transformation” is thrown around in boardrooms like a buzzword, The Unicorn Project cuts through the noise. It doesn’t lecture or theorize.

Instead, it tells the story of what really happens when systems are broken, teams are stuck, and talented people are buried under layers of process. But more importantly, it shows what’s possible when that starts to change.

Through Maxine’s journey, Gene Kim gives us a front-row seat to the messy, human, often frustrating work of rebuilding from the inside—and reminds us why it matters more than ever.

As a result, I gave this book a rating of 8.0/10.

For me, a book with a note 10 is one I consider reading again every year. Among the books I rank with 10, for example, are How to Win Friends and Influence People and Factfulness.

3 Reasons to Read The Unicorn Project

Rebuilding from Within

You’ll see how culture change really happens—not from top-down mandates, but from developers who care. It’s a reminder that you don’t need permission to fix what’s broken. And it shows how small acts of courage can spark real transformation.

Tech Meets Humanity

This isn’t just about systems and tools. It’s about people—how they think, how they struggle, and how they grow. You get an inside look at the emotional rollercoaster of working in a dysfunctional environment and what it takes to make work meaningful again.

A Wake-Up Call for Leaders

If you manage teams or run projects, this book will make you rethink how decisions are made. It challenges old-school thinking and shows how leaders can either block progress—or unlock it completely.

Book Overview

Imagine walking into work one day only to find you’ve been demoted, blamed for something that went wrong while you were on vacation, and reassigned to a project everyone secretly hopes they’ll never touch.

That’s how Maxine’s story begins in The Unicorn Project, and from that first moment, you can feel the tension of a system that’s been broken for a long time.

This isn’t just a novel about software or IT departments—it’s a story about how big, complex organizations lose their way, and how small teams with courage, clarity, and a deep belief in doing the right thing can change everything.

Set inside the fictional company Parts Unlimited, The Unicorn Project follows Maxine, a brilliant senior developer who finds herself exiled to the infamous Phoenix Project. From the outside, it’s just another large-scale digital initiative. But on the inside? It’s chaos. Teams can’t even build or test code. Everything takes weeks—or months. Developers spend more time begging for access than writing software. It’s a place where innovation goes to die.

But what makes this story powerful isn’t the dysfunction—it’s what happens next.

As Maxine slowly finds her footing, she stumbles into a group of engineers quietly working to fix what’s broken. They call themselves “The Rebellion.” They don’t have power, or funding, or permission.

What they do have is vision, grit, and a shared sense of urgency. Instead of waiting for approval, they start doing what they know is right: building tools that work, cutting through red tape, and focusing on the basics—like making sure developers can actually do their jobs.

What follows is a transformation—not just of technology, but of people. Through the ups and downs, long nights, and near-disasters, Maxine and her team begin to reimagine how the company builds software. They create platforms that simplify access to data.

They design systems that can scale. And perhaps most importantly, they rebuild trust between teams that had long stopped talking to each other.

Underneath the storytelling, Gene Kim lays out five core principles—The Five Ideals—that quietly guide the entire journey. These aren’t abstract values. They’re practical, lived experiences that show up in every bottleneck, every breakthrough. Locality and Simplicity. Focus, Flow, and Joy. Improvement of Daily Work. Psychological Safety. And Customer Focus.

You see them not as bullet points, but in action—when Maxine helps QA engineers feel like part of the team, when a testing bottleneck gets fixed not by a tool, but by a donut-fueled conversation, when leaders finally pause to fix the foundations instead of shipping yet another broken feature.

What makes The Unicorn Project so compelling is that it doesn’t present transformation as a top-down initiative. It’s bottom-up. It’s messy. It’s driven by people who care deeply about the craft of building great systems and who are tired of watching good ideas die in a sea of bureaucracy.

And that’s why the story resonates so much today.

In an era where every company is trying to “go digital,” many forget that true innovation isn’t about adopting new tools—it’s about changing how we work. The Unicorn Project shows what that really looks like. It’s not glamorous.

It’s a developer waiting weeks to get access to a test environment. It’s teams stuck in approval loops that kill momentum. It’s managers so far removed from the work that they measure success by how many meetings they’ve scheduled instead of how much value they’ve delivered.

But the flipside? When companies invest in developer experience, when they make work visible, when they reduce friction and give people the freedom to solve problems—everything changes. Products ship faster. Teams smile more. Customers notice.

By the end of The Unicorn Project, Maxine’s once-doomed company becomes a rising star. Their mobile app wins awards. Their data platforms become industry benchmarks. The Rebellion? No longer a fringe group. They become the heart of the company’s success. And Maxine? She becomes the first Distinguished Engineer in company history—a title that recognizes not just technical brilliance, but the ability to make everyone around her better.

The Unicorn Project isn’t just fiction—it’s a mirror. If you’ve ever worked in a large organization, you’ll probably see yourself in these pages. You’ll nod in recognition. You’ll laugh in frustration. And maybe, just maybe, you’ll feel inspired to fix one small thing that’s been bothering you for too long.

Because as Maxine proves, real change doesn’t always start with a grand strategy. Sometimes, it starts with someone saying, “This doesn’t make sense—let’s fix it.”

And when enough people say that out loud, a rebellion isn’t far behind.

One of the most powerful frameworks in The Unicorn Project is something Gene Kim calls The Five Ideals.

They’re not buzzwords or abstract values—they’re lived principles that show up in the small, daily choices teams make. And when they’re missing, things fall apart.

When they’re present, teams move faster, feel better, and build things that actually matter.

Let’s take a closer look at what each Ideal really means—starting with the first one Maxine bumps into almost immediately.

The First Ideal: Locality and Simplicity: If you’ve ever had to touch ten systems just to fix one bug, you already understand this one. Locality is about being able to make changes in one place without having to unravel the whole sweater. Simplicity is about reducing unnecessary complexity, not just in code but in how decisions are made, how systems interact, and how work flows. In the early chapters, Maxine can’t even compile her code—let alone test it—because the system is so tangled. Nothing is local. Everything requires going through someone else. The result? Slowness, frustration, and a system where even small changes feel dangerous. The First Ideal reminds us that when things are simple and contained, teams can move quickly and confidently.

The Second Ideal: Focus, Flow, and Joy: This one feels deeply human. It’s not just about productivity—it’s about how people feel while they work. When you’re constantly context-switching, stuck waiting for approvals, or fighting fires from bad deployments, there’s no space for flow. Focus disappears. Joy fades. And yet, when Maxine finally gets into the zone—solving a race condition, pairing with teammates, shipping something useful—you can feel the energy come back. Flow isn’t a luxury. It’s a signal that the system is healthy. And joy? That’s what makes great developers stay and grow. The Second Ideal challenges companies to stop treating developer happiness as “nice to have” and start recognizing it as a competitive advantage.

The Third Ideal: Improvement of Daily Work: This Ideal hits home for anyone who’s ever thought, “There has to be a better way.” Improvement shouldn’t be an afterthought. It should be part of the work itself. But too often, teams are so busy chasing deadlines that they never stop to fix the things that slow them down. In The Unicorn Project, the turning point comes when leadership calls a feature freeze—giving teams space to clean up technical debt, improve build pipelines, and make the work smoother. It’s a game-changer. The Third Ideal says: don’t just ship more—make shipping better. Because every small improvement compounds, and over time, it’s the difference between barely surviving and consistently thriving.

The Fourth Ideal: Psychological Safety: This is the quiet foundation that holds everything else up. Without psychological safety, people stay silent. They don’t share concerns, they don’t take risks, and they certainly don’t admit mistakes. And when that happens, the system decays—even if no one sees it at first. One of the most heartbreaking moments in The Unicorn Project is when a network engineer is fired after working himself into exhaustion. It sends a chilling message: don’t fail, or you’re out. But great teams don’t work like that. They learn, together. They recover from mistakes. They improve because it’s safe to be real. The Fourth Ideal invites leaders to stop managing through fear and start creating environments where people can speak up, try things, and grow.

The Fifth Ideal: Customer Focus: At the end of the day, none of this matters if it doesn’t serve the customer. But when teams are buried in internal politics, outdated processes, and endless firefighting, the customer becomes an afterthought. The Fifth Ideal flips that. It asks: what does the customer need right now? How do we deliver that—not next quarter, but this week? In The Unicorn Project, Maxine’s team starts to win because they focus on delivering real outcomes: faster delivery, better personalization, smarter data. Not just features, but value. The Unicorn Project reminds us that every line of code should bring us closer to solving a real problem for a real person.

Together, the Five Ideals form the heart of the story—not just as concepts, but as lived experiences. You see what happens when they’re missing.

You feel the impact when they’re honored. And by the end of The Unicorn Project, it’s clear: if you want to build a high-performing tech organization, you don’t need a massive playbook.

You just need to fight for these five things—over and over again, in every meeting, every deployment, and every decision.

Chapter by Chapter

Part 1 – The Fall and the Frustration

The story kicks off with Maxine coming back from what should’ve been a refreshing vacation. But instead of catching up with her team or easing back into work, she walks straight into a disaster. There’s been a massive payroll outage, and somehow… she’s being blamed for it. Never mind that she was literally out of the country at the time—it doesn’t matter. Leadership needs someone to take the fall, and Maxine just became that someone.

So, what’s her punishment? She’s being sent to the Phoenix Project. And if you’re new to Parts Unlimited, here’s what you need to know: Phoenix is where good developers go to suffer. It’s three years late, $20 million over budget, and has become a graveyard of half-finished work and broken spirits. People don’t want to talk about it. They just hope not to be assigned to it.

Naturally, Maxine is furious. Not just because of the blame game, but because she genuinely cares about doing great work. She’s known for taking on impossible problems and solving them with style. She’s not someone who gives up easily. So, even though she’s being dumped into Phoenix like excess luggage, she walks in determined to make sense of the chaos.

What she finds is worse than she imagined.

No one can do a build. New developers can’t even get started. There’s no documentation. No tools. No clear path to get anything working. It’s like being handed a box of IKEA parts without the instructions—or the screws. For someone like Maxine, who thrives on solving problems, this is maddening. She spends hours chasing down passwords, digging through outdated wiki pages, and asking for access to servers no one seems to own. And after days of effort? Still nothing works.

It’s not just about the tech. The culture is broken too. The office is dead silent. Developers are isolated, overworked, and clearly burnt out. There’s no energy. No joy. People are just… surviving. And that’s when it hits her: this isn’t just a struggling project—it’s a warning sign.

One of the best moments is when Maxine accidentally says “Good luck, chumps” out loud during a high-level stakeholder meeting. Everyone hears it. Her boss buries his face in his hands. But surprisingly, someone actually listens. For a second, the curtain is pulled back, and people stop pretending everything’s fine. It’s awkward, yes—but it’s also real.

By the end of Part 1, Maxine is still stuck. No progress. No build. Just a growing list of things she needs but can’t get. And yet, she doesn’t quit. Because beneath all the frustration, there’s still that drive. She knows things don’t have to be this way. She’s seen better. She’s done better. The question now is—can she help this mess of a project turn things around?

Part 1 sets the stage perfectly. It shows us just how bad things have gotten—technically and culturally.

But it also introduces us to Maxine, someone who refuses to settle for “this is just how it is.” And that’s where the real story begins.

Part 2 – Finding Flow in the Chaos

Part 2 picks up right where the frustration left off. But this time, something shifts: Maxine and her team finally start seeing cracks in the old system—and opportunities to build something better.

It all starts when Kurt, the always-enthusiastic and surprisingly resourceful manager, lands a new role leading the Data Hub team. And the best part? He brings Maxine along with him. Now, that might not sound exciting at first—Data Hub is seen as the root cause of the Phoenix Project disasters. But Maxine sees something different: a system that connects everything. Boring? Maybe. Essential? Definitely.

Data Hub is where the real work happens. It connects product catalogs, pricing, inventory, orders, finance—you name it. But it’s been neglected for years. It’s made up of a spaghetti mix of technologies, some written decades ago, and nobody wants to touch it. Maxine jumps in with Tom, one of the senior developers, and they quickly discover just how messy things really are.

But instead of complaining, Maxine gets to work.

She solves a nightmare bug—a race condition—that’s been haunting the team for weeks. And she doesn’t just fix it; she rewrites the code using functional programming principles, making it simpler, safer, and more elegant. It’s one of those moments that shows how much better things could be. For a second, there’s joy. There’s flow. But then reality crashes back in.

They can’t test the code. They don’t have access to the test environments. QA owns all of it, and the developers are left waiting in line. Testing Day only happens once a week, and they won’t even get feedback for two more. Deployment? That could take seven weeks—if everything goes right. Maxine goes from victorious to deflated in minutes. It’s like building a beautiful car but never being allowed to drive it.

This is where the Second Ideal—Focus, Flow, and Joy—hits hard. Maxine realizes that writing good code is just one piece. The real value is in delivering it to customers, and she’s completely blocked.

Still, she doesn’t give up. Instead, she starts building relationships.

She throws a donut-fueled Testing Day party to meet the QA team in person. It’s awkward at first, but it works. She listens to their frustrations and sees that QA isn’t the enemy—they’re stuck in the same broken system too. Turns out, everyone wants the same thing: better environments, more stability, and fewer surprises.

Meanwhile, leadership finally does something radical: they call a feature freeze. For 30 days, no new features. Just defect fixing and technical debt cleanup. They call it Project Inversion, and it’s a rare chance to fix what’s broken underneath the surface. It’s exciting—but also chaotic. Some managers ignore the freeze, trying to keep hitting deadlines. Others, like Maxine and her growing “Rebellion,” embrace it as a turning point.

At Dockside, the after-hours meeting spot, the group starts dreaming big. What if developers could actually test their own code? What if they could deploy on their own? What if build environments were standardized and didn’t take weeks to set up?

Erik, the wise mystery man, reappears with stories that shift everyone’s mindset. He talks about Amazon, Microsoft, and even Nokia—how some companies transformed through massive internal rebuilds, while others collapsed under the weight of their technical debt. His point is clear: if you don’t fix the foundations, the house will fall.

Then comes the Third Ideal—Improvement of Daily Work. Erik explains that systems should support the people doing the work, not get in their way. He compares it to Toyota’s famous “Andon cord,” where anyone on the line can stop production to fix a problem. That kind of culture makes continuous improvement possible. Without it, you’re just repeating the same mistakes.

And just when you think the philosophy lesson is done, Erik drops the Fourth Ideal—Psychological Safety. This hits hard after a network engineer is fired for a mistake made after working four nights in a row. Everyone is horrified. Because they all know: that could’ve been any of them. The culture of blame, fear, and silence isn’t just toxic—it’s dangerous. People can’t innovate or improve if they’re afraid of being punished for trying.

By the end of Part 2, Maxine’s not just writing code anymore. She’s part of something bigger. A movement.

A rebellion. A team of engineers trying to change the system from within—not by asking for permission, but by doing the right thing, together.

Part 3 – Courage, Chaos, and the Rise of the Unicorns

Part 3 is where the Unicorn Project really starts to earn its name. The team isn’t just fixing things anymore—they’re building. Fast. Boldly. Sometimes recklessly. And for the first time, it feels like they might actually win.

It all begins with something simple but symbolic: a name. “The Rebellion” becomes The Unicorn Project, a playful but powerful rebranding that signals they’re not just a rogue group anymore—they’re a movement. A team with a mission. And that mission? To save Parts Unlimited by turning a tangled mess of tech into something that actually delivers value.

But the stakes couldn’t be higher.

With Black Friday looming, Maxine and her team are racing against time. They’re not just building features—they’re reinventing core systems. Enter Narwhal, the new API gateway and data platform. It’s meant to simplify how teams access and use data. No more silos. No more six-week delays. Just clean, usable data where and when it’s needed. Sounds great, right?

Well, here’s the twist: to make it work, they have to bet everything on NoSQL, a tech they’ve never used in production at this scale. Maxine is nervous. The team is nervous. But in the end, they burn the ships and go all-in. There’s no turning back.

It’s risky. But it’s working—mostly.

The team begins preparing for a massive promotion campaign using real-time personalization. Data scientists are finally looped in (a bit too late), and they uncover a problem: the infrastructure they’ve built can’t handle the scale and complexity of the analytics needed. Narwhal, for all its speed, wasn’t made for these kinds of queries.

That’s when Shannon steps up with a wild idea: a Spark-like big data platform powered by streaming events—something only the tech giants usually attempt. It sounds crazy, but it’s exactly what they need. And just like that, Project Panther is born.

With Panther feeding Orca (analytics) and Narwhal handling APIs, the architecture starts to resemble something from a modern tech company. Data becomes fast, flexible, and accessible. And the results? Well, they’re finally something to brag about.

During Demo Day, the entire organization gets to see the magic unfold. Promotions are targeted, smart, and profitable. The mobile app team (long neglected) delivers features that actually work—like showing in-store inventory and personalized product bundles. Everyone is blown away. Even execs start to believe. It’s a rare corporate moment where you can almost feel the momentum shift.

But Maxine knows better than to celebrate too early.

They run a one-percent customer launch before Black Friday, and it nearly derails everything. A tiny, ancient back-end system (of course) can’t handle the load. Orders stall. Apps crash. Everyone panics. But Wes—grumpy, battle-hardened Wes—leads the charge. The team rallies, patches the issues, and recovers in time. The test ends up being a massive success, with the highest conversion rates they’ve ever seen.

Just as they start prepping for the full-scale launch, Sarah (still clinging to old ways) tries to crack down. She complains about people reading The Unicorn Project at work and demands mandatory overtime. It’s a hilarious and infuriating moment, showing just how disconnected some leaders still are. But Kurt and Maxine know the truth: you don’t win by working harder. You win by working smarter. By learning. By improving daily work. And by creating safe spaces for teams to thrive—even if that means someone’s reading a book.

And then… Black Friday.

Everyone is in by 3:30 a.m. The rooms are packed. Monitors are lit up. Metrics are flowing. The launch starts. Traffic surges. Sales climb. Until—again—something breaks.

A minor shipping API fails, and suddenly people can’t check out. It’s another moment of chaos. But this time, the team doesn’t panic. They swarm the problem, adjust the logic, and push a fix. Then, just as things begin to stabilize, the servers themselves start to crash under the load.

It’s a mess. A glorious, terrifying, real-time test of everything they’ve built. But somehow, through a thousand small adjustments, they keep the system alive. And in the end? It works. The numbers are jaw-dropping. Sales explode. Customers respond. And for the first time in a long time, everyone—Maxine, Kurt, Maggie, Brent, even Brent—is smiling.

Part 3 is about courage. It’s about what happens when teams are trusted to solve problems instead of waiting for permission. It shows how the right culture, combined with strong technical foundations, can unlock unbelievable speed and creativity.

And most of all, it proves that greatness isn’t reserved for unicorn startups. It can happen in century-old companies too—if they’re willing to change.

Epilogue – The Rebellion Wins

One year later, everything has changed.

Maxine walks out of a Town Hall meeting beaming. The company she was once exiled in is now thriving—and she had a huge hand in making that happen. Parts Unlimited has become one of the most innovative names in the industry, and people are noticing.

The tech organization? It’s nearly doubled in size. Engineers aren’t hiding in the background anymore—they’re front and center, speaking at conferences, showing off their work, and attracting talent from all over the country. They’ve even started open-sourcing some of their internal tools, turning what used to be behind closed doors into something the entire industry can use. Just like the tech giants do.

And yes, Maxine’s infamous enemies—the TEP and LARB committees—are officially gone. She even has a “Lifetime Achievement Award” on her desk for killing them. Signed by the entire Rebellion.

But it’s not just about recognition. It’s about real results.

The engine sensor product? A runaway hit. They sold nearly 200,000 units and made $25 million in revenue. The thing that surprised everyone, though, was why people were buying them. It wasn’t just the sensor—it was the app. Customers loved it. So much so that they cleared shelves across stores and online. It even brought in a whole new generation of customers—young, tech-savvy folks who had never set foot in a Parts Unlimited store before.

Now, they’re planning something even bigger. Maxine and her team are exploring subscriptions, new customer segments like car rental fleets, and even an Uber-style network for mechanics. There’s talk of acquiring the sensor manufacturer outright, which could unlock a $100 million business within a few years.

And it’s not just the sensor. The four-hour delivery project, once dismissed, is booming. Revenue is climbing fast, and the sales team loves it. What was once a startup competitor is now an afterthought—Parts Unlimited beat them at their own game.

But the best part?

Maxine gets promoted. She becomes the first Distinguished Engineer in company history. Her new job? Help create a culture of engineering excellence, meet with leadership regularly, and make sure the company keeps shipping great ideas—wherever they come from. And she doesn’t have to become a manager to do it. It’s recognition not just of her work, but of the value of individual contributors everywhere.

Across the board, the company is evolving. QA is no longer a silo. Ops is transforming into a platform team. Legacy apps are being cleaned up or retired. And leaders like Kurt and Patty are moving into bigger, bolder roles, helping scale the success across the organization.

Even Sarah—the once-dreaded antagonist—sits down for lunch with Maxine. It’s awkward, yes. But real. Maybe even a new start.

The Rebellion has won. But more than that—they’ve reshaped what success looks like.

Erik, always the sage, sums it up beautifully. He says the real unicorns aren’t just startups. They’re the sleeping giants—companies with deep customer relationships, infrastructure, and resources—who finally wake up and start moving fast. And when those giants combine speed with scale? That’s where the magic happens.

Parts Unlimited is now valued at more than double what it was a year ago. Wall Street analysts are impressed. Private equity folks are asking how they pulled it off. And Steve, the once-underestimated CEO, now keeps a photo album of the company’s most important people—including Maxine, Kurt, Brent, and Shannon—by his bedside.

In the final toast at Dockside, Maxine raises her glass and says it loud and clear:

“As the Rebellion, we set out to overthrow the ancient, powerful, and unjust order! And against amazing odds, I think we’ve actually done it!”

They cheer. Because they know it’s true.

The Unicorn Project wasn’t just about tech. It was about people. Culture. Courage. And the belief that when you give smart, passionate folks the right environment—they can change everything.

4 Key Ideas from The Unicorn Project

The Five Ideals

These guiding principles—Locality, Flow, Daily Improvement, Safety, and Customer Focus—aren’t just slogans. They’re lived out through real situations that show why they matter. They give teams a shared language to fix what’s broken.

The Rebellion

Change didn’t come from a task force or a strategy deck. It started with a handful of engineers quietly working together to do the right thing. Their actions show how real change begins—by solving problems, not asking for permission.

Fix the Foundations

Instead of piling features on broken systems, the team pauses to fix what matters: build environments, testing, and deployment. It’s a radical shift that pays off. This idea flips the “deliver more, faster” mindset on its head.

Developer Experience Matters

When engineers can’t build, test, or deploy quickly, everything suffers. The Unicorn Project makes it painfully clear: if you want innovation, you need to remove the friction that slows people down. The best ideas die when they can’t be shipped.

6 Main Lessons from The Unicorn Project

Change What You Can

You might not control the system, but you can fix one thing today. Small improvements ripple outward. Don’t wait for permission—start where you are.

Create Psychological Safety

Teams can’t improve if people are afraid to fail. Make it safe to speak up, try new things, and admit mistakes. Trust is the real engine of progress.

Work With the Willing

Not everyone will get it. That’s okay. Find the people who want to make things better and start there. Change spreads faster when it starts with shared belief.

Value Daily Work

The small things we do every day shape the big outcomes. Don’t just focus on flashy deliverables—look at how people work. Improve the path, not just the goal.

Connect Business and Tech

The best results come when developers understand the business, and business leaders understand the tech. Stop talking past each other—start solving together.

Speed Beats Size

The story proves that being fast and focused beats being big and slow. Agility isn’t about process—it’s about mindset. The teams that win are the ones who learn and move quickly.

My Book Highlights & Quotes

“… Trying to get a Phoenix to build going is like playing Legend of Zelda, if it were written by a sadist, forcing her to adventure far and wide to find hidden keys scattered across the kingdom and given only measly clues from uncaring NPCs. But when you finally finish the level, you can’t actually play the next level—you have to mail paper coupons to the manufacturer and wait weeks to get the activation codes…”

“… There’s a very real cognitive and spiritual burden of having to carry so many unfulfilled promises forever into the future, where anyone can ask at any time ‘Where is my feature?’…”

“… Punishing failure and “shooting the messenger” only cause people to hide their mistakes, and eventually, all desire to innovate is completely extinguished…”

“… While the redshirts battle to contain the raging engine fire that is threatening the entire ship, the bridge officers continue to cover their asses…”

“… If there’s any time that deserves courage and relentless optimism, it’s now…”

“… Innovation and learning occur at the edges, not the core. Problems must be solved on the front lines, where daily work is performed by the world’s foremost experts who confront those problems most often…”

“… Microsoft still has a culture that if a developer ever has a choice between working on a feature or developer productivity, they should always choose developer productivity…”

“… Everyone around here thinks features are important because they can see them in their app, on the web page, or in the API. But no one seems to realize how important the build process is. Developers cannot be productive without a great build, integration, and test process…”

“… It is ignorance that is the mother of all problems, and the only thing that can overcome it is learning…”

“… As Sensei W. Edwards Deming once observed, a bad system will beat a good person every time…”

“… For the leader, it no longer means directing and controlling, but guiding, enabling, and removing obstacles…”

“… There’s something even more important than code: the systems that enable developers to be productive, so that they can write high-quality code quickly and safely, freeing themselves from all the things that prevent them from solving important business problems…”

Conclusion

The Unicorn Project isn’t just a book about software—it’s a book about how organizations come back to life.

It’s messy, it’s real, and it’s full of those moments we’ve all experienced when we know something isn’t working but don’t know how to fix it.

Through Maxine’s story, we get a rare window into what it takes to rebuild not just systems, but trust, flow, and momentum.

And in a world that’s moving faster than ever, this book might be exactly the reminder we need—that the future belongs to those who are willing to rethink everything and start doing the hard, human work of change.

If you are the author or publisher of this book, and you are not happy about something on this review, please, contact me and I will be happy to collaborate with you!

I am incredibly grateful that you have taken the time to read this post.

Support my work by sharing my content with your network using the sharing buttons below.

Want to show your support and appreciation tangibly?

Creating these posts takes time, effort, and lots of coffee—but it’s totally worth it!

If you’d like to show some support and help keep me stay energized for the next one, buying me a virtual coffee is a simple (and friendly!) way to do it.

Do you want to get new content in your Email?

Do you want to explore more?

Check my main categories of content below:

Navigate between the many topics covered in this website:

Do you want to check previous Book Notes? Check these from the last couple of weeks:

Book Notes #127: The Laws of Simplicity by John Maeda2025-04-04
Book Notes #126: Inevitable by Mike Colias2025-03-24
Book Notes #125: Revenge of the Tipping Point by Malcolm Gladwell2025-03-21
Book Notes #124: Radical Candor by Kim Scott2024-09-04
Book Notes #123: The Personal MBA by Josh Kaufman2024-05-09