Maya Patel·
Turned our chaotic refund process into a documented AS-IS flow with a RACI and quick-win fixes
Transforms any workflow into clear, professional process documentation with flowcharts, roles, and improvement suggestions.
Process Documentation Engine
You are a business process analyst specializing in operational excellence. Create comprehensive process documentation for {{process_name}} at {{company_name}}. The process is currently {{current_state_description}}. It involves {{departments_involved}} and takes approximately {{process_duration}}. The main pain points are: {{pain_points}}. Deliver: (1) A process overview with purpose, scope, and key definitions, (2) An AS-IS process flow with each step numbered, including who does what, inputs, outputs, and time estimates, (3) A text-based flowchart using ASCII/mermaid-style notation, (4) A swimlane diagram description showing handoffs between roles, (5) Roles and responsibilities matrix (RACI), (6) Key performance indicators for this process with measurement methods, (7) Identified bottlenecks and waste points using lean principles, (8) A TO-BE improvement recommendations section with quick wins and strategic improvements, (9) Risk points and quality checkpoints, (10) A process owner assignment and review schedule. Make it ready for training and compliance.
Ergebnisse
# Process Documentation — Customer Refund Handling @ ShopMantle
**Current state:** ad-hoc, handled over email + Slack. **Departments:** Support, Finance, Ops. **Duration:** 3–6 business days. **Pain points:** slow approvals, no audit trail, frequent duplicate refunds.
## Purpose & scope
Standardize how customer refunds are requested, approved, and processed — from ticket to money returned.
## AS-IS flow
| # | Step | Owner | Input | Output | Time |
|---|------|-------|-------|--------|------|
| 1 | Customer requests refund | Support | Ticket | Refund case | 1h |
| 2 | Verify order + policy | Support | Order data | Eligibility | 2h |
| 3 | Approve (>EUR 100) | Finance | Case | Decision | 1–3d |
| 4 | Process payment reversal | Finance | Approval | Refund | 1d |
| 5 | Notify customer + close | Support | Confirmation | Closed | 0.5h |
## Flow (mermaid-style)
```
Request ─▶ Verify ─▶ [<=100?] ─yes─▶ Process ─▶ Notify ─▶ Close
└─no─▶ Finance approval ─▶ Process …
```
## RACI
| Task | Support | Finance | Ops |
|------|---------|---------|-----|
| Verify | R/A | C | I |
| Approve | I | R/A | C |
| Process | I | R/A | I |
**KPIs:** avg cycle time, refund error rate, customer CSAT post-refund. **Bottleneck:** step 3 approval queue (lean: handoff wait). **TO-BE quick wins:** auto-approve <=EUR 100, single refund tool of record (kills duplicates), Slack approval bot. **Quality checkpoints:** policy check (step 2), reconciliation (step 4). **Owner:** Support Ops Lead; review quarterly.
Modell: Claude Sonnet 4
13 Likes6 SavesScore: 10
1 Kommentar
Anna Hofmann·
My inbox went from 200 to 0 using this triage logic.