The UX Kanban

In some organizations, the user experience (UX) team is seen as a problem child. It has merits, brilliant minds and capable hands. But, it has its own ways of working.

In a typical services company, the UX team works in a horizontal mode – providing consultancy to every business unit. In product companies, the UX team may be divided according to the product portfolios. Regardless of size and nature of business, one thing is common that managing the UX team takes a toll on the CxOs of the organization. The pressures of billability, team members’ utilization and investment of tools are the commonplace problems. Of course, there is no panacea (the cure-all medicine) to these problems.

Many tools, methodologies have been attempted to “civilize” the team. One of them is Kanban.

Kanban literally means ‘signpost’, a just-in-time production system designed by Taiichi Ohno at Toyota. Kanban is a system to control the logistical chain from a production point of view, and is not an inventory control system.

In simple words, Kanban means to produce only when there is a demand. It helps organizations to be leaner, productive and have faster turnarounds. There is ample material available on the net to read and watch videos on Kanban system.

I took the Kanban approach and applied to the typical UX team scenarios. The first sketch shows a Kanban dashboard of projects in UX portfolio. It has visual cues and legends that helps the UX managers / leads to focus on what is important from delivery and sales point-of-view.

The overall view

The overall view

The second sketch depicts the Kanban system from the team and tools perspective – how many designers we need to hire, what tools we need to purchase.

The team and tools view

The team and tools view

The third sketch shows the Kanban cards the UX team members would receive as work queues. They will get a precise description of what needs to be delivered, how and when.

The UX delivery view

The UX delivery view

If you tie these three sketches together, it could lead you to a system of UX team management – a web tool or an iPad app (if you visualize). Who does not want some structure to the maverick team :)?

Those cricketing ideas…..

At the moment, India is the ICC Cricket World Cup Champion defending its title in the 2015 edition. As I write, India has started off the defense campaign by a win over Pakistan. Online media, social networks and messengers are loaded with anecdotes, videos, game analysis, predictions and player trivia.

Indians are passionate about two things – Cricket and Bollywood. I have grown up on other sports in India too – tennis and football (soccer). But when it comes to the World Cup of cricket, other sports take a backseat. This will be the first time in 20 years, Indian cricket team will be playing without Sachin Tendulkar. He had been a regular figure in last 5 world cups, garnering maximum accolades to the team.

Over the years, the data visualization aspect of the game has improved. Nowadays, a cricket match analysis is replete with infographics and tools like wagon wheel, projection deliveries, momentum, hawk-eye, snickometer, etc.

There are multiple cameras that capture the action on the pitch and ground through different angles and get the granular data. From the sports data scientists’ point of view, the golden age of sports data (or rather cricketing data) is about to come. We now hear about the video analytics tools deployed by respective cricket teams to gauge the weakness and strengths of players.

Four years ago, I worked on two concepts related to cricket. One is the cricket scorecard and second is an iPad application.

I wanted to change the way cricket scorecards were presented to the users on television and websites. I wanted to give a new feel to it. This was my humble creation as I was just entering into the world of infographics design. Now, I look back and wonder at these designs and think they can be designed better :).

Scorecard - 1

Scorecard – 1

Scorecard - 2

Scorecard – 2

Scorecard - 3

Scorecard – 3

The second concept I did was a Twitter based cricket application called “IndiTalk!”. The premise is simple – talk, talk and talk about cricket. iPad was just launched, back then. The app UI bears good resemblance to the first generation iPad apps. This app, if designed today will probably have a different character to it.

IndiTalk_1

IndiTalk_1

IndiTalk_2

IndiTalk_2

IndiTalk_3

IndiTalk_3