Definition
FMDS (Floor Management Development System) is Toyota’s structured approach to visual management and supervisory development at the shop floor level. It provides group leaders with a standardized methodology for tracking key performance indicators, making problems visible, managing change points, and connecting the daily activities of their groups to broader plant and company objectives through hoshin kanri (policy deployment). The Japanese term is 日常管理板 (nichijō kanri ban, “daily management board”).
FMDS operates at the intersection of daily management and people development. On one hand, it is a management system: a set of visual boards, processes, and routines that structure how a group leader monitors performance, identifies abnormalities, and drives improvement. On the other hand, it is a development system: a deliberate progression that builds the group leader’s capability from basic problem recognition to self-reliant problem solving connected to plant-level targets. The “D” in FMDS is as important as the “M.”
FMDS is closely integrated with the 3 Pillar Activity (3本柱活動), which provides the substantive shop floor management content that FMDS makes visible and measurable. The FMDS board explicitly includes a 3 Pillar section, and the two systems are designed to be mutually reinforcing. However, FMDS also stands on its own as a visual management and KPI cascading system that connects every group’s daily work to the company hoshin.
Japanese Origin
日常 (nichijō) means “daily, everyday.” 管理 (kanri) means “management, control.” 板 (ban) means “board, panel.” Together: “daily management board” — a board used for the daily practice of management.
The English acronym FMDS (Floor Management Development System) is used internationally, but within Toyota the concept is part of the broader 日常管理 (nichijō kanri, “daily management”) system.
The FMDS Board
The centerpiece of FMDS is a physical management board maintained by the group leader at the shop floor level. The board is organized as a matrix. The columns represent the plant’s hoshin categories, and the rows represent layers of management information that cascade from strategic objectives down to specific shop floor activities.
Columns: Hoshin Categories
The standard columns align with Toyota’s management categories. Typical columns include Safety, Quality, Production/Maintenance (生産・保全), Cost (原価), and Personnel/Human Development (人事). Some plants use Environment (環境) as a column; others use Productivity or HRD (Human Resource Development).
The specific column labels may vary by plant, but they always reflect the hoshin categories that the plant has established for that fiscal period. This directly links the group leader’s board to the company’s strategic direction.
Rows: Layered KPI Structure
The rows create a logical cascade from high-level targets down to specific activities and their results:
Theme/Objective (課目標). States the overarching management themes for the section.
Main KPI (メインKPI). Directly linked to the plant hoshin. Visualizes monthly and historical performance trends with clear targets specified. This row answers the question: what does the plant need from this group?
Analysis (分析). A space between Main KPI and Sub KPI for the group leader to analyze the gap between target and actual.
Sub KPI (サブKPI). A breakdown of the Main KPI to the countermeasure level. Clear targets are specified, and spikes (abnormalities) are annotated. This row takes the high-level target and makes it specific enough for the group leader to act on. The annotations on spikes are important: they force the group leader to notice and record when something deviates from normal.
Activity. Shows the specific issues identified and the improvement activities being undertaken. Displays process impact and provides evidence of PDCA. This is where the group leader documents what they are actually doing about the problems surfaced by the KPIs above.
Activity KPI. Shows results from each activity with a logical connection back to the Sub KPI. This row answers two questions: “Did we do it?” and “What was the result?” It closes the loop by demonstrating whether the activities undertaken actually moved the needle on the Sub KPI.
3 Pillar (3本柱). Tracks the status of each 3 Pillar activity (Standardized Work, Ownership Maintenance, Cutting Point Management) and the “kodawari” (こだわり, points of particular focus or insistence) within each. This row connects the group’s 3 Pillar certification activities to the broader performance management structure. The kodawari notation — particularly under Quality — indicates where the group leader has identified specific commitment points tied to 3 Pillar activities.
The exact structure varies by plant and context, but the principle is consistent: a logical, visual cascade from strategic objectives to daily activities and back to results.
Six Design Principles
The FMDS board follows six design principles:
1. Display prominently where everyone passes. The board is posted in a high-traffic location — not tucked in a team leader’s office or a corner of the production area. Everyone who walks through the area sees it. This includes members from other departments, which helps improvements spread across the organization.
2. One board shows everything from policy to results at a glance. The single-board constraint is intentional. Policy, goals, targets, current status, improvement activity, and results are all visible together. Each person can see how their own work connects to company goals — not in theory, but on the board in front of them.
3. Organize by hoshin category in columns. The management categories (Safety, Quality, Production, Cost, Human Development) are aligned to company policy. Each category has its own column with targets, status, and improvement activity.
4. Assign responsible persons and display. For each improvement theme and action item, the board shows who is responsible, what they are doing, and by when. The “who, by when, what” is explicit and visible to everyone.
5. Visualization builds problem-finding and problem-solving capability. By making the current situation visible through graphs and data, every team member can see where problems exist. This develops the ability to find problems — not just solve them when assigned.
6. Deliberately insist on handwriting. The person responsible writes the data by hand. This is not a holdover from pre-digital times — it is an intentional design choice. Writing by hand creates personal ownership and forces the writer to engage with the numbers, rather than passively printing a report.
Manager-Level FMDS: The KPI Corral
FMDS is not limited to the group leader level. At the section manager level, an FMDS structure called the “KPI Corral” aggregates information from multiple group leader boards and links it directly to the company hoshin. The KPI Corral “sets direction for the section” by translating company-level objectives into the specific targets and priorities that cascade down to each group’s FMDS board.
This creates a continuous line of sight from the company hoshin through the section manager to each group leader and, ultimately, to each team member’s daily work.
Additional Management Elements
Change Point Management
A structured communication process for managing 4M changes (Man, Method, Material, Machine). When a change occurs, the group leader documents what happened, what the risk is, who is responsible for managing it, and when the change condition will end. This is displayed on a “Change Point Wing” attached to or near the FMDS board.
The purpose is to ensure that no change goes unmanaged, since change points are where defects, safety incidents, and process instability most commonly originate.
Focus Activity
A PDCA-cycle improvement activity directed at solving specific problems raised by the FMDS board. When the board’s KPI tracking reveals a gap or recurring abnormality, the group leader initiates a focused improvement effort to address the root cause. This is displayed on a “Focus Activity Wing” and provides the mechanism for converting the problems made visible by the board into actual countermeasures and results.
FMDS Dojo
A dedicated training environment where supervisory staff develop their FMDS capability. Participation typically includes managers, assistant managers, group leaders, and team leaders. The dojo provides a controlled setting where leaders can practice board management, KPI analysis, problem identification, and PDCA thinking before applying these skills on the live shop floor.
Group Leader Development: See → Show → Solve
FMDS embodies a deliberate, staged approach to developing group leader capability. The framework follows a general progression that is typically implemented over a multi-year period:
Stage 1: “See the Problem”
The group leader learns the basics of floor management: understanding process knowledge, developing fundamental skills, and learning to use FMDS for group KPI management. The focus is on the group leader’s ability to recognize that a problem exists, which requires understanding what “normal” looks like and noticing when conditions deviate.
This is primarily about developing the group leader’s eyes — their ability to read the shop floor and the data on the board.
Stage 2: “Show the Problem”
The group leader progresses to actively utilizing and teaching FMDS tools. This stage introduces Change Point Management and Focus Activities, and includes training through the FMDS Dojo and TBP (Toyota Business Practice) / KPI Tree analysis.
The emphasis shifts from merely recognizing problems to making them visible to others through the board, structured communication, and teaching team members to see what the group leader sees.
Stage 3: “Solve the Problem”
The group leader achieves self-reliance, becoming capable of problem solving to impact plant-level targets. This stage includes TPS Dojo training and the ability to connect shop floor kaizen directly to hoshin objectives.
At this stage, the group leader is not just managing daily operations but actively driving improvement that contributes measurably to company strategy. The board becomes a true management tool rather than merely a display.
This progression — see, show, solve — reflects Toyota’s broader philosophy that capability must be built in sequence. A group leader who cannot see a problem cannot show it to others, and one who cannot show it cannot mobilize the resources to solve it.
Relationship to the 3 Pillar Activity
FMDS and the 3 Pillar Activity are designed as complementary systems. The 3 Pillar Activity provides the substance of shop floor management: the specific practices, evaluation criteria, and certification levels for managing people (Standardized Work), equipment (Ownership Maintenance), and product quality (Cutting Point Management). FMDS provides the structure for making that substance visible, measurable, and connected to organizational goals.
In practical terms, the FMDS board’s 3 Pillar row tracks each group’s progress in their pillar activities and displays how those activities connect to operational KPIs. When a group’s Ownership Maintenance activities reduce machine breakdowns, that result should be visible in the Sub KPI and Activity KPI rows for productivity. When Standardized Work improvements reduce safety incidents, the Safety column should reflect it. FMDS prevents 3 Pillar activities from becoming disconnected improvement exercises — it forces them to demonstrate their contribution to measurable outcomes.
The Obeya meeting process further reinforces this connection. At the developing and mature stages of implementation, section managers conduct regular Obeya meetings where they review the FMDS boards and 3 Pillar activity scores across their groups, confirm achievement and positive impact on plant KPIs, and provide coaching where gaps exist. Some plants also conduct “Asaichi” (early morning) cross-functional problem-solving sessions that use FMDS data as their starting point.
The People Development Purpose
The board’s deeper purpose is developing capable people (実力のある人材を育てていくしくみ). The tracking of safety, quality, production, cost, and human development data is the mechanism through which leaders develop their capability to manage.
A group leader who maintains the board daily — updating data by hand, identifying deviations, assigning responsibilities, following up on improvement activities — is practicing the fundamentals of management: observation, analysis, prioritization, delegation, and follow-through. The board structures this practice so that it happens consistently, not sporadically.
Rather than assuming group leaders arrive with management capability, FMDS treats that capability as something that must be systematically built through a defined progression. This reflects Toyota’s experience that many group leaders, particularly in overseas plants or plants with rapid turnover, have limited tenure and cannot rely on accumulated tacit knowledge alone. FMDS provides the structure within which management knowledge is developed regardless of individual background.
Common Mistakes
Treating it as a results tracking board. If the board only shows what happened yesterday — production counts, defect rates, incident numbers — it is a scoreboard, not an FMDS board. The FMDS board must show the cascade from hoshin policy through KPI layers to improvement activity. Results without the policy context and improvement activity are incomplete.
Digitizing the board. The physical board at the point of production serves a specific function: it creates a gathering point for daily management discussions and makes the information available to everyone who passes by. A digital dashboard in an office serves a different function. The deliberate insistence on handwriting — forcing the responsible person to physically engage with the data — is lost when the board moves to a screen.
Making it a display for visitors. An FMDS board that is cleaned up and formatted for plant tours but not used for daily management is theater. The board should reflect the real, current state of the area — including problems that haven’t been solved yet.
Disconnecting it from hoshin. If the hoshin columns are empty or generic, the board loses its integrating function. The power of the FMDS board is in connecting the top-level hoshin direction to the specific daily work of the shop floor. Without that connection, it reverts to a standalone tracking board.
Skipping the development progression. Deploying FMDS boards without the accompanying group leader development — the See → Show → Solve progression — produces boards that are maintained as administrative tasks rather than used as management tools. The board is only as effective as the group leader’s capability to use it.