Thinking Like a Business Owner

Understanding the Owner Mindset

Running an architecture or engineering firm is not the same as running a pure production shop. Your value is not in doing every drawing mark-up yourself or checking every calculation. Your value is in setting standards, protecting quality, and making sure the firm grows without the owner becoming the choke point. The owner mindset means you think like the person responsible for the whole firm, not like the busiest technical person in the room.

A big part of that mindset is the 80% Rule. If a project manager, job captain, or engineer can complete a task to 80% of your preferred style and quality, you should usually let them own it. That does not mean accepting sloppy work. It means teaching your team what “good enough to move forward” looks like, instead of insisting on your personal touch on every sheet, memo, and client email.

#

Why the 80% Rule Matters

In an architecture/engineering firm, perfectionism often shows up as endless redlines, over-checking, and owner-level review of tasks that others could handle. A principal who insists on rewriting every consultant coordination note or redlining every DD set will slow down the entire firm. Projects pile up, deadlines get tight, and the owner becomes the last stop for every issue.

The better path is to set a clear standard. For example, a project architect can prepare a schematic design package that meets the client brief, code intent, and internal QA checklist. If it is 80% of the way to the principal’s style, it should still move forward. The last 20% can be coached, not hoarded.

The Importance of Delegation

Delegation in an architecture or engineering firm is not just about getting tasks off your plate. It is how you build bench strength. A firm cannot grow if only the owner can lead a client meeting, review a fee proposal, or resolve a consultant coordination issue.

Think about a civil engineering firm where the owner keeps handling every utility coordination call. The owner ends up trapped in project noise while younger staff never learn how to manage those conversations. Delegation changes that. When you pass real responsibility to others, they start thinking like owners too.

Good delegation means more than saying, “Handle it.” It means giving the person the scope, the deadline, the standard, and the authority to make decisions within limits. That is how project managers become stronger, how senior designers become leaders, and how the firm gains depth.

The Role of Trust in Leadership

Trust is the backbone of a healthy firm. In architecture and engineering, trust is not blind faith. It is earned through clear expectations, repeatable checks, and the willingness to let capable people carry work without hovering over them.

When staff know they are trusted, they speak up earlier, solve problems faster, and take ownership of deliverables. A structural engineer who feels trusted will flag a design issue before it reaches the client. A BIM manager who feels trusted will fix a coordination clash without waiting for the principal to approve every move.

If people feel like they will be second-guessed no matter what, they stop taking initiative. Then everything climbs back to the owner’s desk.

Implementing the 80% Rule

1. Identify Tasks to Delegate: Look for repeatable work that others can handle with a clear checklist. This may include internal redline prep, meeting notes, proposal formatting, permit submittal packaging, or first-pass coordination review.
2. Set the Standard: Define what 80% looks like in your firm. Use sample markups, QA checklists, code review steps, and client communication templates so the team knows the target.
3. Give Real Authority: Let project managers approve routine changes, let senior staff lead portions of client meetings, and let discipline leads own technical follow-up within their scope.
4. Review the Right Things: Check outcomes, not every tiny action. Review whether the package is accurate, on time, and aligned with the client’s goals instead of rewriting every sentence.
5. Coach, Don’t Grab Back: If the work is close but not quite right, give specific feedback and let the person improve next time.

A good example is a principal who stops personally reviewing every consultant transmittal and instead gives the project architect a checklist for scope, dates, and coordination items. The principal then reviews only the important exceptions. That frees time for business development, staffing, and fee strategy.

Conclusion

Thinking like a business owner in an architecture or engineering firm means protecting the firm’s future, not just polishing today’s deliverables. The 80% Rule helps you delegate without chaos, build trust without losing control, and grow a team that can carry the firm forward. If you keep everything on your own desk, you stay busy. If you build systems and trust, you build a firm.