Hi, I'm Jeana
As a designer I categorize myself as a generalist, often oscillating between the big picture vision and the small details that make that vision come to life through an attention to craft and the human scale. For me, the end product is a malleable thing, a function of discovering the spirit of the why and the how.
There are many parallels between designing physical spaces and designing digital experiences, and often my work incorporates elements of both. As I transition from the world of architecture to the world of UX, I have found it helpful to diagram both the differences and similarities in the design processes.
VISION VS. VERSION
The design process is never a straight line from start to finish, no matter what the deliverable is. However, one of the main differences between architecture and UX is the idea of vision vs. version.
For the most part architecture projects have a clear beginning and a clear end. The vision you begin with is (ideally) what the end product looks like.
In contrast, design in the digital world is much more iterative. Products can be shipped incrementally, and can build upon one another to work towards the end version. Even when the 'vision' is completed, it might be leading to yet another idea.
DESIGN PROCESS / TASK FLOW
The general flow of tasks completed in architecture is very similar to UX, though the tasks might have slightly different deliverables and nomenclature.
CHECK OUT HOW I HAVE APPLIED THESE IDEAS: