What Leaders and Managers Can Learn from Farsighted

When a leader considers a reorganization or a big policy change, the natural focus is on the org chart square directly involved. But a change to one team ripples into hiring plans, morale in adjacent teams, and relationships with external partners who work with the people affected. Before finalizing a plan, map out everyone and everything the decision touches, not just the department whose name is on it.

A manager decides to merge two teams to cut overhead, mapping only the reporting lines and the immediate cost savings. They don't map the effect on a long-running client relationship that depended on one specific team's continuity, and the account nearly walks within the quarter.

For any decision affecting more than one team, list every group, process, and external relationship it touches before drafting the plan.

Leaders tend to plan for the smooth version of a change — the one where the announcement lands well and everyone adjusts quickly. A more useful habit is sketching a few different ways the change could unfold, including the version where key people push back or leave, and having a rough response ready for each.

A director announces a new performance review process assuming it will be welcomed as fairer and more transparent. She never imagined the scenario where senior staff read it as a signal of distrust, and by the time pushback arrives, there's no plan beyond defending the original announcement.

Before rolling out a significant change, write down two or three different ways people might react to it and prepare a response for each.

The higher you sit in an organization, the harder it becomes to hear disagreement, because people calibrate what they say to you based on your authority over them. Before locking in a major decision, deliberately seek out someone positioned to disagree — a peer in another department, someone leaving the company, or a subordinate you've explicitly told it's safe to contradict you.

A leadership team decides on a new policy after discussing it only among themselves in a room where everyone already reports up to the same person. Nobody voices the objection that frontline staff raise within a day of rollout, because nobody in the room had frontline exposure.

Before finalizing a major decision, ask one person you don't manage and who has no reason to simply agree with you what they think is wrong with the plan.

Most organizations move from one initiative to the next without ever writing down what leaders actually expected and comparing it, later, to what happened. Keeping a plain record of your reasoning at decision time — and revisiting it after the outcome is known — is what turns one decision into useful preparation for the next one, rather than a memory that gets rewritten in hindsight.