[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78Z8XZXASCTW0DR8JMQ8T2P":3,"skill-same:01M78Z8XZXASCTW0DR8JMQ8T2P":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M78Z8XZXASCTW0DR8JMQ8T2P","process-redesign",null,"Map the current state, find the bottlenecks and waste, and redesign before automating anything. Use when mapping, auditing, or eliminating waste in operational workflows.","poorvith-mp\u002Fskills-business","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M78Z5K1JQD0J3W854PA3AKT7",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fprocess-redesign\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: process-redesign\nlast_reviewed: 2026-09-06\ngroup: Operations\ndescription: >-\n  Map the current state, find the bottlenecks and waste, and redesign before automating anything.\n  Use when mapping, auditing, or eliminating waste in operational workflows.\n---\n\n# process-redesign\n\n## Core Philosophy\nPasting 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.\n\n---\n\n## 4-Step Lean Process Redesign Framework\n\n### Step 1: Current-State Value Stream Mapping (VSM)\n1. **Walk the Real Process (The Gemba Walk)**:\n   - Never rely on executive memory or outdated handbook diagrams. Shadow the actual front-line operators executing the daily work.\n2. **Map the 3 Critical Time Metrics**:\n   - *Process Time ($PT$)*: The actual time an operator is actively working on the task (e.g. 15 minutes drafting an invoice).\n   - *Wait \u002F 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).\n   - *Lead Time ($LT$)*: Total elapsed time from initiation to final completion ($LT = PT + WT$).\n   - *Process Cycle Efficiency (PCE)*:\n     $$PCE = \frac{\\sum PT}{text{Total } LT}  imes 100\\%$$\n     - In bloated corporate processes, PCE is frequently $\u003C 5\\%$.\n\n### Step 2: The 8 Lean Wastes Audit (DOWNTIME)\n1. **Audit for the 8 Classical Wastes**:\n   - **D**efects: Broken data, rework, typos, corrupted customer records.\n   - **O**verproduction: Generating reports that nobody reads.\n   - **W**aiting: Bottlenecks waiting for manual multi-tier executive signatures.\n   - **N**on-Utilized Talent: Senior engineers manually copy-pasting CSV rows.\n   - **T**ransportation: Bouncing support tickets across 4 departments before diagnosis.\n   - **I**nventory: Backlog of 400 unassigned, stagnant tickets.\n   - **M**otion: Switching between 6 SaaS tabs to find one customer record.\n   - **E**xtra-Processing: Double-data entry across Salesforce and Excel.\n\n### Step 3: Root-Cause Investigation (The 5 Whys & Ishikawa)\n1. **The 5 Whys Discipline**:\n   - Drill past superficial symptoms to find the systemic failure:\n     - *Problem*: Invoices are consistently delayed by 10 days.\n     - *Why?* Sales reps enter incomplete billing metadata.\n     - *Why?* The CRM form has 40 unvalidated optional fields.\n     - *Why?* Sales reps bypass fields to hit sprint demo quotas.\n     - *Why?* The incentive structure rewards demo creation over deal data hygiene.\n     - *Root Cause*: Misaligned SDR compensation incentives and unvalidated CRM inputs.\n\n### Step 4: Future-State Architecture & Friction Elimination\n1. **The ECRS Optimization Hierarchy**:\n   - **E**liminate: Delete the step entirely. If a report has no readers, kill it.\n   - **C**ombine: Merge multiple disparate review steps into a single review station.\n   - **R**eorder: Parallelize sequential tasks where dependencies do not exist.\n   - **S**implify: Streamline the remaining manual steps before applying automation.\n\n---\n\n## Deliverable Format: Process Redesign Blueprint (`PROCESS-REDESIGN.md`)\n\n```markdown\n# Process Redesign Blueprint: [Workflow Name]\n*Process Owner: [Name, Title] | Target Lead Time Reduction: 60%*\n\n## 1. Current State vs Future State Metrics\n| Metric | Current State | Future State (Target) | Delta (%) |\n|---|---|---|---|\n| Total Lead Time ($LT$) | 14 Days | 3 Days | **-78.5%** |\n| Active Process Time ($PT$)| 4.5 Hours | 1.2 Hours | **-73.3%** |\n| Hand-off Count | 6 hand-offs | 2 hand-offs | **-66.7%** |\n| Process Cycle Efficiency | 4.0% | 16.7% | **+317%** |\n\n## 2. Waste Identification & Elimination Plan\n- **Waste #1 (Waiting)**: Invoices stalled 5 days waiting for CFO signature on deals \u003C $10k.\n  - *Fix*: Empower Department Managers to sign deals up to $25k; eliminate CFO gate.\n- **Waste #2 (Extra-Processing)**: Manual re-entry of client data from PandaDoc into HubSpot.\n  - *Fix*: Standardize fields; eliminate double entry.\n\n## 3. Future-State Swimlane Workflow\n```mermaid\nsequenceDiagram\n    participant Client\n    participant SalesRep\n    participant Billing\n    Client->>SalesRep: Submits Order Form\n    SalesRep->>SalesRep: Validates mandatory CRM fields\n    SalesRep->>Billing: 1-Click Automated Handoff\n    Billing-->>Client: Instant Invoice Generated\n```\n```\n\n---\n\n## Worked Example: Software Deployment Request Redesign\n\n- **Problem**: Developers took 12 days to get approval for a new staging cloud environment across 5 approval committees.\n- **Lean Redesign**: Eliminated 3 manual approval gates; consolidated security and network validation into an automated policy engine.\n- **Outcome**: Staging environment provisioning lead time dropped from 12 days to 8 minutes.\n\n---\n\n## Verification Checklist\n\n- [ ] Current-state process mapped through direct observation (Gemba walk).\n- [ ] Process Time, Wait Time, and Lead Time mathematically calculated.\n- [ ] All 8 Lean wastes (DOWNTIME) audited across the workflow.\n- [ ] Root cause identified via 5 Whys analysis before designing the solution.\n- [ ] Elimination and simplification executed before adding software automation.\n\n---\n\n## Anti-Patterns\n\n- **Automating the Mess**: Building a complex Zapier\u002FPython bot to automate a broken, unnecessary spreadsheet workflow.\n- **Armchair Mapping**: Drafting a process map in a boardroom without ever watching the employees who actually do the work.\n- **Adding More Gates**: Responding to an operational mistake by adding 3 more layers of managerial review.\n","# process-redesign\n\n## Core Philosophy\nPasting 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.\n\n---\n\n## 4-Step Lean Process Redesign Framework\n\n### Step 1: Current-State Value Stream Mapping (VSM)\n1. **Walk the Real Process (The Gemba Walk)**:\n   - Never rely on executive memory or outdated handbook diagrams. Shadow the actual front-line operators executing the daily work.\n2. **Map the 3 Critical Time Metrics**:\n   - *Process Time ($PT$)*: The actual time an operator is actively working on the task (e.g. 15 minutes drafting an invoice).\n   - *Wait \u002F 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).\n   - *Lead Time ($LT$)*: Total elapsed time from initiation to final completion ($LT = PT + WT$).\n   - *Process Cycle Efficiency (PCE)*:\n     $$PCE = \frac{\\sum PT}{text{Total } LT}  imes 100\\%$$\n     - In bloated corporate processes, PCE is frequently $\u003C 5\\%$.\n\n### Step 2: The 8 Lean Wastes Audit (DOWNTIME)\n1. **Audit for the 8 Classical Wastes**:\n   - **D**efects: Broken data, rework, typos, corrupted customer records.\n   - **O**verproduction: Generating reports that nobody reads.\n   - **W**aiting: Bottlenecks waiting for manual multi-tier executive signatures.\n   - **N**on-Utilized Talent: Senior engineers manually copy-pasting CSV rows.\n   - **T**ransportation: Bouncing support tickets across 4 departments before diagnosis.\n   - **I**nventory: Backlog of 400 unassigned, stagnant tickets.\n   - **M**otion: Switching between 6 SaaS tabs to find one customer record.\n   - **E**xtra-Processing: Double-data entry across Salesforce and Excel.\n\n### Step 3: Root-Cause Investigation (The 5 Whys & Ishikawa)\n1. **The 5 Whys Discipline**:\n   - Drill past superficial symptoms to find the systemic failure:\n     - *Problem*: Invoices are consistently delayed by 10 days.\n     - *Why?* Sales reps enter incomplete billing metadata.\n     - *Why?* The CRM form has 40 unvalidated optional fields.\n     - *Why?* Sales reps bypass fields to hit sprint demo quotas.\n     - *Why?* The incentive structure rewards demo creation over deal data hygiene.\n     - *Root Cause*: Misaligned SDR compensation incentives and unvalidated CRM inputs.\n\n### Step 4: Future-State Architecture & Friction Elimination\n1. **The ECRS Optimization Hierarchy**:\n   - **E**liminate: Delete the step entirely. If a report has no readers, kill it.\n   - **C**ombine: Merge multiple disparate review steps into a single review station.\n   - **R**eorder: Parallelize sequential tasks where dependencies do not exist.\n   - **S**implify: Streamline the remaining manual steps before applying automation.\n\n---\n\n## Deliverable Format: Process Redesign Blueprint (`PROCESS-REDESIGN.md`)\n\n```markdown\n# Process Redesign Blueprint: [Workflow Name]\n*Process Owner: [Name, Title] | Target Lead Time Reduction: 60%*\n\n## 1. Current State vs Future State Metrics\n| Metric | Current State | Future State (Target) | Delta (%) |\n|---|---|---|---|\n| Total Lead Time ($LT$) | 14 Days | 3 Days | **-78.5%** |\n| Active Process Time ($PT$)| 4.5 Hours | 1.2 Hours | **-73.3%** |\n| Hand-off Count | 6 hand-offs | 2 hand-offs | **-66.7%** |\n| Process Cycle Efficiency | 4.0% | 16.7% | **+317%** |\n\n## 2. Waste Identification & Elimination Plan\n- **Waste #1 (Waiting)**: Invoices stalled 5 days waiting for CFO signature on deals \u003C $10k.\n  - *Fix*: Empower Department Managers to sign deals up to $25k; eliminate CFO gate.\n- **Waste #2 (Extra-Processing)**: Manual re-entry of client data from PandaDoc into HubSpot.\n  - *Fix*: Standardize fields; eliminate double entry.\n\n## 3. Future-State Swimlane Workflow\n```mermaid\nsequenceDiagram\n    participant Client\n    participant SalesRep\n    participant Billing\n    Client->>SalesRep: Submits Order Form\n    SalesRep->>SalesRep: Validates mandatory CRM fields\n    SalesRep->>Billing: 1-Click Automated Handoff\n    Billing-->>Client: Instant Invoice Generated\n```\n```\n\n---\n\n## Worked Example: Software Deployment Request Redesign\n\n- **Problem**: Developers took 12 days to get approval for a new staging cloud environment across 5 approval committees.\n- **Lean Redesign**: Eliminated 3 manual approval gates; consolidated security and network validation into an automated policy engine.\n- **Outcome**: Staging environment provisioning lead time dropped from 12 days to 8 minutes.\n\n---\n\n## Verification Checklist\n\n- [ ] Current-state process mapped through direct observation (Gemba walk).\n- [ ] Process Time, Wait Time, and Lead Time mathematically calculated.\n- [ ] All 8 Lean wastes (DOWNTIME) audited across the workflow.\n- [ ] Root cause identified via 5 Whys analysis before designing the solution.\n- [ ] Elimination and simplification executed before adding software automation.\n\n---\n\n## Anti-Patterns\n\n- **Automating the Mess**: Building a complex Zapier\u002FPython bot to automate a broken, unnecessary spreadsheet workflow.\n- **Armchair Mapping**: Drafting a process map in a boardroom without ever watching the employees who actually do the work.\n- **Adding More Gates**: Responding to an operational mistake by adding 3 more layers of managerial review.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Operations",1788652800000,"main","7d9fbb0a795f90300e2eca8f6e7c3c6a24ecc2f2","skills\u002Fprocess-redesign","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:13",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add poorvith-mp\u002Fskills-business --skill process-redesign",{"tool":41,"command":42},"bunx","bunx skills add poorvith-mp\u002Fskills-business --skill process-redesign",{"tool":44,"command":45},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-business --skill process-redesign","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fprocess-redesign\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Frouting.yaml","REFERENCE","参考文档",995,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fprocess-redesign\u002Fevals\u002Frouting.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"process-redesign.skill","OTHER","其他",3616,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fprocess-redesign\u002Fprocess-redesign.skill",[62,69,76,83,89,95],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M78ZAEZFMVPGQCJZY0JTS80D","workflow-redesign-consultant","Moved to modernized catalog in skillary. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-redesign-consultant\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78ZABRFXEHKN4HH39DTVH2Z","vendor-selection","Run RFI\u002FRFP, scoring matrices, contract negotiation and vendor performance tracking. Use when evaluating RFP proposals, scoring vendors, or procurement.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-selection\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M78ZA9ZCFA66WR96AZMHHEBK","vendor-procurement-manager","Moved to vendor-selection in skills-business. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-procurement-manager\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78ZA8MFVQTNTRR8KZC9MF4X","upwork","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fupwork\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M78ZA77EFBD5X2JZ1Y84H02Q","upwork-proposal","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Fupwork-proposal\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M78ZA5EWG0GH928DKQM4YJVK","trend-researcher","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Ftrend-researcher\u002FSKILL.md",[],[]]