Eryk Orłowski · hretheumhretheum.com/questions/user-research
Question P4 of 8
All questions4How do they work with user research?
At argonauts (2003–2005), launched and ran a usability research lab, where around 2004 prototypes of online banking for Volkswagen Bank Direct were tested. The research made it possible to remove design problems early and make another iteration of the prototype. At iPKO biznes, alone designed, documented and researched the interface of transactional banking for businesses, in an 18-month project. At ING, introduced user research to an organization that minimizes risk by default, and at Sportradar the team researched solutions with traders.source sources: wr-07, vw-04, vw-01, vw-03, wp-03, ing-16, sr-15
Evidence
Around 2004 I ran lab studies of prototypes of a transactional e-banking interface for Volkswagen Bank Direct.”
I ran the studies as IDIs following typical usage scenarios, with sessions observed in the lab and recorded.”
I was responsible for research, interaction design and prototype validation.”
"Synthetic users", the tools that promise to replace research with simulated people. […]"Synthetic users", the tools that promise to replace research with simulated people. A model can tell you what an average user would plausibly say, and that's exactly the problem. Research is worth doing for the things you didn't expect: the child who doesn't know what a pear is, the trader who watches eight screens at once. A simulation gives you back your own assumptions in a confident voice. At most it's useful for rehearsing an interview guide before you talk to real people.”
The studies made it possible to find and fix design problems early and to run a further iteration of the prototype.”
At iPKO biznes I led the complete process of designing, documenting and researching the transactional banking interface for businesses, in a project lasting 18 months.”
I brought user research into the process of an organisation that minimises risk by default.”
At argonauts, from 12.2003 to 10.2005, I was a project manager and ran the usability lab.”
I set up a usability lab in an advertising agency.”
In August 2017, at the Innovation Bootcamp at ING, I worked in a cross-functional team of 5 people on self-service permissions management.”
We rewrote the labels as questions users ask themselves.”
In ING Allow Me we designed the full customer journey for the permission management processes.”
We ran innovation projects in the PACE process, blending design thinking, agile and lean startup.”
I extended the team's craft through research with traders, workshops, mentoring, changing the scope of tasks and taking part in discovery.”
At Sportradar customer journey mapping was a standard tool in every project.”
At Kokos.pl I persuaded the client to reorder the tasks around the user's goals: getting a loan or investing.”
At Morizon the loan application was led by an adviser in the form of a conversation in natural language.”
I ran qualitative research for PEKAO S.A., AVIVA, Provident, Plus GSM, T-Mobile and Orange.”
Cognitive Mirror's measurement properties are laid out on the COSMIN scheme, in a table generated from the measurement data.”
The one I'm proudest of isn't the biggest. […]The one I'm proudest of isn't the biggest. I ran the discovery phase for an e-learning platform that ORPEG, the centre for Polish education abroad, was building for its remote schooling programme: lessons for children of Polish citizens who live abroad for a while. My job was to identify and document the requirements, so I spent a lot of time listening to the everyday problems of teaching these children. Some of those stories stayed with me. One child didn't know what a pear was. Another had never heard of Santa Claus, for cultural reasons. And all of them had to work through the Polish national curriculum. That changes how you think about content, language and what you can assume a user already knows. I like doing work that matters to someone, and this one did.”
By agreeing what "good enough" means before the work even starts. […]By agreeing what "good enough" means before the work even starts. It's the same rule I use in my R&D lab, where a decision only counts if the success criterion was set before the measurement. Otherwise everyone moves the bar to wherever the design happens to land. In practice, a design is ready when it solves the problem we confirmed in testing and has no critical issues. Everything else becomes iteration after launch. And past a certain point, more polishing teaches us less than real users will in the first week, so holding the release back stops being care and becomes delay.”
Regularly, and I'd worry about any designer who says otherwise. […]Regularly, and I'd worry about any designer who says otherwise. The point is to find out early, while being wrong is still cheap. That's been my habit since the usability lab I ran in the early 2000s, where we tested e-banking prototypes for Volkswagen Bank Direct, and it hasn't changed since: at ING we validated prototypes with users before building, and at Sportradar the designers tested their ideas with the traders who would use them. I also agree up front what would count as success, so a wrong decision shows up as a result that misses the bar, not as an argument after launch. Most of my wrong calls died in a prototype, and that's exactly where I want them to die.”
Limit
The concept did not go into production in this form; ING implemented a permissions management module developed and imposed globally.”
E-mail: [email protected] (kt-01) · LinkedIn: linkedin.com/in/eofek (kt-02)