I Finally Published the Book
This post is part of my Medium blog.
I spent several years not publishing Redundant. There was always a reason to wait — find an agent, revise the opening chapters, prepare a query letter explaining why this particular novel about technology and organizations deserved shelf space alongside the ones already sitting on somebody's desk.
Eventually I ran out of patience for that. Redundant, the first book in The Condition Set trilogy, is available now.
A few things should be said up front.
The companies are fictional. The characters are fictional. This isn't a thinly disguised account of a former employer or a client whose name I changed for legal comfort. And Rob Coleman is not me — not an idealized version, not the version who says the right thing in the meeting instead of thinking of it twenty minutes later in the car. He's a character.
But the work he does is real.
I spent six or seven years talking to a lot of people who do FinOps across a lot of companies. After a while, you stop treating each problem as unique. The names change. The cloud providers change. The org charts change. The same patterns keep surfacing in different configurations.
People are asked to explain costs they don't control. Teams are given responsibility without authority. The person who actually understands the numbers gets invited to the meeting after the decision has already been made. FinOps is expected to be accurate, useful, diplomatic, and quiet — usually all at once.
Those aren't stories about one company. They're structural patterns, and they repeat.
Redundant is built on those patterns, but it's not a business book with the nouns swapped out. I can't stand those — the corporate novella where every character exists to demonstrate a job title and every conflict resolves into a management lesson. That's one of the fastest ways to make me stop reading.
The book opens with Rob summoned to a meeting of the company's vice presidents. He's the director of FinOps, and he's reached the point in his career where he's genuinely good at the job — good enough to find the cost hidden inside the architecture, explain the number to people who don't want to hear it, and tell when a forecast is real and when it's just a slide that has learned to stand upright.
He has also learned that being good at FinOps doesn't necessarily get you promoted.
FinOps sits between finance and engineering. Both sides depend on it; neither fully claims it. The job requires translating between functions, explaining the consequences of decisions, and telling people when the numbers don't support the story they want to tell.
That last part is the problem.
The meeting Rob walks into contains a hint that something is happening inside the company — something he's not part of. He knows enough to recognize he's being kept outside the real conversation. He doesn't know what the conversation is. The story develops from there.
I'm not going to explain what happens. You'll have to read the book.
What matters is why I wrote it.
I no longer work in FinOps day to day, which gives me distance from the work but also removes the excuse that I'm making a point about a current employer or settling an industry argument. I'm writing about what I saw across a field of work — what those patterns reveal when you put them into a story instead of a slide deck.
FinOps people are investigators by necessity. Cloud costs don't arrive with a neat explanation. The answer is usually spread across architecture, contracts, usage patterns, organizational decisions, and somebody's optimistic assumption from eighteen months earlier. You learn to pull at the thread past the first plausible explanation. You learn to trace a cost through the architecture and see who will carry the consequence of the decision later.
That kind of work matters more than ever now — not because every company needs another dashboard, but because the distance between a technical decision and its human consequences is getting shorter, and the person who can see both ends of that line is getting rarer.
That was the person I wanted Rob to be.
Redundant begins with FinOps, but it doesn't stay there. The trilogy follows what happens when the work of understanding cost, risk, and responsibility starts to move into other parts of the organization. The first book is about who gets cut. The later books ask who gets used and who gets protected. The story does not remain a corporate drama about cloud spend.
It becomes something else.
I wanted someone who knows nothing about FinOps, AI, or cloud architecture to be able to read this book and find a story. The technical details are setting, not a membership test. The real subject is how companies make decisions, how responsibility moves through an organization, and what happens to the person who keeps finding the truth after everyone else has decided what they want the truth to be.
You can buy Redundant as an EPUB from Amazon and other booksellers, or directly from The Condition Set website. I recommend the direct edition — the trilogy is finished, but I'll continue making corrections and refinements as I find them, and the direct version is the one that receives those updates.
I spent years getting the book ready. That's enough. It's done.
Start with the foreword or Chapter 1 and decide for yourself.