Designing BBC internal software tools: iSite and iBroadcast


Tagged with:

Hi, I’m Alistair Tearne a User-Experience designer (UX) working at the BBC. I work within the Publishing Tools team at the BBC with Jay Heal, UX designer, and Joanna Attree, UX Architect.

So, those BBC articles you read, and those iPlayer episodes you watch, how does all that stuff end up online? Is there a big machine that takes video clips, articles, images, and audio and spins them together into order; steam cleans and irons them into crisp processed content?

Well, that’s sort of how it is! We have a selection of internal software tools that staff, journalists and production teams use to create and manage content that you find on BBC Online, and applications on mobile and TV. iBroadcast and iSite are two of these. They are two of the BBC’s most vital tools used to output programmes, video clips, audio and images, and in the case of iSite, pages for programme sites such as Top Gear, The Voice, Eastenders, CBeebies, and Desert Island Discs. Even this blog post was published using iSite.

iBroadcast and iSite logos

What is great about software design is that we’re solving problems for users close to us. There are over one thousand BBC staff members who rely on iSite every day, and over two thousand who use iBroadcast. Amongst other things, our job as UX designers involves identifying and designing solutions for user needs. If we can make something more intuitive, we might improve the working lives of our colleagues. And if they can work more efficiently, they can offer better content to you!

So, what are the challenges of designing such software?

Software design is complex. Even with a strong voice from the product owner, the detail around interaction patterns and behaviours can be lost-in-translation between Business Analyst, Designer, and Developer. Involving the wider product group in ideation and documentation has proved essential for establishing a shared vision of the product, and we found Gamestorming an incredibly useful set of techniques for collaborative working.

Using Gamestorming techniques

One style fits all?

Many of our content producers and editors switch between iSite and iBroadcast for various tasks. It’s important to remember, therefore, that as a suite of products, the interaction patterns, visual style, and behaviours are as consistent as possible. The more intuitive we make our products, the more trust there will be in any given workflow.

iSite and iBroadcast headers and main navigation

iSite is currently undergoing a complete redesign. The current version, built on the open source Alfresco framework, worked well for several years but is no longer able to keep up with the evolving requirements of the BBC. It will be replaced with the brand new iSite 2, built completely in-house, with a well-defined and finite list of requirements. iBroadcast 2, however, is an evolving product. Designers have joined and left the team over the years and they’ve all left their mark on the design. It would be amazing to start afresh, bringing both products inline. But, with iBroadcast’s short releases and growing list of requirements (see Mathew Browning’s post), this would cause more pain to the user.

The new iSite interface

So, we’ve had to audit, consolidate and refresh the design of iBroadcast, whilst being aware of a growing base of existing user habits. It’s dangerous to change a button style, or workflow navigation, when the user has grown so used to it. Furthermore, each product has its own mechanics. The unifying style guide needs to unite a suite of tools, yet remain loyal to the user’s understanding of its functions. After all, we want to greatly improve the experience of the product, whilst minimising the learning curve.

Example of the style guide

User testing is vital for this purpose. We test little and often, and validate our design assumptions to ensure we’ve understood each problem. We use paper prototypes, clickable PDFs, and occasionally, coded prototypes. Often, what you think may be a successful design can fail when tested, so although we aspire to a single visual style guide and set of interaction patterns, being fit for purpose will always come first.

This is a small insight into the work we do as User Experience Designers, and the world of internal software. We’re continuing to learn and improve our design techniques. Let us know if you want to hear more about our work.

Alistair Tearne is a User Experience designer in UX&D, BBC Future Media

Tagged with:


This entry is now closed for comments.

  • Comment number 4. Posted by Jay Heal

    on 31 Jul 2013 14:22

    Great post!!! iSite UI looks great!

    Interaction design looks pretty good too :-)

    • This entry is now closed for comments. Number of positive ratings for comment 4: 0
    • This entry is now closed for comments. Number of negative ratings for comment 4: 0
  • Comment number 3. Posted by Alistair Tearne

    on 30 Jul 2013 10:34

    @ FishFingers

    Hi there,

    Thanks for your question.

    Our User Experience Architects (UXA) are essentially Information Architects with a degree of overlap with User Experience Design (UXD).

    Information Architecture is about understanding content, its use to the user, its metadata, considering its scalability and maintenance. It often involves auditing, assessments and defining the structure of the content and how it appears to a user.

    Our User Experience Designers (UX), however focus more on interaction design, that is, what buttons do, how a user navigates from one space to another, highlight effects, etc. I would also say there is more visual design involved in UX than in UXA, which focusses largely on the data itself.

    I hope this helps! Like I say, there is overlap between the two roles here, but largely, UXA designers work on projects where there are particularly complex data structures, such as iBroadcast.


    Thanks very much! There should be more UX&D posts coming soon, so do check back.


  • Comment number 2. Posted by Benjamin

    on 25 Jul 2013 16:44

    Stunning design! I would indeed like to see more about the projects the user experience designers work on.

    • This entry is now closed for comments. Number of positive ratings for comment 2: 0
    • This entry is now closed for comments. Number of negative ratings for comment 2: 0
  • Comment number 1. Posted by FishFingers

    on 23 Jul 2013 11:05

    Interesting post, wish there were more screenshots!

    Can you explain what the difference between a UX Designer and a UX Architect is at the BBC?

    • This entry is now closed for comments. Number of positive ratings for comment 1: 0
    • This entry is now closed for comments. Number of negative ratings for comment 1: 0

More Posts