Design begins when we make the imperative known.......
Functional programming in the world of architects and landscape architects is usually a pretty dry affair. Detailed requirements are established and listed. Groupings are confirmed. And key spatial relationships (adjacencies and separations) are outlined. Actual design often grows directly out of operational diagrams, with varying degrees of architectural gesture as little more than appliqué or pastiche over the "bones" of these operational diagram.
Effective building certainly requires that we complete thorough analysis of needs and functional relationships, and we spend a lot of our time working within exactly this framework of analysis, confirmation, and functional diagramming in order to assure that our buildings work well.
However, there is another side to every building and public space project.
There are underlying priorities, wishes, values and necessities which are often not articulated - and which can provide clarity and focus to a project. It is these "un-said" - but obvious once said - priorities that can become the guiding light for design and project structure. And we work very hard to listen for and to hear them.
Once these un-said, not-yet-clear, priorities begin to see the light of day, they become the real core of our design process...........allowing this now-articulated core to drive physical order and celebratory gesture.