What Does Gemba Look Like in Commercial?
If you've spent time around lean environments/organizations, you've probably heard someone say "go to gemba." If you work in sales, marketing, or service, you may never have heard the term at all. That's a missed opportunity, because it may be the lean idea that translates most directly to commercial work.
What gemba is, and where it comes from
For anyone not familiar with it, gemba (sometimes written genba) is Japanese for "the actual place." In lean terms, it means the place where the work happens and where value is created for the customer.
The idea comes from the Toyota Production System. Taiichi Ohno, one of the architects of that system, developed the practice of walking the floor to see the work firsthand and find waste, instead of managing from reports. Toyota calls the broader principle genchi genbutsu: go to the actual place and see the actual thing. A short version of the guidance is often attributed to Toyota executive Fujio Cho: go see, ask why, show respect.
The reason it matters is simple. A report tells you what happened. Going to the place where it happened shows you why. A problem that looks straightforward on a dashboard usually has causes nobody in a conference room can see, and the people doing the work often already know what they are.
Gemba was never meant to stay on the plant floor. Quality and product development practitioners have long used the word for the customer's place of business, where the product is put to work. For a commercial organization, that's the definition that matters most. Your gemba is anywhere your customer experiences you: their site and the line or lab where your product runs, but also the sales call, the quote, the service visit, the order confirmation, and the search a buyer typed into your website before talking to anyone.
A lot of that gemba is digital now. Calls are recorded, tickets are logged, and website visits are tracked, so going to see is easier than it has ever been, as long as someone actually looks.
Gemba, function by function
Every part of the commercial organization has its own gemba, and its own version of what a good visit should produce.
Marketing
Marketers write about customers they rarely get to meet. Their most valuable gemba is the sales conversation itself, along with the places buyers do their research before a rep is involved.
- Ride along with field sellers, with the goal of listening rather than presenting.
- Listen to recorded discovery calls and write down the exact words customers use to describe their problems. Those are the words that belong in your campaigns.
- Work the trade show booth to listen, not just to scan badges.
- Read lost-deal notes and RFQs. They show what buyers compare you against.
- Retrace a buyer's path through your website, including what they search for and where they leave.
What success looks like: campaign language you can trace back to things customers actually said, and sellers who recognize their own customers in the content marketing produces.
Sales
Sales is the function closest to the customer, which makes it easy to assume sellers are already at gemba. Often they're in the buyer's conference room, which is only part of the picture. Sellers' gemba starts earlier in the customer journey than the first meeting, and extends well past the signed order.
- What the buyer saw before the first call. Most buyers have read your website, downloaded a spec sheet or case study, compared you in search results or on a distributor's site, and maybe stopped by your trade show booth before they ever talk to a seller. Go through that material the way a buyer would. It tells you what the customer already believes about you, which questions are still open, and where marketing and sales are telling different stories.
- The line, lab, or plant where your product is used, and the operators and technicians who use it, not just the purchasing contact.
- Your own order process. Follow one order from quote to delivery and see what the customer experiences after the handshake.
- Your own calls. Reviewing a recording of yourself is uncomfortable, and it's one of the fastest ways to improve.
- A joint visit with a service technician, who often hears what a customer would never tell a salesperson.
What success looks like: sellers who walk into the first meeting knowing what the buyer has already read, who can describe how the customer uses the product day to day, and who see fewer surprises after the order is placed. Marketing benefits too, because sellers can tell them which content is helping and which is raising the wrong questions.
Product management
Product managers decide what gets built, often with the least direct exposure to how it gets used.
- Installations and commissioning, where gaps in setup and documentation show up first.
- Service calls, alongside the technicians who fix what broke.
- Time with real operators, watching them use the product in their own environment rather than in a demo.
- Returns, warranty claims, and support tickets, read as a set rather than one escalation at a time.
What success looks like: roadmap decisions that point to something the team saw firsthand, and fewer features that look good in a demo but don't hold up in the customer's environment.
Service
Service teams spend more time at customer sites than almost anyone else in the commercial organization. The bigger gap is usually getting what they see back to the rest of the business. The customer's site also isn't their only gemba; service touches several other points in the customer journey:
- The handoff from sales. Review how a new account moves from sales to installation and service. Compare what was promised in the deal with what the service team was told and what the customer expects.
- The customer's side of requesting service. Call your own service line or submit a request the way a customer would. Notice how long it takes to reach someone, how many times the problem has to be explained, and what the customer is told about timing.
- How the customer plans around you. Ask the customer's maintenance or operations lead how they schedule downtime, stock spare parts, and decide when to call you. Those decisions shape how they judge your service.
- Repeat visits. Go back to the accounts with the most repeat calls for the same issue and look at what the first visit missed.
Then build the path back to the rest of the organization:
- Short, structured debriefs after visits, with the same few questions every time.
- Root-cause tags on service reports, so patterns show up across visits instead of staying in one technician's memory.
- Technicians in the room for product reviews and key account planning.
What success looks like: more issues fixed on the first visit and fewer repeat calls; a product or sales change you can trace back to something a technician reported; and renewal conversations that start from the customer's actual experience rather than the contract terms.
Customer service and inside sales
For these teams, most of the work happens in the phone queue, the inbox, and order entry. That's one gemba, and the people working there see every friction point in the order process. But doing the work by phone doesn't mean they should never see the customer in person. A rep who has stood in a customer's plant handles that customer's next call differently.
- Listen to the queue. Leaders should spend regular time listening to calls and reading customer emails, and track the top reasons customers contact you. Every repeat reason points to a problem upstream.
- Walk an order from the customer's side. Request a quote, place a test order, or check an order's status the way a customer would, through the portal, by email, or by phone, and see how long each step actually takes.
- Learn how your customer buys. Ask a few customers' purchasing teams to walk you through how they place an order: the approvals, the systems, and the reasons a PO gets held. Reps who understand that process can remove friction before it slows down the next order.
- Sit with order entry to see where orders stall, get re-keyed, or come back for corrections.
- Ride along with a field seller or service technician. Visit a few of the accounts you talk to every week. Meet the buyer or planner on the other end of the phone, see where the product is used, and see where your orders land: the receiving dock, the storeroom, the line that's waiting on the part.
- Bring what you learn back to the field. Inside teams hear patterns across hundreds of accounts. A ride-along is a chance to tell the field seller or technician what you're hearing, and to hear what they see on site that never comes up on the phone.
What success looks like: a team that can name the top reasons customers contact them and is working to remove them, faster quote turnaround, fewer orders that need correcting, and reps who can picture the customer's operation when the phone rings.
Commercial leadership
Leaders set the tone for every function above. When a VP of Sales joins calls to listen instead of coach, visits a customer with no deal on the table, or spends an hour in the support queue, it tells the organization that going to see matters. It also gives leaders information no dashboard will show them.
- Go regularly, not only when a number turns red. A visit that only happens during a crisis feels like an inspection.
- Ask instead of tell. What's getting in your way? What did the customer say that surprised you? What would you change?
- Close the loop. When people raise a problem during a visit, they should hear what happened next.
- Put it on the calendar. Gemba belongs in a leader's standard work, with a set cadence, so it doesn't get crowded out by the next meeting.
Where AI fits, and where it doesn't
AI makes some kinds of gemba far easier to scale. Call transcripts and summaries mean a marketer can review twenty discovery calls in an afternoon, and a product manager can search a year of support tickets for one recurring complaint. That's a real expansion of what one person can see.
It's also not a substitute. A transcript tells you what was said. It won't show you an operator's face when the machine jams, the workaround taped to the side of the equipment, or the look a buyer gives a colleague when your price comes up. Use AI to cover more ground, and still go in person to see what the data can't capture.
Making gemba a habit
Gemba works when it's a routine with structure, not an occasional event. A few practices make it stick:
- Set a cadence by role. For example, one ride-along a month for each marketer, or one installation or service visit a quarter for each product manager. Start small enough that it actually happens.
- Use a simple observation template, so every visit captures the same things.
- Share what you saw. Make gemba observations a standing item in a weekly team meeting, so the learning reaches people who weren't there.
- Go to learn, not to audit. Ask why, and show respect for the people doing the work.
A simple gemba card: Where did I go? Who did I talk to or watch? What did I see that I didn't expect? What's one thing we should change? Who needs to hear about it?
Industrial companies built world-class operations by going to see. The commercial side of the business can use the same habit, and the customer is the one who benefits when the people who sell, market, design, and support the product have all recently stood where the customer stands.
Sources: Gemba and genchi genbutsu background: Wikipedia, "Gemba"; TWI Institute, "Gemba Walk".


