3. Deep-dive: This is more of a tool than a methodology. It is a combination of brainstorming, prototyping and feedbackcombined in a way that allows managers to develop solutions for different business-related problems and tasks.
The various stages in this methodology are-
Evaluate and Refine
First, one needs to understand the needs, constraints, problem areas.
Then, it needs to be well observed in the real-world setting among real people.
Following that, one begins to envision new, unique solutions which are then tested and finally, commercialized.
4. RMT: It stands for Risks, Motivation and Trigger. In simple terms it means-
Firstly, try to analyse the risks faced by users.
Then what's their motivation area (which inspires them to do a task)
Finally, watch out for their trigger points and formulate a design solution based on your research.
5. MoSCoW: stands for Must have, Should have, Could have, Would like, Won't get.
The MoSCoW method is most effective when it comes to prioritizing requirements in projects with either fixed or tight deadlines. It works by understanding the idea that all project requirements can be considered important but that they should be prioritized to give the biggest benefits in the fastest possible period.
6. Simon Herbert: This methodology divides the process into 7 distinct stages namely: Define, Research, Ideate, Prototype, Choose/Objectives, Implement and Learn.
Although considered a non-iterative process, the Simon Herbert methodology stages can occur simultaneously and may be repeated as well.
7. Bootcamp Bootleg: One of the most well-defined and complete methodologies existing is the one developed by Stanford d.school.
It defines its steps as Empathize, Define, Ideate, Prototype, and Test.
Bhai, ye toh stanford wale bhi follow karte hain! Toh sahi hin hoga xD
8. DONUT: A circular and iterative methodology is the Donut. Also known as the Iterative Design Process Cycle, it begins with the design brief and moves circularly until it arrives at a solution.
divided into the following stages: problem finding (observing and research), problem selecting (reframing and contextualizing), solution finding (converging and establishing core user needs) and solution selecting (experimenting and prototyping).
In the first stage, an in-depth research is done which includes literature reviews, personal observations etc.
In the second stage, approaches to problem-solving are employed by careful analysis of the information collected and patterns are identified.
In the third stage, user needs are identified and prioritized.
Finally, in the last stage, the tools or products are built and tested that meet the consumer needs as well as offers solutions to identified problems.
There are many design methodologies but here, I've tried to discuss only a few of them. :) You can go forth reading design methodologies in a continuous loop, but it won't be advantageous if you don't implement them in your design thinking process.
Here's a link in case you want to dive in deep and complete your projects asap by following design methodologies.
About Kaphal Studio
Kaphal Studio is a modern, internet university for creators that brings community and learning together. We aim to prepare designers for the startup economy. We offer a new approach to online education through synchronous cohorts with an emphasis on peer-to-peer learning.