What is the Design Thinking Process?

TL;DR

• The design thinking process is a structured way to understand problems before building solutions
• It focuses on people, workflows, systems, and data — not just outputs
• Most organisations rush or skip this step, which leads to rework and poor adoption
• A design-led approach reduces risk, aligns stakeholders, and leads to better outcomes
• Notitia applies this through a structured readiness and design-led process before any build begins

‍

What is the design thinking process?

‍

The design thinking process is often described in neat, structured stages: empathise, define, ideate, prototype, test. It’s a useful starting point, but it doesn’t quite reflect how organisations actually operate.
‍

In practice, design thinking is less about following a sequence and more about building a clear, shared understanding of a problem before moving toward a solution. It requires stepping back from assumptions and looking closely at how work is really being done, not how it’s documented, not how it’s intended, but how it actually plays out day to day.
‍

At its core, the design thinking process is about creating clarity. It brings together different perspectives across a business and makes sense of how people, systems, and data interact. Without that clarity, even well-funded projects can drift off course, because they’re built on an incomplete or inconsistent view of reality.

‍

Why this matters more than most teams realise

‍

There’s a common belief that if a project has strong requirements and the right technology, it should succeed. But that’s rarely what happens in practice.
‍

Across sectors, from healthcare to government to commercial organisations, the same pattern shows up again and again. Teams move forward with delivery before they’ve fully aligned on what the problem is. Requirements are signed off, but they reflect different interpretations across the business. Systems are implemented, but they don’t quite match how teams actually work.
‍

This gap between expectation and reality is where most issues begin.
‍

It’s not that organisations don’t care about getting it right. It’s that the step where these issues could be resolved, right before a build begins, is often treated as optional. It’s seen as slowing progress, or something that can be worked out along the way.
‍

In reality, skipping this step is what creates delays later. It leads to rework, frustration, and solutions that need to be reshaped after they’ve already been built.
‍

The design thinking process (in real terms)

When you move beyond theory, the design thinking process becomes less about stages and more about understanding what’s actually happening within an organisation.
‍

1. Understanding people and context
‍

This is where the process begins, but it’s often underestimated.
‍

It’s not just about gathering feedback or running interviews. It’s about building a genuine understanding of how different teams operate, where decisions are made, and what pressures people are working under. In many cases, this reveals a version of the organisation that hasn’t been formally documented.
‍

Workarounds, informal processes, and unwritten rules often play a significant role in how work gets done. Without recognising these, any future solution is already misaligned.
‍

2. Mapping how the organisation operates
‍

As these insights come together, a clearer picture starts to form.
‍

You begin to see how workflows move across teams, where systems intersect, and where gaps or inconsistencies exist. This step often highlights duplication, conflicting definitions, and reliance on manual processes that have developed over time.
‍

What’s important here is not just identifying these issues, but understanding how they connect. When people, processes, and systems are mapped together, patterns become visible in a way that isolated analysis can’t achieve.
‍

This is often the point where organisations realise the problem is different, and more complex, than initially assumed.
‍

3. Defining the actual problem
‍

This is the point where design thinking has the most impact, and it’s also where most organisations fall short.
‍

There’s a strong tendency to move quickly into solution mode. A need is identified, and it’s translated into something tangible, a dashboard, a system, a platform. But these are outputs, not definitions of the problem itself.
‍

Taking the time to properly define the problem requires challenging assumptions and bringing stakeholders together around a shared understanding. This can be uncomfortable, particularly when different teams have different perspectives.
‍

But without this alignment, any solution is built on unstable ground.
‍

4. Exploring and testing ideas before building
‍

Once the problem is clearly defined, the process becomes more practical.
‍

Instead of committing to a single approach, different ideas can be explored and tested. This might involve simple prototypes, walkthroughs, or early-stage designs that allow teams to see how a solution could work in practice.
‍

This stage is less about perfection and more about validation. It gives organisations the opportunity to test assumptions and refine their approach before making significant investment decisions.
‍

In many cases, this step prevents organisations from building something that would have needed to be reworked later.
‍

5. Designing and delivering with clarity
‍

By the time delivery begins, the difference is noticeable.
‍

Requirements are no longer based on assumptions, they’re grounded in how the organisation actually operates. Stakeholders are aligned, not just on what’s being built, but on why it’s being built. Risks have been identified early, rather than emerging during delivery.
‍

This doesn’t remove complexity, but it does make it manageable. It creates a foundation where what gets built is far more likely to be used, trusted, and effective.
‍

Where Notitia’s design-led approach fits
‍

Understanding design thinking is one thing. Applying it consistently in complex environments is another.
‍

This is where many organisations struggle. They recognise the value of defining problems properly, but they don’t have a clear way to operationalise it across stakeholders, systems, and data.
‍

Notitia’s approach is designed to bridge that gap. It takes the principles of design thinking and turns them into a structured process that can be applied in real-world environments — particularly where complexity, risk, and scale are high.
‍

Notitia’s design-led process (how this works in practice)
‍

At Notitia, the design thinking process is applied through a design-led readiness approach. The focus is not just on understanding users, but on understanding the full operating environment before any solution is defined.
‍

Step 1: Establishing operational reality
‍

The starting point is building a clear and grounded view of how the organisation operates. This is done through four interconnected lenses: people, processes, systems, and outputs.
‍

Looking at these together allows a more complete picture to emerge. It highlights where decisions are made, how work flows, where data is created and used, and what information is relied on.
‍

This step often surfaces insights that haven’t been visible before, simply because they haven’t been examined in a connected way.
‍

Step 2: Identifying gaps, risks, and misalignment
‍

With this foundation in place, areas of friction become easier to identify.
‍

These might include inconsistencies in how data is defined, gaps between systems, or unclear ownership of reporting and decision-making. In many cases, these issues sit beneath the surface and only become visible when the organisation is viewed as a whole.
‍

This step is critical because it shifts the focus away from tools and toward the underlying causes of inefficiency.
‍

Step 3: Aligning stakeholders on the problem
‍

Alignment doesn’t happen automatically, particularly in larger or more complex organisations.
‍

Different teams often have different priorities, perspectives, and definitions of success. Bringing these together requires structured conversations and a shared view of how the organisation operates.
‍

This is one of the most valuable parts of the process. Once stakeholders are aligned on the problem, decisions become clearer and more consistent.
‍

Step 4: Defining the right path forward

‍

Only after this alignment is established does the focus shift toward solutions.
‍

At this stage, potential approaches can be explored with a much higher level of confidence. Objectives are clear, constraints are understood, and the organisation is in a position to make informed decisions about what to build, or not build.
‍

Step 5: Designing with purpose
‍

The final step connects directly to delivery.
‍

Because the groundwork has been done, design and development are guided by a clear understanding of the organisation. This reduces ambiguity and ensures that what is built reflects how the business actually operates.
‍

It also creates a stronger foundation for adoption, because users can see their own workflows and needs reflected in the final outcome.
‍

What this approach does, in simple terms, is remove guesswork.
‍

Instead of relying on assumptions or partial views of the organisation, it creates a shared understanding that informs every decision that follows. This reduces the likelihood of rework and increases the chances that what is delivered will be used and trusted.
‍

It also changes the nature of project risk. Rather than risk emerging during delivery, it’s identified and addressed early, when it’s easier and less costly to resolve.

‍

If you’re about to invest in new technology, reporting, or a system build, the most important question isn’t what to build. It’s whether there’s a clear, shared understanding of how the organisation works, and what problem needs to be solved. That’s where a design-led approach makes the difference. ‍
‍

Get in touch with our team to find out how we can help.

‍

Frequently asked questions

What is the design thinking process in simple terms?

It’s a way to understand a problem properly before solving it, by focusing on how people, systems, and data interact in the real world.

How does Notitia apply design thinking differently?

Notitia applies it as a structured, design-led readiness process that maps how organisations actually operate before defining or building solutions.

Why do projects fail even after requirements are signed off?

Because requirements are often based on assumptions or misalignment, rather than a shared understanding of the problem.

What is a design-led approach to problem solving?

It’s an approach that prioritises defining the problem through real-world understanding before designing or building a solution.

‍