JavaScript Disabled

To enjoy the full experience available to this page, please enable JavaScript for this browser.

Portfolio Design Process

Designers facilitate the engineering and development a product needs to be accessible, usable, learnable, and useful. We are our users' advocate and their champion.

It is right that we designers should challenge the enterprise and each other. We should innovate and excel, but we must recognise which battles to take on, and those that cannot benefit from the effort. Sometimes that's the Project Manager's role...

A Process

There are many design processes. Some are similar to ADDIE (Analysis, Design, Development, Implementation, Evaluation): a cycle closely related to how we learn. The Analysis part of the ADDIE cycle is often expanded. As you will see below, there is much to cover in the analysis of a design task and it can take a little organising.






Close The Accordions

Conflict and Change

Conflict between designers can appear 'bloody' and at times damaging. But the benefits can outweigh the emotional wounds, which should be shrugged off by next breakfast anyway.

Conflict tests habits, ideas, and perceptions. It invigorates debate and encourages learning and change.

Designers will almost always conflict over something or other. At times the conflict will be trivial and at others you may see cataclysmic exchanges including salvoes of id. But as long as it is not only the loudest voice or largest ego that wins, and the outcome is positive to the enterprise, then it can be encouraged*.

Designers know that conflict is healthy. And they should know when it is not. Team managers need to be aware that conflict generally has a cause - and right or wrong, that cause may feed vital insight into a design.

*Caution: never leave two instructional designers on their own in a room together for longer than half a cup of coffee. (At least, not armed with tea spoons 😂)


There's no one-size-fits-all design process. ADDIE outlines the general flow. Each designer and enterprise will follow what works for them. It is only essential that whatever the analysis is, that it is thorough and not overly compromised by low resources.

It is important for the designer takes ownership of their design and support its development and implementation closely. They must be available to make informed decisions quickly when issues arise with it. Designers are a resource too.

It's the thought that counts?
Meme: It's not a bug - it's a feature