I won't discuss all the tips... Although the first tip reminds me of what I learned as a software architect. Speak their language. If you're working with the executive team, skip the change management lingo and speak in business terms.
Big insight: Meet people where they are. Ground organizational design in a familiar context, and make it tangible.
Kim's tips add up to a set of behaviors: Get scrappy, get tangible, find your people, and learn by doing.
Quite often, simple rules are used to reinforce a paradigm shift, so the rules often focus on the counterintuitive elements of decision making. Here are seven simple rules, or principles, for software development.
1. Eliminate waste: Spend time only on what adds real customer value.
2. Amplify learning: Accelerate feedback loops.
3. Decide as late as possible: Keep your options open as long as possible.
4. Deliver as fast as possible: Deliver value to customers as soon as they ask for it.
5. Empower the team: Let people who add value use their full potential.
6. Build integrity in: Don't try to tack on integrity after the product is built.
7. See the whole: Beware the temptation to optimize part at the expense of the whole.
These simple patterns are powerful. Due to their simplicity the concepts can be used in a variety of product development situations.