Inside of my head...scary?

TECHNOLOGY AND BUSINESS ARCHITECTURES BECOME ONE

The rational to change the role from selling data into architecting systems intelligent solutions is likely that the most important perspective comes from the result of the “platform” phenomena. The key concerns;1) the relationship between technology architectures and business models, and 2) the “role” that platforms and relationships will play in enabling a whole new level of differentiation. Platform development decisions must be aligned with the corresponding business and revenue models.

Two “architectures”—technology and business—need to be mutually supportive without inhibiting one or the other.

If you look around, and it is easy to see that an ever-tighter coupling of them, success will increasingly go to those that effectively utilize the combined potential of both. In turn, the emerging platform will become the central organizing mechanism for delivering new added value from data, towards information and ultimately systems intelligence, and drive the outcome based services - The Killer APP -

However, coordinating and leveraging technology architecture and business architecture has never been in the wheelhouse of traditional B2B companies, and it often creates contention. Management attention in the businesses that has traditionally focused on the known, the visible, and the predictable. Anything too difficult to measure is too often treated as if it were unreal. Further, management in many businesses tends to assume that, whatever the tangible focus is, business and their peers share similar characteristics, organisation structures, product development protocols and sales and marketing practices.

Even more misleading is the assumption that “business as usual” will prevail over a given planning period. Such assumptions leave little room for dynamic management (or creation) of change, the early identification of emerging markets or technical discontinuities, or the increased presence of unfamiliar competitors.

So – what matters to an (I)IoT Solution Architect? Recently, I spotted The EA Headspace infographic and it is a fun way to communicate what’s on the mind of Enterprise Architects. Just for fun, EA Architects started sketching a network diagram of concepts that are important to an architect. As the list grew we noticed many of the ideas had a strong bias toward analytical, left brain thinking, while others were more in the intuitive space – and several ideas were somewhere in the middle, drawing from both.

A fun way to start the discussion; “What matters to our business and what is in the mind of the (I)IoT solutions architect”