Quite frequently I am being asked about the value of architecture, sometimes out of actual curiosity and other times as a (welcome) challenge. I hence consider a good answer to this question a key skill for any senior architect and conduct the same exercise in my transformation workshops. I also consistently find out just how difficult it can be to answer this seemingly harmless question in a succinct and convincing manner to a non-technical audience.

What’s the value of postponing a decision?

A colleague once suggested that my KPI should be how many decisions I make. I had a gut feeling that this isn’t what I am after but was unable to intelligently articulate it at the time. However, my gut feel triggered a thought that the inverse, being able to postpone decisions, adds value. This thought led me to a new way of articulating the value I bring as chief architect: I sell options.

Options: Deferring Decisions

In the financial world, an option is well-known as the right, but not the obligation, to buy or sell a financial instrument at a future point in time (or over a future time span for American-style options). An option is therefore a way to defer a decision: instead of deciding to buy or sell a stock today, you have the right to make that decision in the future, at a known price.

Any person involved in the financial industry knows that options aren’t free: there’s a whole market for buying and selling options and other derivatives. If there was any doubt, it was cleared out by Fischer Black and Myron Scholes, who managed to compute the value of an option with their famous Black-Scholes Formula (see Wikipedia). One important parameter in establishing the value of the option is the strike price, i.e. the price at which the stock can be purchased in the future. The lower this strike price, the higher the value of the option.

IT Options

Translating the formula to IT architecture, selling options gives the business and IT a way to defer decisions. What size of server do you need to purchase for a system? If your application is architected to be horizontally scalable, this decision can be deferred: additional servers can be purchased later, at a known unit cost. What authentication mechanism should an application use? An architecture that properly separates concerns allows you to change that decision late in the project or even after go-live, at a nominal cost.

Just as with financial options, it’s important that the right to exercise the option in the future is tied to a known price. In the world of IT architecture this means that a future change or addition to the system can be made at the same or similar cost as doing it today. Following Black-Scholes, options whose strike price is higher than the stock’s current price still have value. So it’s OK if exercising the (architecture) option in the future has a slightly higher price than today. The value of the option originates from being able to defer the decision until you have more information while fixing the price.

Options and volatility

When I once shared my “option” metaphor with a head of asset management, he not only grasped it immediately, but even took it to a new level: knowing Black-Scholes very well, he immediately concluded that with high volatility (denoted by the letter Sigma, σ, in the formula above) the value of the option increases. Therefore, in times of technological uncertainty, as we are facing them today, the value of the options that architecture sells increases. Businesses should therefore buy more options, i.e., invest more into architecture.

Isn’t it fantastic when a person not from your field adopts your metaphor and takes it to a level that you had not considered yourself?