Two Kinds of “Just”

The phrase that makes professionals groan

Every workplace has a phrase that makes experienced people quietly grind their teeth.

It starts like this.

“Can’t you just…”

Can’t you just add that field to the report?
Can’t you just tweak the dashboard?
Can’t you just build a quick tool for that?

The person asking thinks it is a five minute change.

The person doing the work knows it is five days and twenty pages of code.

At the AASP Leadership Summit this phrase came up and the room reacted instantly. Heads nodded. People laughed the kind of laugh that says yes, this happens to me every week.

Because “just” is deceptive.

It compresses complexity.
It hides the real work.
And it quietly assumes the barrier is the person, not the problem.

In most organizations, that tiny word creates a lot of friction.

A watercolor interruption

A few days later I was painting coffee cups.

Readers will be happy to know I have moved on from sewing and am now experimenting with watercolor. Apparently my free time has turned into a rotating hobby laboratory.

I was practicing shapes. Coffee cups. Teapots. Playing with color, shadows, and the general chaos that comes with learning something new.

At one point I paused and thought:

“What if I just…”

And then I stopped.

Because this “just” felt completely different.

Same word. Different posture.

The “can’t you just” version minimizes complexity.

The “what if I just” version invites curiosity.

Same word. Completely different posture.

One assumes the answer is easy and the person doing the work is the problem.

The other opens the door to experimentation.

What if I just try a different brush here.
What if I just add a little more shadow.
What if I just see what happens if the cup tilts this way.

No pressure. No assumption that it will work.

Just a tiny test.

The leadership shift

This is the shift curious leaders make.

They move teams away from “can’t you just” thinking and toward “what if we just” experiments.

Instead of pushing for an immediate answer, they create space for a small test.

What if we just try this with one donor segment.
What if we just prototype the dashboard before building the whole system.
What if we just look at last year’s data before redesigning everything.

Tiny experiments do two important things.

They reduce risk.

And they make the hidden complexity visible.

Once you see the real shape of the problem, better decisions follow.

Where inflection points hide

Every big project has moments where things could go in very different directions.

A rushed assumption.
A dismissed concern.
A curious question.

These moments are easy to miss in real time. They look small. Ordinary. Just another conversation.

But they are often inflection points.

The moment when a team shifts from assumption to curiosity.

From “can’t you just” to “what if we just.”

Same word.

Very different path forward.