User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
I'm a product designer, UX/UI (whatever else you wanna call it).
I work closely with devs during the pre-deployment phases. Because of the speed at which we operate, and the complexity of the product flow permutations, there are lots of edge cases to catch during development. 70%-ish of the time, we (design/dev) catch these missed flows or logic ad hoc.
Does anyone have a workflow that works and if so, share? Much thanks.
I don't think there is a workflow that is guaranteed to work, because it will depend on the product, people and process (and to an extent the tools) used as to what would be the optimal workflow when it comes to efficiency.
So I would suggest you try to weigh up the product (i.e. what is being delivered), people (what are they comfortable with in terms of communication and processes) and process (sign-off and handover procedures and tools) to see where the bottlenecks and confusions lie before making the decision on a workflow.
Different teams require slightly different approaches, but lean and agile are philosophies and not prescribed methods of doing work, and there is room to adjust so that it can be tailored to specific team needs.
I think it's partially inherent to working 'lean'. You design the product flow tension-based & when you catch these missed flows, you fix it ad hoc / improve it.
I think, over time, your accumulated experience will guide you towards a more complete handoff, with all flows, error states, etc. included. Maybe a solution would be to start working on a handoff-checklist, in which you include all your learnings over time during handoffs of different types of projects / pages / flows.
