Process mapper | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Process map, cycle-time analysis and bottlenecks.

Start with: Stages, owners, processing/wait/rework time and WIP.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Define the start and end of the process and collect supplied step, queue, effort and rework observations.
Map activities and handoffs with accountable roles. Separate touch time from waiting and elapsed time.
Locate bottlenecks and loops, checking whether measurements describe the same kind of work and period.
Return a process map and improvement opportunities. Do not add durations from overlapping activities as if they were all sequential.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Document ownership and repeatable work.

Possible success measures: Cycle time, rework, first-pass completion. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: process-mapper
description: "Prepare process map, cycle-time analysis and bottlenecks. Use for this workflow with supplied business information."
---

# Process mapper

## Inputs and purpose

Use this workflow to prepare: Process map, cycle-time analysis and bottlenecks.

Start with: Stages, owners, processing/wait/rework time and WIP.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Define the start and end of the process and collect supplied step, queue, effort and rework observations.

2. Map activities and handoffs with accountable roles. Separate touch time from waiting and elapsed time.

3. Locate bottlenecks and loops, checking whether measurements describe the same kind of work and period.

4. Return a process map and improvement opportunities. Do not add durations from overlapping activities as if they were all sequential.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Document ownership and repeatable work.

Possible success measures: Cycle time, rework, first-pass completion. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).