Running BA and design for an 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.
- Client
- OMNE, LLC (US)
- Role
- Director of Business Analysis and Design, as a consultant
- Since
- 2023 as BA owner, 2025 as director
- Team
- 15 analysts and designers
What the work covers
All of it. Stock, sales, purchasing, finance, people and permissions, and they all affect each other. Change how a stock count handles a serial number and finance sees a different figure on the valuation report. Someone has to see across the whole thing.
The product has about 70 modules, and more than 20 are live on web and mobile. My recorded rulings touch more than 60 of them. Here's the split by area.
Inventory and warehouse
Items, cycle counting, physical inventory, warehouse structure, receiving, inventory movement, units of measure, categories, lots
600+rulings
Platform and access
User access control, security, settings, onboarding, notifications, import and export, activity logs, calendars
580+rulings
Sales and returns
Quotes, sales orders, shipping, returns (RMA), customer invoicing, pricing
510+rulings
Procurement
Purchase orders, vendor invoicing and payments, recommended purchase orders
310+rulings
Partners and communication
Customers and vendors, partner groups, contacts, communications, email templates
240+rulings
Finance
Chart of accounts, cash management, currencies, general ledger, financial reporting, billing
170+rulings
People and production
Work centres, people, shifts, employee self-service, equipment, bills of materials, scheduling
140rulings
Across modules
Design system, team process, navigation, and rules every module shares
600+rulings
Source: the Omne decision wiki, counted on 16 November 2026. The counts grow every night.
In numbers
Product rulings with me as the one who decided. The record holds more than 15,500 in total.
Product meetings recorded and written up since July 2023.
Design reviews with the CEO. Plus 140+ internal reviews, 140+ daily stand-ups and 80+ handoffs.
Analysts and designers in the team I lead. I report to the CEO.
Source: the Omne decision wiki, counted on 16 November 2026. The counts grow every night.
How I run meetings
Product decisions at OMNE get made in four kinds of meeting: daily stand-ups, internal reviews, design reviews with the CEO, and handoffs to engineering. I set how they run, and a few things always hold.
- Nothing goes to the CEO until I've reviewed it internally.
- Every meeting ends with a recorded ruling: who said it, when, and what kind of call it was.
- Every ruling goes into the Jira story, the spec and the decision wiki, so nobody has to remember it.
Daily stand-up
I run it. Everyone gives an update and small calls get made on the spot.
Internal review
I go through a module's design with its analyst and designer before the CEO sees it.
Design review
The CEO reviews the design and makes the calls, with the module team there.
Handoff
The analysts take the developers through the stories, the prototype and the spec.
More of the work
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.