{{…}} feature is one of the many new features that Transifex is planning to launch as part of a larger roadmap ahead.

The core complexity of the feature itself, the need of multiple planning, cross-team collaboration, definition of problem and user drove us to rethink and re-evaluate our internal process with the purpose to work and deliver in a more efficient and faster way.

The circular approach that we followed was consisted of 6 major chapters that we defined as:

Learn, Research, Map, Prototype, Show Evaluate

The knowledge that we gained by practicing these was invaluable and will help all departments and our design team perform faster and more accurately in the future.

0. Learn

Project File Structure — From theory to practice

In this phase we are trying to learn more about design principles, studies and processes, see what other design teams and organisations are doing, if we can try something new along the way.

During this phase we learned more about the design thinking processes like Design Sprint from Google and also get inspired by others that aligned perfectly with our mentality and culture like Show your work from Atlassian — I was biased into applying this due to my old print-design history.

Where to get that knowledge?

1. Research

Information Architecture & Whiteboard User Flows

During research we discover the problem and the user. We get inspired by similar solution or well-defined best practices. We talk internally about specs, customers and end goals.

We use the whiteboard a lot to draft the information architecture with the purpose to extract a core path that the user persona will follow in order to solve his/her problem or perform an action.

What is expected to gather and/or produce at this phase:

  • Inspiration resources
  • Specs & Docs
  • Whiteboard wireframes
  • User Personas
  • User Journeys

2. Map

Storyboards, Design Sprint, Lo-fi Mockups

During this phase we craft lo-fi mockups, rough hand-drawn sketches or mid-fidelity prototypes and ask for feedback. Comments and concerns are documented, discussed and we iterate on the initial prototypes fast and with more data in our arsenal.

What is expected to gather and/or produce at this phase:

  • Whiteboard [iA, user flows]
  • User Journeys
  • Affinity diagrams

3. Prototype

In the prototype we dive deep into the stories of users with storyboard exercises where members of the design team have to draw a quick storyboard in 15-min and on specific journeys.

Also in this phase we keep iterating on low-fi or hi-fi screens that were produced. We define some clear user flows that we transform into clickable prototypes. Flow charts are extremely useful as well to visualise the user paths and out possible break points in the experience.

What is expected to gather and/or produce at this phase:

  • Storyboards
  • Flow charts
  • Designs & Mockups

4. Show

The Wall — Design Show

The show phase is where we present to all stakeholders and gather input for our initial assumptions. We decided to use various methods to show our progress.

We have presented screens and userflows in The Wall were we explained our hypotheses and solutions with all members, and invited everyone at any time to see the screens and write his/her comments and feedback with post-it notes. 
Also we use InVision a lot to produce online clickable prototypes which turn out to be extremely useful for instant feedback & continuous iterations..

What is expected to gather and/or produce at this phase:

  • The Wall
  • Interactive Prototypes
  • Presentations
  • Videos

5. Evaluate

Post-it comments on “The Wall” design show

We continue in gathering feedback through a beta program with real users and we initiate a user testing process — which this alone is a major chapter in our process.

On top of that every design has a KPI structure and is mapped to Analytic tools where we extract helpful data that validate or not our assumptions.

What is expected to gather and/or produce at this phase:

  • Feedback Docs
  • User Testing sessions
  • Analytics Data
User Testing Plan
User Testing Session

This is Transifex approach to Design process. We keep questioning our process, defining and validating the correct path and test results.

And because the chance is pretty high that unexpected things will happen or processes might not work in the near future we don’t worry — it’s part just part of the whole process.

So that is the design process or the creative process. Start with a problem, forget the problem, the problem reveals itself or the solution reveals itself and then you re-evaluate it. This is what you are doing all the time. 
Paul Rand

Source link—-138adf9c44c—4


Please enter your comment!
Please enter your name here