…about design, the design process, and technology as part of that process, its limitations, added value, adventures, and discoveries in that process. Design Process Technology? Yes, a conversation.

I am an architect and principal at Hoy+Stark Architects.

Our practice is that of an architectural studio; I invite you to see our website,  HoyStark.com

Our practice is one of involving clients within the design process as much as they want. Ours is a practice of relationships, not just projects. Relationships with clients, authorities, contractors, and material providers. The same can be said of the elements we utilize in our practice – the hardware, software, and tools we use to progress the design process. Nothing stands alone. Everything in our process relies, in some way, on the things around it. Staff, conversation, presentation, input, thought, response, result, hardware, software, output, product, documents, models, drawings, specifications, seals, sets of documents for project delivery.

Design is a verb. Design has value and that value can be measured. By what measure, and what value, our clients determine and bring to a project.

These are personal observations and thoughts that my office and partners have heard before and agreed (and sometimes disagreed) with over time. This is a round-about way to discover “value” in the process. Ultimately, you decide where value is – our clients decide this, contractors, officials, suppliers – we all decide this.

Where is the value in the process?

Is the result worth the costs?

Technology? Time? Efforts? Ownership? All of these come into play in this adventure.

How much technology? How current is the technology?

What kind of time is involved in the design process? How about time involved in the technology effort – just to keep it running and current – and to keep ourselves current? What kind of effort does this take? Ownership: who owns who? Do we own the hardware and software (and updates, versions, conflicts, training, licenses, subscriptions, etc)….or do they own us? Honestly, sometimes it’s hard to know which.

Don’t get me wrong,  I love what I do.

It’s exciting and challenging and rewarding on all kinds of levels. I can’t think of anything else I’d rather be doing. Over the last 15-20 years the pace of the architectural world, our local practice, and the design process and technology I’m referring to has ramped up in pace, scale costs, and need of attention – it’s really quite exciting. Really.

My studio utilizes Apple hardware and both MAC OS and Windows operating systems. I’ve been asked to speak on these things at two state conferences and several other events to illustrate how we do what we do – but more importantly, illustrate what can be done – opening the door to that and beyond what we are currently doing.

So, what are we doing?

MAC? – Yes,  with all it offers in ability and limitations.

Windows? – Yes, with all it offers in ability and limitations as well.

Mobile devices? Absolutely.

“Cloud”? – reluctantly,  yes.

Virtual Machines? Yes.

Drones? Yes.

3D printing? Yes.

Virtual Reality/Augmented reality? Not yet, but it’s coming…

Digital vs Analog? Yes, but not vs – rather, along with.

BIM? Yes?

2D Cadd? Well yes, but fading…

Sketching? Hand Drawing? Yes. Absolutely.

An example of what I’m refering to is a video I prepared for an architectural school exhibit. Everything shown is digital. Yet, it looks at times not digital. We blur the lines and do not want to distinguish between or separate the two – digital and analog can live, work, and flourish together. This is a wonderful world now. Why should you have to choose between vinyl records or digital music – why not both? The same can be said for everything we do.

HSA Digital examples from Monty Stark on Vimeo.

It’s a beautiful thing. A wonderful soup of swirling possibilities and opportunities of success, conflicts, updates, compatibilities, conversations, and solutions.

I invite you to join me as I share with you what we have discovered and confirmed. It’s always a moving target – let’s see where this goes.