war
Using akido on the landscape
Always allow them an escape route
Thoughts On Shitpost Diplomacy
Your intention to cut
A Quote by Miyamoto MusashiThe primary thing when you take a sword in your hands is your intention to cut the enemy, whatever the means. Whenever you parry, hit, spring, strike or touch the enemy’s cutting sword, you must cut the enemy in the same movement. It is essential to attain this. If you think only of hitting, springing, striking or touching the enemy, you will not be able actually to cut him.
The McNamara fallacy
A DefinitionThe McNamara fallacy, named for Robert McNamara, the US Secretary of Defense from 1961 to 1968, involves making a decision based solely on quantitative observations (or metrics) and ignoring all others. The reason given is often that these other observations cannot be proven.
The fallacy refers to McNamara's belief as to what led the United States to defeat in the Vietnam War—specifically, his quantification of success in the war (e.g., in terms of enemy body count), ignoring other variables.
The Art of War
A Book by Sun Tzu
Pair Design: Better Together
Pair design is the counterintuitive practice of getting more and better UX design done by putting two designers together as thought partners to solve design problems. It’s counterintuitive because you might expect that you could split them up to work in parallel to get double the design done, but for many situations, you’d be wrong. This document will help explain what pair design is, how it works, and tour through the practicalities of implementing it in your practice.
It involves two brains
It involves two brains on a project at the same time. This doesn’t mean part time, checking in with each other on work that’s been accomplished separately.
Pair design really means being in the same room, working on the same problem, with both brains focused on the problem simultaneously for the duration of the project.
A distinct and complementary stance
Each person in the pair takes a distinct and complementary stance toward the design problem as they work together. One generates solutions. That is, one individual materializes solutions to the problem at hand for discussion and iteration. The other synthesizes the proposed solutions.
Gens and synths
Gens are generally comfortable drawing and drawing in front of their partner. Additionally, the generator needs to have “fearless generativity,” to be able to come up with a dozen pretty good solutions to a problem even with incomplete information.
Designers in the synthesizer role need to be skilled at describing designs and explaining rationale in writing. The role requires the designer to be detail oriented and have a strong memory, to keep the big picture of the system, stakeholders, and users in mind as a reference for designs on the table.
We come as a team
There is a legend at Cooper of one team who found pairing with each other so powerful and fruitful that when they left that company, they sought out opportunities and even interviewed at other organizations as a pair.
Starting off with pair design
It’s better to start small. Find the “genniest” designer you can and pair her with the “synthiest,” have them work through a few projects as a pair to see how it goes, evolve a process that works for your organization, smooth out the wrinkles, and become resident experts. Then, split them up, assign them with new pairs, and begin to spread.
What are the benefits of pair design?
It Makes for Better Design
- Pairing forces constant iteration: idea testing and course-correction.
- It brings to bear two brains and two stances.
It Makes for Better Designers and Better Design Organizations
- They are happier.
- Pair design makes it easier to focus on core aptitudes.
- They cross-pollinate: a mechanism for a learning organization.
Pair Design Makes for a More Effective Process
- Pairing avoids the problem of dueling whiteboards.
- It encourages designers to materialize ideas early.
- It encourages designers to vocalize their rationale.
- It encourages constant course-correction.