From a Specialized Methodology to an Experience Entrepreneurs Could Understand

01 — Context

A Saudi entrepreneurship and innovation initiative offering programs that help participants move from an initial idea to a project or product that can be tested. The programs follow a structured journey covering idea generation, design thinking, validation, prototyping, experimentation, launch, and operation.

The methodology itself was well established and based on internationally recognized practices. The challenge was making it understandable to an audience that was not necessarily familiar with its terminology. For someone seeing terms such as “validation,” “prototype,” or “design thinking” for the first time, it was not always clear what they would actually do, whether the program was right for them, or what they would leave with at the end.

The work focused on turning the methodology into a digital experience that explained the program in terms closer to how participants think and make decisions, while also creating a consistent system for program pages, supporting materials, reports, and presentations that could evolve across different cohorts and versions of the initiative.

02 — The problem

The same questions came up before almost every registration: What will I actually do week by week? Do I need to have an idea already, or is developing the idea part of the program? And what will I have at the end?

The website did not answer these questions directly. Program pages described the stages through the language of the methodology rather than explaining what the participant would actually experience. For someone who had never built a project or product before, it was difficult to understand whether a particular stage was a workshop, an assignment, or a tangible output they would carry into the next stage.

Information was also spread across program pages, registration pages, social media, reports, and presentations. Some of the strongest evidence of the programs’ value, such as prototypes and projects created by previous participants, existed in internal files that prospective participants never saw.

The initiative therefore had a strong methodology and a real track record of participant outputs, but the digital experience was not communicating that value with the same clarity.

03 — What I did

I rebuilt the program experience around the actual stages participants go through, while translating the methodology into language they could understand before becoming familiar with its terminology. Each stage clearly explained what the participant would do, what they would produce, and how they would move to the next step. The methodology remained present, but it came after the practical explanation rather than replacing it.

I also brought the entry questions to the beginning of the experience. Each program made it clear who it was for, whether participants needed an existing idea, and what they needed to know before starting. This made the decision to register more straightforward and reduced the need to search elsewhere for basic answers.

The outputs of the programs were also brought forward in the experience. Prototypes, projects, and previous participant work became part of how the programs were presented rather than something hidden at the end. The methodology explained how the journey worked, while the outputs showed where that journey could lead.

At the broader digital-system level, I brought program pages, registration, communications, reports, and presentations into a more consistent structure and visual language. Instead of rebuilding the experience from scratch for every new cycle, each version could build on an established system and adapt as the programs evolved.

The work also extended to interfaces, reports, presentations, and communication materials for programs that continued over several years, maintaining consistency across different cohorts while allowing the content and program structure to develop.