Some time ago I described the process on a project as trying to ‘form Voltron’. My colleagues shook their heads, not understanding what I meant. They googled it, and still didn’t have a clue. Voltron is an anime that ran before I was even born, but I spent a lot of my growing years watching it with delight, I thought the whole world watched it. Voltron (Defender of the Universe ) is the name of a giant robot which is formed by robot lions piloted by space explorers.
What Are Voltron projects ?
There are two main types of projects I have worked on. One is the ‘Big Bang’ project (built from scratch) and the second is, the ‘Voltron’ project which uses existing applications, components or systems to build something new. The Voltron projects can be built entirely on existing ‘Live’ components and they can also have a new component brought into the process. All of these have their challenges, however the Voltron project which looks like the easier route can be the trickiest.
How do you make Voltron work?
Working in a large organisation these projects are fairly common, as with any project these should not be missing.
1. A clear goal/vision – Voltron was never formed without a ‘Robeast’ it had to defeat. The goal and vision of your project must be visible to all involved parties. Everyone should be able to own that vision and understand it. Even if you inherit a project, it is your responsibility as a UX-er to get into it. Ask questions, talk to people, research, own the goal.
2. Strong leadership – The robot lions had a clear leader who gave direction for any of their undertakings. The leader should inspire people to work on the project despite the difficulties it seems to introduce , it is about blending the right skills with the right attitude. . As a UX-er it is valuable to own the product. When in doubt, take responsibility.
3. Communication – This kind of project requires a high level of collaboration. It is easy to assume that stakeholders already know what’s going on, but usually these people have many other projects they are looking after (esp in the case of inheritance). Go after them, ask questions. Bear in mind that a change in one of the components you need might affect other products which use them. As a UX-er you have to have your eyes wide open. Sometimes there will be compromises, but everyone has to be on the same page.
These are just a few things I’ve learnt and experienced but the UX-er’s work is never done.