This article will take around 2m20s to read according to Read-o-Meter.
The funny thing about leading a digital agency when you’re not from a tech background is the role you get to play every day. One client recently described me as an interpreter – someone who listens to what clients actually want and asks the right questions every time. It’s often in the early exchanges that we clear up any inconsistencies and misunderstandings, which saves time, money and heartache later on.
Let me give you an example. If a client says “We need a microsite delivering in two weeks’ time”, I know that the techs will start thinking “How can we do it” and “Which CMS are we going to use” and lots of other valid, practical steps. Whereas, I’d tend to ask “What’s the driver behind the two week deadline?” and “What are you trying to achieve with this microsite?” and lots of other “Is this the best solution that Burfield can offer” types of questions.
I’m interested because at the heart of our business is a desire to provide the quality of work you’d expect from a mega agency at the prices you’d expect from a South West agency. And we can only do that if we don’t over engineer the process.
Which brings me to the point of this blog post – how I came to fall in love with Trello.
I’ve used Basecamp.
I’ve used Teamwork PM.
I’ve used Work[etc].
Then I’ve used MS Project.
Finally, somebody convinced me to use Trello.
It’s not some overwrought piece of technology that has 2,000 bells and whistles that you’ll never use, designed by geeks for use by geeks.
No, Trello is – at its heart – a whiteboard. Which is probably why it appeals to the non-geek in me so much. I love a whiteboard.
I’d fallen out of love with some many project management tools over the years that I was not keen to try a new one. But Trello digitally replaces that whiteboard which is now gathering dust in the back office.
It’s flexible enough to store visuals and to do lists, have deadlines and alerts, and yet not so complex as to lose site of actually getting on with the tasks in hand. All very refreshing and a bit like working with Burfield, really.
Can we use MS Project? Yes. Do we do so regularly? Only when the client wants us to or the size of the project calls for it. In our experience, it’s much better to use an appropriate technology and keep our costs down as a result of the time we save. That’s Burfield in a nutshell.
Let me know if you’d like to hear more about working with Burfield and our ‘beyond partnership’ approach.