Designing for teams that will edit it later

We learned this over several projects, and it changed how we work. We get asked this a lot, so this is how we approach it.

In short: the obvious answer is usually right, almost every time. We learned this the hard way, and it changed how we work. Here is a small example from our own work. In short: clarity beats cleverness, almost every time.

The short version: clarity beats cleverness, almost every time. If you take one thing from this: decide before you design. We came to this over several projects, and it stuck.

Here is a small example from the last few months. The one thing to remember from this: start with the problem. In short: clarity beats cleverness, almost every time.

Here is a small example from the last few months. The short version: clarity beats cleverness, more often than not. We learned this the hard way, and it changed how we work. Here is a small example from our own work.