Design’s Real Crisis: When Practice Becomes Invisible

A Personal Reflection on Design, Leadership, and Organizational Maturity

The Moment I Realized

I used to think design problems were design problems.

Someone would ask me to redesign a feature. I’d research it. I’d sketch solutions. I’d prototype. I’d iterate. And I’d ship something that worked. I thought that was the job.

Then I moved to a company where the design process looked the same, but felt completely different.

Same research. Same sketches. Same prototyping. Same shipping.

But the impact was 10x different.

I didn’t understand why until someone said: “The difference isn’t your skill. It’s whether anyone listens to what you learn.”

That sentence stuck with me for years.

What I’ve Learned (The Hard Way)

I’ve worked in organizations where design was:

• A final step: “Make it look good”
• A checkbox: “We did user research”
• A service: “Design will do whatever you need”
• A capability: “Design shapes what we build and how we build it”

Same discipline. Completely different impact.

The difference wasn’t the designers. It wasn’t the tools. It wasn’t the process.

The difference was whether the organization treated design as a practice worth investing in — or a service to resource when needed.

What “Design Practice” Actually Means

Let me be specific about what I mean by design practice, because it’s not what most people think.

Design practice isn’t:

• Pretty pixels
• User interface polish
• A research methodology
• A list of best practices

Design practice is: A structured way of thinking about problems before solving them.

It’s asking “who are we building for, and why?” before jumping to solutions.

It’s gathering evidence instead of guessing.

It’s testing assumptions instead of confirming them.

It’s measuring whether the thing you built actually solved the problem.

And here’s the part organizations often miss: This practice only works if someone is listening.

If you do brilliant research but no one values it, the research is wasted.

If you propose alternative solutions but you don’t have authority to influence decisions, the alternatives are ignored.

If you measure impact but no one cares about the metrics, the measurement is theater.

Design practice requires organizational permission to matter.

The Structure That Enables (or Blocks) Practice

Over the years, I’ve noticed a pattern in which organizations’ design practices actually create impact.

It’s not random.

Organizations where design practice thrives have certain structural elements in common:

1. Someone advocates for design thinking (a design leader with strategic voice)
2. Designers see a future for themselves (career paths and growth)
3. Design decisions are evidence-based (metrics that matter, not opinions)
4. Design shapes what gets built (not just how it looks)
5. Designers learn from each other (peer community and standards)

Organizations where design practice atrophies are usually missing one or more of these.

A Confession: I Used to Blame the Designers

I spent years thinking: “If only designers were more strategic. If only they could speak the business language. If only they understood the numbers.”

As if the problem was individual designer skill.

Then I realized something: I was wrong.

I watched brilliant designers become invisible because their organization didn’t have a design leader to advocate for them.

I watched sharp researchers produce insights that got filed away because there was no process to act on the research.

I watched experienced designers leave companies because there was no path forward — not because they weren’t good, but because the organization didn’t believe in design enough to create one.

The problem wasn’t the designers. It was the organization.

But here’s what’s important: That’s actually good news.

Because organizations can change. Individuals can build structures. Leaders can make different decisions.

Who This Matters For (Everyone, Actually)

Let me be direct: This applies to you, regardless of your role.

If You’re a Designer

You’re probably feeling one of two things:

If you’re frustrated: “My ideas aren’t heard. My research doesn’t influence decisions. I’m just executing specs.”

If you’re thriving: “I can do my best work. People listen. I can see how my work affects the business.”

The difference between these two isn’t your talent. It’s your organizational structure.

The brutal honesty: If your organization doesn’t have structure that values design practice, you have three options.

1. Work to build that structure (from inside, with allies)
2. Accept that you’re going to be less impactful than you could be
3. Move to an organization that already has it

All three are legitimate. But know what you’re choosing.

If You’re a Design Leader

You’re probably managing a team and trying to figure out: “How do we make sure this team has impact? How do we prevent burnout? How do we build something that lasts?”

You’re thinking about structure because you have to.

The structure you build determines whether your team becomes strategic or stays tactical.

It determines whether designers grow or plateau.

It determines whether they stay or leave.

The five elements I mentioned earlier — they’re not theory. They’re infrastructure. They’re the foundation you need to build.

And yes, it takes time and political capital. Yes, it’s harder than just shipping features.

But it’s the difference between managing a service function and building a capability.

If You’re an Executive or Leader in Any Function

You might not think about “design practice” as your problem.

But you should.

Because design practice isn’t just for design departments.

Product teams need it. Operations teams need it. HR teams need it. Customer success teams need it.

Any team that solves problems for users (internal or external) benefits from:

• Structured thinking before jumping to solutions
• Evidence-based decisions instead of gut feel
• Measuring whether you actually solved the problem
• Building on what worked, not repeating what failed

Design practice is organizational thinking.

And the question for you is:

Do you have leaders and structures that enable it? Or are you hoping each team invents it themselves?

What Changed My Perspective

I stopped thinking about this as “design advocacy” and started thinking about it as “organizational capability.”

When you frame it that way, the question isn’t: “Does design deserve a seat at the table?”

The question becomes: “Do we want to solve problems thoughtfully, or do we want to hope for the best?”

And suddenly, design practice isn’t a nice-to-have. It’s a basic business requirement.

The Five Elements (Why They Matter)

If I were advising any organization — design-heavy or not — on building a practice of thoughtful problem-solving, I’d focus on these five things:

1. Someone Has to Advocate for the Practice

What this looks like: A leader (in design, product, operations — doesn’t matter) who believes in the practice and has authority to defend it.

Why it matters: Thoughtful problem-solving takes time. It requires asking questions before jumping to answers. When timelines are tight, corners get cut. Without a leader willing to defend the practice, it gets cut first.

The cost of skipping this: Decisions get made on speed, not substance. Problems get half-solved. You end up in rework cycles.

2. People Need to See a Future in It

What this looks like: Career paths. Mentorship. Different roles (specialist, leader, researcher, architect). Room to grow.

Why it matters: If the only path forward is “become a manager,” you lose good individual contributors. If there’s no mentorship, people don’t develop. If everyone does the same job, there’s no learning.

The cost of skipping this: Your best people leave. Institutional knowledge walks out the door. You have to rebuild constantly.

3. You Need to Measure What Actually Matters

What this looks like: Metrics that show whether you solved the problem. Not activity metrics (“we did research”), but outcome metrics (“this research changed the decision and improved the result”).

Why it matters: Without measurement, it’s just opinion. Your opinion versus my opinion. Design thinking wins arguments when you have data.

The cost of skipping this: Design gets treated as taste, not strategy. Every decision gets debated. You can’t prove value.

4. The Practice Has to Influence What Gets Built

What this looks like: Design/research/thinking happens early, when decisions can still be shaped. Not after engineering has already committed.

Why it matters: If you solve the problem perfectly but start from the wrong foundation, you’ve wasted effort. If you solve the right problem, you accelerate.

The cost of skipping this: Rework in every cycle. Features ship and need redesign. You’re always playing catch-up.

5. People Need Community Around the Practice

What this looks like: Spaces where people practicing this way can learn from each other. Critique sessions. Case study discussions. Peer mentorship. Shared standards.

Why it matters: When you’re isolated, you think your problems are unique. When you have community, you realize they’re common and solvable. You learn faster. You feel less alone.

The cost of skipping this: People burn out. They make the same mistakes repeatedly. Standards drift. Quality becomes inconsistent.

The Five Elements Don’t Have to Start with “Design”

Here’s what I want to emphasize: These five elements don’t only apply to design functions.

I’ve seen product organizations that have great structure and culture.

I’ve seen operations teams that practice this way.

I’ve seen HR functions that do this thoughtfully.

Any organization trying to solve problems systematically benefits from these five elements.

It’s not “design structure.” It’s “structure for thoughtful problem-solving.”

The Truth About Burnout (Why It Matters)

I mentioned earlier that good structure prevents burnout. Let me explain why.

Burnout happens when:

• You work hard but nothing changes
• You have ideas but no one listens
• You grow your skills but there’s nowhere to apply them
• You see problems but can’t fix them
• You’re isolated and think your struggles are unique

None of these are personal failures. They’re all structural.

If your organization has:

• A leader who advocates for your work
• A path to grow
• Evidence that you’re having impact
• A seat in decisions
• Peers facing similar challenges

Then burnout becomes less likely. Not impossible — reasonable workloads matter, and your own resilience matters. But less likely.

And here’s what I’ve learned: Organizations that prevent burnout don’t do it by accident. They do it by building structure.

The Question I’m Asking You

Whether you’re a designer, a design leader, or an executive in any function:

Does your organization have these five elements?

1. Someone advocating for thoughtful problem-solving
2. Career paths and growth opportunities for people doing it
3. Measurement of actual outcomes
4. Early involvement in decisions
5. Community and peer learning

If yes: You’re building something that lasts. You have an advantage over competitors who rush.

If no: You’re betting on individual heroics. It works until it doesn’t.

If partial: You know what to build next.

What I’d Do If I Were Starting Over

If I were starting a new organization or restructuring an existing one, here’s how I’d think about design practice:

Month 1: Identify or hire someone who believes in it (design leader, product leader, operations lead — whoever will fight for it)

Month 2–3: Work with that person to define what “thoughtful problem-solving” looks like in your context. What does research mean? What does measurement mean? What does good look like?

Month 4–6: Start building the other four elements. Create clear roles. Start measuring. Bring people into decisions earlier. Create space for people to learn together.

Month 7–12: Iterate. See what works. Double down on what’s working. Fix what isn’t.

Year 2+: Expand. Train others. Scale the practice. Make it cultural, not dependent on one person.

The cost: One person’s salary/time. Some process overhead. Maybe some inefficiency while you’re learning.

The return: Problems get solved better the first time. People stay longer. You move faster than people who have to rework constantly.

Why This Matters Now (And Why It Will Matter More)

I mentioned AI at the start, and I want to come back to it.

As organizations deploy more AI, the decisions become:

• Who should this system serve?
• When should humans override the algorithm?
• How do we ensure it’s fair?
• What’s the user’s experience when the AI fails?

These are design questions. They’re not technical questions. They’re not product questions. They’re questions about human experience and responsibility.

If your organization doesn’t have people trained to ask these questions — and trained to do it early — you’re going to end up with AI systems that are efficient but confusing, powerful but untrustworthy.

Design practice becomes even more essential in an AI-driven world.

But it only works if you have the structure to make it matter.

The Hard Truth (And the Hope)

The hard truth: If your organization doesn’t have structure that values design practice, individual heroics won’t fix it. You can be brilliant and still be ignored.

The hope: Organizations can change. Structure can be built. Leaders can make different choices.

The reality: It requires investment. It requires someone to care enough to build it. It requires time.

But every organization that’s done it says the same thing: “This is worth it.”

What I Believe (After All This)

I believe that:

Every organization solves problems. That’s the core work. Whether you’re building products, running operations, managing people, or serving customers — you’re solving problems.

Some organizations solve them thoughtfully. Others solve them randomly.

Thoughtful problem-solving isn’t magic. It’s structure. It’s asking the right questions before jumping to answers. It’s gathering evidence. It’s measuring results. It’s building on what works.

And here’s what I’ve learned: Organizations that build structure for thoughtful problem-solving don’t just have better outcomes. They have happier people. They keep their best people. They move faster. They have competitive advantage.

This isn’t a design issue. This is an organizational issue.

And it applies to you — whether you’re a designer frustrated by being ignored, a design leader building a team, or an executive trying to figure out how to stay competitive.

The Invitation

So here’s what I’m asking:

Look at your organization. Do you have the five elements?

If you do: Celebrate it. Protect it. Fight to keep it because it’s valuable.

If you don’t: Pick one. Build it. See what changes.

If you’re a designer: Work with allies to build the structure. Or evaluate whether you want to stay.

If you’re a leader: Invest in the structure. You’ll get it back in outcomes and retention.

If you’re an executive: Understand that this structure affects your competitive position. Get involved.

Design practice isn’t a luxury. It’s organizational thinking. Every organization needs it.

The question is: Do you have the structure to enable it?

Closing Thought

I started by saying I used to think design problems were design problems.

Now I know: Most “design problems” are actually organizational problems.

The solution isn’t better designers. It’s better structure for all the designers you have.

And that’s something any organization — any leader — can build.

The question is: Will you?