In addition to our framework deep-dive it is a pleasant distraction to also keep making stuff, to prototype our interaction with the end-user. How will the 21 capacities as a framework (the model of the Skool) relate to the Next practices of WWXD. Are this two very different propositions or is it an integral service? I don't hope we are ending with two companies, again! Make it tangible

This week we crafted our first "WWXD" (What Would X Do) magazine or mailing or.... The theme we are focusing on is the Art of Meeting. This is either connected to capacity 17 (culture & skillset) or 11 (system & skillset) As we tinker our way forward with Powerpoint and Keynote (let's make a decision pfff), we've discovered two distinct approaches:

1. CONCRETE; The "What Would X Do" approach, offering tips and tricks from real-world examples. WHat would Bezos do? What would Musk do? What would the UN do?

2. ABSTRACT; A pattern-based approach, providing a more instrumental view of how we perceive meetings. For example, what kind of meetings exist? What are the design elements and principles?

First mock-up

Our goal is to complete the first version by this Friday. To achieve this, we've created an initial mock-up to demonstrate how it might work. We've chosen a distinctive template featuring a diagonal layout: the upper section always displays a human photo, while the lower section showcases a structural visualization or illustration. We're aiming for high contrast in the color scheme to make it visually striking. This screams ACTION!

Navigation; Swiping left or down (oops too complex) Navigation through the diverse WWXD examples is achieved by horizontal scrolling, while vertical scrolling allows users to explore the content in depth. This unique design ensures an engaging and intuitive user experience.

The L-template of the WWXD digital magazine

In our current prototype, we've included three fascinating examples:

1. The Ubuntu approach of a Tribe

2. Jeff Bezos's Two Pizza Rule (and his no PowerPoint policy)

3. Elon Musk's no-meeting strategy

These examples form the horizontal axis of our guide. Vertically, we delve into various types of meetings, each accompanied by concrete "hacks" to improve efficiency and effectiveness.

Our WWXD guide will offer fresh perspectives from successful leaders and organizations, while also providing practical tools for immediate implementation.

While I'm writing this our conceptual enthusiasm is a bit fading. Users need interfaces that are intuitive, which they recognize otherwise we have to sell our philosophy, our services ánd how to use them. That hurdle is too much. yet we will test anyhow since it is always good to see and learn what they do like (and maybe why?) And... a first editorial overview... a topic model (term borrowed from Data Science);