{"id":4906,"date":"2016-07-20T15:01:12","date_gmt":"2016-07-20T15:01:12","guid":{"rendered":"https:\/\/modelo.io\/blog\/?p=4906"},"modified":"2020-12-16T06:27:29","modified_gmt":"2020-12-16T06:27:29","slug":"design-manifestos-david-marks-teecom","status":"publish","type":"post","link":"\/blog\/index.php\/2016\/07\/20\/design-manifestos-david-marks-teecom\/","title":{"rendered":"Design Manifestos: David Marks of\u00a0TEECOM | Modelo Blog Series"},"content":{"rendered":"
\n

Design Manifestos: David Marks of TEECOM<\/h1>\n<\/div>\n
\n
\n
\n
<\/div>\n
<\/canvas><\/div>\n<\/div>
David Marks (Photograph courtesy of TEECOM)<\/figcaption><\/figure>\n<\/div>\n
\n

David Marks is the President and CEO of TEECOM<\/strong><\/a>, with offices in Oakland, California, the United Kingdom, Dallas, Texas and shortly Portland, Oregon. Believing that people are the key to a successful services business, David began early in his career surrounding himself with the best people, treating them like family, and giving them the tools necessary to do outstanding work for the firm\u2019s clients. Today, those efforts have paid off. The San Francisco Business Times has ranked TEECOM as one of the top 100 fastest growing companies, as well as one of the top 20 best places to work. David has led by example to create a company where all employees work toward the same goal: integrating forward-thinking and innovative ideas and technology into architecture that is practical and aligns with the business objectives of the firm\u2019s clients.<\/p>\n

TEECOM is an integrated technology design company that forges the ultimate convergence of technology and experience. By creating the infrastructure solutions that make today\u2019s buildings smart and social, the firm brings strategic thinking and innovative engineering to telecommunications, security, audiovisual, acoustics, virtual reality, wireless, network, VoIP, and other electronic systems. Modelo<\/strong><\/a> <\/strong>spent some time learning about David\u2019s current role and the evolution of TEECOM.<\/p>\n

\n
\n
<\/div>\n
<\/canvas><\/div>\n<\/div>\n<\/figure>\n

On becoming an engineer<\/strong>
\nIn high school, I enjoyed math and science, but I had no idea what I wanted to do. A computer science teacher suggested I explore engineering. I didn\u2019t know what an engineer did, but I figured if it was math and science it sounded good. I went to the University of California, Berkeley and majored in electrical engineering and computer science, and absolutely hated the program.<\/p>\n

I decided to leave school to pursue an internship at an engineering firm and do the things that an engineer does. My first project was the Moscone Convention Center Expansion in San Francisco. I was amazed. I had no idea that engineers designed buildings and that they worked with architects. I always loved buildings and marveled at how they were built. I fell in love with the profession and ended up going back and finishing my degree in electrical engineering at Cal Poly in San Luis Obispo.<\/p>\n

On discovering his voice as an engineer<\/strong>
\nWhen you first start out in any profession, you\u2019re not sure if your ideas and opinions are valid. Once you have more experiences where you have an idea and somebody else says it and everyone thinks it\u2019s great, you start to trust yourself a little bit more.<\/p>\n

One of the instrumental moments in my life was when I went to a senior engineer and asked why he designed something a certain way. His response was, \u2018I don\u2019t know I just copied it from someone else. I figured it was right.\u2019 I was shocked because he was someone I respected and trusted for his knowledge. It taught me that not everyone in the industry who has an opinion about something knows why they believe it.<\/p>\n

If you truly understand something, you understand all the properties and principles of it: the goals, why you\u2019re designing it, how it works, and that fact overrides opinion. When you understand all of the fundamentals about your idea, you\u2019re much more confident saying, \u2018This is how it should be done. I know everyone does it this way but I\u2019m doing it this way and it\u2019s much better for these reasons.\u2019 That is how we progress the industry.<\/p>\n<\/div>\n

\n
\n
\n
<\/div>\n
<\/canvas><\/div>\n<\/div>
Parkland Hospital (Photograph \u00a9 2015 Dan Schwalm: HDR courtesy of TEECOM)<\/figcaption><\/figure>\n<\/div>\n
\n

On starting TEECOM<\/strong>
\nEver since I was 16 and had my first job working at a Carl\u2019s Jr. (a fast food restaurant) and then at a Best Products (a big box retailer), I believed that I could run a business. One of the things that I\u2019m naturally good at is that I see a process or system and I know how to improve it. I started TEECOM because I saw what was being done in the industry by other professionals and I would ask them, why do you recommend that it be done that way? Or why are you recommending this solution over another? Usually they didn\u2019t know. They repeated something that they had heard.<\/p>\n

I took the time to ask why and learn the reasons and facts behind various design choices. I had a strong opinion and felt that I should share it. I knew I wanted to start my own company. I was growing the company that I was with, but not all of the owners saw a future in designing technology for buildings. I disagreed, so I left and started TEECOM in 1997. It was the perfect time to start a business because we had the whole Silicon Valley dot-com boom and the first round of Internet companies. There was so much work.<\/p>\n

On the evolution of his approach<\/strong>
\nWhen you start out doing something, you\u2019re exposed to one specific task, whether it\u2019s to design a building or a system. As you do it over and over again, you start to see how it could be done better or how it relates to something else. TEECOM started out just doing IT infrastructure engineering. We looked at all the systems attached to that\u200a\u2014\u200athe network, audiovisual systems, security systems, acoustics related to audiovisual performance, or project management. We found that the industry was lacking in good engineering and project management.<\/p>\n

Over the years, we continue to add services where there was a need. That\u2019s probably true of many different businesses. You have an initial idea of what you want to do and a service or product that you want to develop, but then you find that in order to control the end user\u2019s experience with that product or service, you have to control more of the process. So you expand and do more things that deliver a more integrated and higher-level result.<\/p>\n

When we talk to clients, we don\u2019t really talk about IT infrastructure or displays or card access readers. We talk about what problems they\u2019re having, how we can better connect their people internally to an office or organization, with the outside world, their clients, how to keep them safe from a physical security but also electronic security standpoint. We figure out how to deliver it. That\u2019s what clients want. They don\u2019t necessarily want the end product or service, they want the experience. They want someone to handle it, take over and deliver it whether they know to ask for it or not. Over the years we\u2019ve grown to deliver experiences rather than services.<\/p>\n<\/div>\n

\n
\n
\n
<\/div>\n
<\/canvas><\/div>\n<\/div>
Cal Academy (Photograph \u00a9David Wakely Photography courtesy of TEECOM)<\/figcaption><\/figure>\n<\/div>\n
\n

On specific principles he strives to adhere to<\/strong>
\nOne of the things that bothers me is poor design. Poor design usually results from people not thinking about it in advance. That\u2019s why you see pathways strapped to the outside of buildings or satellite antennas stuck to rooftops in plain view. It doesn\u2019t need to be seen.<\/p>\n

The best way to describe our design philosophy is that if it doesn\u2019t need to be seen or heard, it shouldn\u2019t be. Unless there\u2019s a reason to see the cables, the pathways, the antennas or all the electronics that go into making something happen, it should be invisible to the user. The space should speak for itself.<\/p>\n

On his role at TEECOM<\/strong>
\nEven though I\u2019m the CEO, when I first started out I did engineering, interfaced with our clients, put together drawings, wrote specifications, spoke with contractors, walked jobsites, and did anything that needed doing. As the company grows, you have to learn to train other people to do what you do. My role became more about training people in engineering. Then as you start to pass 20\u201330 people, you find that you need people to lead specific aspects of the business.<\/p>\n

You start to put a leadership team in place: someone who\u2019s in charge of engineering, someone in charge of operations, someone in charge of business development and marketing and someone in charge of HR and finance. My job now is about making sure I have the right leadership in place. We\u2019re about 85 people. We\u2019ll probably be over 100 people by the end of the year. I haven\u2019t walked a jobsite in a while. I don\u2019t put together drawings anymore. In fact, the design tools that our staff uses have surpassed my abilities. I have never used Revit, which is a little uncomfortable for me because I was so hands-on.<\/p>\n

My job now is about designing a business that\u2019s scaled from $1 million a year in revenue to $10 million a year in revenue to over $20 million a year in revenue. In order to do that, you have to think about how to sustain a business that can deal with all of the challenges that come with having a lot of people with competing interests, ideas, goals, clients, and industries. How do you do what you did when you were small and it was easy on a much larger scale?<\/p>\n<\/div>\n

\n
\n
\n
<\/div>\n
<\/canvas><\/div>\n<\/div>
Palomar Hospital (Photograph \u00a9John Linden courtesy of TEECOM)<\/figcaption><\/figure>\n<\/div>\n
\n

On recent projects that represent TEECOM\u2019s unique approach<\/strong>
\nWe probably have 200\u2013300 different building projects going on at one time. The California Academy of Sciences in Golden Gate Park is the first natural history museum, planetarium, aquarium, and research institute all housed in a single new building. We put every electronic system on a converged network. It was the first museum of its kind to operate that way, and probably one of the first buildings of its kind to operate anywhere that way.<\/p>\n

The project won an award from InfoWorld for being one of the top 15 green IT projects in the world. That was the result of a great team, a great vision for the client and people who were willing to do things that hadn\u2019t been done before.<\/p>\n

The hospitals we work on are good examples. There\u2019s somewhere between 120\u2013150 different electronic systems in your typical hospital and the whole healthcare industry is in need of innovation. We\u2019ve been fortunate enough to work on Palomar Hospital in San Diego, California; Parkland Hospital in Dallas, Texas; Stanford Hospital in Palo Alto, California; and UCSF Hospital in San Francisco, and we\u2019ve been able to bring a different level of thought, envisioning, and integration that improves patient outcomes. I\u2019m proud of that.<\/p>\n

On the other spectrum, we build corporate offices for fortune 100 companies all over the world. We\u2019re able to oversee and deliver design from San Francisco to New York to London to Tokyo to Melbourne. It\u2019s nice to have the client come back to you and say \u2018you\u2019re delivering space and services better than we ever delivered ourselves internally. We never thought that an external partner could do that.\u2019 It makes us feel good.<\/p>\n

On the firm\u2019s design toolkit<\/strong>
\nWe use a lot of tools. AutoCAD and Revit are the two big ones from a design standpoint. Then there are all the collaboration tools like Slack for internal communications and Asana for project management. Office 365 because you still have to communicate with clients over email and put together Excel and Word documents. We also use Confluence, which is our internal knowledge management platform. We use Bluebeam for cloud markups of drawings and drawing management. Plangrid we use a lot out in the field.<\/p>\n

When the latest software comes out we like to test it to determine if it improves the process. We\u2019re always trying to stay on the cutting edge of what\u2019s available. We even tend to develop our own software internally if we don\u2019t like what\u2019s out there. It takes all of that to deliver a better product.<\/p>\n<\/div>\n

\n
\n
\n
<\/div>\n
<\/canvas><\/div>\n<\/div>
UCSF Medical Center (Photograph \u00a9Stantec courtesy of TEECOM)<\/figcaption><\/figure>\n<\/div>\n
\n

On the state of software today<\/strong>
\nIt could be a lot better. Twenty-five years ago while in school, my capstone project involved developing an interface for what was called ICADS, Intelligent Computer Aided Design Systems, which the architecture department at Cal Poly was developing. It already used 3D modeling and the concept of objects rather than drawing lines or symbology to represent a real world object.<\/p>\n

It understood what a room was and what a window was, what electrical power was and heat loads were. It used these intelligent agents written in an artificial intelligence-based software called CLIPS that understood building codes, the UBC, the electrical code, local codes, and Title 24. It also understood cost. As you designed a building and chose materials, whether it was wood-framed or steel-framed or concrete, it would tell you that your window was too big or the cost was too high. It would resolve it for you and make suggestions on what you could do to meet code or a local ordinance or energy guideline.<\/p>\n

If you wanted to reduce cost, it would give you the best ways to do it. We still don\u2019t have anything like it in the industry. I follow Bret Victor and his pursuit in life is to better integrate the tools that we use to design things with the outcomes of those tools. The design process is too disjointed. You have to do a lot of iterative work and then look at the outcome and then go back and change it, and then look at the outcome again. You should be able to work in both domains. You should be able to look at the outcome and describe what you want to have happen in the outcome, and have the design tool make the necessary changes.<\/p>\n

On the future of the AEC industry<\/strong>
\nThe industry needs better design tools and better collaboration tools. I think the raw capability of the existing tools is fantastic, but they need to be easier to use so that people are comfortable using them. Regarding collaboration, it\u2019s still frustrating when you have to travel to an architect\u2019s office and sit in a room of 30 engineers and designers for three to four hours every week to talk about a project and everyone gets two to five minutes to talk. The rest of the time you\u2019re listening or the discussion has nothing to do with what you\u2019re involved in.<\/p>\n

The technology exists to allow people to collaborate on specific issues electronically or virtually. We have to get out of this mode of everyone having to sit in the same room and go through this long drawn-out process to resolve issues. There\u2019s value in being in the same room and getting to know people when you have to work together. You\u2019re much more likely to answer my question or help me if you know me as a person rather than just a name on an email or a website. Use the face-to-face meeting time for building relationships and then use better electronic tools for collaborating remotely.<\/p>\n

As designers, we have to focus on the client\u2019s experience as we do on the product or the service that we deliver. If you think about any time that you go shopping or you have your car serviced or you eat at a restaurant, it\u2019s more about the experience than about that product or service. You want people to demonstrate that they care about you. You want to feel good and enjoy the experience. People tend to get focused on the technical aspect of the design or the product and not the overall experience.<\/p>\n

On advice he would give himself<\/strong>
\nI would tell myself to trust my instincts earlier. To speak up, rather than waiting, and to not be afraid to try new things. Early on, when you run an organization, you don\u2019t want to make a mistake. You don\u2019t want to do something that\u2019s going to end your career and the business. You tend to play it safe. As you get older and wiser, you start to understand that your ideas, when based in fact and experience, are pretty good and it\u2019s okay to buck the norm.<\/p>\n

For example, offering unlimited personal time off or allowing people to work from home or wherever it is that they want. You can work from anywhere given today\u2019s technology. Or putting a compensation plan in place that incentivizes behaviors like providing a great experience, generating repeat business, and delivering great design. All those things are possible. While it is highly uncommon to do a number of those things in the industry, it\u2019s okay to be different. In fact, there are a lot of good things that come out of being different. When you have an idea or you\u2019re trying to solve a problem and the solution may be unconventional, push yourself to take risks.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

Design Manifestos: David Marks of TEECOM David Marks (Photograph courtesy of TEECOM) David Marks is the President and CEO of TEECOM, with offices in Oakland, California, the United Kingdom, Dallas, Texas and shortly Portland, Oregon. Believing that people are the key to a successful services business, David began early in his career surrounding himself with the best people, … <\/p>\n

Continue reading “Design Manifestos: David Marks of\u00a0TEECOM | Modelo Blog Series”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":4908,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"\/blog\/index.php\/wp-json\/wp\/v2\/posts\/4906"}],"collection":[{"href":"\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=4906"}],"version-history":[{"count":2,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/posts\/4906\/revisions"}],"predecessor-version":[{"id":6568,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/posts\/4906\/revisions\/6568"}],"wp:featuredmedia":[{"embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/media\/4908"}],"wp:attachment":[{"href":"\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=4906"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=4906"},{"taxonomy":"post_tag","embeddable":true,"href":"\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=4906"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}