n a surprisingly tranquil street for the middle of Manhattan, inside an unassuming brick townhouse, gathered around a ping-pong table, sit the members of CASE inc. Or at least the members who do not telecommute from other parts of the Americas. William Mitchell tops the pile of books on the table, although the whole scenario would fit inside one of Mitchell’s books. The only signage is a business card taped to the door, which announces you have entered a place more like a start-up than an architectural office. And it is. CASE aren’t just another consultancy rationalizing Maya models, CASE are a new generation of designers, unusual not just for their working arrangements, but because they seek to change how architects practice. They do all the rationalisation stuff, but they also guide firms through technological changes and openly share what they do on a suite of websites (Design Reform, Design by Many, CASE inc, on Twitter, and even a spot on Arch Daily). I visited David and Federico when I was in New York and asked them a few questions. To me the salient part of their answers is how little they talk of technology and how little they fetishise complex geometry, to them the real challenge of computational design is an organisational one – a challenge few people (especially academics) are in a position to observe.
We all bought into a lot of things that SHoP was talking about, bought in is not necessarily the right word, but we really believed in it. They were out there using the technology to push design and as a small firm they were able to do some really amazing things. A lot of that wasn’t really making its way out into the broader industry. In their case I think it worked because they had great buy-in from the partners, they believed in it, and they gave us the flexibility, but that doesn’t scale. So we saw an opportunity as a consultancy to go out and help the industry to implement a lot of these things.
CA lot of it is people problems. Or people challenges – problems is not the right word. I am sympathetic to it. Often we get hired and the decision has been made, ‘we want to implement Revit’ – lets say – so we are the guys that come in and teach you Revit and help you setup your standards. Some people just don’t want any part of that. They just don’t see the value in it. This is also one of the biggest challenges for clients – conveying why they are doing it. Often times it is a reason like ‘a client said so’, which is not very easy to get buy-in from everyone doing the production on a daily basis. If it was more along the lines of ‘we think this is how we can change the industry, this is how we think we can do twice as much design and get better fees because we are leveraging technology’ then I think people could get onboard with that, but just ‘the client said so’ is kind of meh.
So a lot of it is around people and communication. You can ultimately make technology work, there is always other software. I don’t think cost is a big deal either since the software is switching to these yearly subscriptions, so it doesn’t matter whether they are buying software X or software Y.
CI think there is two routes. Either fragmentation, where firms get smaller [and hire consultants]. Or vertical integration where a large firm has centres of excellence – a geometry group that services the rest of the firm. I think [vertical integration] is hard to manage because ultimately that group has to answer to somebody and needs some level of accountability. Whereas us as an independent business, our accountability is that if we don’t do it right we are going to go out of business.
Those are the two ways I see it going. And that is not to say they are mutually exclusive but that is what I could see happening.
CI like all our clients, I like all their work, I like all of them, I think they are all equally good. [ Laughs and says not to publish any firm names, ‘that will be the first email to come back to me’]. But they are all different. Some firms have a CIO, some don’t, some have a CTO, some don’t, some have a CKO (Chief Knowledge Officer), some don’t, some are partnerships, some are corporations, some have independent profit centres per office, some don’t. It really is so different per office. And that does translate into how I feel about them as a firm, not in a bad way, but it just gives me sympathy to say ‘I understand they have 10,000 plus people and they just can’t do what a 60 person firm does.’ It is just not apples and oranges. So one thing over time is my appreciation for the complexity being far beyond the geometry. In academic persuits it’s like ‘oh yea that is really cool geometrically’ but that is such a small part of everything that goes into a building. Complex systems, complex contracts, liability structures, delivery structures, schedules, all of that stuff is complex and can benefit from technology. So different firms tackle that stuff in different ways, which are not trivial by any means.
Evgeny Shirinyan
… and complex information management. Even in a small bureau it can be not easy, maybe because of flexible and sometimes chaotic workflow. What is amazing in other industries, e.g. manufacturing, that they are going in a similar “nonlinear” way when whatever sort of complexity arises.
More data granularity, less hierachical structures, powerful search, semantic technologies etc. These concepts I was testing and investigating with a certain developer for last 5 months – and I like it)
Btw, great interview, Daniel. I was always interested in stuff they’re doing
Daniel
Yea I think it is interesting to see how our skills as designers (in curating complexity) apply to many other disciplines of ‘complex information management’. I hadn’t really given it much thought until I meet CASE, but there are so many interesting problems beyond geometry to explore.
Evgeny Shirinyan
Actually that kind of information mgmt was always part of my practice – DIY CAD-mgmt etc. Now we get new tools. More elegant and userfriendly. So you begin to think in two ways: from bottom-up (how you create information) and top-down (searching, filtering, diagramming in a meaningful way)
Ben
Both CASE and SHoP have a unique perspective on digital workflows, in that they see the problem of information managment and office management to be integrally related. My favorite part of the interview was when he put his business consultant hat on and began hinting at how office legal and business structures affect how and what technology is implemented on a base level. BIM and other complex computational methods are going to affect the organization of architectural practice to a degree that previous techologies never have.