The strategy archetype is a design factor that describes how an enterprise uses information and technology to achieve its goals and objectives. There are six strategy archetypes defined in COBIT 2019: customer intimacy, product leadership, operational excellence, compliance-driven, data-driven, and innovation-driven.
Each archetype has different implications for the governance and management of information and technology in terms of focus areas, processes, practices, roles, structures, and metrics. The best approach when determining which strategy archetype most closely aligns with an enterprise's own strategy is to select the one that reflects the enterprise's information and technology risk profile, which is another design factor that describes how an enterprise identifies, assesses, responds to, monitors, and reports on information and technology risks. The risk profile helps to determine the level of risk appetite and tolerance that an enterprise has for its information and technology activities, as well as the level of control and assurance that is required for its governance framework. By selecting the strategy archetype that matches the risk profile, an enterprise can ensure that its governance framework is appropriate for its context and objectives5 References: 5: COBIT
2019 Design Guide, page 35-39 : COBIT 2019 Design Guide, page 41-43

Explanation
The COBIT 2019 publication that includes a workflow for planning a tailored governance system for the enterprise is COBIT 2019 Design Guide: Designing an Information and Technology Governance Solution.
This publication provides guidance on how to design a customized governance system for information and technology using COBIT as a reference framework. It includes a workflow for planning a tailored governance system for the enterprise that consists of seven steps: define design factors; define focus areas; define current state; define target state; identify gaps; define roadmap; select implementation method.14 References: COBIT
2019 Framework: Introduction and Methodology, COBIT 2019 Design Guide: Designing an Information and Technology Governance Solution

The change enablement tasks are the tasks that involve preparing for managing and sustaining the changes that are required for implementing a governance system for an enterprise using COBIT 2019. The change enablement tasks help to ensure that the changes are aligned with the enterprise's strategy objectives needs expectations etc., that they deliver value and benefits to the enterprise and its stakeholders that they overcome resistance and barriers to change that they create a culture of continuous improvement etc. One of the key change enablement tasks that must be completed during the driver identification phase of an IT initiative is identify the business and governance drivers. The driver identification phase is the first phase of the governance implementation roadmap which involves identifying and analyzing the internal and external factors that trigger or influence the need for designing and implementing a governance system for an enterprise using COBIT 2019. The business drivers are the factors that relate to the enterprise's business strategy objectives performance risks issues opportunities etc., such as market conditions customer demands competitive pressures regulatory requirements etc. The governance drivers are the factors that relate to the enterprise's information and technology governance strategy objectives performance risks issues opportunities etc., such as IT alignment IT value delivery IT risk management IT resource management IT performance measurement etc. By identifying the business and governance drivers during the driver identification phase an enterprise can establish a clear understanding of why it needs to design and implement a governance system using COBIT 2019 what are the expected outcomes benefits value etc., from doing so who are the relevant stakeholders their roles responsibilities requirements expectations etc., how to communicate engage involve them in the change process etc.

These components (of a governance system) can be either generic or "variants of generic." Generic components are described in the COBIT Core Model and apply in principle to any situation (although they "generally need customization before being practically implemented.") Whereas variants are based on the generic components but tailored for a specific purpose or context within a focus area.