Delegating, Managing & Letting People Go

Introduction to an Execution Cadence

An architecture or engineering firm needs a dependable management rhythm. Projects move through many hands: principals, project managers, designers, engineers, BIM staff, consultants, contractors, and clients. Without a shared cadence, a missed decision can turn into a late drawing set, an unpaid change order, or a costly field error.

An execution cadence gives the firm a repeatable way to coordinate work. It usually includes short daily check-ins for active project teams, weekly project and operations reviews, and quarterly planning for staffing, sales, cash, and capacity. The goal is not to fill calendars with meetings. The goal is to make decisions early, assign clear owners, and keep project work moving.

Delegating Effectively

Delegation means giving a defined outcome to the right person, along with the authority, information, and deadline needed to deliver it. It does not mean handing someone a vague task and waiting for a surprise at the end.

For example, a principal may be reviewing every door schedule, consultant question, and client email on a hospital project. Instead, the principal can assign the project architect ownership of the door schedule review, provide the office standards, set a Thursday deadline, and require escalation only for code conflicts or major scope changes. The principal remains accountable for the project but no longer performs every technical check.

Good delegation in a firm includes five points: the result required, the person responsible, the decision limits, the review date, and the standard for acceptable work. Start with repeatable work such as consultant coordination logs, permit submission checklists, meeting minutes, fee tracking, and routine drawing reviews. As staff prove reliable, delegate larger responsibilities such as client presentations, subconsultant coordination, or project delivery leadership.

Managing with Metrics

A firm cannot manage well by asking, “How is everything going?” Use a small set of visible measures instead. Useful measures include percentage of design milestones submitted on time, hours spent versus fee budget, outstanding requests for information, overdue client decisions, unbilled work, and change orders awaiting approval.

These numbers are not meant to punish project teams. They show where a principal or project manager needs to help. If a project is at 82 percent of its labor budget but only 65 percent complete, the team needs a scope, staffing, or fee conversation. If a project has twelve unanswered client decisions, the next action may be a decision meeting rather than more drafting.

Review metrics weekly. Ask what changed, why it changed, and who will act by when. Keep the dashboard simple enough that project managers will update it without spending half a day maintaining it.

The Importance of Letting People Go

Keeping the wrong person too long damages both project quality and team trust. A staff member may miss coordination deadlines, ignore review comments, or create conflict with clients and consultants. One weak performer can force senior staff to redo work, reduce margins, and make dependable employees feel that standards do not matter.

Before ending employment, set clear expectations, provide suitable training, document the performance problem, and follow applicable employment laws and firm policy. A capable person who lacks experience may improve with coaching. Someone who repeatedly rejects feedback or creates risk after fair support may not belong in the role.

The same principle applies to a toxic high performer. A senior engineer who wins work but belittles junior staff can cause valuable people to leave and can weaken the firm’s reputation. Protecting the culture and delivery standard is more important than preserving one person’s short-term billings.

Real-World Application

Consider a 25-person civil engineering firm where the owner still approves every proposal, reviews every plan sheet, and joins every client call. The owner introduces a weekly project review, assigns each project manager clear authority, and uses a dashboard for fee burn, schedule, open decisions, and quality issues. Project managers take over routine reviews, while the owner focuses on key clients, hiring, and financial planning.

One project manager continues missing deadlines after written expectations, coaching, and a formal improvement period. The firm replaces that manager carefully, transfers active work using a written handoff, and communicates the plan to clients. Within two months, review backlogs fall and senior engineers regain time for billable project leadership.

Conclusion

Strong delegation, simple operating measures, and timely personnel decisions create a healthier architecture or engineering firm. The owner’s job is not to touch every drawing or answer every question. It is to set standards, assign ownership, inspect important results, and act quickly when a role or person is not working. A steady cadence gives the team clarity without turning the firm into a meeting machine.