Lean in furniture operations: how to stop running without moving

Lean in furniture operations: how to stop running without moving

Lean isn’t ‘clean floors’ or blind cost-cutting. It’s a system that reduces waiting, rework, and urgency. I diagnose it by measuring invisible queues—not by hanging posters.

3 min
Hernán Villalba Muzzin

Hernán Villalba Muzzin

Article author

Reading
    • lead time (order → delivery)
    • touch time (real work)
    • queue time (waiting).
    • you measure tidiness, not queues and wip.
    • you ask for habits, but don’t change rules.
    • improvement depends on a lean “hero.”
    • one area improves while the system worsens.
    • you talk tools (5s/kanban) without talking flow and constraints.
    • how many projects are open at once (total wip)?
    • how much does a project change after launch?
    • how often do you replan the same order?
    • what share of work arrives as “urgent”?
    • how big are the queues before key steps?
    • how much time is lost searching for material/info?
    • do installation kits ship complete with evidence—or by feel?
    • are defects recorded as a system or fixed silently?
    • is variability customer-driven or self-inflicted?
    • is the constraint stable or moving weekly?
    • are prioritization rules clear—or pressure-driven?
    • does the team trust the plan—or treat it as “approximate”?
    • impact on lead time and promises
    • repeatability (families of comparable work)
    • urgency pain (structural, not a one-off spike)
    • measurability (queues/wip/defects)
    • reputation risk (second visits, claims).
    • lead time
    • total wip
    • first pass yield
    • otif-style (on time, in full—especially kits)
    • replans per order.
    • local productivity
    • utilization (busy ≠ flowing)
    • pieces/day without context
    • plan adherence when the plan isn’t credible.
Imagen 1 — Lean in furniture operations: how to stop running without moving
Strategic Audit

Key control points: Lean in furniture operations

  • Is there a defined standard for this operation?
  • Do the same dependencies repeat weekly?
  • Does the team know the exact decision criteria?
  • Is there visibility into the real process bottleneck?

Share

Other articles you might like

TPM and OEE without makeup: your factory can be busy… and still losing moneyOPERACIONES

TPM and OEE without makeup: your factory can be busy… and still losing money

When output depends on ‘let’s hope the machine behaves today,’ you don’t have capacity—you have luck. How I diagnose whether the leak is maintenance, changeovers, micro-stops, or quality, and why badly measured OEE misleads you when you need control most.

Psychological safety on the shop floor and on site: the KPI nobody tracksOPERACIONES

Psychological safety on the shop floor and on site: the KPI nobody tracks

How to detect a fear culture (silence, hiding, repeated incidents) and why it hits quality, lead time, and margin harder than many tools.

Robotization and cobots in SMEs: automating without breaking flexibilityOPERACIONES

Robotization and cobots in SMEs: automating without breaking flexibility

Robots are no longer just for automotive giants. Discover how cobots (collaborative robots) can automate repetitive tasks in your furniture SME.

Advanced visualization: renders and VR that sell without creating operational debtOPERACIONES

Advanced visualization: renders and VR that sell without creating operational debt

Renders, VR and configurators are not ‘marketing’: they are a visual promise. I treat them as a decision system, not as polish. Signals, risks and criteria to detect whether visualization protects margin or destroys it.

Omnichannel and phygital experience: when the customer lives a project, not a channelOPERACIONES

Omnichannel and phygital experience: when the customer lives a project, not a channel

Real omnichannel in high-ticket projects: channel drift signals, operational risks, and how I diagnose whether your phygital experience builds trust… or triggers price comparisons.

The technical office as a margin guardian before you sellOPERACIONES

The technical office as a margin guardian before you sell

How to spot (and stop) projects that sell well but are born broken: technical decisions, promises, and variability that destroy margin before execution starts.

Warehouse design and physical flow: margin is lost by walkingOPERACIONES

Warehouse design and physical flow: margin is lost by walking

A warehouse doesn’t ‘get messy’: it’s quietly designed to create extra travel, extra touches, and extra urgency. I diagnose physical flow with simple signals—how many times you touch an item, how far it travels, and where the promise breaks.

Cybersecurity in the connected factory: when downtime starts with a clickOPERACIONES

Cybersecurity in the connected factory: when downtime starts with a click

A connected factory doesn’t fail only because of machines. It fails because of identities, permissions, and inconsistent truths. I don’t sell fear; I care about continuity, margin, and promises that don’t rely on heroics.