Research observation, night one: a crew member opens CrewPal, navigates to her schedule, takes a screenshot, closes the app, opens WhatsApp, sends the screenshot to the crew WhatsApp group.
Me: 'Why did you do that?'
Her: 'Because this is faster than asking people to open the app themselves.'
I asked the next 8 crew members I observed. All of them did the same thing. Different WhatsApp groups. Same workaround.
Nobody on the product team knew this was happening. Analytics showed users opening the schedule screen regularly — they had no visibility into what happened next. The screenshot workflow was invisible to the data.
This is the core problem with analytics-only research: it tells you what users do in the app. It doesn't tell you what they do because of the app, or instead of the app.
The fix in the redesign: a native 'Share schedule' button that formatted and shared a clean text version of the duty assignments. WhatsApp workaround: unnecessary. More importantly: the pattern that revealed the workaround led to three other insights about the crew's actual workflow that we'd never have found in quantitative data.
The Takeaway
Workarounds are the most honest user feedback you'll ever get. They mean 'your product doesn't solve this well enough, so I built my own solution'. Find the workarounds.