Chapter "API Governance" from API Management - Part II (Category Management)

Continuing the story from pastWe will discuss how you can take the divide and conquer approach and organize the governance process through a mix of centralized and decentralized approaches. To do this, it is worth dividing the decision-making process into separate stages, which are similar to a pieplan development:) These steps are as follows: 1. Inception (beginning). Every decision is made because someone thinks that decision has to be made. This means that someone has determined that a problem or opportunity exists with more than one possible solution. 2. Choice generation (optionalization). If you’re making a decision in an area where you have a lot of experience, generating options can be pretty straightforward. But if there are many unknowns, you will need to spend more time identifying the possibilities. 3. Selection (choice). This is the heart of decision-making that most people focus on, but the importance of the choice element depends largely on the volume of options available. 4. Authorization (authorization). The fact that a choice has been made does not mean that a decision has been made. The choice must be authorized before it can be implemented. Authorization is the work of deciding on the validity of a chosen choice. Was the right choice made? Will it work? Is he safe? Does it make sense in the context of other decisions? 5. Implementation (implementation). The decision-making process does not end when the choice is authorized. Implementation is an important part of API management work. If the implementation of decisions is too slow or poor quality, then all your decisions are in vain. 6. Challenge (contest). Decisions are not immutable, and every decision you make for your API management system should be open to challenge. Often we do not think that the decisions we make may require revision, change or even cancellation in the future. Defining the challenge element allows us to plan for continuous change at the decision-making level.

And the beauty is that you can centralize or decentralize every step of this approach to decision-making. Inception - centralized, choice generation - centralized, the rest decentralized. The point is that the available languages are centrally defined, and the teams decide which languages to write in decentralized ways.

The authors note that good governance systems should include the following features: Distribution of solutions based on impact, scope, and scale (That was in the first post.) Enforcement of System Organizations and Validation of Implementation (centralized solutions) Incentivization for decision-making (for decentralized solutions) Adaptability of impact measurement and continuous improvement

Continuation in last post from this seriesWhere we will talk about governance processes.

#Architecture #Software #Governance #Management #Leadership #Processes #Leadership