I always make it a point to educate myself when I have nothing to do. I've been doing sketching exercises with workbooks and reading up on advises from expert designers all over the globe. And feasting my eyes on pictures of Damian Lewis on the internet (LOL - what is work without some play mixed in right?).
Anyway, this Sunday I decided to check out slide presentations, having just finished teaching Microsoft Office 2007 on Word, Excel and Powerpoint to Agricultural Extension Workers last Friday. I found this slide presentation about project processes and there was this part that really, really, REALLY makes me wish I worked for them. The article is found here: Simon Collison
The Creative Team
I wholly believe that our processes should be inclusive, and that all members of a team can influence all aspects of the design and build of a product.
One of my most stringent rules as a creative director is that anyone, anywhere in the team can feel free to add value. They all have brains and common sense. Anyone, at any stage can contribute an idea, pose a question, throw a spanner in the works, piss on our collective chips, or get so excited that they piss on themselves.
I’m certainly no fan of the production line approach. Project manager passes request to developer; developer passes framework to designer; designer colours it in etc. Everyone working within a niche skillset on a need-to-know basis. No. I favour, as many do, an open platform, where all team members are informed and involved from day one. If we are all aware of the project’s goals and aims, we can all contribute. Findings throughout should be made transparent and shared with the whole team; and I would not exclude any client-side politics, budgets or contractual details from that either.
Forgive the role-pigeonholing here for a second. A developer can challenge a designer about a chunk of CSS or use of type. A designer can challenge a developer. Anyone can do this so long as they have a deep understanding of the process being undertaken, pairing that with the backbone of the project and their own experience.
Whilst some will always remain specialists, an individual’s general skillset or knowledge-base increases dramatically through collaborative design. This also assists individuals to achieve their own goals. For instance, even the quietest designer can find themselves doing a pitch or chasing a potential client if they wish. It promotes a Musketeers all-for-one ethic that puts a collaborative, thriving team at the heart of everything.I would like to work in a place where my opinion will be valued, even if it's a wrong one. I do think not all of my opinions will be wrong. This would be nice. No. This would be great. My friend from Haribon says this is the process they adapt when they plan. When will they ever adapt this strategy to organizations like mine? I promise myself, if I ever get the chance to lead a team, this will be my process approach - everyone in my creative team will have a voice - and their voice will be valued.

















