Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 16, Issue 18;   May 4, 2016: Just-In-Time Hoop-Jumping

Just-In-Time Hoop-Jumping

by

Securing approvals for projects, proposals, or other efforts is often called "jumping through hoops." Hoop-jumping can be time-consuming and frustrating. Here are some suggestions for jumping through hoops efficiently.
Magic Lantern Slide of a dog jumping through a hoop

A Magic Lantern Slide of a dog jumping through a hoop, ca. 1830. The metaphor about "jumping through hoops" is a reference to circus acts like this. Courtesy U.K. National Media Museum via Flickr, artist unknown.

In many organizations, bureaucracy consists of people, policies, and procedures that focus organizational resources on reaching accepted objectives. Bureaucracy can also be an unnecessary obstacle, but that's a topic for another time. For now, let's focus on how to operate within bureaucracy to get our work done with minimal frustration and wasted effort.

One approach might be what I call Just-In-Time Hoop-Jumping, which means deferring preparations for jumping through a given hoop until the time is right.

For example, if you're preparing a project plan for a sequence of reviews by sponsors, managers, and governance boards, you know that some of these folks review only parts of the plan. Others review the entire plan piecewise in a set of mini-reviews. Some review items only after others have reviewed them, and so on.

The straightforward approach to final approval involves developing the entire plan and submitting it to reviewers, in turn, making adjustments after each review. But Just-in-Time Hoop-Jumping often produces better results, because you develop in detail only enough of the work to meet the requirements of the next reviewer along the path to final approval.

Of course, a clear view of that entire path is necessary — including answers to any questions that any reviewer might ask. But it isn't necessary to have those answers in final form until you reach the point where they might be asked.

Here are three guidelines for implementing Just-In-Time Hoop-Jumping.

Synchronize your work to your audiences
On the path to final approval, you'll probably face a sequence of different audiences. Be certain that your work meets the needs of each audience, but complete treatment of each part of the work is necessary only for the part to be reviewed by that audience. Sketchy versions of portions to be reviewed by later audiences might be adequate for now.
Break your task into layers
As you progress, How can you operate within bureaucracy
to get your work done with minimal
frustration and wasted effort?
expectations for completeness and sophistication of the work increase. Meet those expectations. But going beyond what's necessary at any one stage exposes you to the risk that the above-and-beyond part might need rework if elements it depends on undergo change. Develop the effort in detail no more than is required for a particular stage of the review process.
Use modularity to manage the risk of rework
Understanding the standards to be applied at any stage of the process is a given. But you can limit the impact of failure to satisfy a reviewer by limiting the interactions between modules of the work. By making the modules of your proposal independent, you can reduce the work required to bring the entire work into compliance when one module changes.

Just-in-Time hoop-jumping can feel wrong and risky at first, but that's where the advantage comes from. It gives you time to focus your effort on the parts that matter most right now. Go to top Top  Next issue: Characterization Risk  Next Issue

Go For It: Sometimes It's Easier If You RunLove the work but not the job? Bad boss, long commute, troubling ethical questions, hateful colleague? This ebook looks at what we can do to get more out of life at work. It helps you get moving again! Read Go For It! Sometimes It's Easier If You Run, filled with tips and techniques for putting zing into your work life. Order Now!

Your comments are welcome

Would you like to see your comments posted here? rbrenYILqGkwvWtqcKFNmner@ChacbqEGxYfukQQjRHjLoCanyon.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.

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:

The Boott Cotton Mills and Eastern CanalThere Is No Rumor Mill
Rumors about organizational intentions or expectations can depress productivity. Even when they're factually false, rumors can be so powerful that they sometimes produce the results they predict. How can we manage organizational rumors?
Tenacious under full sailThe Solving Lamp Is Lit
We waste a lot of time finding solutions before we understand the problem. And sometimes, we start solving before everyone is even aware of the problem. Here's how to prevent premature solution.
The Johari WindowAssumptions and the Johari Window: I
The roots of both creative and destructive conflict can often be traced to differing assumptions of the parties to the conflict. Working out these differences is a lot easier when we know what everyone's assumptions are.
An informal meeting geometryPreventing Sidebars
Sidebar conversations between meeting participants waste time and reduce meeting effectiveness. How can we prevent them?
North Fork Fire in Yellowstone, 1988The Risks of Too Many Projects: II
Although taking on too many projects risks defocusing the organization, the problems just begin there. Here are three more ways over-commitment causes organizations to waste resources or lose opportunities.

See also Personal, Team, and Organizational Effectiveness and Project Management for more related articles.

Forthcoming issues of Point Lookout

Jeffrey Skilling, in a mug shot taken in 2004 by the United States Marshals ServiceComing 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.
The end of the line for a railroad trackAnd 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.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendDQyslVPXLaSIcaQner@ChacGcWPhiTWYkMtuIatoCanyon.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:

Reprinting this article

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

Public seminars

Technical Debt Management: Making the Business Case
This Technical Debt Management: Making the Business Caseprogram 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:

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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:

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople 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.

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.