Designing the "Blank Slate" of an organization
The first time you open an application you just installed, you might see several frames and components that look empty. These will fill up with your data as you start using the application. Designers call this initial state a "Blank Slate."
It's now widely recognized that neglecting to design the blank slate is a big mistake because it's the user's first impression of your product. You might have the best user interface when the app is filled with data, but users may never reach that stage if it's not clear how to interact with the application when it's empty.
This is a fascinating concept, and as I was reflecting on how organizations evolve, I thought that many business leaders could take a page from the designer’s book about the importance of “blank slates” in their plans. Sure, when you step into a new role, tasked with transforming a department, it’s crucial to have a vision for how teams will interact in the future, which roles to introduce, which profiles to hire, and who will be responsible for what. However, a leader should not bypass the design of the “blank slate”, as in, the snapshot of what the organization looks like at the beginning of this transformation.
Too often, leaders can’t resist the temptation of dictating their vision from an ivory tower, while hiring a layer of smart middle-managers and delegating the execution of the plan to them. But even the most brilliant hires will get lost in the mess if they are shown a picture that only exists in the head of their enlightened boss. Imagine welcoming a new engineer into a maze of legacy services nobody remembers how to sunset. She receives a visionary slide describing a “data mesh” utopia, yet her onboarding checklist is full of monoliths that refuse to die.
In the gulf between present reality and promised future, talent grows frustrated, momentum stalls, and politics fill the gaps. Legacy services keep getting more and more consumers without a clear horizon for deprecation. Teams and people who struggle to see themselves in the future picture fight to stay relevant, trying to expand their area of influence until someone with a mandate tells them to stop.
Designing that organizational blank slate means scripting the first moves, not just day‑three‑hundred outcomes. Leaders should map out temporary but explicit ownership zones, identify what must be kept running at all costs, and label the placeholders that are expected to disappear. Much like the “Add your first project” card in an empty dashboard, these markers tell every newcomer, “Here’s where to start making an impact, and here’s when this chunk of work should gracefully sunset.”
