5S for Salesforce: Manufacturing Lessons for Implementations Your Users Will Actually Use

Long before I wrote my first formula field, I spent years on factory floors watching what separated efficient operations from chaotic ones. The pattern was always the same. The best plants weren't the ones with the most expensive equipment, they were the ones where the people running the machines could find what they needed, when they needed it, without thinking about it.

That's 5S. And after years of implementing Salesforce, I'm convinced it's one of the most underrated frameworks in our ability to develop systems people actually want to use.

What 5S Actually Is

5S originated at Toyota and spread through global manufacturing because it solved a stubborn problem: workers waste enormous amounts of time on the workspace itself rather than the work. The five steps, Sort, Set in Order, Shine, Standardise, Sustain, are deceptively simple. The discipline of applying them is where the value lives.

Most Salesforce implementations fail not because the technology is wrong but because the workspace we hand to end users is cluttered, inconsistent, and exhausting to navigate. We give a service rep a record page with 47 fields, three of which they actually use, and then wonder why adoption is poor and data quality is worse.

Let's walk through each S with the end user in mind.

Sort: Remove What Doesn't Earn Its Place

In a factory, Sort means walking through the workspace and tagging anything that isn't actively earning its keep. Old jigs, half-empty boxes, the spare part nobody can identify. If it isn't being used, it goes, or at least leaves the work cell.

In Salesforce, Sort is about ruthlessly removing fields, objects, automations, and reports that no longer serve the user. Every field on a page layout is cognitive tax. Every legacy custom object from a previous admin's experiment is a place for new admins to second-guess themselves. Every record-triggered flow that nobody can quite explain is a future incident waiting to happen.

When I start a refactor, I run usage queries. Which fields have data populated in the last 12 months? Which reports have been opened? Which Apex triggers haven't fired in production this quarter? The output is uncomfortable. Most orgs I see have 30+ percent of their custom fields functionally abandoned.

For the end user, Sort means they open a record and see what they actually need to do their job. Not a museum of past business processes. Not the field someone added in 2019 because the CFO at the time wanted a metric they never followed up on.

Set in Order: A Place for Everything

A well-organised workstation has tools positioned where the hand naturally falls. The torque wrench used most often is closest. Items used together are stored together. Visual cues mark where things belong, so a missing tool is instantly noticeable.

This is where Lightning page design becomes craft rather than configuration. Dynamic Forms lets us conditionally show fields based on what stage a record is in. Compact Layouts surface the right summary at the right time. Quick Actions sit precisely where the user needs them, not three clicks deep in a related list. Path components make stage progression visual and obvious.

When I design a page for a Key Account Manager, the question isn't "what fields exist on this object?", it's "what does this person do at this point in their day?" If they're qualifying a lead, the fields for qualification should be front and centre. The fields for closed-won analytics should not be on the same screen.

For the end user, Set in Order means the system feels like it was designed for their actual workflow. They reach for what they need and it's already there.

Shine: Clean Data Is a Daily Discipline, Not a Project

In a factory, Shine isn't just cleaning, it's inspection. You wipe down a machine and you find the leaking seal. You sweep the floor and you spot the loose bolt. The act of cleaning surfaces problems before they become failures.

In Salesforce, Shine is about data quality as a continuous practice. Validation rules that prevent dirty data at entry. Required fields where they genuinely matter. Duplicate management running consistently rather than as an annual heroic effort. Address normalisation, picklist hygiene, ownership reassignment when people leave roles.

I've spent enough time on deduplication projects to know the cost of skipping this. The tooling matters less than the discipline of using it regularly. A monthly dedupe routine outperforms an annual data cleanse every time, regardless of which product you've chosen.

For the end user, Shine means they trust the data. When they pull a report, they don't have to mentally compensate for the records they suspect are duplicates. When they search for a contact, they find one record, not three.

Standardise: The Same Job Done the Same Way

Standardisation is what turns individual best practice into organisational capability. In manufacturing, work instructions, visual standards, and standard operating procedures ensure that the second-shift operator builds the part exactly like the first-shift operator did.

In Salesforce, this is page layout consistency, naming conventions, documented automation patterns, approval processes that mirror real authority structures, and templates that encode good practice. It's the difference between an org where every admin has invented their own way of handling activity tracking and an org where activity tracking works the same way across every team.

I lean towards Type picklist fields over Record Types in many scenarios precisely because they make standardisation easier to maintain. Record Types proliferate. Permissions get tangled. Meanwhile a well-designed Type field with conditional layout logic gives you the same user experience differentiation with a fraction of the administrative overhead.

For the end user, Standardise means muscle memory works. The Save button is in the same place. The Stage picklist follows the same pattern across opportunity types. New hires learn one system, not seven micro-systems.

Sustain: The S Most Implementations Skip

This is the one that separates a successful implementation from a Salesforce graveyard. Sustain is the discipline of keeping the first four S's alive after the launch party. In manufacturing, this means daily 5S audits, visible dashboards, leadership engagement, and reinforcement loops.

In Salesforce, Sustain means using the Lightning Usage App to spot adoption drift. It means running quarterly reviews where you ask end users, not stakeholders, end users, what's frustrating them. It means having a backlog process that captures field requests but also field removal requests. It means change management that treats every release as an opportunity to either reinforce good practice or accumulate debt.

The hardest conversation I have with clients is the one about ongoing investment. Implementations get funded; sustainment rarely does. So Sustain often falls to the admin alone, who ends up firefighting rather than improving. I've started building monthly enhancement retainers into proposals specifically because Sustain needs a budget line, not a hope.

For the end user, Sustain means the system gets better over time, not worse. It means their feedback gets heard. It means the org that worked on day one still works on day 500.

The End User Is the Whole Point

Manufacturing taught me that systems are only as good as the experience of the person doing the work. A beautifully engineered process that frustrates the operator will be circumvented within a week. A simple process that respects the operator's time will outlast its designer.

Salesforce is the same. The architecture diagrams and the technical design documents are means to an end, and that end is the salesperson who needs to log a call between meetings, the fundraiser who needs to record a gift before they forget, the case worker who needs to find a beneficiary's history without learning a new query language.

5S is, fundamentally, a framework for respecting the end user. Sort respects their attention. Set in Order respects their time. Shine respects their trust in the data. Standardise respects their muscle memory. Sustain respects their right to a system that keeps working.

When I bring my manufacturing background into a Salesforce project, this is what I'm bringing. Not a metaphor. A method.

If you're staring at a Salesforce org that's accumulated several years of well-intentioned customisation, the first S is usually the right place to start.