{"id":7436,"date":"2026-06-09T10:50:00","date_gmt":"2026-06-09T02:50:00","guid":{"rendered":"https:\/\/www.jodoo.com\/blog\/?p=7436"},"modified":"2026-06-15T11:24:35","modified_gmt":"2026-06-15T03:24:35","slug":"%e3%83%aa%e3%83%bc%e3%83%b3%e7%94%9f%e7%94%a3%e6%96%b9%e5%bc%8f%e3%83%84%e3%83%bc%e3%83%ab","status":"publish","type":"post","link":"https:\/\/www.jodoo.com\/blog\/ja-jp\/lean-manufacturing-tools","title":{"rendered":"\u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb\uff1a\u30c7\u30b8\u30bf\u30eb\u5316\u3055\u308c\u305f\u88fd\u9020\u73fe\u5834\u5b9f\u884c\u306e\u305f\u3081\u306e\u5b9f\u8df5\u30ac\u30a4\u30c9"},"content":{"rendered":"

<\/span>Introduction: Why Lean Manufacturing Tools Still Matter on the Digital Shop Floor<\/span><\/h2>\n\n\n\n

Many manufacturers lose significant performance through everyday execution gaps, not only through major breakdowns. In many plants, small delays, missing materials, late quality feedback, and inconsistent shift follow-up quietly reduce output long before anyone sees the full impact. That is why \u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb<\/a><\/strong> still matter: they are designed to remove waste, stabilize work, and make problems visible early.<\/p>\n\n\n\n

Lean tools are the practical methods behind lean manufacturing techniques, such as 5S, Kanban, value stream mapping, Andon, and standard work<\/strong>. Their purpose is straightforward: improve flow, reduce variation, and help teams respond faster without adding labor, inventory, or unnecessary process steps. But in modern factories, especially those running multiple shifts or mixed production, paper boards and manual checklists often cannot keep pace with the shop floor.<\/p>\n\n\n\n

Digital shop-floor execution closes that gap. It means turning lean methods into daily actions through digital forms, workflows, mobile reporting, and live dashboards, so issues are captured, assigned, escalated, and reviewed in real time. In this article, you will see which lean tools matter most, what problems they are meant to solve, and how to make them easier to sustain in actual plant operations.<\/p>\n\n\n\n

<\/span>What Lean Manufacturing Tools Are Designed to Fix in Modern Plants<\/span><\/h2>\n\n\n\n

In most discrete manufacturing plants, the problem is not a lack of lean tools. It is the gap between the intended method and what actually happens during the shift. A production line may have a 5S checklist, a kanban system, a standard work sheet, and a daily board, yet still lose output because abnormalities are seen too late, passed on poorly, or never closed. That execution gap is exactly what lean manufacturing techniques are meant to fix.<\/p>\n\n\n\n

To make that concrete, imagine an electronics assembly line building control boards across three shifts. At 9:20 a.m., an operator notices a feeder mis-pick issue causing intermittent solder defects, the WIP rack near final test is already filling, and one kanban card for a common connector is missing from the replenishment loop. None of these issues is catastrophic on its own, but together they create waiting, rework, extra motion, and unclear ownership by the end of the shift.<\/p>\n\n\n\n

<\/span>Delayed Visibility Turns Small Abnormalities Into Output Loss<\/span><\/h3>\n\n\n\n

On a busy line, the first failure is often not the defect itself but the delay in making it visible. An operator may spot rising rejects at SMT inspection, but if that information stays local until the next hourly walk or end-of-shift review, the line continues producing bad units or starving downstream stations. Lean tools are designed to surface abnormalities early so action happens while the problem is still small.<\/p>\n\n\n\n

In our assembly-line example, the feeder mispick starts as a minor stoppage and a few solder defects. Because the line leader is covering another area, the operator writes the issue on a whiteboard and keeps running to avoid falling behind the takt target. By the time quality checks the board later, reject counts have tripled, the final test is waiting on good boards, and rework has become the biggest consumer of labor for that hour.<\/p>\n\n\n\n

Therefore, \u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb<\/strong><\/a> are not just records or visual aids; they shorten the time between abnormality, response, and containment. Without that speed, even well-trained teams end up managing yesterday\u2019s problems instead of the current shift\u2019s losses.<\/p>\n\n\n\n

<\/span>Inconsistent Execution Across Shifts Creates Hidden Variation<\/span><\/h3>\n\n\n\n

A second problem is inconsistency between shifts, supervisors, and lines. Many plants define standard work clearly, but actual execution drifts because training is uneven, changeovers are handled differently, and shift handovers rely on verbal updates. The result is hidden variation that looks like random instability but is often a failure to sustain lean discipline.<\/p>\n\n\n\n

On the same electronics line, first shift flags the feeder issue and temporarily adjusts inspection frequency. At handover, the outgoing technician mentions the issue verbally but does not record the suspected cause, the parts replaced, or whether the nozzle was changed. Second shift then resets the machine, assumes the problem is solved, and reduces checks, only to see defects return an hour later under a different operator.<\/p>\n\n\n\n

This is one reason continuous improvement tools often stall after initial rollout. Plants may complete audits and post standard work instructions, but they do not control whether the same response happens every time under real shift pressure. The standard may say what to do, but execution breaks down when that standard is hard to access, easy to bypass, or disconnected from escalation.<\/p>\n\n\n\n

<\/span>Paper-Based Follow-Up Slows the Improvement Loop<\/span><\/h3>\n\n\n\n

Traditional lean methods often rely on paper tags, manual checklists, logbooks, and spreadsheet trackers. These can work in a stable, low-complexity area, but they struggle once issue volume rises and multiple functions must coordinate. The problem is not that paper is always wrong; it is that paper makes follow-up slow, fragmented, and hard to audit.<\/p>\n\n\n\n

Back on the assembly line, quality records the defect spike on a paper nonconformance form, maintenance notes the feeder check in a separate logbook, and materials writes down the missing connector card for later review. By mid-afternoon, three records exist for one chain of disruption, but no one has a single view of whether containment is in place, who owns the root cause, or whether the material signal failure is connected to the defect event. The team has data, but not a usable workflow.<\/p>\n\n\n\n

This is where lean tools like value stream mapping and kaizen activity often lose momentum after the workshop stage. Teams identify delays, rework loops, and handoff waste correctly, yet the follow-through sits in disconnected files and meeting notes. In other words, the plant can diagnose waste but still fail to remove it at the pace needed on a live production floor.<\/p>\n\n\n\n

<\/span>Weak Accountability Lets Problems Survive Across the Shift<\/span><\/h3>\n\n\n\n

The last major gap is accountability. In many factories, everyone sees the issue, but ownership is vague once it crosses functions. The supervisor is trying to ensure production output. The quality department is concerned with control issues. The maintenance department is looking for the causes of equipment failures. The materials department is focused on resolving shortages. Yet no one owns the full chain from signal to closure.<\/p>\n\n\n\n

In our example, the missing kanban card causes a connector shortage at the exact time the defect issue is reducing usable output. Final test blames SMT for unstable supply, SMT blames materials for late replenishment, and materials argue that the signal was never triggered. By the evening review, the line has lost throughput from three forms of waste at once: waiting at downstream test, extra transport of rework trays, and excess motion as staff search for material and status updates.<\/p>\n\n\n\n

Lean manufacturing tools<\/strong><\/a> are built to make this ownership visible. A proper lean system should clarify who responds first, who contains the issue, who approves the workaround, and who verifies closure. When that accountability is weak, even a plant with 5S, daily meetings, and improvement boards can repeat the same disruption across multiple shifts.<\/p>\n\n\n\n

<\/span>Why Traditional Lean Controls Break Down at Scale<\/span><\/h3>\n\n\n\n

Manual lean controls tend to work best when the area is small, the team is stable, and the supervisor can personally monitor every exception. They break down when a plant adds product variants, more shifts, tighter customer response times, and cross-functional dependencies. That is why automotive and electronics manufacturers often find that the same lean tools that worked on one line become harder to sustain across ten.<\/p>\n\n\n\n

The electronics line in our example does not fail because the team lacks lean knowledge. It fails because issue visibility is delayed, standard work is inconsistently applied, follow-up is split across paper and spreadsheets, and accountability weakens at each handoff. Lean tools are meant to close exactly these gaps so problems are seen earlier, acted on faster, and carried through to resolution instead of being rediscovered on the next shift.<\/p>\n\n\n\n

<\/span>The Core Lean Tools Every Operations Team Should Know<\/span><\/h2>\n\n\n\n

Lean manufacturing tools<\/strong><\/a> work best as a system, not as isolated initiatives. Some tools stabilize the workplace, some control material flow, some prevent defects, and some make labor deployment more efficient. For operations leaders, the practical question is not which tool is \u201cbest,\u201d but which one addresses the next constraint in your process. Used together, these lean tools create a tighter daily management loop across execution, problem-solving, quality, and capacity.<\/p>\n\n\n\n

A useful way to group them is by purpose. 5S<\/strong> \u305d\u3057\u3066 standard work<\/strong> strengthen daily control on the shop floor; the kanban system<\/strong> improves material flow; \u30dd\u30ab\u30e8\u30b1<\/strong> helps prevent errors, while Andon<\/strong> makes quality and process abnormalities visible before they spread; \u30d0\u30ea\u30e5\u30fc\u30b9\u30c8\u30ea\u30fc\u30e0\u30de\u30c3\u30d4\u30f3\u30b0<\/strong> helps teams see end-to-end waste; and line balancing<\/strong> improves labor and equipment utilization. \u30ab\u30a4\u30bc\u30f3<\/strong> sits across all of them as the discipline of ongoing improvement rather than a single method.<\/p>\n\n\n\n

\"Infographic<\/figure>\n\n\n\n

<\/span>5S: Build a Workplace That Supports Reliable Execution<\/span><\/h3>\n\n\n\n

5S <\/strong>lean manufacturing focuses on sorting, organizing, cleaning, standardizing, and sustaining the work area. It is most useful where operators lose time searching for tools, materials, gauges, or documents, or where clutter hides abnormal conditions. In machining, assembly, and maintenance environments, strong 5S often improves changeover speed, safety, and first-pass yield at the same time.<\/p>\n\n\n\n

The most common mistake is treating 5S as a one-time cleanup campaign. Plants may repaint floors and label shelves, but if ownership, audit discipline, and replenishment rules are weak, the area gradually returns to disorder. A better approach is to tie 5S to specific performance outcomes, such as reducing tool retrieval time from 90 seconds to 20 seconds or cutting motion waste in a cell by 15%.<\/p>\n\n\n\n

<\/span>Kaizen: Turn Small Improvements Into a Management Routine<\/span><\/h3>\n\n\n\n

\u30ab\u30a4\u30bc\u30f3<\/strong> is the structured practice of making frequent, incremental improvements close to the work. It is especially effective when frontline teams face recurring friction points that do not justify a major engineering project, such as awkward fixture placement, slow inspection handoffs, or repeated waiting during model changeovers. Over time, many small changes can produce large gains in throughput and stability.<\/p>\n\n\n\n

A common implementation mistake is running kaizen events without a follow-up system. Teams generate ideas, post action lists, and then lose momentum because owners, deadlines, and verification steps are unclear. Strong kaizen depends on a simple discipline: identify a problem, test a countermeasure, measure the result, and standardize only what works.<\/p>\n\n\n\n

<\/span>Kanban System: Control Replenishment Without Overproducing<\/span><\/h3>\n\n\n\n

A kanban system<\/strong> is designed to signal when material should be replenished, moved, or produced. It works best in environments with repeatable demand patterns, known consumption rates, and clear container quantities, such as fastener supply for assembly, packaging material refill, or subassembly supermarkets feeding final production. The goal is not just lower inventory, but smoother flow with fewer shortages and less overproduction.<\/p>\n\n\n\n

The biggest mistake is launching Kanban with poor parameter design. If lot sizes, reorder points, lead times, or container quantities are inaccurate, the system creates either stockouts or excess inventory, and teams quickly lose confidence in it. Effective kanban requires disciplined review of actual consumption, supplier response time, and floor-level adherence to pull rules.<\/p>\n\n\n\n

<\/span>Value Stream Mapping: See Waste Across the Full Process<\/span><\/h3>\n\n\n\n

\u30d0\u30ea\u30e5\u30fc\u30b9\u30c8\u30ea\u30fc\u30e0\u30de\u30c3\u30d4\u30f3\u30b0<\/strong> helps teams visualize material flow and information flow from order to delivery. It is most valuable when performance problems cross departmental boundaries, such as long queue time between stamping and welding, repeated approval delays before production release, or excessive waiting in incoming inspection. This tool helps operations teams distinguish process time from waiting time, which is often where the largest hidden losses sit.<\/p>\n\n\n\n

The common mistake is producing a map that is accurate but not actionable. A future-state map should identify a small number of priority improvements, such as reducing batch size, removing a redundant inspection step, or shortening handoff time between planning and production. In many plants, the map itself is less important than the decisions it drives over the next 30 to 90 days.<\/p>\n\n\n\n

<\/span>Andon: Make Abnormal Conditions Visible and Escalatable<\/span><\/h3>\n\n\n\n

Andon<\/strong> is a visual or digital signal that alerts the team when a problem needs attention. It is most useful where a short delay in response can create scrap, line stoppage, missed takt, or safety risk, such as a torque fault in assembly, feeder failure on an SMT line, or a missing component at pack-out. The strength of Andon is speed: it turns hidden problems into visible action triggers.<\/p>\n\n\n\n

A typical mistake is designing Andon only as a display, not as a response process. Flashing lights or status boards may show that something is wrong, but if response roles are unclear, escalation is inconsistent, and closure is not tracked, the tool becomes background noise. Good Andon design links alert types to response expectations, such as who must react, within how many minutes, and what constitutes containment.<\/p>\n\n\n\n

<\/span>Standard Work: Lock In the Best Known Method<\/span><\/h3>\n\n\n\n

Standard work<\/strong> defines the current best method for performing a task safely, consistently, and at the required pace. It is most important in operations with repeatable sequences, operator variation, and high-quality sensitivity, such as manual assembly, setup verification, in-process inspection, and shift handover routines. Without standard work, improvement gains are difficult to sustain because each operator may perform the same task differently.<\/p>\n\n\n\n

The most frequent mistake is creating documents that are technically complete but operationally unusable. If instructions are too long, outdated, disconnected from actual cycle time, or inaccessible at the point of use, operators will rely on memory or informal coaching instead. Effective standard work is visual, current, and specific enough to reduce variation without preventing necessary problem-solving.<\/p>\n\n\n\n

<\/span>Poka-Yoke: Prevent Errors Before They Become Defects<\/span><\/h3>\n\n\n\n

\u30dd\u30ab\u30e8\u30b1<\/strong> refers to mistake-proofing methods that either prevent an error or make it immediately obvious. It is especially valuable in processes where a small human error can create expensive downstream impact, such as reversed connector insertion, wrong-part picking, skipped fastening steps, or incorrect label application. In quality-critical operations, Poka-Yoke often delivers a faster return than additional inspection because it attacks the defect at the source.<\/p>\n\n\n\n

A common mistake is relying on warnings instead of true prevention. Labels, reminders, and retraining have value, but they are weaker controls than fixtures, sensors, interlocks, or part designs that make the wrong action difficult or impossible. The best Poka-Yoke solutions reduce dependence on memory, attention, and operator interpretation.<\/p>\n\n\n\n

<\/span>Line Balancing: Match Work Content to Takt and Capacity<\/span><\/h3>\n\n\n\n

Line balancing<\/strong> is the practice of distributing work evenly across operators and stations to match takt time and reduce bottlenecks. It is most useful in assembly lines or mixed-model environments where uneven work content creates waiting, overburden, or recurring backlog at one station. Better balance improves flow, labor productivity, and schedule attainment without necessarily adding headcount.<\/p>\n\n\n\n

The most common mistake is balancing based on averages rather than actual observed work. If teams ignore walking time, model mix variation, rework frequency, or machine interaction, a line may look balanced on paper and still miss output targets in practice. Good balancing uses real cycle-time data and is reviewed whenever demand, product mix, or staffing changes.<\/p>\n\n\n\n

<\/span>How to Turn Lean Tools Into Digital Shop-Floor Workflows<\/span><\/h2>\n\n\n\n

For most plants, the priority is not to deploy all lean manufacturing techniques at once. It is to choose the tools that fit the actual condition of the process, then make sure each tool is tied to a routine that people can maintain. The practical shift is simple: treat each lean tool not as a document or meeting ritual, but as a workflow with a trigger, owner, action, deadline, and review point. That is what makes \u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb<\/strong><\/a> sustainable in daily operations, instead of being dependent on the supervisor’s memory. <\/p>\n\n\n\n

A useful mapping looks like this: 5S lean manufacturing<\/strong> becomes a mobile audit form with scores, photos, and corrective actions; the kanban system<\/strong> becomes a replenishment trigger tied to min-max levels; \u30d0\u30ea\u30e5\u30fc\u30b9\u30c8\u30ea\u30fc\u30e0\u30de\u30c3\u30d4\u30f3\u30b0<\/strong> becomes a tracked list of bottleneck-reduction actions; Andon<\/strong> becomes an escalation workflow; and standard work<\/strong> becomes controlled SOP distribution with acknowledgment and revision tracking. In other words, traditional lean tools become digital transactions that can be captured, routed, measured, and closed. That turns continuous improvement tools into operating discipline rather than good intentions.<\/p>\n\n\n\n

\"Diagram<\/figure>\n\n\n\n

<\/span>Start With Structured Data Capture at the Point of Work<\/span><\/h3>\n\n\n\n

The first step is to make the trigger easy for operators to use in real time. On the electronics line, when feeder material drops below the reorder point, the operator should not have to leave the station, find a paper card, or call three people to get action started. A mobile form or station-level screen can capture the line, SKU, feeder location, quantity remaining, time, and urgency in less than 20 seconds.<\/p>\n\n\n\n

The same principle applies to 5S audits, defect capture, and standard work confirmation. If the form is too long, workers will delay entry until the end of the shift, which defeats the purpose. Good digital lean tools use only the fields needed to trigger the next action, while allowing optional photos, comments, and reason codes for better follow-up.<\/p>\n\n\n\n

<\/span>Route Each Lean Event to the Right Owner Automatically<\/span><\/h3>\n\n\n\n

Once the event is captured, the workflow should decide what happens next without manual sorting. In the running example, a low-material signal from Line 3 can route directly to the warehouse runner if it is a normal replenishment, but escalate to the production supervisor and planner if the part is already below safety stock. That logic is where lean manufacturing techniques become executable, because response rules are built into the process.<\/p>\n\n\n\n

This is also how different lean tools connect across functions. A failed 5S audit can create a task for area ownership, a repeated Andon stop can open a quality investigation, and a value stream mapping workshop can feed approved actions into engineering, maintenance, or logistics queues. Instead of separate spreadsheets and whiteboards, the plant gets one flow from signal to task.<\/p>\n\n\n\n

<\/span>Build a Closed-Loop Flow From Issue to Review<\/span><\/h3>\n\n\n\n

For digital execution to work, the workflow must stay closed-loop. On the same electronics line, the operator reports a component shortage, the warehouse receives the task, the supervisor is notified if the response time exceeds the target, and the line leader can see whether the request is still open before the machine stops. When the refill is completed, the handler records the actual response time and quantity delivered, creating a usable record for review.<\/p>\n\n\n\n

That same pattern should apply to defects, changeover delays, and standard work exceptions. Capture, assign, act, verify, and review are the backbone of effective lean tools in digital form. Without that loop, plants collect data but still fail to improve execution speed.<\/p>\n\n\n\n

\"Closed-loop<\/figure>\n\n\n\n

<\/span>Digitize 5S and Standard Work for Consistency Across Shifts<\/span><\/h3>\n\n\n\n

5S is often the easiest place to start because the workflow is straightforward and highly visible. A shift leader completes a mobile audit by area, attaches photos of abnormal conditions, and assigns correction tasks with due times to specific team members. Managers can then review score trends by line, recurring failure points, and overdue actions instead of waiting for weekly summaries.<\/p>\n\n\n\n

Standard work benefits from the same structure, especially in mixed-model production. Operators should receive the current SOP by product or station, confirm acknowledgment after revisions, and record exceptions when reality does not match the documented method. This creates revision control and helps supervisors distinguish between training gaps, process drift, and outdated work instructions.<\/p>\n\n\n\n

<\/span>Turn Kanban Signals Into Replenishment and Escalation Rules<\/span><\/h3>\n\n\n\n

A digital kanban system should do more than show stock status. It should trigger the next material movement based on quantity thresholds, route the task to the correct handler, and time the response against a service-level target. In high-mix environments, this reduces the common failure mode where cards are visible but no one owns the replenishment timing.<\/p>\n\n\n\n

On the electronics line, each feeder location can have a digital replenishment rule tied to part number, supermarket location, and standard refill quantity. If the request is not fulfilled within, for example, 8 minutes, the workflow can notify the line supervisor; if the same part triggers repeated urgent calls in one shift, it can also flag planner review. That is where a kanban signal starts supporting root-cause action, not just material movement.<\/p>\n\n\n\n

<\/span>Use Value Stream Mapping to Manage Improvement Actions, Not Just Workshops<\/span><\/h3>\n\n\n\n

Value stream mapping often produces a strong current-state diagnosis but weak follow-through. The digital version should convert each approved improvement into a tracked action with an owner, target date, expected impact, and status. That keeps the map connected to execution after the workshop ends.<\/p>\n\n\n\n

In the running example, repeated replenishment delays may show that supermarket layout, pick route design, and planning frequency are all contributing to machine waiting time. Those actions can then be assigned to logistics, industrial engineering, and planning, with progress reviewed in one dashboard. This is a better fit for continuous improvement than static action logs because leaders can see which countermeasures are stalled and which are reducing lost minutes.<\/p>\n\n\n\n

<\/span>Make Andon Actionable With Escalation Paths and Response Metrics<\/span><\/h3>\n\n\n\n

Andon only works when every abnormality has a defined response path. A digital Andon workflow can classify the event by category, such as quality, material, machine, or manpower, and then notify the first responder based on line and shift. If the issue is not acknowledged or resolved within the target window, the workflow escalates automatically.<\/p>\n\n\n\n

This is especially important for short-cycle production where one unresolved stop quickly affects output attainment. On many lines, a delayed response of even 5 to 10 minutes<\/strong> can consume a meaningful share of the hourly target, particularly when OEE is already under pressure. With digital routing and timestamps, supervisors can review not just how many calls occurred, but who responded, how fast, and which issue types caused the most downtime.<\/p>\n\n\n\n

<\/span>Use Dashboards to Support Daily Management<\/span><\/h3>\n\n\n\n

The final layer is visibility. Digital workflows generate real-time data that can feed tier meetings, shift handovers, and morning reviews without additional manual reporting. For the electronics line, a supervisor should be able to see open material calls, overdue 5S actions, top Andon causes, standard work acknowledgment rates, and response-time trends in one place.<\/p>\n\n\n\n

This is where a configurable no-code platform such as Jodoo<\/a><\/strong> becomes useful in practice. Operations teams can build mobile forms, routing rules, escalation workflows, and dashboards around their actual line logic rather than forcing lean processes into rigid software categories. That matters because shop-floor execution usually varies by product family, shift pattern, support-team structure, and plant maturity.<\/p>\n\n\n\n

<\/span>How to Roll Out Digital Lean Tools Without Waiting for MES<\/span><\/h2>\n\n\n\n

<\/span>Start With the Lean Tools That Break Down Most Often in Daily Use<\/span><\/h3>\n\n\n\n

You do not need to digitize every lean tool at once. Start with the ones used most frequently, involve the most handoffs, create the heaviest audit burden, or require fast escalation when something goes wrong. In most plants, that usually means daily 5S checks, issue escalation, shift handovers, material replenishment tied to a kanban system, and action tracking from value stream mapping or Kaizen reviews.<\/p>\n\n\n\n

A simple prioritization rule works well: digitize the process where delays are expensive, and follow-up is inconsistent. If a paper checklist is completed once a month, it may not be your first target. If supervisors chase updates across three shifts every day, that process is a better candidate because the return shows up quickly in response time, closure rate, and accountability.<\/p>\n\n\n\n

<\/span>Use Four Selection Criteria to Rank Candidates<\/span><\/h3>\n\n\n\n

Start with frequency: the more often a routine happens, the more waste a poor process creates. A 5S audit done by 20 team leaders every shift creates far more data handling effort than a quarterly review, so even small improvements save time quickly. High-frequency lean manufacturing techniques are usually the easiest place to prove value fast.<\/p>\n\n\n\n

Cross-functional handoffs are the second filter. If an abnormality moves from production to maintenance to quality and then back to the line, spreadsheets and whiteboards often lose ownership between steps. Lean tools that depend on multiple departments, such as Andon follow-up or corrective actions from standard work deviations, benefit early from digital routing and status tracking.<\/p>\n\n\n\n

Audit burden is the third filter. If managers spend hours consolidating paper checklists, photographing boards, or rebuilding reports in Excel, the process is already telling you it needs a better execution layer. This is common with layered process audits, standard work confirmation, and recurring 5S lean manufacturing reviews.<\/p>\n\n\n\n

Escalation speed is the fourth filter. Any process where delay increases scrap, downtime, or missed shipments should move up the list. A replenishment signal in a kanban system or a line stop escalation often has a much stronger business case than a lower-risk administrative workflow.<\/p>\n\n\n\n

<\/span>Choose the Right Technology for the Problem<\/span><\/h3>\n\n\n\n

Spreadsheets are still useful when the workflow is simple, the team is small, and there are few dependencies across functions. They are cheap and familiar, but they become fragile once you need mobile data capture, approval control, timestamps, alerts, or reliable revision history. In practice, spreadsheets support analysis better than execution.<\/p>\n\n\n\n

Point tools can work well if you are solving one narrow problem, such as a standalone audit app or a single maintenance ticketing workflow. The trade-off is fragmentation: one tool for audits, another for action tracking, another for dashboards, and no shared data model between them. That makes it harder to connect lean tools into one continuous improvement system.<\/p>\n\n\n\n

A no-code platform fits best when you need speed, plant-level flexibility, and connected workflows without waiting for a full MES rollout. It is usually faster to configure than MES, far more workflow-capable than spreadsheets, and easier for operations teams to adapt as standard work, escalation rules, or reporting needs change. MES is the stronger choice when you need deep machine integration, production traceability, and transaction control at enterprise scale, while ERP should remain focused on planning, finance, procurement, and master data rather than daily shop-floor execution.<\/p>\n\n\n\n

\"Comparison<\/figure>\n\n\n\n

<\/span>Sequence the Rollout for Quick Wins, Not Perfect Architecture<\/span><\/h3>\n\n\n\n

A practical rollout sequence is to start with one visible, repeatable workflow that supervisors already care about. Good first pilots include 5S audit execution, abnormality escalation, or shift handover because they combine operator input, supervisor action, and management review. These processes also create data that can feed dashboards quickly, which helps sustain support after the pilot starts.<\/p>\n\n\n\n

The second step is to connect that first workflow to one adjacent process. For example, a digital 5S audit can feed corrective action tracking, or a material shortage signal can trigger a replenishment request and supervisor notification. This is where separate lean tools begin to function as one operating system instead of isolated activities.<\/p>\n\n\n\n

The third step is standardization. Once one line proves the process, lock the core fields, ownership rules, and escalation logic before copying it to other lines or shifts. That prevents each area from reinventing the workflow while still allowing local adjustments where they matter.<\/p>\n\n\n\n

<\/span>A Realistic 30-Day Pilot Plan<\/span><\/h3>\n\n\n\n

Days 1\u20135: Pick One Use Case and Define Success<\/h4>\n\n\n\n

Select one production line or cell, not the whole plant. Choose a workflow with clear pain in execution, such as standard work confirmation, a kanban replenishment trigger, or action tracking from daily management meetings. Define three to five metrics only, such as response time, closure rate, missed checks, or time spent consolidating reports.<\/p>\n\n\n\n

Days 6\u201310: Map the Current Process in Detail<\/h4>\n\n\n\n

Document who starts the process, what data must be captured, who acts next, and when escalation should happen. Keep the scope tight by excluding edge cases that happen rarely. If the team cannot explain the current process in one page, it is too early to digitize it.<\/p>\n\n\n\n

Days 11\u201320: Build, Test, and Run in Parallel<\/h4>\n\n\n\n

Configure the digital version and run it alongside the current method for one to two weeks. This is where a no-code approach is useful because operations teams can adjust fields, notifications, and approval steps without a long IT cycle. Expect small corrections around form design, user roles, and exception handling after the first few days of real use.<\/p>\n\n\n\n

Days 21\u201330: Review Results and Decide the Next Workflow<\/h4>\n\n\n\n

At the end of the pilot, compare actual results against the baseline. Plants often see gains first in reporting speed, action visibility, and compliance rather than in headline OEE improvement, and that is fine because execution discipline is the foundation. If the workflow reduces missed follow-ups and cuts administrative effort, move to the next connected use case instead of expanding too broadly at once.<\/p>\n\n\n\n

<\/span>What Good Rollout Discipline Looks Like<\/span><\/h3>\n\n\n\n

Keep ownership with operations, not only IT. Lean tools fail digitally for the same reason they fail on paper: unclear process ownership, weak follow-up, and too many local workarounds. The technology matters, but the rollout succeeds when one line leader, one support function owner, and one plant sponsor review the workflow every week and remove friction quickly.<\/p>\n\n\n\n

Avoid the common mistake of treating digitization as a software project first and a management system second. The best results come when you digitize a proven routine, measure whether execution improves, and then expand in sequence. That approach lets you strengthen continuous improvement tools now, instead of waiting 12 to 18 months for a full MES program to reach the shop floor.<\/p>\n\n\n\n

<\/span>Conclusion: Building a More Executable Lean System With Jodoo<\/span><\/h2>\n\n\n\n

Lean manufacturing tools<\/strong><\/a> create results only when they move beyond posters, paper checklists, and spreadsheet follow-up into daily execution. In practice, that means operators can report issues immediately, supervisors can assign actions without delay, quality teams can verify closure, and managers can see trends before small losses become recurring waste. The real value of lean is not just defining the method, but making it repeatable across shifts, lines, and plants.<\/p>\n\n\n\n

\u3053\u3053\u306f Jodoo<\/strong><\/a> fits well for manufacturers that want digital lean execution without waiting for a full MES rollout or heavy custom development. As a no-code lean manufacturing platform, Jodoo<\/strong> can be configured to support 5S audits, Andon escalation workflows, shift handover forms, standard work acknowledgment, and continuous improvement dashboards in one connected system. That makes it easier to standardize routines, automate follow-up, and keep accountability visible at every level. <\/p>\n\n\n\n

If you want to make your lean tools more actionable on the shop floor, you can \u7121\u6599\u30c8\u30e9\u30a4\u30a2\u30eb\u3092\u958b\u59cb\u3059\u308b<\/a><\/strong> \u307e\u305f\u306f \u30c7\u30e2\u3092\u4e88\u7d04\u3059\u308b<\/a><\/strong> Jodoo\u3092\u4f7f\u3063\u3066\u3002.<\/p>\n\n\n\n

<\/p>","protected":false},"excerpt":{"rendered":"

\u6d41\u308c\u3068\u8aac\u660e\u8cac\u4efb\u3092\u5411\u4e0a\u3055\u305b\u308b\u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb\u3092\u3054\u7d39\u4ecb\u3057\u307e\u3059\u3002Jodoo\u304c\u30ea\u30fc\u30f3\u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u3092\u3069\u306e\u3088\u3046\u306b\u30c7\u30b8\u30bf\u30eb\u5316\u3059\u308b\u304b\u3092\u3054\u89a7\u304f\u3060\u3055\u3044\u3002\u7121\u6599\u30c8\u30e9\u30a4\u30a2\u30eb\u3092\u958b\u59cb\u3057\u307e\u3057\u3087\u3046\u3002.<\/p>","protected":false},"author":1,"featured_media":7531,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":["post-7436","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-solutions"],"blocksy_meta":[],"yoast_head":"\nLean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution - Jodoo Blog<\/title>\n<meta name=\"description\" content=\"Discover lean manufacturing tools that improve flow and accountability. See how Jodoo digitizes lean workflows. Start your free trial.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.jodoo.com\/blog\/ja-jp\/\u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb\/\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution - Jodoo Blog\" \/>\n<meta property=\"og:description\" content=\"Discover lean manufacturing tools that improve flow and accountability. See how Jodoo digitizes lean workflows. Start your free trial.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.jodoo.com\/blog\/ja-jp\/\u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb\/\" \/>\n<meta property=\"og:site_name\" content=\"Jodoo Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/company.jodoo\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-09T02:50:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-06-15T03:24:35+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.jodoo.com\/blog\/wp-content\/uploads\/2026\/06\/\u6570\u5b57\u5316\u8f6c\u578b.png\" \/>\n\t<meta property=\"og:image:width\" content=\"768\" \/>\n\t<meta property=\"og:image:height\" content=\"464\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Jodoo\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@JodooHQ\" \/>\n<meta name=\"twitter:site\" content=\"@JodooHQ\" \/>\n<meta name=\"twitter:label1\" content=\"\u57f7\u7b46\u8005\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jodoo\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data2\" content=\"23\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools\"},\"author\":{\"name\":\"Jodoo\",\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/#\\\/schema\\\/person\\\/b958cef486b1eb00d0f82e6f0a294481\"},\"headline\":\"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution\",\"datePublished\":\"2026-06-09T02:50:00+00:00\",\"dateModified\":\"2026-06-15T03:24:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools\"},\"wordCount\":4997,\"image\":{\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/\u6570\u5b57\u5316\u8f6c\u578b.png\",\"articleSection\":[\"Solutions\"],\"inLanguage\":\"ja\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools\",\"url\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools\",\"name\":\"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution - Jodoo Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/\u6570\u5b57\u5316\u8f6c\u578b.png\",\"datePublished\":\"2026-06-09T02:50:00+00:00\",\"dateModified\":\"2026-06-15T03:24:35+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/#\\\/schema\\\/person\\\/b958cef486b1eb00d0f82e6f0a294481\"},\"description\":\"Discover lean manufacturing tools that improve flow and accountability. See how Jodoo digitizes lean workflows. Start your free trial.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools#primaryimage\",\"url\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/\u6570\u5b57\u5316\u8f6c\u578b.png\",\"contentUrl\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/\u6570\u5b57\u5316\u8f6c\u578b.png\",\"width\":768,\"height\":464},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/lean-manufacturing-tools#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"\u9996\u9875\",\"item\":\"https:\\\/\\\/www.jodoo.com\\\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/\",\"name\":\"Jodoo Blog\",\"description\":\"Get the latest information about no-code development, updates, events, and other news about Jodoo.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/#\\\/schema\\\/person\\\/b958cef486b1eb00d0f82e6f0a294481\",\"name\":\"Jodoo\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/250e0d43b77e764b8fd961bf41dc0e46963912235f6724430a4fdb771e857168?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/250e0d43b77e764b8fd961bf41dc0e46963912235f6724430a4fdb771e857168?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/250e0d43b77e764b8fd961bf41dc0e46963912235f6724430a4fdb771e857168?s=96&d=mm&r=g\",\"caption\":\"Jodoo\"},\"sameAs\":[\"http:\\\/\\\/wp.sre.jodoodevelop.com\"],\"url\":\"https:\\\/\\\/www.jodoo.com\\\/blog\\\/ja-jp\\\/author\\\/wp-admin\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution - Jodoo Blog","description":"\u6d41\u308c\u3068\u8aac\u660e\u8cac\u4efb\u3092\u5411\u4e0a\u3055\u305b\u308b\u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb\u3092\u3054\u7d39\u4ecb\u3057\u307e\u3059\u3002Jodoo\u304c\u30ea\u30fc\u30f3\u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u3092\u3069\u306e\u3088\u3046\u306b\u30c7\u30b8\u30bf\u30eb\u5316\u3059\u308b\u304b\u3092\u3054\u89a7\u304f\u3060\u3055\u3044\u3002\u7121\u6599\u30c8\u30e9\u30a4\u30a2\u30eb\u3092\u958b\u59cb\u3057\u307e\u3057\u3087\u3046\u3002.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.jodoo.com\/blog\/ja-jp\/\u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb\/","og_locale":"ja_JP","og_type":"article","og_title":"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution - Jodoo Blog","og_description":"Discover lean manufacturing tools that improve flow and accountability. See how Jodoo digitizes lean workflows. Start your free trial.","og_url":"https:\/\/www.jodoo.com\/blog\/ja-jp\/\u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb\/","og_site_name":"Jodoo Blog","article_publisher":"https:\/\/www.facebook.com\/company.jodoo","article_published_time":"2026-06-09T02:50:00+00:00","article_modified_time":"2026-06-15T03:24:35+00:00","og_image":[{"width":768,"height":464,"url":"https:\/\/www.jodoo.com\/blog\/wp-content\/uploads\/2026\/06\/\u6570\u5b57\u5316\u8f6c\u578b.png","type":"image\/png"}],"author":"Jodoo","twitter_card":"summary_large_image","twitter_creator":"@JodooHQ","twitter_site":"@JodooHQ","twitter_misc":{"\u57f7\u7b46\u8005":"Jodoo","\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"23\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools#article","isPartOf":{"@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools"},"author":{"name":"Jodoo","@id":"https:\/\/www.jodoo.com\/blog\/#\/schema\/person\/b958cef486b1eb00d0f82e6f0a294481"},"headline":"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution","datePublished":"2026-06-09T02:50:00+00:00","dateModified":"2026-06-15T03:24:35+00:00","mainEntityOfPage":{"@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools"},"wordCount":4997,"image":{"@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools#primaryimage"},"thumbnailUrl":"https:\/\/www.jodoo.com\/blog\/wp-content\/uploads\/2026\/06\/\u6570\u5b57\u5316\u8f6c\u578b.png","articleSection":["Solutions"],"inLanguage":"ja"},{"@type":"WebPage","@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools","url":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools","name":"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution - Jodoo Blog","isPartOf":{"@id":"https:\/\/www.jodoo.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools#primaryimage"},"image":{"@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools#primaryimage"},"thumbnailUrl":"https:\/\/www.jodoo.com\/blog\/wp-content\/uploads\/2026\/06\/\u6570\u5b57\u5316\u8f6c\u578b.png","datePublished":"2026-06-09T02:50:00+00:00","dateModified":"2026-06-15T03:24:35+00:00","author":{"@id":"https:\/\/www.jodoo.com\/blog\/#\/schema\/person\/b958cef486b1eb00d0f82e6f0a294481"},"description":"\u6d41\u308c\u3068\u8aac\u660e\u8cac\u4efb\u3092\u5411\u4e0a\u3055\u305b\u308b\u30ea\u30fc\u30f3\u751f\u7523\u65b9\u5f0f\u30c4\u30fc\u30eb\u3092\u3054\u7d39\u4ecb\u3057\u307e\u3059\u3002Jodoo\u304c\u30ea\u30fc\u30f3\u30ef\u30fc\u30af\u30d5\u30ed\u30fc\u3092\u3069\u306e\u3088\u3046\u306b\u30c7\u30b8\u30bf\u30eb\u5316\u3059\u308b\u304b\u3092\u3054\u89a7\u304f\u3060\u3055\u3044\u3002\u7121\u6599\u30c8\u30e9\u30a4\u30a2\u30eb\u3092\u958b\u59cb\u3057\u307e\u3057\u3087\u3046\u3002.","breadcrumb":{"@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools"]}]},{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools#primaryimage","url":"https:\/\/www.jodoo.com\/blog\/wp-content\/uploads\/2026\/06\/\u6570\u5b57\u5316\u8f6c\u578b.png","contentUrl":"https:\/\/www.jodoo.com\/blog\/wp-content\/uploads\/2026\/06\/\u6570\u5b57\u5316\u8f6c\u578b.png","width":768,"height":464},{"@type":"BreadcrumbList","@id":"https:\/\/www.jodoo.com\/blog\/lean-manufacturing-tools#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"\u9996\u9875","item":"https:\/\/www.jodoo.com\/blog"},{"@type":"ListItem","position":2,"name":"Lean Manufacturing Tools: A Practical Guide for Digital Shop-Floor Execution"}]},{"@type":"WebSite","@id":"https:\/\/www.jodoo.com\/blog\/#website","url":"https:\/\/www.jodoo.com\/blog\/","name":"Jodoo\u30d6\u30ed\u30b0","description":"Jodoo\u306b\u95a2\u3059\u308b\u6700\u65b0\u60c5\u5831\u3001\u30a2\u30c3\u30d7\u30c7\u30fc\u30c8\u3001\u30a4\u30d9\u30f3\u30c8\u3001\u305d\u306e\u4ed6\u306e\u30cb\u30e5\u30fc\u30b9\u3092\u5165\u624b\u3057\u307e\u3057\u3087\u3046\u3002.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.jodoo.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Person","@id":"https:\/\/www.jodoo.com\/blog\/#\/schema\/person\/b958cef486b1eb00d0f82e6f0a294481","name":"Jodoo","image":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/secure.gravatar.com\/avatar\/250e0d43b77e764b8fd961bf41dc0e46963912235f6724430a4fdb771e857168?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/250e0d43b77e764b8fd961bf41dc0e46963912235f6724430a4fdb771e857168?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/250e0d43b77e764b8fd961bf41dc0e46963912235f6724430a4fdb771e857168?s=96&d=mm&r=g","caption":"Jodoo"},"sameAs":["http:\/\/wp.sre.jodoodevelop.com"],"url":"https:\/\/www.jodoo.com\/blog\/ja-jp\/author\/wp-admin"}]}},"_links":{"self":[{"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/posts\/7436","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/comments?post=7436"}],"version-history":[{"count":5,"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/posts\/7436\/revisions"}],"predecessor-version":[{"id":7575,"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/posts\/7436\/revisions\/7575"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/media\/7531"}],"wp:attachment":[{"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/media?parent=7436"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/categories?post=7436"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jodoo.com\/blog\/ja-jp\/wp-json\/wp\/v2\/tags?post=7436"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}