Because too many buttons feel like responsibility, not empowerment.
There's a moment in a lot of internal apps where users freeze. Not because the process is hard. Because the screen gives them six options that all look equally important.
Call, email, create, edit, save, submit, escalate, assign, approve.
All visible. All loud. All competing for attention.
On paper, that looks helpful. In reality, it creates a very human reaction: hesitation. When everything is an action, nothing feels like the right action.
This is what I call "button panic." It's not a "bad maker" problem. It's a design problem. Most business apps are built with good intentions — let's give users all the tools they might need. But intention is not the same as clarity.
Games teach us a different lesson. In games, you can do a hundred things too. Yet you rarely feel lost — because the experience always makes one thing feel like the smartest next move. Always.
That feeling is what we need in business apps. Not fewer features. Better direction.
The Game UX Principle Behind "Next Best Action"
Games are masters at guiding attention. Even in open-world games like Minecraft, you still get a quest marker — a highlighted objective, a next mission suggestion, a clear signal that says: this is what matters right now.
That's not controlling. That's reducing mental noise.
CTA chaos triggers three hidden problems:
Decision fatigue
Every button is a micro-decision. Users don't feel "powerful" when they face many decisions. They feel tired. Games reduce decision fatigue by turning a complex set of options into one clear recommendation. You can still choose something else — but the default path is obvious.
Fear of choosing wrong
Business apps often carry consequences. You might notify the wrong person, submit the wrong data, create a record that triggers a workflow. When a user is unsure, they stall.
Games are surprisingly good at preventing this. They make the safe path clear, the consequences understandable, and they let you undo or confirm. HUD thinking makes actions feel safer because the path is predictable.
No sense of flow
Flow happens when the next action is clear and the feedback is immediate. Button panic breaks flow because users keep stopping to decide. The pattern is simple: make the next best action visible, and push everything else into calm, secondary space. This is not about removing actions — it's about hierarchy.
How to Apply the Quest Marker Pattern in Power Apps
This pattern works in almost every Power App, especially ones that include a list and a detail view. The goal is to make your app answer one question instantly: what should I do next?
1. Define the primary outcome for each screen
Most screens have one main job. A list screen is usually about selecting or creating. A detail screen is usually about updating or completing. A review screen is usually about submitting.
If your screen has no primary outcome, users will invent one. That's risky.
Pick one primary action per screen — not per app, per screen.
2. Create an explicit "Next Step" area
Instead of placing five buttons in a row, create a single card or banner:
Next step — based on your current status, do this.
Then put one strong primary button inside it. That's your quest marker. Everything else becomes secondary: a small "More actions" menu, context actions hidden behind an icon, secondary links lower on the screen. Users still have access — but the app stops shouting.
3. Make the next best action depend on status
This is where business apps become smart and feel game-like.
- If status is Draft → next step is Complete details
- If status is Ready → next step is Submit
- If status is Submitted → next step is View confirmation
- If status is Blocked → next step is Fix missing fields
When you do this, the user stops thinking and starts moving. That's the whole magic.
4. Add a confirmation moment
In games, the objective changes when you complete it. In business apps, the UI often stays the same even after you do the thing — which is why users click twice, or assume it failed.
After the primary action, update the next step. Show "Completed" and move the quest marker to the new objective. This turns the app into a journey instead of a toolbox.
A Quick Test for Your Own App
Open your screen and ask a new user: What would you click first?
If they hesitate, you don't need more documentation. You need a quest marker.
Give them one next step. Let the rest be optional.
Because clarity is not limiting. It's the thing that makes people finish.
Want more like this?
I write about play, leadership, Women in Tech, and building things that matter. More posts below — or reach out if you want to talk.