"To define is to limit" (Oscar Wilde)
Tuesday, April 28, 2009 | Author: Jo Goodwin
Ok, so I'm sure Wilde wouldn't be over joyed at his work being used in the context of web development, but he had a point and it applies to the wireframe process. Yes, wireframes can limit creativity but they also limit scope creep. So should we use them and what other solutions are there?

I use wireframes a lot and find them pretty useful for defining functionality for developers, keeping a project in scope and helping clients to understand functionality. Plus they are good for understanding user interaction before a build.

The problem with them is that not only do they limit creativity/innovation in house but clients also can find it difficult to think of wireframes as just defining functional spec rather than design, making it hard for them to except new layouts/designs. Another problem is that often the wireframing process can mean that an Information Architect can end up defining a site's functionality with little involvement from the rest of the team - who do after all hold a lot of useful information.

So what are the solutions to these problems? One idea is to abandon wireframes and give clients, designers and developers a written spec with a written visual guide e.g. content area should take 50% of the page. Although this is it can make it easy to miss functionality out of a spec. A wireframe can be used as a "thinking device", before writing out the tech spec to help solve this problem, but functionality can still be easy to miss in a build if a spec is simply written down. Wireframe abandonment perhaps isn't the perfect solution for the client either - wireframes help them to visualise functions and ideas too. It can also help the client get stakeholder buy in for sign off.

So if wireframe abandonment isn't the perfect solution, we need another solution. Maybe it's the approach we take to wireframes that needs to be reviewed. How detailed should they be? Just how much do we pin down functionality? Who should be involved? Who shouldn't be involved? When should they be involved? How are wireframes presented to the client? How much of the site is wireframed?

It would be a nice have "one solution fits all" ideal. That's not going to happen, so it would be good to have a solution that works most of the time. I still don't know what that is - I would like to know if there are any other good alternatives to wireframes being used out there though. I will investigate and experiment!

If you haven't come across wireframes before read this: "Introduction to wireframes" and for further reading go to Wireframes Magazine.
Digital Innovation
Tuesday, January 13, 2009 | Author: Jo Goodwin
As Digital Project Manager, you are often dealing with challenging situations. Clients expect the moon on a stick, with neon flashing lights for 3p, when none of your developers have much experience of the moon, sticks or light fittings.

New cutting edge projects are likely to need research and development time, which often impacts on deadlines and of course budget. Thus new technologies can put the fear of god into any Project Manager, creating negative connotations with innovation. Innovation that is essential to keep up with, if not lead current web trends.

This is just one reason why putting budget aside for new technology research/development is so important. I think it's a good idea to have a budget set aside for this within a controlled environment, preferably not involving client deadlines. Also it keeps your "creative types" and developers, happy and motivated.

Head London seem to have fully taken innovation on board with their Head Labs project. Best of all it's making them money too as clients have seen what they are doing and want a piece of the pie. To be honest you are better off letting Head telling you about this first hand at www.headlondon.com/pages/head-labs. They have a fab logo too.
, | comments (0) | + Share
Half way there
Monday, January 12, 2009 | Author: Jo Goodwin
Ok, I've finally logged back into my account after some time away. Since I last wrote, lots has happened! I'm well on my way to getting into Digital Marketing.

For nearly a year, I have worked as a Digital Project Manager. This has been nothing less than a rollercoaster of emotion! Never the less it has been interesting, fun, revived my interest in the web and given me the chance to work with some huge household names.

At the agency I've been employed at the PM (Project Management) role includes both managing time/budget and writing wireframes/IA - quite unusual, I think?

I've now decided that my heart is in getting a website right for the client and meeting their customer needs rather then just getting it out on time /budget. In essence I'm not a pure Project Manager - in fact my heart is in taking offline marketing principles to the web and making them work online. Therefore I want to concentrate on being an expert in this field.

What I'm slowly getting to is, I've change role again. In one months time I'll be a Strategic Consultant for a NMA top 100, London based agency.

In my new job, I'll be working more closely with clients to make websites that really do combine marketing knowledge, audience needs and business needs to make websites that work. The company work with focus groups, truly investigate audiences and user journeys. It's all stuff that you dream an agency will do when you are sat in lectures at University.

I feel pretty bad for leaving my current company, after all they gave me the chance to cut my teeth. At the end of the day, the reason I love the web is the speed at which it moves on and I need to be moving with it. I feel, I have made a at least a small mark in my current company. A senior PM at the company thanked me for inspiring her about the web again text me this "I've been stagnating for years with my career as a PM and this is the first time I've been motivated to raise my game & learn latest about the industry". That makes me feel proud.

I really hope I have made the right decision. I love working where I do now but I need to strive to take my career in the direction I want it to go in. Reading my first post written on here just under a year ago, I'm fairly pleased with my process so far - let's hope I've made the right move and I can continue to develop my skills.

My New Years Resolution - to write more on this blog!
, | comments (0) | + Share