It Would Be Easier If: Find the Problem Hiding in Your Complaints

Teams rarely struggle to come up with solutions. They struggle to say, plainly, what actually hurts.

So the room fills with fixes for a problem nobody has named. Everyone is solving, and nobody agrees on what. Until the pain is named, every solution is just a guess wearing confidence.

It would be easier if… is how I get a room to name it. Watch the video, then use the worksheet to do it yourself.

How to use this

1. Download the follow-along worksheet. It matches the video part by part.
2. Press play, and pause whenever I ask you to write.
3. Bring one Easier If to your next team meeting.

What you'll do

• Replay your day. Start when you open your laptop. Where's the first speed bump? What have you answered four times today? What jolts you awake at bedtime? Notice the good moments too.
• Write it out. Your frustrations, the things you did over and over, what went well, and what you or others could have done better.
• Turn your top grievance into "It would be easier if…" Write two or three, then move to the next one.
• Dig up what's underneath. Every Easier If hides one of two things: a pain point dressed up as a solution, or a solution dressed up as a pain point.

What an Easier If is really saying

• "It would be easier if AI would just do it." Underneath: the work is repetitive, nobody owns it, and nobody has said that out loud.
• "It would be easier if we just canceled this meeting." Underneath: no decision-maker is in the room, so nothing ever closes.

Why the wild ones matter most

"It would be easier if we fired everyone."

Don't argue with it. The wilder the statement, the louder the signal underneath it. Don't ask whether it's a good idea. Ask why it felt like the easiest path, because that tells you how unbearable the current situation feels.

Stack the questions

On its own, an Easier If is a spark, not a system. It narrows the raw material and starts to uncover the problem. It doesn't define the problem or solve it. So stack it with three question frameworks:

1. Own it: the question behind the question. From John G. Miller's QBQ, a framework on personal accountability. Trade "why," "when" and "who" for "what" and "how," and trade "they" for "I." Not "Who dropped the ball?" but "What can I do so the handoff goes better next time?"
2. Define it: the Phoenix Checklist. Originally developed by the CIA so analysts could interrogate a problem before trying to solve it, and popularized by Michael Michalko in Thinkertoys. It makes sure you're solving the problem, not a symptom of it.
3. Go wide: SCAMPER. Substitute, combine, adapt, modify, put to another use, eliminate, reverse. Get as many options on the table as fast as you can.

The whole flow

• Easier If. What's the raw complaint or wish? The room moves from silence or venting to a named pain.
• Own it. What's my role in it? The room moves from blame to ownership.
• Define it. Are we solving the right problem? The room moves from an assumed problem to a precisely defined one.
• Go wide. What are the possible solutions? The room moves from one narrow option to a wild field of options.

And that's just the warm-up.

Keep going

• Download the worksheet and work through it page by page as you watch.
• Want to work it on a whiteboard, alone or with your team? Duplicate the free Easier If Miro template. It gives every Easier If its own lane.
• Want an outside read on where your systems are stuck? Take the free AI Clarity Assessment.

The pain is already in the room. The questions just need to find it.