PSYCH 678 Week 2 Contracting and Entry Example

Writing the Engagement Letter: Contracting With Engineering Firm Partners Over a Performance System They Chose

[Student Name]

University of Phoenix

PSYCH/678: Consulting and Business Skills

Week 2 Assignment

[Instructor Name]

[Date]

The engineering firm, its people and the engagement letter are composites written for a model paper; consulting guidance and ethical standards come from the sources listed.

Last week, an engineering firm's chief operating officer asked me for a new performance rating form. I suggested a free first meeting instead. This paper describes that meeting, the agreement we reached and the engagement letter that came out of it.

The Meeting

Lauren, the operations chief, brought Ted, the managing partner. Ted spoke first and defended forced distribution with conviction: before it, he said, almost everyone received top ratings, raises were spread evenly and the firm could not tell its best engineers from its weakest. Lauren said that the distribution rule had become the main complaint and that the three project managers who left had each mentioned it. Ted replied that people always complain about being rated.

That exchange told me more than any document could. The partners do not agree on what is wrong, and the person who chose the system is in the room. Any engagement that begins by assuming forced distribution is the problem, or assuming it is not, will lose one of them.

Wants and Offers

Block (2011) treated contracting as an explicit negotiation of wants and offers on both sides. The consultant asks what the client wants from the engagement and from the consultant personally, states what the consultant can and cannot offer and also states what the consultant wants from the client, such as access to people, time from leaders and a commitment to act on findings. Block urged consultants to name their own reservations directly, to treat the client's concerns about control and exposure as legitimate and to put agreements in writing so that later disappointments can be traced to the contract rather than to bad faith.

In our meeting, I asked each of them what a successful outcome would look like in a year. Ted wanted a system that still separates strong from weak performers. Lauren wanted to stop losing experienced people. I offered a short diagnostic phase to find out what is actually driving complaints and departures, with a commitment to report what the data show, including evidence about forced distribution, whatever it turns out to be. I said what I needed: interviews with partners, managers and engineers, an anonymous survey, access to two years of ratings and turnover data and a ninety-minute session with both partners to discuss findings.

The Client Owns the Problem

Schein (1999) set out principles for building a helping relationship. Among them: the consultant should always try to be helpful, should stay in touch with what is actually happening rather than with assumptions, should acknowledge what the consultant does not know and should remember that everything the consultant does, including asking questions, is an intervention. Above all, the client owns both the problem and the solution.

That principle shaped my answer when Ted asked directly whether I thought forced distribution was a mistake. I told him the research is mixed and that his firm's data would matter more than my opinion, and that if the diagnosis found the rule was a major cause, he would hear it from me plainly and decide what to do about it.

Telling the managing partner that his decision might be the problem was easier in the first meeting than it would have been in the last.

Ethical Terms

The ethics code (American Psychological Association, 2017) applies to psychologists who provide services to or through organizations. It requires psychologists to settle at the start which party is the client, the nature and objectives of the services, the intended recipients and how information will be used and who will have access to it, and that they explain the limits of confidentiality. When a third party requests services for others, the psychologist must clarify roles and the probable uses of information. Fees and billing arrangements should be agreed as early as possible.

For this engagement, the partners' group is the client; employees are participants owed honest information about how their data will be used. Employees will be told that participation is voluntary, that interview notes will be seen only by me and that results will be reported in aggregate, never in groups smaller than five.

The Engagement Letter

The letter I sent the next day contained these terms. Purpose: to diagnose the causes of dissatisfaction and turnover related to the performance management system and recommend options. Scope: the performance management process, including ratings, the distribution rule, manager preparation and links to pay and promotion; compensation levels and individual personnel decisions are out of scope. Activities: interviews with both partners, eight managers and twelve engineers selected across levels and offices; an anonymous survey of all employees; analysis of two years of ratings and turnover. Deliverables: a written report and a feedback session with the partners in week six. Fees: $18,500, half on signing and half on delivery of the report. Client commitments: a liaison in HR, an announcement from Ted explaining the project and access to data within two weeks. Confidentiality: aggregate reporting with the five-person minimum, raw data held by me and destroyed after one year.

Handling the Disagreement

I did not try to resolve whether forced distribution should stay. Instead, the letter frames the question as one the diagnosis will answer and commits both partners to reviewing the findings together. This keeps both of them invested and avoids making me an ally of either.

Why Ted's Announcement Matters

The managing partner's announcement is not a courtesy. Engineers who believe the project is Lauren's attempt to undo Ted's system may hold back, and those who believe it is a public relations exercise may not participate at all. An announcement from Ted, saying that he wants honest answers about a system he introduced, signals that candor is safe and that the partners will act on what they hear. I offered to draft it with him.

What I Left Out of Scope

Two topics came up that I deliberately left out. Ted asked whether I could also review salary bands, since engineers had complained about pay compared with competitors. Compensation benchmarking is a different engagement with different data, and adding it would blur the diagnosis and double the timeline. Lauren asked whether I could advise on whether to rehire one of the departed project managers. That is an individual personnel decision, and taking a position on it would compromise my standing with managers whose trust the interviews depend on. Naming both exclusions in the letter prevents later disappointment.

Entry Risks

Entry also carries risks. Engineers may assume I was hired to defend the system, so the announcement and my first interviews must establish independence. Managers may worry that findings will be used against them, so I will interview them before engineers and explain how their views will be reported.

Conclusion

Contracting turned a request for a new form into an agreement to understand the problem first, with both partners committed to hearing the results. Clear wants and offers, a scope with boundaries, fees and confidentiality terms written into the letter give the engagement a foundation that will matter most if the findings are uncomfortable.

References

American Psychological Association. (2017). Ethical principles of psychologists and code of conduct (2002, amended effective June 1, 2010, and January 1, 2017). https://www.apa.org/ethics/code

Block, P. (2011). Flawless consulting: A guide to getting your expertise used (3rd ed.). Pfeiffer.

Schein, E. H. (1999). Process consultation revisited: Building the helping relationship. Addison-Wesley.