PD030

Higher Design Reusability Across Business Units vs. Faster Localized Delivery

Business Context. Designing a process to be reusable across every business unit from the outset requires broader requirements gathering than a single business unit's localized delivery timeline can typically accommodate.

Process TRIZ Resolution. Rather than designing for universal reuse upfront, organizations should deliver a working solution for the first business unit quickly, then extract a reusable design pattern once a second business unit's requirements confirm which elements genuinely generalize.

Applicable TRIZ Principles

Principle 21 (Skipping) skips speculative generalization until a second use case confirms it is warranted.

Principle 15 (Dynamics) evolves the design toward broader reuse incrementally rather than all at once.

Principle 26 (Copying) uses the first business unit's implementation as a template rather than a rigid mandate.

Expected Outcome

Fast localized delivery

Evidence-based reusability

Reduced speculative design cost

Sustainable multi-unit adoption

Decision Indicators

Universal design efforts delay the first business unit's delivery significantly.

Reusable designs are built before any second use case exists.

Business units abandon a universal design because it fits no one well.

Design generalization is driven by assumption rather than evidence.

Delivery timelines slip due to premature scope expansion.

If several of these indicators are present, the contradiction is likely active and the Process TRIZ resolution above should be evaluated.