;

Y20 Nº006 GRID Mag – Who do we serve in complex broadcast teams

Featured Image

Dear (none)Designer,

Welcome back to the sixth Design at Scale™ Newsletter – focusing on innovation and how design drives change in a large organisation.

There would be no update if the designer did not work for or with the British Broadcasting Corporation, known as the BBC. Many talented designers have had the opportunity to experience the nuances of fast-paced broadcast design.

Besides the BBC, ITV, Sky, and many other broadcast media houses, they all tend to have very product-led cultures. Therefore, the design function is primarily organised in a central team and later redistributed to separate design and product teams.

This creates two possible challenges for the designer IC. First, having two or sometimes multiple bosses. Product Owner, Line manager, Design Director, and the Producer – all debating that the priority of their task or request is above anything else. A recent mentee has brought this up in a very polite question:

"Who do I serve?"

The trick here is that serving everyone you serve no one.

Later in Design at Scale™ – Academy, we'll explore the Network effect in large organisations that helps individuals like yourself navigate these situations. Additionally, it's essential to understand the organisation's maturity, whether the communication channels are established for operational excellence, and whether people are effectively informed about what is happening.

In this scenario, the Design Director was the key stakeholder. In less than 4 weeks, we have mitigated all tensions and broadened the design on the track, so to speak.

How?

Multiple people have different objectives on how and why they want to be informed. Some seeks the power, some are seeking control, some are influencers, and some are decision makers.

Product Owner – Inform on a daily basis, ToDo, In Progress, Done, so-called status report.  

Line manager – Inform every week, RAG report

Design Director – Inform me about the proposition, customer, business, objectives, KPIs, etc. – also how to communicate back to CPO and the Producer.

Producer – every other day. Is the product in good shape to run smoothly, for live streaming or broadcasting?

Y/N.

If "No", how do we mitigate the issue at hand?

Can design help, and if so, how?

This goes back to the Design Director – this way, the flow in the organisation stays intact and everyone gets their portion of peace.

What we have done specifically.

1/ We've set up the Design Drop – and email, message or other piece of communication where she can communicate to a broader audience what happened. What are the blockers and potential threats?

2/ Mo-We-Fr – she communicated design challenges and how she wanted to approach them. In a very old-school email style, she stated the problem, provided a solution, and asked for direction.

3/ Weekly, she has sent a summary email to all project leaders, highlighting the challenges for an open discussion.

4/ Finally, she organised a small show and tell for her team to see where her thinking is and how the leaders contributed to unblock the decisions, sharing the credit with her supervisor.

This way, she simply turned the situation to her advantage and leveraged it to gain more time with her leadership team, as she presented problems and potential solutions.

That's all for this edition! I hope these insights were valuable and sparked new ideas for scaling your design propositions. Remember, the journey from concept to widespread impact is a shared one, and your experiences are invaluable. Keep experimenting, keep learning, and stay tuned for our next newsletter, featuring more strategies and success stories from our incredible community.

Happy scaling through design!

Hey, I’m Jiri Mocicka.
London-based Product Design Director, Trusted Advisor and Author of Design at Scale™. The method that empowers individuals to shape the future organisation through design.
If you have a question, join our Community and reach out to like-minded individuals who scale design propositions. An online Academy can help you to define teams of 01, 10, and 100, and 1% is supported by Grid Magazine and Supply section, where we bring more insights weekly on how to become a design leader in your Agentic Organisation

Jiri Mocicka

AVATAR

inResearch

21

inWriting

45

Released

260
EMT

Related.

Featured Image
Empathy as Infrastructure: The Internal User Experience of Scaled Systems The ultimate metric of any enterprise system is a deceptively simple question: Does it …
February 16, 2026
 · 
4 min read
Featured Image
Organisations trimming entry-level positions in pursuit of AI-driven efficiencies are engaging in a calculation that appears eminently rational when viewed through the lens of …
April 3, 2026
 · 
7 min read
Featured Image
Aligning Human Senses and Technical Communication to Unlock Enterprise Scale In a quickly evolving global corporate environment, cross-functional alignment is the ultimate metric of …
April 6, 2026
 · 
4 min read
Featured Image
Yes, let's begin. Where shall we start? The newsletter, articles, posts and many other forms of content are generated in order to scale your …
January 30, 2020
 · 
2 min read
Featured Image
Write the Press Release Before You Write a Line of Code Most teams write documentation to justify what they’ve already decided to build. Amazon’s …
February 15, 2023
 · 
5 min read
Featured Image
Build Down From Why, Or You’re Just Building Features Most product visions get written backwards: the feature list comes first, and a mission statement …
February 8, 2023
 · 
5 min read
Featured Image
Build the Fit Before You Build Anything Else A product doesn’t usually fail because the build was bad. It fails because nobody has proved …
January 11, 2023
 · 
5 min read
Featured Image
Make the Old New, Then Prove Which Idea Earns Its Build Most brainstorming sessions don't fail for lack of ideas. They fail because nobody …
February 1, 2023
 · 
5 min read
Featured Image
Make the Old New, Then Prove Which Idea Earns Its Build Most brainstorming sessions don't fail for lack of ideas. They fail because nobody …
January 25, 2023
 · 
5 min read

GRID Magazine

Explore OUR 
Articles

Every week we bring set of stories reflecting on communication, operation and technology.

Newsletter

Subscribe.

We share our 20 years of experience in creating, managing and scaling products and services that allow individuals to shape organisations through design.

Design at Scale™

LINE_MAGENTA_050_301

Categories

LINE_MAGENTA_050_301

Data

LINE_MAGENTA_050_301

Share

Internal

Collaborate

Resources

IBM PlexSan
Regular
Charcoal

Design at Scale™ is defined by three models, which form the Method. Each model operates in a different part of the business and collects and informs parties on design and engineering decisions that have a direct impact on the delivery.

All brands and trademarks presented on the Design at Scale™ website are owned by their relevant companies or agencies. The projects represent collaborations between designers, developers and product owners. Do not copy or publish any of the projects shown here without written approval from Design at Scale™ (alternatively GIVE™, 9V™) and/or relevant companies and agencies.

SOC_Twitter
SON_LinkedIn
SON_Instagram
SOC_-Medium
View