What Will This Yes Cost?

Listen to this article (BETA)

Preparing the reader…

Your progress: Not started

Mark Complete Start Over Reset History

▶ Listen

Daniel stopped beside Elena’s desk at 4:17p on Tuesday afternoon.

He was the president of a growing professional-services company, and Elena led its four-person communications team. Daniel was preparing for a dinner with several prospective clients on Thursday evening when an idea occurred to him.

“What if we opened with a short video?” he asked. “Nothing elaborate. Maybe three minutes. A few customer comments, some footage from the office, and a strong close about where the company is headed.”

Elena glanced at the production schedule on her screen.

Her team was already completing a client presentation due Wednesday, preparing materials for a Friday training event, and finishing a website launch that had been scheduled for Thursday morning. Every hour had been assigned. The timing was tight, but it was workable—as long as nothing changed.

Something had just changed.

Elena knew what a three-minute video would require. They would need to identify and contact customers, schedule interviews, record them, collect release forms, find usable office footage, write the narration, edit the material, choose music, balance the audio, revise the first cut, export the finished files, and test the video at the dinner venue.

Daniel saw three minutes.

Elena saw somewhere between thirty and forty hours of work.

She felt the proper response forming in her mind: We can do it, but let me show you what it will affect.

Instead, she smiled and said, “We’ll make it happen.”

Daniel thanked her and walked away believing that his request could be absorbed within the existing schedule. Why would he think otherwise? The person who understood the schedule had just told him they would make it happen.

The communications team stayed until nearly midnight on Tuesday. Two people returned early Wednesday morning. The client presentation went out with several errors that normally would have been caught. The website launch was delayed. One employee canceled dinner with her parents. Another missed most of his daughter’s school program. Elena worked both evenings and arrived at Thursday’s dinner carrying a laptop, a spare cable, and the unmistakable expression of someone whose bloodstream was now primarily coffee.

The video played beautifully.

Daniel loved it.

On Friday afternoon, however, the delayed website launch produced an expensive problem for one of the company’s largest clients. Daniel called Elena into his office to find out what had happened. As they traced the chain of events, the full cost of the video finally became visible.

Daniel stared at her.

“If I had known it would delay the launch, I never would have asked you to do it.”

Elena answered quietly, “You did ask. I just never told you what yes would cost.”

Neither of them had acted maliciously. Daniel had not deliberately sacrificed the team. Elena had not intentionally misled him. One made a request without asking what it would displace. The other accepted the request without revealing what it would require.

Together, they made a decision neither of them would have made if both had been working with the same information.

---

Every request spends something

Leadership requires decisions, and leaders make a remarkable number of them. Some are strategic and carefully considered. Others arrive in hallways, text messages, meetings, or beside someone’s desk at 4:17p on Tuesday afternoon.

“Could we add this?”

“Can you move that up?”

“Let’s have something ready by Friday.”

“It would be great if we could…”

The request may sound small from the leader’s side of the desk. The team sees the collision.

The team sees the production schedule, the deadlines already promised, the people working at capacity, the quality controls that cannot be rushed, and the other departments waiting for their contribution. They may also see the soccer game, anniversary dinner, church responsibility, or quiet evening at home that will eventually absorb the cost.

The leader sees the request. The team sees what the request will displace.

That does not necessarily mean the leader is selfish, careless, or incompetent. Leaders cannot see every schedule, dependency, workload, and downstream consequence. The higher someone rises within an organization, the farther that person can become from the details of execution. This is one reason leaders need capable people around them. The leader may know what the organization needs. The people closest to the work know what fulfilling that need will require.

A competent team does not expect leadership to possess information it cannot reasonably have. It supplies the missing information.

This is not resistance. It is stewardship.

An employment relationship is an exchange of stewardship, not ownership.

The employee entrusts an agreed portion of his time, ability, energy, and responsibility to the organization. The employer provides compensation, direction, opportunity, appropriate resources, reasonable expectations, and responsible care for the person performing the work. Both parties receive something of value. Both parties assume obligations. Neither party should prosper through the continuing exploitation of the other.

Good business is only good when it is good for both parties.

A salary purchases an agreed portion of someone’s work. It does not purchase the whole person—or his family.

There will be demanding seasons. Emergencies happen. Important opportunities sometimes arrive without consulting the annual calendar. Faithful employees will occasionally give extraordinary effort because they believe in the mission and care about the people they serve. A wise leader receives that sacrifice with gratitude. He does not quietly convert it into the new minimum expectation.

Every new yes requires another no

Time, attention, money, and human energy are finite. Adding a priority does not enlarge them. It reallocates them.

When we say yes to one thing, we are saying no to something else.

Sometimes the organization should say no to a less important project. Sometimes a deadline should be moved, a standard adjusted, a budget increased, or additional help secured. Occasionally, the team may decide together that an extraordinary sacrifice is justified.

The essential issue is not whether the request has a cost. It does. The issue is whether that cost will be identified, weighed, and intentionally assigned—or left hidden until it is silently charged to someone who never participated in the decision.

Jesus asked, “Which of you, wishing to build a tower, does not first sit down and count the cost to see if he has the resources to complete it?” (Luke 14:28).

The immediate context is the cost of discipleship, which is infinitely more consequential than a production schedule. Yet the illustration works because Jesus’ hearers understood its obvious wisdom: commitments have costs, and wise people identify them before beginning.

A leader may possess the authority to change task priorities. He does not possess the ability to eliminate the consequences of changing them.

The leader must ask; the team must reveal

The governing principle is simple:

The person making the request has a responsibility to ask what it will cost. The person receiving the request has a responsibility to reveal what it will cost.

Neither person gets to surrender stewardship to the other.

The leader cannot say, “They should have told me,” if he has created a culture in which questions are treated as insubordination. The team cannot say, “Leadership should have known,” when the people who possessed the information remained silent.

The leader usually owns the final decision about organizational tasks. The team owns the responsibility to provide the information necessary to make that decision wisely.

Simon Sinek says, “Leadership is not about being in charge; it’s about taking care of those in your charge.”¹ Taking care of people does not mean protecting them from every difficult assignment. It means recognizing that they are people rather than interchangeable units of production. Their time matters. Their families matter. Their health matters. Their existing promises matter. The work already entrusted to them matters.

Leadership is faithful stewardship applied to people. If everything ultimately belongs to God, then the people under our leadership belong to Him as well. They are not ours to consume.

“Be sure to know the condition of your flocks,” Solomon wrote, “and pay close attention to your herds” (Proverbs 27:23). A steward must know the actual condition of what—and whom—has been entrusted to him. A leader who does not know that the team is exhausted, overloaded, or repeatedly surrendering family time does not know the condition of his flock. He has not reached being a Level 2 Leader yet.

At the same time, people closest to the work cannot withhold operational truth and then blame the leader for failing to consider it. Ephesians 4:15 calls believers to speak “the truth in love.” Love without truth becomes enabling. Truth without love becomes accusation. Mature communication requires both.

Brené Brown captures the principle in four memorable words: “Clear is kind. Unclear is unkind.”²

It is not kind to say yes while silently resenting the request. It is not kind to conceal the cost, complain to coworkers, and wait for the plan to fail. It is not kind to allow leadership to make an avoidable mistake because telling the truth felt uncomfortable.

Clear is kind upward, downward, and sideways.

Leaders do not always know what their requests mean

Too many leaders treat every new idea as though it arrives with its own staff, budget, and forty-eight-hour extension to the week.

It does not.

Some leaders fail to ask about the cost because they are separated from the daily work. Others underestimate the complexity of implementation. They see the three-minute video but not the forty hours required to produce it.

Some confuse an idea with a priority. The leader says, “It would be interesting if…” and the staff hears trumpets from heaven followed by a new organizational commandment.

Some leaders are highly creative and continually energized by new possibilities. Their minds naturally run ahead. That ability can be a wonderful leadership strength—until every new thought becomes another project for someone else.

Some see only their department’s need. They do not recognize that fulfilling their request may create problems for three other departments.

Some have been protected from the consequences of previous requests. The team stayed late, rescued the deadline, corrected the errors, and never revealed what the rescue required. The leader saw the completed work but not the exhausted people who completed it.

Conscientious teams can inadvertently train leaders to expect the unreasonable. They repeatedly perform miracles, and leadership gradually mistakes miracles for ordinary capacity.

A wise leader therefore learns to ask:

“What will this require?”

“What will it displace?”

“Who will carry the additional work?”

“What existing commitment will be delayed?”

“Will this affect anyones personal life?”

“Do you have the people, time, authority, and resources to do this well?”

“Is there a better or less costly way to accomplish the same purpose?”

“Am I sharing an idea, making a request, or changing an organizational priority?”

Jordan Peterson’s ninth rule in 12 Rules for Life is, “Assume that the person you are listening to might know something you don’t.”³ That is particularly valuable advice for leaders. The person raising a concern may not lack vision, commitment, or courage. He may simply know something about the work that the leader does not.

A leader does not weaken his authority by asking for that information. He strengthens the quality of the decision made with it.

Teams do not always say what leadership needs to hear

The communication gap also has another side.

Staff members may recognize the cost of a request and still fail to communicate it.

Some fear being labeled negative, difficult, uncooperative, or disloyal. Some have previously worked under leaders who interpreted every question as resistance. Others genuinely do work within unhealthy cultures where unwelcome information is punished.

Some team members confuse submission with silence. They believe honoring authority means immediately agreeing with everything authority requests, even when they possess information leadership needs.

Some want approval. They would rather absorb unreasonable work than risk disappointing the leader.

Some avoid conflict. They say yes in the room and no in the hallway. They comply verbally, resist emotionally, and complain horizontally.

Some assume leadership already understands the consequences. Usually, leadership does not. If the leader fully understood the cost, the conversation might not be necessary.

Some say yes before calculating. The confidence of “We can handle it” is followed several hours later by the discovery that nobody has any idea how they will handle it.

Others have built part of their identity around heroic overwork. They become the person who always rescues the organization, even though every rescue teaches the organization that planning and capacity no longer matter.

There is also a timing problem. People often remain quiet when a calm, professional conversation would be helpful. Then, after several more requests and considerably less sleep, they finally speak with enough accumulated frustration to make legitimate information sound like an indictment.

Leadership expert John Maxwell has long emphasized that effective leadership depends upon influence and connection, not merely position. Level 2 leadership—Permission—develops when people follow because they want to, not simply because they must. A leader who consistently sacrifices people to his preferences may continue to receive compliance, but he is spending relational trust with every unnecessary demand.⁵

A healthy team helps protect that trust through early, respectful honesty.

Personality shapes both the request and the response

[We use The DISC Model of Human Behavior when talking about personality. It is a simple way of understanding the four primary patterns of personality: Dominant, Inspiring, Supportive, and Conscientious (spelling DISC). It considers a person’s Pace—whether Outgoing or Reserved—and Compass—whether primarily Task-oriented or People-oriented—to help explain how people naturally communicate, make decisions, approach work, and respond to others. Most people display a blend of all four patterns, with one or two usually appearing more strongly. DISC describes observable tendencies, not ability, maturity, or character, and it helps us understand how someone may naturally behave, but never excuses how anyone chooses to behave.]

Personality does not determine whether someone will act wisely, selfishly, courageously, or responsibly. That is a matter of character. It does, however, influence what a person notices first, how a request is made, and how that person initially responds when additional work collides with existing tasks and priorities. The problem may therefore look quite different depending upon who is making the request and who is receiving it.

A decisive, fast-paced, task-oriented leader (Dominant—D) may see the new objective and move immediately toward it. Because this leader naturally focuses on results, obstacles can appear to be problems that capable people should simply overcome. The request may be brief and direct: “We need this by Friday. Make it happen.” The leader may not intend to disregard the team; he may genuinely assume that urgency, ingenuity, and effort will carry the day. When serving as a staff member, this same personality may accept the assignment quickly, confident that a solution can be forced into existence. He may also push back directly—sometimes too directly—by saying, “That deadline is impossible,” before explaining the operational reasons or offering alternatives. His growth point is to slow down long enough to count the human and organizational cost, then use his decisiveness to choose among clearly presented tasks or priorities rather than merely adding another one.

An outgoing, people-oriented, enthusiastic leader (Inspiring—I) may introduce new work through excitement rather than command. “I just had a fantastic idea!” can mobilize a room before anyone has calculated what the idea will require. Because this leader sees possibilities and can inspire others to see them too, the team may enthusiastically agree before remembering that enthusiasm has never added an hour to Thursday. As a staff member, this personality may say yes because the idea sounds exciting, because the leader seems pleased, or because disappointing someone feels uncomfortable. Only later does the actual workload become visible. His growth point is to pause between inspiration and commitment, ask practical questions, and remember that agreeing relationally is still committing operationally.

A patient, supportive, people-oriented leader (Supportive—S) may be less likely to issue abrupt demands, but may still add work indirectly because he wants to help someone, preserve harmony, or meet a need. He may assume the team will quietly cooperate just as he would. Because he dislikes disrupting relationships, he may present a substantial request so gently that its priority remains unclear. As a staff member, this personality is especially vulnerable to absorbing the additional burden without objection. He may rearrange his schedule, stay late, and protect everyone else from the consequences while his own frustration and exhaustion quietly accumulate. His growth point is to recognize that gracious honesty does not damage healthy relationships. It protects them. A calm statement such as, “We want to help, and here is what we would need to move in order to do so,” is not disloyal. It is responsible stewardship.

A careful, reserved, task-oriented leader )Conscientious—C) will often consider details and consequences more thoroughly before making a request. Yet this leader may still underestimate the cost if he understands the desired standard but not the workload already assigned to the people responsible for producing it. He may expect the team to identify conflicts precisely and may become frustrated when they do not. As a staff member, this personality may see every complication immediately but hesitate to speak until he has assembled enough evidence to defend the concern beyond dispute. By the time he is ready, the decision may already have been made. If pressed too quickly, he may respond with a long inventory of everything that could go wrong, causing leadership to hear resistance rather than useful analysis. His growth point is to communicate earlier and more concisely: identify the principal cost, provide the most relevant evidence, and recommend a workable alternative.

These differences can also collide. A fast-moving leader may interpret a careful staff member’s questions as obstruction. The careful staff member may interpret the leader’s urgency as recklessness. An enthusiastic leader may mistake a supportive employee’s agreeable manner for available capacity. The employee may assume the leader should somehow recognize that the yes was reluctant. Neither is necessarily acting in bad faith. They may simply be sending and receiving information through very different personalities.

This is one reason mature teams establish a shared language for adding work. The decisive person needs to know that questions are not automatically resistance. The enthusiastic person needs to know that excitement is not capacity. The supportive person needs to know that kindness does not require silent overextension. The careful person needs to know that useful information delivered too late is no longer as useful.

Personality helps explain our initial response; it does not excuse an irresponsible one. Every personality must grow beyond its natural reflex. Leaders must learn to ask what their people may be hesitant to tell them. Staff members must learn to communicate what their leaders may not naturally see. Character takes the strengths of personality and places them under the stewardship of love, wisdom, courage, and truth.

When leaders punish honest information, people learn to hide the cost. When teams hide the cost, leaders learn to make uninformed decisions.

The pattern then repeats. Leadership requests. The team silently absorbs. The work gets done. Leadership concludes that capacity existed. The next request becomes larger. Resentment grows. Quality declines. Families begin paying. Eventually, someone leaves—and leadership is surprised.

Turnover is the collection agency

If work is repeatedly accomplished only because conscientious employees surrender evenings, weekends, family commitments, sleep, or health, the organization is not operating efficiently.

It is borrowing against the lives of its people.

That means the organization is accumulating debt. Eventually, collections comes knocking.

The demand may arrive as burnout, disengagement, declining quality, illness, resentment, damaged family relationships, or resignation. Whatever form it takes, the debt does not disappear merely because leadership failed to record it on a spreadsheet.

The additional financial cost can be substantial. Gallup estimates that replacing a frontline employee costs approximately 40 percent of that position’s annual salary; replacing someone in a technical or professional role costs approximately 80 percent; and replacing a leader or manager may cost approximately 200 percent—not including every loss in organizational knowledge, relationships, continuity, and morale.⁴

The organization that repeatedly saves time by overtaxing its people may eventually spend far more replacing them than it would have spent supporting them properly.

When an organization routinely borrows from the lives of its people, turnover is merely the collection agency.

You can repeatedly solve organizational problems by spending other people’s families. Many organizations do. The presentation gets finished. The event is produced. The deadline is met. Leadership congratulates itself on the team’s commitment.

Then the bill comes due.

Brian Tracy has built much of his work around planning, priorities, and disciplined execution. One of the practical truths beneath that work is that beginning something new without deciding where it belongs among existing priorities is not planning. It is accumulation. A growing list of “top priorities” eventually becomes a list in which nothing is truly prioritized.⁶

Zig Ziglar frequently taught that lasting success cannot be separated from helping other people succeed. That principle belongs inside the organization as much as it does in the marketplace. A business cannot rightly claim success while systematically diminishing the people whose labor created it.⁷

Productivity that continually consumes the worker is not productivity. It is liquidation.

This responsibility also runs sideways

This is not only a leader-and-follower issue. Peers consume one another’s capacity too.

A department head asks another department for “a little help.” A coworker requests something “whenever you have a minute.” Someone schedules a one-hour meeting with eight people and does not recognize that the meeting is consuming eight organizational hours—not counting preparation and recovery.

A peer may not possess the authority to rearrange another person’s responsibilities. Courtesy requires asking rather than presuming.

“Would you have the capacity to help with this?”

“What would this affect on your side?”

“If this needs to move ahead of your current work, should we ask our leaders to clarify the priority?”

“How can we accomplish this without simply transferring the pressure from our team to yours?”

Philippians 2:4 says, “Each of you should look not only to your own interests, but also to the interests of others.” That includes their workload, commitments, and capacity. My urgent need does not automatically become your urgent obligation.

Organizations become healthier when people stop tossing work across departmental fences and calling it collaboration.

From pushback to responsible cost clarification

“Pushback” is not entirely the wrong word, but it can sound adversarial. It suggests two people pushing against each other to see who moves first.

The goal is not to stop leadership from acting. The goal is to help leadership act with accurate information.

A better description is responsible cost clarification.

Responsible cost clarification says:

“Yes, we can do that. Before we commit, I want to make sure you understand what it will affect.”

“To complete this by Friday, we would need to delay the client proposal until Tuesday, move two people off the current project, or authorize overtime. Which option best reflects your priority?”

“We have capacity to complete two of these three projects at the expected standard. If all three must move forward, we will need additional time, people, or funding.”

“I understand the urgency. Here is the effect this change will have on the team and the schedule. Here is our recommendation.”

Those responses do not challenge leadership’s right to decide. They provide the information leadership needs to decide wisely.

A helpful process is:

Ask. Reveal. Weigh. Decide. Own.

The person making the request begins by asking what the new work will require.

The person receiving the request reveals the likely effect on time, people, money, quality, schedules, and other commitments.

Together, they weigh whether the desired outcome justifies the cost and consider reasonable alternatives.

The appropriate leader decides which priority will change.

Then everyone owns the decision and its known consequences. No silent resentment. No historical revisionism. No later claim that everyone should have understood what nobody actually discussed.

This is not bureaucratic delay. It does not require a committee meeting every time someone needs a water bottle before the meeting. It is proportional stewardship. The greater the likely disruption, the more explicit the conversation should become.

A five-minute request may require nothing more than ordinary cooperation. A forty-hour request disguised as a three-minute video deserves a conversation.

Acts 6: an important need handled wisely

The early church encountered a serious operational problem in Acts 6. The Hellenistic Jews complained that their widows were being overlooked in the daily distribution of food.

The apostles did not dismiss the concern. Caring for vulnerable widows mattered deeply. Neither did they simply add the responsibility invisibly to their own workload and hope that prayer, preaching, administration, and food distribution would somehow fit inside the same number of hours.

They identified the need, protected their existing calling, involved the community, established appropriate qualifications, and entrusted the work to capable people.

They did not deny the new priority. They resourced it.

That is wise stewardship.

Sometimes the right answer is yes. Sometimes it is no. Frequently it is, “Yes, if we change this, provide that, or stop doing something else.”

Good leadership does not merely determine what should be done. It considers how the work will be carried, who will carry it, and what faithfulness requires in the process.

The heart beneath the request

This is ultimately a heart issue for everyone involved.

Leaders must examine whether their desires have quietly become demands. Are they using authority to serve the mission and the people, or using people to serve their impulses? Do they welcome operational truth, or do they prefer immediate agreement? Do they express gratitude for extraordinary sacrifice, or have they begun to expect it?

Staff members must examine their own hearts as well. Are they respectfully telling the truth, or merely resisting inconvenience? Are they protecting legitimate commitments, or guarding personal comfort? Are they offering alternatives and recommendations, or simply identifying obstacles? Are they speaking directly to the appropriate person, or cultivating agreement among dissatisfied peers?

Professional courtesy does not mean leaders stop asking for difficult things. Courageous leadership will sometimes ask people to do what has never been done before.

Professional courtesy also does not mean teams agree without thought. Faithful followers help leaders distinguish between a necessary sacrifice and an unnecessary one.

Both must approach the conversation with humility.

The leader says, “You may know something I do not.”

The team member says, “You may see a priority I do not.”

Together they ask, “What is the wisest and most faithful use of what has been entrusted to us?”

Before the next yes

Every organization occasionally needs its people to stretch. The goal is not to remove difficulty, urgency, sacrifice, or ambition from meaningful work. The goal is to ensure that sacrifice is understood rather than presumed, purposeful rather than habitual, and shared rather than quietly transferred to the people with the least authority to refuse it.

Leaders, before making the next substantial request, ask what it will cost.

Team members, before offering the next automatic yes, reveal what it will cost.

Peers, before transferring your urgency into someone else’s schedule, respect the responsibilities that person already carries.

The leader has the authority to set the priority. The team has the responsibility to reveal the price. Everyone shares responsibility for stewarding the people who will ultimately pay it.

Because every yes has a cost.

Wisdom makes certain we know what it is—and agree that it is worth paying—before the bill comes due.

---

Key truths to remember

• Every request spends time, attention, money, energy, quality, or trust.

• Every new priority displaces an existing one.

• The person making the request should ask what it will cost.

• The person receiving the request should reveal what it will cost.

• Responsible cost clarification helps leadership make better decisions.

• Leaders must make honest upward communication safe.

• Teams must communicate concerns early, directly, and professionally.

• Peers should ask before transferring urgency into someone else’s schedule.

• Extraordinary sacrifice should be occasional, understood, and appreciated.

• A salary purchases agreed work—not the whole person or the person’s family.

• When an organization borrows against people’s lives, the debt eventually comes due.

---

Endnotes

1. Simon Sinek, “Leaders Eat Last,” The Optimism Company. Simon Sinek on caring for those in your charge.
2. Brené Brown, “Clear Is Kind. Unclear Is Unkind,” October 15, 2018. Brown notes that she originally heard the expression in a twelve-step meeting and later adopted it as a central leadership principle. Brené Brown on clarity and difficult conversations.
3. Jordan B. Peterson, 12 Rules for Life: An Antidote to Chaos (Random House Canada, 2018), Rule 9.
4. Gallup, “42% of Employee Turnover Is Preventable but Often Ignored,” updated February 16, 2026. Gallup estimates additional replacement costs at approximately 40 percent of salary for frontline employees, 80 percent for technical professionals, and 200 percent for leaders and managers. Gallup’s role-specific employee replacement estimates.
5. John C. Maxwell, The 5 Levels of Leadership: Proven Steps to Maximize Your Potential (Center Street, 2011).
6. Brian Tracy, Eat That Frog!: 21 Great Ways to Stop Procrastinating and Get More Done in Less Time, 3rd ed. (Berrett-Koehler, 2017).
7. Zig Ziglar, See You at the Top, 25th anniversary ed. (Pelican Publishing, 2000).

---