I Agreed to a Deadline That Was Impossible from the Start - How to Estimate Work Realistically, Communicate Risk, and Renegotiate Dates Before an Ambitious Plan Turns into a Weekend in Excel ebook

Cover

I Agreed to a Deadline That Was Impossible from the Start

How to Estimate Work Realistically, Communicate Risk, and Renegotiate Dates Before an Ambitious Plan Turns into a Weekend in Excel

Max Paradox

PROBLEM? RELAX. YOU'VE GOT THIS!

ISBN: 978-83-8483-832-7

ALL-IN Rafał Płonkowski

Table of contents

Title page

INTRO

Chapter 1 - The Most Expensive Word in Business Is Yes

Chapter 2 - Four Hours of Work, Three Weeks to Deliver: Where the Missing Time Goes

Chapter 3 - The Magic of One Date: How Guesses Become Official Commitments

Chapter 4 - More Meetings, Less Sleep, and Other Brilliant Ways to Rescue a Broken Schedule

Chapter 5 - Everything Is Urgent, Nothing Gets Finished: The Hidden Cost of Doing Too Much at Once

Chapter 6 - It's Just One Tiny Change: How Scope Creep Eats the Deadline

Chapter 7 - Waiting on Someone Else: How Dependencies Hijack Your Deadline

Chapter 8 - Everything's Green Until It Isn't: Spotting Trouble Before the Deadline Breaks

Chapter 9 - Estimating Without a Crystal Ball: How to Put a Number on Work You Haven't Done Yet

Chapter 10 - From Estimated Hours to an Actual Deadline: Building a Schedule That Can Survive Reality

Chapter 11 - The Warning Nobody Wants to Hear: How to Communicate Risk Without Starting a War

Chapter 12 - The Deadline Conversation You'd Rather Avoid: How to Renegotiate Without Losing Credibility

Chapter 13 - Can We Make It Faster? The Real Price of Accelerating a Project

Chapter 14 - Everyone Says They're Ready: Getting Different Departments to Deliver the Same Project

Chapter 15 - When the Deadline Cannot Move: Making Sensible Decisions Against an Immovable Clock

Chapter 16 - The Deadline Has Already Passed: How to Recover Without Making Another Impossible Promise

Chapter 17 - Accountable for the Deadline, but Not in Charge: Managing Work Without the Authority to Make It Happen

Chapter 18 - The Same Deadline, the Same Disaster: Turning Hard Lessons into Better Habits

Chapter 19 - Here We Go Again: Spotting the Return of Bad Deadline Habits Before They Take Over

Chapter 20 - A Deadline You Can Put Your Name On: Learning to Promise What You Can Actually Deliver

Landmarks

Cover

Title page

Table of contents

Start of content

INTRO

At 4:37 on a Thursday afternoon, someone asks a question that should come with a warning label: "Could we have the new reporting dashboard ready for next Wednesday?" You're sitting in a meeting with six people, three laptops, and a presentation containing an impressive number of arrows. The dashboard still needs data from two departments, several calculations haven't been validated, and the person responsible for testing is away on Monday. You know all this. You also know that everyone wants to finish the meeting. So you smile, nod thoughtfully, and say, "Yes, that should be doable." Congratulations. You've just converted a few seconds of social discomfort into a week of operational chaos. Somewhere in the building, an innocent spreadsheet has been sentenced to overtime.

The fascinating thing about impossible deadlines is how quickly they become official. One moment, a date is merely a suggestion made by someone who would appreciate an early result. A minute later, it appears in meeting notes. By Friday morning, it's on a project tracker. By Monday, somebody has promised the finished dashboard to senior management. Nobody has added resources, resolved dependencies, or checked whether the original estimate made sense. Yet the deadline has acquired the authority of a legally protected national monument. Questioning it now feels considerably more dangerous than questioning it when it was first proposed.

Why do intelligent, experienced people agree to commitments they already suspect are unrealistic? Usually, it isn't because they're incapable of estimating work. They want to be helpful. They want to appear competent, flexible, and commercially aware. Sometimes they're dealing with a demanding client or a manager who treats uncertainty as a character flaw. Sometimes they're simply optimistic about their own abilities. Saying yes creates immediate relief, while explaining a limitation risks an awkward conversation. Unfortunately, the relief belongs to the present version of you. The consequences are delivered to a future version who wasn't consulted and will have several legitimate complaints.

There's also a fundamental misunderstanding about how long work takes. We often estimate the time required to perform the most visible activity while ignoring everything needed to make that activity possible. Building a dashboard might require twelve hours of technical work, but the complete delivery also depends on obtaining reliable data, confirming business definitions, testing calculations, correcting errors, and securing approval. Twelve hours of effort can easily occupy several calendar days when information arrives in stages. If the necessary people have other commitments, the elapsed time grows further. A task doesn't become faster simply because someone describes it as urgent. Urgency is a priority signal, not a new unit of measurement.

Then we have the remarkable optimism built into most calendars. People plan as though every working hour is available for the project currently being discussed. Existing responsibilities, interruptions, conflicting priorities, and unexpected questions are treated as minor inconveniences that will somehow arrange themselves around the important deadline. One specialist is allocated to three projects simultaneously, each assuming nearly complete availability. On paper, everyone is fully utilized. In reality, the organization has invented a person who can occupy three chairs at once. Human resources departments have yet to develop a reliable recruitment process for this particular talent.

Even when the arithmetic is technically correct, the assumptions underneath it may be hopelessly optimistic. A schedule can contain beautifully formatted dates, carefully linked tasks, and a progress indicator displaying exactly 63 percent completion. None of those features establishes that the remaining work will fit into the available time. Precision and reliability aren't interchangeable. You can calculate a predicted finish date down to the minute while being completely uncertain about the approval required to start the next stage. The software isn't lying. It's simply calculating what you told it to calculate, with the refreshing indifference of a machine that will never have to explain the result to your client.

Of course, not every aggressive deadline is foolish. Businesses face genuine constraints. A product may need to launch before an important event. A customer may have contractual expectations. A decision may lose much of its value if the supporting analysis arrives too late. Ambition can encourage useful improvements, and pressure sometimes helps people concentrate on what matters. The difficulty begins when an ambitious target is presented as an achievable commitment without examining the trade-offs. If the date cannot move, perhaps the scope, sequence, resources, or delivery approach must change. Pretending that everything can remain fixed doesn't eliminate the conflict. It merely postpones the moment when someone has to acknowledge it.

Unfortunately, organizations have developed an impressive collection of techniques for postponing that moment. They schedule emergency meetings about productivity, demand more frequent progress reports, and ask already overloaded teams to demonstrate greater commitment. Occasionally these actions genuinely remove obstacles. More often, they increase activity without changing the underlying capacity. Employees spend additional hours explaining why they haven't finished work they could have been doing during those same hours. Eventually, overtime becomes the invisible ingredient that makes the official schedule appear successful. Management celebrates the delivery, and next month's plan quietly assumes the same extraordinary effort will happen again.

This book takes a different approach. You'll learn how to estimate work using evidence rather than instinct alone, how to recognize uncertainty without hiding behind vague excuses, and how to distinguish the time spent doing something from the date when it can realistically be finished. We'll explore why seemingly minor additions can overwhelm a project, why too many simultaneous priorities slow everything down, and how to recognize which activities genuinely determine the finish date. Most importantly, these ideas will become practical decisions you can make during ordinary working conversations, not elaborate theories requiring a dedicated planning department and a ceremonial meeting room.

You'll also learn to handle the conversations that make realistic planning difficult in the first place. Warning someone that a deadline is at risk shouldn't require a dramatic confession or a seventy-slide defense presentation. Useful communication identifies what's happening, what it could affect, which options remain available, and what decision is needed. Renegotiation works best when it offers a credible way forward rather than merely requesting more time. Sometimes the right outcome will be a revised date. Sometimes it will be a smaller initial delivery. Occasionally the responsible decision will be to acknowledge that the requested result cannot be achieved under the existing constraints.

None of this assumes that you control your entire working environment. Perhaps you're a project manager without authority over staffing, a specialist whose priorities change whenever a director calls, or a business owner trying to satisfy customers while protecting a small team's capacity. You may understand the problem perfectly and still be unable to change an imposed deadline. The goal isn't to grant you imaginary power over everyone else's decisions. It's to help you make your own commitments responsibly, communicate limitations clearly, and identify where someone with the appropriate authority must choose between competing demands.

You won't finish this book able to predict every delay or persuade every manager to appreciate realistic estimates. People will still change requirements, suppliers will still disappoint, and some meetings will continue to produce deadlines with almost supernatural confidence. What can change is your response. Instead of accepting a date because the room expects reassurance, you can examine the work behind it. Instead of waiting for a problem to become undeniable, you can raise it while useful choices remain. And instead of treating every missed target as a personal failure, you can distinguish poor decisions from genuine uncertainty.

So the next time someone asks, "Can you have it done by Friday?" remember that you don't have to choose between enthusiastic surrender and outright refusal. You can ask what needs to be delivered, check what is realistically possible, and offer an answer you can actually stand behind. That may not produce the most exciting moment in the meeting. But it could produce something considerably more valuable: a finished project, a credible commitment, and a Friday evening during which your laptop remains exactly where it belongs.

Preferably closed.

Chapter 1 - The Most Expensive Word in Business Is Yes

There is a peculiar moment in professional life when your mouth becomes considerably more ambitious than your calendar. Someone describes a task, mentions a deadline, and looks at you expectantly. You haven't checked the requirements, considered your existing workload, or spoken to the people whose cooperation you'll need. Nevertheless, you hear yourself saying, "Absolutely, we can make that happen." The words leave your mouth with impressive confidence. Your brain, which was apparently not invited to participate in the decision, begins reviewing the consequences approximately three seconds later. By then, the conversation has moved on. Someone is congratulating the team on its flexibility, and your new commitment is being entered into a project tracker. You have achieved an immediate social victory by creating a future operational problem. Business schools rarely advertise this particular management technique, although plenty of organizations appear to teach it informally.

Consider an account manager at a creative agency who receives a request from an important customer. The customer wants a complete set of materials for an upcoming trade exhibition: printed brochures, digital advertisements, product descriptions, and a short promotional video. During the conversation, the customer casually mentions that everything should be ready in ten working days. The account manager knows that the agency's design team is already busy, the video editor is finishing another campaign, and the customer hasn't supplied the final product information. Yet the account manager responds enthusiastically. After all, the customer is valuable, the opportunity is exciting, and nobody wants to introduce unpleasant arithmetic into a promising relationship. The agreement is celebrated as excellent customer service. Later, the production team receives the request and discovers that excellent customer service has apparently become a technical specification.

The immediate problem is not necessarily dishonesty. The account manager may genuinely believe that the agency can produce the materials. That belief might even be correct. What remains unexamined is whether the complete package can be delivered within the requested period, with the available resources and necessary approvals. These are different questions. Being capable of performing a task does not mean being capable of performing it by any date someone happens to suggest. A qualified chef can prepare an elaborate banquet, but asking for two hundred meals in fifteen minutes does not create additional ovens. Professional competence operates within practical limits. Unfortunately, agreeing to deadlines sometimes feels less like assessing those limits and more like demonstrating personal enthusiasm.

Why does this happen so easily? Because a request for commitment is rarely experienced as a neutral mathematical question. It often carries an unspoken social message: Are you capable? Are you supportive? Can I rely on you? Do you want this opportunity? We may hear all those questions simultaneously, even when the other person merely wants to know whether Thursday is feasible. Saying yes becomes a way to protect our professional identity. We want to be the person who solves problems rather than the person who immediately produces reasons something cannot be done. The difficulty is that confidence displayed before understanding the problem can become indistinguishable from recklessness. A willingness to help is valuable. A willingness to promise what hasn't been assessed is considerably less useful.

Organizations sometimes reinforce this behavior without intending to. During meetings, confident commitments may receive immediate praise, while careful questions are met with impatience. A manager who says, "We can deliver next week," appears decisive. Another who says, "I need to confirm two dependencies before accepting that date," may appear less energetic. Yet the second answer can demonstrate better control of the situation. The difference becomes apparent later, when the first manager must explain why next week has mysteriously become next month. Unfortunately, the praise and the consequences occur at different times. We receive social rewards for agreeing immediately, while the cost of an unrealistic promise is spread across future days, other people's schedules, and a collection of increasingly uncomfortable meetings.

There is also the pressure of silence. Imagine a senior executive asking whether a new customer onboarding process can be launched before the quarterly review. The question hangs in the room. Nobody wants to be the first person to express doubt, particularly if the executive has just described the initiative as strategically important. You can almost hear everyone's internal calculations. Perhaps it will work. Perhaps another team can help. Perhaps the missing requirements aren't complicated. As nobody objects, the proposed date begins to look more credible. Silence gradually transforms into apparent consensus. Eventually, someone says, "Sounds good," and the commitment becomes official. It is a remarkable form of decision-making in which everyone privately possesses reservations and publicly contributes to the impression that none exist.

A date suggested by an influential person creates another difficulty: it becomes an anchor. Once the executive says "the fifteenth," people tend to evaluate whether they can somehow fit the work before that day instead of first estimating how long the work should reasonably take. An estimate of eighteen days may suddenly feel excessive because the desired window contains only twelve. The conversation shifts from discovering the required duration to defending any number that exceeds the proposed target. The date may have been chosen for a perfectly reasonable commercial purpose, or simply because it creates a tidy slide in the quarterly presentation. Either way, it has acquired an influence on estimates that it doesn't necessarily deserve.

This doesn't mean that requested deadlines should be dismissed. Customers and managers often have legitimate reasons for wanting a particular date. Their needs should inform the discussion. The trouble begins when the desired outcome is confused with evidence that the outcome is achievable. If an executive needs the onboarding process before the quarterly review, that is an important business requirement. It tells you why the date matters. It does not tell you how much work remains or which resources are available. Both sets of information belong in a responsible decision. Treating a business priority as proof of execution capacity merely gives ambition a more impressive job title.

Sometimes the pressure comes from inside us rather than from the organization. We remember completing a similar assignment quickly and assume we can repeat the achievement. We want to prove ourselves after a promotion, impress a new customer, or outperform a competing department. Ambition can sharpen our concentration, but it can also make inconvenient details seem less important. We imagine an ideal sequence in which everyone responds promptly, the first draft is accepted, and unexpected requests politely postpone themselves until the project has finished. The scenario feels plausible because none of its individual assumptions is impossible. Unfortunately, a successful project usually requires several conditions to hold together, not merely one.

There is a particularly seductive variation of this mistake: promising results based on your personal best performance rather than your normal capacity. Perhaps you once completed a complex presentation overnight because the information was unusually clear and nobody interrupted you. That achievement may be worth celebrating. It does not establish overnight completion as a reliable standard for every future presentation. When exceptional performance becomes the baseline for commitments, ordinary working conditions start looking like failure. You eventually find yourself apologizing for delivering a perfectly reasonable amount of work because you once managed something extraordinary under exceptional circumstances.

The Commitment You Actually Made

One useful way to interrupt premature agreement is to distinguish acceptance of responsibility from confirmation of a deadline. These decisions can happen together when the work is familiar and the conditions are clear. They don't have to happen together when important information is missing. You can say, "Yes, we'll take this on. I'll confirm the delivery date after checking the requirements and our team's availability." That is a positive response, not a rejection dressed in administrative clothing. It tells the other person that the request is being taken seriously while protecting everyone from an unsupported promise. Adding a specific time for confirmation makes the response stronger. "I'll come back with a delivery proposal by 2 p.m. tomorrow" provides a useful commitment you can actually control.

The wording matters because vague caution can sound like avoidance. If you respond to every request with "We'll see," other people have little reason to feel reassured. A useful answer identifies what needs checking and when the decision will be made. The agency account manager, for example, could say, "We can prepare the exhibition materials. I'll check the video production schedule and confirm which customer inputs we need before committing to ten days." The customer learns that the request is being evaluated rather than ignored. The production team receives an opportunity to assess feasibility. And the account manager no longer needs to invent a new calendar system in which designers can complete several projects simultaneously.

Before accepting a meaningful deadline, it helps to understand what the other person believes will be delivered. "A complete campaign" can mean finished assets ready for publication, concepts awaiting approval, or files prepared for a production vendor. These distinctions matter because people often use the same words for different expectations. You don't need to interrogate the requester as though investigating a financial crime. A few precise questions can reveal whether the apparent agreement is genuine. What exactly must be ready? Who will approve it? Are the required inputs available? Is the requested date the final delivery or an intermediate review? Once those points are clear, the conversation becomes about a defined obligation rather than an optimistic impression.

A common obstacle is the requester who demands an immediate answer. "I don't need a detailed analysis. Just tell me whether you can do it." Sometimes the request genuinely requires speed. A customer may have to choose a supplier that afternoon. You cannot always insist on several days of investigation. But speed doesn't justify pretending certainty. You might distinguish what you can confirm from what still depends on verification: "We can commit to the brochure designs by that date using the existing materials. I can't confirm the finished video until we've checked editing capacity and received the approved script." The response may not be everything the customer hoped to hear, but it gives them information they can use.

There will also be situations where refusing or qualifying a commitment carries a genuine professional cost. A manager may dislike uncertainty. A client may select another supplier. A difficult workplace may reward compliance more consistently than candor. It's important not to pretend that better wording eliminates those pressures. Sometimes your choices are constrained, and you must decide how much risk to accept. Even then, distinguishing a target from a confirmed commitment helps. If someone imposes a date despite unresolved dependencies, you can document the assumptions and explain what must happen to make it feasible. You may not control the decision, but you can avoid silently transforming someone else's requirement into your own unsupported guarantee.

Another source of trouble is casual agreement after the initial commitment. The customer asks for one additional format, a slightly longer video, or another approval round. Each request sounds reasonable, so you accept it without reconsidering what was promised. Eventually, the assignment you are delivering bears only a passing resemblance to the one you estimated. The date, however, remains proudly unchanged. Recognizing this pattern requires noticing when an apparently small request alters the conditions of an existing promise. You don't need to renegotiate every minor correction. You do need to recognize when the accumulated work is no longer what both parties originally agreed to.

A practical habit is to confirm meaningful commitments in writing, using ordinary language. After a conversation, a short note might say: "We're preparing three brochure layouts and four digital advertisements for review next Thursday. Video delivery will be confirmed after the script is approved and editing availability is checked." This gives everyone a common reference point. It also reveals misunderstandings while they are still relatively inexpensive. Documentation should support clarity, not create a courtroom atmosphere in which every email sounds like potential evidence. If colleagues begin addressing you as "the aforementioned party," the process may have become slightly too formal.

The deeper change is learning to tolerate the brief discomfort of not immediately pleasing someone. A pause, a question, or a conditional answer can feel awkward in the moment. Yet that awkwardness is usually much cheaper than discovering later that several people have organized their work around a promise you never properly evaluated. Responsible confidence means being prepared to say what you know, what you need to verify, and when you can make a reliable commitment. It doesn't mean always giving the fastest possible answer.

The next time someone asks whether you can deliver an ambitious result, notice what happens before you respond. Are you evaluating the work, or managing the other person's impression of you? Are you thinking about the available resources, or remembering how pleased everyone looked the last time you agreed immediately? That brief moment of awareness can change the entire conversation. You can still be enthusiastic, commercially minded, and willing to take responsibility. You simply stop treating an attractive deadline as proof that it can be achieved.

A professional yes should mean that you understand the commitment and have reasonable grounds for accepting it. Anything less is an expression of hope wearing a business suit. Hope has its place in professional life, but it shouldn't be authorized to sign delivery schedules without supervision.

Chapter 2 - Four Hours of Work, Three Weeks to Deliver: Where the Missing Time Goes

A small heritage museum decides to create an audio walking tour for visitors. The idea is straightforward: six short recordings that people can listen to on their phones while exploring the town's historic buildings. The museum director asks the communications coordinator how long production will take. She consults the person responsible for audio editing, who replies that each recording should require approximately two hours of editing. Six recordings, twelve hours. Add a little time for uploading the files, and the director announces that the new tour can launch the following Friday. Everyone is pleased with the efficiency of the operation. Unfortunately, nobody has written the scripts, selected the narrator, secured approval of the historical descriptions, recorded the audio, or checked whether the visitor-facing links work. The editor's estimate was perfectly reasonable. The conclusion drawn from it was spectacularly unhelpful.

This is how a great many scheduling problems begin: someone estimates one visible piece of work, and the organization mistakes that estimate for the duration of the entire undertaking. The distinction isn't always obvious because everyday language makes activities sound wonderfully compact. We say "produce a video," "prepare a proposal," or "update the website" as though each phrase describes one continuous action performed by one available person. In reality, the finished result may depend on several different kinds of work, approvals, information transfers, and waiting periods. Some require concentrated effort. Others require no effort from your team at all, merely the passage of time while another person completes something essential. Both affect the delivery date.

The most important distinction is between effort and elapsed time. Effort describes the amount of actual work required, commonly measured in person-hours or person-days. Elapsed time describes the period between starting the process and obtaining the finished result. A ten-hour task might be completed during two focused working days, but it might also take a fortnight if the responsible person can contribute only one hour each day. A thirty-hour assignment might finish sooner if independent parts can be performed simultaneously by several available people. Neither outcome can be determined from effort alone. Dividing the estimated hours by eight and calling the answer a delivery schedule is convenient arithmetic, but it quietly assumes conditions that may not exist.

For the museum, the distinction becomes obvious when the coordinator identifies the actual work involved. Someone must research and write the scripts, another person must check historical accuracy, a narrator must record the material, and the editor must turn those recordings into usable files. The finished tour also needs accessible supporting information, working playback links, and a basic visitor test. Imagine that these activities require forty hours of effort altogether. Forty hours is one standard working week for one person, but that doesn't make the project a one-week undertaking. The researcher cannot approve material she hasn't received. The narrator cannot reliably record scripts that are still being revised. And the editor cannot improve the sound quality of a recording that hasn't happened yet, however impressive the equipment.

To estimate the full assignment, begin by describing what finished actually means. Does success require six playable audio files, or a complete visitor experience with accurate content and working access instructions? Will the tour be available in one language or several? Must recordings meet particular accessibility or technical requirements? These questions aren't bureaucratic decoration. They establish the boundaries of the work. Without them, people may agree on a delivery date while imagining entirely different results. The museum director might picture a polished public launch, while the editor expects to deliver six files to an internal folder. Both could sincerely believe they've understood the assignment. Their disagreement will become apparent at precisely the moment when fixing it is most expensive.

Once the desired result is clear, identify the activities that must happen to produce it. This doesn't require breaking every movement into a separate line on a project board. You don't need an item called "open recording software" followed by "consider microphone" and "experience brief uncertainty about microphone." You need enough detail to distinguish meaningful stages and expose major sources of effort. For an audio tour, researching, scripting, recording, editing, review, and publication are useful categories because each requires different conditions. For another project, a different division may be appropriate. The purpose is to make the work understandable, not to create a magnificent administrative replica of the work.

The Work Between the Work

One easily overlooked source of delay is preparation. Tasks often depend on information or materials that must be made available before meaningful execution begins. An editor can estimate how long it takes to process a recording, but that estimate assumes the audio has been captured in a usable format. A narrator can estimate recording time, but needs approved scripts and clear pronunciation guidance for unfamiliar place names. A researcher might know how long drafting normally takes, but discover that several historical claims require checking against original records. None of these activities is necessarily complicated. Their importance lies in the fact that they're prerequisites. Ignoring them doesn't make the main task smaller. It merely conceals work that must eventually be performed.

Handoffs introduce another kind of time. A completed script may sit in a review queue before the museum's curator can examine it. Once reviewed, it may return with corrections that require the writer's attention. The revised version then has to be checked again if the changes affect factual accuracy. The actual effort could be modest: perhaps forty minutes of review and twenty minutes of correction. Yet the process might occupy four calendar days because the people involved aren't continuously available. It would be misleading to describe those four days as four days of work. It would be equally misleading to omit them from the delivery forecast.

This is where a calendar becomes more useful than a calculator. Suppose the writer needs fourteen hours and can allocate seven hours each working day. Drafting requires two days. The curator is available to review the scripts the following Monday. Recording can begin Tuesday, provided the scripts are approved. The narrator is then available for two afternoons, and editing begins after the first usable recordings arrive. Now we can start describing a plausible sequence. We haven't discovered a way to calculate the exact future, but we've identified concrete conditions that determine when the work can happen. That is much more valuable than announcing that forty hours divided by eight equals Friday.