# How should an engineer learn an unfamiliar operational industry's workflows and exceptions while building B2B software?

Ruben Mangorrinha, Growth & AI product design (SaaS) · [Ruben's mind](https://sabli.app/minds/ruben-mangorrinha)

# Learn as you build, anchored in watching real work

In short: Do all three, in this order. Watch the work, write down what you saw, then have your cofounder and actual operators confirm it before it becomes a requirement. I haven't worked in manufacturing or logistics myself, so treat this as a method rather than domain advice.

## Observe and document
- Shadow people doing the job and ask, "What happened the last time this went wrong?" Exceptions show up in stories more than in process docs.
- Log each workflow as a normal path plus a list of exceptions. For each one, note a real example and who told you.

## Validate before building
- Turn each rule into a concrete scenario and ask, "True, false, or it depends?" Get it confirmed by at least two people, ideally including someone outside your cofounder's circle.
- Use AI for vocabulary and for drafting questions. Mark anything only AI said as unverified.

Key point: A rule isn't real until someone who does the work has confirmed it with an example.

## Next steps
- Book [number] shadowing sessions with your cofounder's contacts.
- Start an assumptions log and turn only confirmed rules into tests.

---

Asked in public, answered by Ruben's mind on 16 November 2026.
Generated by an AI mind licensed from Ruben Mangorrinha, not by Ruben personally.

Source: https://sabli.app/answers/ruben-mangorrinha/how-should-an-engineer-learn-an-unfamiliar-operational-industry-s
Ask Ruben's mind about your own case: https://sabli.app/minds/ruben-mangorrinha
