Lisa Thomas at LaMont Engineering Custom Case Solution & Analysis

Case Evidence Brief: Lisa Thomas at LaMont Engineering

Prepared by: Business Case Data Researcher

1. Financial and Project Metrics

• Lisa Thomas Tenure: Two years at LaMont Engineering as a Project Manager.
• Ben Miller Tenure: Fifteen years at the firm; senior technical expert.
• Project X Status: High-priority initiative with aggressive milestones; currently experiencing delays in the technical design phase.
• Headcount: Lisa manages a cross-functional team of six, including senior engineers and junior designers.

2. Operational Facts

• Organizational Structure: Matrix management environment where project managers lead technical staff who report to functional heads.
• Communication Breakdown: Ben Miller bypassed Lisa to discuss technical specifications directly with the client on three documented occasions.
• Performance Issues: Ben Miller failed to deliver the thermal analysis report by the Friday deadline, citing conflicting priorities that were not previously disclosed.
• Reporting Lines: Lisa reports to Jim Carpenter, Vice President of Operations. Ben reports to the Head of Engineering but is assigned to Lisas project.

3. Stakeholder Positions

• Lisa Thomas: Believes her authority is being undermined by Bens refusal to follow project protocols. Seeks to establish leadership while ensuring project success.
• Ben Miller: Views Lisa as less experienced and technically inferior. Argues that his seniority and technical knowledge grant him autonomy over communication and timelines.
• Jim Carpenter: Acknowledges Lisas talent but maintains a hands-off approach. Expects Lisa to resolve the conflict independently as a test of her leadership maturity.
• Project Team: Observing the friction; morale is declining as team members receive conflicting instructions from Lisa and Ben.

4. Information Gaps

• HR History: The case does not provide Bens past performance reviews or whether he has had similar conflicts with other female or minority project managers.
• Contractual Penalties: Financial consequences for Project X delays are not specified.
• Functional Manager Stance: The position of the Head of Engineering regarding Bens behavior is not recorded.

Strategic Analysis

Prepared by: Market Strategy Consultant

1. Core Strategic Question

• How can Lisa Thomas establish legitimate authority over a senior technical expert who actively undermines her leadership without compromising the technical delivery of Project X?
• Should Lisa prioritize the immediate project timeline by accommodating Ben or prioritize her long-term career viability by forcing a confrontation?

2. Structural Analysis

The power dynamic at LaMont Engineering is skewed by an imbalance between formal authority and expert power. Ben Miller utilizes his fifteen-year tenure and technical expertise to bypass the formal project management structure. Jim Carpenters refusal to intervene creates a vacuum where the project managers legitimacy is determined solely by her ability to manage up and manage across. The matrix structure fails here because the functional support for the project manager is absent. The conflict is not merely interpersonal; it is a failure of the accountability framework within the firm.

3. Strategic Options

4. Preliminary Recommendation

Lisa must pursue Formal Performance Correction. The behavior of Ben Miller is a direct threat to the organizational hierarchy. Accommodating him sets a precedent that technical expertise excuses insubordination. Lisa should document the missed deadlines and unauthorized client communication, then present Ben with a formal Project Charter that explicitly defines communication protocols and delivery expectations.

Implementation Roadmap

Prepared by: Operations and Implementation Planner

1. Critical Path

• Phase 1 (Immediate): Conduct a one-on-one meeting with Ben Miller to review the Project X Charter. Explicitly state that all client communication must flow through the Project Manager.
• Phase 2 (Day 2): Document the meeting outcomes in a formal email to Ben, copying the Head of Engineering and Jim Carpenter. This establishes the baseline for accountability.
• Phase 3 (Week 1): Implement a daily fifteen-minute technical stand-up meeting. This forces Ben to report progress in front of the team, increasing peer pressure for compliance.
• Phase 4 (Month 1): Perform a milestone review. If Ben fails to meet the new standards, request his immediate removal from the project.

2. Key Constraints

• Technical Monopoly: Ben possesses unique knowledge of the thermal analysis. His removal could cause a six-week delay while a replacement is briefed.
• Management Apathy: Jim Carpenters hands-off stance means Lisa lacks an immediate enforcement mechanism if Ben ignores the new protocols.

3. Risk-Adjusted Implementation Strategy

The plan assumes Ben will test the new boundaries immediately. To mitigate the risk of project failure, Lisa must identify a secondary technical resource—perhaps a senior engineer from another department or an external consultant—who can step in if Ben becomes a total blocker. The focus is on removing the single point of failure that Ben currently represents. Contingency time of 15 percent must be added to all remaining Project X milestones to account for potential friction during this transition.

Executive Review and BLUF

Prepared by: Senior Partner

1. BLUF (Bottom Line Up Front)

Lisa Thomas must force a binary outcome: Ben Miller complies with project protocols or he is removed from the team. The current situation is a leadership test disguised as a technical conflict. Jim Carpenters refusal to intervene is a deliberate assessment of Lisas ability to exercise power. Lisa should immediately formalize performance expectations and document every breach. If Ben does not align within ten days, she must demand his replacement. Maintaining a toxic senior expert is more damaging to the firm than a temporary project delay.

2. Dangerous Assumption

The analysis assumes that Jim Carpenter will eventually support Lisa if she provides enough documentation. There is a significant risk that Jim values Bens technical output more than Lisas management authority, regardless of the evidence provided. If Jim favors technical continuity over leadership structure, Lisas position at the firm is untenable.

3. Unaddressed Risks

• Client Relationship Damage: Ben has already established a direct line to the client. If Lisa cuts this off abruptly, the client may perceive it as a loss of expertise on the project, harming the reputation of the firm.
• Systemic Bias: The analysis treats this as a standard management conflict. It fails to account for the possibility that Bens behavior is rooted in deep-seated biases that documentation alone cannot solve. This requires an HR-led cultural intervention that the implementation plan ignores.

4. Unconsidered Alternative

The team did not consider a Strategic Realignment of the project leadership. Lisa could propose a Co-Leadership model for this specific project where Ben is the Technical Lead and she is the Commercial Lead, with equal status. While this cedes some authority, it aligns formal titles with the informal power Ben is already exercising, potentially neutralizing the conflict while keeping the project on track. However, this may permanently signal that Lisa cannot manage difficult high-performers.

5. Final Verdict

APPROVED FOR LEADERSHIP REVIEW