When users try to "hack" your flow: what frustration reveals about motivation in UX

About the Talk

Every product team has watched it happen: users find a path through the product that the team never designed. Copy-paste workarounds, weird filter combinations, the same field reused for three different things, the spreadsheet exported just to be re-imported. Designers call it misuse. Eva Bandke argues it is the most honest piece of user research you will ever get.

Her core idea: when users "hack" your flow, they are not failing your UX. They are revealing the gap between the motivation you assumed and the one they actually have. Frustration is the signal, the workaround is the data, and the redesign opportunity is the difference between the two.

Key topics covered:

• ●Frustration as a research instrument: why complaints, abandonment, and weird shortcuts are richer signals than satisfaction surveys, and how to spot them in session recordings, support tickets, and product analytics.
• ●The motivation behind the hack: a framework for moving from "what did the user do" to "what were they actually trying to achieve", and how often it is not what the brief said.
• ●Intrinsic vs. extrinsic motivation in product flows: when users push back on your flow because the reward structure does not match their internal drivers, and what to change first.
• ●Designing for the real job: turning observed hacks into product decisions. How to redesign a flow so the user's natural path becomes the happy path, instead of fighting it.
• ●When not to "fix" the hack: cases where the workaround is healthier than the flow you would design instead, and how to recognize them.