--- title: 5 Kaizen Experiments to Cut Setup and Cycle Time in CNC Shops description: "Five practical kaizen experiments for small CNC shops to cut setup and cycle time: the metrics, targets and sprint template to run them." image: https://www.jitbase.com/hubfs/blog-images/5-kaizen-experiments-cut-setup-cycle-time-hero.jpg --- [+1 438 942-8501](tel:+1%20438%20942-8501) [Log In](https://app.jitbase.com/) - [English](https://www.jitbase.com/blog/5-kaizen-experiments-cut-setup-cycle-time) - [Français](https://www.jitbase.com/fr/blog/kaizen-cnc-reduire-temps-cycle-suivi-production) [![JITbase black logo](https://www.jitbase.com/hs-fs/hubfs/Logos/jitbase-logo-black-horiz.webp?width=175&height=88&name=jitbase-logo-black-horiz.webp)](https://www.jitbase.com) - Solutions Back ##### [Machine Monitoring](https://www.jitbase.com/machine-monitoring) - ##### [Machine Monitoring](https://www.jitbase.com/machine-monitoring) Back - [Live Dashboard](https://www.jitbase.com/machine-monitoring) - [Track OEE](https://www.jitbase.com/machine-monitoring#Track-OEE) - [Track Downtime Reasons](https://jitbase.com/machine-monitoring#Track-Downtime-Reasons) - [Reporting](https://jitbase.com/machine-monitoring#Reporting) - [Timelines](https://jitbase.com/machine-monitoring#Timelines) ##### [Production Monitoring](https://www.jitbase.com/production-monitoring) - ##### [Production Monitoring](https://www.jitbase.com/production-monitoring) Back - [Accurate Standard Times](https://jitbase.com/program-monitoring#Accurate-Standard-Times) - [Tool path & M00 tracking](https://jitbase.com/program-monitoring#Tool-path-M00-tracking) - [Performance tracking](https://jitbase.com/program-monitoring#Performance) - [CNC Program Improvement](https://jitbase.com/program-monitoring#CNC-Program-Improvement) - [Overtime Reasons](https://jitbase.com/program-monitoring#Overtime-Reasons) - [Lights-out Operations](https://jitbase.com/program-monitoring#Light-Out-Ope) ##### [Scheduling & Workforce Management](https://www.jitbase.com/workforce-management) - ##### [Scheduling & Workforce Management](https://www.jitbase.com/workforce-management) Back - [Operator Workload](https://jitbase.com/workforce-management#Operator-Workload) - [Workforce Scheduling](https://jitbase.com/workforce-management/#Operator-Daily-Allocation) - [Live Job Tracking](https://jitbase.com/workforce-management#Live-Job-Tracking) - [Production Planning and Scheduling](https://jitbase.com/workforce-management#Job-Operation-Planning) - [Live guidance for Operators](https://jitbase.com/workforce-management#Live-guidance-for-Operators) ##### [Edge Platform](https://www.jitbase.com/edge-platform) - ##### [Edge Platform](https://www.jitbase.com/edge-platform) Back - [Manage your own infrastructure](https://www.jitbase.com/edge-platform#Manage-your-own-infrastructure) - [Send Machine data to local server](https://www.jitbase.com/edge-platform#Machine-data-to-local-server) - [Drivers for standard protocols](https://www.jitbase.com/edge-platform#Drivers-for-standard-protocols) - [Integrations](https://www.jitbase.com/edge-platform#Integrations) - Resources Back ##### [Our Downloadable Resources](https://www.jitbase.com/download) - ##### [Our Downloadable Resources](https://www.jitbase.com/download) Back - [Case Studies](https://jitbase.com/download#case-studies) - [White Papers](https://jitbase.com/download#white-papers) - [Brochures](https://jitbase.com/download#brochures) - [Product & Integration](https://jitbase.com/download#Product-Integration) - [In the Media](https://jitbase.com/download#in-the-media) ##### [Education](https://www.jitbase.com/education) - ##### [Education](https://www.jitbase.com/education) Back - [Workforce Management vs. Machine Monitoring](https://jitbase.com/education#Workforce-Management-vs-Machine-Monitoring) - [How to start?](https://jitbase.com/education#How-to-start) - [Infrastructure & Cyber-Security](https://jitbase.com/education#Infrastructure-Cyber-Security) - [Why the Cloud?](https://jitbase.com/education#Why-the-Cloud) - [FAQ](https://jitbase.com/education#Education-FAQ) ##### [Forms](https://www.jitbase.com/demo) - ##### [Forms](https://www.jitbase.com/demo) Back - [Return on Investissement](https://www.jitbase.com/return-on-investment) - [Machines we connect](https://www.jitbase.com/machines-we-connect) - [Demo Request](https://www.jitbase.com/demo) ##### [Blog](https://www.jitbase.com/blog) - ##### [Blog](https://www.jitbase.com/blog) Back - [Machine Monitoring](https://www.jitbase.com/blog/tag/machine-monitoring) - [Labor Management](https://www.jitbase.com/blog/tag/labor-management) - [Production Planning and Scheduling](https://www.jitbase.com/blog/tag/production-planning-and-scheduling) - [Quality and Inspection](https://www.jitbase.com/blog/tag/quality-and-inspection) - [Plans](https://www.jitbase.com/plans) - Why JITbase Back - ##### [Why JITbase](https://www.jitbase.com/why-jitbase) - ##### [About Us](https://www.jitbase.com/about-us) - ##### [Partners](https://www.jitbase.com/partners) [Connect Machines for Free](https://sso.jitbase.com/realms/webapp/protocol/openid-connect/registrations?client_id=website-registration&response_type=code&scope=openid&redirect_uri=https://admin.jitbase.com) [+1 438 942-8501](tel:+1%20438%20942-8501) [Log In](https://app.jitbase.com/) - [English](https://www.jitbase.com/blog/5-kaizen-experiments-cut-setup-cycle-time) - [Français](https://www.jitbase.com/fr/blog/kaizen-cnc-reduire-temps-cycle-suivi-production)   [Book a demo](https://www.jitbase.com/demo) [Connect Machines for Free](https://sso.jitbase.com/realms/webapp/protocol/openid-connect/registrations?client_id=website-registration&response_type=code&scope=openid&redirect_uri=https://admin.jitbase.com) ![CNC operator organizing tooling and parts on a shop floor: kaizen experiments to cut setup and cycle time with JITbase](https://www.jitbase.com/hubfs/blog-images/5-kaizen-experiments-cut-setup-cycle-time-hero.jpg) Blog [Machine monitoring](https://www.jitbase.com/blog/tag/machine-monitoring) [Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring) # 5 Kaizen Experiments to Cut Setup and Cycle Time in CNC Shops [*written by* Judicael Deguenon on March 17, 2026](https://www.jitbase.com/blog/author/judicael-deguenon) Small CNC shops can reclaim hours of productive time with focused, measurable kaizen experiments that target setup and cycle time. This guide presents five hands-on experiments, from a one-day SMED pilot to validated cycle-time extraction from CAM programs. It also shows what to measure, which targets to set, and a 6-week sprint you can run. The goal is simple: run low-cost trials that produce measurable improvements, so you can increase throughput without hiring more staff. **TL;DR:** - Target fast wins first: a focused SMED pilot and small fixturing changes on your most frequent jobs, with an acceptance target of at least 30% less setup time. - Measure before you change: collect setup time, cutting time, operator touch time and interventions per part, with a stopwatch and a spreadsheet or with cycle-time monitoring. - Run a 6-week sprint: limit pilots to two people, define acceptance criteria before starting, and only scale changes that keep first-pass yield stable. ## Why Run Kaizen Experiments to Cut Setup and Cycle Time in Small CNC Shops Small job shops often run a mix of short runs and one-offs. Consider a six-machine shop where each machine spends one to two hours per day on setups and frequent operator interventions: that is 6 to 12 machine-hours lost every day. Short, targeted kaizen experiments can convert those losses into capacity. A kaizen experiment is a time-boxed, data-driven change: a clear hypothesis, a measurement plan, and acceptance criteria for success. Kaizen and ECRS (eliminate, combine, rearrange, simplify) are well-established lean approaches for reducing cycle time without major capital outlay. Other lean methods that apply here include SMED (single-minute exchange of dies), 5S, kanban, standard work and OEE tracking. Short experiments also reduce risk: they avoid long approval cycles and pay back quickly, which matters when hiring or large investments are not options. ## Set Up Baselines and Key Metrics to Track (What to Measure and How) Before changing anything, define your baseline and the metrics you will use to judge success. Keep the measurement plan simple so operators will follow it. Essential metrics: - **Setup time:** minutes from the last good part of the previous job to the first good part of the new job (wall clock). - **Total cycle time (door-to-door):** time from cycle start to door open for one part or batch. - **Active cutting time (spindle on):** machine-reported or measured spindle-on time. - **Operator touch time:** minutes the operator spends per setup or cycle. - **Interventions per part:** count of manual stops or corrections per batch or shift. - **First-pass yield:** percentage of parts accepted without rework. - **Throughput (parts per hour):** useful for scheduling and bottleneck analysis. - **OEE components:** availability, performance and quality, to track long-term trends. ### How to Collect Reliable Data with Minimal Hardware - Start with a stopwatch, a spreadsheet and randomized sampling of 10 to 20 setups and cycles. That gives a valid baseline quickly. - For ongoing pilots, consider low-cost cycle-time monitoring hardware or sensors; see the guide to [cycle time monitoring](https://www.jitbase.com/blog/implement-cycle-time-monitoring-cnc-shop-minimal-hardware) for minimal-hardware approaches. - Use machine data (controller-reported cycle), but always validate it with wall-clock runs: CAM times omit many real-world activities. - Track data per job and per machine, and tag it by operator and shift to find sources of variance. The article on how to [track machine OEE](https://www.jitbase.com/blog/en/blog/how-to-effectively-track-the-oee-of-your-machine-tools) shows how OEE adds context to cycle metrics. **Get your baseline without a stopwatch.** JITbase captures real cycle times, setups and changeovers on every connected CNC machine, so every kaizen experiment starts from measured data. [Explore production monitoring](https://www.jitbase.com/production-monitoring) The table below summarizes the five experiments, the metrics they affect, a realistic target to set, and the effort involved. The targets are starting points for your acceptance criteria, not guaranteed results. | Experiment | Metrics impacted | Example target | Time to implement | Rough cost | | --- | --- | --- | --- | --- | | Rapid SMED | Setup time, operator touch time, interventions | 30% or more setup reduction on the pilot job | 4 to 24 hours pilot | Under $500 (tooling, labels) | | Program cycle validation | Total cycle time, variance, scheduling accuracy | Close the gap between programmed and real cycle time | 1 to 3 days of validation runs | Minimal (time) | | Modular fixturing | Setup time, clamping time, throughput | Measurable setup reduction on repeat parts | 1 to 2 weeks pilot | $200 to $4,000 per fixture | | Operator checklists and simple automation | Interventions, defects, time between interventions | Fewer routine interventions on repeat jobs | 1 to 3 days pilot | Under $1,000 (probe cycles, labels) | | Workload balancing and kanban | Throughput, WIP, lead time | Higher throughput with less WIP | 1 to 4 weeks | Minimal (process change) | ### Targets and Reporting Cadence - Use shift-level reporting during the first two weeks of a pilot (a daily log of setups and interventions). - Then publish weekly summaries for the shop: average setup minutes per machine, interventions per day, validated cycle versus program cycle. - Set acceptance thresholds before the pilot. Example: the SMED pilot is accepted if average setup time drops by at least 30% without raising scrap by more than 1%. Two caveats: - CAM and post-processor times can be optimistic. Capture tool changes, probing and loading or unloading explicitly during validation. - Granularity matters: per-job, per-machine data shows where to scale. ## Experiment 1: Rapid SMED to Cut CNC Setup Time in Short, Repeatable Steps SMED divides changeover steps into external steps (done while the machine runs) and internal steps (the machine must stop). For small shops, a one-day SMED pilot focused on a frequent job family yields high returns. ### A 1-Day SMED Checklist Tailored to Small CNC Shops 1. Map the current setup with a stopwatch: record every step from the last good part to the first good part. 2. Label each step as internal or external. 3. Move external steps off the machine (tool pre-staging, parts staging). 4. Convert internal steps to external where possible (preload tool holders, pre-tighten clamps). 5. Simplify the remaining internal steps (single-point adjustments, captured tool offsets). 6. Standardize the final sequence and create a one-page standard work sheet. ### Pilot Measurements, Hypothesis and Acceptance Criteria - **Hypothesis:** pre-staged tools and labeled fixturing will cut setup time by at least 40% for Job A. The acceptance threshold below is lower (30%) on purpose: the hypothesis is the target, and the threshold is the minimum that justifies scaling the change. - **Measurement:** 10 baseline setups and 10 pilot setups, comparing mean and standard deviation. - **Acceptance:** mean setup time falls by at least 30% and first-pass yield stays within 1% of baseline. ### Common Quick Wins - Tool pre-staging on a labeled cart. - Standardized clamps and single-hand tightening points. - Single-point adjustment bolts and locator pins, so operators do not have to measure. - Shadow boards for tools, and tools labeled with their offsets. **Time-study example:** setups dropped from 45 minutes to 20 minutes after three internal steps were converted to external ones and locator pins were added. With four setups per machine per day, that frees about 100 minutes of run time per machine every day, and the variance between setups also fell. For the scheduling side of setup reduction, which removes changeovers instead of only shortening them, see the guide on [reducing setup time with better scheduling](https://www.jitbase.com/blog/reducing-setup-time-with-better-scheduling). Also consider small investments like shadow boards and pre-staging racks: they are cheap but force consistent behavior. Train operators with two supervised runs and document the new standard work. ## Experiment 2: Extract Accurate Cycle and Standard Times from CNC Programs and Validate Them CAM and post-processor reports give a baseline for cycle time, but they omit many realities of the shop floor: operator loading, real tool change times, probing cycles, and stoppages for coolant or chip clearing. ### How to Get Cycle Estimates from CAM and What They Miss - The CAM-reported cycle covers toolpath motion at programmed feeds. It usually misses or underestimates tool change times, probe cycles, pallet swaps, manual loading and interventions. - Controller cycle reports may log spindle-run time and M-code events, but they may not reflect door-open time or operator touches. ### Validation Runs: Quick Trials to Correct the Program-Based Standard Time Run a trial of 3 to 5 parts under normal shop conditions and record: - The controller-reported cycle, if available. - The wall-clock door-to-door time. - The time and reason for each manual intervention. - Tool change and probing times, measured separately. Then convert the results into a validated standard time: CAM cycle plus average tool change time, average load and unload time, and an intervention allowance (or zero if interventions disappear after the process improvement). **Example calculation:** CAM cycle 2.2 min + tool changes 0.8 min + load and unload 0.5 min + probing 0.2 min = validated cycle of 3.7 min. Use that figure for scheduling and quoting. The guide to [extracting cycle times from G-code](https://www.jitbase.com/blog/extract-cycle-times-from-g-code-in-7-steps) details the full method. Document both the program cycle and the validated standard in your routing. Once validated, integrate these numbers into scheduling; for guidance on feeding validated cycle times and operator labor data into higher-level systems, see how to [connect shop-floor data](https://www.jitbase.com/blog/integrate-shop-floor-data-erp-real-time-labor-tracking-oee). Lean thinking supports frequent validation. The Lean Enterprise Institute describes kaizen as continuous improvement that removes waste and refines standards; its [kaizen resource guide](https://www.lean.org/lexicon-terms/kaizen/) explains the PDCA approach that applies to cycle-time validation. ## Experiment 3: Modular Fixturing and Quick-Change Tooling, Small Investments with Big Impact Fixturing often determines how long a setup takes. Modular fixturing reduces clamping time and enables repeatable location. Small shops can use lower-cost approaches that still deliver real savings. ### Low-Cost Fixturing Upgrades That Reduce Clamping Time - Quick-clamp kits and single-turn clamps that tighten with one hand. - Removable subplates with pre-located pins and dowels. - Locator pins and hardened bushings, to avoid measuring at every setup. - Indexed fixture plates or small pallet systems for mills and lathes. - Magnetic bases for soft jaws or repeat fixtures on horizontal mills. ### How to Pilot Tooling Changes and Measure ROI - Choose a repeat part family or the shop’s most frequent short run. - Record baseline clamping and alignment time over 10 setups. - Install a subplate with locating pins, then measure again over 10 setups. - **Example ROI:** a $1,200 subplate that saves 15 minutes per setup on a job that runs 4 times a week saves 1 hour a week. At a machine rate of $40 per hour, payback takes about 30 weeks. Spreading the same subplate across several jobs shortens the payback. - Compare proprietary zero-point and pallet systems (fast and scalable, but costly and dependent on matching pallets) with DIY subplates (cheaper and flexible, slightly slower). DIY subplates let a shop test the concept before investing. A small pilot that reduces clamping time by 10 to 20 minutes per setup across several jobs frees machine hours that can be filled with additional production or preventive maintenance. For digital methods and case examples, see the APO [digital kaizen guidebook](https://www.apo-tokyo.org/wp-content/uploads/2024/08/ROC-SCG-Manualcompiled_EN_web_0902_PUB.pdf). ## Experiment 4: Reduce Manual Interventions with Operator Checklists and Simple Automation Manual interventions disrupt cycle times and raise scrap risk. Many of them are preventable with short checklists and small automation steps. ### Top Causes of Manual Interventions on CNC (and How to Eliminate Them) - **Wrong tooling or offsets:** use labeled tool carts and pre-checked offsets. - **Wrong program revision:** add a program revision check, with version stickers or controller comments. - **Missing clamps or wrong torque:** use visual clamp indicators and torque-controlled tools. - **Coolant or pressure problems:** add quick visual checks and scheduled top-ups. - **Fixturing errors:** use locator pins and fixture checklists. ### Designing Concise Operator Checklists and Fail-Safes Keep checklists under six steps and readable in under two minutes. Example of a six-step check before cycle start: 1. Confirm the program number and revision. 2. Verify that the tool list and offsets match the job card. 3. Confirm fixture location and clamp tightness. 4. Check the coolant level and chip conveyor. 5. Run a dry run or single-block probe cycle if programmed. 6. Announce the run start (in the scheduler or with the light stack). For automation, add probe cycles at the start of the program, controller program revision checks, and simple PLC signals that require operator acknowledgment before starting. Track interventions per day, mean time between interventions (MTBI) and the percentage of cycles needing an intervention. These metrics show clearly when automation or additional training is warranted. On repeat jobs, a checklist combined with a single probing cycle usually removes most routine interventions and reduces unplanned stops. ## Experiment 5: Workload Balancing, Small-Batch Routing and Kanban to Increase Throughput Reducing setup time only creates capacity if scheduling and routing use that capacity well. Workload balancing and small-batch routing let shops increase throughput without hiring. ### How to Balance Operator and Machine Workloads Without Hiring - Cluster repeat operations on specific machines during dedicated days to amortize setups. - Level the load by part family: group similar setups back to back. - Cross-train operators to cover peak shifts and bottleneck machines. - Use shift-based metrics so planners can see imbalances and move work before they turn into bottlenecks. **Balance operator workload with live data.** JITbase schedules jobs and allocates operators from real machine data, so the capacity freed by each kaizen experiment is actually used. [Explore scheduling and workforce management](https://www.jitbase.com/workforce-management) ### Using Small Batches and Kanban to Reduce WIP and Lead Time - Small batches reduce lead time and expose problems earlier. - Implement a simple two-bin kanban for recurring jobs: a visual cue triggers the next small batch and avoids large queues. - Pull (kanban) reduces WIP and lead time for recurring products; push (schedule-driven) suits tight due dates and one-offs. Use kanban where repeat jobs exist, and schedule-driven planning for custom or high-priority work. - Track throughput (parts per day), WIP and lead time to measure success. With less work waiting between machines, each job moves through the shop faster, so smaller batches shorten lead time as long as the extra setups stay affordable. For deeper tactics, see the [workload balancing playbook](https://www.jitbase.com/blog/lean-workload-balancing-playbook) and the [scheduling and kanban blueprint](https://www.jitbase.com/blog/throughput-boost-blueprint-scheduling-kanban), which show how to turn reduced setup time into consistent throughput gains. ### When to Change Routing vs When to Change Batch Size - Change routing if a process step is the bottleneck and can be offloaded. - Change batch size if lead time or late discovery of defects is the main concern. Shorter setups lower the economic batch size, and the guide to [lot sizing for CNC shops](https://www.jitbase.com/blog/lot-sizing-cnc-shops) explains how to set it for each machine. - In practice, try a hybrid: reduce batch size while moving repeat operations to a cluster day to capture both benefits. ## A 6-Week Kaizen Sprint Template: Plan, Run, Measure and Scale A simple sprint keeps experiments focused and measurable. Below is a compact 6-week plan, with who does what. ### Week-by-Week Plan and Roles - **Week 1 (baseline and planning):** the planner and production lead collect 10 to 20 samples of setup and cycle times, then define the hypothesis, success criteria and data templates. Roles: shop lead, operator champion, process engineer. - **Weeks 2 and 3 (implement experiment A):** two people (operator champion and engineer) run the pilot on a single job family. Daily logs capture setup minutes, cycle times and interventions. - **Week 4 (measure and decide):** analyze the pilot data and compare it with the baseline. Decide to iterate, stop, or start a second experiment. - **Week 5 (implement experiment B or iterate A):** if A succeeded, pilot a second job family or run experiment 2 (program validation). Keep the daily log running until the end of the sprint. - **Week 6 (scale or roll back):** if the acceptance criteria are met, create standard work, update routings and plan the shop-wide rollout. ### Data Collection Templates, Acceptance Criteria and Scale-Up Checklist - Use a daily log with these fields: job, machine, operator, baseline setup (min), pilot setup (min), program cycle time, validated cycle time, number of interventions, first-pass yield. - Example acceptance: setup reduction of at least 30% and a first-pass yield change of no more than 1 percentage point. - Scale-up checklist: write standard work, update ERP or MES routings and validated cycle times, train two operators, and schedule a first follow-up audit at 30 days. When folding experiment outcomes into planning and routing, adjust the production plan and scheduling parameters; see how to [optimize the production plan](https://www.jitbase.com/blog/optimize-manufacturing-scheduling-production-plan) and how to use [real-time data for scheduling](https://www.jitbase.com/blog/how-real-time-data-enhances-manufacturing-scheduling-and-efficiency). Decide who signs off: the production manager approves, quality signs off on yield, and engineering documents the changes in job cards. Keep experiments small: two people running each pilot, changes small enough to test within a week or two, and acceptance criteria documented before starting. That discipline prevents scope creep and protects quality. ## The Bottom Line: Prioritize Experiments with the Fastest Payback and Lowest Disruption Start with SMED and program cycle validation: they usually offer the fastest payback and the least disruption. Always define the hypothesis, measurement plan and acceptance criteria before starting a pilot. If an experiment cuts operator touch time and pays back in under eight weeks, prioritize it; defer changes that need more than $5,000 and long lead times. For tracking, keep a simple dashboard showing daily setup minutes, interventions, validated cycle time versus CAM time, and throughput trends, so decisions stay data-driven. The central goal remains the same: reduce setup and cycle time in ways that increase throughput without compromising quality. **What would your kaizen gains be worth?** Estimate the return of shorter setups and validated cycle times with your own production data. [Calculate your ROI](https://www.jitbase.com/return-on-investment) ## Frequently Asked Questions ### How long should a kaizen experiment run before I judge results? In most small shops, two to six weeks. Use the first week for baseline and planning, the second for the initial pilot and daily measurement, and weeks three to six for stabilization and iteration. A quick fix such as a one-day SMED pilot can show a clear signal within days, while changes to fixturing, scheduling or workload balancing need the longer window because their effects depend on the job mix of the period. Low-volume jobs may need longer to collect enough samples: aim for at least 10 valid setups or 30 parts for cycle-time comparisons. Define the acceptance criteria in advance (for example, at least 30% less setup time and no increase in scrap) so you can decide objectively at the end of the sprint. If the data is still noisy at week six, extend the pilot by two weeks rather than judging on a handful of runs, and do not change two variables at once or you will not know which one worked. ### Which experiment gives the fastest payback? SMED-style changeover reduction and the validation of CAM program cycle times normally deliver the quickest return. A one-day SMED pilot that converts internal steps to external ones and adds locating pins can significantly cut setup time and pay back within weeks on frequent jobs, because every setup on that job family benefits from the change. Program validation fixes scheduling and quoting errors with virtually no hardware cost, only the time needed for measurement and adjustment. Modular fixturing pays back more slowly, since it involves a hardware purchase: in the example above, a $1,200 subplate saving 15 minutes on a job run four times a week takes about 30 weeks to pay for itself, which falls to a shorter period when the same subplate serves several jobs. Operator checklists and workload balancing cost little but their gains are harder to attribute. As a rule, start with the experiment that has the lowest cost, the shortest pilot and the most frequent job, then reinvest the freed machine hours in the next one. ### Can I measure cycle time without new hardware? Yes. Stopwatch time studies and simple spreadsheets work well for pilots. Record wall-clock door-to-door times, operator touch time and interventions for 10 to 20 runs, and note the reason for each stop so you can separate planned events, such as tool changes and probing, from avoidable ones. Randomize the sampling across shifts and operators, otherwise a single good day can distort the baseline. The limit of manual tracking is consistency: it depends on someone writing down every run, and the data rarely survives beyond the pilot. Once a pilot proves an approach, consider low-cost sensors or cycle-time monitoring for automated, long-term tracking, and always cross-check the machine-reported cycle with a few wall-clock runs, since controller data can miss door-open time and operator touches. Starting manually still has a benefit: it forces the team to agree on definitions before any tool is chosen. ### How do I standardize changes after a successful experiment? Document the new steps as standard work, update job cards and routings with validated cycle times and setup procedures, and train at least two operators so the change does not depend on one person. Update ERP or MES parameters for run times and labor allowances, otherwise the schedule and the quotes will keep using the old numbers. The production manager should sign off on the updates, and quality should confirm first-pass yield before a full rollout. Schedule a 30-day audit to confirm the change holds in normal production, comparing the daily log with the baseline and checking that operators still follow the one-page standard work sheet. If results slip, find out whether the cause is the procedure, the training or a change in the job mix before correcting it. Once the change is stable, extend it to the next job family and record the result, so that each experiment builds on the previous one instead of starting from scratch. ### What if an experiment reduces setup time but increases defects? Stop scaling and perform a root-cause analysis. Collect defect data and compare it with the baseline. The cause is often a skipped verification step or unclear standard work, and reintroducing a probe cycle or a short checklist fixes most cases. Quality must be the gatekeeper: time savings should never come at the expense of first-pass yield, and the acceptance criteria defined before the pilot (for example, scrap no more than 1% above baseline) settle the question without debate. Review each shortened step with the operators, since they know which checks were removed along with the wasted motion. Test the fix on the same job family over another 10 setups before extending it, and keep the time gain only if first-pass yield returns to baseline. If the defects persist, roll back to the previous procedure and document what was learned: a failed experiment that is recorded still improves the next one. Require no material increase in defects before any rollout. #### SHARE [mailto:email@example.com?subject=Mail%20from%20our%20Website](mailto:email@example.com?subject=Mail%20from%20our%20Website) ## Related Articles [![Production planner reviewing a digital scheduling dashboard beside CNC machines.](https://www.jitbase.com/hs-fs/hubfs/blog-images/implanter-planificateur-numerique-saas-hero.jpg?width=352&name=implanter-planificateur-numerique-saas-hero.jpg)](https://www.jitbase.com/blog/digital-production-scheduler-implementation-guide) [Machine monitoring](https://www.jitbase.com/blog/tag/machine-monitoring), [Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring) ### [Digital Production Scheduler: A Step-by-Step Implementation Guide](https://www.jitbase.com/blog/digital-production-scheduler-implementation-guide) Read more [![Shop manager standing at a workbench in a small CNC machine shop evaluating monitoring software options — MachineMetrics alternative with JITbase](https://www.jitbase.com/hs-fs/hubfs/blog-images/machinemetrics-alternative-small-cnc-shops-hero.jpg?width=352&name=machinemetrics-alternative-small-cnc-shops-hero.jpg)](https://www.jitbase.com/blog/machinemetrics-alternative-cnc-shops) [Machine monitoring](https://www.jitbase.com/blog/tag/machine-monitoring), [Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring) ### [MachineMetrics Alternative for Small CNC Shops (2026)](https://www.jitbase.com/blog/machinemetrics-alternative-cnc-shops) Read more [![CNC operator carrying stacked parts across a machine shop, illustrating lean workload balancing, shop-floor flow optimization, and efficient task distribution with JITbase.](https://www.jitbase.com/hs-fs/hubfs/blog-images/lean-workload-balancing-playbook-hero.jpg?width=352&name=lean-workload-balancing-playbook-hero.jpg)](https://www.jitbase.com/blog/lean-workload-balancing-playbook) [Machine monitoring](https://www.jitbase.com/blog/tag/machine-monitoring), [Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring) ### [Lean Workload Balancing — A Practical Playbook to Reduce Operator Bottlenecks Without Hiring](https://www.jitbase.com/blog/lean-workload-balancing-playbook) Read more [![Operator supervising a CMM inspection of a machined metal part, illustrating CNC machining quality control, dimensional inspection, and production verification with JITbase.](https://www.jitbase.com/hs-fs/hubfs/blog-images/ultimate-guide-cnc-machining-cmm-inspection-hero.jpg?width=352&name=ultimate-guide-cnc-machining-cmm-inspection-hero.jpg)](https://www.jitbase.com/blog/ultimate-guide-cnc-machining-cmm-inspection) [Machine monitoring](https://www.jitbase.com/blog/tag/machine-monitoring), [Production Monitoring](https://www.jitbase.com/blog/tag/production-monitoring) ### [the Ultimate Guide to CNC Machining: Basics, Program Optimization, Machine Monitoring and Tracking, and CMM Inspection Software](https://www.jitbase.com/blog/ultimate-guide-cnc-machining-cmm-inspection) Read more [![JITbase block logo](https://www.jitbase.com/hs-fs/hubfs/eca01011d7169e8c6395a8d7eebe802d.webp?width=317&height=158&name=eca01011d7169e8c6395a8d7eebe802d.webp)](https://www.jitbase.com) ![image-2](https://www.jitbase.com/hs-fs/hubfs/image-2.webp?width=156&height=78&name=image-2.webp) Solutions - [Machine Monitoring](https://www.jitbase.com/machine-monitoring) - [Production Monitoring](https://www.jitbase.com/production-monitoring) - [Scheduling & Workforce Management](https://www.jitbase.com/workforce-management) - [Edge Platform](https://www.jitbase.com/edge-platform) - [Plans](https://www.jitbase.com/plans) Resources - [Download](https://www.jitbase.com/download) - [Education](https://www.jitbase.com/education) - [Return on Investment](https://www.jitbase.com/return-on-investment) - [CNC Machines we connect](https://www.jitbase.com/machines-we-connect) - [Demo Request](https://www.jitbase.com/demo) Why JITbase - [Why JITbase](https://www.jitbase.com/why-jitbase) - [About Us](https://www.jitbase.com/about-us) - [Partners](https://www.jitbase.com/partners) - [Contact Us](https://www.jitbase.com/contact) [Book a demo](https://www.jitbase.com/demo) [Connect Machines for Free](https://sso.jitbase.com/realms/webapp-ngen/protocol/openid-connect/registrations?client_id=website-frontend&response_type=code&scope=openid%20email&redirect_uri=https://admin.jitbase.com/next-gen) © 2026 All rights reserved. - [Privacy Policy](https://www.jitbase.com/privacy-policy) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Judicael Deguenon", "url" : "https://www.jitbase.com/blog/author/judicael-deguenon" }, "dateModified" : "2026-10-08T16:25:36.228Z", "datePublished" : "2026-03-17T12:41:12.000Z", "headline" : "5 Kaizen Experiments to Cut Setup and Cycle Time in CNC Shops", "image" : [ "https://www.jitbase.com/hubfs/blog-images/5-kaizen-experiments-cut-setup-cycle-time-hero.jpg" ], "mainEntityOfPage" : { "@id" : "https://www.jitbase.com/blog/5-kaizen-experiments-cut-setup-cycle-time", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.jitbase.com/hubfs/logo%20jitbase%201.svg" }, "name" : "JITbase" } } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "In most small shops, two to six weeks. Use the first week for baseline and planning, the second for the initial pilot and daily measurement, and weeks three to six for stabilization and iteration. A quick fix such as a one-day SMED pilot can show a clear signal within days, while changes to fixturing, scheduling or workload balancing need the longer window because their effects depend on the job mix of the period. Low-volume jobs may need longer to collect enough samples: aim for at least 10 valid setups or 30 parts for cycle-time comparisons. Define the acceptance criteria in advance (for example, at least 30% less setup time and no increase in scrap) so you can decide objectively at the end of the sprint. If the data is still noisy at week six, extend the pilot by two weeks rather than judging on a handful of runs, and do not change two variables at once or you will not know which one worked." }, "name" : "How long should a kaizen experiment run before I judge results?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "SMED-style changeover reduction and the validation of CAM program cycle times normally deliver the quickest return. A one-day SMED pilot that converts internal steps to external ones and adds locating pins can significantly cut setup time and pay back within weeks on frequent jobs, because every setup on that job family benefits from the change. Program validation fixes scheduling and quoting errors with virtually no hardware cost, only the time needed for measurement and adjustment. Modular fixturing pays back more slowly, since it involves a hardware purchase: in the example above, a $1,200 subplate saving 15 minutes on a job run four times a week takes about 30 weeks to pay for itself, which falls to a shorter period when the same subplate serves several jobs. Operator checklists and workload balancing cost little but their gains are harder to attribute. As a rule, start with the experiment that has the lowest cost, the shortest pilot and the most frequent job, then reinvest the freed machine hours in the next one." }, "name" : "Which experiment gives the fastest payback?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yes. Stopwatch time studies and simple spreadsheets work well for pilots. Record wall-clock door-to-door times, operator touch time and interventions for 10 to 20 runs, and note the reason for each stop so you can separate planned events, such as tool changes and probing, from avoidable ones. Randomize the sampling across shifts and operators, otherwise a single good day can distort the baseline. The limit of manual tracking is consistency: it depends on someone writing down every run, and the data rarely survives beyond the pilot. Once a pilot proves an approach, consider low-cost sensors or cycle-time monitoring for automated, long-term tracking, and always cross-check the machine-reported cycle with a few wall-clock runs, since controller data can miss door-open time and operator touches. Starting manually still has a benefit: it forces the team to agree on definitions before any tool is chosen." }, "name" : "Can I measure cycle time without new hardware?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Document the new steps as standard work, update job cards and routings with validated cycle times and setup procedures, and train at least two operators so the change does not depend on one person. Update ERP or MES parameters for run times and labor allowances, otherwise the schedule and the quotes will keep using the old numbers. The production manager should sign off on the updates, and quality should confirm first-pass yield before a full rollout. Schedule a 30-day audit to confirm the change holds in normal production, comparing the daily log with the baseline and checking that operators still follow the one-page standard work sheet. If results slip, find out whether the cause is the procedure, the training or a change in the job mix before correcting it. Once the change is stable, extend it to the next job family and record the result, so that each experiment builds on the previous one instead of starting from scratch." }, "name" : "How do I standardize changes after a successful experiment?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Stop scaling and perform a root-cause analysis. Collect defect data and compare it with the baseline. The cause is often a skipped verification step or unclear standard work, and reintroducing a probe cycle or a short checklist fixes most cases. Quality must be the gatekeeper: time savings should never come at the expense of first-pass yield, and the acceptance criteria defined before the pilot (for example, scrap no more than 1% above baseline) settle the question without debate. Review each shortened step with the operators, since they know which checks were removed along with the wasted motion. Test the fix on the same job family over another 10 setups before extending it, and keep the time gain only if first-pass yield returns to baseline. If the defects persist, roll back to the previous procedure and document what was learned: a failed experiment that is recorded still improves the next one. Require no material increase in defects before any rollout." }, "name" : "What if an experiment reduces setup time but increases defects?" } ] } ```