22
Fri, Nov
1 New Articles

Overcommitting (or I'm Just a Girl/Boy Who Can't Say No)

Commentary
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

I first became aware of overcommitment early in my professional career when I was writing a program in an awkward, now obsolete language called Table Processor. I was having trouble getting the program to compile, much less run, and with my deadline looming like a hungry predator, I went to my manager for assistance. I explained my failings with exemplary contriteness and was prepared to recite a litany of mea culpas. But my manager interrupted me and said, “Don’t worry. Give it to Robert. He’ll take care of it.”

Now, Robert was a first-class programmer and our best (and only) systems analyst. In his spare time, he doubled as our communications expert and supported off- shift operations by fielding many a midnight phone call. He would have been my first choice for consultation, but any idiot could see he was busier than God during the first six days of creation. In any event, I felt guilty disturbing him with my problem since he had plenty of his own and I knew he was already under enough pressure to make a tea kettle moan. So I mentioned to my manager that, seeing as how Robert was busy and all, perhaps someone else could assist me. I remember how my boss abruptly stopped scanning the papers on his desk, looked up, and smiled slyly. He examined me over his glasses in apparent amusement, perhaps at my naivete, and said, “Son, if you want to get something done, always give it to the busiest person.”

Aha! A learning moment. Of course. It made perfect sense. Those who were competent and willing would always be swamped. Those who sat around with not much to do (like me at the time) probably either hadn’t yet developed their skills sufficiently or had offered them so grudgingly that they were seldom asked to do more. Busy, I realized, begets busy.

Everywhere I worked after that, there seemed to be a handful of people who did everything. They accepted every task and patiently answered every question no matter how many times it had been asked before. They worked grindingly long hours, and what spare time they had was often filled with work they took home. They were sometimes frazzled, usually tired, and occasionally resentful. But they never said “no.” In so doing, they trained everyone else to become dependent on them. And with increased dependence came increased demands. At times, without being fully aware of it, their management and

coworkers took merciless advantage of them. They had, in a sense, become casualties of their own capability and good nature.

The paradox is that overcommitters are typically ultra-competent people who are in control of just about everything except their own motivations. The potent and complex fuel mixture that propels overcommitment is usually blended in childhood. By the time it manifests itself in adulthood, it typically contains some combination of desires to please, placate, or prove oneself.

Pleasing, placating, and proving have closely related characteristics. First among them is searching for approval from the outside. The giving up of self for the approval of others is, of course, an unending process and, for the seeker, ultimately ungratifying. Each new commitment holds the false promise of esteem but is soon replaced by the next and the next. Like Egyptian pyramid builders, overcommitters will work until they drop. Sometimes literally. Their self-worth is tied to doing, rather than being. They can be counted on to be compliant and to play by the rules. They are the backbones of many an understaffed organization.

Overcommitment may also stem from a lack of trust in the ability of others and the belief that if you want something done right, you have to do it yourself. First-time managers will frequently find themselves overcommitted, having not yet discovered the emancipation of delegation.

Another type of overcommitment is frequently practiced by highly gifted people who thrive on constant stimulation. Not by coincidence, many such people are drawn to careers in Information Technology (IT), where change is as predictable as political scandal. They progressively agree to take on more and more responsibility but will only work on a given task full-heartedly until it ceases to be interesting. Once bored, they start looking for the next challenge, the next operating system, the next exciting gadget to configure. Like inquisitive tornadoes, they move through the workscape looking for new domains to chew up, leaving a junkyard of partially completed projects in their wash. They cringe at the prospect of performance measurements and rebel against restrictions.

In their quest for the creative challenge, they overlook the possibility that any activity becomes creative when you commit to doing it better than you did it before.

Whichever variety of overcommitment you practice, all of the stresses, pressures, and burn-out common to those who slavishly assume unwarranted obligations can be attributed to the inability to utter a single word: no. It is a failure to set boundaries, to define limits, and, in some cases, to focus on a task through to completion. It may also evidence a refusal to properly care for oneself. Many overcommitters I know run on caffeine, eat quickly rather than nutritiously, and sleep marginally.

Saying “no” is an acquired skill and, like any skill, requires practice and repetition. A simple place to start is to say no to project B until you have completed project A. Time can also be a delimiter—commit to no more than can be accomplished in a single business day. Informing your coworkers that you are intent on interrupting the overcommitment cycle will help them understand the new word in your vocabulary. It may also temper the volume of their requests.

The inability to say “no” has many prices, not the least of which is that it becomes the onramp to resentment. Years of saying “yes” when you mean “no” exacts a toxic toll. Resentment is like swallowing poison and expecting the other person to die—not very effective as an outcome.

The results of all of this are both good and bad. Obviously, the world would run much differently without overcommitters. Lots of stuff wouldn’t get done. But lots of stuff doesn’t get done anyway because overcommitters frequently give an incongruent “yes” to new responsibilities they know they cannot possibly assume. As a result, overcommitters are often left with feelings of failure and disappointment when the impossible fails to happen. They may also be targets for the discontent and frustration of coworkers who were promised things that were not delivered. To compensate, the skillful overcommitter will redouble his efforts by overcommitting anew.

While in the process of learning to say “no,” prioritization will help set reasonable limits. Draw a nine-square grid like the one shown here.

All incoming tasks will fall into one of the nine squares. Obviously, PRESENT/URGENT tasks get top priority. FUTURE/TRIVIAL should not even be on the radar screen. In fact, only four blocks on the grid should occupy your attention: PRESENT/URGENT, PRESENT/ IMPORTANT, PENDING/URGENT, and PENDING/IMPORTANT. The rest you can ignore unless they move up the priority ladder by virtue of your having completed all other tasks.

When a project request comes in, ask the requestor to help prioritize it. Yes, people tend to think that their tasks are more important than the next person’s, but a realistic prioritization can be negotiated. In cases of impasse, ask your manager to act as a mediator. If uncertain, check to ensure that your priority list matches your manager’s. If you accept a task, commit to seeing it through to the end.

Managers can help by having clearly defined job descriptions that are frequently updated based on changing job requirements and new technologies. Compare job descriptions with what employees are actually doing and adjust where necessary. Managers can also deliberately begin to ease their dependence on “the busiest people,” staff up where necessary, and distribute the workload more equitably.

On the surface, it would appear that overcommitters are self-starters who seem to need little supervision. The opposite, in fact, is true: They need help focusing on the priority at hand, which for some may be a casual reminder (“Remember, we agreed you’d have the report finished by Wednesday.”) and for others, a weekly review of assigned tasks. Perhaps most important is this: Employees with a history of saying “yes” will need a manager’s backing to say “no.”

In the final analysis, overcommitment is a habit, and it will require time to reframe. Unraveling the motivation behind the behavior is always helpful but is particularly challenging for overcommitters because it requires them to stop and reflect. People who pack so much into every moment are often afraid to stop. A busy life is not necessarily a purposeful life, and self-immolation is sometimes preferable to self-examination.

Whatever the trials that accompany overcommitment, as a manager I always preferred overcommitters to undercommitters: The former are employees who work hard but are a challenge to direct; the latter drift without direction, seeking neither challenge nor exertion. The important word in overcommitment, after all, is commitment.

Urgent

Important Trivial

Present

Pending

Future

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: