From Engineer to PM: What Actually Makes You Effective

Key Concepts

• Technical Foundation: The essential base of engineering knowledge required to build credibility and confidence as a project manager.
• Managing Up: Proactively seeking opportunities to understand project financials, proposals, and management responsibilities from supervisors.
• The "Quarterback" Analogy: A framework for project management where the PM coordinates various disciplines and stakeholders to ensure project execution, even without being the technical expert in every sub-field.
• Due Diligence: The critical initial phase of a project where potential risks, red flags, and client goals are identified to prevent future surprises.
• Public Interface: The high-stakes phase where a project is presented to boards or the public, requiring tailored communication and confidence.
• Post-Production/Lessons Learned: A "gloves-off" meeting held after project milestones to evaluate performance and identify process improvements.

---

1. Career Trajectory and Professional Growth

Jesse Copley, a licensed professional engineer and geographic discipline leader at Colliers Engineering and Design (CED), emphasizes that his transition from a design engineer to a project manager (PM) was an organic process spanning 20 years.

• Early Career: Starting as a design engineer, he worked on diverse projects (residential, industrial, municipal). He avoided being "pigeonholed" by wearing multiple hats—handling layout, grading, and stormwater design simultaneously.
• Current Role: His responsibilities have shifted from technical design to client management, financial oversight, staff development, and business development.

2. The Transition to Project Management

Jesse identifies three pillars for a successful transition:

• Technical Mastery: Reading regulations thoroughly and becoming a "trusted resource" for managers. This technical competence allows a PM to speak with authority to clients and reviewing agencies.
• Financial Literacy: Understanding the business side early by reviewing proposals, tracking personal billable hours against budgets, and managing project profitability.
• Communication Nuance: Learning to tailor messages to the audience. For example, avoiding overly technical jargon (like Manning’s equation) during public meetings to maintain community support, and keeping emails concise.

3. Methodologies for Project Success

• The "Quarterback" Framework: A PM acts as the central coordinator. They do not need to be the best at every specific task (e.g., structural or geotechnical), but they must know where every team member is and how their work integrates.
• Communication Modes: While email is vital for documentation, Jesse argues that phone calls are the most efficient way to resolve issues, gain immediate buy-in, and avoid misinterpretation.
• Internal Coordination: In multi-disciplinary firms, PMs must treat internal departments (survey, traffic, geotech) as partners. This requires early kickoff meetings to define scopes and milestone meetings to track progress.

4. Key Arguments and Perspectives

• Accountability: Jesse asserts that the PM is the "face" of the project. If an internal discipline fails to deliver, the PM cannot blame them in front of the client; the PM is ultimately responsible for the outcome.
• The Value of "No": A PM builds trust by being honest about limitations. If a project is outside their capacity or budget, admitting it—and offering to find the right person—builds more long-term credibility than over-promising.
• Relationship Building: Professional success is rooted in relationships. Building a network within the organization—including social connections—makes it easier to secure support during urgent project phases.

5. Notable Quotes

• "I went to school to be an engineer. I didn't go to school to be an accountant... those skills are things I had to learn along the way." — Jesse Copley
• "If you don't have an answer, you failed. So even though it might have been another in-house discipline that is slow... you can't throw them under the bus with the client." — Jesse Copley (quoting his mentor, Ron Lazat)
• "We're not reinventing the wheel here. Engineering's been around a long time... when you start digging into that and you understand the why behind those things, it gives you that strong base." — Jesse Copley

6. Synthesis and Conclusion

The transition from a technical professional to a project manager is not about abandoning technical skills, but rather using them as a foundation to build confidence and credibility. The most successful PMs are those who:

1. Are proactive: They volunteer for meetings and shadow experienced leaders to learn the "boring" but necessary administrative tasks.
2. Prioritize Upfront Communication: They identify risks during the due diligence phase to avoid costly surprises.
3. Master the "Why": They understand the regulations and design standards, allowing them to explain project decisions clearly to stakeholders.
4. Foster Relationships: They treat internal teams and clients as partners, building a network that facilitates smoother project delivery.

Ultimately, the role of the PM is to balance technical excellence with financial and interpersonal management, ensuring that the project moves forward efficiently while maintaining the trust of all involved parties.