Principles of Shaping | Shape Up

basecamp.com · 1,690 words · saved by 1 readers

Heads up! This page uses features your browser doesn’t support. Try a modern browser like Firefox or Chrome for the best experience. CHAPTER 2: Next: Set Boundaries When we shape the work, we need to do it at the right level of abstraction: not too vague and not too concrete. Product managers often err on one of these two extremes. When design leaders go straight to wireframes or high-fidelity mockups, they define too much detail too early. This leaves designers no room for creativity. One friend put it this way: I’ll give a wireframe to my designer, and then I’m saying to her: “I know you’re looking at this, but that’s not what I want you to design. I want you to re-think it!” It’s hard to do that when you’re giving them this concrete thing. Over-specifying the design also leads to estimation errors. Counterintuitive as it may seem, the more specific the work is, the harder it can be to estimate. That’s because making the interface just so can require solving hidden complexities and i

Principles of Shaping | Shape Up sidebar#closeWithKey"> Heads up! This page uses features your browser doesn’t support. Try a modern browser like Firefox or Chrome for the best experience. sidebar#open" aria-label="Shape Up Table Of Contents"> Shape Up Chapter 2: Principles of Shaping Wireframes are too concrete Words are too abstract Case study: The Dot Grid Calendar Property 1: It’s rough Property 2: It’s solved Property 3: It’s bounded Who shapes Two tracks Steps to shaping Next: Set Boundaries sidebar#close mouseup->tweet#update input->tweet#update keydown->tweet#update scroll@window->twee

Principles of Shaping | Shape Up

related reading