Now we have a quite good set of principles :-)

Congratulations. Now we finally have a quite good set of principles that will make our organisation flourish. But, it can be even better, through digging into human science, etc., which is a coming blog post. But, here are the principles so far:

Principle: We need to be able to work in parallel (if needed).

Principle: We need to be able to work incrementally (if possible).

Principle: We need to have timely* Integration Events** end to end- (to get just-in-time* feedback).

Principle: We need to have end to end control*** of our activities and their interdependencies, especially them on the critical line, when we are developing our system product and its deliverables, both short-term and long-term and timely updated, as well as on the different levels of our organisation.

Principle: We need to respect each other.

Principle: We need to have a common vocabulary.

Principle: We need to have the right competence and information to be able to make our system product and its deliverables.

Principle: We need full-time people in the same boat.

Principle: We need to nourish interactions; within the silos, between the nearby silos and cross-functional over all silos (end to end), as well as at all different levels of the organisation (so the activities with interdependencies easily can be solved).

Principle: We need to nourish broad competence, when needed in the end to end flow, to achieve better flexibility short-term (spanning from the needed T-shape when solving different interdependent activities in product development, to the needed multi-I-shape in production when solving different independent activities).

I hope you are as excited as I am, because this will give us opportunities that is totally mind blowing.  No kidding. But, that will be tomorrow’s blog post, sorry for the cliff hanger.

C u then.

 

*according to context and the needed flexibility, which means that we need to understand, nourish and be able to do work in every domain of the Cynefin™ framework, and also recognize and promptly respond to context switches, deliberate or accidental.

**in manufacturing we have Aggregation Points, which is a special case of Integration Events taking zero time.

***since variability always is around, we need to handle it with over-capacity or/and time plan margins, see this blog post for a deep dive.