Wednesday, February 28, 2007

Project Review Board

We have a Project Review Board who are our conscience and our guides. They also make the really difficult decisions that might require funding or a strategic change of direction.

This week they will be reviewing our status.

It's a difficult time when things can appear worse than they actually are. The project scope is still hazy which is reasonable given that we are still collecting business requirements, but it means that when time and money are estimated it makes sense to assume the worst. This means that cost and time estimates can look a little frightening. This is OK providing we understand that the estimates are 'worst case scenario' and things will improve.

It's also a difficult time because everyone is enthusiastic about what is possible. The air is full of ideas and creative thought. If we did everything on everybody's wish list we'd still be working on the project in 2020. But we don't want to disregard all of these things out of hand just because they might cost a bit more, or take a bit more time.

This is a time to collect all of the good stuff in preparation for the analysis that determines the what's in and what's out. That's where some of the really tough decisions will have to be made.

Can you bear the excitement?

We've had a flurry of late submissions to the competition to name the new NWP tool.

If you want to submit a name I won't be consolidating and shortlisting until Monday or Tuesday of next week so you could probably squeeze a few extra submissions in.

Suggestions will be posted here next week. Watch this space.

Wednesday, February 21, 2007

Find out more

There's going to be a nice little get together of the Marketing Managers in March. I think someone called Mickey is invited. Anyway this is a great opportunity for us to communicate our thoughts on the new system, which will definitely not be called Firefly. :)

Thursday, February 15, 2007

The future is here

A European Communications strategy meeting has helped us with the direction for the new site.

For those of you who haven't seen the Book of Surprises - you need to take five minutes to absorb it.

Google

I met with Google and we had a lot to talk about, mainly questions, and mainly questions asked by me.

There was an interesting discussion about a Saturn promotion using Google Maps.

We discussed a Google search product that could be integrated into the new website to improve in site search. This is one of a few alternatives to improve search functionality.

Consumer Generated Content was mentioned because we want to know how other companies moderate this material.

There is Google Analytics, Google Base, Google Video, YouTube etc.

Additionally Google have conducted research among car buyers. No real revelations but research is always interesting.

Google really are taking over the world and this blog is only available to you because of the mighty Google.

Features and Specs

One thing that research says again and again is that Features &Specs is an area that we need to improve. We have made a half hearted attempt last year and this but frankly it has barely moved the needle and, it simply isn't good enough.

I think we would be failing abysmally if we launched with carry over functionality here.

Fortunately, we don't have to. Burrows have suggested a data warehouse solution that could feed the new Content Management Tool (whatever it is called). The timing is compatible and the budget is something I'll endevour to find.

It doesn't matter what the project is, there's never enough time or money. One thing I try to keep in mind is something someone once said "Lack of money has never got in the way of a good idea."

Configurator

We had a couple of meetings on Configurator. The first challenge was to understand how Configurator works. There are a scary number of systems involved in producing the class leading toy that we perhaps take for granted.

We discovered that we can consider playing around with the tool and integrating the application on more than just a surface level. We're still not sure whether that's what we want to do but it is important for us to understand the possibilities.

It's also worth remembering that what we have is liked by those who use it and I am very aware of the phrase "If it ain't broke, don't fix it". However there could be a stunning and irresistable solution that makes it all worthwhile - it's too early to say.

We also determined which bits of the Configurator puzzle can be available for change, and which cannot.

New name

We need a new name.

Firefly is history, or will be history once we've launched our brave new world.

The last newsletter asks people for suggestions and we've had a few. Some are better than others.

It's a competition and the best name, i.e. the name that is chosen, will win a prize.

Some contestants are keeping their powder dry. Brendan, at the last count, had 36 suggestions. That's either greedy or very enthusiastic.

One thing I do know - the winning suggestion will not be Firefly.

Several kick off meetings

The first thing we did was to meet with the Fatwire team. It was a revelation.

Fatwire is the software that will drive our new websites.

Having worked with Firefly for a while I have become used to it's restrictions. Naturally most of the questions we were firing at the Fatwire team related to limitations we experience with the current system. I don't think there was anything we wanted to be able to do that didn't seem possible in the new system. If there's anything you would have asked the Fatwire team, leave a comment and we'll ask for you.

The next thing we did was have a kick off meeting to introduce the key content and application stakeholders to one another. Included in this meeting was a 'quick and dirty' user experience thought starter. This caused great debate and we had to stop ourselves from designing the answer, before we knew what the question was. The biggest applications impacted by this meeting were Configurator and Features and Specs and there were follow up meetings arranged to dig into the detail of these applications.

Then we needed an IT kick off meeting. This was an attempt to nail down more of the detail of what will be done, by whom. It's always tricky to do this before the scope of the project has been identified and before completion of the initiation phase things are still a little hazy. One of the key outcomes of this meeting was the need to mesh the IT and Wunderman work plans because as they were presented in the kick off meeting, there was a huge disconnect.

Somewhere in the midst of all of these meetings we had funding sign off - sighs of relief all round.