ERP
Made for the Ones Who Uses it Daily
For day-to-day tasks, quick decisions, and everything in between.
"Efficiency is doing things right; effectiveness is doing the right things."
Peter Drucker
MANAGEMENT CONSULTANT
When we set out to build this ERP system at Tinkerve, it wasn’t just about creating software but it was about solving real, everyday problems for the people who would actually use it. This wasn’t a product for the public. It was an internal tool for our client, designed to support how their operations run on the ground
That became the foundation of how I approached the product as not just as an ERP system, but as a tool that quietly enables everyone to do their job better.
Challenge #1
What Happens When Everyone Needs Something Different?
Designing for One System with Three Very Different Realities
This ERP system wasn’t meant for a single type of user. It had to work for general workers handling day-to-day tasks, supervisors who needed a clear overview to make decisions, and our own ERP consultants who were configuring and maintaining the system behind the scenes.
Workers wanted speed. They didn’t care about the system but they just needed to get in, complete a task, and move on. Supervisors, on the other hand, needed clarity. They weren’t inputting data as much as they were scanning, reviewing, and making quick decisions based on what they saw. Then there were the consultants, who required flexibility such as access to controls, configurations, and the ability to adapt the system to different business needs.
Determining the flow for General Workers
Form Request Tracker
Submit Form Access Mobile
Request Form from Side Nav
For general workers, success isn't measured by how many features the system offers. It's measured by how quickly they can complete a task and move on to the next one. They value speed, familiarity, and consistency far more than flexibility. Every design decision was made with one question in mind: "Can they complete this with as little friction as possible?"
A supervisor's workflow is driven by questions rather than actions. What needs their attention? Where are the bottlenecks? Which reports require follow-up? Their experience isn't about completing forms quickly but it's about reducing the time it takes to find answers and make informed decisions. Every dashboard, filter, and data visualization was designed to shorten that journey.
Approval for Stock Taking
Inventory Overview for Each Warehouses
Material Request Table
Workflow Log
The challenge wasn’t just designing features for each group. It was making sure one experience didn’t get in the way of another.
If we designed for flexibility first, we risked overwhelming the workers. If we simplified too much, we limited what consultants could do. And if we focused only on data visibility, we slowed down execution on the ground.
So the approach became clear; design for simplicity on the surface, and power underneath.
This meant keeping the interfaces clean and task-focused for daily users, while structuring the system in a way that allowed deeper control without exposing unnecessary complexity upfront. Instead of one bloated experience, we created layers with each role interacting with the system differently, but all within the same product.
