process-mapper

Topics in the source

• process-mapper
• Purpose
• When to use
• Workflow
• Scripts
• Quick example
• References
• Assumptions

BPMN-style business process documentation, bottleneck detection, and cycle-time analysis for internal-operations leaders. Internal-operations work suffers from three recurring failure modes: 1. Implicit process — the steps exist only in tribal knowledge, so handoffs drop and onboarding takes weeks. 2. Invisible waiting — most of the elapsed time on any business process is queue / wait / approval time, not actual work; teams optimize the wrong stage. 3. Local optimization — Goldratt's Theory of Constraints is ignored; resources are added to non-constraint stages, gaining nothing. This skill produces a documented process map, identifies where work waits, and points the constraint out by name with deterministic logic — not LLM intuition. Documenting a new business process (procurement intake, vendor onboarding, employee onboarding, incident handoff, expense reimbursement, customer onboarding, claims adjudication). An existing process is "too slow" but nobody can name the bottleneck. Cycle time is being measured but value-add ratio is not — so the team can't tell whether the process is healthy or waste-heavy. Cross-functional handoffs are dropping work and root cause is unclear. Five-s

This is an excerpt. Refer to the complete source and its current requirements.