About the project
Understand My Workflow is built around a simple engineering principle: understand the workflow before trying to fix the bug.
Created by Steven Tomczak
Steven Tomczak has a background in theoretical physics, engineering-oriented consulting, and structured problem solving. He is the author of Successful Consulting for Engineers and Data Processing Professionals, published by John Wiley.
The current project extends that practical consulting background into modern software workflow debugging: help technical people understand confusing systems by breaking the problem into staged, inspectable reports.
The website deliberately avoids overpromising. The first objective is not to replace engineers. The first objective is to help engineers see the structure of the problem more clearly.
Project principles
- Bound the active problem.
- Identify the workflow before the fix.
- Map cycles and nested cycles.
- Track handoffs and accumulated state.
- Ask for targeted evidence.
- Separate orientation from certification.
- Respect engineering judgment.
Why this matters
Many software problems become difficult because the team does not yet have a shared map of the workflow. People jump to fixes while still disagreeing about where the state lives, when the retry resumes, which side effects already happened, or what “done” really means.
Understand My Workflow is designed to slow that process down just enough to create useful structure.