;

Y23 Nº037 GRID Mag – Signal vs Noise

Featured Image

Dear (none)Designer,

Welcome back to the thirty-seventh Design at Scale™ Newsletter – focusing on innovation and how design drives change in a large organisation or an agency.

As we enter the 21st century, we find ourselves in an era of data saturation, significantly impacting our daily lives. The McKinsey 7S Framework is a well-recognised tool that helps organisations evaluate and manage change by analysing seven interconnected elements. These elements work together to ensure that an organisation performs effectively while maintaining alignment and mutual reinforcement.

The seven "S" elements are:

Hard Elements (more tangible):

  • Strategy: The "tactical" plan for achieving competitive advantage.
  • Structure: How the organisation is organised
  • Systems: The processes, procedures, and daily operations.

Soft Elements (more intangible):

  • Shared Values: The core beliefs and corporate culture that guide the organisation.
  • Skills: The capabilities and competencies of the organisation and its employees.
  • Staff: The individuals within the organisation, including their demographic, educational, and attitudinal characteristics.
  • Style: The leadership and management approach within the organisation.

Paradoxically, leaders focus on a guiding YouTube video on how to conquer the amount of emails or how best to manage our Slack and MS Teams. How can we collect feedback from the site or any other communication medium? Additionally, do we have a roadmap, weekly plans, and a 'how might we' plan for the level of effort in a constantly evolving, dynamic world of constant change?

To many designers (or other professionals), this is not a so-called "cohesive and complete picture" of the proposition that your team is spending the time on.

Many companies create and maintain processes that replicate the agreements and the communication across the two chains of command (client-agency, business–delivery). Believing that what has been agreed (with minimal knowledge at the beginning) will remain throughout the entire proposition, the same.

In contrast to containing the understanding of a constantly evolving proposition, we need to translate the overall business complexity into a space (not a document) that reflects the level of effort, statement of work, identification document, and other relevant documents living in an ecosystem and constantly adapting to new situations. In other words, these documents function like smart documents and evolve in response to one another.

How can we navigate correctly across all these different touchpoints, and how can we identify the signals and reduce the noise?

Inevitably, each document or other piece of evidence, so to speak, will have at least some fraction of the information that designers need. Preferably, all tied to design function, in a unified form or shape that reflects the design team and how it fits into a big picture—profoundly altering the whole cycle and the blend between business, design and development.

Specifically, the type of information we need to deliver the proposition on time.

Here are some questions you might want to ask;

  • What problem are we solving instead of what are we building?
  • Do we rely on existing functionality, or are we building a new proposal?
  • Are we integrating the brand or changing it?
  • Do we have a design system, and if not, are we building one?
  • Do we have access to the engineering team, and if not, how do we hand over our files?
  • If we do, what are the SLAs in place, and what can we rely on to reach a successful handover?
  • How many people are in our team?
  • How many people do we support?
  • How many people support us?
  • What, when, and how we communicate the incremental delivery update throughout the entire project or delivering the proposition

Inevitably, these high-level questions should give you a better, if not greater, understanding of where you and your team are. Whether you are a junior, midweight or senior designer, these questions and hopefully their answers will guide you through the process of where you are and where you need to go next.

To those who wish to set themselves apart from the competition, we offer a Design at Scale™ – Academy courses where we collect, debate and train designers in teams of 001, 010, and 100 to break the silos and communication barriers and become leaders that deliver Design at Scale™.

For more information, please visit Designa at Scale™ – GRID Magazine, where you can find additional relevant articles that explore high-performing teams, self-organising teams of 001, teams of 010, and teams of 100 that deliver the value proposition within a product-led environment.

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% supported by Grid Magazine and Supply section, where we bring more insights weekly on how to become a design leader in your Agentic Organisation

Author's Name

AVATAR

inResearch

42

inWriting

77

Released

230
EMT

Related.

Featured Image
Welcome to the Jira for Designers series brought to you by Design at Scale™ – Academy. In a previous article, we discussed Design planning(↘︎Link) and how the basic structure of design operations can improve organisational …
 · 
2023-03-27
 · 
6 min read
Featured Image
The most common interview opener is also the most commonly botched. Not because candidates lack a wealth of experience or confidence, but because they fundamentally misunderstand what is being asked of them. Master this …
 · 
2021-01-03
 · 
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 operational achievement. Yet, semantic and physiological noise creates friction at …
 · 
2026-04-06
 · 
4 min read
Featured Image
Welcome back; this article is part of the series called DaS™ – Naming convention. The previous article explored the history and mental models behind sorting information in digital space. This article will discuss how …
 · 
2020-05-11
 · 
6 min read
Featured Image
Welcome back; this article is part of the series called Naming convention. The previous article explored the history and mental models behind sorting information in digital space.[001↗] This article aims to discuss the naming …
 · 
2020-05-04
 · 
6 min read
Featured Image
We’ve all been there. Someone, most probably a boss, asks us to find the latest email or Miro [001↘︎] board or simply share a file created a while ago, and we struggle to find …
 · 
2020-04-27
 · 
5 min read
Featured Image
Welcome back; this article is part of the series called Naming convention. The previous articles explored the impact of folder naming conventions. This article discusses the naming convention inside the CX and UI files …
 · 
2020-04-20
 · 
5 min read
Featured Image
The tech industry, and design within it, often perpetuates a comfortable myth that every designer needs a single, seasoned mentor to navigate their career in constant change. That is why thousands of designers turn …
 · 
2021-08-01
 · 
6 min read
Featured Image
Welcome to the Design at Scale Method series. Today’s article has no more minor ambition than to connect, empower and unify all product designers under a simple Manifesto, which easily translates the value of …
 · 
2021-02-17
 · 
3 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