Waste is, and will always be, a serious problem. Do we use 100% of any tool, no of course not. Should the supplier create something that only fits one customer’s need? Well that is not the way to create a tool that can be used by many.

The same problem when you create a service in a Service Oriented Architecture(SOA). If you build a service, that fits only one specific use, you build indeed just enough and probably just in time but reuse will also be minimal.

Our customers face the problem of enterprise architecture versus project architecture.

When there is no enterprise architecture, the choice for the long-term solution is often discarded. To benefit from a Service Oriented Architecture, there should be an idea how to get to the point where the benefits start to out way the costs, both in time and money. The implementation of any service can be diverse; the interfacing should be at least based on industry standards and the information source authentic.

Today I tried to analyse a process from a document.

It is never easy but with only a document as reference it is almost impossible.

You can ask a person what he means with “nearly” or “around 5 minutes”, a document cannot. So the next step is to picture the process without any detail and I will have to interview the owner of the document and also the one for whom it is written.