Marigold was now hopelessly late, which is why Andrew was now sitting in Jane's office, asking for advice. "So you think asking Emmons for help is the way to break the news," he said.
"Yup," said Jane. "Worked for me."
Absorbing this, Andrew realized that Jane probably knew how to go about it. "OK, but how can I make sure we get the help we need, and not what he thinks we need?"
"Easy," Jane said, "you do your homework first. Show him what's going on and why, compressing it to keep his attention while you lay out the story. You have to make it interesting."
"Sounds good, but how?"
"Start by asking him for ten minutes — that should be enough. Then you lay out the headline, and go from there."
Jane has just given Andrew three of the keys for asking for help successfully. Here are ten tips for asking for help.Work with your peers
before you go upwards
in the organization
- Do everything you can do first
- Ask for help only after you've done what you can in your own circle of autonomy. Work out whatever you can with your peers before you go upwards in the organization.
- Choose your forum
- If your needing help would be embarrassing to you or to anyone you ask for help, think carefully about the forum in which you make the request. Be discrete.
- Ask permission
- Work out a mutually agreeable time and setting for making your request.
- Ask early
- The temptation to delay is strong, because we often hope that the problem will resolve itself. Resist temptation. If you wait until panic sets in, you risk foreclosing options.
- Deliver the headline first
- Begin with the big idea — don't build up to it. For instance, Andrew could say, "Marigold will be late, and I need your help."
- Organize your options
- Have in mind at least a couple of kinds of help. The third one can always be: "Can you suggest something else?"
- Have a clear objective
- Define the problem, and then describe the solution you have in mind. Whether you need advice, expertise, or resources, ask for it specifically. Be clear, but be open to alternatives.
- Explore alternate solutions
- Be prepared to justify the solution you've selected, but be ready to explore alternatives. People tend to feel uncomfortable about helping the unprepared or the narrow-minded.
- Make it interesting
- Present your problem in an intriguing way. You'll be presenting a solution, too, so touch hot buttons that will intrigue the listener.
- Use what you get
- Because rejecting or ignoring help you've asked for can create real problems, be prepared to accept the help that's offered.
Why is asking for help, or remembering that we can ask, so difficult? How can we make it easier? Read about it.
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 welcomeWould you like to see your comments posted here? rbrenBOsYucoVRdyJIOrYner@ChaclaKETLgdPHzWgQQIoCanyon.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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- Diagonal Collaborations: Dazzling or Dangerous?
- Collaborations can be very productive. There are some traps though, especially when the collaborators
are of different rank, with the partner of lower rank reporting to a peer of the other. Here are some
tips for preventing conflict in diagonal collaborations.
- Take Any Seat: I
- When you attend a meeting, how do you choose your seat? Whether you chair or not, where you sit helps
to determine your effectiveness and your stature during the meeting. Here are some tips for choosing
your seat strategically.
- How to Procrastinate
- You probably know many techniques for procrastinating, and use them regularly, but vociferously deny
doing so. That's what makes this such a delicate subject that I've been delaying writing this article.
Well, those days are over.
- Mitigating Outsourcing Risks: II
- Outsourcing internal processes exposes the organization to a special class of risks that are peculiar
to the outsourcing relationship. Here is Part II of a discussion of what some of those risks are and
what can we do about them.
- The Artful Shirker
- Most people who shirk work are fairly obvious about it, but some are so artful that the people around
them don't realize what's happening. Here are a few of the more sophisticated shirking techniques.
Forthcoming issues of Point Lookout
- Coming May 23: Narcissistic Behavior at Work: IX
- An arrogant demeanor is widely viewed as a hallmark of the narcissist. But truly narcissistic arrogance is off the charts. It's something beyond the merely annoying arrogance of a sometimes-obnoxious individual. What is narcissistic arrogance and how can we cope with it? Available here and by RSS on May 23.
- And on May 30: Chronic Peer Interrupters: I
- When making contributions to meeting discussions, we're sometimes interrupted. Often, the interruption is beneficial and saves time. But some people constantly interrupt their peers or near peers, disrespectfully, in a pattern that compromises meeting outcomes. How can we deal with chronic peer interrupters? Available here and by RSS on May 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenWLjdsFswCZmSqXUkner@ChacBzmSMAhJgfgYmEkqoCanyon.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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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 words in your inbox in one hour. License any article from this Web site. More info
- Technical Debt Management: Making the Business Case
- This program
outlines the steps necessary for deploying a program for rational management of technical debt. For
many organizations, adopting a program for rationally managing technical debt entails organizational
change. And unlike some organizational changes, this one touches almost everyone in the organization,
because technical debt isn't merely a technical problem. Technical debt manifests itself in technological
assets, to be sure, but its causes are rarely isolated to the behavior and decisions of engineers. We
can't resolve the problem of chronically excessive levels of technical debt by changing the behavior
of engineers alone. Technical debt is the symptom, not the problem. In this program we outline the essential
elements of an effective business case for adopting a rational technical debt management program. But
this business case, unlike many business cases, cannot be captured in a document. We must make the case
not only at the leadership level of the organization, but also at the level of the individual contributor.
Everyone must understand. Everyone must contribute. We explore five issues that make technical debt
so difficult to manage, and develop five guidelines for designing technical debt management strategies
for the modern enterprise. Read more about
this program. Here's a date for this program:
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield,
Illinois 62701: June 12,
Monthly Meeting, Central
Illinois Chapter of the Project Management Institute. Register now.
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield, Illinois 62701: June 12, Monthly Meeting, Central Illinois Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: The Power of Agile Development
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough. Lessons abound. Among the more important
lessons are those that demonstrate the power of the agile approach to project management and product
development. Read more about this program. Here's
a date for this program:
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227:
Monthly Meeting, Cincinnati
chapter of the International Institute of Business Analysis. Register now.
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. Register now.
- The Power Affect: How We Express Our Personal Power
- Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.