"So what about Marigold?" Sara asked. She and Karl were concerned that Wolf would argue for trying to fix Marigold first, before even looking at their proposal for Metronome. But Karl had an idea.
"Maybe we don't say anything about Marigold. Suppose we critique a third idea — not Marigold — that looks at least as good as Wolf's. Then we're not arguing against Marigold, and it's a lot less personal. But it still raises questions about his approach."
Sara was impressed. "Yes, and if Metronome is an even better idea, it might be easier to turn the discussion back to Metronome. Interesting…"
Karl and Sara are devising one of the key elements of any proposal — the discussion of alternatives. By demonstrating the advantages of their proposal relative to all plausible alternatives, they effectively turn attention to the approach they're advocating.
Here are the key elements of an effective proposal. Some might not apply in your situation, so be selective.
- What's the issue?
- What issue does your proposal address? Present the issue from your management's perspective. Stick to one issue — complexity is a demotivator.
- What's the impact?
- What was the impact of this issue on a current or recently completed project? Did it affect schedules? Budgets? Relationships? Customers?
- What's the impact of inaction?
- Project what will happen if this issue isn't addressed effectively. Estimate budget and schedule effects, showing how the issue affects future or current projects. Estimate the financial costs and lost revenue associated with these factors, going forward quarter by quarter, for three years.
- Where will the impact be greatest?
- All projects To effectively advocate
for a position,
understand first
what your audience
cares about.
Let that drive
everything else.are unique. What kinds of projects are most likely to be affected by this issue? Rank project types by impact, and estimate schedule, budget, and revenue consequences. This is especially persuasive if your proposal helps favored projects or customers. - Are there alternatives?
- Every problem has multiple solutions, and no solution is best all around. Explore the advantages and disadvantages of three alternatives. Include financial consequences. This is the piece that Karl and Sara are working on.
- What do you recommend?
- Of the alternatives you explored, which one are you proposing and why? Take a position and defend it.
- What should we do next?
- Assuming that your proposal is adopted, what's the next doable step? Sketch a plan for implementation, including a schedule with milestones, and a budget. Include a risk plan.
- Who should do it?
- Who would work this plan, and how much of their time would be required? Are consultants involved? New hires?
- How will we know if we succeed?
- What criteria determine success? Will we need resources to determine success? How much? When?
Do you have a rejected proposal in a file somewhere? Dig it out. How many of these key elements were covered? Can you see ways to improve it? Top
Next Issue
The article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More
Your comments are welcome
Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend me your comments by email, or by Web form.About Point Lookout
Thank you for reading this article. I hope you enjoyed it and
found it useful, and that you'll consider recommending it to a friend.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
Related articles
More articles on Personal, Team, and Organizational Effectiveness:
If Only I Had Known: I
- Have you ever regretted saying something that you wouldn't have said if only you had known just one
more little fact? Yeah, me too. We all have. Here are some tips for dealing with this sticky situation.
Remote Facilitation in Synchronous Contexts: I
- Whoever facilitates your distributed meetings — whether a dedicated facilitator or the meeting
chair — will discover quickly that remote facilitation presents special problems. Here's a little
catalog of those problems, and some suggestions for addressing them.
Accepting Reality
- Those with organizational power can sometimes forget that their power is limited to the organization.
Achieving high levels of organizational and personal performance requires a clear sense of those limits.
Virtual Clutter: I
- With some Web searching, you can find abundant advice for decluttering your home or office. And people
are even thinking about decluttering email inboxes. But the problem of clutter is far more widespread.
Improvement Bias
- When we set about improving how our organizations do things, we expose ourselves to the risk of finding
opportunities for improvement that offer very little improvement, while we overlook others that could
make a real difference. Cognitive biases play a role.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming July 16: Responding to Unwelcome Events
- Unwelcome events have two kinds of effects on decision-makers. One set of effects appears as we respond to events that have actually occurred. Another set manifests itself as we prepare for unwelcome events that haven't yet occurred, but which might occur. Making a wrong decision in either case can be costly. Available here and by RSS on July 16.
And on July 23: Microdelegation
- Microdelegation is a style of delegation in which the delegator unintentionally communicates the task to the subordinate in such detail and so repetitively that the subordinate is offended. As a result of this delegation style, many subordinates feel distrusted or suspected of fraud or goldbricking. Available here and by RSS on July 23.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed

- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.
- More