Turn a Strategic No into a Change in the Work

Oracle, 1997. Ray Lane, Oracle's president, had promoted me to run application sales for any company over $1 billion west of the Mississippi and into Asia. I was 27, and almost everyone on my team had more experience than I did. Then I got the call from Bechtel's procurement officer. He was watching my team try to have side conversations with him. At the same time, the technology sales executives were having their own side conversations with him, specifically to change who got credit within Oracle. Two Oracle teams, one customer, competing against each other instead of selling. The fight over credit had become part of the customer's experience.

Ray Lane had a simple rule: a dollar is a dollar. Adding more names to a deal did not create more commission dollars for Oracle to pay. The available commission had to be divided under a defined credit rule, with the same total payout regardless of how many people joined the deal. Mike Deceaser, my counterpart on the technology side, and I had to turn that principle into rules the field could use on a live deal, with no playbook. That meant taking money out of people's wallets. When an application rep got credit and a technology rep did not, that rep did not get paid, their manager did not get paid, their manager's manager did not get paid. There were no easy conversations. Deal by deal, the conversations hardened into rules: the applications team led application deals, the technology team led database deals, and before a deal started the teams agreed on the supporting work each would do and how the credit would be split. We held the split every time, including when a good rep with a real customer had a tempting reason for an exception. Mike and I had no authority over Oracle's compensation policy, only our own deals and our own teams, and that was enough to build the rule. Customers saw one Oracle. We won the Bechtel deal.

A no changes nothing until it changes a budget, a workload, or a rule. Cava announced its acquisition of Zoe's Kitchen in August 2018: 66 restaurants acquiring 261. It did not stop operating Zoe's at closing. It tested conversions first: eight through the end of fiscal 2020. Its IPO prospectus reported significantly stronger financial results after conversion, and Cava accelerated. Cava ultimately converted 153 former Zoe's locations. That was not all of the original 261, and the reported conversion total does not account for every location. A transition can take years and still have a clear destination, as long as it has a sequence, resources, milestones, and an end condition.

Microsoft shows why a new priority also needs a stop decision. Satya Nadella became CEO on February 4, 2014. Fifty one days later he introduced Office for the iPad, on a device Microsoft did not control. The costlier change came in phones. Microsoft closed its acquisition of Nokia's phone business less than three months into his tenure. In July 2015 it announced plans to eliminate up to 7,800 positions, and later that month it reported a $7.5 billion impairment related to that business. Changing direction meant owning both consequences. In a 2018 McKinsey interview, Nadella described the change behind the strategy: shared leadership metrics that combined revenue and profit with measures of usage and customer satisfaction, and sales compensation that moved beyond a single license sale or booking to include actual consumption. The company was changing what people were rewarded for. The lesson is to give the chosen priority room in the business, not add it to a list where everything still has equal protection.

Then the no inside the product. At Rightsline, Warner Brothers asked us to take on physical asset management. It ran against our focus, and it was a market moving too fast for us to compete in. We chose not to solve it. That no kept the team on the rights and royalty work Rightsline existed to do.

The No List, specific enough to change spending and behavior. Beside it, three records you use only when their problem appears: the Two-Future Test, the Exception Ledger, and the Sequence Conversion.

If you set the priorities, end the next priority session with one authorized stop, decline, or conversion, the capacity it frees, and the evidence that would reopen it. "We need more focus" is not a decision. If you cannot stop the work yourself, show the person who can what the competing commitments are costing the chosen priority, and ask for a decision by a date. If you are the one absorbing every exception because you are the person who can, say what finishes before the exception starts, and who authorized it. The few people everyone already depends on are where unfunded yeses land.

If you run a team, your no is the exceptions you stop granting.