Make to Order, Provide from Stock, Assemble to Order. The three maturity levels that are understood and tried and true in the manufacturing community. In the IT community, most organizations reside in level one and are attempting to “speed things up” – all within maturity level one.

Underlying maturity level three requires two concepts and underlying technologies. Change, displacement, new learnings, and reward systems are all part of the equation, which makes people uncomfortable – and resistant to change.

In the age of digital transformation, big data, cloud computing, one fundamental fact remains. What we in organizations are doing is processing data. Technology departments have many names nowadays. But fundamentally, they process data.

We outline our approach to understanding processes – Process Mining that leads to a Business Process Warehouse. We review benefits & challenges, & outline field-proven approaches to obtaining benefits. We will also outline the methodology used to guide efforts.

Luke is the President/CEO at Retail Band, where he aims to help businesses sell appliances through online channels and allow their market to grow and expand. He has extensive product development and entrepreneurial experience.

Luke and his team are especially adept at creating product launch strategies at a wide variety of ecommerce sites.

We will get an understanding of Luke’s approaches to managing organizational change in his digital businesses.

The movement of applications to the cloud are well underway. With this movement, of course, comes observations both pro & con.

We will cover the good stuff & gotchas - some obvious & some hidden. The upsides of the cloud are pretty well discussed, documented, debated, and advertised. The gotchas, not so much!

We will provide you with a framework to think about both sides of the equation, to allow you to possibly make more informed decisions.

Our EACOE Enterprise Architecture practice looked at security as part of Enterprise Architecture, not as a separate activity.

Starting with this objective is key. In the physical world, look at the Ring doorbell – warn me before someone enters the house, rather than telling me someone is in the house. This comes from REAL Enterprise Architecture. Security is a Business Strategy first - not only an implementation technology concern.

Have you looked at your “smart phone” and its “agility” – your ability to change what you see with a simple press on the screen, and compared it to your internal technology systems or those that you provide to your customers?

This is a manufacturing concept called Mass Customization.

We must realize in information technology solutions, that no matter how quickly we write software, it is handcrafting. We will never be able to meet individual requirements.

You want a roadmap to clearly define what needs to be done to enable your Mission Strategy.

No one wants a series of endless “sprints” not knowing where the goal line is. You want to know what your end-state objective is, how to get there, & how to identify capabilities. No one really wants a set of intellectually entertaining models but to analyze potential mergers or acquisitions of a competitor & determine the degree of “fit”.

That is a Business Outcome Driven Enterprise Architecture.

Major analyst & advisory firms recognize two distinct focus areas in Enterprise Architecture – (1) focus on technology enablement, & (2) focus on facilitating and creating deliverables that guide and inform business decision making – enabling Business Strategy.

We outline what is required & the skill-sets required to bring Business Outcome Driven Enterprise Architecture to your organization. Join the movement to Business Outcome Driven Enterprise Architecture.

Being data driven, achieving digital transformation, developing effective marketing campaigns, making valid business decisions, & ensuring regulatory compliance, are just a few things businesses do, requiring good quality data.

Studies show the low self-reported beliefs on how good the data actually is. Millions of dollars are spent each year on technologies to “clean up” the data organizations are using. It's time to step back & realize that data issue doesn't require technological magic.

What is Enterprise Architecture (EA)? How long has EA been around? How do you cost justify EA? Where should EA reside in the organization? Who is the audience for EA? When do I need to do EA? Why should an organization do EA? What is an EA Framework? What is an EA Methodology? What does EA certification actually mean? What is the background required for a great Enterprise Architect? How do I start?