"The topic for this article is in reality a sequel to one I wrote about in 2024 (you can read that first installment here). In that article I explained the reasons as to why the Design Process can at times be perceived as a lengthy one, and what factors influence it. I also provided some color to this topic courtesy of some products and engagements I went through in the past that are revelatory of processes that can be labeled "long" and "short". This "sequel-article" is a more succinct follow up, and I'm aiming to dispel the concept of Process as something bloated. Hopefully what I'm about to write will spark some conversations/discussions/reflections, which is ultimately what I always aim to be a catalyst of."
"Somehow the association that the Design Process is tied with a lengthy set of tasks that requires a considerable amount of time has been imprinted for some professionals in the Technology field, typically those who are more on the periphery and have a very superficial knowledge of what the process actually entails. I'm going to reinforce that for a Design process to be successful, it requires a methodical approach to it, one that is tied with being thorough and systematic in its diligence."
The Design Process should be methodical and systematic without being inherently slow or wasteful. Methodical is defined as habitually proceeding according to method and requires thoroughness and diligence to achieve successful outcomes. Being thorough does not equate to being time-wasting; efficiency can coexist with systematic practice. Misperceptions of a bloated process often arise from peripheral professionals with superficial understanding who favor cutting corners. Observations across teams show critics of process length are frequently those who undervalue rigor. The goal is to reframe process as disciplined and efficient rather than excessive.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]