You've made the call. The decision's on the table. So what now — do you just sit back and hope it works out?
Turns out, a lot of people treat "making a choice" as the finish line. In any real problem solving process, the step that comes right after you decide is the part where most things actually succeed or fall apart. It isn't. And it's the part nobody talks about at dinner parties.
The short version is this: after making a choice, the next problem solving step is usually implementation — putting the decision into action — followed closely by evaluation. But the way those two play out in real life is messier than any textbook diagram suggests Simple, but easy to overlook. Took long enough..
You'll probably want to bookmark this section.
What Is the Step After Making a Choice
Let's be honest. When someone asks "which problem solving step comes next after making a choice," they're usually picturing a neat flowchart. Step 1: identify problem. Step 2: list options. Step 3: pick one. Step 4: ??? Most people skip this — try not to. Turns out it matters..
The "???" is where it gets interesting.
In plain language, once you've chosen a path, you move from deciding to doing. Plus, that's implementation. Which means it's the act of carrying out the solution you selected. But implementation isn't just blind execution. You're translating a mental decision into real-world moves — and the real world pushes back Worth keeping that in mind..
Decision vs. Action
Here's what most people miss: a choice is a hypothesis. That's why you've guessed that Option B will fix the leaking pipe, calm the angry client, or get your side project shipped. Until you act, it's untested. Implementation is the experiment Most people skip this — try not to..
And look, some frameworks split this into "act" and "check.In practice, " The labels vary. Plus, " Others call it "execute and monitor. The point doesn't: the step after choosing is proving the choice was any good Easy to understand, harder to ignore. No workaround needed..
Why "Evaluation" Tags Along
You can't have implementation without some form of evaluation riding shotgun. Here's the thing — even if you don't write it down, you're watching. Did the thing do the thing? That watching is evaluation. So really, the next step isn't one step. It's a two-beat move: do, then see That's the whole idea..
Why It Matters
Why does this matter? Because most people skip it.
I know it sounds simple — but it's easy to miss. Also, you make a tough call at work, announce it in a meeting, and everyone nods. Here's the thing — two weeks later the problem is back, worse than before, and someone says "well, we tried that solution. " Did you, though? Nobody owns the follow-through. Which means then the meeting ends. Or did you just decide to?
In practice, the gap between choosing and implementing is where good ideas go to die. Also, a friend of mine once "decided" to switch his small business to a new inventory system. This leads to he picked the software. Day to day, he told his team. And then he kept using the old spreadsheets because training felt like a hassle. The choice meant nothing without the step after.
And on the flip side — evaluation done wrong hurts too. If you act but never check whether it worked, you can double down on a broken fix for months. That's how companies sink money into strategies that looked great in the deck and never got measured.
The official docs gloss over this. That's a mistake.
How It Works
So how do you actually do the step after making a choice without fumbling it? Here's the meaty part Took long enough..
1. Name the First Concrete Move
Right after you decide, write down the very next action. If you chose to change your diet, the first move might be "throw out the soda tonight.Not the whole plan. That said, the next action. " If you chose a new hiring process, it's "draft the new interview script by Friday.
Small, specific, dated. That's implementation starting instead of stalling.
2. Assign Ownership (Even If It's Just You)
A decision with no owner is a wish. Say who does what. In a team, this is obvious but often skipped. Solo? Then literally say out loud "I am doing X on Tuesday." Sounds dumb. Works.
3. Set a Check-In Point Before You Start
We're talking about the evaluation half, pre-loaded. Before you act, decide when you'll look at the result. "After two weeks, I'll see if support tickets dropped." Without a date, evaluation becomes "someday," which means never.
4. Do the Thing, Watch the Edges
Now execute. But here's the real talk: watch for friction. Implementation always surfaces hidden problems. The software needs a permission you didn't know about. The conversation you planned goes sideways. Note those. They're data Easy to understand, harder to ignore..
5. Evaluate Honestly
At the check-in, ask the only question that counts: did it move the original problem? Even so, not "did we do what we said" — that's just activity. Did the problem shrink? If yes, keep going. If no, the next problem solving step is revisiting the choice — not shame, just loop back.
6. Adjust or Exit
Sometimes implementation reveals your choice was wrong. Good. That's the system working. The step after a failed evaluation is "identify why" and then either tweak the approach or pick a different option from the old list. You're not starting over. You're cycling.
Common Mistakes
This section is where I get opinionated, because the mistakes here are painfully repeatable It's one of those things that adds up..
Mistake one: confusing announcement with action. You told people the decision. That's not implementation. I've watched whole departments celebrate a "solution" that existed only in a Slack message.
Mistake two: no success metric. If you can't describe what "fixed" looks like, evaluation is impossible. "Improve morale" isn't measurable. "Turnover under 10% this quarter" is Small thing, real impact..
Mistake three: evaluating too late. Six months is too late to learn the fix made things worse. The step after making a choice needs a near-term mirror, not a year-end review.
Mistake four: protecting the decision. Once some folks choose, they defend it even as it burns. The next step isn't "prove I was right." It's "find out if it worked." Those are different.
Mistake five: skipping the loop. Problem solving isn't linear for messy real issues. You decide, act, learn, adjust. People who treat the choice as final and never revisit are the ones stuck The details matter here..
Practical Tips
Here's what actually works, from someone who's botched this plenty.
- Write the next step on the same note as the decision. If your choice lives in your head, the follow-through won't.
- Use a stupidly simple tracker. A checkbox in a notes app beats a fancy dashboard you'll ignore.
- Tell a friend. Accountability isn't corporate fluff. Say your plan out loud to someone who'll ask "so how'd that go?"
- Expect the first attempt to be rough. Implementation v1 is rarely clean. That's normal. Evaluation is how you clean it.
- Keep the old options visible. When you circle back, you don't want to re-brainstorm from zero. The list you made before choosing is gold the second time.
- Separate "did we do it" from "did it work." Two questions. Both needed. Most teams only ask the first.
And look — if you're solving a personal problem, same rules. And the step after is the first week of tracking spend. But chose to end a toxic arrangement? Chose to budget better? The step after is the actual conversation, then noticing if your stress drops Which is the point..
FAQ
What is the immediate next step after making a decision in problem solving? Implementation — taking concrete action on the choice you made. Right after that comes evaluation, where you check if the action actually addressed the problem.
Is evaluation really part of the step after choosing, or a separate step? It's bundled. You act, then almost immediately start watching results. Most models list them as distinct phases, but in real life they overlap. You can't implement blind and call it done.
What if my chosen solution doesn't work after I try it? That's expected sometimes. The next move is to analyze why, then either adjust the implementation or return to your earlier options and pick differently. Problem solving cycles; it doesn't end at a bad result.
**Why do teams struggle with the step after
the decision more than the decision itself?**
Because the decision feels like progress. The step after—actually doing the thing and finding out it was wrong—carries none of that polish. It closes a meeting, fills a slide, and gives everyone the comfort of motion. It exposes friction, and most teams would rather ship a confident plan than survive an honest "this isn't working." So they optimize the choice and neglect the carry-through, which is where the real problem either dies or multiplies Surprisingly effective..
Conclusion
The step after making a decision is where problem solving is won or lost. A decision is a starting line, not a finish. Treat implementation and evaluation as one continuous movement, keep your old options in sight, and stay willing to be wrong out loud. Think about it: not in the brainstorm, not in the vote, but in the unglamorous act of doing, watching, and correcting. The work begins the moment you choose—and it doesn't end until the problem is actually gone The details matter here..
