Dawn Dahlke

Introduction: The Job You Were Hired to Do Is No Longer the Only Job You Have

Imagine accepting a project manager position with an organization you believe in.

You are excited about the opportunity. You have reviewed the responsibilities, discussed expectations with leadership, and developed an understanding of the projects you will be managing.

You know there will be challenges. Every project has them.

Deadlines, competing priorities, stakeholder expectations, resource limitations, unexpected risks, and the occasional problem that requires everyone to come together and find a solution will arise.

That is project management.

You are prepared for those responsibilities because they are part of the profession you chose.

Then something interesting begins to happen.

A few months into your position, you discover that some of the organizational processes you expected to support your project are either incomplete, outdated, inconsistent, or nonexistent.

Perhaps the organization lacks a clearly defined change management process.

Project documentation may be scattered across departments.

Maybe communication between teams depends more on individual relationships than established procedures.

You discover that employees have different understandings of how work should move through the organization.

Some teams follow one process, while others have developed their own.

New employees are learning responsibilities through conversations rather than formal training.

Decisions are made, but they are not always documented.

Ownership is assumed rather than assigned.

And suddenly, you realize something important.

You cannot manage the project effectively without addressing the organizational conditions preventing it from moving forward.

So you begin helping.

You document a process.

You coordinate a training session.

You clarify responsibilities.

You establish a communication procedure.

You organize information that has never been maintained consistently.

You help departments understand how their work connects to the larger project.

Leadership notices.

They appreciate your initiative.

They recognize the value of your work.

They encourage you to continue.

And why wouldn't they?

You are making a difference.

You are helping the organization become more effective.

You are demonstrating leadership beyond the responsibilities outlined in your job description.

But somewhere along the way, something changes.

The work you were hired to do hasn't disappeared.

The projects still have deadlines.

Stakeholders still expect updates.

Budgets still require oversight.

Risks still need to be managed.

Teams still need direction.

And now, alongside all those responsibilities, you are helping build the organizational structure that should have existed to support the work in the first place.

The additional responsibilities may be reasonable.

They may be necessary.

They may even be rewarding.

But that does not mean they are sustainable.

This raises a question that deserves far more attention in conversations about leadership and project management:

When an organization recognizes that additional work is necessary, who is responsible for creating the capacity to accomplish it?

And perhaps an even more uncomfortable question:

At what point does recognizing someone's capabilities become an excuse to keep expanding their responsibilities?

The Difference Between Managing a Project and Building the Environment That Makes Project Management Possible

People often describe project management through its responsibilities.

We initiate projects, develop plans, coordinate resources, manage risks, monitor progress, communicate with stakeholders, and guide work toward successful completion.

Those responsibilities are substantial.

They require technical knowledge, leadership skills, sound judgment, communication, and an understanding of how organizational decisions affect delivery.

But project management does not exist in isolation.

Every project operates within an organizational environment.

That environment includes processes, governance structures, policies, reporting relationships, communication channels, technology, and established expectations.

When those elements function effectively, they help project managers do their jobs.

When they don't, the project manager often becomes the person expected to compensate for what is missing.

Consider a relatively simple example.

A project requires approvals from three departments before implementation can proceed.

In a mature environment, a documented approval process exists.

Everyone understands who approves what, how long approvals should take, and where decisions are recorded.

Now imagine the same project in an organization where no consistent approval process exists.

One department communicates through email.

Another expects a meeting.

The third assumes someone else has already approved the work.

The project manager must now determine the correct approval path, identify decision makers, coordinate conversations, resolve misunderstandings, and document the outcome.

That work may be necessary to deliver the project.

But it is not simply project coordination.

It is compensating for a missing organizational process.

Now multiply that example across change management, resource allocation, training, requirements gathering, risk escalation, and project reporting.

The project manager is no longer only managing project delivery.

They are helping establish the operational environment required for delivery.

There is nothing inherently wrong with this.

Organizations evolve.

Processes need improvement.

Even mature organizations discover gaps when new projects introduce unfamiliar requirements.

The problem begins when temporary compensation for organizational weaknesses becomes an ongoing expectation.

A project manager can improve an organizational process without permanently owning every process that needs improvement.

That distinction matters.

Helping establish a process is one responsibility.

Maintaining that process indefinitely is another.

Training employees to follow a new procedure is one responsibility.

Becoming the permanent resource for every future question about that procedure is another.

Identifying a gap is part of effective project management.

Being assigned ownership of every identified gap is not automatically part of the role.

Organizations must recognize the difference.

Otherwise, the person who identifies a problem can unintentionally become the person expected to solve it, manage it, document it, train everyone on it, and maintain it.

Once that expectation is established, stepping away can be interpreted as a lack of commitment rather than a necessary clarification of responsibility.

The Invisible Work That Never Appears in the Project Plan

One of the biggest challenges in managing expanding responsibilities is that much of the added work stays invisible.

Project plans are designed to make work visible.

We identify deliverables.

We establish milestones.

We estimate effort.

We assign resources.

We track progress.

We monitor dependencies.

We identify risks.

But what happens when the work required to keep a project moving is not included in the plan?

Consider how much time project managers spend on activities that may never appear as formal deliverables.

Explaining an existing process to a new employee.

Helping two departments understand why their priorities conflict.

Following up on a decision that should have been documented.

Clarifying who owns a task.

Finding information that should be centrally available.

Coordinating training because a team isn't prepared to use a new system.

Rebuilding a workflow because the current one creates unnecessary delays.

Helping leadership understand why a recurring issue keeps affecting delivery.

Individually, these activities may seem minor.

Collectively, they can consume a significant portion of the working week.

Because they often happen through conversations, meetings, messages, and informal problem-solving, they can be hard to measure.

The project manager may appear to be managing the same number of projects as before.

But the actual workload has changed considerably.

This is where organizations can develop a distorted understanding of capacity.

Leadership sees the projects assigned to the employee.

They may not see the countless supporting responsibilities required to keep those projects moving.

A calendar filled with meetings does not always communicate the complexity of the decisions being made during those meetings.

A completed process document does not reveal the hours spent gathering information from multiple departments.

A successful training session does not show the preparation, coordination, and follow-up required to make it effective.

A project that stays on schedule may hide the extraordinary effort required to keep it there.

The absence of visible problems does not necessarily mean the workload is manageable. Sometimes it means someone is working exceptionally hard to prevent those problems from becoming visible.

That distinction matters for leadership.

Outcomes often evaluate project managers.

Did the project meet its objectives?

Were stakeholders informed?

Were risks addressed?

Was the work delivered?

Those are legitimate measures.

But organizations should also examine what it took to achieve those outcomes.

Was the workload reasonable?

Were responsibilities clearly assigned?

Did the project manager have adequate support?

Were organizational gaps addressed systematically, or did one individual repeatedly compensate for them?

Was the success repeatable without relying on extraordinary personal effort?

A project delivered successfully through unsustainable effort should not automatically be considered evidence of an effective operating model.

Sometimes it shows the operating model needs improvement.

When Initiative Becomes an Unspoken Expectation

Most project managers do not enter the profession because they enjoy watching problems remain unresolved.

They naturally organize, coordinate, communicate, and find solutions.

When they see an obstacle, they want to understand it.

When they discover a gap, they want to close it.

When a team struggles, they want to help.

These are valuable qualities.

They can also make project managers particularly vulnerable to taking on more responsibility.

Imagine a project manager who notices inconsistent onboarding procedures.

They develop a simple checklist.

It works.

New employees have clearer expectations.

Managers appreciate the improvement.

Leadership recognizes the initiative.

A few weeks later, another department asks whether the project manager can help organize its onboarding process.

Then someone requests a training guide.

Another person asks for a process review.

Eventually, the project manager becomes the informal owner of onboarding improvements across multiple departments.

No one necessarily intended for this to happen.

No one may have formally decided to expand the role.

Each request may have seemed reasonable at the time.

But the responsibilities accumulated.

And because the project manager consistently delivered, the organization began relying on that willingness to help.

This is a subtle but important organizational pattern.

What begins as initiative can gradually become expectation, and what becomes expectation can eventually be treated as obligation.

That progression deserves attention.

Encourage employees to demonstrate initiative.

Organizations benefit when people look beyond their immediate assignments and identify opportunities for improvement.

But initiative should not automatically create permanent ownership.

If an employee develops a solution to an organizational problem, leadership should decide how to maintain it.

Who owns the process?

Who is responsible for future updates?

Who will train new employees?

What resources are required?

Does the responsibility belong within the employee's existing role?

If it does, what other responsibilities should be adjusted?

Without those conversations, the organization risks turning its most proactive employees into permanent solutions for problems that should be addressed structurally.

And eventually, those employees may become hesitant to identify additional opportunities for improvement.

Not because they have stopped caring.

But because they have learned that identifying a problem often means inheriting it.

That is a dangerous outcome for any organization that claims to value continuous improvement.

Supportive Leadership Does Not Automatically Mean Sustainable Leadership

It's easy to frame this discussion as a problem caused by poor leadership.

But that would overlook an important reality.

Sometimes leadership is genuinely supportive.

Managers listen.

Executives acknowledge problems.

Departments cooperate.

Employees receive recognition for their contributions.

The organization may sincerely want to improve.

And yet the workload can still become unsustainable.

Why?

Supporting an idea and supporting the capacity required to execute it are not the same thing.

A leader may recognize that a project manager has identified an important process improvement.

They may encourage the employee to move forward.

They may offer flexibility, provide visibility, and express appreciation.

Those are positive responses.

But if the improvement requires substantial effort, encouragement alone does not create additional hours in the workweek.

Recognition does not eliminate existing deadlines.

Flexibility does not automatically resolve competing priorities.

And appreciation does not replace staffing.

This is not an argument against supportive leadership.

It argues for taking supportive leadership further.

Consider two possible responses when a project manager identifies a significant organizational gap.

The first response is:

"That is a great idea. Please move forward with it."

The second response is:

"That is an important issue. Let's determine what resources are needed, who should own the work, and what we may need to reprioritize so it can be completed successfully."

Both responses acknowledge the value of the improvement.

But the second recognizes that meaningful work requires capacity.

It also recognizes that adding a responsibility is a management decision with consequences.

Those consequences may affect project schedules, team availability, quality, and employee well-being.

Supportive leadership should not stop at permission.

It should include prioritization.

It should include resource planning.

It should include clear ownership.

And when necessary, it should include the willingness to say that something important cannot be completed immediately.

An organization can have supportive intentions while still creating unsustainable expectations through its decisions.

Recognizing that possibility is not an accusation.

It is an opportunity for better leadership.

The Dangerous Assumption That Capable People Have Unlimited Capacity

A particular challenge comes with being someone others trust to get things done.

Success creates confidence.

Confidence creates opportunity.

Opportunity creates additional responsibility.

In healthy organizations, this progression can support professional growth.

Employees gain experience.

They develop new skills.

They become trusted leaders.

They receive promotions and opportunities to influence organizational decisions.

But the same progression can become problematic when organizations confuse capability with capacity.

A project manager may be exceptionally skilled at organizing complex initiatives.

That does not mean they can manage an unlimited number of them.

An employee may be excellent at solving cross-functional problems.

That does not mean every cross-functional problem should be assigned to them.

Someone may be capable of creating training materials.

That does not mean they have the time to become the organization's training department.

Being capable of performing additional work does not mean someone has the capacity to absorb it.

These are two different considerations.

Capability asks whether a person has the knowledge, skills, and judgment to perform the work.

Capacity asks whether the person has sufficient time, resources, attention, and support to perform it alongside existing commitments.

Organizations sometimes answer the first question and assume they have answered the second.

They see an employee who consistently delivers.

They conclude that the employee can handle more.

But past success may have required overtime, personal sacrifices, delayed administrative work, or reduced opportunities for professional development.

It may have required the employee to spend evenings preparing for meetings or catching up on documentation.

It may have required constantly shifting attention between competing priorities.

None of those conditions is necessarily visible in a project status report.

When leadership assigns more work based only on successful outcomes, it risks building future expectations on an incomplete understanding of how those outcomes were achieved.

This is why capacity conversations should be ongoing.

They shouldn't happen only when someone announces they are overwhelmed.

By that point, the organization may already be experiencing the consequences of excessive workload.

The goal should be to recognize limitations before they become crises.

The Difference Between Professional Growth and Role Overload

One common argument for expanding responsibilities is that additional work creates growth opportunities.

And that argument has merit.

Project managers benefit from understanding the broader organization.

They become stronger leaders when they learn about operations, governance, training, change management, and strategic planning.

Exposure to unfamiliar responsibilities can help employees discover interests and capabilities they didn't know they had.

Some of the most meaningful career opportunities begin when someone volunteers to solve a problem outside their normal role.

But professional development and role overload aren't the same.

The difference often comes down to intention, structure, and support.

Professional growth generally includes a clear purpose.

The employee understands what they are learning and why the opportunity matters.

Expectations are discussed.

Resources are considered.

Feedback is provided.

The experience contributes to a larger development path.

Role overload is different.

Responsibilities accumulate without a clear plan.

The employee continues performing the original job while additional work becomes routine.

Success is expected, but priorities don't adjust.

The organization benefits from the expanded contribution without necessarily acknowledging that the role itself has changed.

This distinction matters most when employees are praised for being flexible.

Flexibility is valuable.

Adaptability is essential in project management.

But flexibility should not replace organizational planning.

There is a difference between temporarily helping another team through a critical deadline and permanently becoming responsible for that team's work.

Learning a new skill is different from being expected to perform two distinct jobs.

And there is a difference between taking on a leadership opportunity and absorbing responsibilities simply because no one else has been assigned to them.

Organizations should ask whether additional work genuinely develops an employee or merely relies on that employee to fill a structural gap.

Employees should feel comfortable asking the same question.

Growth should expand a person's opportunities.

It should not continuously consume the time and energy required to pursue them.

The Organizational Cost of Always Saying Yes

Project managers often find themselves in situations where saying yes feels like the responsible choice.

A department needs help.

A process must be documented.

A stakeholder requests additional reporting.

Leadership identifies an improvement opportunity.

A team needs training before implementation can proceed.

Each request has a legitimate business reason.

The difficulty is that organizations rarely experience these requests one at a time.

They accumulate.

Without clear prioritization, every request can feel equally urgent.

Imagine a project manager responsible for three major initiatives.

Each has defined milestones, stakeholder commitments, and dependencies.

Now imagine the manager is also asked to create a training program, establish a reporting procedure, and coordinate a cross-departmental process improvement.

None of those additional responsibilities is unreasonable on its own.

Together, they may exceed available capacity.

What happens next?

The project manager may begin working longer hours.

Administrative tasks may be delayed.

Risk reviews may receive less attention.

Stakeholder communication may become more reactive.

Documentation may be completed later than intended.

Decisions may take longer because one person is involved in too many competing activities.

Eventually, project delivery itself can suffer.

This creates an unfortunate contradiction.

The additional work was intended to improve organizational performance.

But because the work was not properly resourced, it begins affecting the performance of the projects the employee was originally hired to manage.

When organizations add responsibilities without adjusting capacity, they don't eliminate the cost of the work. They are transferring that cost somewhere else.

Sometimes the cost appears as overtime.

Sometimes it appears as delays.

Sometimes it appears as reduced quality.

Sometimes it appears as frustration, fatigue, or disengagement.

And sometimes the cost remains hidden until an experienced employee decides to leave.

That is why saying yes to every reasonable request is not necessarily responsible project management.

Responsible project management requires understanding trade-offs.

Every additional commitment consumes resources.

Every new priority competes with existing priorities.

Every decision to accelerate one activity can affect another.

Project managers are expected to understand those realities when managing projects.

Organizations should apply the same discipline when managing their employees' responsibilities.

When the Project Manager Becomes the Organizational Safety Net

In some organizations, project managers gradually become the people who catch whatever falls between departments.

A requirement has no clear owner.

The project manager follows up.

A communication process breaks down.

The project manager coordinates a solution.

Training was not completed.

The project manager organizes it.

A decision remains unresolved.

The project manager brings the appropriate people together.

A recurring problem affects multiple teams.

The project manager documents the issue and proposes a new procedure.

At first, this can look like excellent leadership.

And in many ways, it is.

Project managers are expected to facilitate communication, identify dependencies, and remove obstacles within their authority.

But facilitating accountability is different from becoming accountable for everything.

A project manager should help ensure the right people are involved in decision-making.

That does not mean the project manager should permanently own every decision-making process.

A project manager should identify when implementation requires training.

That does not automatically make the project manager responsible for developing and maintaining all organizational training.

A project manager should raise concerns about inadequate procedures.

That does not mean they should independently redesign the organization's entire operating model.

When those distinctions disappear, project managers can become organizational safety nets.

They catch problems before those problems reach leadership.

They bridge communication gaps.

They compensate for unclear ownership.

They make fragmented processes appear more coordinated than they actually are.

This can create a dangerous illusion of organizational maturity.

From the outside, projects may appear well managed.

Internally, however, success depends heavily on a few individuals' effort and institutional knowledge.

What happens when those individuals take vacation?

What happens when they receive promotions?

What happens when they leave?

If the organization cannot maintain its processes without relying on one person's extraordinary involvement, it hasn't fully resolved the underlying problem.

It has created a dependency.

A strong organization should benefit from capable people without becoming dependent on their willingness to compensate for every structural weakness.

Project managers can help identify those weaknesses.

They can support improvements.

They can facilitate implementation.

But lasting organizational capability requires shared ownership.

Why More Responsibility Does Not Always Mean More Authority

Another challenge emerges when project managers are expected to improve organizational processes without receiving the authority necessary to implement meaningful change.

They may be asked to coordinate across departments but have limited influence over departmental priorities.

They may identify inefficiencies but lack the authority to change established procedures.

They may be expected to resolve resource conflicts without controlling the resources involved.

They may be asked to improve accountability without direct authority over the people responsible for completing the work.

This creates a difficult leadership position.

The project manager is accountable for progress but cannot independently control many of the conditions affecting that progress.

Experienced project managers understand that influence is central to the profession.

They know how to build relationships, facilitate discussions, communicate expectations, and encourage collaboration.

But influence has limitations.

An organization cannot reasonably expect one employee to resolve every structural problem through relationship management alone.

At some point, leadership must provide direction.

Policies may need to change.

Departments may need to accept new responsibilities.

Resources may need to be reassigned.

Decision-making authority may need to be clarified.

Those are organizational decisions.

They require organizational leadership.

When project managers receive additional responsibility without corresponding authority, they can get caught between expectations they must meet and decisions they cannot make.

This is especially challenging when the work involves improving processes across multiple departments.

Each department may have legitimate priorities.

Each may face resource limitations.

Each may have established practices that employees resist changing.

The project manager can facilitate conversations.

They can document recommendations.

They can explain the benefits of improvement.

But sustainable change requires leadership alignment and ownership.

Accountability requires the authority, resources, and organizational commitment needed to achieve the expected outcome.

Otherwise, expanding responsibility can become a source of frustration rather than professional development.

The Project Management Triangle Applies to People Too

Project managers spend considerable time explaining how scope, schedule, cost, resources, and quality relate.

When project scope increases, we evaluate the consequences.

Will additional work require more time?

Will it require additional resources?

Will the budget need to change?

Can the existing team absorb the work without affecting quality?

These are familiar questions.

Yet organizations do not always apply the same reasoning to employee workloads.

Consider the irony.

A project manager may be required to submit a formal change request when a stakeholder adds a significant deliverable.

The request must be evaluated.

The impact must be documented.

Approvals may be required.

But when the project manager is personally assigned additional responsibilities, the workload change may receive little formal consideration.

There may be no capacity assessment.

No revised priorities.

No discussion of which responsibilities should be reassigned.

No adjustment to deadlines.

The new work becomes part of the job.

If project managers applied that approach to every project change, organizations would quickly recognize the risk.

Why, then, should expanding an employee's responsibilities be treated differently?

Imagine a project with a defined scope and a team operating near its planned capacity.

Leadership introduces several additional deliverables.

The project manager explains that the new work will require more resources, more time, or fewer other commitments.

That is not resistance.

That is responsible planning.

Now imagine the project manager making the same statement about their own workload.

"I can take responsibility for this process improvement, but we need to determine which existing commitments will be adjusted or what additional support will be available."

View that statement through the same professional lens.

It is not a refusal to contribute.

It is an assessment of capacity.

Organizations should manage expanding employee responsibilities with the same discipline they expect project managers to apply to expanding project scope.

If additional work is important enough to assign, it is important enough to plan.

The Hidden Risk to Project Quality

When workload expands, the first consequences are not always obvious.

A project may continue meeting its milestones.

Status reports may remain positive.

Stakeholders may express satisfaction.

But beneath those visible indicators, project management practices can begin to deteriorate.

Risk identification may become less proactive.

Instead of regularly reviewing emerging threats, the project manager focuses on resolving immediate problems.

Communication may become more transactional.

Instead of engaging stakeholders thoughtfully, updates become brief exchanges designed to keep information moving.

Documentation may become less complete.

Decisions are recorded quickly, but the reasoning behind them may be lost.

Lessons learned may be postponed.

Process improvements may be implemented without sufficient follow-up.

These changes do not necessarily result from a lack of skill or commitment.

They can result from a lack of time.

Effective project management requires more than responding to whatever is most urgent.

It requires reflection.

It requires planning.

It requires examining trends.

It requires identifying risks before they become issues.

It requires understanding how today's decisions may affect future outcomes.

Those activities demand attention.

When a project manager spends most of the day moving between meetings, answering questions, coordinating unrelated tasks, and addressing organizational gaps, time for thoughtful project oversight shrinks.

The organization may not recognize the problem until something significant is missed.

A risk that should have been identified earlier becomes an issue.

A dependency is overlooked.

A stakeholder raises a concern that should have been addressed weeks before.

A project experiences a delay that more deliberate planning might have prevented.

It is easy to respond by asking why the project manager did not anticipate the problem.

But a more useful question may be whether the organization created conditions that allowed the project manager to perform the necessary oversight.

Project quality depends not only on the project manager's competence but also on the capacity to practice effective project management.

Organizations should not expect proactive leadership while continuously consuming the time required for proactive thinking.

The Emotional Cost of Being the Person Everyone Depends On

This discussion also has a human dimension.

Project managers are professionals, but they are also people.

They take pride in their work.

They care about their teams.

They want to meet expectations.

They want their organizations to succeed.

For many, being trusted with difficult responsibilities is meaningful.

It communicates confidence.

It creates a sense of purpose.

It reinforces the belief that their contributions matter.

But being the person everyone depends on can become exhausting without clear boundaries.

The pressure comes from knowing multiple teams are waiting for your response.

There is pressure in realizing that a delayed decision may affect several other activities.

There is pressure in trying to balance project deadlines with responsibilities that were never part of the original plan.

And there is pressure to say no, even when it may disappoint people who have come to rely on your willingness to help.

This is where professional commitment can become complicated.

A project manager may recognize that the workload is excessive but hesitate to raise concerns.

They may worry that leadership will interpret the conversation as an inability to manage responsibilities.

They may fear appearing uncooperative.

They may believe that asking for support will undermine the confidence others have placed in them.

So they continue.

They adjust their schedules.

They work longer.

They postpone personal priorities.

They tell themselves the workload will become more manageable after the next milestone.

But the next milestone arrives with additional responsibilities.

And the cycle continues.

Over time, the employee may begin to feel that success is no longer measured by what they accomplish, but by how much more they can absorb.

That is not a healthy foundation for sustained performance.

Organizations should create environments where employees can discuss capacity without feeling that they are questioning their own competence.

A person can be highly capable and still be overloaded.

A person can be committed and still need support.

A person can value professional growth and still recognize that their responsibilities have become unreasonable.

Those statements are not contradictions.

They are realities of professional life.

Why Recognition Alone Is Not Enough

Recognition matters.

Employees want to know that their work is valued.

They want leadership to acknowledge their contributions.

They want to see that their improvements have a meaningful impact.

But recognition becomes less effective when it consistently comes with additional expectations without corresponding support.

Imagine an employee who has successfully delivered a complex project while also improving several internal processes.

Leadership praises the employee's performance.

They describe the individual as dependable, proactive, and essential to the team's success.

Then they assign another initiative.

And another.

And another.

The recognition is sincere.

But the workload continues growing.

Eventually, the employee may begin to question what the recognition actually means.

Does the organization value the contribution enough to protect the employee's ability to continue performing?

Does leadership recognize the effort required?

Is the expanded role reflected in development discussions, authority, compensation, staffing, or revised responsibilities?

Or is the primary reward for successful work simply more work?

This is not an argument that every additional responsibility requires a promotion or salary increase.

Organizations frequently need employees to adapt to changing business needs.

But when a role expands significantly and permanently, the change deserves a deliberate conversation.

Leadership should examine whether the job description still reflects the actual work.

They should consider whether the employee has appropriate authority.

They should evaluate whether additional staffing is needed.

They should discuss professional development and career progression.

They should recognize that appreciation is most meaningful when paired with decisions that support continued success.

The strongest form of recognition is not always praise. Sometimes it means protecting someone's time, clarifying their priorities, and providing the resources they need to succeed.

The Responsibility of the Project Manager: Speaking Up Before the Work Becomes Unsustainable

Leadership has an important responsibility in managing capacity.

But project managers also play a role.

They cannot always assume that others understand the full extent of their workload.

Many additional responsibilities develop gradually.

Some arise through informal conversations.

Others begin as temporary requests.

A few become recurring obligations without anyone formally acknowledging the change.

If the project manager doesn't make those responsibilities visible, leadership may keep making decisions based on incomplete information.

This is where professional communication becomes essential.

The conversation should not begin with blame.

It should begin with clarity.

Instead of saying, "I have too much work," a project manager might explain:

"My responsibilities have expanded beyond the original project delivery scope. In addition to managing the current initiatives, I am now coordinating process documentation, training activities, and several operational improvements. I believe these activities are valuable, but we need to review priorities and determine how to support them without affecting existing project commitments."

That approach changes the conversation.

It identifies the additional work.

It acknowledges its value.

It connects the concern to organizational outcomes.

And it invites leadership to help solve it.

Project managers can also document the time and effort tied to support responsibilities.

This does not require tracking every minute.

The objective is to create visibility.

What recurring activities have been added?

Which responsibilities belong to project delivery?

Which are organizational improvements?

Which require ongoing ownership?

What work is currently delayed or at risk because of competing priorities?

What decisions are needed from leadership?

These questions turn an emotional concern into a management discussion.

They also reinforce a central project management principle.

Identify and communicate risks before they become problems.

Workload capacity is no exception.

Raising a capacity concern is not a failure of leadership. It can be an example of responsible leadership.

The objective is not to avoid additional responsibilities.

The goal is to ensure commitments remain achievable.

The Responsibility of Leadership: Stop Confusing Willingness With Availability

One of leadership's most important responsibilities is understanding the difference between an employee who is willing to help and one who has the capacity to help.

Those two conditions do not always exist together.

A project manager may be enthusiastic about improving a process.

They may recognize its importance.

They may possess the skills required.

But that does not mean they have sufficient time to perform the work without affecting other commitments.

Leadership should resist the temptation to interpret enthusiasm as available capacity.

Before assigning additional responsibilities, managers should ask what the employee is already responsible for delivering.

They should understand existing deadlines.

They should consider the effort the new work will require.

They should identify what they can postpone, delegate, or remove.

And they should determine whether the responsibility is temporary or permanent.

This is especially important when employees have a track record of successfully managing difficult workloads.

High performance should create trust.

It should not eliminate the need for resource planning.

Leadership must also recognize that employees may be reluctant to say no.

Some may fear disappointing their managers.

Others may worry about limiting career opportunities.

Some may believe they must accept additional work to demonstrate commitment.

Effective leaders do not wait for employees to reach their limits before discussing workload.

They ask questions.

They look for patterns.

They examine how responsibilities have changed.

They create opportunities for honest conversations.

And they make it clear that identifying capacity limitations is not the same as refusing to contribute.

A healthy leadership culture allows employees to say:

"I can help with this, but we need to determine what takes priority."

That statement should start a planning discussion, not raise concerns about the employee's attitude.

Reduce the Load or Add Capacity? Why the Answer May Be Both

We return to the central question.

When a project manager's role expands beyond project delivery and into building organizational capability, should leadership reduce the workload or add capacity?

I believe the answer requires more thought than choosing one option over the other.

Sometimes the organization needs to reduce the load.

Sometimes it needs to add capacity.

Sometimes it needs to clarify ownership.

And sometimes it needs to reconsider whether the work should be assigned to the project manager at all.

The appropriate response depends on the nature of the responsibilities and the organization's priorities.

When reducing the load makes sense

Reducing the load may be appropriate when the project manager has accumulated responsibilities that no longer align with the primary role.

Perhaps recurring administrative activities can be reassigned.

Perhaps reporting requirements can be simplified.

Some meetings may no longer be necessary.

Perhaps lower-priority projects can be postponed.

Perhaps temporary process improvement work has reached the point where a permanent owner should take responsibility.

Reducing the load does not necessarily mean eliminating valuable work.

It may mean distributing responsibilities more effectively.

When adding capacity makes sense

Additional capacity may be appropriate when the organization has identified legitimate needs that require ongoing attention.

A new training program may need a dedicated coordinator.

A process improvement initiative may require a business analyst.

An expanding project portfolio may justify additional project management support.

A technical implementation may require specialized resources.

In these situations, the problem is not that the work is unnecessary.

The problem is that the organization hasn't allocated enough resources to complete it sustainably.

When ownership needs to change

Sometimes neither reducing the work nor adding another person immediately addresses the underlying issue.

The problem may be unclear accountability.

A project manager may be performing work because no department has formally accepted ownership.

In that situation, leadership must decide who owns the responsibility.

The project manager can help transition the work.

They can document the process.

They can support training.

But permanent ownership should align with the organization's operating structure.

When priorities must be reconsidered

Sometimes an organization cannot complete every desirable improvement immediately.

Budgets are limited.

Resources are finite.

Business priorities compete.

That reality does not represent a failure.

It represents the need for strategic decisions.

Leadership may determine that one improvement must wait until a major project is completed.

Another initiative may need to be reduced in scope.

A third may require a longer implementation timeline.

Make those decisions openly rather than leaving employees to absorb the conflict through personal effort.

The goal should not be to find a way for one capable person to do everything. The goal should be to organize work so the right people complete the right responsibilities, with realistic expectations.

A Practical Framework for Managing Expanding Responsibilities

Organizations do not need an overly complicated system to address this problem.

They need a consistent way to recognize when responsibilities are expanding and evaluate what that expansion means.

I would encourage leaders and project managers to approach these situations through five considerations.

First: Identify the work.

Begin by documenting the responsibilities the employee is actually performing.

Do not rely exclusively on the original job description.

Include formal projects, recurring operational tasks, process improvements, training, coordination, reporting, and other supporting activities.

The objective is to understand the full scope of the role as it exists today.

Second: Determine ownership

For each responsibility, ask who should ultimately own the work.

Does it belong to project management?

Is it an operational responsibility?

Should a functional department manage it?

Does it require a dedicated process owner?

Is the project manager temporarily supporting the work or expected to maintain it indefinitely?

Clear ownership prevents temporary assistance from becoming permanent dependency.

Third: Evaluate capacity

Estimate the effort required to complete the work effectively.

Consider not only scheduled activities but also preparation, follow-up, communication, documentation, and coordination.

Compare those demands with existing project commitments.

Identify where competing priorities create risks.

Evaluate capacity realistically, not solely based on an employee's past ability to overcome difficult circumstances.

Fourth: Establish priorities

Not everything can be the highest priority.

Leadership should identify which activities are essential, which can be delayed, and which can be delegated.

When the organization approves additional work, it should determine whether existing commitments need to change.

This is where difficult but necessary decisions occur.

A leader may need to explain that a desirable improvement cannot begin immediately.

A project manager may need to recommend postponing an initiative.

A department may need to accept ownership of a process it previously relied on someone else to maintain.

These conversations are part of responsible organizational management.

Fifth: Review and adjust

Responsibilities change.

Projects conclude.

New initiatives begin.

Processes mature.

Employees develop new skills.

Capacity planning should reflect those changes.

A responsibility that was manageable three months ago may no longer be manageable today.

A temporary assignment may have become permanent.

A process improvement may now be ready for transition to an operational owner.

Regular reviews help organizations identify these changes before they create significant problems.

The framework is straightforward:

Identify the work. Clarify ownership. Evaluate capacity. Establish priorities. Review and adjust.

The difficulty is not understanding the steps.

The difficulty is creating a culture where organizations consistently follow them.

What Happens When Organizations Ignore the Warning Signs?

Workload problems rarely appear without warning.

Indicators often appear long before a project manager becomes overwhelmed.

Meetings start to take up more of the day.

Follow-up activities are completed later.

Documentation falls behind.

Decisions require repeated reminders.

Project managers get pulled into conversations that established process owners should handle.

Employees work outside normal hours to complete tasks that require uninterrupted attention.

The organization may begin depending on one individual to explain how multiple processes operate.

When that person is unavailable, progress slows.

These are not always signs of poor individual performance.

They may indicate that responsibilities are no longer distributed effectively.

If the organization ignores those indicators, several consequences can follow.

Project delivery may become increasingly reactive.

Knowledge may remain concentrated in a few individuals.

Employee engagement may decline.

Improvement initiatives may lose momentum.

Departments may become more dependent on informal coordination.

Leadership may struggle to understand why an employee who previously delivered consistently is now struggling.

One of the greatest risks is that the organization may misinterpret the problem.

Instead of recognizing an unsustainable operating model, it may conclude that the employee needs better time management.

Time management is important.

Prioritization is important.

Organization is important.

But none of those skills creates unlimited capacity.

At some point, improving personal efficiency cannot resolve a structural workload problem.

You cannot continuously solve a resource problem by asking the same person to become more efficient.

Eventually, the organization must address how it assigns, supports, and prioritizes work.

The Role of Organizational Maturity

This discussion also raises important questions about organizational maturity.

Organizations develop at different rates.

Some have well-established governance structures and clearly documented procedures.

Others grow rapidly and build processes as new needs emerge.

Some are transitioning between systems, leadership models, or business strategies.

Others have operated successfully for years through informal relationships and institutional knowledge.

No single organizational structure works for every business.

And a lack of formal processes does not automatically mean an organization is ineffective.

But as organizations grow, informal practices can become difficult to sustain.

A process that works for a small team may not work when multiple departments become involved.

A decision-making approach based on personal relationships may become unreliable when employees change roles.

A training method that depends on experienced coworkers may become inconsistent as hiring increases.

These challenges are natural parts of organizational development.

Project managers often encounter them because projects bring people, processes, and departments together.

A project can expose gaps that were previously hidden within individual teams.

This gives project managers a valuable perspective.

They can identify patterns.

They can explain how process weaknesses affect delivery.

They can recommend improvements.

They can help leadership understand where organizational capability needs to grow.

But identifying a maturity gap and owning the entire maturity improvement effort are different responsibilities.

If an organization wants to become more mature in its operations, it must treat that development as an organizational objective.

It may need dedicated resources.

It may need executive sponsorship.

It may need governance changes.

It may need training programs.

It may need clearly defined process ownership.

And it may need time.

Organizations cannot build organizational maturity sustainably through unplanned extra effort from employees who already have full-time responsibilities.

Project managers can contribute significantly to that development.

But the organization must own the commitment.

Why This Matters for the Future of Project Management

The project manager's role continues to evolve.

Organizations increasingly expect project managers to understand business strategy, organizational change, technology, communication, stakeholder engagement, and cross-functional collaboration.

Those expectations reflect the growing importance of project management.

Projects are not simply collections of tasks.

They are mechanisms organizations use to introduce change, deliver value, and pursue strategic objectives.

Project managers often operate at the intersection of those activities.

They see how decisions made in one department affect another.

They understand how unclear priorities influence delivery.

They recognize how inadequate training can undermine implementation.

They observe how missing processes create delays and confusion.

That perspective makes project managers valuable contributors to organizational improvement.

But it also creates a risk.

As the profession becomes more connected to organizational strategy, businesses may expect project managers to take on an increasingly broad range of activities.

Change management.

Process improvement.

Operational coordination.

Training.

Governance.

Strategic reporting.

Technology adoption.

Cross-functional communication.

Each area can be relevant to successful project delivery.

But relevance does not automatically establish ownership.

Organizations need to define what they expect project managers to lead, what they expect them to support, and what belongs to other functions.

Without those distinctions, the profession risks being defined less by its purpose and more by its willingness to absorb responsibilities that don't fit neatly elsewhere.

That would be a mistake.

Project management creates value by coordinating work in a disciplined way toward defined objectives.

Its strength comes from combining planning, communication, leadership, risk management, and sound judgment.

Those strengths should not be diluted by treating project managers as unlimited organizational resources.

The future of project management should include broader influence.

It should include strategic involvement.

It should include opportunities to improve how organizations operate.

But that evolution must come with clearer expectations, realistic capacity planning, and appropriate support.

Expanding project managers' influence should not require endlessly expanding their workload.

A Message to Project Managers: Your Value Is Not Measured by How Much You Can Carry

I want to address project managers directly for a moment.

Many of us take pride in being dependable.

We want to be the person who finds a solution.

We want to support our teams.

We want to demonstrate that leadership can trust us with difficult responsibilities.

And when someone asks for help, our instinct is often to find a way to make it happen.

That commitment is nothing wrong.

But we need to remember something important.

Your value as a project manager isn't measured by how many responsibilities you can carry at once.

It is not measured by how many organizational problems you personally resolve.

It is not measured by how often you sacrifice your own time to compensate for missing resources.

And it is certainly not measured by your willingness to remain silent when expectations become unrealistic.

Your value is reflected in your judgment.

Your ability to recognize risks.

Your understanding of priorities.

Your capacity to communicate difficult information professionally.

Your ability to help teams work toward shared objectives.

And your willingness to make decisions that protect the work's long-term success.

Sometimes that means accepting additional responsibilities.

Sometimes it means recommending a process improvement.

Sometimes it means stepping forward when an organization needs leadership.

But sometimes it means having a difficult conversation.

It means explaining that the current workload is not sustainable.

It means identifying what may be delayed.

It means asking leadership to clarify priorities.

It means recognizing that doing everything is not the same as doing the right things well.

Project managers spend their careers helping organizations understand constraints.

We should not be afraid to acknowledge our own.

Knowing your capacity is not a weakness. It is part of leading responsibly.

A Message to Organizational Leaders: Protect the People Who Protect Your Projects

I also want to address organizational leaders.

When you have a project manager who consistently identifies problems, improves processes, supports teams, and delivers results, you have someone valuable.

That employee may understand your organization in ways that are not immediately visible through formal reporting structures.

They may spot weaknesses before they affect customers.

They may resolve conflicts before they become escalations.

They may connect departments that otherwise struggle to communicate.

They may help employees navigate change.

They may create clarity where confusion previously existed.

Those contributions deserve recognition.

But they also deserve protection.

Not protection from responsibility.

Protection from unreasonable expectations.

Protection from unclear ownership.

Protection from competing priorities that no individual can realistically satisfy.

Protection from becoming the permanent solution to every organizational problem simply because they have demonstrated the ability to solve difficult challenges.

If you value the initiative your employees demonstrate, create conditions that let them keep demonstrating it.

Ask what support they need.

Examine how their responsibilities have changed.

Clarify which work is temporary and which is permanent.

Reassign activities when appropriate.

Invest in additional resources when the business case supports them.

And recognize that sometimes the most effective leadership decision is to remove a responsibility rather than add another.

The objective is not to make work easier simply for the sake of making it easier.

The objective is to make success sustainable.

An organization should not have to choose between delivering projects and improving its internal capabilities.

But achieving both requires deliberate planning.

It requires shared accountability.

And it requires leadership to recognize that people are not unlimited resources.

The Question We Should Really Be Asking

When I consider the original scenario, I don't see a project manager unwilling to contribute beyond a job description.

I see someone who recognized opportunities to improve the organization.

Someone who understood that project delivery depends on more than schedules and task assignments.

Someone willing to help establish the processes, procedures, and training needed for success.

I also see an organization that may genuinely appreciate those contributions.

Leadership may be supportive.

Departments may be cooperative.

The improvements may be valuable.

But even in that positive environment, an important question remains.

How much can one person reasonably be expected to carry?

We often discuss the importance of project managers being adaptable.

We encourage them to demonstrate initiative.

We praise their problem-solving ability.

We celebrate their willingness to lead without formal authority.

Those are admirable qualities.

But adaptability should not eliminate boundaries.

Initiative should not create unlimited obligations.

Problem solving should not become permanent compensation for inadequate resources.

And leadership without authority should not mean accountability without support.

The conversation should not be reduced to whether the project manager is willing to do more.

The more meaningful question is whether the organization is prepared to support the additional work it has recognized as necessary.

That requires honesty from both sides.

Project managers must communicate when responsibilities expand beyond available capacity.

Leadership must respond with more than encouragement.

Together, they must decide what matters most, who owns the work, and what resources are required.

When everything is important, the answer isn't always to ask the same person to do more.

Conclusion: The Best Organizations Do Not Build Success on Unlimited Personal Sacrifice

There is a difference between being a dedicated employee and becoming the solution to every organizational problem.

There is a difference between professional growth and accumulating unlimited responsibilities.

There is a difference between supportive leadership and leadership that actively protects the capacity required for success.

And there is a difference between recognizing necessary work and providing the resources needed to complete it.

Project managers will always encounter situations that require them to step beyond their original plans.

That is part of the profession.

We adapt.

We collaborate.

We solve problems.

We identify opportunities for improvement.

We help organizations move forward.

But we should not confuse that commitment with an expectation that project managers can absorb unlimited responsibilities.

When organizations discover they need additional processes, procedures, training, or operational improvements, they have identified a business need.

That need deserves the same thoughtful consideration as any other business initiative.

What is the objective?

Who owns the work?

What resources are required?

What are the priorities?

What existing commitments will be affected?

How will success be sustained?

Those questions are not obstacles to progress.

They are the foundation of responsible progress.

I believe the strongest organizations are not those where a few exceptional employees somehow manage to do everything.

They are organizations where capable people have clear responsibilities, effective processes, realistic priorities, and leadership willing to make difficult resource decisions.

And I believe the strongest project managers are not those who never question their workload.

They understand that protecting project outcomes sometimes requires challenging the assumptions behind how work is assigned.

We should celebrate employees who take initiative.

We should encourage project managers who identify opportunities to improve the organization.

We should recognize those who willingly contribute beyond their immediate responsibilities.

But we must also understand that continued success requires more than dedication.

It requires capacity.

It requires support.

It requires accountability.

And it requires organizations to recognize when the responsibilities they are assigning have fundamentally changed.

Recognizing that additional work is necessary does not automatically create the capacity to deliver it.

That may be one of the most important leadership lessons in this entire conversation.

Because ultimately, the question is not whether project managers should help organizations improve.

Of course they should.

The question is whether organizations are willing to invest in the people, processes, and resources necessary to make those improvements sustainable.

A capable project manager can help an organization move forward. But a capable organization should never depend on one project manager to carry everything and keep it moving.

A Final Question for Leaders and Project Management Professionals

When a project manager's responsibilities expand beyond managing projects to developing processes, coordinating training, closing operational gaps, and building organizational capability, where should the responsibility for that expanded workload rest?

Should leadership reduce existing commitments?

Should additional resources be assigned?

Should responsibility be redistributed across departments?

Or should organizations reconsider how they define the project manager's role in the first place?

I would argue that the answer begins with recognizing that capacity is an organizational responsibility, not simply an individual challenge to overcome.

What has your experience been?

Have you found yourself managing not only the project, but also the organizational processes needed to make the project successful?

And if so, did your organization recognize the need to adjust your responsibilities, or did the additional work become part of your job?

I would welcome hearing perspectives from both project managers and organizational leaders.

This is not simply a conversation about workload.

It is a conversation about leadership, accountability, professional growth, and what it truly takes to build an organization where success can be sustained.

One publisher said no. One year of work still matters. And my story is far from over.

Today, I received a rejection from a publisher.

There it is. I said it.

Rejection.

A word that can feel so small when we say it, yet carry so much weight when we experience it.

I could tell you that I brushed it off, smiled, and immediately started thinking about the next opportunity. But that would not be entirely truthful.

For a moment, I was disappointed.

I had spent nearly a year working on something I believed in. A project that began as an idea and slowly developed into something meaningful. I spent hours researching, writing, rewriting, questioning myself, learning, and trying to find the right words to communicate what I wanted others to understand.

It was not simply a book proposal.

It was a year of my life, my knowledge, my experiences, and my belief that I might have something worth sharing.

And today, someone decided it was not the right fit.

But I found myself asking: Does someone else's rejection mean my work has no value?

Absolutely not.

And perhaps that is the most important lesson I will take away from today.

When You Put Yourself Out There, You Risk Hearing No

Pursuing something outside your comfort zone comes with a certain vulnerability.

I am a Technical Project Manager. I work with projects, deadlines, challenges, stakeholders, and changing expectations. I understand that not everything goes according to plan.

I also believe strongly in continuing education, personal development, and never letting age, circumstances, or someone else's expectations determine what we can accomplish.

But knowing those things professionally and experiencing them personally are two very different things.

When I decided to write a book about using artificial intelligence effectively in project management, I was stepping into unfamiliar territory.

I was not an established author.

I did not have a collection of published books behind my name.

What I had was experience, curiosity, research, and a genuine desire to help people entering the project management profession.

I wanted to turn what I had learned into something useful for someone else.

I believed, and still believe, that new project managers deserve guidance that helps them understand not only how to use emerging technology but also how to use it responsibly, thoughtfully, and with confidence.

So I started writing.

Some days, the words came easily. Other days, I questioned whether I was qualified to write them.

But I continued.

And eventually, I did something that required even more courage than writing the book.

I shared my idea with someone who had the authority to say yes or no.

Today, the answer was no.

But I refuse to confuse someone's decision with who I am.

Rejection Is an Outcome, Not an Identity

How often do we allow rejection to become personal?

We apply for a position and do not get it.

We share an idea in a meeting and watch someone dismiss it.

We pursue a promotion, an opportunity, a partnership, or a dream, only to discover that someone else doesn't see what we see.

And almost immediately, the questions begin.

Was I good enough?

Did I overestimate my abilities?

Was I foolish to think I could accomplish this?

Who did I think I was?

I know those questions because I have asked them myself.

But I am learning something important.

Being rejected does not mean you are incapable. It means that particular opportunity did not move forward.

There is a difference.

A publisher declining my proposal does not erase the research I completed.

It does not erase the knowledge I gained.

It does not erase the hours I invested or the professional experiences that inspired me to begin.

Most importantly, it does not erase the possibility that my work may eventually reach the people I wrote it for.

It simply means I have another decision to make.

Do I stop here?

Or do I find another way forward?

A Year of Work Is Not a Year Wasted

One of the easiest things to do after disappointment is to look back and question whether the effort was worth it.

A year.

Think about what that means.

A year of evenings spent researching.

A year of ideas that needed organizing.

A year of learning more about artificial intelligence, project management, professional responsibility, and the challenges facing people who are just beginning their careers.

A year of believing that perhaps my experience could make someone else's journey a little easier.

Was all of that wasted because one publisher said no?

Not for a moment.

This project made me a better researcher.

I am a more confident writer because of this project.

I have challenged myself intellectually and professionally.

And I have learned that I can begin something without knowing exactly where it will lead.

That alone has value.

We spend so much time measuring success by the final result that we sometimes forget to recognize who we became while working toward it.

Not every investment produces the outcome we anticipated.

But that does not mean it produced nothing.

Sometimes the greatest return is the person we become through the experience.

Perhaps This Is Where My Project Management Experience Matters Most

As a project manager, I know a plan isn't a guarantee.

We establish objectives, identify risks, develop strategies, and work toward a desired outcome.

And then something changes.

A stakeholder changes direction.

A requirement evolves.

An assumption proves incorrect.

A proposed solution does not receive approval.

What do we do?

We assess.

We learn.

We adjust.

And when the objective still has value, we determine the next appropriate step.

Why should I approach my personal goals any differently?

Today, I received information that changes my original publishing plan.

That does not necessarily change my objective.

My objective was never to receive a publishing contract.

My objective was to create something meaningful that could help others.

That objective remains.

Maybe the next step is another publisher.

Maybe it is revisiting my proposal and strengthening how I communicate the book's value.

Maybe it is exploring a different publishing approach altogether.

Right now, I don't know.

And for once, I am allowing myself to be comfortable with not having every answer.

What I do know is that one closed door does not require me to abandon the entire journey.

Knowing Your Worth Without Needing Everyone's Approval

This may be the hardest part of rejection.

Separating our worth from someone else's willingness to recognize it.

We live in a world where validation can feel like proof of success.

The promotion.

The acceptance letter.

The publishing contract.

The invitation.

The recognition.

Those moments are wonderful, and there is nothing wrong with wanting them.

But what happens when they do not come?

Do we suddenly become less knowledgeable?

Less capable?

Less deserving of an opportunity?

Of course not.

Our value cannot depend entirely on others' decisions.

That does not mean we should ignore constructive criticism or refuse to improve.

Quite the opposite.

I want to learn from this experience. I want to understand what could make my proposal stronger. I want to continue developing as a writer and as a professional.

But I can acknowledge that I have room to grow without deciding that I have nothing worthwhile to offer.

Confidence is not believing that everything we do will be accepted. Confidence is knowing that rejection doesn't take away our ability to try again.

And I believe there is tremendous strength in that distinction.

The Courage to Begin Again

I have written before about self-doubt, continuing education, leadership, and believing in possibilities that others may not immediately recognize.

Today, I find myself practicing the very things I have encouraged others to believe in.

It is easy to write about perseverance when things are going well.

It is harder when you are sitting with a disappointment that matters to you.

But perhaps that is when our words become most meaningful.

When we are willing to live by them.

I have spent much of my life learning that the path forward is not always predictable.

I have raised three children, continued my education, developed my career, and pursued goals that once seemed far beyond my reach.

There have been moments when I questioned myself.

There have been moments when I wondered whether I had started too late or expected too much.

And there have been moments when the easiest choice would have been to stop trying.

Yet here I am.

Still learning.

Still working.

Still finding new things I want to accomplish.

And now, apparently, still trying to become a published author.

That last sentence makes me smile.

Because even after today's disappointment, I can still imagine what might be possible.

What Happens Next?

I wish I could end this article by telling you that I already have another publisher interested.

I cannot.

I wish I could tell you that I have a perfect strategy for what comes next.

I do not.

What I can tell you is that I am not walking away from something I have invested a year in simply because the first path did not lead where I hoped.

I may need to revise.

I may need to research other opportunities.

I may need to ask more questions, seek guidance, and learn more about an industry that is still relatively new to me.

And perhaps I will hear no again.

That possibility is real.

But so is the possibility that someone, somewhere, will see the value in what I am trying to create.

And even if the traditional publishing route never becomes my path, another way may exist to bring this work to the people who could benefit from it.

The important thing is that I keep making thoughtful decisions rather than letting disappointment make them for me.

To Anyone Who Has Recently Heard No

Maybe you did not get the job.

Maybe your proposal was declined.

Maybe someone questioned your abilities.

Maybe you worked for months or years toward something that did not turn out as you hoped.

I will not tell you rejection doesn't hurt.

Sometimes it does.

Especially when the opportunity represents something deeply personal.

But I will encourage you to remember something.

You are allowed to be disappointed without being defeated.

You can question your approach without questioning your entire worth.

You are allowed to take time to process what happened without deciding that your journey is over.

And you are absolutely allowed to try again.

Not because success is guaranteed.

But because one person's "no" shouldn't automatically become your final answer.

My Final Thought: I Have No Regrets

Today, I received a rejection from a publisher.

Tomorrow, I will still have a book I believe in.

I will still have a year of research, writing, and learning behind me.

I will still have the experiences that inspired me to begin.

And I will still have the desire to help others navigate the changing world of project management.

Would I have preferred a different response today?

Absolutely.

Am I disappointed?

Yes.

Do I regret spending a year pursuing this?

Not for one second.

Because I did something that mattered to me.

I took an idea seriously enough to turn it into a project.

I invested in myself.

I took a chance.

And even though the answer wasn't what I wanted, I am proud I dared to ask.

So what do I do now?

I look for the next opportunity.

I keep learning.

I keep writing.

And I remind myself that my worth was never waiting inside someone else's acceptance letter.

Today, a publisher said no.

But I have not said no to myself.

That may be the most important decision I make on this entire journey.

Why Our Experiences, Perspectives, and Willingness to Speak Up Matter More Than the Titles We Hold

Today, something happened that made me stop and think.

Someone reached out after reading something I wrote and shared. They sent me an article and asked for my opinion.

A simple request, right?

Yet, for a moment, I was genuinely taken aback.

Me? You want to know what I think?

My immediate reaction wasn't to analyze the article or organize my thoughts. Instead, I wondered why this person would be interested in my perspective.

I am not a CEO. I do not run a multimillion-dollar company. I am not an executive sitting in a boardroom making decisions that affect thousands of employees.

I am a technical project manager, an educator, a graduate student, a mother, and someone who has spent years learning, working, making mistakes, overcoming challenges, and trying to become a better version of herself.

So why would my opinion matter?

And then another thought occurred to me.

Why wouldn't it?

That question stayed with me, and the more I thought about it, the more I realized that this small interaction represented something much bigger.

How often do we convince ourselves that our voices aren't important enough to be heard?

How often do we hold back an idea because someone else in the room has a more impressive title, more education, more experience, or greater authority?

And perhaps most importantly, how many valuable perspectives go unheard because the person holding them doesn't believe they have earned the right to speak?

When Did We Start Measuring the Value of a Voice by a Job Title?

Somewhere along the way, many of us began associating credibility with position.

We listen when the CEO speaks.

We pay attention when an executive shares an opinion.

We quote successful entrepreneurs, industry leaders, professors, and public figures.

Nothing is inherently wrong with that. Experience, education, expertise, and responsibility can provide valuable insight.

But when did we decide those qualities exist only at the top of an organizational chart?

A person doesn't suddenly become insightful the day they get a promotion.

A new title does not automatically create wisdom, emotional intelligence, or sound judgment.

Likewise, someone without an executive position doesn't lack meaningful knowledge simply because a prestigious designation doesn't follow their name.

Consider the employee who has spent fifteen years working directly with customers. That individual may understand customer frustrations better than an executive who primarily reviews quarterly reports.

Consider the administrative assistant who notices communication problems long before management realizes something is wrong.

Consider the technician who identifies a process improvement because they work with the system every day.

Or the teacher who recognizes that a student is struggling long before the grades reflect it.

Knowledge does not belong exclusively to those who hold authority.

It exists wherever people observe, question, learn, and experience the world around them.

Sometimes the person with the most valuable insight is the one who has been sitting quietly, waiting for someone to ask what they think.

The Quiet Voice of Self-Doubt

What surprised me most about today's interaction was how quickly self-doubt appeared.

I have spent years developing my professional skills, managing projects, collaborating with teams, teaching, and continuing my education.

I have written articles about leadership, personal growth, resilience, and the importance of believing in yourself.

Yet when someone asked for my perspective, my first instinct was to question whether I was qualified to give it.

Isn't that interesting?

We can spend years encouraging other people to recognize their value while still struggling to recognize our own.

I wonder how many people experience that same hesitation.

Perhaps you sat in a meeting when an idea came to mind but stayed silent because you thought someone more experienced would eventually suggest it.

Perhaps you considered writing an article, sharing a professional observation, or joining a discussion, only to convince yourself nobody would be interested.

Perhaps you have looked around a room full of impressive titles and assumed everyone else's opinion carried more weight than yours.

I believe these moments are more common than we realize.

But here is something I am continuing to learn.

You do not need to know everything to have something meaningful to contribute.

You do not need to be the most experienced person in the room.

You do not need universal agreement.

And you certainly do not need permission to think independently.

Your perspective is shaped by experiences that no one else has lived in the same way.

That doesn't make every opinion automatically correct, but it does mean your perspective may offer something another person hasn't considered.

Experience Is an Education of Its Own

One reason this interaction affected me is that I have never believed learning happens exclusively in a classroom.

I value formal education tremendously. I am continuing my own graduate studies because I genuinely love learning.

But some of the most meaningful lessons in my life have come from experiences that never resulted in a certificate or degree.

Being a mother taught me responsibility, patience, sacrifice, and perseverance.

Navigating challenges as a single mother taught me to make difficult decisions, adapt as circumstances changed, and keep moving forward when the path was uncertain.

Technical project management has taught me that communication, trust, accountability, and understanding people matter as much as schedules, budgets, and deliverables.

Teaching has reminded me that learning is not simply about providing answers. It is about encouraging curiosity, asking questions, and helping others discover what they can achieve.

Returning to higher education has reinforced my belief that growth has no expiration date.

Every one of those experiences has shaped how I view leadership, education, professional development, and success.

Does that mean my opinions are always right?

Of course not.

I expect to be challenged. I expect to encounter people who disagree with me. And I hope to continue learning from those conversations.

But I am beginning to understand something important.

My experiences don't have to resemble someone else's to have value.

And neither do yours.

Why Good Leaders Ask for Opinions

As a project manager, I spend a great deal of time thinking about communication, collaboration, and how teams make decisions.

One of a leader's biggest mistakes is assuming the most valuable ideas will always come from the most senior people.

In reality, successful collaboration depends on understanding different perspectives.

A developer may spot a technical risk a project manager overlooked.

A quality assurance professional may identify a problem that everyone else considers minor.

A business analyst may recognize that a requirement does not fully address what the customer needs.

A new employee may ask a question that challenges a process everyone else has accepted for years.

And sometimes that simple question changes everything.

This is why I believe leadership should never be confused with having all the answers.

Leadership also means creating an environment where people feel comfortable sharing their answers, questions, concerns, and ideas.

When individuals believe their opinions will be dismissed, they often stop sharing them.

And when people stop sharing, organizations lose opportunities to learn.

We cannot claim to value collaboration while only listening to people who agree with us.

We cannot encourage innovation while discouraging questions.

And we cannot build strong teams if people believe their professional worth depends entirely on their position in the organizational hierarchy.

A leader does not need to agree with every opinion.

But a good leader should listen, consider the reasoning behind it, and recognize that valuable insight can come from unexpected places.

Having an Opinion Does Not Mean You Have to Be Right

Another part of this conversation deserves attention.

Having an opinion is not the same as possessing expertise, and being asked for your thoughts does not mean you are expected to provide the definitive answer.

Sometimes people ask for our opinions to understand how someone else sees an issue.

They may be looking for a different interpretation, an experience they have not considered, or simply an opportunity for meaningful discussion.

That is one of the things I appreciate most about thoughtful conversations.

We do not have to agree to learn from one another.

In fact, some of the most valuable discussions I've had involved people who challenged my assumptions.

They made me reconsider something I thought I understood.

They encouraged me to research a subject more deeply.

They helped me recognize that an issue was more complicated than I initially believed.

And sometimes they changed my mind.

I don't see that as a weakness.

I view it as growth.

The purpose of sharing an opinion should not always be to convince someone that we are right. Sometimes it should simply be to expand the conversation.

There is a difference between speaking confidently and refusing to listen.

There is also a difference between having an informed opinion and assuming our personal experience represents everyone's reality.

Our opinions become more valuable when we stay curious, examine evidence, acknowledge what we don't know, and are willing to reconsider our conclusions.

That is what meaningful dialogue should encourage.

The Opinions We Never Hear

I keep returning to one question.

How many people have something important to say but never say it?

How many ideas are lost because someone believes they are not educated enough?

How many professionals stay silent because they fear being judged?

How many young people convince themselves that their thoughts are unimportant because no one has ever taken the time to ask?

And how many adults carry that same belief long after gaining valuable knowledge and experience?

I think of people who have worked tirelessly behind the scenes, raised families, supported organizations, served their communities, and overcome challenges others may never fully understand.

Their experiences have taught them things a textbook can't always capture.

Yet they may never consider themselves qualified to contribute to a larger conversation.

That is something I hope we can change.

Not by suggesting every opinion is equally informed or that expertise doesn't matter, but by recognizing that everyone deserves the opportunity to contribute, ask questions, and be treated with respect.

We should encourage people to speak thoughtfully, not remain silent out of fear.

We should teach young people that asking questions shows curiosity, not inadequacy.

And we should remind professionals at every stage of their careers that meaningful contributions aren't reserved for those in the highest positions.

Sometimes All It Takes Is Someone Asking

Perhaps the most meaningful part of today's experience was not the article itself.

It was the fact that someone thought to ask me what I believed.

They may not have realized that such a simple question would make me reflect on my own confidence and sense of professional worth.

But it did.

It reminded me of how powerful it can be when someone shows genuine interest in another person's perspective.

Think about the last time someone asked for your opinion and truly listened.

Not because they needed your approval for a decision.

Not because they were required to include you in a discussion.

But because they genuinely wanted to understand what you thought.

That experience matters.

It communicates respect.

It acknowledges that your experiences may offer insight.

And it creates an opportunity for connection.

I believe we underestimate how much encouragement can come from a simple question:

"What do you think?"

Those three words can invite someone into a conversation they might otherwise have avoided.

They can give a quiet employee the confidence to share an idea.

They can encourage a student to participate.

They can remind someone who doubts their abilities that their perspective matters.

And sometimes they can inspire an entire article.

You Do Not Need a Title to Have a Voice

I have written before about the belief that leadership does not require a title.

Today reminded me that the same principle applies to having a voice.

You do not need to be a CEO to offer meaningful insight into leadership.

You do not need to own a company to understand workplace challenges.

You do not need to be a professor to appreciate the importance of education.

You do not need to be famous to inspire someone.

And you do not need to have lived a perfect life to share something valuable from your experiences.

Sometimes the lessons we learn through setbacks, mistakes, uncertainty, and perseverance are exactly what someone else needs to hear.

I think about the person I was years ago, questioning my decisions, navigating responsibilities, and wondering whether I was capable of accomplishing certain goals.

I think about the person I am today, still learning, still questioning, and still working toward becoming better.

Both versions of me had something meaningful to contribute.

I did not always recognize it.

And perhaps that is the lesson I needed today.

We do not suddenly become worthy of being heard when we reach a particular level of success. Our voices matter throughout the journey.

A Reminder to Myself, and Perhaps to You

When I began thinking about today's interaction, I almost dismissed it as something small.

Someone asked for my opinion.

That was all.

But sometimes the smallest moments reveal the beliefs we have quietly carried about ourselves.

For a brief moment, I questioned why anyone would want my perspective.

Then I realized I was measuring my value against positions I had never claimed.

I was comparing my experience to someone else's title rather than recognizing what my own journey had taught me.

And I suspect I am not alone.

So here is what I want to remember, and what I hope others will remember as well.

Your opinion doesn't have to be the loudest to matter.

Your experiences do not have to be extraordinary to teach someone something.

Your professional title does not determine whether you can contribute to an important conversation.

And your willingness to listen, learn, and reconsider your thinking can strengthen your perspective, not weaken it.

We should never confuse being heard with always being right. We should also never confuse humility with having nothing worthwhile to say.

Today, someone asked for my opinion.

At first, I wondered why.

Now I'm grateful they did because it reminded me of something I believe deeply but sometimes forget to apply to myself.

Everyone has a story. Everyone has experiences that have shaped their understanding. Everyone can contribute something meaningful.

Not every opinion will change a decision.

Not every idea will be accepted.

Not every conversation will lead to agreement.

But sometimes a single perspective can challenge an assumption, encourage a new way of thinking, or help someone feel less alone in their experiences.

Sometimes the person offering that perspective isn't the CEO, the executive, or the person with the most impressive résumé.

Sometimes it is simply someone who has lived, learned, struggled, grown, and found the courage to share what they think.

So the next time someone asks for your opinion, resist the temptation to wonder why they would want to hear from you.

Instead, consider what your experiences have taught you, what you genuinely believe, and what you might contribute to the conversation.

And just as importantly, remember to ask others what they think.

A voice's value isn't determined by the title attached to it.

Sometimes the most important perspective in the room belongs to the person who has never been asked to share it.