Opening: make leadership a job people can learn
Leadership development works when the firm treats it as part of operating the business. Define what leaders do, give them meaningful responsibility in stages, and review how they handle it. The goal is not to create a copy of the founder. It is to build people who can protect technical quality, serve clients, manage teams and make sound decisions when an owner is unavailable.
That work takes time. A future leader needs chances to practice before the firm faces a succession event, a sudden departure or a period of rapid growth. Owners also need to be willing to share information and authority. If every important decision returns to the principal, the firm may have capable employees but no tested successors.
A practical approach connects nine areas: role clarity, delegated authority, project and client exposure, mentoring, management systems, retention, ownership education, fair evaluation and continuity risk. Each area supports the others. Authority without management systems can create confusion. Mentoring without real responsibility can become talk. Ownership education without clear evaluation can feel like a promise. A firm should build these parts into its regular work, then adjust them as people and needs change.
Define what leadership means in your firm
“Future leader” can mean many things. One employee may be suited to technical leadership, another to project delivery, client development or firm operations. A future principal may need to work across several areas, but the firm should not assume that every talented engineer wants the same path.
Write down the roles the firm needs, both now and as senior owners reduce their involvement. For each role, describe the work and decisions attached to it. A project manager might be responsible for scope, schedule, coordination, client updates and issue escalation. A technical lead might set review expectations, assign design checks and resolve technical disagreements. An office or practice leader might plan staffing, monitor backlog and contribute to hiring.
Keep role descriptions grounded in observable work. “Has executive presence” is hard to develop or assess. “Explains project risks to clients early, documents decisions and brings options to the owner when a scope change affects fees” is clearer. The same principle applies to people skills. Define what good supervision and communication look like in your firm. Also describe the judgment you expect.
Separate present responsibility from future potential. Someone may deliver excellent work and still need experience with financial decisions or client negotiations before taking on broader authority. That does not diminish the person’s contribution. It gives the firm a more accurate development plan.
Ask employees what kind of responsibility they want. A strong engineer may prefer deep technical work over firm management. Another may be keen to lead a team but need practice handling difficult client conversations. Development should respond to both the firm’s needs and the employee’s interests. Do not promote someone into a role simply because they are the most senior person available or because the firm lacks a succession plan.
Delegate authority in stages
People cannot demonstrate judgment if every meaningful decision requires approval. At the same time, transferring responsibility without boundaries can expose the firm and its clients to avoidable problems. Staff may also be affected. Delegation works best when the owner says what the employee may decide, what information they should use and when they must involve someone else.
Set authority by category. For example, a project leader may be able to assign work within an approved budget, agree on routine meeting dates or address a minor coordination issue. A fee change, a new contractual commitment or a technical decision outside the person’s competence may require review. Your firm’s contracts, insurance requirements and quality procedures should inform these boundaries. Applicable professional obligations matter too.
Put the boundaries somewhere people can find them. A simple responsibility matrix can name the decision, the person who recommends it, the person who approves it and the circumstances that require escalation. If the rules live only in an owner’s memory, staff will either interrupt the owner constantly or guess at what is allowed.
When delegating a decision, provide the context behind it. Explain the client relationship, project constraints, fee assumptions, technical concerns and prior commitments. Authority without context is a trap. Give the employee a chance to explain their recommendation before you step in with your own. When a decision needs to change, discuss what information or constraint changed it, instead of taking the work back without explanation.
Increase authority as the person shows they can handle the responsibility. Start with a defined part of a project or a limited client interaction. Review the outcome, then expand the scope of decisions. Make clear that asking for help is a sign of sound judgment, not failure. Delegation should increase the firm’s capacity while preserving appropriate technical review and professional accountability.
Give future leaders real project and client exposure
Project experience develops leadership when the person sees how work moves from proposal through delivery and closeout. It is not enough to assign someone more design tasks. Give developing leaders responsibility for coordination, staffing conversations, fee awareness, schedule updates, quality processes and client communication within the authority you have set.
Let them attend relevant project reviews and explain the status themselves. Have them prepare a forecast or risk summary, then discuss what the numbers and issues mean. They should learn how scope and staffing affect one another. Schedule and client expectations are also connected. A project that appears technically straightforward can still become difficult if decisions are delayed, assumptions are unclear or the team does not raise a problem early.
Client exposure should be deliberate. Introduce the employee as a meaningful part of the team, not as an observer who may or may not remain involved. Let them lead a meeting agenda, present a technical update or follow up on a client request. Over time, give them responsibility for a defined relationship or part of an account.
Prepare them before important conversations. Review the client’s priorities, commitments, likely questions and any issues that could change the discussion. Afterward, talk through what they heard, what they committed to and what needs follow-up. This builds client judgment and protects trust.
Exposure should match competence and professional responsibility. A developing leader can coordinate a discussion and surface options while a licensed professional retains the judgment and approvals required for the work. Give employees room to participate without blurring who is accountable for engineering decisions. Local codes and contracts govern technical work. Firm quality procedures apply as well.
Build mentoring into actual work
Mentoring is useful when it helps someone handle a real responsibility. A recurring meeting can create space to discuss decisions and setbacks. It can also help someone reflect on growth, but it should connect to work the employee is doing. Both people should know what they want the relationship to accomplish.
A mentor can help a future leader prepare for a client meeting, understand a project forecast or think through a staffing problem. The mentor should ask how the employee sees the issue before offering advice. The point is to improve judgment, not to provide an answer for every situation.
Separate mentoring from performance management where possible. A manager may need to discuss deadlines, quality or compensation. A mentor can provide a safer place to consider longer-term goals, difficult relationships or areas where the person feels unprepared. If one person serves both roles, agree on what can remain private and what must be shared for business or professional reasons.
Mentoring should work in both directions. A senior principal may understand the firm’s history and client expectations, while a newer employee may bring a different view of communication, software or team practices. Respectful exchange can help the firm change without losing what clients value.
Do not make mentoring the only development mechanism. A supportive conversation cannot substitute for decision authority, client access or adequate training. It should help employees make better use of those opportunities.
Put management systems under the leaders you are developing
A growing firm cannot depend on each principal remembering every commitment or solving every issue personally. Basic management systems let new leaders see how the business works and give them a consistent way to make decisions.
Useful systems include project startup and closeout routines, staffing reviews, workload discussions, backlog reviews, quality procedures, proposal review, client follow-up and financial reporting. The firm need not bury people in forms. A short, reliable cadence is more useful than a complex process that teams ignore.
Give developing leaders access to the information relevant to their role. A project manager needs a useful view of project performance and staffing. A practice leader may need to understand backlog, hiring needs and client concentration. A future owner needs a wider picture, including how cash flow and risk affect the firm. Reinvestment affects it too. Provide context with the numbers. Financial reports without explanation can mislead or intimidate.
Use regular management meetings to assign ownership for decisions and follow-up. Each item should have a responsible person, a due date or next review point, and a way to resolve a blocker. If every discussion ends with “the principal will take care of it,” the system is reinforcing dependence.
Management routines also reveal where the firm has weak processes. If no one can explain how a proposal is priced, how a project risk gets escalated or who owns a client follow-up, the problem may be larger than an individual’s readiness. Make the process clear before judging whether a prospective leader can operate it.
Retain people through credible opportunity
Firms often lose promising people when responsibility grows but recognition and support do not. Career options matter too. Retention is not a single benefit or compensation decision. It rests on whether people can see a credible path, receive fair treatment and do meaningful work without being left alone with impossible expectations.
Discuss career goals early enough to plan around them. Explain which roles may become available, what skills those roles require and what the employee still needs to demonstrate. Do not guarantee a title, ownership stake or timeline the firm cannot promise. Be direct about what is known, what remains undecided and when the conversation will continue.
Review pay and rewards with attention to responsibility and performance. The firm’s compensation practices also matter. If a person takes on client or operational duties beyond their current role, discuss how the firm will recognize that work. Avoid relying on vague future benefits to compensate for an immediate increase in responsibility.
Workload and management quality matter too. A developing leader can burn out when expected to perform a full technical workload while also managing staff and clients. Adjust assignments as duties change. Give people training and support. Allow time to learn the new role. A firm that wants leaders to stay must make leadership work sustainable.
Look at departures as information. If capable employees leave after repeated delays in advancement, unclear ownership discussions or limited client access, the firm should examine those patterns. Exit conversations can help, but the more useful evidence often comes from regular conversations before an employee decides to leave.
Teach ownership before offering it
Ownership should be explained as a business and governance commitment, not just a reward for tenure. A prospective owner needs to understand what equity represents, how decisions are made, what financial obligations may apply, how compensation differs from distributions and what can happen when an owner leaves. The specifics depend on the firm’s legal structure and governing documents.
Start with education, not a pitch. Explain how the firm earns revenue, manages cash, funds equipment or growth, handles risk and makes decisions. Describe the difference between owning a share and having authority over a particular business decision. Discuss how ownership affects responsibilities to employees and clients. Other owners are affected too.
Be clear about process and eligibility. If the firm has criteria for becoming an owner, document them and explain who evaluates candidates. If the process is still being designed, say so plainly. Do not imply that a person has earned equity when the firm has not made a decision or set terms.
Before any ownership offer, have the firm’s structure and terms reviewed by qualified legal and tax professionals. Valuation professionals may also be appropriate. The prospective owner should have a fair opportunity to understand the documents and ask questions. Existing owners should be prepared to explain their expectations around governance, distributions, reinvestment, transfer restrictions and succession.
Ownership education also helps an employee decide whether they want the obligations that come with equity. Some excellent leaders will prefer a senior employment role. Others may want ownership but need time to understand the tradeoffs. Treat either choice with respect.
Evaluate people fairly and consistently
Leadership decisions affect careers and firm continuity, so they deserve a process that people can understand. Set criteria before evaluating candidates. The criteria should connect to the work of the role: technical judgment, project delivery, client trust, communication, staff development and financial awareness. Follow-through matters as well, when relevant.
Use evidence from more than one project or relationship. A single difficult client meeting or late project does not tell the full story. Consider the conditions the person faced, the support they received and whether the firm’s own processes contributed to the result. Ask for the employee’s account before drawing conclusions.
Calibrate evaluations across managers. Different supervisors may use different standards for responsiveness, leadership presence or technical confidence. A periodic review among principals can reveal inconsistent expectations. Keep notes on specific examples and agreed next steps, rather than relying on impressions or recent events.
Give direct feedback close to the work. Name what went well, what needs to change and what the next opportunity will be. For example, if a project lead needs to improve escalation, specify the kind of issue that should be raised, the timing and who should be contacted. Then provide another opportunity to practice.
Fair evaluation does not mean every person receives the same role or ownership outcome. It means decisions follow clear criteria, relevant evidence and a consistent process. Employees should understand what they can do to improve their readiness and when the firm will review progress again.
Reduce continuity risk before it becomes urgent
A firm may be exposed when one principal holds most client relationships, technical knowledge, approval authority or institutional history. The risk is not limited to retirement. An illness, unexpected departure, dispute or sudden workload change can leave the firm without a clear path to serve clients and make decisions.
Map critical responsibilities and identify who can cover them. Include client contacts, proposal approvals, project reviews, staff decisions, banking or administrative access and recurring obligations. For each item, ask whether another qualified person knows the current status and can act within their authority.
Capture knowledge where the work happens. Keep project decisions, client commitments, key procedures and contact histories in systems the right people can access. Avoid creating a document archive that no one maintains. Assign owners to review important information and update it when responsibilities change.
Test coverage with ordinary work. Have a developing leader run a project review, lead a client check-in or chair a staffing discussion while the principal remains available for escalation. Note what information was missing and where authority was unclear. This is a practical continuity exercise, even if the firm does not call it one.
Continuity planning should include technical accountability. Identify which licensed professionals are responsible for review and approval, and how work will be covered if someone is unavailable. A succession plan cannot transfer professional judgment by title alone. The relevant licenses, local codes, contracts and quality controls continue to govern.
Make development a recurring owner responsibility
The next generation of leaders will not emerge from a single seminar, title change or ownership meeting. They develop through repeated practice, timely feedback and access to the information and authority required to do the job. The principals must create those conditions and then let people use them.
A useful starting point is to select a small group of roles the firm must cover well. Define the work, identify interested employees and give each person a practical development assignment. Set boundaries, name a mentor or manager, and schedule a review of what happened. Add client exposure and financial context as readiness grows.
Review the plan as a group of owners. Are decisions moving to capable people? Are employees getting a fair chance to demonstrate readiness? Do management systems support the work? Is client knowledge distributed? Are ownership conversations clear and accurate? These questions turn leadership development from an aspiration into operating practice.
The firm benefits when its ability to serve clients and make sound decisions does not rest on one person. The employees benefit when advancement is tied to real work, honest feedback and a credible path. Start with the next responsibility the firm can delegate well, then build from there.
Related CivilEngineers.com resources
Explore the resources library, guides, checklists and CivilEngineers.com directory for more firm management resources.
General education only, not engineering, legal, tax or investment advice. Licensed PE judgment and local codes govern.
