Taking Action under Pressure

January 2026

Hard decisions are often hard not because you lack facts but because what you want won’t all work together. You want to volunteer, but you don’t want to give up your evenings. You want to move, but you don’t want to uproot your kids. You want a pet, but you don’t want to lose your freedom.

When this happens, a natural reaction is to list more pros and cons, do more research, or have more conversations. But that often misses the real problem. The difficulty isn’t uncertainty. It’s a conflict between what matters.

Instead, focus on your drivers: the results you’re trying to protect, gain, avoid, or preserve. Spend your energy deciding which drivers must guide the decision, and which can only support.

Try this

• • Write down a decision that’s hanging over you and list the options.
  • For each option, ask: “If I choose this, what am I trying to protect, gain, avoid, or preserve?” Those answers are drivers.
  • Pick the one or two drivers you would truly regret ignoring.
  • Use those drivers to make the choice.

Example

• • Decision: Should I take on a weekly volunteer role or not?
  • Drivers: Protecting weeknights for family, supporting a cause I care about, staying connected with the community, learning new skills.
  • Guiding drivers: Protecting my weeknights and supporting the cause.
  • Choice: Don’t take the weekly role. Find another way to help.

From PMEZ’s STEADY Approach

December 2025

Most advice starts with how.

• • How to manage your time.
  • How to communicate better.
  • How to plan.
  • How to stay motivated.

But when people feel stuck, how is often the wrong place to start. It assumes an approach without  knowing the problem.  And feeling stuck can come from different places.

Sometimes it’s from the burden of pressure. Too many important decisions must be made. Too many things must be done at once.  Too many opinions are slowing you down.

Sometimes it’s from the frustration of losing momentum . You have important ideas and goals, but you never quite finish them. You’re busy, but progress is uneven.  You’re working towards one thing, but the rules change.  You’re halfway done, but you run out of money.

Sometimes it’s from the sheer size of the endeavor. The work involves many teams, moving parts, resources and expectations. It requires handoffs, approvals and checkpoints. And it lasts for months and months. 

Those are three different problems. Tackling them in the same way will lead to mixed results.

That’s why PMEZ has three approaches for when you’re stuck:

• • STEADY is for moments when pressure interferes with sound thinking and action.
  • DONE is for when something important needs to be brought to completion.
  • NAVIGATE is for when a team or organization must deliver something big.

Each approach has been adapted from engineering and project management for everyday life.  But each fits a different kind of challenge because not everything needs a plan, gets fixed with a simple hack, or is tied to achieving a goal.

Start by understanding what your problem is.  Then decide how to proceed using the right approach for the problem.

From PMEZ’s STEADY–DONE–NAVIGATE approach

December 2025

When you’re doing something that matters, people will have opinions. Some are useful. Many aren’t. If you treat all input as equal, you can get pulled off course, slow down decisions, and end up optimizing for someone else’s preferences instead of your own.

A practical way through this is to decide who has a say based on their role in what you’re trying to achieve.

• • Engage: directly affected or accountable for the outcome. They get a say.
  • Target: helpers or experts. They get a say only in their lane.
  • Sincerely acknowledge: everyone else. You listen, thank them, and move forward as you see fit.

This isn’t cold. It’s how you keep the right people involved, ensure quieter voices aren’t drowned out, and avoid wasting energy on endless justifications. It’s also how you prevent “whoever talks the most” from steering the work.

Try this

• Pick one goal you care about.
• List every person who has offered input, might offer input, or should have input but hasn’t weighed in.
• Then label each person as Engage, Target, or Sincerely acknowledge.
• For anyone you Target, write their lane (for example: reviewing designs, making an introduction, giving a recommendation, handling a specific task).

Example

Planning a wedding

• Engage: the couple and those paying
• Target: the friend doing flowers (flowers only), the musician (music only).
• Sincerely acknowledge: the cousin with strong opinions about “what weddings should be.”

From PMEZ’s DONE approach

November 2025

Worry shows up as a voice in your head, so it can feel personal. It’s thoughts of what could happen. What if it rains at the fair? What if the car breaks down again? What if I finish late?

When someone shares a worry, the response is often: “don’t stress,” or “it’ll be OK,” which means well, but avoids addressing the concern. Without a way to talk about uncertainty, worry stays personal and can grow.

But in engineering and project work, “it’ll be OK” is not an appropriate answer. If a builder is worried the beams are too weak for the skyscraper, nobody says, “try to relax.” The worry gets stated, assessed, and handled.

Worries and risks are both about uncertainty. The difference is what you do next. Risk is worry that’s been pulled out into the open and addressed with the right amount of action. Any uncertainty, at home, at work, at school, can stay as worry, or it can become a risk you can respond to.

Try this

• Write a vague worry as a specific risk
• Pick one small action that reduces the likelihood it occurs.

Example

• Vague worry:  I might mess up the presentation
• Risk:  I might run long or I might sound nervous
• Action:  Rehearse out loud with a few friends and a timer.

From PMEZ’s STEADY approach

October 2025

Many small organizations don’t want “project management.” People don’t have time for a new vocabulary, a stack of templates, or complicated tools.

But they still want their projects to move.

NAVIGATE helps by providing a lightweight project structure to run a project. But structure alone doesn’t guarantee success.

In practice, projects can succeed or fail based on a collaboration skills. When those skills are strong, a lightweight approach works fine. When they’re weak, even a well-trained team can stall—because the problem isn’t the method. It’s how people are working together.

Three skills matter more than most teams expect:

Communication that actually transfers information:

Not updates. Not long emails. Not meetings that end with “great discussion.” Real communication pulls the right information out early, catches misunderstandings before they become rework, and explains decisions clearly enough so people can act.

Conditions that encourage contributions:

Teams in smaller organizations tend to be ad hoc and overloaded. Priorities shift. Dependencies multiply. Someone has to provide direction when things are confused, make it OK to surface issues, and care about morale.

Conflict handling before it turns into delay:

Most conflict isn’t a blow-up. It’s side conversations, quiet resistance, and decisions that never quite get made. The practical skill is naming the real disagreement early and resolving it without making everything personal.

NAVIGATE combines simple structure with these collaboration skills so work keeps moving—without confusion, unnecessary friction, or preventable problems.

From PMEZ’s NAVIGATE approach