Introducing Evo in a development organisation environment is usually done by visiting the organisation one day a week for an average of 10 weeks. Within a circle of about 200 km around Utrecht, The Netherlands, this is the preferable way.

Outside this area, but within Europe, this scheme is still possible. However, for every visit, 0.5 to 1 extra days will be charged for the travel involved. An alternative scheme is suggested, as shown below.

Outside Europe, 1 to 3 extra travel days per visit are charged, making the one day per visit rather impractical.
Therefore an alternative scheme is suggested:

Example Evo Introduction Plan

This Evo Introduction Plan will put two or three development teams of 5 to 10 people each on the Evo track, as described in the booklet: How Quality is Assured by Eolutionary Methods. Note that we can work out any other program. The basis is always win-win. If my involvement would cost the same amount as you are saving: DON'T DO IT! The savings we are going to make (less loss, or preferably: more profit) should be at least twice the amount you will spend on my involvement, although I agree that this is not so easy for you to judge up front. Imagine the revenues if we save one month of your project: we save the cost of the project, plus the extra revenues of the result. And how much late were your recent projects? Remember also the Satisfaction Guarantee on the Availability page: you are never stuck with me. I expect that together we can save some 30% on your current project within a few weeks.

1st visit:
Thursday and Friday: Working with several (pilot) projects to organize their work and their next week.
One week later on Thursday and Friday: closing the TaskCycle, analyzing the results of the past week, learning from it, and planning the next week, based on what we learnt.
We could spend one more day (Wednesday) to discuss the technique more generally for the organization, and how to visualize the process.
Available working days in this visit: 7, but total time probably needed: 5 working days. I take it upon myself to spend the remaining days usefully.

2nd visit, several weeks later:
Wednesday: Discussing the progress in general: what can we add and do better.
Thursday and Friday: closing the current TaskCycle, analyzing the results of the past week, learning from it, and planning the next week, based on what we learnt. Because people have done this now for several weeks, they will understand some details better now.
Expected number of working days: 3.

3rd visit, several weeks later: similar to 2nd visit.

It is important to close a full TaskCycle loop in the first visit, because this way a lot of small but important details come to life. Between visits, I will check the progress of the pilot projects and advice on a distance. This will take me a few hours per week.

At the end of every visit we analyze what we did, whether it was useful and whether and how we think we should continue this process. At the end of 3 visits we can decide that we did enough or that we want to carry on to disseminate further into the organization or improve even further.

Because it is my experience that it is very difficult for anyone to understand exactly what we are going to do, until we are actually doing it, I work with two types of guarantee:

Satisfaction Guarantee
All work by Malotaux is done to the best of his ability. Still, it may be possible that the ways of working or the expectations of the Client and Malotaux don't fit. Therefore, termination of the cooperation is possible at any moment, only by formally telling this, while explaining the reason. In such cases, only the work until that very moment will be charged.

No cure no pay
Further more, any day you would be dissatisfied with the results of Malotaux’s work will not be charged, on the condition that you file your complaint with Malotaux within 5 days after that day, or in any case before any next day of Malotaux’ work. In such a case, any planned further activities by Malotaux will be automatically deferred, until we decide that satisfaction can again be expected.
These clauses keep both me and you on the alert that we continuously are contributing value. After all, we should practice what we preach!

August 2008.