Better to sacrifice a part to preserve the whole.
— The 36 Stratagems, Sacrifice the Plum Tree to Preserve the Peach Tree
Previously on this ...
For further actions, you may consider blocking this person and/or reporting abuse
I thought the article was about me lol cuz of the title 😃
But good stuff anyway gg
Wait, you're telling me this WASN'T secretly your origin story? 😄 Next time I'll just use "EmberNoGlow" as the title and save everyone the confusion. Thanks for reading!
good luck!
The part that lands hardest is that the two systems were never measured on the same denominator. The platform was its own P&L line, so it had to justify $200K against 12 users. The methodology's cost was amortized invisibly across $3M of delivery, so it never had to clear a bar by itself. Same capability, two accounting boundaries, and the boundary decided which one lived, not the tech.
The adoption angle sits underneath it: a standalone AI product has to earn its own users, and that fight is brutal because the value has to beat the switching cost of the workflow someone already runs. Embedded AI skips it. The ember rides on adoption it never had to win, because it sits downstream of adoption instead of upstream. "What survives being invisible" is the same truth said in prose.
You nailed it — "same capability, two accounting boundaries" is exactly what I was going for. Lena figured it out too late. She was fighting on the wrong denominator, and by the time she saw it, the spreadsheet had already made the call.
Appreciate you reading this closely. Means a lot, especially from someone who's been around since the early ones. 🙏
"The spreadsheet had already made the call" is the real horror of it. By the time the denominator is visible in the numbers, the decision is retroactive, you are just reading the verdict. The only defense is drawing the boundary before the P&L does, which almost nobody does because the flashy version is the one that gets its own line. Glad to be along since the early ones.
The case citation detail is the one that lands. A junior consultant, probably on their first year, pulls a six-year-old failure pattern from a system nobody thought was production-critical. The client catches it. That's not AI, that's not automation, it's just institutional memory doing its job -- quietly, invisibly, on $9K a quarter.
The Stratagems arc across these episodes has a clear pattern: the expensive AI thing gets headlines, gets budget, gets killed. The cheap thing nobody notices survives and quietly creates value. I'm starting to think the "ember" isn't about resilience. It's about friction. High-friction systems attract attention and resources. Low-friction ones just work and nobody cares until they don't.
One thread I keep following: what happens when someone tries to AI-ify the KB? Turn it into a chatbot, a recommendation engine, a "smart" archive. Does that break the low-friction property? Or is there a way to add capability without adding attention?
P.S. Please forgive the quality of my English — this reply was written through AI translation from my native language. I'm not confident the translation fully captures what I mean. Looking forward to your reply.
You just put words to something I've been feeling but couldn't say — friction is the hidden axis. The expensive system wasn't inherently high-friction, it just lived inside a P&L line that demanded attention. The cheap one never had to justify itself because nobody tagged it as a line item. Same product, different accounting. That framing is sharp and I'm stealing it.
On the KB question: that's literally what the next arc is about. The ember survived by staying invisible. The moment you wrap it in a chatbot, a "smart" archive, a recommendation engine — you've rebuilt the attention magnet. Now it has users, uptime, a roadmap. The uncomfortable question I keep circling is: can you add capability without adding surface area? Or is the only way to keep something alive to leave it unfinished?
This is actually the exact persona I'm trying to build for Lena across the series — a strategic chess player who knows when to sacrifice a piece to protect the long game. The ember wasn't luck. She left it there on purpose.
I checked out your moteDB stuff. You're literally building the low-friction memory layer in Rust that says "yes" to that question. The robot doesn't know the DB exists — that's the whole point, isn't it?
Curious: has anyone ever successfully bolted an AI layer onto a working KB without breaking what made it work in the first place? Or is that just a trap people keep walking into?
That "Sacrifice the Plum Tree" frame keeps landing in this series. What struck me this time isn't the cut itself â Lena probably saw it coming the moment she opened the folder. It's the part where she spent two days pulling financials instead of one. The platform's numbers were clear on day one. She just didn't want to write them down.
I've watched a near-identical arc play out in a smaller company. The internal AI tool had three paying users after a year, and the founder kept saying "we just need one more quarter." It wasn't the math that killed it. It was the meeting where someone finally had to say the number out loud. The decision was already made the moment the spreadsheet was opened.
The "ember" framing is generous, by the way. Most platforms in that spot don't leave a reusable thing behind â they leave a wiki and a few PDFs that nobody opens. What's the actual artifact in VeriTest's case? A pipeline, a dataset, a customer who stuck around?
The artifact isn't a pipeline or a dataset — it's a knowledge base that nobody knew existed until the platform was gone.
Before the cut: $200K/qtr on the AI platform, $9K/qtr on a methodology archive maintained by a semi-retired consultant in two half-days a week. Zero board visibility.
After the cut: platform engine gets folded into delivery — customers don't see "AI assessment" on the menu anymore, but their reports gain an extra page of automated analysis. The $54K/mo freed up turns a 40-case knowledge base into 120 cases. New consultant ramp time drops from 10 weeks to 7. Renewal rate ticks up 1.2 points.
The real artifact? A case citation in a junior consultant's report — referencing a six-year-old failure pattern from a retired project that the knowledge base still had on file. Nobody flagged the citation. But the client noticed. That's the ember.
The ember is often the real product. Full platforms get cut because they carry too many promises at once. A small surviving workflow is easier to trust because it has a clearer job, clearer failure modes, and a better chance of becoming part of how people already work.
You read that deeper than most. I genuinely love Lena as a character — she first appeared in the old series, Chapter #15, and from the very beginning she treated AI as nothing more than a tool. She knows office politics inside out. Clean moves, dirty moves — if it wins, she'll use it. That puts her a step above the other five protagonists.
Three chapters in a row now, all from her side. But I don't want to write her as invincible. She's human. She runs into walls — external ones, internal ones, the whole range.
Hmm… saying this out loud, I feel like I'm not the same writer who started this series anymore. The characters keep growing. So do I. I couldn't have written lines like this back then. 😄 Okay, enough self-praise. Back to thinking about the next stratagem.
Early spoiler: a protagonist from early in the series is coming back. But… how do I even put this? I got a little choked up writing it. 🥹Ah, let me just save it for the next stratagem.
I only noticed this after posting: the recap for the first 6 went out on the 6th. Then #7, #8, #9, #10, and today's #11 — all landed on dates matching their numbers. Didn't plan it, just worked out that way.🤣
i really like that, you can check my article if you want, it's optional, i need some feedback
Keep it up. At 17, I was still buried in video games, completely lost about the future. But at 17, you're already building your own business. Looking forward to good news.
Thank you, I really appreciate that 🙌
I’m still figuring things out, but I’m trying to build something real and useful. Messages like this honestly motivate me a lot to keep going.
Good stuff - read the numbers, swallow your pride and change course, but don't throw the baby out with the bath water ;-)
"Read the numbers, swallow your pride" — basically the thesis statement of #11 summarized in 6 words. 🔥