« March 2007 | Main | June 2007 »

18 May 2007

The next BIG presentation tool?

A recent online message said "I'm tired of using PowerPoint... what's the next big presentation tool we can use in our industry?"  Here's what I think --

When you prepare an SOQ or a proposal, you demonstrate your technical qualifications to do the work, including the training and experience of your staff and the projects your firm has completed. When you get a letter saying you've made the short list and inviting you to make a presentation, the client is saying "we've decided you're qualified; now we have to figure out if we want to work with you."

Therefore, other than information specifically requested in the short-list letter, the presentation has little to do with technical competence, and everything to do with the "fit" of the personalities of your project team members with the client's relevant staff.

How does the client determine whether this "fit" is good? They put people together in a room and let them interact. They talk with each other. Someone asks questions and someone else answers. People watch each other's body language for the more than half of all communications that is non-verbal in nature. Over the course of the session, the client determines which of the short-listed teams will make for more of a fun experience than any of the others. That's who gets the job.

And PowerPoint pretty much gets in the way of this determination. It's hard for a client to assess who will be great to work with when everyone in the room is looking at the slides on the wall, presenters are speaking "at" the client's staff rather than "with" them, and there is very little real interaction until the Q&A section at the end.

How do I know that the most important thing to the client is the interaction, the relationship, the "fun" quotient? Well, in the last few years, I have seen a number of short-list letters specifically stating that a PowerPoint presentation will not be allowed. Many clients have actually said that the quality of the work experience is as important to them as the quality of the work product.

So much for differentiation based on technical capabilities!

In addition, clients want to hear from the project manager and technical staff, not the principal whom they will rarely see during the actual project. They want their staff to interact with the people who will actually do the work and be in project meetings on a day-to-day basis.

Therefore, the next BIG presentation tool will be HUMAN BEINGS!!

What does this mean for the typical planning and design firm? It means that they have to promote or hire project managers for their management and communication skills, and for their ability to "connect" with the clients.  Firms can no longer afford project managers who think they are simply the most senior designer on the team. As a land development client recently told 175 staff members of a California A/E firm, "if you're designing my project, you're not managing it!"

However, the next big presentation tool will not be just any human beings. It will be those who can stand up in front of a room -- calmly, comfortably -- make eye contact with the listeners, and speak clearly and confidently in a well-modulated voice. These people will not only be experienced speakers, but speakers who have had sufficient rehearsal of the current presentation that they are in control of both the material and the meeting.

For many years, firms have been saying that their employees are their biggest/best asset. This is now more true than ever.

09 May 2007

Be Fair to the Little Guy

A client called last Thursday asking for help with a public agency request for qualifications, starting with a detailed review of the RFQ and a Go/No Go decision. The client had allowed 18 calendar days from RFQ release date to due date, and asked for the following information:

1.  A statement of interest for providing on-call, as-needed A/E services for minor construction, repair and renovation projects, including the prime firm's unique qualifications pertaining to task orders; a statement of availability and commitment of the prime, its principals and professionals to the project; a brief history of the prime firm and each subconsultant; a graphic representation of the team (org chart); and a completed SF254 (later amended to allow a completed SF330).

2.  Information on Historically Underutilized Business (HUB) status -- minority- and women-owned firms -- of the prime and other team member firms.

3.  Information on the prime firm, including name, address, years in business, type of operation, number of employees by skill group, and average revenues for the past 10 years; resumes of key project staff including experience with task ordeers, years with firm and city of residence; proposed assignments and lines of authority/communication for principals and key professional staff (another org chart); identification of members of the proposed team who worked on projects presented in the Experience section; firm financial statements for the past two years; documentation of financial stability; information on potential sale of or acquisitions by the company; details of past or pending litigation; information on any current or previous defaults on loans or financing agreements; and a 5-year claims history under professional malpractice insurance.

4.  The same information as item 3 (above) for each of the subconsultant firms, plus information on how members of other firms would be integrated into the team; resumes of key staff; a graphic description of assignments and lines of communication (more org charts); basis for selection of that firm for the team; prime's process for working with subconsultants and integrating them into the design process.

5.  Prime's past performance on projects for similar facilities within the last 5 years including project name, location, contract delivery method and description; initial and final construction and total task order costs; project size in gross square feet; type of construction; start and finish dates for design; notice to proceed and substantial completion dates for construction; description of the professional services provided; name of project manager and project architect; list of all project consultants. Past performance was to be evaluated based on accuracy and quality of cost estimates; design to and control of program scope within budget during schematic, design development and construction documents phases; effective management and tracking of schedules; provision of accurate, complete and coordinated plans and specifications; effective management of change orders and claims.

6.  Representative projects -- three projects involving similar scopes of services, regardless of facility or client type, including all of the information required in Item 5 above; three projects that won awards for design excellence with descriptive information; color images of all projects described in this section.

7.  An explanation of how the prime intends to make sure any project under this on-call contract will comply with the Facility Master Plan and incorporate the requirements of the client's design standards for the project.

8.  Best practices -- using specific examples from three projects described earlier -- related to quality assurance proceedures; the owner's specific system design and construction standards; the prime's service support philosophy; the types of records, reports, monitoring systems and information management systems the prime uses to manage projects; cost control methods for the design and construction phases; ensuring continuity of project objectives from design solutions, to construction documents, to the actual construction project; assurance of timely completion, including methods for schedule recovery if needed; a section based on a review of the draft agreement stating which services the prime considers a part of Basic Services and which would be considered Additional Services.

9.  Problem identification and resolution -- describe your understanding of the administrative, physical and aesthetic challenges and opportunities and your strategy for resolving these issues; what are the critical issues for task orders; using any three projects described earlier, discuss conflicts with owner, consultants, contractor or subcontractors, and described methods used to resolve the confloicts.

10.  References -- owner's name, representative and phone number; contractor's name, representative and phone number; length of business relationship and background information of project (year of project, summary of services performed, etc.).

Responses were limited to 100 pages plus SF254 or SF330 and HUB documents.

For the average small firm, which probably does not track all of this information, and which certainly does not have any fancy response preparation software, is this not just a bit excessive?

I had to recommend that this was not an appropriate pursuit, even though the client was perfectly suited to undertake and successfully complete the assignments envisioned under the contract. The submittal would require more time (his and mine) than he anticipated because he didn't track the required data in any purposeful, organized form. Every piece of data would have to be researched separately.

If he wanted to make this a strategic client, pursuing multiple projects for them each year, he could spread the development costs over multiple opportunities. However, the actual expense would all fall under the current pursuit, and he would have to come up with a big time commitment and a pay a big fee to develop this first submittal.

I understand that there are numerous systems out there today to track this information, many of which are not that expensive. The data can even be tracked using Word templates or Excel spreadsheets, softwares which everyone already has in their offices.

But many DBE, MBE, WBE, 8(a), DVBE and other small firms do the majority of their projects as a subconsultant and rarely think ahead to the time when they will submit as the prime and need this depth of information.

Wouldn't it be more fair if, when public agencies issue RFQs and RFPs for smaller programs and projects, where they anticipate that smaller firms will compete and win the work, they would cut these small firms some slack and only ask for information that is truly required for selection?