Category Archives: Design Management

Architecture and Design Fees: Why hours?

Posted on by
4

money by fedee P, on FlickrWhy is it, that in an age where the value of a company is no longer based on assets or staff numbers, but on ideas – that architects still charge by the hour?

Once upon a time, the value of a company and the number of staff it employed had some correlation, but today this is no longer the case. In 1979, GM employed 853,000 people and had a turnover of $66 billion, today Google turns over a similar amount but with only 60,000 people.  The stories for Microsoft, Apple, Facebook and many other companies are the same.  Making money is no longer tethered to staff and hours.

In architecture, interior design and engineering however, hourly rates are still the norm. “When they choose to strike out on their own, architects tend to follow the outdated model of trading hours for dollars. One of the consequences of this mindset is the fact that clients continue to perceive architectural services as a cost rather than a value.” (Quote from Architizer) Even if, as is commonly the case, a lump sum fee is being generated, this is usually based upon hourly charge out rates of staff multiplied by a guess (educated or otherwise) as to how many hours a task will take. (I’ve written about traditional fee methods previously here) Clients commonly expect a detailed breakdown of the number of hours allocated to each staff member across different project phases. Why are we charging this way when it both limits our ability to increase profit as well as our flexibility in how we deliver services? If I can reduce my hours either by the selection of staff or by automating part of the process, shouldn’t I as the business owner be able to chose if I pass this saving onto my customers (clients) or if I achieve a higher margin? Why is is that clients seem to think that architects and designers are trying to rip them off with higher margins.  Architectural margins are  very low, and in some sectors fees have effectively shrunk over the last 15 years.  We need to make money where we can in order to stay in business.

Obviously at some point there is a minimum fee a company with employees has to charge in order to pay costs, overheads and salaries – although perhaps salaries also need not reflect hours. If architects don’t charge by the hour, what could the alternatives be?

Charging by  the deliverable

In some senses we already charge by deliverable – the lump sum fee essentially considers the building to be the deliverable. While it’s important we don’t lose sight of this fact, the truth is that not every building requires the same amount of work. A great article on this topic is the story of 3 bike sheds by Dimase Architects  which clearly explains that architectural services are not just about building types or construction budgets but about desired outcomes.

Outside if the residential sector, it is also very common for client organisations to dictate deliverables, meeting schedules, required reviews and documentation standards. Frequently these requirements have very little to do with delivery of the building, but are to meet the client’s managers or user group expectations. Sometimes they come with extensive time and cost impacts. How do we charge for a video walk through? The hours in producing the video itself might be very low, but should the cost of software licenses necessarily be considered an office overhead if only used on some projects? Maybe only 1 or 2 people in the office are capable of this work. Should the fee structure for this work take these factors into account?  This leads to the idea of value based fees.

Value based fees

How valuable is your service to your client?  This is a concept I find really interesting, the idea that you change a client based upon the value they place on your services or even the value you create for them. A residential complex is the most obvious example, if you can design to fit in an extra apartment, the developer client makes additional profit, so why should the architect not benefit from this via some kind of bonus? Some would suggest that the architect might compromise design quality at the expense of profit, but I’d say if you are working for a developer – you probably already feel like you are doing this but not getting paid anything for it. In some ways this would be align the architects and the developers interests better.  Most architects would still value good design and their own names and developers would realise that at the point when the architect said no more apartments would fit, they really had reached the sensible limit.

I can see how this kind of fee structure could apply to many kinds of development – car parks, childcare centres or nett lettable area of office buildings. The challenge would be how to apply value to the more difficult to measure or immeasurables like productivity in an office or the positives such as mental wellbeing coming out of good quality design.

I can also see the potential that this fee structure could perhaps backfire – some clients would only want to pay based upon achieving targets or would impose fee penalties for not meeting targets.  But possibly they are the types of clients who already try to get free work or push fees down that we would all rather not work for anyway!

Architect as developer

If you search the Internet for blogs about architect entrepreneurs, the architect as developer is the most common model. Instead of working for the developers, why not become one yourself? So far, the examples I have seen generally relate to small to medium scale residential developments or small commercial premises (you can find lots of examples at Archipreneur). It’s certainly true that the profit margins are higher in development than architecture, although the risks are obviously greater too. However, this model will only ever work for certain project types.

A similar model that has recently emerged is architect as one investor rather than as developer.  This model seems to be emerging in non-traditional development sectors such as The Commons in Melbourne or SWARM in the UK. What both these two initiatives have in common, is the idea of quality development for the good of the community.  Again, this is a potentially higher risk model than traditional architectural practice, but could allow architects interested in working on projects with a social conscience a lot more scope for both work and potential income.  Again, this model won’t apply to projects where there is no development to invest in (eg an educational facility or a client workspace).

Creating proprietary products

Architects often create designs as part of their commissions, they may work with suppliers for one off custom elements to be incorporated into the project.  Very few architects get paid for this.  Apparently Renzo Piano does.  He was involved in developing a new glass louvre system developed for Aurora Place in Sydney and now he gets paid when the product is used on other projects.

So what about our salaries?

One of the things that any model of fees has to take into account is how we pay ourselves and our staff. If our project fees are no longer based upon hourly rates, should the way architects are employed and paid also change? The idea of the gig based economy, where freelancers sign up for a set fee to a specific project (similar to a movie production) is often mentioned in the context of architecture and the economy of the future more generally. Whilst I can see that this could work for larger projects where architects may be involved for 2 years or more, would it be as well suited to smaller projects which may only run for a few months and frequently don’t require full time involvement? Perhaps this is only my current bias or perception, as the idea of piecemeal freelance work continues to grow more common for projects and tasks both large and small, and as technology and co-working allow different options for working together maybe this will be feasible. If we do move towards this model, payment structures would need change, likely increasing to assume that people don’t always have a forty hour work week. An industry structured this way could be a good or bad thing – potentially better work-life balance through time off between projects but potentially more stress about where the next job is coming from.

Maybe our employment structures don’t need to change all that much.  The idea of bonuses or profit sharing isn’t a common one in architecture and interior design but there is no reason this couldn’t be change very easily.

There are a lot of other ways that architects and designers are making money through non-traditional structures, but many of these are quite limited in their applications or potential to earn – for example internet competitions, although the guy who runs the site probably does quite well from it.  But this takes us into non-traditional services, offering services for other architects and designers, which is becoming relatively common on the web (examples include ArchSmarter and EntreArchitect).

I’d like to think there will be a viable model for fees for designing buildings and interiors for other people and organisations, which recognises and pays for the value of design.  We have to remember that“Concept design is not a loss leader. It is our most precious commodity.”  Design is what our clients value us for, and its not something that can be calculated by the hour.

I’d love to hear from anyone working with non-traditional fee structures, or with other ideas about how architects and designers can structure their fees.  Has anyone worked on a value based fee project?  Or even a project which included a bonus for the architect?

Ceilidh Higgins

Image Credits: “money” (CC BY-NC-ND 2.0) by fedee P

The early bird catches the worm? When to engage engineers

Posted on by
Reply
Breakfast by Ron Wooten, on FlickrWorking as a collaborative team with project managers, engineers and other consultants as well as the client is a topic I have written about or touched on in many of my previous posts.  Some of my earliest posts on this blog were about working together with engineers, starting with this post on Collaborating with Engineers.

Earlier this year, after coming across this post, sourcable.net asked me to comment on why engineers should be involved early in projects.  “I think early engagement with engineers allows you to explore a lot more possibilities and solutions and not be constrained so much”.  As well as discussing the benefits of early engagement of engineers, this article also discuss the barriers to doing so. To read the full article on sourceable.net click here.

And I should also mention – when I refer to sharing drawings…of course I also mean to include models! Really I should have said sharing design information, which is what really working as a collaborative team is about.

When do you engage with engineers?  What stops you doing so earlier? Do engineers want to be involved early, or would you rather wait until the architect has ‘finished designing’? (Now there is a topic for another day!) Do you see benefits to sharing more information across the consultant team?

Ceilidh Higgins

Image Credits: “Breakfast” (CC BY-SA 2.0) by  Ron Wooten 

Are you an architect if you don’t draw? Is a design manager still an architect?

Posted on by
3

7597713652_c246737d9c_oAre you an architect? Do you draw?  In the sense I’m referring to that question today, it is usually meant to include modelling as well, and usually means more than just mark up or do a quick napkin sketch. Are you still an architect if your day job doesn’t involve drawing? What does an architect actually do day to day if they don’t draw? Today, the tasks that an architect do can be so broad, that many architects don’t even seem to understand what other architects they work with actually do. If we don’t understand what our colleagues are actually doing, then is it any surprise that many of our clients don’t really understand (or value) all the tasks that go into creating a building project.

I’ll start by saying, technically, I’m not an architect (although I do still draw depending on workload and projects). The reason I’m not an architect is very much a technicality, and whilst its not about drawing, I think it is relevant to the way in which the profession seems confused about itself and what architects actually do. I studied architecture for 6 years, have worked in the industry for 15 and I have even sat for and passed the Board of Architecture exams. However, I don’t pay the annual registration fee to the board, so that means I’m not an architect. (That’s my choice though, as I work as an interior designer – the relationship between designers and architects being a story for perhaps another post sometime). In Australia, anyone who not passed the exam and registered is not supposed to call themselves an architect, but a graduate of architecture, even if they have been practicing for 30 years.  It’s not this kind of semantics or industry protection that I’m really wanting to talk about today (though personally I don’t think architects really benefit from the protection if the term), it’s the tasks we actually do to deliver our projects. And can often apply just as much to other building design disciplines such as interior design and engineering too.

For any architect (or graduate of architecture) or interior designer that works in an office of more than a few people,  you won’t do everything yourself. Some people will undertake business development and bring in the work, some will have face to face client roles, some will draw, some will use BIM, some will know all the graphic software, some will write specifications, some will be good at the overarching idea, some will be focussing on construction and technical detailing, and someone needs to ensure that the subconsultants are briefed, the team is delivering on time and the team size and mix is the right one.  Most of us do a mix of these things, very few of us are good at all of them. The whole point of working in a team (to me anyway) is to benefit from these different mixes of skills.

Given that delivering a building project is therefore very much a team sport of many different positions, it therefore surprises me then when I hear comments like “as architects is job is mostly drawing” or “what are you actually doing on the project – you are not drawing or writing the spec?”  That fact that the later was made by an architect who was managing more than 20 architects (and happened to be involved with the board or architects), is to me, quite disturbing. Do architects really not understand and value what their team mates are up to on the job, thinking that only certain parts of the project are actually important to the architecture?

I guess that partially it is related to the increasing complexity of large construction projects. When I first graduated a bit over 10 years ago, we didn’t have sustainability consultants, access consultants or BIM managers – every project our consultant teams seem to grow ever larger. (Recently I saw a consultant team list which included a wind consultant – a new one to me).  Managing all of these people, briefing them and coordinating their work is a big job on its own. You can then add the work often involved in meeting client stakeholder management and reporting processes, quality assurance processes and code compliance checking (which whilst we have consultants is still so much the responsibility of the designer be they architect, interior designer or engineer). Between all these tasks n a larger project you easily have a full time role, commonly referred to as design manager.

It is really important that this is understood as a different role to the project manager – whilst one person may do both, just because there is a project manager doesn’t mean you don’t need someone undertaking the tasks of design manger. In fact, sometimes it can become even more critical to  ensure that these tasks are actually undertaken and don’t fall through the cracks when the independent project manager consultant is the lead consultant. They won’t generally do your  co-ordination checks for you. Whilst a project manager ifs often at arms length from the actual design and documentation, and may have very different qualifications and skills to the architect – to me, the true design manager needs to understand what is being designed – they need to be an architect (or a designer or engineer depending on the project/design team being managed). However, there seem to be a lot of architects and designers who don’t understand that this role is very much a valuable and necessary one (whatever it is called), and, if the project team is structured well, not just another layer of management.

If I told an architect who sat at the computer all day writing specifications that they weren’t an architect because they couldn’t manage a 20 person team to deliver a multi million dollar project they would scoff at me. Same thing if I told the autoCAD technical detailer she wasn’t an architect because she didn’t use BIM (and had no interest in learning or even understanding why you would use it). But many these kinds of team members seem to think its ok to put down the work of those managing the projects (or even those brining in the work) as not being real architects because they don’t draw.

One of the funny things to me in all of this, is that in Australia, the registration exams actually focus on these management and practice management tasks – not on design, drawing, technical detailing or specifications. This knowledge is taken as assumed (through your studies and your log book of experience) – neither the written exam or the interview deal with these topics. So maybe it’s the opposite – real architects don’t draw? (But of course in my world they are all expected to use BIM!)

Image Credits: Mennonite Church USA Archives via Flickr

It is mandatory that external walls are waterproof: What do client design guidelines, specifications and requests for tender have in common?

Posted on by
8
Red boat - Venice by MorBCN, on FlickrSeriously I am not joking – this sentence came out of a client design guideline document. I am a little worried about the standard of their existing building given that they feel the need to write this out for their future architects to read. Surely for any building waterproof external walls is a pretty basic design expectation? The client shouldn’t have to ask for it. If the walls aren’t waterproof I’d say its a pretty big mistake, I’m pretty sure it’s negligent either on the part of the architect or the builder – so why write it down? It’s also pretty unlikely that it was deliberately designed that way, so putting it into a design guideline isn’t going to fix it. All it does is create work for someone to write it (the client organisation probably paid an architect to write this down) and more work for their next architect to read it. And whilst we all want more work,I think as architects and designers we would rather our clients were paying for something of value – for example our design skills – than this kind of bureaucratic process that wastes everyones time and in the end achieves nothing.

Originally when I started thinking about this post I was only thinking about client design guidelines, but then I realised that a similar problem exists with the specifications we write for builders, the briefs we or our clients write and request for tender or proposal documents written by our clients. We all spend a lot of time writing down things that are obvious, standard practice or a stautory requirement. How often have you read any one of the above documents that says the building has to comply with the BCA (Building Cde of Australia)? Doh – of course it does (assuming its in Australia!). What is much more important or relevant is specific details of how this building needs to comply – such as the levels of fire rating required. But that’s not defined. It’s left up to the project team to resolve – no problem, but they would have done that anyway without being told the building had to comply with the BCA.

All of these documents are often necessary and valuable documents for communication between parties in a construction project – but frequently seem to provide no value – just waste everybodies time.

In looking at client design guidelines what I like to see is actual requirements and details. For me, dealing mostly with interior design guidelines, I find that usually finishes, furniture and signage requirements are reasonably well defined, not surprising, as this is the look and feel as well as interchangeability of components – one of the main reasons for a large client organisation to have design guidelines in the first place. However, even with these items, often you start to get into the finer detail and things like materials or construction are not so well defined – is that Parchment white laminate table on 25 or 33mm thick board. And the thing is, if a client has gone to the trouble of having a design guideline more than likely they care about this level of detail, so then I have to ask what seems like a million questions.

It tends to get even more poorly defined when it comes to construction of fitout – partitions, doors, door hardware. Again, it seems misty definitions are typical. If you have a standard expectation for how partitions are constructed to achieve a certain level for acoustics – how about instead of referencing the Australian standard you just give me the details? That way you will save yourself getting a different acoustic engineer to give you advice on the same partition construction over and over again.

For some reason building services often seem to be a little better defined, but maybe this is because I’m not getting into the detail of it, and its a similar situation to the furniture. Perhaps some of my readers out there want to comment on this?

The problem seems to be that clients want to have design guidelines but they don’t want to take on any of the risk or liability for the design. They want to tell the consultant architect or designer what to do, but not to tell them too exactly, because then it somehow seems like the architect or designer has some kind of choice or responsibility. This is a ridiculous situation, wasting everyone’s time and money (and one I wonder which would stand up in court if tested anyway). If you as client have certain requirements or ways of doing things that have worked in the past – just tell your architects or designers – and if you do it the same way all the time, have someone write it down.

Moving to the other side though, we architects can be just as bad when it comes to specifications. I usually use Natspec (an Australian standard specification package) to put together my specifications. I want to point out that none of my comments are specific against Natspec but apply to the industry and the way we have come to write specifications generally. To me, specifications basically come into 4 parts – schedules/items of stuff that go into the building, installation methods, standards and submission requirements. So – the stuff that makes up the building, that’s pretty critical, if we don’t specify that we will have a problem. Now how to install it – is that our job or the builders job? And what’s the point of writing ‘install to manufacturers specifications’, that’s pretty obvious? Or even more stupidly why copy out the manufacturers specifications and standard details? As for standards – why do we need to reference them? Shouldn’t it be expected that glazing will comply with AS1288 as that’s the standard that is applicable? As for witness points and submissions, we frequently request loads of items that no one might ever look at. That is, until something goes wrong. And that is the point of most of the specification, it seems to be there for when something goes wrong and isn’t done properly – on many jobs I bet its not ever even read by anyone on the contractor team. It’s a shame we put so much time into something that’s almost just in case.

So what can we do to change all of this? Part of the problem is that our industry, so frequently all of the parties are separated by contracts which seem to actually prevent people from working together to sort things out and do things better, and everyone is trying to pass risk onwards down the chain. Outside of individual projects, when do clients, architects, engineers and contractors actually talk to each other about how to improve the way we work and construction industry productivity? Not so much in terms of making money – but in terms of all of us working smarter. Not very often.

One of the few times I see consultants, clients and contractors together is in the BIM space – although there is still not enough participation across all levels and sectors of the industry – and the lack of collaboration across the industry is has been one of the hinderances to BIM uptake to date. By coincidence, at the same time as I was thinking and writing on this topic, I received an invitation to be part of one of the Collaborate ANZ working groups on Level of Detail – now while Level of Detail might be a BIM issue (read a good explanation at Practical BIM) – in the end, it comes down to the same things I’ve been talking about in this post – making sure that the right information is shared across the industry and across projects with the people who need it at the time they need it. Whilst Collaborate ANZ is BIM focussed, most of the people involved are passionate about improving collaboration and communication across the industry as a whole. If we can get people talking about collaboration on BIM, and if BIM becomes a standard tool across the industry and starts to cover things like client guidelines and specifications – hopefully this will start to solve some of the problems across the industry. If my client could give me a full BIM package – template and families – maybe I wouldn’t have to read through all the irrelevant wordy guidelines and maybe my BIM model could go to the contractor with all the information they needed, but nothing extraneous included – and that could be our documentation. No specifications, no design guidelines. (It still doesn’t solve the problem of requests for tender though does it?)

However maybe I am being too optimistic here? What do you think – how can we streamline the way we work and reduce unnecessary documentation? What are the strangest design guidelines or specification requirements you have seen? Or should things stay as they are – are these kinds of documents generating work for architects and designers?

Image Credits:
Creative Commons Attribution-Noncommercial-Share Alike 2.0 Generic License by MorBCN

What’s in a Room: Room Data Sheets and the briefing process

Posted on by
6

DollhouseA room can be considered the container for interior design. The elements of an interior – walls, flooring, joinery, furniture, services, lighting, graphics and signage all belong to a room or a space. In the briefing process, room data sheets are the container for information about the room or space. Particularly for more complex architectural and interior design projects, room data sheets have long been a key part of the briefing process. I am a firm believer in a rigorous briefing process, and have long used room data sheets as a part of this process for all but the most simple of projects. Lately I’ve been thinking about how this process can be improved – both from an efficiency and automation point of view through the use of BIM tools, but also if room data sheets are in fact the best tool for capturing and communicating this information.

Within an architectural or interiors office you can frequently find a whole array of room data sheets depending on project types and client requirements. They may be in Word or Excel, or even occasionally Access. For larger projects there are a range of softwares such as Codebook, dRofus, Building One and the like dedicated to this space planning and briefing process. The dedicated software systems have extensive integration with BIM software such as Revit and ArchiCAD, but tend to be expensive and complex requiring dedicated staff and training. For this reason they are infrequently used for anything but the largest projects. However, for any size of project there would be obvious benefits in having some level of link between the room data sheets and the BIM model. Currently much information is entered (at least twice) – once into the room data sheet and then again into the model. As a simple example, room names and room numbers. If this kind of information could be linked, immediately time is being saved and the potential for errors is being reduced. An ideal use for BIM.

One on the interesting things I found when I first started to discuss the concept of room data sheets with BIM managers was that (depending on their background) many saw a room data sheet as being a document which listed everything in the model. However this isn’t the purpose of the room data sheet. The room data sheet is a briefing tool. The room data sheet is the document which records what has been agreed with the client. It is a work in progress throughout the early design phases, but at some point, the room data sheet is signed off by the client and frozen and becomes the final brief for all interior disciplines. The aim is that at 100% documentation completion the model contents will match the room data sheet contents. One of the biggest potential benefits of being able to link the room data sheet and the revit model is the ability to check for discrepancies. One of the challenges to checking for discrepancies is that the room data sheet, by its very nature, as a briefing document, will have a lesser level of information and development than the model. For example the room data sheet is not the place where colour schemes are usually proposed, although material types will be. So for example we need to check that the room designated in the room data sheet to have resilient flooring has some kind of vinyl or linoleum in the model – not a particular material type.

At the same time as I have been considering these technological and software issues, I was also wondering if room data sheets were in fact the best method for communicating with clients and the design team. The point of the room data sheet is to transfer information between the architect or interior designer to the client and then back to the wider consultant team. The problem is that you hand a client a stack of 50 room data sheets and ask them to review all the details and (unsurprisingly) many do slightly freak out at how much work they have to do to review all of this. It is also hard for people whose brains don’t seem to cope well with picking up small discrepancies and errors in a pile of data presented in this format (and I admit to being one of them myself). Whilst many clients have trouble reading plans, I find there are just as many who find the visual communication of the plan more effective than the numeric/data format room data sheet.

Another issue is that as rooms or spaces become larger and more flexible with multiple zones or activities taking place within a space, does a room data sheet work anymore? Is a room data sheet going to function for a whole or even half a floor dedicated to activity based working? The amount of information on the sheet and the level of uncertainty about where within the floor an object is required means that it is probably not going to work very well. I think the room data sheet has to become an activity data sheet, but I’m not quite sure yet entirely how this would differ from a room data sheet. Much of the information would be the same, but somehow it seems more flexibility might be required.

The risk with room data sheets is that such a process can sometimes be too regimented. Its not so difficult for a laboratory or a hospital room where the room contents are more rigidly fixed by the functions and understood by both client and designer. But in a fast tracked project or more design oriented projects, it can be hard to manage the process of sufficiently developing the design to the level needed for the client sign off on the room data sheets. At what point in the office fitout design is it determined that reception will have a lounge versus armchairs versus an ottoman. Is that level of detail to be included in the room data sheet? If its not it means that the client hasn’t signed off on the idea, but if it is some detailed decisions may be locked in too early compared to other parts of the design process. I have to say I don’t feel like I have the answer to this problem.

Anyway, over several months of thinking about these issues and discussing with colleagues, I decided that I would set myself a deadline for my exploration of the automation of room data sheets – I submitted a talk for Revit Technology Conference on this subject, What’s in a Room: Revit Models,Room Data Sheets and Interiors. You can download it here.

What’s in a Room? from Ceilidh Higgins

At the same time as looking at the linking of room data sheets to a BIM model, I explored how I could use this data in more visual ways, displaying room data via coloured floor plans. At this point, it would be quite an efficient process to be able to produce both plans and room data sheets as required depending on the project stage and client requirements. Its also probably a useful workflow for design and construct projects where full detailed documentation is not being produced by the architect. The process is pretty simple using Revit, BIMLink and Excel to create a bi-directional link between excel room data and the Revit model.

The outcome is that the workflow demonstrated in this presentation is a very practical one for the many projects that currently use room data sheets and a BIM model. Whilst its not a perfect solution to integration, there are many efficiency and accuracy gains. I don’t think I’ve come up with the perfect alternative to room data sheets though, and certainly haven’t solved the problem of managing more open design problems or larger activity based spaces.

I have added an extract from the slideshare presentation with a  room data sheet example after a request in the comments.

Do you use room data sheets? Do they work as part of your design process or do you think there is a better way? Would you like to integrate your room data sheets and your BIM process?

P.S. I’ve started work full time again after enjoying a long sabbatical. I’m at Daryl Jackson Robin Dyke Architects. The Midnight Lunch will continue, but posts may be a little less frequent than before.

Image Credits: Original colour image by

Is your architecture or design client value for money?

Posted on by
Reply

Money by Philip Taylor PT, on FlickrLast week I started a discussion on how the client and their expectations impacts on the cost of design. Whilst there was some hope expressed on linkedin about this next post offering solutions…I’m not really sure I’ve got the answers. As I was originally writing this blog, I found that as I wrote I was moving more and more towards discussion of another contentious topic – competitive tendering. So today, while I continue pondering the impact of the client, this has segwayed into a consideration of the problems of competing tendering.

Often the project brief (or lack thereof) is the beginning of the problem. Whilst developing the brief can be part of the architect or interior designers scope, if it is teamed with unreasonable contract conditions or unreasonable interpretations by the client, significant additional work can be required. I have encountered contracts which expressly forbid the designer from claiming variations due to a prolonged program, limiting the number of meetings or site inspections or from an increased project value. This, to me is incredibly unfair on the part of the client. When the brief is little more than this – design a 5,000m2 fitout in a new building of 5 storeys to accommodate 400 staff in a mix of open plan and enclosed offices with support facilities. To me, the program and budget are key considerations in my scope, the scope is not just the final construction documents. Whilst it is true that the architect or interior designer could increase the construction cost due to design decisions, it is equally true that the client could increase construction costs and the amount of detailed design and documentation required due to their decisions on a higher level of acoustics or particularly extensive and complex joinery requirements as examples. I guess the decision has to be made at the fee proposal stage – do I take this risk of bidding on an very undefined scope and how do I (if possible) cost this into my structure. If the client then gets unreasonable in assessing variation claims, this is a recipe for cost overruns. In the end this kind of client should suffer with reduced quality for their project, but often they don’t, because we as designers still want to do a good job and keep the client happy. And our companies can often somehow think they will be able to make the money back on the next job, but in my experience its hard to make this work if you are dealing with clients who require competitive tendering on every job.

At the other end of the scale I have seen very detailed briefs, which (I thought) set out the clients full expectations of activities and deliverables. I responded to this detailed scope, pricing accordingly. We were even shortlisted for a tender interview. However, it turned out the client was interviewing all the tenderers (there were 3-5 selected tenderers) because there was such a large difference in the fee values (I think it was something like 200%) and they wanted to ask further questions of each party. I thought the interview went very well, but then we didn’t get the job. When we asked for a debrief, we were informed that we were offering a ‘blue ribbon’ service and that the client couldn’t afford this. So apparently the project had gone to someone with a much lesser level of services than they had put the tender out for, and a matching lower price. So much for fair tendering processes. If they didn’t want our ‘blue ribbon’ services, we should have been given the opportunity to price the same as the other company – or perhaps if they weren’t fixed on the services but on the outcome (eg the fitout) then they shouldn’t have specified all the detailed meetings, reports and the like in the tender. Very frustrating.

Although the tender process makes these things worse, even with more involvement with a potential client up front there is still no telling. Just like a job interview, it is a pretty brief time you spend with someone, where both parties are on their best behaviour. Later when things start to get even a little bit difficult or go wrong it could be a different story. Or it could be that the people change, or additional people get involved in the project. Having a user group that violently disagrees with the project manger/property person responsible for delivering the project can be a challenging process to work through for both the architect or interior designer and the client representative.

The most time consuming client I ever had, was one who used to pop into the office every single day for weeks at a time. She had decided to personally take charge of the colours and finishes. Whilst I wasn’t happy with that, the client organisation had agreed she would do this (I think that people thought it would reduce our workload! Little did they know…) If I told reception I wasn’t available she started to ask for the other project team members. She would then ask to come in and look at the samples library – but she wouldn’t just be doing this quietly on her own, the whole time she would be asking the opinion of whoever had let her into the office and they couldn’t get back to their own work. At the end of the project she sent back a removalist size carton of samples. We did actually end up charging the client extra fees, and thankfully in this case, the organisation was reasonable and recognised the additional work we had incurred due to the behavior of their staff member.

For me the problems is that these different client attitudes have costs attached and this time can also impact upon the project program. We have planned the project process based upon certain time periods, and its not always a simple matter of throwing extra resources against the project when the client requirements expand the time required. So how do we as an industry change this? We can’t always work for repeat clients that we know and understand, where we can somewhat predict their behaviours and expectations at the fee proposal stage. Particularly when it comes to competitive tendering we don’t have the opportunity to get to know the client. Or if we do know them, we might overprice the job or the opposite, we can win the job by offering a lesser level of service than the tender calls for. In my view, we as an industry need to take some responsibility for this. Architects and interior designers need to be less hesitant about defining scope and claiming variations. All architects and interior designers need to take responsibility for this, as often client attitudes are determined by the other architects/consultants they have worked with in the past. We need to educate our clients. But I also think that large client organisations, who purchase architectural and design services frequently also need to take responsibility. In particular, in Australia, government at all levels is a large user of architectural services, generally uses competitive tendering processes and frequently promotes one sided contracts. Clients need to understand their roles in the process and what has been allowed for in the fees. The staff involved need further support and education. Value for money does not mean cheapest. The conditions at tendering stage need to suit the actual project expectations. Client organisations need to judge project management success on more than just keeping consultant fees down.

If one of our largest clients (as an industry) treats architects and interior designers as not worth being treated as professionals with a high level of skills and value, what does that say about our profession? What is your experience – do you think competitive tendering offers the client the best outcomes? Do your clients understand that program or meeting attendance is part of the scope and can impact on your fees? What kinds of additional services have your clients expected without changes to your fees?

Image Credits:
Creative Commons Attribution 2.0 Generic License  by  Philip Taylor PT 

How many architects or interior designers does it take to design a building (or fitout)?

Posted on by
3

Light bulbs No, that’s not the start of a joke comparing architects versus interior designers. And it’s just as applicable to engineers too. The question is really how do we determine how many hours it will take to design a particular project? I’m back to what seems to be one of my readers favourite subjects again – design fees. Last week a comment on my post on BIM-onimics queried the number of hours spent on some of the example projects. This question put me in mind of a number of issues I’d been meaning to blog about one day – the main one being how do you cost the client themselves into your design fees? To me this is often more difficult than the already difficult task of putting a number of hours on creativity.  However the more I started to think and write on the subject, the more it has expanded, and so this will be a 2 part post.

As I mentioned in my response to the comment on the number of hours a project takes, and I’ve discussed previously (in my post What makes a great workplace design client) clients come in many forms. I find particularly in the areas I of design I have worked in (workplace, healthcare, labs), the client group expects to be (and in my view quite rightly is) part of the design process. But that said, different clients at both the organizational and the individual level have very diverse views about what their role is, what their architect or interior designers role is, what deliverables should be provided, how many review points they should have, how frequently we should meet and generally how much involvement they will have in the design (and even construction process). The client’s level of industry knowledge and familiarity with the design and construction process also differs. All of these factors will impact on the amount of time I spend working on a project – not necessarily designing, but managing the client inputs, reviews and approvals, answering their questions and producing documents which are specifically for their use and not a requirement for construction.

I don’t necessarily mind doing any of these things. The problem is that if I don’t know the client (and by this I mean both the organisation and the individual) at the fee proposal stage then gauging what kind of client they are and what their expectations might be can be exceedingly difficult, and in some cases downright impossible. If you’re lucky you have a client who is only seeking proposals from  a small number of your competitors (or even better you are single select) and they may meet with you once or twice to discuss the project. You have a chance to speak directly with them to clarify the scope and their expectations. It may even be likely that if there was an obvious difference in scope between the proposals the client would come back to you to discuss this. Unfortunately, in my experience this has not been the norm. Maybe in some sectors and firms it is, which is great (give me a call, I’d love to come work with you!). Particularly when dealing with government or large institutions or organisations, competitive tendering becomes a more usual approach.

Even on an invited or short listed tender with a limited number of companies it is unlikely that there will be any significant interaction between the designers and the client representatives. Whilst a site inspection may be held, this usually involves all tenderers and doesn’t really provide an opportunity for the designer to get to know the client. The first time this is likely to occur is after you have submitted your fee, at a tender interview. Indeed for some larger open tenders, there is never even the opportunity for the architect or designer to speak to the client. The only means of contact may be via an anonymous procurement email address, with the whole tender process run by a different individual than the person who will be the client representative.

Especially when the person who becomes the client representative in the design stage has had very little involvement in procurement their expectations can differ markedly from what is documented in the tender and project brief. Individuals can have very different views over what constitutes a review or approval and how the design should progress. With some of my clients I know that if we have a meeting and I present some preliminary design options, I will get instant feedback and go away straight after the meeting to revise and develop the design. However with others, the decision makers are not in the room or further people need to be consulted, I will be lucky if I get feedback and direction 1 week later. These two scenarios affect my resource planning and my project costs. Design is not just dollars per hour, every time I start and stop it costs more. There is also the likelihood that during the time the client is reviewing the schemes they will have more questions, will ask me to explore more options and that overall there will be more meetings and the project will take longer. Now, I can and do try to reduce my exposure to such risks by including a detailed scope and program, limiting the number of meetings and options and other such assumptions within my fee proposal. But still, a number of scenarios have arisen for me in the past where for a wide variety of reasons other issues arise which further complicate the potential project costs or reveal interesting things in relation to the expectations of the client.

Tune in again next week to find out more about some of these issues, a discussion of competitive tendering and my opinions on what needs to happen to help sort out this mess!  In the meantime, feel free to offer your own stories, suggestions and comments.

PS. My TEDx video is now available on line. Click here for the Audience Talks. I’m at around 9 minutes of the way through.

Image Credits:

BIM-onomics: How will BIM change the business of design?

Posted on by
8

Money by Tax Credits, on FlickrDoes BIM cost your design practice more? How does BIM impact your fee proposals? How does BIM impact your business? These were some of the questions I was recently asked to address in a presentation at the Revit Technology Conference held in Auckland.

Partially as a result of my previous blog posts Architecture and Interior Design is a business, isn’t it? And The art (or is that science?) of architecture and interior design fees, I was invited to address the topic of the economic and financial impacts of BIM on a design consultancy – I think due to being among the relatively small group of industry professionals who understand both BIM and the business of design. I convinced another such individual Rodd Perey – committee member of RTC Australasia who had invited me to do this talk – as well as Principal and Group Design Technology Manager at Architectus, to join me in discussion of this topic.

One of the most interesting things about preparing the talk, was that whilst Rodd and I come from very different practice and BIM backgrounds, much of the time we agreed on the issues affecting a design practice who are using BIM by themselves and for their own benefit. We termed this Lone BIM – as opposed to the benefits of using BIM as part of a larger project process in conjunction with clients, sub-consultants and contractors. This Lone BIM, the efficiencies and impacts on practice, and its opportunities for reducing project risks, were the focus of our talk.

I have attached the slide deck to this blog via Slide Share.

BIM-onomics slidedeck from Ceilidh Higgins

As you will see from the slides, one of the repeated messages was that practice directors, principals and anyone costing or managing design projects need to firstly understand what BIM is actually being used and produced in their office and secondly what BIM outputs will be delivered to the client. How can you calculate your fees if you don’t understand your deliverables?

Right now in the industry and even within individual practices BIM can mean different things to different people. It’s important to understand which BIM deliverables and processes are additional services outside traditional services, and which ones can help you improve your efficiency in providing traditional services. To model every part if a building at 1:1 with full operational and facilities data will certainly cost you more than traditional documentation, but is that what the client has actually contracted you to deliver?

We felt that there were a number of key aspects to using Revit (or other BIM software) within your practice that improve your “BIM-onomics”. Aside from understanding what BIM you deliver, you need to leverage the information and automation aspects of the BIM – for example scheduling, keynoting and proper use of materials which allow consistency and automation across the project. Directors and principals need to have some understanding of these concepts so they can question the outputs. However its not all about BIM either – continuous improvement, ongoing training and debriefs are necessary to capture and spread the learnings across your organisation. This needs leadership.

Then we get to really the key thing – BIM impacts all areas of your business delivery model. BIM impacts upon your project workflows, your resources, your programs and your QA. Are these things you are just going to leave to drafters or modellers? You can’t leave your practice to the “revit robots” nor can you buy in the revit “A team” to solve your BIM implementation problems (though it will help). Economically successful BIM relies on the knowledge of your team, the mix of knowledge between software, design, construction and business. Everyone is part of the BIM team. The senior architects and managers may not be on the tools, but need to be able to speak a common language and communicate with someone who can understand both the BIM and the business. Someone needs to direct the BIM process to ensure that over modelling and over servicing is not occurring, a common reason for cost overruns on BIM projects. But one that is more typically related to management practices than the BIM software itself.

BIM will change your project programs. As Rodd pointed out though, that most overused of conference graphics the MacLeamy curve is wrong – what consultant in their right mind would sign up for a process that makes you do the same amount of work earlier in the process, when the client is still most unsure? Both of us agree, that whilst BIM does put some of the workload forward, it will be overall less work – and the project examples we used demonstrated this (the graphs come up later in the slide deck).

Your quality checking procedures also have to change – again this isn’t one for the junior revit modeller in your office is it? But it is another opportunity to leverage your information – you can use BIM to check your BIM. Examples shown include using auotmated drawings to check precast panel details and smoke/fire compartments. The more uses you can find within the BIM itself the more valuable the BIM becomes. The BIM becomes also a risk reduction tool – you get in right during design and spend less time on site, you think things through and solve problems in the design phase. But again senior and experienced project staff need to be part of this process – they need to know what is possible with the BIM, and then they should be asking for it in their own offices.

Both Rodd and I presented a set of comparison projects with an analysis of an AutoCAD project versus a Revit project. Unfortunately it is impossible to ever directly compare 2 projects as every design project has different factors, but we both selected the most similar projects we were able to find. In Rodd’s case, 2 hotel redevelopment projects on the same site for the same client, and in my case 2 office fitouts of a similar size for similar client types. As you can see on the slides Rodd and I examined slightly different project metrics based upon the information we had available. The one metric in common though was the percentage difference between the number of hours and the number of drawing sheets. We both proved the Revit project to be significantly more efficient based on this metric, and amazingly we came up with figures within 5% of each other!

A question from the audience worth repeating here, was how long had the teams been using Revit? For both Revit examples it was between 2-5 years, and it was certainly not a case of having a super BIM team and a crappy AutoCAD team – both myself and Rodd considered the teams also to be comparable. To get a good return on investment isn’t going to be an overnight process.

BIM is a process you need to manage the whole way through your projects – right from fee proposal stage. Its pretty straight forward really…define what you are providing, what others are providing (such as point clouds, parts of models/existing models, BIM standards) and understand what you are costing. If you as the person costing a job don’t understand all the technical aspects, talk to someone in your office who does. Build the understanding between the technical people and the business people – or find people who are able to do so and bridge the gap, becoming the translator and teaching at both ends of the equation.

In conclusion – does the BIM-onomics stack up? If you manage the process, manage the risk and are delivering the same it should cost you less.

Do your BIM-onomics stack up? Do you know by comparing projects? If your BIM is not yet economic, what are the challenges and issues you see as stopping it? If you are a practice director or principal do you know your BIM? If you don’t, do you have someone who can translate for you? Have we missed any factors you consider critical to the economic success of BIM in your practice? Do any of my slides not make sense to you? (if so comment)

You can find my other RTC presentations – What’s in a Room and InforMeDesign on Slideshare.

Image Credits:

. http://taxcredits.net/