Search Results for: business model

Business Transformation Survey: The Results

by

Organizations have always had to adapt to change in order to stay relevant. But in today’s fast-paced market, change is more necessary than ever. In a recent survey we found that over 60% of C-level management thinks that changing the business model is the main driver for business transformations.

In collaboration with BPtrends, The Open Group, and the University of Twente, we surveyed over 550 IT professionals worldwide, from C-level management to practitioners in a wide range of disciplines, in order to gain more insight into business transformations.

Key Takeaways From Informatica World 2016: Informatica Pivots From A Data Company To A Business Insights Company

by

Informatica World wrapped up in San Francisco last week where almost 3,000 customers and partners gathered in the Moscone West conference center for four days packed with executive keynotes, customer and partner presentations. Based on my time there it…

The role and rise of the business-anarchist

by

You may have noticed some new role-titles turning up in the enterprise space. Chief Disruption Officer, for example. Or Chief Transformation Officer. A fair few variants on that theme. But what you probably won’t see – not as yet, anyway…

Designing the Business of IT … but will it add value to my business?

by

As awareness and interest in the Open Group’s new IT4IT Reference Architecture continues to gather pace in online communities, blogs and industry events, one over-arching question remains; what is the business value of this new […]

The post Designing the Business of IT … but will it add value to my business? appeared first on Enterprise Architects.

How MDD brings business relevance to the PaaS space

by

It seems that we have past the top of the hype around Platform-as-a-Service. A good moment to assess how serious the adoption of PaaS is in the enterprise. The different PaaS flavours It’s a while ago that I tried to structure and categorize the different cloud approaches to clarify the different types of “cloud” that we see in todays market.  I distinguished among 3 layers of Platform-as-a-Service (and some more layers that.

The post How MDD brings business relevance to the PaaS space appeared first on The Enterprise Architect.

Don’t Sacrifice Your Business Architecture

by
Business architecture is core for an organisation’s Enterprise Architecture. Both the leading Enterprise Architecture frameworks, TOGAF and Zachman advocate Business Architecture to become a fundamental corner stone of Enterprise Architecture. Business architecture is about not just about business process modelling and business capability definition on a project to project basis. I think it is also about defining the Target Operating Model of the organisation. I have personally experienced the power of applying pragmatic business architecture to model current (as-is) and target (to-be) business operating models.
However Business Architecture is not easy to deliver on. An organisation needs skilled and experienced practitioner architects to engage stakeholders, establish relationships to understand and model the business capabilities, business processes workflows etc. Business architects should ideally also need reasonable domain knowledge of the respective business to make a meaningful contribution in the design of such model. Otherwise that individual runs the risk of becoming simply (an expensive) documentation resource.
These days often the funding for Enterprise Architecture is limited and high priority projects and programs are often competing for best resources and funding. In these situations often the Business Architecture resources are sacrificed to make way for technical architects (e.g. infra, integration). In such scenarios an organisation runs the risk of doing Enterprise Architecture without Business Architecture. This probably results in this organisation doing IT Architecture rather than Enterprise Architecture. See below graphic. 
It will probably still deliver value by bringing structure, discipline, visibility and planning to the critical IT project delivery. However these efforts risk falling short of becoming something much more meaningful and sustainable investment for business and not just IT.

I strongly feel that organisations should not sacrifice Business Architect. When resource and funding is limited, instead such organisations should find clever alternative ways to resource them. Some of the options which have worked for me in the past are;
  • Get your most important projects to fund it and then expand that to Enterprise level
  • Use your experienced application or data architect to play the role of Business Architect in the interim
  • Leverage your strategic partners / suppliers to perform this role
  • Leverage your customers / internal business stakeholders to play this role directly and indirectly. I came across an excellent real life use case of this recently. More on this in next post.

Don’t Sacrifice Your Business Architecture

by
Business architecture is core for an organisation’s Enterprise Architecture. Both the leading Enterprise Architecture frameworks, TOGAF and Zachman advocate Business Architecture to become a fundamental corner stone of Enterprise Architecture. Business architecture is about not just about business process modelling and business capability definition on a project to project basis. I think it is also about defining the Target Operating Model of the organisation. I have personally experienced the power of applying pragmatic business architecture to model current (as-is) and target (to-be) business operating models.
However Business Architecture is not easy to deliver on. An organisation needs skilled and experienced practitioner architects to engage stakeholders, establish relationships to understand and model the business capabilities, business processes workflows etc. Business architects should ideally also need reasonable domain knowledge of the respective business to make a meaningful contribution in the design of such model. Otherwise that individual runs the risk of becoming simply (an expensive) documentation resource.
These days often the funding for Enterprise Architecture is limited and high priority projects and programs are often competing for best resources and funding. In these situations often the Business Architecture resources are sacrificed to make way for technical architects (e.g. infra, integration). In such scenarios an organisation runs the risk of doing Enterprise Architecture without Business Architecture. This probably results in this organisation doing IT Architecture rather than Enterprise Architecture. See below graphic. 
It will probably still deliver value by bringing structure, discipline, visibility and planning to the critical IT project delivery. However these efforts risk falling short of becoming something much more meaningful and sustainable investment for business and not just IT.

I strongly feel that organisations should not sacrifice Business Architect. When resource and funding is limited, instead such organisations should find clever alternative ways to resource them. Some of the options which have worked for me in the past are;
  • Get your most important projects to fund it and then expand that to Enterprise level
  • Use your experienced application or data architect to play the role of Business Architect in the interim
  • Leverage your strategic partners / suppliers to perform this role
  • Leverage your customers / internal business stakeholders to play this role directly and indirectly. I came across an excellent real life use case of this recently. More on this in next post.