I’m about to follow the DOJO workshop by Larissa Rosochanski https://www.ministryoftesting.com/dojo/lessons/designing-test-cases-focused-on-the-user-experience-with-larissa-rosochansky
Basically I’m trying to work out the real kink in process were UI moves between idea->wireframes-> code->final approved screens. The pain I have is that people not only use different language when saying user experience , but completely exclude performance, quality and only talks “workflow”. Loads of places I have worked, it is just loads of pictures given to the developers. Pictures which get hard to keep updated, are less useful to the tester who has to verify them, and also don’t capture “implicit” design experiences or rules like
- do all buttons start out disabled when a form is empty, or
- do all fields have hint-bubbles.
Things, that are all rather tedious to show in wireframes.
As someone who has stuck my head above the parapet on the whole UI experience and the accessibility thing, I’m looking for more hints on how to communicate to stakeholders. Waiting until all the screens have been coded up, before we decide, no this one does not quite look right, is a pretty terrible idea. Mainly because a developer who last worked on a piece a month or so ago needs to go back, but also that testing gets impacted. Developers are often focused only on the component they are working on, so consistency will often suffer. Testers can get builds long before stakeholders get to see the resulting screens, so are well placed to spot issues early, but without any good communication skills, where do I start?