Management by Walking Around (MBWA): Definition and How to Do It

By Tara Minh · Updated Oct 10, 2026

Management by walking around (MBWA) is a leadership practice where managers regularly leave their offices to talk with employees, watch the work, and hear problems firsthand. The visits are informal and mostly unscheduled. The goal isn't inspection. It's staying close enough to the work to know what's really happening.

It sounds almost too simple to need a guide. But most leaders who say they "walk the floor" do it badly: a quick lap, a few nods, and back to the desk. This article covers where MBWA came from, how it differs from similar practices, a step-by-step method, a copy-ready template, and the research that shows when it backfires.

Where MBWA came from

The practice is tied to Hewlett-Packard. The HP Archives describe Bill Hewlett and Dave Packard practicing an innovative management style built on the belief that nothing replaces personal involvement and one-on-one communication. The Computer History Museum notes that the founders were known for management by walking around on the manufacturing floor, and that Hewlett named the practice "MBWA," which he called "management by wandering around."

The phrase reached a much bigger audience through Tom Peters and Robert Waterman. In a piece on his own site, Peters says they learned MBWA from a much smaller, more intimate Hewlett-Packard when they began researching in 1979, and that he and Waterman were preparing for a 1982 television appearance about In Search of Excellence when they argued over who would get to say the term on air. Peters calls staying in touch the manager's number one priority.

You'll see both "walking" and "wandering" used. They mean the same thing. "Wandering" stresses that the route isn't scripted, and that's the heart of the idea.

Key Facts

Key Facts

• HP's founders practiced MBWA on the shop floor, and the HP Archives tie it to the belief that nothing replaces personal involvement and one-on-one communication.
• Peters and Waterman say they learned the concept at Hewlett-Packard while researching In Search of Excellence, published in 1982.
• The Lean Enterprise Institute defines the related gemba walk as a practice for grasping the current situation through direct observation and inquiry before taking action.
• A randomized field study of an 18-month MBWA-based patient safety program covered 20 program hospitals and 48 control hospitals. Nurses' perception of performance fell in the program hospitals.
• The study's authors say visits help only when they lead to active problem solving, and can backfire when management fails to meet the expectations they raise.

MBWA versus similar practices

MBWA gets confused with several neighbors. They overlap, but each answers a different question.

The line between MBWA and micromanagement is intent. If you're there to listen and learn, it's MBWA. If you're there to check and correct, employees will read it as surveillance. Its cousin on the other side, macromanagement, keeps leaders at arm's length from the work, and MBWA is one way to correct for that.

MBWA and the gemba walk

The closest relative is the gemba walk from lean management. The Lean Enterprise Institute's lexicon defines it as a practice for grasping the current situation through direct observation and inquiry before taking action. It pairs the walk with the idea of "go and see," and recommends following a single product family or customer-facing process from start to finish. You'll find the full method in our guide to the gemba walk.

Here's a rule of thumb. MBWA is about people and relationships, so it's loose and frequent. A gemba walk is about a process, so it has a focus, a route, and a follow-up. Many good managers do both: a quick unscripted lap each day, plus a scheduled process walk once a month.

Why leaders do it

Three benefits come up again and again in management writing.

You get information before it gets filtered. By the time a problem reaches a dashboard or a status report, it's been summarized and softened. A conversation by someone's desk skips those layers.

You show people you care about their work. Attention is a signal. When a leader asks a specific question about a task, it tells the person the task matters. This connects to what psychological safety research says about speaking up: people share problems when they believe the response will be curiosity, not blame.

You learn what's really happening. Process documents describe how work should go. The floor shows how it does go. The gap between the two is where most improvement ideas live.

There's a related caution. Visible attention can change behavior simply because people know they're watched, a pattern explained in the Hawthorne effect. If you walk the floor once a quarter, people will perform for you. Regular, low-key presence is what lets that wear off.

What the research says

The evidence is more mixed than the enthusiasm suggests. The best-known test is a randomized field study by Anita Tucker and Sara Singer, published in Production and Operations Management in 2014. It followed 20 hospitals that completed an 18-month MBWA-based patient safety program, with 56 work areas, against 48 randomly selected control hospitals with 138 work areas. Contrary to what the researchers expected, the program had a negative effect on nurses' perceptions of performance.

The authors' explanation is the useful part. Per the same report, senior managers spent too much time deciding which problems to solve and too little acting on them, and presence on the front line helped only when it enabled active problem solving. Tucker was quoted as saying MBWA can backfire if management fails to meet the staff expectations the program raises.

So the lesson isn't "don't walk around." It's that walking around creates a promise. When someone tells you about a broken tool or a confusing handoff, they expect something to happen. A visit with no follow-through is worse than no visit.

Note too that this was a structured program in hospitals, not a lone manager's daily habit. It doesn't prove how MBWA works everywhere. It does show that the follow-through matters more than the walking.

How to do MBWA step by step

Step 1: Decide why you're walking

Pick a purpose for each week, even if the conversations stay unscripted. It could be "learn what slows onboarding" or "hear how the new tool is landing." A purpose keeps you from drifting into small talk, and it makes the follow-up clearer.

Step 2: Block time, then keep the route loose

Put 30 to 60 minutes on your calendar several times a week. Don't announce a route. Vary the time and the order so you meet different people on different days. The scheduling is about protecting the habit. The wandering stays free.

Step 3: Start with listening

Open with a question about the work, not the person's performance: "What's the most annoying part of your day?" or "What would you change if you could?" Ask, then stop talking. If you fill the silence, you'll hear your own opinions back.

Step 4: Ask about specifics

General questions get general answers. Ask about this week's order, that customer's complaint, the report due on Friday. Specific questions show you're paying attention and surface real detail.

Step 5: Hold back on fixing and judging

You'll see things you want to correct. Resist, unless safety is at stake. If you jump in every time, people learn to hide problems when you appear. Note the issue and decide later whether it's a coaching topic or a system problem.

Step 6: Write it down right after

Spend five minutes logging what you heard, who said it, and what you promised. Memory fades fast, and promises are the thing you can't afford to lose.

Step 7: Close the loop

Within a few days, tell the person what happened to their input, even if the answer is "we can't fix that now, and here's why." This is the step the hospital study suggests matters most. Visible follow-up is what turns a walk into trust.

Template: walk plan and observation log

Copy these two tables into a doc or notebook. The first plans the week. The second records each visit.

Weekly walk plan

Observation log

Review the log once a week. Group entries by theme. When three people mention the same obstacle, it's no longer an anecdote, it's a system problem worth a real fix.

Examples by business function

These are hypothetical scenarios, written to show how the practice looks in different settings.

Sales. A sales director sits in the bullpen for an hour twice a week and listens to a few calls from a distance, then asks reps what prospects keep objecting to. She learns that a pricing page is confusing buyers. She sends the objection list to marketing the same day and tells the reps it's done.

Customer support. A support head spends part of each morning near the queue. He notices agents switching between four tabs to answer one common question. Instead of coaching them, he asks the team to help him write one shared answer template.

Manufacturing and operations. A plant manager walks the line at shift change, when handoffs happen. She asks what got left undone from the previous shift. The answers give her a list of handoff gaps, and she picks the most common one to fix first. For a structured version of this, see the gemba walk.

Engineering and product. An engineering manager stops by the team's working session without an agenda. A developer mentions that the staging environment is down half the time. That never made it into a status update, because nobody thought it was worth raising.

Healthcare and field services. A clinic manager checks in with front-desk staff and nurses mid-shift, asking what slowed patients down that morning. Given the hospital research above, she's careful to commit only to fixes she can deliver.

MBWA for remote and hybrid teams

You can't wander through a Slack workspace the way you wander through a warehouse, but the intent translates. The aim is unscheduled, low-stakes contact that gives people a chance to raise things they wouldn't put on an agenda.

Some ways to do a virtual version:

• Drop-in office hours. Keep an open video room for 30 minutes at fixed times, with no agenda. Anyone can pop in.
• Short, unscripted check-ins. Message someone: "Have 10 minutes? I'd like to hear how the launch looks from your side." Make it clear it isn't a status request.
• Read the work, not the reports. Browse project boards, shared docs, and support threads, then comment with a real question or a thank-you. This is the closest equivalent to glancing at someone's desk.
• Join channels as a listener. Sit in team channels and read before you post. Respond to the substance, and don't turn every thread into a task.
• Visit in person when you can. If your team meets occasionally, use that time to walk the space and talk with people, not just run meetings.

Remote MBWA has one extra risk. Because everything is visible and logged, it can easily feel like monitoring. Be open about what you look at and why, and keep commenting to questions and recognition, not corrections. The advice in radical candor on caring personally while challenging directly applies here.

Do's and don'ts

Common mistakes

Treating it as a performance. If people see you coming with a smile and a checklist, they'll give you the polished version. Short, frequent, plain visits beat dramatic ones.

Skipping the quiet people. Managers gravitate toward people who talk easily. Use your observation log to see who you haven't spoken to in weeks.

Fixing in the moment. On-the-spot corrections teach people that a visit means trouble. Gather information first, decide later.

Confusing walking with managing. A walk collects information. It doesn't replace clear goals, proper feedback, or decisions. As organizations grow, you'll need other mechanisms alongside it, as covered in managing at scale.

Start this week

Choose one team and two fifteen-minute slots in your calendar. Ask one question each time: "What's getting in your way?" Write down the answer, do one thing about it, and tell the person. That single loop is the whole practice. Everything else is repetition.