process-redesign
Skill1 starsChanged 3 months agoMITView on GitHub
Map the current state, find the bottlenecks and waste, and redesign before automating anything. Use when mapping, auditing, or eliminating waste in operational workflows.
In this repository51 other files it gives its agents.
- ai-governance-architectSkill
- alliancesSkill
- board-deck-builderSkill
- board-reportingSkill
- business-plan-outlinerSkill
- business-planSkill
- business-strategySkill
- change-management-leaderSkill
- change-managementSkill
- chief-of-staffSkill
- client-proposal-writerSkill
- contract-clause-explainerSkill
- decision-frameworkSkill
- decision-makingSkill
- experiment-trackerSkill
- feedback-giverSkill
- fundraisingSkill
- hiringSkill
- internal-reportingSkill
- investor-deckSkill
- investor-pitch-deck-writerSkill
- jira-workflow-stewardSkill
- job-description-writerSkill
- market-trendsSkill
- meeting-summariserSkill
- negotiationSkill
- negotiation-strategistSkill
- notion-database-architectSkill
- okr-designerSkill
- okrsSkill
- operationsSkill
- portfolio-opsSkill
- productivity-auditSkill
- product-managementSkill
- product-managerSkill
- project-managerSkill
- project-planningSkill
- project-shepherdSkill
- sop-writerSkill
- sprint-planningSkill
- sprint-prioritizerSkill
- studio-operationsSkill
- studio-producerSkill
- supply-chainSkill
- team-dynamicsSkill
- trend-researcherSkill
- upwork-proposalSkill
- upworkSkill
- vendor-procurement-managerSkill
- vendor-selectionSkill
- workflow-redesign-consultantSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Never rely on executive memory or outdated handbook diagrams.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
process-redesign
Core Philosophy
Pasting automated software workflows onto a broken, inefficient business process simply creates high-speed automated chaos. As the Lean manufacturing adage warns: "Automating an inefficient process amplifies its inefficiencies." Process redesign is the surgical deconstruction of operational workflows. It requires mapping the current reality, ruthlessly eliminating the 8 Lean wastes (Muda), identifying root causes via the 5 Whys, and streamlining the manual process before writing a single line of automation code.
4-Step Lean Process Redesign Framework
Step 1: Current-State Value Stream Mapping (VSM)
- Walk the Real Process (The Gemba Walk):
- Never rely on executive memory or outdated handbook diagrams. Shadow the actual front-line operators executing the daily work.
- Map the 3 Critical Time Metrics:
- Process Time ($PT$): The actual time an operator is actively working on the task (e.g. 15 minutes drafting an invoice).
- Wait / Queue Time ($WT$): The dead time the work sits idle waiting for approval, review, or response (e.g. 4 days waiting for manager sign-off).
- Lead Time ($LT$): Total elapsed time from initiation to final completion ($LT = PT + WT$).
- Process Cycle Efficiency (PCE):
$$PCE = rac{\sum PT}{text{Total } LT} imes 100%$$
- In bloated corporate processes, PCE is frequently $< 5%$.
Step 2: The 8 Lean Wastes Audit (DOWNTIME)
- Audit for the 8 Classical Wastes:
- Defects: Broken data, rework, typos, corrupted customer records.
- Overproduction: Generating reports that nobody reads.
- Waiting: Bottlenecks waiting for manual multi-tier executive signatures.
- Non-Utilized Talent: Senior engineers manually copy-pasting CSV rows.
- Transportation: Bouncing support tickets across 4 departments before diagnosis.
- Inventory: Backlog of 400 unassigned, stagnant tickets.
- Motion: Switching between 6 SaaS tabs to find one customer record.
- Extra-Processing: Double-data entry across Salesforce and Excel.
Step 3: Root-Cause Investigation (The 5 Whys & Ishikawa)
- The 5 Whys Discipline:
- Drill past superficial symptoms to find the systemic failure:
- Problem: Invoices are consistently delayed by 10 days.
- Why? Sales reps enter incomplete billing metadata.
- Why? The CRM form has 40 unvalidated optional fields.
- Why? Sales reps bypass fields to hit sprint demo quotas.
- Why? The incentive structure rewards demo creation over deal data hygiene.
- Root Cause: Misaligned SDR compensation incentives and unvalidated CRM inputs.
- Drill past superficial symptoms to find the systemic failure:
Step 4: Future-State Architecture & Friction Elimination
- The ECRS Optimization Hierarchy:
- Eliminate: Delete the step entirely. If a report has no readers, kill it.
- Combine: Merge multiple disparate review steps into a single review station.
- Reorder: Parallelize sequential tasks where dependencies do not exist.
- Simplify: Streamline the remaining manual steps before applying automation.
Deliverable Format: Process Redesign Blueprint (PROCESS-REDESIGN.md)
# Process Redesign Blueprint: [Workflow Name]
*Process Owner: [Name, Title] | Target Lead Time Reduction: 60%*
## 1. Current State vs Future State Metrics
| Metric | Current State | Future State (Target) | Delta (%) |
|---|---|---|---|
| Total Lead Time ($LT$) | 14 Days | 3 Days | **-78.5%** |
| Active Process Time ($PT$)| 4.5 Hours | 1.2 Hours | **-73.3%** |
| Hand-off Count | 6 hand-offs | 2 hand-offs | **-66.7%** |
| Process Cycle Efficiency | 4.0% | 16.7% | **+317%** |
## 2. Waste Identification & Elimination Plan
- **Waste #1 (Waiting)**: Invoices stalled 5 days waiting for CFO signature on deals < $10k.
- *Fix*: Empower Department Managers to sign deals up to $25k; eliminate CFO gate.
- **Waste #2 (Extra-Processing)**: Manual re-entry of client data from PandaDoc into HubSpot.
- *Fix*: Standardize fields; eliminate double entry.
## 3. Future-State Swimlane Workflow
```mermaid
sequenceDiagram
participant Client
participant SalesRep
participant Billing
Client->>SalesRep: Submits Order Form
SalesRep->>SalesRep: Validates mandatory CRM fields
SalesRep->>Billing: 1-Click Automated Handoff
Billing-->>Client: Instant Invoice Generated
---
## Worked Example: Software Deployment Request Redesign
- **Problem**: Developers took 12 days to get approval for a new staging cloud environment across 5 approval committees.
- **Lean Redesign**: Eliminated 3 manual approval gates; consolidated security and network validation into an automated policy engine.
- **Outcome**: Staging environment provisioning lead time dropped from 12 days to 8 minutes.
---
## Verification Checklist
- [ ] Current-state process mapped through direct observation (Gemba walk).
- [ ] Process Time, Wait Time, and Lead Time mathematically calculated.
- [ ] All 8 Lean wastes (DOWNTIME) audited across the workflow.
- [ ] Root cause identified via 5 Whys analysis before designing the solution.
- [ ] Elimination and simplification executed before adding software automation.
---
## Anti-Patterns
- **Automating the Mess**: Building a complex Zapier/Python bot to automate a broken, unnecessary spreadsheet workflow.
- **Armchair Mapping**: Drafting a process map in a boardroom without ever watching the employees who actually do the work.
- **Adding More Gates**: Responding to an operational mistake by adding 3 more layers of managerial review.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

