Still confused with the difference between process optimization and project work?

Still confused with the difference between process optimization and project work? Well, projects involve design and implementation phases.

The design phase usually starts with the process as-is assessment to a certain level of depth. Rule of thumb is to get to the level where all activities are still sequentially ordered and present a clear value chain. Do the weak points identification throughout the whole process and workshop on root causes after that (I prefer using combination of Brainstorming, Ishikawa and Tree diagram followed by Affinity diagram). What will probably happen is that eventually you will find that some root causes are intertwined and affecting more then one weak point. After that (or in parallel) start drafting to-be process based benchmarks you have, industry standards or customer journeys.

Once detailed as-is and to-be are understood, gap analysis should not be a problem. It could be done with operating model in mind, i.e., for each process step to depict what needs to be done in terms of the activities, systems/data, organization, and people competencies (skills, knowledge, attitudes).

This will basically inform the project scope. Analysis of the projects impacts, efforts, resources, low hanging fruit vs. long term tasks, etc. may ensue and will take the project to the implementation phase where all organizational intricacies are usually revealed.... This is where the true journey starts.

Enjoy the ride!