MGMT 8425M Week 11 Final Leadership Brief Example

Formalize the Old Route Before Closing It: A Final Leadership Brief Recommending That an Engineering Director Appoint an Acquired Team's Former Manager as Liaison for Two Quarters, With Findings and Inferences Kept Apart, Rather Than Mandating the New Design Forum

Student Name

Walden University

MGMT 8425M: Responding to Behavior and Change as a Multicultural Leader

Instructor Name

Month Day, Year

Formalize the Old Route Before Closing It: A Final Leadership Brief Recommending That an Engineering Director Appoint an Acquired Team's Former Manager as Liaison for Two Quarters, With Findings and Inferences Kept Apart, Rather Than Mandating the New Design Forum

Summary

Situation: eight months after a composite industrial controls company acquired a 22-person motion-control engineering firm in Ann Arbor, the acquired engineers have stopped posting questions in the company's design forum and route nearly every technical question through their former manager, now a principal engineer without managerial authority. Design decisions are slowing, and the engineering director's peers see the team as unwilling to integrate. Recommendation: the director should formally appoint the former manager as liaison between the team and the wider engineering organization for two quarters, with a written handover plan that moves specific question types into the forum on a schedule. Rival: mandate forum use for all technical questions and stop answering questions routed through the former manager. The brief recommends the first and argues against the second.

1. The Workaround and the Director's Baseline

The director's notes and the forum's records show the pattern. During months one and two under the new owner, the Ann Arbor engineers posted 37 questions in the forum. In months six through eight they posted four. Over the same period, the former manager's message volume to engineers in the acquiring company rose sharply, and most of the questions he relayed were ones his former team had asked him. Two forum threads from month three show acquired engineers' questions answered with links to internal documents they could not open, and one answer that began, "As anyone here would know."

The director states her own baseline openly: in her experience, engineers should raise questions where everyone can see them, so answers are shared and no single person becomes a bottleneck. The brief treats that baseline as a preference to be tested, not a standard to be assumed.

2. Evidence: Findings and Inferences

Finding. Graebner (2004), studying the integration of eight technology acquisitions, found that leaders from the acquired firm played a key role in realizing both expected and unexpected value, and that they helped combine the benefits of integration and autonomy.

Finding. Ranft and Lord (2002), studying seven high-technology acquisitions, found that the transfer of technologies and capabilities depended on the nature of the acquired firm's knowledge and on how implementation was managed, including how much autonomy the acquired unit retained and how key people were treated.

Finding. Edmondson (1999) linked team learning to psychological safety, meaning members' confidence that a question or an admitted error will not bring embarrassment or punishment.

Inference. The forum threads suggest that asking a question there carried a risk of looking uninformed in front of a new and larger group. The former manager offers a route with no such risk, because the engineers already trust him.

Inference. The workaround is not refusal to integrate. It is the acquired team using its most trusted connection to get answers, which is the role Graebner's findings suggest acquired leaders can play well.

Inference. Mandating the forum would remove the safe route without making the forum safer.

3. The Recommended Response

The director appoints the former manager as liaison for two quarters, publicly and with defined duties. He will relay questions as now, but each relayed question and its answer will also be posted in the forum, attributed to the team rather than an individual, so knowledge is shared. Each month, one category of question, beginning with tooling and documentation, moves to direct forum posting by the engineers, with the liaison answering first in the forum to model the practice. The director will also ask forum moderators to replace links to restricted documents with summaries and to flag dismissive answers. At the end of two quarters, the liaison role ends, and the director reviews forum participation.

4. The Rival Response

Mandating forum use has real advantages: it is quick, consistent with company practice and ends the bottleneck immediately. Its risk is that it removes the route the engineers trust while leaving the forum as it was. The likely result, on the evidence of the first months, is fewer questions asked at all, with errors found later in design reviews rather than earlier in conversation. It would also signal that the acquired team's ways are a problem to be corrected, which Ranft and Lord's work suggests can drive away key people whose knowledge the acquisition was meant to secure.

5. When This Recommendation Fails

The recommendation fails if the liaison becomes permanent in practice, if the former manager uses the role to preserve the team's separation, or if forum participation does not rise as categories move. The director will know by the end of the first quarter: if fewer than half the questions in the moved categories are posted directly, she should reconsider and, if needed, move to the mandate with the forum's problems fixed first.

References

Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. https://doi.org/10.2307/2666999

Graebner, M. E. (2004). Momentum and serendipity: How acquired leaders create value in the integration of technology firms. Strategic Management Journal, 25(8-9), 751-777. https://doi.org/10.1002/smj.419

Ranft, A. L., & Lord, M. D. (2002). Acquiring new technologies and capabilities: A grounded model of acquisition implementation. Organization Science, 13(4), 420-441. https://doi.org/10.1287/orsc.13.4.420.2952