Flow vs Dual Track Development

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 wholeThe 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.

—Peter Gabriel

Tonic’s Rules to Live by

Tonic’s “Rules to live by” are quoted without permission from a little booklet I got at the SIGGRAPH ’93.

Be kind

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.

People, Product, Process

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.

Agile & Lean Product Development Topics

Plethora of topics to cover on agile & lean product development
Plethora of topics to cover on agile & lean product development

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

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.

  1. Know your no. Identify what’s important to you and acknowledge what’s not.
  2. Be appreciative.
  3. Say no to the request, not the person.
  4. Explain why.
  5. Be as resolute as they are pushy.
  6. Practice.
  7. Establish a pre-emptive no.
  8. Be prepared to miss out.
  9. 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 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.

Therefore:

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.

Variations

  • Say “Yes, as soon as… (I’ve completed all these things first).”

Mirror Mirror On The Wall

Click image for PDF.
Click image for PDF.

About 30 people in a lean startup context, with about one third coming from various internal departments and two thirds from external parties, assembled to completely overhaul the digital experience—website and apps—from a major Dutch company.

Only recently the group is complete, storming towards their goal. Each individual brings her or his own view on agile and lean, resulting in a potpourri of practices, each trying to find the best way to get going.

To streamline all these efforts and embed organizational and practical feedback loops, the group conducts a series of values-based Agendashift experiments. A six week cadence of Agendashift surveys provides the input for regular ‘retroprospection’. The first survey has just been completed.

Based on the survey’s results, a single lean style ‘A3 Mirror’ distills the essence of the first survey. Next survey is in a couple of weeks, and allows the team at large to check their progress in specific areas.

The results of the survey fall into two categories:

  1. Tops
    • key areas that the team sees as their strengths;
    • a simple copy the survey’s prompt.
  2. Tips
    • key areas that can improve the team’s way of working;
    • phrased as “instructions” in order to turn observations into action-oriented language—just like in the patterns of a Pattern Language; and
    • the source for three key objectives to bring focus on what matters most, and candidates to be turned into a limited set of Objective & Key Results.

Wishes for future revisions of Agendashift and the A3 Mirror:

  • generate the A3 Mirror directly from the survey results, facilitating continuous retroprosection or learning;
  • include vector-based charts in the A3 Mirror;
  • maybe just one or two key points per Top and Tip for each of the six focus areas in order to make it even more terse and comprehensive;
  • include a timeline of Flower Charts to see the team coming to full blossom.

Related:

Flower Chart

Somehow, I always have disliked radar charts. They connect unassociated dots and I find them antique remnants from the past millennium. They yearn for a fresh new look. Pondering and visualizing, I came up with the ‘flower chart’. The unfolding of the flower shows its gradual development, adds the time laps or ‘Zeitgeist’ to it.

The examples below use the six values of Mike BurrowsAgendashift, value-based delivery, change, and leadership, based on Agile, Lean, and Kanban.

Depth Flower Shu
Depth Flower Ha
Depth Flower Ri

Thoughts?

The Universe on Agile

This just in, a Note from the Universe captures the essence of agile:

Start it; you don’t have to be fancy.

Keep moving; you don’t have to go crazy.

Visualize; you don’t have to admit it.

See the end result; it doesn’t have to be material.

Expect miracles; they don’t have to be huge.

Pretend you’ve arrived; you don’t have to dance on tables.

And above all else, Martien, have fun.

This is why you started it, right?

Life, what a trip

—The Universe

Okay, okay, Martien, they can be huge and you can dance anywhere you like… but you might rethink the frilly tutu.

Rehearse to boost adaptive power

aap
Image: Business Insider » Why star US Gen. Stanley McChrystal eats only one meal per day

General Stanley McCrystal from the U.S. Joint Special Operations Task Force in HBR » What Companies Can Learn from Military Teams:

I still believe in rehearsals, but I’ve learned they have a different value. When I joined the Army Rangers in 1985 we’d rehearse airfield seizure operations—we’d parachute in wearing night vision goggles, and take the field. It’s a pretty complex thing, and we’d do it over and over. We’d have contingencies in case things went wrong, but we were always trying to make things as foolproof as we could.

The longer we did it, the more I realized the value of rehearsal was not in trying to get this perfectly choreographed kabuki that would unfold as planned.

The value of rehearsal was to familiarize everybody with all the things that could happen, what the relationships are, and how you communicate. What you’re really doing is building up the flexibility to adapt.

I’ve never been on an operation that went as planned.