Which practice advocates creating modular OmniScripts for common processes so they can be reused later?

Which practice advocates creating modular OmniScripts for common processes so they can be reused later?

• A. Logical Structure and Sequence
• B. Prefill as much data as possible
• C. Design for Reuse
• D. Remember to Guide

Answer: (C)

Design for reuse means building OmniScripts as modular, interchangeable blocks that can be leveraged across multiple processes. By creating reusable components or sub-OmiScripts for common steps (like collecting contact information, address data, or consent) and parameterizing them for different contexts, you cut duplication, ensure consistency, and speed up both development and maintenance—a single update to a reusable piece benefits every flow that uses it. While other practices improve different aspects of a flow—structure for readability, prefilled data for efficiency, and guiding the user for clarity—they don’t inherently promote the cross-process reuse that modular design enables.

Design for reuse means building OmniScripts as modular, interchangeable blocks that can be leveraged across multiple processes. By creating reusable components or sub-OmiScripts for common steps (like collecting contact information, address data, or consent) and parameterizing them for different contexts, you cut duplication, ensure consistency, and speed up both development and maintenance—a single update to a reusable piece benefits every flow that uses it. While other practices improve different aspects of a flow—structure for readability, prefilled data for efficiency, and guiding the user for clarity—they don’t inherently promote the cross-process reuse that modular design enables.