{"id":814,"date":"2012-04-19T04:50:35","date_gmt":"2012-04-19T08:50:35","guid":{"rendered":"http:\/\/facilitativeleadership.wordpress.com\/?p=814"},"modified":"2026-05-01T15:56:02","modified_gmt":"2026-05-01T19:56:02","slug":"requirements-gathering","status":"publish","type":"post","link":"https:\/\/mgrush.com\/blog\/requirements-gathering\/","title":{"rendered":"How to Facilitate Requirements Gathering and Prevent Omissions"},"content":{"rendered":"<h2>When products or projects are accused of poor requirements gathering, the accusation is normally false. The requirements gathered are usually solid, but risk increases with additional costs because some of the requirements are missing.<\/h2>\n<p><span style=\"font-size: 14pt;\">To\u00a0facilitate\u00a0any type of descriptive or prescriptive build-out of a process or series of activities, and to prevent omissions, use a structured approach to understanding the complete Use Story. Groups have a tendency to forget activities or events that occur less frequently, particularly activities that support planning and control. Therefore, this approach to requirements gathering provides structured support that squeezes out potential omissions. Structure solidifies requirements gathering when relying on a proven method<span style=\"color: #000000;\">&#8212;<\/span>life-cycle analysis.<\/span><\/p>\n<blockquote>\n<div><span style=\"font-size: 14pt;\"><i>NOTE: Requirements can be gathered to understand an internal process or they can be gathered externally to help build new products and services.<\/i><\/span><\/div>\n<\/blockquote>\n<h3><strong>Method<\/strong><\/h3>\n<div id=\"attachment_857\" style=\"width: 296px\" class=\"wp-caption alignright\"><img wpfc-lazyload-disable=\"true\" loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-857\" class=\"wp-image-857\" title=\"Structured Requirements Gathering\" src=\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/requirements-286x300.png\" alt=\"Structured Requirements Gathering or How to Facilitate Requirements Gathering (Primer)\" width=\"286\" height=\"300\" srcset=\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/requirements-286x300.png 286w, https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/requirements.png 667w\" sizes=\"(max-width: 286px) 100vw, 286px\" \/><p id=\"caption-attachment-857\" class=\"wp-caption-text\"><strong>Structured Requirements Gathering<\/strong><\/p><\/div>\n<p><span style=\"font-size: 14pt;\">Therefore, the developmental support steps for requirements gathering include:<\/span><\/p>\n<ul>\n<li><span style=\"font-size: 14pt;\">Determine the business purpose of the process or functional area. Strongly suggest using the \u201c<em>Purpose is to . . .<\/em> \u201c tool.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Next is the first activity of the brainstorming method\u2014List. Label the top of the flip chart with \u201cVERB NOUN\u201d and ask the group to identify all the activities that do or would support the business purpose created in the prior step. Enforce the listing and capture them only as Verb-Noun pairings.<\/span><\/li>\n<\/ul>\n<h4><span style=\"font-size: 14pt;\">Plan\u27a0Acquire\u27a0Operate\u27a0Control<\/span><\/h4>\n<ul>\n<li><span style=\"font-size: 14pt;\">Use the Plan\u27a0Acquire\u27a0Operate\u27a0Control life-cycle to help stimulate thinking about what activities may be missing.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">You should find one to two planning, one to two acquiring, bunches of operating, and at least one to two controlling activities for each business process or scope of work.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">After identifying the various activities (sometimes called \u201csub-processes\u201d by others), convert the verb-noun pairings into \u201cuse cases\u201d or some form of input-process-output. Build one use case for each pairing.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Consider assigning the SIPOC tables (a form of use case) to sub-teams. Demonstrate one in its entirety with the whole group and then break them out into two or three groups.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">For each activity, build a narrative statement that captures the purpose of the activity, why it is being performed, then:<\/span><\/li>\n<\/ul>\n<ol>\n<li><span style=\"font-size: 14pt;\">Continue to identify the specific outputs\u00a0or what changes as a result of having completed the activity.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Link the outputs with the customer or client of each; i.e., who is using each output.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Next, identify the inputs required to perform the activity.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Finally, identify the sources of the inputs.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-size: 14pt;\">An illustrative SIPOC chart is shown below. SIPOC stands for the <strong>S<\/strong>ource of the input, <strong>I<\/strong>nput(s) required to complete the activity, <strong>P<\/strong>rocess (i.e., our activity), <strong>O<\/strong>utput resulting from the activity, and <strong>C<\/strong>ustomer or client of the output.<\/span><\/p>\n<div id=\"attachment_855\" style=\"width: 776px\" class=\"wp-caption aligncenter\"><img wpfc-lazyload-disable=\"true\" loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-855\" class=\"wp-image-855 size-full\" title=\"sipoc\" src=\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/sipoc.png\" alt=\"How to Facilitate Requirements Gathering (Primer)\" width=\"766\" height=\"274\" srcset=\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/sipoc.png 766w, https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/sipoc-300x107.png 300w\" sizes=\"(max-width: 766px) 100vw, 766px\" \/><p id=\"caption-attachment-855\" class=\"wp-caption-text\">Mountain Climbing Illustration of a SIPOC Chart<\/p><\/div>\n<h4><span style=\"font-size: 14pt;\"><em>Summary of steps to be included in this sequence\u00a0<\/em><\/span><\/h4>\n<ol>\n<li><span style=\"font-size: 14pt;\">Identify the activity (i.e., process). Agree on its purpose and how the activity performed supports the purpose.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Detail HOW it is or should be performed.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">List the outputs from the completed activity.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Link the outputs to the respective clients or customers.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">List the inputs needed to complete the activity.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Identify the source(s) for each of the inputs.<\/span><\/li>\n<\/ol>\n<h3><strong>Success Keys<\/strong><\/h3>\n<p><span style=\"font-size: 14pt;\">Consequently, use a visual illustration or template to build clear definitions of \u201crequirements\u201d. Additionally,<\/span><\/p>\n<ul>\n<li><span style=\"font-size: 14pt;\">Have the group pre-build all the potential sources and customers of the process and code them so that when you build the SIPOC tables; the group can refer to the code letter\/ number instead of the full name (thus substantially speeding up the method). As you discover new sources or customers, simply add them.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Then, keep quiet (i.e., \u2018shut up\u2019) after asking questions (seek to understand rather than be understood).<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Write down participant responses immediately and fully.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Provide visual feedback, preferably through modeling.<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Advance from activity identification to the inputs and outputs required to support the activity; then associate each with its sources and clients (SIPOC).<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Separate the WHAT from the HOW.<\/span><\/li>\n<\/ul>\n<h3><strong>Simple Agenda<\/strong><\/h3>\n<p><span style=\"font-size: 14pt;\">You may consider using the method described above with a simple agenda that could look like:<\/span><\/p>\n<ul>\n<li><span style=\"font-size: 14pt;\">Introduction<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Purpose of __________<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Activities (NOTE: Take each \u201cThing\u201d and ask\u2014\u201cWhat do you do with this thing ?\u201d\u2014forcing \u201cVerb-Noun\u201d pairings. Test for omissions using the Plan \u27ba Acquire \u27ba Operate \u27ba Control prompting)<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Value-Add (i.e., SIPOC)<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Walkthrough<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Wrap<\/span><\/li>\n<\/ul>\n<h2 style=\"font-weight: 400;\"><span style=\"font-size: 18pt;\"><strong>Activity Flows (<em>aka<\/em> Functional Decomposition)<\/strong><\/span><\/h2>\n<p style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\">This approach supports building an <em>Activity Flow<\/em> diagram also known as a process flow diagram. This workshop delivers up the \u201cverbs\u201d or activities that should be adding value (if not, consider eliminating them).<\/span><\/p>\n<p style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\"><em>Activity Flows<\/em> can benchmark or help optimize during business process improvement efforts. Use this approach whenever you need a detailed understanding of WHAT is required to support a process. Leverage the deliverable from this workshop to build \u201cUse Cases\u201d or SIPOCs or process-flow diagrams (swim lanes), helping to ensure that nothing substantial or critical gets missed.<\/span><\/p>\n<p style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\">This approach applies structures around complex situations that may look overwhelming. As background material, it can help a team keep focus on the life-cycle of a product or project.<\/span><\/p>\n<h3 style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\"><strong>Deliverable<\/strong><\/span><\/h3>\n<p style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\">An <em>Activity Flow<\/em> diagram (traditionally known as <em>Functional Decomposition<\/em>) with detailed charts of the activities being performed. Consider using ProChart, Visio, or some graphical tool to help build your process flow diagram.<\/span><\/p>\n<h3 style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\"><strong>Participants<\/strong><\/span><\/h3>\n<p style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\">People performing the work. Should include management and supervisory people within a business area. Use breakout teams to expedite the SIPOC charts when finalizing the detailed requirements.<\/span><\/p>\n<h3 style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\"><strong>Visual Aids Used<\/strong><\/span><\/h3>\n<ol>\n<li><span style=\"font-size: 14pt;\">Definitions for terms<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Work life cycle prompt (Plan, Acquire, Operate, Control)<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Illustration of your analogy down to the SIPOC (or use case)<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">If using an easel or whiteboard also consider:<\/span><\/li>\n<\/ol>\n<ul>\n<li><span style=\"font-size: 14pt;\">Large Post-it notes (for the gerunds or groups [<em>aka<\/em> processes])<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">Smaller Post-it notes (verb\/ noun pairings or activities)<\/span><\/li>\n<li><span style=\"font-size: 14pt;\">For online sessions, consider getting some documentation help. While we know you are stellar, it can get really tough plotting and listening at the same time.<\/span><\/li>\n<\/ul>\n<blockquote>\n<p style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\"><em>Comments: <\/em><em>HOT TIP on WHAT vs HOW\u2014<\/em><em>If you are uncertain whether an activity is \u201c<\/em><em>WHAT<\/em><em>\u201d they do or \u201c<\/em><em>HOW<\/em><em>\u201d they do it, ask whether it is concrete or abstract. For example, you might \u201cconserve energy\u201d that is abstract and scribes \u201c<\/em><em>WHAT<\/em><em>\u201d you are doing. <\/em><em>HOW<\/em><em> you do it is to \u201cswitch off the lights\u201d or \u201cdial down the thermostat\u201d\u2014more concrete and visual. Or, <\/em><em>WHAT<\/em><em> you are doing with your vehicle is \u201cstarting\u201d but \u201cturn the key\u201d is <\/em><em>HOW<\/em><em> you are doing it. Or, you cannot see \u201cacceleration\u201d but you can visualize a \u201cfoot on the pedal\u201d.<\/em><\/span><\/p>\n<\/blockquote>\n<p style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\">The figure below illustrates part of the deliverable and documentation. Comprehensive process identification may take a few days unless you are beginning with a narrow scope and small group of activities.<\/span><\/p>\n<div id=\"attachment_13648\" style=\"width: 1229px\" class=\"wp-caption aligncenter\"><img wpfc-lazyload-disable=\"true\" loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-13648\" class=\"wp-image-13648 size-full\" src=\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png\" alt=\"Activity Flows for the Navigating Process Required in Mountaineering \" width=\"1219\" height=\"395\" srcset=\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png 1219w, https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2-980x318.png 980w, https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2-480x156.png 480w\" sizes=\"(min-width: 0px) and (max-width: 480px) 480px, (min-width: 481px) and (max-width: 980px) 980px, (min-width: 981px) 1219px, 100vw\" \/><p id=\"caption-attachment-13648\" class=\"wp-caption-text\"><span style=\"font-size: 14pt;\"><strong>Activity Flows for the Navigating Process Required in Mountaineering<\/strong><\/span><\/p><\/div>\n<p style=\"font-weight: 400;\"><span style=\"font-size: 14pt;\">When possible, work with a meeting designer or methodologist ahead of time to understand the questions and grammatical constructs of the model that match well with the tool being used to record the model.<\/span><\/p>\n<h4 style=\"text-align: center;\"><span style=\"color: #ff0000; font-size: 14pt;\"><strong>______<\/strong><\/span><\/h4>\n<p><span style=\"font-size: 14pt;\">Don\u2019t ruin your career by hosting <a href=\"https:\/\/mgrush.com\/blog\/bad-meetings\/\">bad meetings<\/a>. Sign up for a <a href=\"https:\/\/mgrush.com\/public-facilitation-training\/\" target=\"_blank\" rel=\"noopener\">workshop<\/a> or send this to someone who should. <em><a href=\"https:\/\/web.archive.org\/web\/20260106090117\/https:\/\/mgrush.com\/\">MGR<span style=\"font-size: 12pt;\">USH<\/span><\/a><\/em> workshops focus on meeting design and practice. Each person practices tools, methods, and activities every day during the week. Therefore, while some call this immersion, we call it the road to building high-value facilitation skills.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>When products or projects are accused of poor requirements gathering, the accusation is normally false. The requirements gathered are usually solid, but risk increases with additional costs because some of the requirements are missing. To\u00a0facilitate\u00a0any type of descriptive or prescriptive build-out of a process or series of activities, and to prevent omissions, use a structured [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":13648,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_wp_convertkit_post_meta":{"form":"-1","landing_page":"","tag":"0","restrict_content":"0"},"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[453185968,453185961],"tags":[453192181,453190731,11969182,453190729,453190730,208811033],"class_list":["post-814","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analysis-methods","category-decision-making","tag-activity-flows","tag-facilitate-requirements-gathering","tag-functional-decomposition","tag-how-to-facilitate-requirements-gathering","tag-requirements-gathering","tag-structured-facilitation"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.8 (Yoast SEO v27.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>How to Facilitate Requirements Gathering and Prevent Omissions<\/title>\n<meta name=\"description\" content=\"When projects are accused of poor requirements gathering, the accusation is normally false because the requirements gathered end up solid . . .\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/mgrush.com\/blog\/requirements-gathering\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Facilitate Requirements Gathering and Prevent Omissions\" \/>\n<meta property=\"og:description\" content=\"To facilitate either descriptive or prescriptive build-out of a process or series of activities, and to prevent omissions, use a structured User Story.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/mgrush.com\/blog\/requirements-gathering\/\" \/>\n<meta property=\"og:site_name\" content=\"MG RUSH Facilitation Best Practices Blog\" \/>\n<meta property=\"article:publisher\" content=\"http:\/\/www.facebook.com\/FacilitationTraining\/\" \/>\n<meta property=\"article:author\" content=\"http:\/\/www.facebook.com\/FacilitationTraining\/\" \/>\n<meta property=\"article:published_time\" content=\"2012-04-19T08:50:35+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-05-01T19:56:02+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1219\" \/>\n\t<meta property=\"og:image:height\" content=\"395\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Facilitation Expert\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:description\" content=\"To facilitate either descriptive or prescriptive build-out of a process or series of activities, and to prevent omissions, use a structured User Story.\" \/>\n<meta name=\"twitter:creator\" content=\"@TerrenceMetz\" \/>\n<meta name=\"twitter:site\" content=\"@terrencemetz\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Facilitation Expert\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/\"},\"author\":{\"name\":\"Facilitation Expert\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#\\\/schema\\\/person\\\/33b05e43036ff09de0ddfccfef9a4497\"},\"headline\":\"How to Facilitate Requirements Gathering and Prevent Omissions\",\"datePublished\":\"2012-04-19T08:50:35+00:00\",\"dateModified\":\"2026-05-01T19:56:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/\"},\"wordCount\":1212,\"commentCount\":6,\"publisher\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/wp-content\\\/uploads\\\/2012\\\/04\\\/Activity-Flows-2.png\",\"keywords\":[\"Activity Flows\",\"Facilitate Requirements Gathering\",\"Functional Decomposition\",\"How to Facilitate Requirements Gathering\",\"Requirements Gathering\",\"Structured Facilitation\"],\"articleSection\":[\"Analysis Methods\",\"Decision Making\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/\",\"url\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/\",\"name\":\"How to Facilitate Requirements Gathering and Prevent Omissions\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/wp-content\\\/uploads\\\/2012\\\/04\\\/Activity-Flows-2.png\",\"datePublished\":\"2012-04-19T08:50:35+00:00\",\"dateModified\":\"2026-05-01T19:56:02+00:00\",\"description\":\"When projects are accused of poor requirements gathering, the accusation is normally false because the requirements gathered end up solid . . .\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/#primaryimage\",\"url\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/wp-content\\\/uploads\\\/2012\\\/04\\\/Activity-Flows-2.png\",\"contentUrl\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/wp-content\\\/uploads\\\/2012\\\/04\\\/Activity-Flows-2.png\",\"width\":1219,\"height\":395,\"caption\":\"Activity Flows for the Navigating Process Required in Mountaineering\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/requirements-gathering\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Facilitate Requirements Gathering and Prevent Omissions\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/\",\"name\":\"MG RUSH Facilitation Best Practices Blog\",\"description\":\"Compelling observations about structured, facilitative leadership\",\"publisher\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#organization\",\"name\":\"MG RUSH Facilitation Best Practices\",\"url\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/06\\\/SquareLogo800X800.png\",\"contentUrl\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/wp-content\\\/uploads\\\/2023\\\/06\\\/SquareLogo800X800.png\",\"width\":700,\"height\":700,\"caption\":\"MG RUSH Facilitation Best Practices\"},\"image\":{\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"http:\\\/\\\/www.facebook.com\\\/FacilitationTraining\\\/\",\"https:\\\/\\\/x.com\\\/terrencemetz\",\"http:\\\/\\\/www.linkedin.com\\\/in\\\/teammetz\",\"http:\\\/\\\/pinterest.com\\\/teammetz\",\"http:\\\/\\\/www.youtube.com\\\/mgrushfacilitation\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/#\\\/schema\\\/person\\\/33b05e43036ff09de0ddfccfef9a4497\",\"name\":\"Facilitation Expert\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6a3c33817cc970e9f1c2d60b6bd170c755f6a66e51205d2f0e41842b9814efa9?s=96&d=identicon&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6a3c33817cc970e9f1c2d60b6bd170c755f6a66e51205d2f0e41842b9814efa9?s=96&d=identicon&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6a3c33817cc970e9f1c2d60b6bd170c755f6a66e51205d2f0e41842b9814efa9?s=96&d=identicon&r=pg\",\"caption\":\"Facilitation Expert\"},\"description\":\"Terrence Metz, president of MG RUSH Facilitation Training, was just 22-years-old and working as a Sales Engineer at Honeywell when he recognized a widespread problem\u2014most meetings were ineffective and poorly led, wasting both time and company resources. However, he also observed meetings that worked. What set them apart? A well-prepared leader who structured the session to ensure participants contributed meaningfully and achieved clear outcomes. Throughout his career, Metz, who earned an MBA from Kellogg (Northwestern University) experienced and also trained in various facilitation techniques. In 2004, he purchased MG RUSH where he shifted his focus toward improving established meeting designs and building a curriculum that would teach others how to lead, facilitate, and structure meetings that drive results. His expertise in training world-class facilitators led to the 2020 publication of Meetings That Get Results: A Guide to Building Better Meetings, a comprehensive resource on effectively building consensus. Grounded in the principle that \u201cnobody is smarter than everybody,\u201d the book details the why, what, and how of building consensus when making decisions, planning, and solving problems. Along with a Participant\u2019s Guide and supplemental workshops, it supports learning from foundational awareness to professional certification. Metz\u2019s first book, Change or Die: A Business Process Improvement Manual, tackled the challenges of process optimization. His upcoming book, Catalyst: Facilitating Innovation, focuses on meetings and workshops that don\u2019t simply end when time runs out but conclude with actionable next steps and clear assignments\u2014ensuring progress beyond discussions and ideas.\",\"sameAs\":[\"http:\\\/\\\/MGrush.com\",\"http:\\\/\\\/www.facebook.com\\\/FacilitationTraining\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/terrencemetz\\\/\",\"@teammetz\",\"https:\\\/\\\/x.com\\\/TerrenceMetz\",\"https:\\\/\\\/www.youtube.com\\\/watch?v=j4x3-Qo9Ez4\"],\"birthDate\":\"1955-09-23\",\"gender\":\"male\",\"jobTitle\":\"Managing Director\",\"worksFor\":\"MG Rush Facilitation\",\"url\":\"https:\\\/\\\/mgrush.com\\\/blog\\\/author\\\/teammetz7\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"How to Facilitate Requirements Gathering and Prevent Omissions","description":"When projects are accused of poor requirements gathering, the accusation is normally false because the requirements gathered end up solid . . .","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/mgrush.com\/blog\/requirements-gathering\/","og_locale":"en_US","og_type":"article","og_title":"How to Facilitate Requirements Gathering and Prevent Omissions","og_description":"To facilitate either descriptive or prescriptive build-out of a process or series of activities, and to prevent omissions, use a structured User Story.","og_url":"https:\/\/mgrush.com\/blog\/requirements-gathering\/","og_site_name":"MG RUSH Facilitation Best Practices Blog","article_publisher":"http:\/\/www.facebook.com\/FacilitationTraining\/","article_author":"http:\/\/www.facebook.com\/FacilitationTraining\/","article_published_time":"2012-04-19T08:50:35+00:00","article_modified_time":"2026-05-01T19:56:02+00:00","og_image":[{"width":1219,"height":395,"url":"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png","type":"image\/png"}],"author":"Facilitation Expert","twitter_card":"summary_large_image","twitter_description":"To facilitate either descriptive or prescriptive build-out of a process or series of activities, and to prevent omissions, use a structured User Story.","twitter_creator":"@TerrenceMetz","twitter_site":"@terrencemetz","twitter_misc":{"Written by":"Facilitation Expert","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/#article","isPartOf":{"@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/"},"author":{"name":"Facilitation Expert","@id":"https:\/\/mgrush.com\/blog\/#\/schema\/person\/33b05e43036ff09de0ddfccfef9a4497"},"headline":"How to Facilitate Requirements Gathering and Prevent Omissions","datePublished":"2012-04-19T08:50:35+00:00","dateModified":"2026-05-01T19:56:02+00:00","mainEntityOfPage":{"@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/"},"wordCount":1212,"commentCount":6,"publisher":{"@id":"https:\/\/mgrush.com\/blog\/#organization"},"image":{"@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/#primaryimage"},"thumbnailUrl":"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png","keywords":["Activity Flows","Facilitate Requirements Gathering","Functional Decomposition","How to Facilitate Requirements Gathering","Requirements Gathering","Structured Facilitation"],"articleSection":["Analysis Methods","Decision Making"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/mgrush.com\/blog\/requirements-gathering\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/","url":"https:\/\/mgrush.com\/blog\/requirements-gathering\/","name":"How to Facilitate Requirements Gathering and Prevent Omissions","isPartOf":{"@id":"https:\/\/mgrush.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/#primaryimage"},"image":{"@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/#primaryimage"},"thumbnailUrl":"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png","datePublished":"2012-04-19T08:50:35+00:00","dateModified":"2026-05-01T19:56:02+00:00","description":"When projects are accused of poor requirements gathering, the accusation is normally false because the requirements gathered end up solid . . .","breadcrumb":{"@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/mgrush.com\/blog\/requirements-gathering\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/#primaryimage","url":"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png","contentUrl":"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png","width":1219,"height":395,"caption":"Activity Flows for the Navigating Process Required in Mountaineering"},{"@type":"BreadcrumbList","@id":"https:\/\/mgrush.com\/blog\/requirements-gathering\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/mgrush.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Facilitate Requirements Gathering and Prevent Omissions"}]},{"@type":"WebSite","@id":"https:\/\/mgrush.com\/blog\/#website","url":"https:\/\/mgrush.com\/blog\/","name":"MG RUSH Facilitation Best Practices Blog","description":"Compelling observations about structured, facilitative leadership","publisher":{"@id":"https:\/\/mgrush.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/mgrush.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/mgrush.com\/blog\/#organization","name":"MG RUSH Facilitation Best Practices","url":"https:\/\/mgrush.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/mgrush.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2023\/06\/SquareLogo800X800.png","contentUrl":"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2023\/06\/SquareLogo800X800.png","width":700,"height":700,"caption":"MG RUSH Facilitation Best Practices"},"image":{"@id":"https:\/\/mgrush.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["http:\/\/www.facebook.com\/FacilitationTraining\/","https:\/\/x.com\/terrencemetz","http:\/\/www.linkedin.com\/in\/teammetz","http:\/\/pinterest.com\/teammetz","http:\/\/www.youtube.com\/mgrushfacilitation"]},{"@type":"Person","@id":"https:\/\/mgrush.com\/blog\/#\/schema\/person\/33b05e43036ff09de0ddfccfef9a4497","name":"Facilitation Expert","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/6a3c33817cc970e9f1c2d60b6bd170c755f6a66e51205d2f0e41842b9814efa9?s=96&d=identicon&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/6a3c33817cc970e9f1c2d60b6bd170c755f6a66e51205d2f0e41842b9814efa9?s=96&d=identicon&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6a3c33817cc970e9f1c2d60b6bd170c755f6a66e51205d2f0e41842b9814efa9?s=96&d=identicon&r=pg","caption":"Facilitation Expert"},"description":"Terrence Metz, president of MG RUSH Facilitation Training, was just 22-years-old and working as a Sales Engineer at Honeywell when he recognized a widespread problem\u2014most meetings were ineffective and poorly led, wasting both time and company resources. However, he also observed meetings that worked. What set them apart? A well-prepared leader who structured the session to ensure participants contributed meaningfully and achieved clear outcomes. Throughout his career, Metz, who earned an MBA from Kellogg (Northwestern University) experienced and also trained in various facilitation techniques. In 2004, he purchased MG RUSH where he shifted his focus toward improving established meeting designs and building a curriculum that would teach others how to lead, facilitate, and structure meetings that drive results. His expertise in training world-class facilitators led to the 2020 publication of Meetings That Get Results: A Guide to Building Better Meetings, a comprehensive resource on effectively building consensus. Grounded in the principle that \u201cnobody is smarter than everybody,\u201d the book details the why, what, and how of building consensus when making decisions, planning, and solving problems. Along with a Participant\u2019s Guide and supplemental workshops, it supports learning from foundational awareness to professional certification. Metz\u2019s first book, Change or Die: A Business Process Improvement Manual, tackled the challenges of process optimization. His upcoming book, Catalyst: Facilitating Innovation, focuses on meetings and workshops that don\u2019t simply end when time runs out but conclude with actionable next steps and clear assignments\u2014ensuring progress beyond discussions and ideas.","sameAs":["http:\/\/MGrush.com","http:\/\/www.facebook.com\/FacilitationTraining\/","https:\/\/www.linkedin.com\/in\/terrencemetz\/","@teammetz","https:\/\/x.com\/TerrenceMetz","https:\/\/www.youtube.com\/watch?v=j4x3-Qo9Ez4"],"birthDate":"1955-09-23","gender":"male","jobTitle":"Managing Director","worksFor":"MG Rush Facilitation","url":"https:\/\/mgrush.com\/blog\/author\/teammetz7\/"}]}},"jetpack_featured_media_url":"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2012\/04\/Activity-Flows-2.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/posts\/814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/comments?post=814"}],"version-history":[{"count":0,"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/posts\/814\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/media\/13648"}],"wp:attachment":[{"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/media?parent=814"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/categories?post=814"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mgrush.com\/blog\/wp-json\/wp\/v2\/tags?post=814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}