Writing
By Nophil Anwer, from Tampere
Notes from running business analysis and design for a manufacturing ERP. Every piece starts from something that actually happened at OMNE, and the numbers come from the team's own records.
Latest pieces
Catching drift before handoff
Every module has three records of what it's supposed to do: the user stories, the prototype and the spec. By handoff they rarely agree. The first full review of one OMNE module found about 175 issues between them.
Decision, for now, or just a view?
Most meeting notes say what was decided. Very few say what kind of call it was. Since October 2026 every ruling in the Omne decision wiki says whether it's a decision, a for-now call or just someone's view. Here's why I made that a rule.
How I keep track of every decision in an ERP
Omne ERP's decisions were spread across calls, Slack threads, Jira comments and specs, and nobody could keep track of all of it. So in September 2026 I built a decision wiki with Claude. It reads all of those every night and keeps one record of what was decided.
Bringing AI into a BA and design team
I moved OMNE's analysts and designers onto Claude, built Claude skills for their day-to-day work, and keep clear rules on when to trust what it produces. The point is fewer gaps between what got decided, designed and built.
Running BA and design for a manufacturing ERP
I wrote the original feature set for Omne ERP, an ERP for discrete manufacturers, and I still run its business analysis and design. The numbers here come from the team's own decision records.
Tell me what's stuck
Send a few lines about your product, your team and the problem. If I'm not the right person for it, I'll say so.