When I walk someone through an early prototype, someone almost always asks if the screen can work differently. Could this step come first? Could this field be hidden? What if an appointment needs to be rescheduled on the fly?

My immediate instinct used to be simple: change it right then and there. Opening the settings or tweaking the layout live in the room feels like the ultimate demonstration of agility. It shows that the setup is flexible and that I am listening.

Over time, I learned that live editing almost always derails the room.

The moment I switch into build mode during a presentation, the tone changes. People stop thinking about their daily workflow and start watching my hands. If a page refresh takes five seconds, or if a minor typo causes a validation error, the room suddenly becomes an impromptu troubleshooting session. Even if the fix takes only a minute, the momentum is gone.

A prototype is supposed to help people evaluate an idea, not watch someone configure software.

Now, when someone suggests a change during a walkthrough, I stop and write it down. I ask what prompted the idea and what other steps depend on it. That conversation is always more valuable than opening an admin panel mid-meeting.

I tell them I will think through the edge cases and come back with a revised version. That keeps the focus on their actual process. It also gives me the time to test the change quietly, without fifteen people staring at a loading spinner.