Design without process, or the form factor trap
When I’ve seen designers ask for sign-off for this type of work without something visual to support it, they always end up frustrated when the client changes their mind after seeing the ideas represented in a more tangible form.
I suggest you never present things like this as standalone design work—only present how they affect a person doing a thing
... See moreDonna Spencer • Presenting Design Work
The design phase is not just about putting your ideas into pictures; it also includes expansive thinking and validating your ideas with real people. This includes both the user experience (e.g., mock-ups and visual prototypes) and the technical solution (design docs and technical prototypes).
Gayle McDowell • Cracking the PM Career: The Skills, Frameworks, and Practices To Become a Great Product Manager (Cracking the Interview & Career)
that can and should be done in parallel. For example, I have long argued that requirements (functionality) and design (user experience design) are intertwined and should be done together. I don’t like the old waterfall model of a product manager doing “requirements” and handing that off to interaction designers that do “design.” Most teams understa
... See moreMarty Cagan • Inspired
FIGURE 8.6Typical results for “design process.”
Dan Mall • Design That Scales
When problems are really tough, we need to get drawing. We draw to see what we think, in order to evaluate those ideas.
Christina Wodtke • Pencil Me In
It's so tempting for product teams to immediately slip into an enumeration of all the features they plan to build, with little real thought into the actual benefits for our customers. This technique is intended to counter that and to keep the team focused on the outcome, not the output.
