Workflow Prototyping

Earlier this month, one of Brilliant Basic’s talented Project Manager’s Sergey Soloviov dipped into the General Assembly for a quick chat to a class of aspiring UX designers with a focus on “How to Prototype your workflow”.

The event was held at GA’s headquarters in Farringdon during an immersive UX Design course’s lunch hour. The talk revolved around what it takes to transform the organisation and move from one way of working to the other. There are two methods of working that Sergey explored during his talk — Waterfall and Agile. Sergey advised that pushing yourself beyond your comfort zone is “where the magic happens”. He encouraged the class to exercise new processes of workflow in order to optimise the success of a company’s future.

Sergey preparing his presentation for the eager UX class

Going back to basics — what are both waterfall and agile methodology?

Waterfall methodology is a sequential design process, where each of the processes must be completed before moving onto the next stage a given project, whereas the Agile method follows an incremental approach. Sergey explored the pros and cons of each method and delved into how each method affects clients and internal department relationships.

Laura, the UX Design course leader at GA introducing Sergey to the students

Organisations current workflow

Sergey began his talk by explaining that few organisations use pure method on their projects. This is not down to the lack of trying, but rather due to tailoring the approach to their own reality. Many external and internal factors influence their team strengths and weaknesses, as well as reasons beyond their direct control, such as client expectations. It is because of those reasons that agencies find themselves having to design and evolve their own unique adaptations of processes instead of switching to a new framework overnight.

As we all know any design process carries a risk of getting it wrong, so the trick is to find ways of reducing the risk. Sergey believes the key to success is changing one thing at a time instead of pulling everyone into a new world and watching your team fall apart under immense pressure.

Examples include:

- Build a pattern library for an existing web-app before getting into designing patterns in the first place

- Run user testing sessions within a waterfall project before you rely on user testing in your design process

- Build an interactive prototype while creating traditional page mock-ups before designing in the browser

Running such experiments within otherwise comfortable and familiar environment helps relieve pressure, establish routines and builds synergy across disciplines to create a competitive advantage.

Sergey answering stimulating questions from the UX Design course

The class of aspiring UX Designers presented Sergey with a vast amount of challenging and stimulating questions about his personal experience, which companies are doing it best, and how these methods influence UX specifically.

Brilliant Basics

Trends, insights and opinions from our team of dreamers and doers.

    Hayley Smeulders

    Written by

    Digital Designer

    Brilliant Basics

    Trends, insights and opinions from our team of dreamers and doers.

    Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
    Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
    Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade