A software discussion is more useful when it starts with the way work actually happens. In a manufacturing business, that means understanding how people plan, record, check, and hand over information.
A workflow map does not need specialist software. A shared document or a simple diagram can be enough to start. The aim is to make assumptions visible before choosing features.
Follow one piece of work
Choose a representative job, order, or production task and follow it from the initial request to completion. Record each step, who performs it, and the information needed to move forward.
Include the exceptions: missing information, a changed requirement, a delayed input, or a correction. These situations often reveal needs that a simple list of standard steps misses.
Mark every handover
Look for places where one person or team waits for another. How is information passed across? Is it entered again? How does the next person know it is ready?
Describe these handovers in plain language. “The supervisor needs the revised quantity before planning” is a more useful requirement than a vague request for a dashboard.
Separate facts from assumptions
Record what you have observed and what still needs confirmation. A spreadsheet may contain an unofficial step that another team does not know about. Ask the people doing the work to review the map before treating it as a specification.
Prioritize the problem
Not every inconvenience needs custom software. Identify which gaps create the most difficulty and which could be addressed through a simpler process change. Discuss possible improvements before committing to a feature list.
Define a small, reviewable scope
Choose a workflow that can be described clearly, identify its users, and agree how a proposed solution would be reviewed. Existing-system connections, data ownership, access, and support requirements should be discussed as part of that scope.
The output is a clearer starting point for discovery. It is not a promise of a particular product feature or implementation outcome.
Explore a discovery conversation for questions to guide an initial discussion.