Blog
The Verbasil journal: what we build, what we test, what we learn while making a company memory.
Documentation should not become a second job
Teams do not refuse documentation. Context gets lost when it is requested after the moment it was created.
Your data is not missing. It is not talking to itself.
A dashboard can show many numbers without revealing what connects customer feedback, a decision, an experiment and its result.
Your AI does not know your company's history
A model can answer well while ignoring your decisions, experiments and constraints. The missing piece is often verified company context.
Good onboarding does not only teach what to do. It teaches why.
A rule without its history is applied without judgement. To avoid repeating mistakes, teams need to transfer the context behind their choices.
A decision without the reason why not will always come back
Keeping the chosen option is not enough. When rejected alternatives and their constraints disappear, the team reopens the same debate.
Customer feedback is not enough if it never reaches your decisions
Feedback can exist in calls, messages and notes without ever shaping the roadmap. The real problem is the path from customer evidence to a decision.
Your notes are not enough if they do not return when a decision needs them
A team can have already learned something and still repeat the same discussion. The problem is not a lack of notes. It is lost context.
After a break, the hard part is not getting back to work. It is finding the thread.
This morning I came back from a few days off. I wanted to get going again, but I no longer knew where to start. Here is what that morning taught me about what a break really erases, and what it never should.
A memory that keeps everything can lead you to worse decisions than no memory at all
Two months into building Verbasil, the most counter-intuitive engineering lesson did not come from what the memory forgets. It came from what it confidently brings back when it is no longer true.
The bug I would never have caught alone: my first week of beta
By testing Verbasil like a real user, I found a bug that weeks of coding on my own would never have surfaced. Here is what it taught me, and why I now build in front of people.