#design-research

[sxpxrmxrgxr]

[gadlabs]

GAD - Anatolıum Marmara WIP - Modulation Concept

[jonathanstegall]

"The sketchboard is a low-fi technique that makes it possible for designers to explore and evaluate a range of interaction concepts while involving both business and technology partners. Unlike the process that results from wireframe-based design, the sketchboard quickly performs iterations on many possible solutions and then singles out the best user experience to document and build upon."

[jonathanstegall]

How the 'Failure' Culture of Startups Is Killing Innovation | Wired Opinion | Wired.com

There is absolutely no right amount of — or rigid process for — research except what’s right given one’s goals and resources at a particular time. Someone can take two days, two weeks, or even two years depending on the scope of work and how much is both possible and useful to learn in advance.

The key is to be honest about how much we really know.

We need to identify our most critical assumptions, and then decide how to validate them. For example, a common assumption is that the organization — given its structure and business model — is capable of delivering the service the entrepreneur envisions.

[jonathanstegall]

> "IA thought leader Lou Rosenfeld explains how balance, cadence, conversation, and perspective provide a framework enabling your research teams to think across silos and achieve powerful insights even senior leadership can understand."

[jonathanstegall]

> "What if you could sift, store, and share all your customer learning in a way that breaks down silos, preserves and amplifies insights, and turns everyone in your organization into a researcher? MailChimp’s user experience director Aarron Walter tells how his team did it."

[jonathanstegall]

> "The problem is, adding the box to the beginning of the schedule doesn’t stop derailment. But if our goal is to pass the blame on to stakeholders we interviewed, saying “you didn’t tell us up front when we asked,” then we can declare this as mission accomplished. However, if our goal is to produce a great design that delights our users and meets their needs, we need to move on from adding a box to the schedule to a set of activities that work."

[jonathanstegall]

> "We’ve found the best teams have replaced the requirements gathering box with four core activities which changes the power dynamic. It assumes that nobody knows what we need to build, though some people have ideas. If we can validate the ideas and then refine them, we all become smarter about what would delight customers and users. > The four activities are forming hypotheses, conducting research to test those hypotheses, documenting what we saw with scenarios, and using critique to validate the design is serving what we learned. What’s funny is none of this is new. We’ve known how to do these things all along. Most of us just don’t do them."