What we know, written down properly
Consultancies talk about method. Very few write it down, because writing it down is where you find out whether you actually have one. We have published two guides. Both were written for our own clients, and both are used in our own work.
They are documents, not videos — sourced, structured, and long enough to be useful rather than long enough to fill a playlist.
The Second Brain — Obsidian + AI
141 pages · eleven languages: English, Italian, Arabic, Chinese, German, French, Spanish, Portuguese, Hindi, Urdu, Russian
The infrastructure guide. How to build a knowledge system that survives a decade rather than a laptop.
Vault architecture, data integrity, synchronisation, backup strategy, migration out of a cloud that is failing you, and how to connect an AI to it without handing over what should stay private.
Written after building exactly that system for HYA — the one described on How We Work, across six jurisdictions.
Who it is for: anyone whose knowledge lives in a system they are quietly worried about, and anyone about to connect AI to their company’s documents.
USD 222 · PDF · immediate download
Obsidian, Used Properly — The Method
57 pages · Italian
The companion volume, and the harder of the two to write.
Not a manual: the buttons take an afternoon to learn, and knowledge bases die of missing judgement rather than missing features.
It covers the PARA method and Tiago Forte’s CODE process, Andrej Karpathy’s reading of the LLM as an operating system and of context as the asset, and an honest comparison of Zettelkasten, PARA and Johnny Decimal. Three worked example vaults — a consultant, a small company, a private individual. Three diagnosed graphs. The ten mistakes that kill a knowledge base, and a thirty-day plan.
Who it is for: anyone who has a vault and suspects they are not really using it.
Two reasons, and neither is marketing.
The first is that writing forces precision. A method you cannot write in fifty-seven pages is not a method, it is a set of habits. Publishing is how we test our own.
The second is that clients ask. Every process engagement ends with a company that now has a system and needs to keep it. These guides are what we hand them.
About the publications
Are these courses?
No. They are written documents — 141 and 57 pages respectively — with named sources and worked examples. There is no video, no drip-fed module, and no community upsell.
Which of the two should I read first?
If your concern is that your knowledge system might not survive a laptop failure, a cloud migration or an AI integration, read The Second Brain: it is the infrastructure book. If you already have a working system and suspect you are not really using it, read The Method.
What does a knowledge system have to do with business process consulting?
The same thing a process model has to do with a process: it is the difference between knowledge that exists in a system and knowledge that exists in someone’s head. Every process engagement ends with a company that has new documentation and needs to keep it current. These guides are what we hand over.
Start with a Process Audit.
Two weeks looking at how your company actually works. You get the map, the bottlenecks that cost you most, and a costed plan to fix them in order of return — including whether the answer is software at all.
Two weeks · one senior consultant · scope and fee agreed before we start · you own the output either way.