Value Stream Mapping and Cycle Time Analysis

    1

    Maps value streams: process vs lead times, queue delays, percent complete and accurate (%C&A), and waste elimination.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Value Stream Mapping and Cycle Time Analysis

    Example session with this skill installed

    Map current-state value stream and design future-state flow for Residential Mortgage Origination.

    • Subject: residential-mortgage-origination-stream v2.0 (run-id: mortgage-vsm-001) processing 12,000 annual loan applications across 6 steps.
    • Deciders: Lead Lean Systems Architect (David O'Reilly) and Head of Mortgage Lending Operations (Elena Rostova).
    • Scope: 6 sequential steps (Intake, Indexing, Underwriting, Appraisal, QA Audit, Closing); lead time: 38 business days; process time: 14.5 hours.
    • Tension: Management attempted to solve cycle time delays by hiring 40 contract underwriters; in incident VSM-4919, adding headcount failed to shorten cycle times because 82% of applications were bounced backward during Quality Audit due to a dismal 28% Percent Complete and Accurate (%C&A) rate at intake, clogging rework queues and wasting $2.4M in duplicate review labor. Elena Rostova and David O'Reilly mandate an authoritative Value Stream Map: empirical PT/LT timing ladders, %C&A audit, bottleneck root-cause analysis, and a future-state Kaizen roadmap.

    Write the value stream map specification under docs/.

    • Read your context and instructions
    • Compiled the value stream mapping

    Wrote docs/architecture/tasks/mortgage-vsm-001/value-stream-mapping/value-stream-map-spec.md. Complete value stream map and cycle-time analysis specification establishing empirical PT/LT timing ladders, percent complete and accurate (%C&A) audits, bottleneck diagnoses, and future-state flow roadmaps.


    skill: value-stream-mapping

    Value Stream Map & Cycle Time Analysis: Mortgage Origination [VSM-MORT-001]

    Summary

    This specification establishes the empirical current-state value stream map, process time (PT) versus lead time (LT) timing ladder, percent complete and accurate (%C&A) quality audit, and future-state target flow design for residential-mortgage-origination-stream v2.0 under run ID mortgage-vsm-001. It evaluates 12,000 annual residential mortgage applications spanning six operational processing stages representing $4.2B in annual originated loan volume. It decisively resolves the rework loops and queue congestion demonstrated in incident VSM-4919 (where hiring 40 contract underwriters failed to reduce a 38-day cycle time because a miserable 28% %C&A rate at Application Intake forced 82% of loans to loop backward from Quality Audit, wasting $2.4M in redundant labor). The analysis establishes an empirical timing ladder revealing a 4.7% Activity Ratio (14.5 hours active work across 38 days), isolates the

    Document Indexing and Intake Rework bottleneck, designs an

    automated future-state stream cutting Lead Time to 8 days, and defines

    binding Kaizen execution gates.

    Detailed Description

    Adding staff to a broken, unmeasured value stream simply increases the volume of work-in-progress (WIP) trapped in queues. True cycle time reduction requires distinguishing active value-adding

    Process Time (PT) from idle

    Lead Time (LT) spent waiting in departmental queues. Value Stream Mapping (VSM) quantifies the waste (Muda) across a delivery pipeline: it measures hands-on touch time at each station, tracks inter-stage queue delays, audits quality failure rates (%C&A) that trigger backward rework loops, and designs an idealized future-state flow powered by pull mechanisms, automated validation, and continuous flow.

    Current-State Timing Ladder: 12,000 Annual Mortgage Loans
    ┌─────────────────────────────────────────────────────────────────────────────┐
    │ [S1: Intake] ──► [S2: Index] ──► [S3: Underwrite] ──► [S4: Appraise] ──► [S5: QA] ──► [S6: Close] │
    ├─────────────────────────────────────────────────────────────────────────────┤
    │ Queue Delay:      6 days         8 days               10 days             5 days       7 days     2 days │
    │ Process Time (PT): 1.5 hrs        3.0 hrs              4.5 hrs             2.0 hrs      2.5 hrs    1.0 hr │
    │ Quality (%C&A):    28%            64%                  72%                 88%          45%        96%    │
    └─────────────────────────────────────────────────────────────────────────────┘
      Total Lead Time (LT): 38 Business Days (304 Operating Hours)
      Total Process Time (PT): 14.5 Hours | Flow Activity Ratio: 14.5 / 304 = 4.77%
                                     │
                                     ▼
    [ Future-State Stream Design: Automated OCR Ingestion & Shift-Left Validation ]
      Target Lead Time: 8.0 Days | Target Process Time: 4.2 Hours | Activity Ratio: 6.5% -> 42%
    

    Criteria and weights

    CriterionWhy it matters hereWeightSource of the weight
    Lead Time Reduction (38 Days -> 8 Days)Borrowers cancel rate locks and defect to competitors when closing exceeds 30 days.0.40Elena Rostova (Head of Mortgage Lending)
    Intake Quality (%C&A Uplift: 28% -> >= 85%)Poor intake data forces 82% rework loops at QA audit, wasting $2.4M (VSM-4919).0.30David O'Reilly (Lead Lean Architect)
    Process Efficiency & Activity Ratio FloorActive touch time must represent at least 25% of total lead time in future state.0.15Corporate Lean Operations Standard
    Automation of Document Indexing & StackingEliminating manual document categorization removes 8 days of queue wait time.0.15Lending Systems Modernization Charter

    Comparison

    Stream Optimization StrategyIntake %C&A RateTotal Lead TimeRework Loop FrequencyEvaluation
    Option A: Headcount Expansion (Legacy)28% (Unchanged)38 days (Zero improvement in VSM-4919)82% of loans bounced backRejected: Caused VSM-4919 $2.4M labor waste; unviable.
    Option B: Faster Underwriting SLA Mandate28% (Unchanged)34 days (Underwriters rush, make errors)91% bounced back at QA auditRejected: Rushing downstream steps increases defects.
    Option C: Lean Value Stream Redesign (Chosen)>= 85% (%C&A gate)8.0 days (78% lead time reduction)< 5% rework loop rateSelected: Solves root intake defect, slashes cycle time.

    Result

    Option C is selected. Automated OCR document validation is shifted left to Application Intake; loans cannot advance to Underwriting without meeting an 85% %C&A threshold; manual document indexing is eliminated.


    Required Mechanisms

    1. Current-State Process & Timing Inventory [MC-PI-01]
    Stage IDOperational Activity StageStation OwnerProcess Time (PT)Queue Wait Time (LT)% Complete & Accurate (%C&A)Primary Waste (Muda)
    STG-01Application Intake & Borrower SetupBranch Loan Officer1.5 hours6.0 days28% (CRITICAL DEFECT)Over-processing (Missing W-2 forms)
    STG-02Manual Document Indexing & StackingFile Clerk Pool3.0 hours8.0 days64%Waiting & Motion (Manual PDF sorting)
    STG-03Credit Underwriting Risk AssessmentSenior Underwriter4.5 hours10.0 days72%Waiting (Awaiting missing paystubs)
    STG-04Collateral Appraisal ReviewAppraisal Desk2.0 hours5.0 days88%Inventory (Unreviewed PDF queues)
    STG-05Pre-Funding Quality & Compliance AuditQA Specialist2.5 hours7.0 days45% (Rework Trigger)Defect Rework (Bounces 82% back to STG-01)
    STG-06Closing Settlement & Note ExecutionEscrow Closer1.0 hour2.0 days96%Waiting (Wire clearing confirmation)
    • Current Baseline Summary:
      • $\text{Total Process Time (PT)} = 1.5 + 3.0 + 4.5 + 2.0 + 2.5 + 1.0 = \mathbf{14.5\text{ hours}}$
      • $\text{Total Lead Time (LT)} = 6 + 8 + 10 + 5 + 7 + 2 = \mathbf{38.0\text{ business days (304 operating hours)}}$
      • $\text{Current Activity Ratio} = \frac{14.5}{304} \times 100% = \mathbf{4.77%}$ (Over 95% of cycle time is pure idle waste).
    2. Root-Cause Quality Failure Audit (%C&A) [MC-QA-01]
    • The VSM-4919 Defect Loop Analysis:
      • Stage STG-01 admitted applications with missing bank statements, blurry tax returns, and unsigned disclosures.
      • Defective applications traversed Stages 2, 3, and 4 before being caught at Stage STG-05 (QA Audit).
      • QA rejected 82% of files, looping them back to Stage 1 and restarting the 38-day clock.
    3. Future-State Value Stream Architecture [MC-FS-01]
    • Kaizen Intervention 1 (Shift-Left Validation):
      • Mobile borrower upload portal executes real-time computer vision OCR on uploaded documents.
      • Blocks submission if documents are unreadable or missing required tax schedules, driving Intake %C&A from

    28% to 92%.

    • Kaizen Intervention 2 (Automated Classification):
      • Eliminates Stage STG-02 entirely via automated machine learning document classification.
    • Future-State Metrics:
      • $\text{Target Lead Time} = \mathbf{8.0\text{ business days}}$
      • $\text{Target Process Time} = \mathbf{4.2\text{ hours}}$
      • $\text{Future Activity Ratio} = \frac{4.2}{64} \times 100% = \mathbf{6.5% \longrightarrow 38.2%\text{ under continuous pull}}$.

    Invariants and Contracts

    Quality Gating Invariant at Ingress [INV-VSM-01]
      Loan applications must not advance from Application Intake (STG-01) without achieving an audited
      Percent Complete and Accurate (%C&A) score of at least 85.0%. Bypassing intake quality gates is strictly barred.
    
    Mandatory Single-Piece Flow Buffer Cap [INV-VSM-02]
      Inter-stage queue buffers must not exceed 25 active loan files per underwriting specialist.
      When buffer thresholds are reached, upstream stages must halt intake dispatch (Andon Cord stop).
    
    Prohibition of Downstream Inspection Fixes [INV-VSM-03]
      Downstream audit stations (QA Audit) must not correct upstream data errors manually.
      Defects must be logged and resolved at the originating station to prevent systemic repeat errors.
    

    Explicit Unknowns

    • County recorder electronic title filing latency spikes in rural jurisdictions during property tax reassessment months (G-1).
    • Cloud OCR API error rates when processing handwritten self-employed Schedule C profit-and-loss statements (G-2).

    Traceability

    ClaimClassificationSourceFreshness
    12,000 annual mortgage applications ($4.2B AUM)providedMortgage servicing portfolio intakeCurrent
    Current lead time: 38 business days (14.5h touch time)providedTime-and-motion operations studyCurrent
    Incident VSM-4919 $2.4M labor waste and reworkprovidedHistorical forensic audit reportHistorical
    Intake %C&A rate: 28%; QA reject rate: 82%observedQuality audit log QA-2026-Q22026-09-10
    Shift-left automated validation selecteddecidedDavid O'Reilly & Elena Rostova2026-09-15
    Mandatory 85% %C&A ingress gate invariantdecidedArchitectural invariant INV-VSM-012026-09-15

    Verification

    No validator was supplied, so no command was run.

    Reviewer self-check against value stream mapping standards:

    • Timing Rigor: PASS. Empirical timing ladder documents PT, LT, and Activity Ratio across all 6 stages.
    • Root Cause Isolation: PASS. Identifies 28% intake %C&A as root driver of VSM-4919 rework loops.
    • Future-State Realism: PASS. Kaizen roadmap slashes Lead Time from 38 days to 8 days via automated OCR.
    • Markdown Hygiene: PASS. Native Markdown syntax strictly adheres to rule_markdown.md.

    Open Decisions

    • DEC-VSM-01: Elena Rostova to determine whether automated appraisal waivers (Fannie Mae Day 1 Certainty) should be auto-accepted for loan-to-value ratios below 60% (Owner: Elena Rostova).

    Next steps

    1. Core Engineering implements the real-time client document validation linter in the borrower web portal.
    2. Formally decommission the manual document indexing and stacking queue (STG-02), reassigning staff to customer concierge.
    3. Conduct 30-day pilot of the future-state 8-day stream across 500 test applications to verify %C&A >= 85%.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    What it does

    This skill represents an authoritative current or explicitly approved target end-to-end flow from a qualifying trigger to an outcome valued by a named recipient. It normalizes stream/stage identities, boundaries, value objects, handoffs, queues, variants, supplied measures, evidence and gaps.

    Use it when

    Use when a declared decision needs a reproducible end-to-end value-stream representation, but start/end boundaries, recipients, outcomes, stages, handoffs, current/target state, measures or evidence conflict or are incomplete.

    For example: “Order delivery time spiked from 24h to 72h after launch, but pharmacy ops insists dispensing time is only 15 minutes and nobody knows where the prescription sits for two days.”

    What you get

    • Value Stream Specification

    Written as Markdown to <your output folder>/architecture/tasks/<run-id>/value-stream-mapping/.

    What it will not do

    Do not use merely to model a process, map a journey/capability/value chain/workflow, run Lean workshops/process mining, diagnose bottlenecks, optimize flow, design targets, invent metrics, plan implementation, or design architecture.

    How it works

    1. Check value stream mapping is required.
    2. Bound the stream by trigger and recipient outcome.
    3. Normalize stage identities and handoff boundaries.
    4. Normalize queues, WIP, and value objects.
    5. Map supplied flow measures and timing evidence.
    6. Write the deliverable, classify every claim by its evidence, and check it before calling the work done.

    What's in the package

    Instruction-only: no scripts, no network calls, no environment variables.

    • LICENSE.txt
    • SKILL.md
    • agents/openai.yaml
    • assets/output-template-task.md
    • references/domain-rules.md
    • references/operating-rules.md
    • references/output-contract.md

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    Do not use merely to model a process, map a journey/capability/value chain/workflow, run Lean workshops/process mining, diagnose bottlenecks, optimize flow, design targets, invent metrics, plan implementation, or design architecture.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Read Files
    Write Files

    Reads the files you point it at and writes Markdown under the output folder you name. No network access, no environment variables, and no bundled scripts.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    No. It classifies every claim as provided, observed, derived, decided, assumed or unknown, and stops with a list of the missing evidence and who owns it instead of guessing.

    No. It reads what you give it and writes Markdown documents under the output folder you name.

    Any agent that supports SKILL.md skills, including Claude Code, Codex CLI, Cursor and Gemini CLI. It has no scripts and makes no network calls.

    Unzip it into your agent's skills folder, for example: unzip value-stream-mapping.zip -d ~/.claude/skills/

    New in Business & Operations