The Rhineland Model resonates with the agile philosophy.
The Agile & Lean world often focuses on coaching and leading continuous transformation. Some people always feel somewhat uncomfortable with words like transformation and change, as they often imply people and organisations compelled, coerced even, to change and transform.
How about moving towards coaching and leading continuous development?
The Ancient Greek philosophers identified four aspects of development, each of which is separately necessary but all of which, taken together, are sufficient for continuous development:
- the good, and
- beauty/fun (aesthetics).
Plus, development is of greater concern to a transformational leader than growth (or change, or transformation).
- is an increase in competence and value;
- occurs beyond the norm (rather than blending to the norm);
- focuses on people (rather than on technique and content);
- tests courage (rather than patience);
- focuses on the future (rather than the present);
- urges to maximize potential (rather than standardise);
- has a transformational (rather than transactional character);
- focuses on evolution (rather than maintenance);
- educates (rather than indoctrinates);
- catalyses innovation (rather than maintaining status quo);
- encourages performance (rather than compliance);
- frees people from their boxes (rather than placing people into boxes);
- engages intellectual and spiritual potentials (rather than mechanical potential);
- fosters emotional energy (rather than only rational energy);
- explores unknowns (rather than reiterates knowns);
- pushes your envelope (rather than keeping you in your comfort zone);
- is infinite (rather than finite).
Michael D. Hill introduces RAMPS as a motivation model: Rhythm, Autonomy, Mastery, Purpose, Safety. Michael even goes deep on Mastery as Motivator: The M of RAMPS. Next, Ron Jeffries sings harmony on RAMPS.
With kudos to Michael for writing this up, allow me to join the choral by capturing RAMP’s essence on a single sheet.
BTW, The original Daniel Pink’s Drive: The surprising truth about what motivates us is about AMP, which I associate with AMPlifier.
Use a visual tool to drive the right conversations on the right topic on the right time, and capture your vision, strategy, tactics, and evidence on a single A3, also known as the hoshing kanri x-matrix, in order to:
- involve everyone in its cocreation;
- make sure you are doing the right things;
- align all stakeholders to create a laser focus on vital breakthrough aspirations;
- focus all energy on a few crucial goals;
- integrate daily management and operations with strategy;
- provide structured and fast feedback to check progress;
- stay on track and adjust course if needed.
A new design of the traditional hoshin kanri x-matrix aims to make it easier to read and maintain. Rather than having upside-down and vertical tekst, the new design only uses horizontal text.
A hoshin kanri x-matrix is:
- holistic—covers all aspects and stakeholders of your enterprise;
- fact- and evidence-based—crystal clear OKRs help drivers and leaders make timely and right decisions;
- complete—plans are ready to execute when it is clear what you want to achieve and how you will approach it;
- inclusive—involves everyone in the interactive cocreative process of catchball;
- integrated—is integrated on all levels of your organisations, including incentive systems.
Hoshin (方針) means “compass (管理), or pointing the direction,” and Kanri means “management or control”. Combined, these two words show that hoshin kanri is essentially the process for Strategic Direction Setting.
Take a deep dive at en|hoshin kanri.
Really love and fully agree with the gist of Jeff Patton’s Dual Track Development as well as Desirée Sy’s Adapting Usability Investigations for Agile User-centered Design. Throughout, there are different foci and kinds of work that are needed to evolve great outcomes. Yet, I don’t experience it as a dual track. Also, a dual track seems to split a joint effort into two groups or camps, with the danger of growing into silos and friction.
My image of this important work is much more flow minded. So, more upstream you will find people whose metier it is to continuously and fast discover, create, validate, learn about, and kill lots of ideas, promoting just a few that get fleshed out until they are ready to build by people whose metier it is to develop those ideas into an ever lasting stream of shippable revisions.
Everyone working in or on this flow aim to keep it flowing—No Business Like Flow Business™. Everyone is involved in and accountable for the flow as a whole, yet you spend most of your time in the area of your metier.
Plus, you will need a some people who focus on the big picture and optimise the whole—The Flow Must Go On™.
Also, in flow there are no cycles, yet there is a rhythm:
Drums is the way to start music. To me, rhythm is right up the center of music, and if you start with the drums and get that right, then all the other stuff that requires brain and hard work has a place to go and it all fits much better.
Tonic’s Rules to live by are quoted without permission from a little booklet I got at the SIGGRAPH ’93.
Put things where they belong. Few are won over by misplaced, misalinged, misdesigned anything. Form, really, is a function. Be kind to the user.
Observe a lot. Test everything—because sometimes “common sense” is neither.
It’s hard to make every product so understandable that people know how to use it before they pick it up. But it’s worth shooting for.
[Apple Powerbook (1991)]
Make things simple, but beautiful.
Elegant and timeless beat fancy, gimmicky, or slick. Any day.
[Digidesign RI recording controller (1993)]
Make people lust for it.
Give it a competitive advantage. Make it worth looking at. Worth holding. Worth using. Worth paying good money for.
If the guy next to you on the train had one, would you be more than a little curious? Envious? Good.
[Apple Newton prototype (1992) and Powerbook Duo (1992)]
Make it makeable.
It doesn’t matter how beautiful the thing is if you can’t manufacture it. Befriend the engineering team. Collaborate with the factory.
Instead of designing yourself into a corner, ask for their opinions. So you can produce it–by the thousands. By the millions. Affordably.
[Apple Personal Laserwriter (1990) and Macintosh IIci (1990)]
Invent the future.
If you don’t like your destiny, invent a new one.
Have some fun. Experiment.
Invent a new product category. (Or a whole new industry.) Invent a new design language. Reset the corporate compass.
“It can’t be done,” naysayers will declare. Don’t listen.
[AT&T Personal Communicator concept (1992), Apple Guide concept (1991) and Knowledge Navigator concept (1987)]
© 1993 Tonic Industrial Design, Palo Alto, California, (415) 325-1326, (415) 326-4678, fax. All rights reserved.
So, everything boils down to changing ”’human behavior”’ based on ”’feedback”’ and ”’learning”’.
People give each other feedback and feedforward so the may learn to cooperate and collaborate better. So doing, they improve their behavior.
We run a ”’Lean Startup”’ to pivot like crazy in order to improve our product, while the product and its user stories aim to trigger different behavior from their users.
All this while we tune and tweak our processes—our way of working—to also change or improve our behavior.
There’s loops of loops all over the place, on all levels of [[life is a broccoli]] and across people, product and process. Oh, how elegant.
Now, how can you get all these Agile & Lean Product Development Topics and some descriptive texts on a single, beautiful, comprehensive, and elegant A0-sized poster?
Just say no to make your yes mean something.
Spending your limited time on the things that really matter creates a more intentional and solid yes, builds trust and coherence.
If you believe that you must keep your promises, overdeliver and treat every commitment as though it’s an opportunity for a transformation, then the only way you can do this is to turn down most opportunities.
No I can’t meet with you, no I can’t sell it to you at this price, no I can’t do this job justice, no I can’t come to your party, no I can’t help you. I’m sorry, but no, I can’t. Not if I want to do the very things that people value my work for.
Yes is the future no—in other words, you are lying, often to your dear ones.
Say yes too often, and your body will automatically tell you no in no time.
No is the foundation that we can build our yes on.
Here are nine practices to say a strategic no in order to create space in your life for a more intentional yes.
- Know your no. Identify what’s important to you and acknowledge what’s not.
- Be appreciative.
- Say no to the request, not the person.
- Explain why.
- Be as resolute as they are pushy.
- Establish a pre-emptive no.
- Be prepared to miss out.
- Gather your courage.
Say no to all issues that do not align with values, goals and norms—that fall outside the tolerance of your self or your organization.
- To say “Yes” is about quantity.
- To say “No” is about quality.
- To say “No” gives certainty, dependability, safety and sureness.
Approach (similar to process leading to en|consent):
- Actively listen to the other’s question.
- Say “No’”.
- Show understanding for any response or reaction.
- Provide a focused motivation of your “No”.
- Find a solution that you both can live with.
- Track progress.
Listen to the other’s request and provide an understanding “No”, along with its motivation. Find a solution that you both can live with and track progress.
- Say “Yes, as soon as… I’ve completed all these things first‘.”