Cookies & Privacy
We do not track or sell your personal data. We use a minimal amount of cookies in order to provide the best experience for you. By using this website you agree with our terms of use
Got it
articledanger menuaward user
#Marketing #UX / UI #Product Development

How to mash-up and benefit from PM and the Design Thinking Process

The Homera mash-up car made for one user – Homer

Ever struggled with managing your projects or PMs trying to do so? Well, there is an app… hmm… or something different for that.

Recently I took on the Design Council’s Double Diamond process, “revamped” it, and published it (Link at the end of the post). People have questioned how my approach would relate to “real” project management and projects.

This follow-up post is about my mash-up approach to answering this. This is not about comparing the HCD process to PM but to overlay the two disciplines in order to gain an understanding when working in an environment where people rely one or the other.

Mashing-up stuff doesn’t always work... But f*ck it. I’m doin it anyway.

If you are familiar with my Revamped Double Diamond Design process skip the next paragraph.

Revamped Double Diamond

The Revamped Double Diamond is a design process framework based on the Design Council’s (2007) Double Diamond.

Latest and slightly updated version of my Revamped Double Diamond (01.09.2016). “Themas and clusters” are now a before “Insights”

It aims at making sense of the design process and providing guidance and clarity in order to tackle a design challenge. The framework incorporates tools, methods and techniques from various sources to do so (find links to my detailled article at the end of this post).

Project Management in a nutshell

“Project management is the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements” (PMI, 2013).

I’m not going deeper into PM theory and focus on two major PM “families” : “Waterfall” (traditional, sequential) and “agile”.

One… wait… two more things, though:

When talking about “Agile” I am mainly referring to the mindset and way of thinking rather than one specific method, based on the “Manifesto for agile software development” (Beedle et al., 2001).

The manifesto lists four core values:

Individuals and interactionsover processes and tools

Working softwareover comprehensive documentation

Customer collaborationover contract negotiation

Responding to changeover following a plan

Royce (1970) visualised the probably first and later referred to as “waterfall” PM method, incorporating a two-sided relationship between development phases. He linked each phase back to its predecessor acknowledging potential iterations.

Please sign-up or log-in to continue reading

Parrity is free forever. Join our open beta today & get lifetime superuser access & other awesome perks! 🤗 🚀

Already have an account?   Sign In

Join our beta for a lifetime superuser access & other awesome perks! 🤗 🚀

Join our beta to get lifetime superuser access & learn from the smartest business minds on the planet web 🧠 😎

Join Beta