[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-239357-105":53,"doc-detail-239357-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","gemba-walk-go-see-think-and-do-field-guide","Gemba Walk - Go See Think and Do - Field Guide","","Gemba Walk is a practical field guide structured around GO & SEE, THINK, and DO to help teams observe real work, define problems, and drive improvement. It includes spaces for capturing affected metrics, documenting problem categories, and listing interim corrective actions and quick wins with owners, timing, and status. The THINK section applies 5W1H, builds problem and goal statements, performs cause analysis with 5 Whys, and summarizes root causes and expected benefits. The DO section supports solution planning, tracking target achievement and verification, and defining corrective actions, controls, SOPs, OPLs, audits, training, and follow-up.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/gemba-walk-go-see-think-and-do-field-guide/239357/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/gemba-walk-go-see-think-and-do-field-guide/239357.png","ImageObject",442,249,{"name":88,"@type":89},"Kyle","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-21","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of the GO & SEE section in a Gemba Walk?","Question",{"text":108,"@type":109},"It records the problem description and the metrics being affected, and helps visualize the process using a process map, flowchart, or spaghetti diagram. It also captures interim corrective actions and quick wins with owners, timing, and status.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the THINK section help identify root causes?",{"text":113,"@type":109},"It uses 5W1H to scope and focus the problem, then applies cause-and-effect brainstorming and drills down with the 5 Whys. Verified root causes are circled in the 5 Whys section, followed by a root cause statement and expected benefits.",{"name":115,"@type":106,"acceptedAnswer":116},"What actions are covered in the DO section after root causes are identified?",{"text":117,"@type":109},"It documents solution descriptions and evaluates countermeasures, then summarizes results and checks whether targets were achieved and results verified. It also defines corrective actions, required controls (SOPs/OPLs), audits, training, and steps to replicate the improvement with follow-up.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},239357,1789147570,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":73,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":9,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":125,"read_time":4},3985741905716,"https://ap-avatar.wpscdn.com/davatar_994ba38a5ba835b3df7d355c54d3ed8d","Gemba Walk (Go See Think and Do)  \nArea: Observer:  \nProcess: Date:  \nGO & SEE  \n\n| Problem description-And what metrics are being affected by the problem? |  |  |  | Process illustration-Using a process map, flowchart, spaghetti diagram, etc. |\n| --- | --- | --- | --- | --- |\n|  |  |  |  |  |\n| \u003Cbr>Problem category\u003Cbr>|  |  |  |  |\n| Interim corrective actions and quick wins |  |  |  |  |\n| What? | Who? | When? | Status |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n\nTHINK  \n\n| 5W1H-Scoping and focusing the problem |  |  |  |  |  | Cause and effect-Brainstorming and prioritizing possible causes |  |  |  |  |  |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |\n| What? | Where? | When? | Who? | Which? | How often? | |  |  |  |  | [ ] |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n| Problem statement |  |  | Goal statement |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  | 5 Whys-Drilling down to the root causes (Circle the verified root causes) |  |  |  |  |  |\n|  |  |  |  |  |  | Possible cause | Why? | Why? | Why? | Why? | Why? |\n| Expected benefits |  |  | Key metrics |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  | Cause analysis summary-Root cause statement |  |  |  | Addressing this cause(s) will solve\u003Cbr>\u003Cbr>the problem permanently? |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |\n\nDO  \n| Solution description- Including brainstorming and evaluating possible countermeasures |  |  |  | Result summary- Including results of key metrics |  |  |  |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n|  |  |  |  |  |  |  |  |\n| Start date | Estimated completion date |  |  | Target achieved? | Result verified? |  |  |\n|  |  |  |  |  |  |  |  |\n| Corrective actions-A workable plan to implement the countermeasures |  |  |  | Controls required & follow-up actions-SOPs, OPLs, audits, training, replicate improvement, etc. |  |  |  |\n| What? | Who? | When? | Status | What? | Who? | When? | Status |\n|  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |\n\nContinuous [Improvement Toolkit . www.citoolkit.com](Improvement Toolkit . www.citoolkit.com)","cbCaimgOmFK7rpnN","https://ap.wps.com/l/cbCaimgOmFK7rpnN","pdf",112501,"English","# GO & SEE\n## Problem description and process illustration\n## Problem category and interim corrective actions\n# THINK\n## 5W1H scoping and focusing the problem\n## Cause and effect brainstorming and 5 Whys\n## Cause analysis summary and expected benefits\n# DO\n## Solution description, results, and verification\n## Corrective actions and controls follow-up","[{\"question\":\"What is the purpose of the GO \\u0026 SEE section in a Gemba Walk?\",\"answer\":\"It records the problem description and the metrics being affected, and helps visualize the process using a process map, flowchart, or spaghetti diagram. It also captures interim corrective actions and quick wins with owners, timing, and status.\"},{\"question\":\"How does the THINK section help identify root causes?\",\"answer\":\"It uses 5W1H to scope and focus the problem, then applies cause-and-effect brainstorming and drills down with the 5 Whys. Verified root causes are circled in the 5 Whys section, followed by a root cause statement and expected benefits.\"},{\"question\":\"What actions are covered in the DO section after root causes are identified?\",\"answer\":\"It documents solution descriptions and evaluates countermeasures, then summarizes results and checks whether targets were achieved and results verified. It also defines corrective actions, required controls (SOPs/OPLs), audits, training, and steps to replicate the improvement with follow-up.\"}]","Gemba Walk - Go See Think and Do - Field Guide | PDF"]