I work on enterprise software. Most of my time goes into workflows, handoffs between teams, and the UI that holds it together.
Whole products, not one-off screens.
ContextBuilt as an internal tool for an ISP. Now being developed as a public ERP platform. The interface shown is production UI from that system.
ProblemFinance teams could create, approve, and post to the GL in one step. No second review before errors hit the books.
Why it matteredWrong GL accounts, duplicate invoices, and typos meant reversals, bad vendor balances, and hours of month-end reconciliation.
ValueOnly validated transactions reach the General Ledger. Drafts stay off reports until a Checker approves.
ProblemInventory, sales, and hire-purchase payments were tracked across disconnected tools. Vehicle data entry alone ate hours daily.
Why it matteredMissed payments and stock blind spots cost real money. They needed ops software, not another dashboard.
ValueStock, sales, and hire-purchase tracking in one system. Less reconciliation, fewer missed payments.
ProblemTeams rebuilt UI from scratch on every product. Handoffs were slow. Users noticed the inconsistency.
Why it matteredDelivery kept slipping and maintenance cost was climbing. Leadership needed a system people would actually use.
ValueShared patterns across the suite. Teams stopped rebuilding UI and started shipping features.
ProblemUsers dropped off at wallet setup. The product felt technical when the job was emotional.
Why it matteredCompletion rate was the metric. Every extra step lost someone mid-gift.
ValueGifting flow that reads like a normal app. Live on iOS at evrlinkapp.com.
ProblemWork was scattered across phone calls, WhatsApp, spreadsheets, and paper. Everyone had information. No one had the same information.
Why it matteredMissed jobs, duplicated dispatch, payroll corrections, and idle equipment cost money every day coordination stayed manual.
ValueDispatch, attendance, tasks, equipment, and training connected around a single job workflow instead of separate tools.
Product screens from Pay4Me and the design system.
I'm Wisdom. I design enterprise products, usually the messy kind with a lot of moving parts.
My work tends to sit where finance, ops, or field teams are juggling multiple tools and nobody has the same picture of what's going on.
Before I touch UI, I'm in conversations, mapping how work actually moves, and figuring out where data gets lost between steps.
Most enterprise UX falls apart when teams design screens before they understand how work moves between modules. I map the handoffs first. UI comes later, and yeah, I still care that it looks good.
A screen is one step in a longer chain. I need to know who does what before and after before I design the feature.
Switching modules shouldn't feel like switching apps. Shared patterns cut down training and mistakes.
People use this software under pressure. They need to finish the task, not decode the interface.
PMs, engineers, and domain experts catch things I won't. The best solutions come out of those conversations, not solo wireframes.
Exploration matters, but at some point you pick a direction. Research and constraints help me commit, then iterate from there.
Seven things I keep saying after five years on connected products. Take them or leave them.
Wisdom brings a youthful energy to the team that is both refreshing and inspiring. I wish him the best and recommend him for UI/UX roles.
Wisdom pays so much attention to detail and brought amazing ideas to HeavyOps. I think he is an amazing product guy.
Looking at teams building ERP, CRM, ops platforms, and design systems. If you're hiring, happy to talk.
Get in touch →