Channel 4 ( www.channel4.com ) is one of the UK’s leading broadcast channels, and its youth-oriented E4 service, watched by over 7m 16-34s every month, is one of the strongest brands among this audience group. Always looking ahead, in mid-2007 executives decided to create a website – not just a website, but a web community – to engage and excite their broadcast audience. Creating an interactive medium fed into broader business objectives of building loyalty and delivering new paths for revenue growth.
E4 had already tested their concept using experiments with social networking sites. A MySpace area for the show “Skins” had proved extremely popular, and executives saw they could provide unique and relevant content to their audience - episode trailers, program contests and more - without competing with video streaming sites such as YouTube or social areas such as Facebook. And they could create new revenue streams in the process.
Channel 4 gave the project a green light but with strict directives to ensure financial success. The project had to achieve an aggressive timetable to support the new season marketing launch of one of E4’s most popular programs – which meant the site would have to be online in just six months. The short launch time-frame was also driven by the tight payback period for the project – the site had to recover its costs within a year of launch - by the end of 2008. The project faced technical as well as financial and timing hurdles. Storage and server capacity was limited and would be shared with other Channel 4 sites. And yet, as a community interaction site, performance had to be responsive and scalable. Success depended on it being easy and fun for users - lots of users. Performance and scalability were great concerns. And the site needed complex integration with ten different external system interfaces as well, most notably the content management system.
With a stringent schedule and budget as well as the technical hurdles, an experienced development partner was essential. E4 knew that the decision was as important to overall success as the website conception itself.
ThoughtWorks headed a combined project team that included third party experts on site design, and collaborated closely with E4 every step of the way. The E4 team was overflowing with ideas and enthusiasm for what they wanted to achieve during the kick-off. ThoughtWorks’ streamlined inception process helped them focus on exactly what was required for the initial release which would deliver value to the site's prospective users and the business. After Inception, the team, up to 40 people strong, used Open Source libraries to supplement the custom parts of the Java build, keeping within budget while maximizing available features. Technical experts implemented what is called a RESTful architecture. This leveraged the massive investment in the public internet infrastructure, relying on the Internet Cache Protocol to enable load handling with minimal hardware.
Innovative means of addressing the technical challenges turned out to provide side benefits. For example, integration with the content management system was handled by creating a Query Module, a kind of URL domain specific language, which allows editors to build pages by simply specifying URLs including the required page elements. This makes for a site that can flex around the needs of the editors and the individual programmes from minute to minute. It was imperative that the site be ultimately up–to-date as it is so closely connected with regular TV shows and the user expectation is for an integrated experience between TV and web. In answer to this the specific page is created on the fly - meaning it is always up-to-date. Many different views can be created of the same content, without increasing storage.
Channel 4 were also quick to invest in innovative ways to use the new site infrastructure to integrate the on and offline experience, making headlines along the way. The microsite for E4.com /deadset had a hugely effective viral campaign and won a BAFTA for Interactive Creative Contribution in 2009, which “wouldn't have been possible without the framework ThoughtWorks created.” Paul Edwards, Programme Manager, E4.
Technical brilliance would have been moot if the site were to end up in the headlines for the wrong reason - hackers. With security more and more at issue, Channel 4 commissioned a third party specialist to test the new site. He was challenged by Channel 4’s in-house expert to break the site, but was unsuccessful.
Martyn Lewis - Channel 4 IT security and disaster recovery.
The site went live on schedule, at the end of 2007, instantly becoming a community space for E4 programme fans. In addition to unique E4 content, the site enables user-generated content, commenting and voting – focusing on users who want to participate in the site rather than just consume it. This approach draws the passive visitor into active community involvement, and so regular visits. Automated moderation processes make it all manageable for the client.
The decision to use a RESTful architecture allows the whole site to be backed by just 4 servers, and those are shared with other Channel 4 sites. It handles 1000 read requests per second, as well as 60-70 write requests per second.
Following the E4 site release at the end of 2007, the Channel 4 team decided to take advantage of ThoughtWorks’ Offshore Agile development team in Pune, India for continued site improvements. The transition was managed by Technical Leads from the UK taking a ‘seeding’ visit: they spent several weeks working together with the Pune team and Channel 4 on requirements, to ensure that all parties fully understood the architecture and domain. Day-to-day contact is managed through daily conference call stand ups, videoconference, webex and skype. The delivery team, although physically split between ThoughtWorks in Pune and Channel 4 in London, can keep collaborating and delivering high value functionality to the business. They have already released updates such as advertising innovations and games since the main site went live.
James Tatam - E4.com business manager
The site was built on RESTful architecture using JAVA and Open Source libraries. PicoContainer (dependency injection), String Templates (forcing best coding practice by disallowing logic in views), Hibernate (data management) as well as the Agile tools Go (for continuous integration), and Mingle (story management) were all used.
Partnering with ThoughtWorks, The Guardian developed a new platform, taking advantage of innovative technology and adopting new ways of working ...
This award winning site allows Lonely Planet to monetize their content and created a powerful social network around their content library.
Realizing the expected benefits of offshore software delivery is a significant challenge. Far too many distributed projects deliver late or not at all.
If you have a project or a sticky problem you would like to talk over with us, or would like to know more about our services, get in touch, we would love to meet up...