Skip to main content

Design Science Research (DSR) Made Simple

One of my design science research based  paper was recently accepted by IEEE and that ignited this article that I wanted to write for a while, as a masters dissertation supervisor, I find that many students don't understand Design Science Research (DSR) Methodology well. Many students struggle with DSR because they are used to the usual way of doing research: read some papers, write a report, and finish. But DSR is different. The main idea in DSR is to solve a real problem and show how your solution improved through several rounds of feedback. If you skip the improvements and only build something once, the whole purpose of DSR is lost.

Why Students Find DSR Difficult

Students often think DSR is only about building a system. They choose a topic, create one version of the system, test it once, and think the work is done. But DSR is not like a basic final-year project. You cannot just build something and call it research. You must show how your idea grew step by step.

Another problem is the literature review. Many students read only theory papers or general ideas. But in DSR, you must look for papers where other researchers built something: a prototype, a model, a dashboard, an algorithm, a tool. These papers help you understand how others created and tested their artefacts. You can then compare your work with them.

The Importance of Iteration

Iteration is the heart of DSR. You build, you test, you improve. Then you repeat. Without this cycle, your work becomes a simple development task, not research.

A normal DSR cycle looks like this:

  • Find the problem

  • Talk to people or read documents to understand what they need

  • Build a simple version (it can even be just UI first)

  • Show it to users and collect feedback

  • Improve the design

  • Build the working artefact

  • Get feedback again from users or experts

  • Improve it one more time

Each round must be written clearly. You must show what changed, why it changed, and what feedback made you change it.

Using Qualitative Data

Interviews and feedback forms are very important. They help you understand what people expect and what problems they face.

You can start with simple interviews:

  • What is the current problem?

  • What do you wish existed?

  • What features make your work easier?

  • What kind of interface do you like?

After you build the first UI, give users a small feedback form where they rate:

  • Ease of use

  • How clear the UI is

  • Whether the tool matches the problem

  • What they want changed

Experts can also review the system. They can check the architecture, performance, security, or accuracy. This gives you stronger evidence that your final artefact works.

How Iterations Improve Your Artefact

You can explain your work in steps. For example:

Iteration 1: Understanding the problem You interview users, read papers, and write down the needs.

Iteration 2: First design You create the UI or wireframe. You collect feedback on design and ideas.

Iteration 3: First working version You build the real system with basic functions and let users test it.

Iteration 4: Expert review Experts look at the architecture or code and give suggestions.

Iteration 5: Final version You fix issues, improve features, and prepare the final artefact.

What Counts as an Artefact

An artefact does not need to be a full business system. It can be:

  • A web tool

  • A mobile app

  • A machine learning model

  • A dashboard

  • A unique UI design

  • A new architecture or workflow

The important part is that it must solve a real problem.

Why DSR Is Practical

DSR allows you to create something useful. You can make a real product that people can use. But to make it research, you must connect your artefact to feedback and literature. You must show how every change has a reason.

If you do this well, your final output is stronger than a normal report. You end up with a working solution and proof that it actually helps the user.

Final Thoughts

DSR becomes easy when you stop thinking of it as pure coding and start seeing it as a guided improvement process. You build, test, fix, and repeat. You show how your solution gets better each round. You support every decision with literature, interviews, and feedback. When you do this, you produce real value and a strong piece of research.

Comments

Post a Comment

Popular posts from this blog

The Staff Engagement Paradox: Forcing the Illusion of Choice

Staff engagement, a concept praised for its ability to motivate employees and cultivate a positive work environment, can sometimes become a double-edged sword.  Initially, the intention behind organizing non-work-related activities, such as futsal competitions, was noble. These endeavours sought to provide employees with opportunities to connect and engage beyond the confines of their workspaces. The vision was to ignite motivation and foster unity. However, somewhere along the way, the true essence of these activities became distorted. The Penalties of Being Human Ironically, in their pursuit of encouraging staff engagement, companies implemented attendance marking systems and penalties for absence or tardiness. What was once voluntary and enjoyable participation has now been replaced by fear-driven coercion. Employees attend these events not out of genuine interest or enjoyment, but out of the dread of being shamed, penalized, or left out. The spirit of choice and voluntary engag...
Post a Comment
Read more

How the "push it" culture creates real "down fall".

In the world of organizational culture, the prevalence of a "push it" mentality often serves as a glaring indicator of more profound issues. It signifies more than just a commitment to excellence; it frequently represents the single most significant indication of an isolated, blame-oriented, and ultimately toxic culture.  In environments where the "push it" mantra prevails, collaboration becomes an afterthought, and leaders, whether consciously or inadvertently, exacerbate this toxicity by embracing this phrase. In this article, I will dive into the perils of the "push it" culture, and I will try to shed some light. If you have been hearing the phrase "you have to push it" or "I expect you to push it harder", that means you are already working in a counterproductive environment.  The Toxicity of "Push It" The "push it" culture, seemingly rooted in the pursuit of results, often conceals deeper organizational maladies....
Post a Comment
Read more

A National Cybersecurity Agency that could foster real impact.

  In an age where critical infrastructure and information systems are the cornerstones of national security, the role of a National Cybersecurity Agency has never been more crucial. It transcends the physical realm, acting as a digital guardian, safeguarding the nation's most sensitive data and ensuring the smooth operation of vital services. Beyond Reaction: A Proactive Approach The agency's mission extends far beyond simply reacting to cyberattacks. It's a multi-faceted entity with a diverse set of responsibilities: Strategic Vision:  Developing a comprehensive national cybersecurity strategy that aligns with the ever-evolving threat landscape and incorporates best practices from around the globe. Threat Intelligence Powerhouse:  Continuously gathering, analyzing, and disseminating real-time cyber threat intelligence to keep government agencies, businesses, and citizens informed and prepared. Risk Management Partner:  Assisting government entities and critical infr...
Post a Comment
Read more