Your Architecture Firm is a Design Problem

Architects are trained to solve problems. Give us a complicated site, a difficult program, a demanding client, a limited budget, and a long list of competing constraints, and we know what to do. We gather information, ask questions, study the existing conditions, test ideas, reject the ones that do not work, and develop the ones that do.

Then many of us walk back into our own firms and tolerate business problems that have existed for years. The weekly meeting that accomplishes very little, the proposal process that takes too long, the projects that consistently exceed their budgets, the clients who continually expand the scope, and the marketing that happens only when work gets slow all become accepted conditions. We would never accept these conditions on a building project without questioning them, yet we often accept them inside our businesses.

That is why I believe one of the most powerful ideas available to small firm architects is also one of the most familiar. Your architecture firm is a design problem, and it deserves the same level of attention, curiosity, and discipline that you bring to your architecture.

Apply Your Best Thinking to the Business

During my conversation with Rachel Gresham and Ali Alsaleh for the EntreArchitect Podcast, we discussed the idea that architects who build successful businesses are often doing something very familiar. They are applying design thinking to the way they run their firms. Architects already have many of the skills necessary to improve a business, but we have been conditioned to apply those skills primarily to architecture.

Design thinking begins with curiosity. We do not immediately assume that the first answer is the correct answer. We investigate the problem, understand the users, identify constraints, explore possibilities, test solutions, and refine what works.

That process applies just as well to your business as it does to your architecture. The problem is that when we become firm owners, many of us replace curiosity with reaction. Something breaks, so we fix it. Revenue falls, so we pursue whatever project appears next, and when someone leaves, we hire quickly because we feel we have no other choice.

We solve the immediate problem, but we rarely redesign the system that created it. Successful firm owners learn to do something different by treating the business as something that can be intentionally designed rather than as a collection of emergencies that must continually be managed.

Stop Accepting Existing Conditions

Every project begins with existing conditions. We document them, understand them, and respect their influence on the project. But we do not automatically assume they must remain unchanged.

Your business should work the same way. There are probably dozens of conditions inside your firm that exist primarily because they have always existed. Maybe you have always billed hourly, principals have always reviewed every drawing, project managers have always handled business development, or the entire team has always attended the Monday morning meeting.

Those practices may still be the right solutions, but they may also be outdated assumptions that nobody has questioned in years. One of the most dangerous phrases in business is some version of, “That is just how architecture firms work.” Whenever you hear yourself saying that, pay attention.

Architecture firms are businesses, and businesses are designed systems. Pricing is a system, marketing is a system, project delivery is a system, hiring is a system, communication is a system, and leadership is a system. Every one of those systems can be examined, challenged, and redesigned.

The fact that most architecture firms operate in a particular way does not mean your firm needs to operate that way. Existing conditions are useful information, but they should never become an excuse for accepting a business that does not work the way you want it to work.

Define the Problem Before You Solve It

Architects know that a poorly defined problem usually produces a poor solution. The same principle applies to business, yet owners often move directly from frustration to action without taking enough time to understand what is really causing the problem.

Imagine that your firm is struggling with profitability. The easy conclusion might be that your fees are too low, and sometimes they are. But that is only one possible diagnosis.

Perhaps your scopes are poorly defined, projects are taking longer than you estimate, principals are spending too much time doing production work, or your team is inefficient because responsibilities are unclear. Maybe you are accepting projects that simply do not fit your business model. “Profitability is too low” describes the symptom, but it does not necessarily identify the problem.

The same is true throughout your firm. If you are not generating enough new work, you may assume you need more marketing, but perhaps your real problem is positioning. You may already be visible, but prospects cannot clearly understand why they should choose your firm.

If employees are overwhelmed, you may assume you need to hire. The real issue, however, may be an inefficient project delivery system that creates unnecessary work. Before you implement a solution, spend time defining the actual problem and keep asking why until you understand the condition beneath the symptom.

You already know how to do this. It is the same intellectual discipline you bring to programming a building, and it is just as valuable when you are programming the future of your business.

Develop Alternatives Before Choosing a Solution

One of the strangest differences between design and business is how quickly we accept the first business solution that appears. Imagine presenting one design concept to a client and saying, “This was the first thing we thought of.” We would never work that way, yet firm owners regularly do exactly that when solving business problems.

Need more work? Hire a salesperson. Need more capacity? Hire another architect. Need better productivity? Buy new software. Need better financial performance? Raise fees.

Any of those solutions might be correct, but good design requires alternatives. If you need more capacity, perhaps you hire, but perhaps you improve your processes, outsource a specialized task, change your project mix, adjust schedules, increase fees, eliminate low-value services, or automate repetitive administrative work.

The purpose of developing alternatives is not to make decisions more complicated. It is to prevent ourselves from confusing the most obvious solution with the best solution. Generate several possibilities, understand the tradeoffs, and then select the approach that best serves the larger goals of the firm.

That is design thinking applied to business. We explore before we commit because the quality of the decision usually improves when we refuse to stop at the first answer.

Prototype Business Improvements

Another lesson from design is that not every idea needs to be fully built before you know whether it works. You can prototype changes inside your business, which allows you to test improvements without committing the entire firm to an unproven system.

Suppose your weekly staff meeting has become inefficient. You do not need to commission a six-month organizational study. Design a new meeting format and test it for four weeks.

Shorten the meeting, create a standard agenda, require preparation before the meeting, and move project-specific discussions somewhere else. At the end of four weeks, ask whether the change improved communication and saved time. If it worked, refine it and keep it, and if it did not, change the approach and test something else.

You can take the same approach with many parts of the business. Test a new proposal template with three prospects, try a revised onboarding process with the next employee, experiment with a new project kickoff meeting, or develop a new way to track scope creep on one project before implementing it throughout the firm.

Small experiments reduce risk while creating momentum. Improvement no longer requires a massive initiative, and you can begin changing your firm this week by choosing one contained problem and testing one thoughtful solution.

Measure the Result

Architects sometimes resist measurement because business metrics can feel disconnected from the creative work that attracted us to the profession. But measurement is simply feedback, and without feedback we have no reliable way to know whether our changes actually improved the business.

If you redesign your proposal process, did the time required to prepare proposals decrease, and did your close rate improve? If you change your project delivery system, did projects become more profitable, deadlines become easier to meet, or overtime decrease? If you change your meeting structure, did the team recover several productive hours each month?

Without measurement, we are operating on intuition alone. You do not need an elaborate dashboard with dozens of key performance indicators because too much data can become another form of distraction. Instead, identify the few measurements that tell you whether the change accomplished what you intended.

Then review those measurements consistently and use them to guide your next decision. A business owner who measures results can make informed decisions, while an owner who does not is often forced to rely on feelings, anecdotes, and whatever crisis happened most recently.

Turn What Works Into a System

Experimentation creates improvement, but systems create freedom. This is where many architecture firms lose the benefit of good ideas because someone develops a better way to do something, yet the process remains in that person’s head.

Eventually, that person becomes busy, the team grows, or someone leaves, and the improvement disappears. When something works, document it in a way that makes the successful process repeatable. That does not mean creating a 200-page operations manual that nobody reads.

A useful system may be a checklist, a template, a standard agenda, a written process, a short video, or a clearly assigned responsibility. The goal is consistency, and a strong system means the quality of an outcome no longer depends entirely on someone remembering what to do.

This is especially important for small firms because the owner’s time is one of the business’s most valuable and limited resources. Every system that allows someone else to successfully complete a recurring process gives the owner more capacity to lead, build relationships, pursue opportunities, and think strategically.

Systems do not eliminate creativity. They protect creativity by reducing the amount of energy spent repeatedly solving problems that have already been solved.

Your Firm Will Never Be Finished

There is one important difference between designing a building and designing a business. Eventually, the building is complete, but your business never is.

The market changes, technology changes, your employees change, your clients change, your goals change, and you change. The firm that served you well five years ago may not be the firm you need today, which is why designing your business cannot be an event. It must become part of leadership.

Look at the firm regularly and ask where friction exists. Where are people frustrated, where are you losing money, where are decisions unnecessarily difficult, and where does work depend too heavily on you? Where are clients confused, and where are opportunities being missed?

Those conditions are not simply problems. They are design opportunities that give you a place to begin improving the business.

Choose one recurring issue and define it clearly. Develop alternatives, test a solution, measure the results, and turn what works into a system before moving to the next opportunity.

Progress rarely comes from discovering one transformational idea. It comes from repeatedly improving the way the business works and creating a firm that becomes stronger through intentional, continuous refinement.

Better Business Creates Better Architecture

There is sometimes an assumption in our profession that focusing too much on business somehow compromises the architecture. I believe the opposite is true because a stronger business creates the conditions that allow architects to do better work.

A profitable firm has resources to invest in better people and better tools. A well-organized firm gives architects more time to think, while a firm with strong positioning can be more selective about the projects it accepts. A firm with healthy margins can also take calculated risks and pursue meaningful opportunities that might otherwise be unavailable.

Better business creates the conditions for better architecture. That does not happen because you suddenly become a different kind of architect. It happens because you start applying the skills you already possess to another important design assignment: your own firm.

My conversation with Rachel Gresham and Ali Alsaleh on EntreArchitect Podcast episode EA678 reinforced this idea for me. We talked about the business of architecture, the different ways architects are building firms, and what happens when we apply the thinking we developed as designers to the organizations we lead.

Listen to the full conversation at https://entrearchitect.com/678 and consider how these ideas apply to the business you are building. The episode provides a broader conversation about business, professional growth, and the many different ways architects can think about creating stronger firms.

If you want to continue these conversations with other small firm architects who are actively working to build stronger, more profitable businesses, join us inside the EntreArchitect Network. The Network is where architects share what is working, learn from one another, and turn ideas like these into action.

This week, choose one recurring frustration inside your firm and approach it as you would a design problem. Study the condition, define the real problem, develop alternatives, and test something better. Your next great design project may be your business.