Purpose:
-
Approach Definition:
-
Identify ways to reach goals.
-
-
Business Improvement:
-
Enhance processes.
-
-
Requirement Allocation:
-
Meet needs.
-
-
Future State Pathways:
-
Illustrate paths.
-
Description:
-
Tactical options meet requirements.
-
Trade-offs may be needed.
-
Analysts assess impact.
-
Options evolve.

Inputs
-
Change Strategy: Guides decisions.
-
Requirements: Validated, prioritized.
-
Requirements Architecture: Full set, relationships.
Elements
-
Solution Approaches
-
Create: Direct response.
-
Purchase: Third-party solutions.
-
Combination: Blend of creation and purchase.
-
-
Improvement Opportunities
-
Efficiencies: Streamline processes.
-
Access to Information: Enhance data access.
-
Additional Capabilities: Highlight future value.
-
-
Requirements Allocation
-
Maximize benefits, minimize costs.
-
-
Design Options
-
Align with goals.
-
Includes policies, processes, people, decisions, applications, structures.
-

Guidelines & Tools
-
Existing Solutions: Third-party components.
-
Future State Description: Desired enterprise state.
-
Requirements (traced): Matches needs.
-
Solution Scope: Sets boundaries.
Techniques
-
Benchmarking & Market Analysis: Studies existing solutions and trends.
-
Brainstorming: Generates ideas.
-
Document Analysis: Provides design details.
-
Interviews: Gathers insights.
-
Lessons Learned: Extracts insights.
-
Mind Mapping: Generates options.
-
Root Cause Analysis: Identifies problem causes.
-
Survey/Questionnaire: Collects feedback.
-
Vendor Assessment: Evaluates third-party solutions.
-
Workshops: Collaborative idea sessions.

Stakeholders
-
Domain Expert: Business input.
-
Implementation Expert: Design insights.
-
Operational Support: Integration assistance.
-
Project Manager: Process oversight.
-
Supplier: Functional details.
Outputs
-
Design Options: Various approaches, improvements, components.
