We are re-posting here, with permission of GTDTimes, the second part of a series that Monica is authoring on more effective decision-making at work. Enjoy this article and look for the following sections coming soon!
Getting Decisions Made Part 2: The Meaning of ‘Yes’
Editor’s Note: Monica Enand, the author of this series, developed a passion for improving personal productivity through improved decision management after countless experiences where the stress and inefficiency of organizational decisions frustrated her. She has worked for more than 16 years in large corporations such as Intel and IBM as well as multiple start-ups. As a writer and speaker, Monica has focused specifically on educating people about how to get better results in their own decision making processes. Currently, she is the CEO of Zapproved, an online decision management system she created to help today’s worker overcome this challenge.
In Part 1 of this series on Getting Decisions Made, we focused on creating the proposal that will be sent to others. As in most things, proper preparation is crucial to success. Once you’ve thought through what to ask, honed your words and pulled together the right information, it’s time to share it with others.
Now the key question is focusing on the meaning of what agreement means. If someone says “yes” what exactly will the action be? This post will explore the need for clarity about results and responsibilities so that once consensus is achieved, everyone is on the same page and can execute efficiently.
The most common mistake in getting decisions made is not properly thinking through what outcome is desired by the requester. Sure, people ask for things, but they do it without using empathy for the others involved. Too often, the result is a muddled request that isn’t actionable, or at least, not as actionable as it should be to ensure the team’s success.
After you’ve followed the START process outlined previously, you should have the scope of the proposal tightly defined and the data gathered. Now let’s make sure it is formatted in a way that will respect the opinions and time of your team.
Don’t Bury the Lead
When putting a proposal together, I suggest a technique used in journalism called the “inverse pyramid.” The idea is that the information is organized with the most important content first and then the rest appears in descending order of importance.
Now this isn’t always practical, but the idea of putting the “ask” right up front is critical for driving action. If you want the recipient to act quickly, then you need to deliver the key information up front. How can someone respond in two minutes if it takes them that long to even know what you want?
A strong, actionable lead sentence can make all the difference. You will get action when you write an opening like this:
The purpose of this message is to request your approval by this Friday to proceed on the proposed marketing initiative to grow our customer base in Asia. The plan for this year will cost $2.2M and is projected to grow our market share from 4% to more than 15% in that region resulting in sales exceeding $25M.
In this short sample, some key ideas stand out. The recipient knows immediately what is being asked and what the agreement under consideration is. It’s right there in the first 25 words. The next sentence adds another layer of information about the expected results backed up with data. This signals immediately that what follows has been well thought out and helps others trust the information.
Not every decision is this big or expansive, but whether it is launching a multi-million dollar marketing campaign or buying a laser printer for the office, the clarity of communication and organization of information plays a key role in success. It takes a little practice but the results quickly make it a habit.
Ask for Decisions, Not Opinions
In the sample paragraph above, there was a subtle yet important point that we’ll turn to. The first line said “request your approval.” From that simple phrase it is clear what is being sought, as well as the fact that the request is an “approve/deny” choice.
Working within groups gets messy when key decisions are made and they are open-ended. Occasionally, the group comes together and into a coherent and clear decision. Oftentimes, though, a long back-and-forth of emails ensues that does little more than fill up inboxes.
Use clear, focused language and build the proposal in a way that let’s people respond quickly. Avoid phrases like “What do you think?” or “Give me your feedback.” They lack clarity of purpose and invite others to take the conversation in different directions. After some time, people fatigue from the exchange which usually results in getting nothing done.
Even if someone denies the proposal, the format of the question will compel them to explain their reasoning. This is invaluable because otherwise their objections may remain masked which will cause friction and interfere with progress. Getting a “no” isn’t always a bad thing, plus it gives you something to react to rather than allowing dissenters to hide behind passive techniques like stalling.
By focusing some thought in presenting the proposal, you can stand out within your team by actually making them more efficient and effective. In my experience, those colleagues always stand out by being able to accomplish more with less friction.
You’ve got all the information and it is presented in a clear, actionable format. Part 3 will focus techniques for choosing who to include and not include in a decision so that you get more done as a team.