[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78Z8MP6CWF03HS0396W21MD":3,"skill-same:01M78Z8MP6CWF03HS0396W21MD":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},"01M78Z8MP6CWF03HS0396W21MD","operations",null,"Own process, capacity planning, exception handling and performance tracking day to day. Use when running daily business operations, workflows, or SOP execution.","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\u002Foperations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: operations\nlast_reviewed: 2026-09-06\ngroup: Operations\ndescription: >-\n  Own process, capacity planning, exception handling and performance tracking day to day. Use when\n  running daily business operations, workflows, or SOP execution.\n---\n\n# operations\n\n## Core Philosophy\nBusiness operations is not keeping chaotic spreadsheets updated or firefighting emergencies as they occur. True operational excellence is systems engineering applied to human and technical workflows. High-performance operations is governed by queue theory, Little's Law, Eliyahu Goldratt’s Theory of Constraints, standardized capacity models, and automated exception routing. If a routine operational workflow depends on heroics or memory, the operating system has failed.\n\n---\n\n## 4-Step Scalable Business Operations Architecture\n\n### Step 1: Bottleneck Identification & Theory of Constraints\n1. **The Five Focusing Steps (Goldratt)**:\n   - *1. Identify the Constraint*: Locate the single operational station or resource that limits total organizational throughput (e.g. security review queue).\n   - *2. Exploit the Constraint*: Maximize output of that bottleneck (ensure the security team never wastes time on trivial administrative tasks).\n   - *3. Subordinate Everything Else*: Align upstream workflows to feed the bottleneck at its optimal processing speed (never overwhelm the bottleneck).\n   - *4. Elevate the Constraint*: Invest capital or headcount to expand bottleneck capacity.\n   - *5. Repeat*: Once elevated, identify the new operational constraint.\n\n### Step 2: Queue Theory & Little’s Law\n1. **The Mathematical Law of Work-in-Progress (WIP)**:\n   $$L = \\lambda  imes W$$\n   - Where:\n     - $L$ = Average number of items in the system (WIP).\n     - $\\lambda$ = Throughput rate (items processed per day).\n     - $W$ = Average lead time through the system.\n   - *Operational Axiom*: To reduce cycle time ($W$), you must **reduce Work-in-Progress ($L$)**. Capping concurrent active projects cuts delivery lead time dramatically.\n\n### Step 3: Capacity Planning & Utilization Thresholds\n1. **The 80% Utilization Guardrail**:\n   - In highway traffic and human operational teams alike, when utilization approaches 100%, queue wait times explode toward infinity.\n   - Schedule operational teams for a **maximum of 80% baseline capacity**. Reserve the remaining 20% buffer for unexpected outages, emergencies, and continuous system improvement.\n\n### Step 4: Standard Work Instructions & Exception Routing\n1. **Standardized Operations Runbooks**:\n   - Document deterministic operational routines in executable SOPs with explicit SLAs.\n2. **Automated Exception Handling**:\n   - Route standard transactions automatically; isolate exceptions and route directly to specialized human operators with full context logs.\n\n---\n\n## Deliverable Format: Operational System Specification (`OPERATIONS-SPEC.md`)\n\n```markdown\n# Operational Process & Capacity Specification: [Department \u002F Workflow]\n\n## 1. System Throughput & Capacity Baseline\n- **Core Workflow**: Customer Technical Onboarding Pipeline\n- **Current Throughput ($\\lambda$)**: 12 enterprise accounts onboarded \u002F month\n- **Average Lead Time ($W$)**: 21 days from contract sign to live deployment\n- **Active Work-in-Progress ($L$)**: 8 accounts concurrently active\n- **Team Utilization**: 78% (Target: \u003C 80% to prevent queue delay explosions)\n\n## 2. Identified Bottleneck & Mitigation\n- **Current Constraint**: Security VPC peering configuration\n- **Exploitation Action**: Automated Terraform script generation to replace manual AWS peering requests, cutting bottleneck processing time from 4 days to 2 hours.\n\n## 3. Escalation SLA & Exception Matrix\n| Exception Trigger | SLA | Assigned Resolver | Escalation Path |\n|---|---|---|---|\n| Client webhook failure > 5% | \u003C 2 Hours | Tier 2 Support Engineer | Lead Solutions Architect |\n| Security questionnaire stall > 48h | \u003C 24 Hours | Compliance Specialist | General Counsel |\n| Onboarding milestone delayed > 5 days | Immediate | Dedicated Account Manager | VP of Operations |\n```\n\n---\n\n## Worked Example: Slashing Client Onboarding Lead Time via Little's Law\n\n- **Problem**: Client onboarding was dragging to 48 days; onboarding specialists managed 25 active clients simultaneously, feeling overwhelmed.\n- **Intervention**: Applied Little's Law. Capped WIP to strictly 10 concurrent active accounts per specialist.\n- **Outcome**: Average lead time dropped from 48 days to 14 days; client satisfaction jumped from 72% to 96%.\n\n---\n\n## Verification Checklist\n\n- [ ] Primary operational constraint (bottleneck) identified and exploited.\n- [ ] Work-in-Progress (WIP) limits enforced to reduce cycle times.\n- [ ] Operational capacity planned with at least 20% reserve buffer.\n- [ ] Standard work instructions documented with explicit SLAs.\n- [ ] Automated exception routing prevents standard workflows from stalling.\n\n---\n\n## Anti-Patterns\n\n- **Running Teams at 100% Utilization**: Ensuring every engineer or operator is 100% booked, guaranteeing that a single emergency causes system-wide cascading delays.\n- **Local Optimization**: Spending $50,000 optimizing a non-bottleneck station, producing zero increase in overall system throughput.\n- **Hero Culture**: Relying on specific individual employees working 16-hour days to keep broken processes running.\n","# operations\n\n## Core Philosophy\nBusiness operations is not keeping chaotic spreadsheets updated or firefighting emergencies as they occur. True operational excellence is systems engineering applied to human and technical workflows. High-performance operations is governed by queue theory, Little's Law, Eliyahu Goldratt’s Theory of Constraints, standardized capacity models, and automated exception routing. If a routine operational workflow depends on heroics or memory, the operating system has failed.\n\n---\n\n## 4-Step Scalable Business Operations Architecture\n\n### Step 1: Bottleneck Identification & Theory of Constraints\n1. **The Five Focusing Steps (Goldratt)**:\n   - *1. Identify the Constraint*: Locate the single operational station or resource that limits total organizational throughput (e.g. security review queue).\n   - *2. Exploit the Constraint*: Maximize output of that bottleneck (ensure the security team never wastes time on trivial administrative tasks).\n   - *3. Subordinate Everything Else*: Align upstream workflows to feed the bottleneck at its optimal processing speed (never overwhelm the bottleneck).\n   - *4. Elevate the Constraint*: Invest capital or headcount to expand bottleneck capacity.\n   - *5. Repeat*: Once elevated, identify the new operational constraint.\n\n### Step 2: Queue Theory & Little’s Law\n1. **The Mathematical Law of Work-in-Progress (WIP)**:\n   $$L = \\lambda  imes W$$\n   - Where:\n     - $L$ = Average number of items in the system (WIP).\n     - $\\lambda$ = Throughput rate (items processed per day).\n     - $W$ = Average lead time through the system.\n   - *Operational Axiom*: To reduce cycle time ($W$), you must **reduce Work-in-Progress ($L$)**. Capping concurrent active projects cuts delivery lead time dramatically.\n\n### Step 3: Capacity Planning & Utilization Thresholds\n1. **The 80% Utilization Guardrail**:\n   - In highway traffic and human operational teams alike, when utilization approaches 100%, queue wait times explode toward infinity.\n   - Schedule operational teams for a **maximum of 80% baseline capacity**. Reserve the remaining 20% buffer for unexpected outages, emergencies, and continuous system improvement.\n\n### Step 4: Standard Work Instructions & Exception Routing\n1. **Standardized Operations Runbooks**:\n   - Document deterministic operational routines in executable SOPs with explicit SLAs.\n2. **Automated Exception Handling**:\n   - Route standard transactions automatically; isolate exceptions and route directly to specialized human operators with full context logs.\n\n---\n\n## Deliverable Format: Operational System Specification (`OPERATIONS-SPEC.md`)\n\n```markdown\n# Operational Process & Capacity Specification: [Department \u002F Workflow]\n\n## 1. System Throughput & Capacity Baseline\n- **Core Workflow**: Customer Technical Onboarding Pipeline\n- **Current Throughput ($\\lambda$)**: 12 enterprise accounts onboarded \u002F month\n- **Average Lead Time ($W$)**: 21 days from contract sign to live deployment\n- **Active Work-in-Progress ($L$)**: 8 accounts concurrently active\n- **Team Utilization**: 78% (Target: \u003C 80% to prevent queue delay explosions)\n\n## 2. Identified Bottleneck & Mitigation\n- **Current Constraint**: Security VPC peering configuration\n- **Exploitation Action**: Automated Terraform script generation to replace manual AWS peering requests, cutting bottleneck processing time from 4 days to 2 hours.\n\n## 3. Escalation SLA & Exception Matrix\n| Exception Trigger | SLA | Assigned Resolver | Escalation Path |\n|---|---|---|---|\n| Client webhook failure > 5% | \u003C 2 Hours | Tier 2 Support Engineer | Lead Solutions Architect |\n| Security questionnaire stall > 48h | \u003C 24 Hours | Compliance Specialist | General Counsel |\n| Onboarding milestone delayed > 5 days | Immediate | Dedicated Account Manager | VP of Operations |\n```\n\n---\n\n## Worked Example: Slashing Client Onboarding Lead Time via Little's Law\n\n- **Problem**: Client onboarding was dragging to 48 days; onboarding specialists managed 25 active clients simultaneously, feeling overwhelmed.\n- **Intervention**: Applied Little's Law. Capped WIP to strictly 10 concurrent active accounts per specialist.\n- **Outcome**: Average lead time dropped from 48 days to 14 days; client satisfaction jumped from 72% to 96%.\n\n---\n\n## Verification Checklist\n\n- [ ] Primary operational constraint (bottleneck) identified and exploited.\n- [ ] Work-in-Progress (WIP) limits enforced to reduce cycle times.\n- [ ] Operational capacity planned with at least 20% reserve buffer.\n- [ ] Standard work instructions documented with explicit SLAs.\n- [ ] Automated exception routing prevents standard workflows from stalling.\n\n---\n\n## Anti-Patterns\n\n- **Running Teams at 100% Utilization**: Ensuring every engineer or operator is 100% booked, guaranteeing that a single emergency causes system-wide cascading delays.\n- **Local Optimization**: Spending $50,000 optimizing a non-bottleneck station, producing zero increase in overall system throughput.\n- **Hero Culture**: Relying on specific individual employees working 16-hour days to keep broken processes running.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Operations",1788652800000,"main","7d9fbb0a795f90300e2eca8f6e7c3c6a24ecc2f2","skills\u002Foperations","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 operations",{"tool":41,"command":42},"bunx","bunx skills add poorvith-mp\u002Fskills-business --skill operations",{"tool":44,"command":45},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-business --skill operations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Foperations\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Frouting.yaml","REFERENCE","参考文档",1020,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Foperations\u002Fevals\u002Frouting.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"operations.skill","OTHER","其他",3268,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-business\u002Fblob\u002Fmain\u002Fskills\u002Foperations\u002Foperations.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",[],[]]