Q2 2014 Flywheel

Summer ‘14: Learn how we integrate Architecture at RQ. 
issue no. 22 | 14
Official newsletter of RQ Construction, LLC.
Flywheel
the
One of the ways of
describing RQ’s mission
of being the first choice
of all stakeholders is that
we strive to maximize
value. Why do I bring
us the concept of value
in this edition of the
Flywheel? Because we
are focused on design.
Did you know that design has the ability to create value?
Yes, design is a value creating activity. It is the activity
that we should take on with incredible seriousness and
respect.
It is because design is (or at least has the ability to be) a
value creating activity that RQ decided it had to be in the
design business. There is a great book called Blue Ocean
Strategy. Construction, by itself, is an activity that largely
lives in the red oceans, where it is full of the blood from
sharks feeding upon each other. However, design/build,
as an integrated activity, allows us to bask in the blue
oceans where no one else is swimming, and life is good.
At RQ we are responsible for projects. It is the reason
that we feel that design and construction go together
like a hand in a glove. Design, without attention to
cost and schedule, wanders into areas that the owner
cannot afford, and is full of negative iteration and waste.
Construction, without the ability to create value that
design does, starts looking like a commodity.
At RQ we have taken the lid off the box. For years that box
has constrained design and construction as independent
activities from being able to achieve the ultimate goal of
delivering projects of better quality, faster, and for less
money. The design department at RQ is incredible, not
just because they design creatively, but because they are
actively designing hand-in-hand with construction.
MESSAGE FROM GEORGE:
MESSAGE FROM GEORGE
INITIATIVES
Architects and Mongoose65 2
Friends of MARSOC 3
PEOPLE
Steve Noel 4-5
Stacy Strand 5-6
John Hoglen 6-7
Ashley Labarre 7-8
Sherri Haviken 8-9
FAMILY NEWS
IN THIS EDITION: Learn How We
Integrate Architecture At RQ
1
Thefutureofprojectdeliveryisinintegratedteamsdriving
out waste in projects, as defined by the people paying
for the project. Our integrated teams of designers and
builders are achieving great things. If I was a competitor
of RQ, I would not be happy with what is happening at
RQ. That makes me happy!
George H. Rogers, III
PRESIDENT & CEO
10
Exciting News > Project Award
> RQ Construction, partnered with Bergelectric, is
pleased to announce that we have been awarded the
design and construction of the Repair and Relocation
of Airfield Lighting at Marine Corps Base Camp
Pendleton. The purpose of this project is to repair by
replacement the existing Airfield Lighting System and
construct a new lighting vault. The contract value is
$4,598,560 and will be completed in June of 2015.

Summer ‘14: Learn how we integrate Architecture at RQ. 
ARCHITECTS AND MONGOOSE65
INITIATIVES
ERIC TAYLOR
We have an awesome design team here at RQ. Probably
because they are so awesome we find ourselves in a
position where we want to take further advantage
of the awesomeness and therefore need to grow the
team. Kathy has been working hard to find candidates
that live up to our standards and has come across some
common resistance that I want to address. Namely, there
are still a lot of architects out there that are skeptical of
“working for a general contractor” (as they put it). Their
phraseology all by itself shows their cards. They believe
RQ is a general contractor that design works for. They
are wrong. Technically they are right, but everyone at RQ
knows saying it that way isn’t really right. Build works
for Design just as much as the other way around. We all
work for each other because we are all RQ.
I understand why many outside architects think the
way they do. I recently googled “general contractor
stereotypes” to see what I could find. Stereotypes, after
all, are stereotypes for a reason. There is an element of
truth behind them, generally, most of the time. It’s most
likely some of these “general contractor stereotypes” that
affect how outside architects view the prospect of joining
a company like RQ. In none of the stories or descriptions
in the long list of google outputs did I read descriptors
like “integrity” or “innovation” as stereotypes of general
contractors. The stereotypes don’t even suggest a group
of people with a passion or pride in their trade. One
story I read seems to sum up the actual stereotypes you
and I have both heard and watched and read about (and
experienced). The author called himself Mongoose65. I
don’t know what that means, but hear his story:
Just venting, but I did a recent remodel (almost finished). Every,
and I mean every one of the contractors involved (many), from
the GC, his many subs, to the painters and railing guy that I
hired personally have at times a) done shoddy work, b) nickel
and dimed me over their mistakes, c) not shown up as planned,
d) not called as planned or did not call to explain not showing
up, e) did not know what the other guy was doing i.e. “that’s
not my job so I just left it unfinished...was I supposed to tell
you? gee, sorry?
It amazes me that there is such a lack of professionalism. Don’t
they realize they have the reputation of being crooks? Don’t
they care. Aren’t they interested in referrals or repeat business?
I am truly speechless at how this has gone and am numb.
Ouch. While this stereotype might act as a deterrent to
outside architects considering RQ to be a great place to
practice their highly technical craft, that stereotype is the
reason I am in construction. I can’t speak for everyone,
but I know our CEO and I are on the same page on
this that we want to change a stereotypically negative
industry. How awesome would that be? The bar isn’t very
high if it means simply doing non-shoddy work, not nickel
and diming clients, showing up as planned, or even just
calling to say we weren’t going to be able to show up. A
single phone call would raise the bar for Mongoose65.
I’ve written before that I work for RQ because of our
mission to be the first choice of all stakeholders. That
is true. And it is consistent with wanting to change a
stereotypically negative industry. To be the first choice of
Mongoose65 might mean just a phone call, but I doubt
that would really do it. At the end of the day, Mongoose65
wants what we all want when we are the customer: we
want a great price. We want great quality. We want great
service and a great experience. We want convenience
and confidence and consistency. Whether we’re buying
a pair of shoes or a 60-story skyscraper, that’s what we
all want. RQ wants to give that to our clients, and to our
subs and sub-consultants, and to each other (those of us
that work here).
I took a stab at this article and that first stab is in my
waste basket. In it I tried to explain how RQ is not so
much a general contractor as we are a design-builder. I
went into detail about the history of design-bid-build up
to the recent growing trend towards design-build, asking
and answering the question why the division between
the Design Team and Build Team caused by the old
design-bid-build delivery method hasn’t advanced with
the times to form more Design AND Build Teams. It is so
obvious that having a GC and Architecture fully married
up and living under the same roof is so advantageous to
design-build delivery that it struck me I was writing about
the wrong thing. Architects and everyone else out there
associated with our line of work already know such a
relationship in Kum-ba-ya-land would be advantageous,
and they certainly don’t need a tutorial on the history of
project delivery methods. Writing about knowledge was
the wrong thing to write about. What keeps architects
away from actively pursuing GCs to fully marry up on
their own has everything to do with Mongoose65 and
those stereotypes we have all experienced.
To those of us at RQ, let’s continue to raise the bar
for Mongoose65 and work towards the fulfillment of
our mission by going pro in our profession. Let’s work
towards becoming the Michael Jordan of superintending;
or the Jerry Rice of estimating; or the Michelle Akers of
project accounting. Let’s become first choice by truly
caring for people and each other and by executing our
work smarter than anyone else with nothing but the
utmost character. To those of you not in RQ (or at least
not yet), do some homework. Test us and see if we live up
to our values. Perhaps RQ will be the quake that sparks
a tidal wave that changes the negative stereotypes of an
industry. And perhaps you will either be a part of that
quake yourself, or part of the tidal wave by heralding that
RQ is a different kind of place. I’ll be keeping tabs on you,
Mongoose65. Our desire for you and our stakeholders is
to see ranting turn into raving!
For examples and testimonials of “how” RQ works to
break stereotypes through the integration of Design AND
Build, please just keep reading and hear from several of
our own people. None of them started their careers at
RQ. All of them have experienced the difference (and
quite frankly are a part of making that difference).

Summer ‘14: Learn how we integrate Architecture at RQ. 
FRIENDS OF MARSOC DAY
INITIATIVES
Several RQers received the collective thank you given RQ
from the MARSOC Foundation by attending MARSOC Day.
The pictures tell the story of the kind of fun had. What
the pictures also suggest is that RQ, as an integrated firm
of designers and estimators and superintendents and
officers and project managers... we have fun together. We
work together and can play together. That’s awesome!
Jason Felton
Shooting Instruction
The Group Prepares for Shooting Aaron Espinoza
Tyler Labelle
Stacy Strand and Josh Osborne

Summer ‘14: Learn how we integrate Architecture at RQ. 
... continued on page 5
that it wouldn’t come easy, but it would be worth it.
Everyone contributed to paving the way to implement
the vision and shape what RQ Design looks like today.
We had the convenience of design, cost estimating and
superintendents (the guys who build the buildings)
around the bid room table making decisions together.
We made mutually agreed upon project decisions that
everyone of the team played a part in defining.
The first year at RQ, it was just me helping secure a few
project awards. Then I added design staff; 2 at first, then 4,
then 6. At one point I believe we were doubling our staff
size every few months. Imagine 6 people in a makeshift
office about the size of Mitch’s office today. That is all we
were for the first few years. We took calculated risks, we
tried new things, we even stepped up one day, bought
REVIT (3D modeling software), opened the box and said,
“Ok, this is the project we will complete in 3D modeling.”
It was a good idea, just not well planned. We learned a
lot, which forced us to innovate at a higher level.
The vision for design was taking shape and RQ design
was settling in. We sat together and shaped RQ’s mission
and vision statements, formalized Design Quality Control
(thank you Shawn Sharareh), prepared the first Goals
and Controls and Department Plans. Learned how to
capitalize on our strengths and build up our weaknesses.
Most of all we taught our builders how to design and
taught them the design process. Our builders responded
by teaching me and my design team how to build and
really who was the boss! They were.
As the co-founder of RQ Design (along with George and
Mitch) I have seen great evolution in people, process and
what both RQ and what the RQ Design department has
become. We continuously grew, changed and innovated
for the purposes swimming in the blue waters and ahead
of our competition. I look forward to seeing what RQ will
grow into in the next 10 years and beyond.
What surprised you about working for a design/build
firm vs. a design house (arch. Firm)?
Nothing. What surprised me more was the traditional
firms I worked for did not have the design/build mindset
that I had.
How has working with the “evil” contractor, given you
appreciation for the design/build process from soup to
nuts (concept to completion)?
You know evil is just live spelled backwards. Seriously,
the evil contractor is part of the business. You always are
working for them. The appreciation I have comes from
the people I get to work with and being on a team that
represents the true “Masterbuilder” and is all inclusive.
Imagine how much better Architects could be at their
profession if they understood estimating and actual costs
or subcontractor management, procurement, scheduling
and job site safety. Ultimately, my appreciation comes
from the opportunity to learn all those aspects of
construction from great people at RQ.
PEOPLE
STEVE NOEL
In the beginning there was
only darkness, then George
Rogers said, “Let there be
light” or “at least an Architect
thatunderstandsdesign/build
and who their client is” and
there was Noel. Then George
said, “This was good.” I am
not proclaiming that George
is divine, but many thanks to
him for what RQ Design has
evolved into today. Thanks
George!
In the years leading up to
the genesis of RQ design, the
government was weary of Architects and Contractors
disagreeing over what was being designed and what
the contracts required. George recognized that the
government needed a solution provider and was tired of
contractorshavingtomanageout-of-housedesignersthat
repeatedly designed outside of the RFP and were more
concerned with what those designers deemed as “good
design” versus fully recognizing the true contractor/
client relationship and the design/build delivery system.
It all started at a lunch meeting back in 2005 – George,
Mitch and I discussed business, culture and past
experiences and realized we shared interests and
common views. Views of what “should be” and “could
be” for both design and construction and creating an
in-house design department at RQ. We discussed Telka
vs. Revit, structural vs. interiors, shop drawings as
design submittals and streamlining design process and
management.
All big ideas and a big vision back then, but long story
short, I was challenged with establishing the in-house
design department here at RQ. Simple right? Land a
few contracts, hire a few people, manage traditional
hard-nosed superintendents, make a profit and make it
sustainable. Easy right? Not so fast….
Think of a time in your life when you walked into
opposition. A little unsure, a little unwelcoming and
perhaps a little bit of apprehension. Maybe it was when
you paddled out into a group of locals at Upper Trestles,
or the time you met “her dad” for the first time, or better
yet the time you dared to show up at a Chargers game
wearing your Raiders jersey.
Are you feeling a bit of what it was like for me as an
Architect showing up at a General Contractor’s (RQ’s)
office for the first day of work? It was that and more. Only
kidding. Everyone at RQ was great from the beginning
and oh what a beginning it was. We took collaboration to
a new level. RQ was very different back then. It needed to
be defined, shaped, refined and reshaped over and over.
Everyone seemed to know we had something special and
DIRECTOR OF ARCHITECTURE

Summer ‘14: Learn how we integrate Architecture at RQ. 
What attracted you to design/build?
Back in the late 80’s, early 90’s (before design/build was
even a trade name and when I had an full head of hair), I
worked for a large east coast General Contractor in their
“design department.” We had Civil and Architectural
design in-house as we did a lot of land development and
large build-to-suit and lease-lease-back development. We
also owned all of the earthmoving equipment, owned
the prime electrical and mechanical subs (and designers)
and performed a good amount of subtrade work in-
house (steel fabrication, doors/frames, hardware, walls
and carpentry). This early career experience provided me
with a deep understanding of a truly integrated team
sharing full exposure, risk and opportunity to design and
construct. No fancy titles, no egos, no lines in the sand.
We were just a team of professionals with like minds for
the fine balance of design and construction and what
was possible when you worked together to deliver each
project as a team.
Do you ever get tired of designing BEQ’s and Hangars?
If not, why not?
Personally, I don’t get hung up on the word “design.”
Each project is unique and represents challenges and
opportunities that outweigh the aspect of what most
people think “design” represents to an Architect. An
Architect might say, “the detailing of those façade
elements fit contextually with the monumental material
that serves to anchor the overall theme and creates a
terminus for the entire campus.”
Wow, too many words! If we unpack all of the supporting
attributes in that statement and apply them to BEQ’s,
Hangars, and Vehicle Maintenance Facilities we begin to
understand that there are myriad interwoven decisions
on each project. Those decisions all serve to formulate a
statement like the one above are the reason why I don’t
get tired of designing those types of buildings. Most
importantly, I get to design facilities for the men and
women who serve this great county to live, work, train and
play. They give us their best, I want to give them RQ’s best.
Why did you get into architecture in the first place?
What makes you stay in architecture?
I just kind of stumbled into it. I started out noodling in high
school, won a few awards in local design competitions
(art work, houses, etc) and thought this is pretty neat,
but I would rather play music. Muddled around in various
jobs, concrete, roofing/siding, framing and lugging boxes
at the local truck dock. All the meanwhile, I taught myself
drafting, AutoCad (v2.6 at the time) and finally decided to
focus on a career in design, engineering or some sort of
construction. From there I went through school, training,
work, education, degrees, licenses and finally paid my
Architectural dues. I probably would not have been so
dedicated to architecture if it hadn’t been for my early
influences and experience with construction and the
“build-side” of the master builder concept. For whatever
reason, I seemed to have an eye for design, and an ability
to visualize all the pieces of the puzzle and articulate it in
a way that makes sense.
The diversity of the experience and the passion for design
and construction. It’s not about the Architecture for me,
it is about the orchestration from start to finish of each
project, the people I get to meet and work with and the
unique challenges each project offers.
Give us 2 truths and 1 fib and make us guess which one
is the fib (people need to find you to learn the answers).
• Turned down an invitation to play guitar in a famous
alternative band.
• Was Valedictorian in college.
• Have been cage diving with Great White Sharks.
PEOPLE
STACY STRAND
What surprised you about
working for a design/
build firm vs. a design
house (arch. Firm)?
I was surprised learning
the sequence and timing
of decisions that are
involved to award the
subcontractor work. In
a typical design office I
assumed the subcontracts
are in place when the
construction bid is
awarded. I assumed all
design decisions could
be executed without considering all other parameters.
Design build affords designers the opportunity to assess
schedule,tradeinput,laboravailabilityandmanufacturers
products. This input gives us a huge opportunity to offer
the best value for the construction bid/budget.
When a process is perfected to ensure the best possible
result it gives me satisfaction that I was a part of it. When
a project is announced, the strategy requires input from
the entire team to analyze all objectives. When the
proposal is executed a quick thinking team is essential.
As the documents are prepared attention to the essential
details is paramount. And finally, during the construction,
being flexible to alternate opportunities and providing
unique solutions with the team is rewarding. It is not
working with the contractor it is contributing to the
process for success.
Early in my career I realized that every building
requires a concept and ingenuity/know-how to execute
construction. Only in the design/build arena could I be
involved in both, drawing insight from the tradesperson
and applying my knowledge of building codes to achieve
DESIGN PROJECT MANAGER
NOEL CONTINUED >

Summer ‘14: Learn how we integrate Architecture at RQ. 
the program and needs of the occupant. Knowing we
have the ability to provide a welcoming and pleasant
environment in a holistic atmosphere is more pleasing to
me (than a singular goal or objective).
If not, why not?
Every project has its own DNA. There are very few
buildings that are identical so how could it be boring?
The journey is the project not the physical result. The
journey is dependent on the cast of actors or probably
better defined as characters. What makes every project
unique is the characters you work with and the team
input that steers the process to the physical result. You
just can’t get tired of that especially when you have the
opportunity to work alongside different ‘characters’ in
the RQC culture!
If you think of a project as a Rubik’s cube, I wanted to
solve the puzzle. It keeps me awake at night and drives my
passion for solutions. I stay in Architecture because I strive
to make my next puzzle solution better than the last.
Tell us one interesting thing about yourself that you’d
want to share with others.
I find building something very therapeutic. I have built
room additions, furniture, and everything in-between.
• I lived in Greece.
• I did the ironman in Hawaii.
• I threw out my back stacking hay bales.
STRAND CONTINUED >
JOHN HOGLEN
PEOPLE
dream homes, amusement parks, and luxury yachts. In
retrospect, I must have imagined an amazingly lucrative
future. Architecture is a very diverse and broad profession
that involves balanced capabilities in problem solving,
technical knowledge, and artistic capability. You have to
balance the way something looks, how the space feels,
what the user needs, while also creating safe, nurturing,
and inspiring environments. I think being able to tie all
of those skills into a single project is a fascinating and
unique challenge each time. Architecture is an incredibly
challenging profession, but also incredibly rewarding,
especially when you can see the users amazement at a
new space created just for them.
I had worked with similar integrated project delivery
models before that created more collaborative
relationships between designers and builders, and it’s
clear that when all the experts have a seat at the table, and
each is given space to do what they do best, the process
is smoother and our clients benefit. The designers and
builders also learn more from each other as decisions are
discussed and debated, so the collaboration is making us
both better with each project.
I think I was most surprised by how similar the design
department is to any outside design firm. I expected to
have to learn a lot of processes unique to construction,
and while there have been many learning opportunities,
it has been very easy to jump right in and contribute as
an architect and designer. Also - surprisingly - my table
tennis skills have improved dramatically.
appreciation for the design/build process from soup
to nuts (concept to completion)? What does RQ do
differently with d/b?
RQ must have chased most of the evil contractors out
of the company before I started here, and even Aaron
Espinoza is more mischievous than evil. Really the design
build collaborative environment that we have developed
here is truly something special, and I think it transcends
the traditional rivalry. For example, in D/B we have the
opportunity to work out specific products or details of
how something will go together (sequencing) in the
field. If we know from the PM or Super when a trade is
coming in to the building and our detail can reflect that
relationship, then you get a tighter coordination. The
more thought you put into it up front, the better the end
result.
Here at RQ, we can design with specific ideas in mind.
Traditional design doesn’t get the opportunity to
understand the process in the same way, because they
usually don’t have the opportunity to design with
sequencing, schedule, and specific material choices in
mind. As soon as you’re given insight from the Ops side,
you can draw it the right way with that purpose in mind.
It’s like allowing both people (design and construction)
SR. DESIGN JOB CAPTAIN
Probably the typical curiosity boys have of what makes
things work… I was always taking things apart, or trying
to figure out what went on behind the walls. I think
that evolved to coming up with my own drawings of

Summer ‘14: Learn how we integrate Architecture at RQ. 
to row in the same direction and we both end up going
much faster! This is accomplished each and every
day while sitting down in meetings, talking over the
phone, or walking down hall to ask a question. You can
experience this coordination multiple times a week and
the end result is excellent!
If not, why not?
The building types that we come across in DOD
construction really are more diverse and unique than
most architects come across in their careers. Just in the
last couple years I have worked on a school, a BEQ, two
armories, an headquarters building, an indoor simulated
marksmanship training facility, and several others. When
you keep in mind the people you are designing these
facilities for, it’s really an honor to be a small part of
crafting safe, effective, and well-designed facilities for
our nations’ true heroes and heroines.
I can boil minute rice in 48 seconds…
• Once upon a time I could swim 100 yards in 57
seconds.
• In my wilder youth I once collected 4 speeding tickets
within a year and my insurance premium actually
went down.
• I was kicked out of the second grade for defiantly
breaking the teacher’s watch, a week later cooler
heads prevailed and I was allowed back.
• While driving a campus bus during college, I earned
the radio nickname “sleeping beauty” for repeatedly
sleeping in and arriving late for an early morning
route.
HOGLEN CONTINUED >
ASHLEY VILLORIA
PEOPLE
Why did you get into
architecture in the first place?
What makes you stay in
architecture?
It all started when I was 11
years old. I would draw floor
plans during class at school,
drawings of my dream homes
(at least 11-yr old dream
homes). One day a teacher
caught me and said, “So you
want to be an Architect?”
And it just stuck. When I
went to college, that’s what I knew I was going to do.
And because I put in so much hard work to become an
architect, that’s one of the main reasons I will stay in
architecture! It’s just the right calling for me and makes
DESIGN JOB CAPTAIN
sense, since I thoroughly enjoy it. There’s not just one
item that I enjoy about architecture. I enjoy it because
it changes and you’re rarely doing the same thing every
day. I love the phases a project can take - design for a
while, then develop design, and then see it built. There
are multiple aspects within architecture and it’s a great
career for me.
Nothing attracted me to design/build when I was school
or even right after school. I had no intention to ever be
a part of the design/build approach. Ever. I was referred
by someone at RQ, and let me tell you, nothing sounded
good about design/build when I was first approached to
join the RQ team. But then, my colleague and I talked
further about the approach and slowly but surely, it
sounded better and better. Plus, add to the fact that RQ
had a good atmosphere and I enjoyed the people that
I met. It certainly took some convincing for me to join
RQ. Never in a million years would I have thought my
architectural career would lead me to the D/B approach,
but it has a been a great journey.
Asking me today, I can’t imagine going back to a
traditional architecture firm. When I worked in just
design firm, it was not collaborative. It was all about
design process. You would find out what the designer
wanted and what the user wanted, but you didn’t get
feedback from construction side. And then during
construction, there was always frustration because
there was no communication beforehand. That’s when
the finger pointing started and someone else had to be
wrong for the issues that were being experienced. It was
not enjoyable process. You’d go through all that work,
have design you love, and then see it built a different
way. It wasn’t quite as satisfying.
So not that I’m a part of a design/build firm, having
the construction and design teams all-in-one make the
process so much more satisfying. You can talk from
the beginning of the project to alleviate that stress of
miscommunication down the road.
Following up to what I said above, having everyone on
the same team is huge. It’s interesting, too, because now
my husband works for design firm who does out-sourced
design/build work. But to see how things work here
at RQ with daily integration between design and build
works so much differently than working with outside
design to accomplish the same goal. At my husband’s
firm, they still deal with traditional design firm mentality
vs. contractor mentality and it sure can cause some stress.
So here at RQ, having everyone in house from get-go and
being able to walk 10 ft to ask someone a question is
so valuable. It doesn’t matter where in the process you
are, start or close to the finish line, that direct line of

Summer ‘14: Learn how we integrate Architecture at RQ. 
VILLORIA CONTINUED >
communication is awesome.
If not, why not?
I personally don’t get tired of designing BEQ’s or Hangars
or other DoD structures. For someone who wants to do
design-type buildings, RQ isn’t for them. But for those
who are interested in the design/build process, then RQ
is a great place to be, nor matter what you’re building.
In my 5 years with RQ, I’ve worked on child development
center, elementary school, several BEQs, hotels, and so
many more types of buildings. There are very few firms
where you can get that type of building typology to work
on in your career.
Anywhere you work on the design side will pigeonhole
you at another firm. Even if I’ve done 3 BEQS in the same
year, they’re all different; the process is all different.
Doing the same building type over and over allows it to
be easier, but the experience is still great. It’s not boring.
It’s never really the same building. Even when I tell people
what I do and they see that I do CMU buildings, I reiterate
to them that the process is so different. I mean who gets
to design top secret wings of buildings? You don’t get to
do that at every firm.
I teach at a studio and perform trapeze, Chinese poles, hand
balancing, and other aerial acrobatics as a side hobby.
• I was the only girl on our high school boys’ varsity
wrestling team for 3 years.
• I am a certified airbrush makeup artist.
• I’m only 5 foot 4.
SHERRI HAVIKEN
Why did you get into
architecture in the first place?
What makes you stay in
architecture?
From a young age, I’ve loved
spaces, volume and art.
Also, with my Dad being a
contractor, I grew up working
in construction. I began
working in the field for my
Dad at 14, swinging a hammer.
Given my background in
construction and my love of
art, use of space and volume,
architecture seemed to be
the logical combination for me. It was just natural and I
never seriously considered doing anything else. I knew I
eventually wanted to pursue large commercial work with
my architecture career. Over the years I’ve worked on a
PEOPLE
EXECUTIVE DIRECTOR OF ARCHITECTURE
wide variety of large commercial and residential projects
from beginning to end. It was fascinating to experience
how everything linked together – project conception
and financing, programming and design, construction
documentation, problem solving, construction – the
expression from concept to the final building completed.
Now that I’ve been in the industry for more than 20 years,
I still love architecture, especially the complexity and
integration of design-build. There is never a limit to what
we can learn or expose ourselves to. It’s just fascinating
-- from design, to constructability reviews, and then to
building something. There is so much teamwork and
synergy that goes with it; it’s why I stay.
My first design-build project was a high rise tower with
a design-build company. The design-build contractor
used us, a separate architectural firm, to work with
their construction team. It was an extremely rewarding
experience – and with such team synergy! …I also saw
how efficient the process can be when you team well
between design and construction. We worked seamlessly
together while obtaining a greater understanding of
each other’s area of expertise. About 10 years later, I
had the chance to work for this same integrated design-
build company (with internal real estate, design and
construction), but this time in-house on their team. I
thought the experience would be similar to how I worked
with them while in an outside architecture firm, but it
was ten times better than what I expected once I got into
it. The synergy, process, speed, efficiency, and fun with
which we delivered projects was amazing. It was fun!
And from that point, I’ve never looked back.
My desire to pursue large commercial work took me to
a new integrated design-build company where we had
real estate development, design, and construction all in-
house. What struck me when I first joined the company
was the level of respect and integration within the
group. Not only did people understand their own areas
of expertise, but they also had a greater understanding
and respect for the expertise of others. That allowed
for in-depth discussions, great design charrettes, quick
pricing and financial evaluations, high quality project
execution/construction, and more. All-in-all, the level
of effectiveness meant it took a fraction of the time it
would take to complete the same work in a traditional
contractor/architecture relationship. With integrated
design-build, you find best value by having all the
key players at the table and no contractual lines (or
competing goals) separating you from transparency or
success. We shared our competitive advantage internally
amongst disciplines/groups, which allowed us to have
the same vision across the whole team, and ultimately,
the whole company.
Now, having been a part of RQ for almost 5 years, I try to
infuse that vision into everything I do on a daily basis in

Summer ‘14: Learn how we integrate Architecture at RQ. 
HAVIKEN CONTINUED >
my own work, and in leading the design department. But
that all begins with breaking down any walls between
disciplines/departments/field first, then developing
transparency, a deeper understanding and mutual
respect. Integration follows. Once the walls have are
down, it allows real learning to occur.
The best way to promote this idea of integration is
through increasing our department expertise through
education and training. Education to know what the
expectations are in design-build, understand what other
departments do and how they contribute to the whole,
and learn whatever you can from the construction/field
teams. There is so much expertise that comes from the
construction/subcontractor/field teams that we try to
capitalize on that knowledge. We formally share lessons
learned in our monthly design department meetings –
it’s really great to see that the team is willing to openly
share the “bumps” in the road so that we may all get
better together…increasing transparency.
Here at RQ, our project sizes have steadily grown in their
size and complexity. By taking the existing group of
designers with smaller project experience and bringing
in more seasoned architects, we’ve been able to tackle
the large projects and form a wonderfully maturing,
collaborative group. With that maturity, we’re able to
provide a higher level of delivery to all stakeholders.
Education should never stop, and to continue that
trajectory, team members with a humble attitude foster
respect and transparency through the entire design-build
process. Reward comes from looking at the larger goal of
the design-build process.
appreciation for the design/build process from soup
to nuts (concept to completion)? What does RQ do
differently with d/b?
Because I’ve grown up in construction, I guess I’ve always
had a great deal of respect for the “evil” contractor. There
are so many overlapping trades that require scheduling,
direction, attention, coordination and clarification – all
“RIGHT NOW!”, that the orchestration of the build portion
of the project is no easy feat. I’ve continued to grow in
my appreciation for our field teams that construct what
we design. We don’t just hand-off the documents when
we’re done designing, but provide support to our field
team members. As an integrated team, working together,
we can accomplish complex, high quality projects that
everyone benefits from.
On a day-to-day basis, I seek integration and growth no
matter what I’m doing. I strive to learn what someone
else is doing outside my discipline of design and that
means learning more about the whole process of d/b.
Practically speaking, this means learning more about
RQ’s buyout process, scheduling, sequencing, bidding,
estimating, scopes, teaming, what responsibilities the
Construction Quality Control Manager has in the field,
how to emphasize safety, how constructability review
and lessons learned inform future projects, small
business requirements, and much more! RQ is very
unique in the opportunity it gives to learn about all of
these things - and this is encouraged at all levels so that
it’s never boring. The more I know, the more I can set
our department processes to be more effective. It takes
meshing with everyone and understanding how to close
the gaps I might have.
And for the future, one way I hope to continue growing
our appreciation for our field teams is by bridging
the relationship of design with the construction QCM
and Superintendents on-site. The vision for further
integration also involves understanding more effectively
how Design PM’s and Construction PM’s work together
to develop a single goal and then swim in their lanes
side-by-side toward that singular goal. We also want to
continue growing our “lessons learned” library. We are
all going to make mistakes, but again, education helps
us by not covering them up, but rather, exposing them,
learning from mistakes, and applying them on the next
project. As our understanding grows, we get better as an
integrated d/b team.
If not, why not?
Many of the projects we do at RQ are not “high”
design projects (with some exceptions). Each project
is so technically and functionally unique, that they are
fascinating! We have the unique opportunity to develop
these buildings while understanding how the spaces
and systems function in the training and support of our
Military. Also, the technical expertise required and the
complexity of codes, regulations, requirements for DoD
projects seems endless. Between that and the rigor of the
government’s process, I never get bored! It keeps you on
toes and forces you to peel away the onion to find still
more layers that you may have never seen before. We’re
always in different project phases and the government
sector moves faster to get into the ground than other
sectors from my past and that’s been very good for me.
Since joining RQ, there’s not been one boring day with
the projects we design and build!
I love power tools. In fact, for Christmas my husband gave
me a compound miter saw. My Dad was a contractor, so
I grew up with them and still have a love for them…and
the smell of sawdust.
When I was 12, I used to chart commodities for my Dad,
like pork bellies and grains. It was like tracking the stock
market, but I did it by hand in those days.
• I was the first off the Cessna plane when skydiving.
• I was first off the 1000 ft. high platform when zip-
lining.
• I was first launched out of the raft while class IV white
water rafting.

Summer ‘14: Learn how we integrate Architecture at RQ. 
FAMILY NEWS:
> Suzanne Parish’s son Russel and his wife Allie were
married on May 10, 2014 in Florida. Congratulations to
the new couple!
> Dominic Asa Hamman was born January 11, 2014 in
Oceanside, CA to Debby Dragoo and Dan Hamman. He
weighed 8 lbs. 11 oz. and was 19 ¾ inches long. He is a
pretty cute little guy!

Q2 2014 Flywheel

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (7)

Similar to Q2 2014 Flywheel

Similar to Q2 2014 Flywheel (20)

Q2 2014 Flywheel