Skip to main content

This is how to successfully approach a digital project

 

In this publication with templates, we help you set up a digital project within the cultural sector. All the steps are covered. We explain what a digital project is, the phases it consists of, and what is needed to make a digital project successful. In short: we guide you through the entire process, from start to finish (and beyond!).

38 minutes1 sep `25

What is a digital project?

To set up a digital project, you first need to know what we mean by a digital project. The answer is actually quite simple. As soon as the 'end product' of your project contains an element that is digital, it is already a digital project. This ranges from basic digital facilities, such as a website or CRM system, to innovative applications like a digital exhibition or app.

In this 'longread,' we cover all the steps for a digital project within the basic services. By this, we mean the recurring, structural services that are part of the core of your organization, such as implementing existing internal systems or updating existing digital tools.

This means that a digital project can include a new software system, online document management, a collaborative environment, a new (corporate) website, or an administrative system (scheduling system, accounting system, etc.).

For a digital project as part of your basic services, you can clearly define in advance the outcome you aim for and the impact the project will have on the organization.

voorbereiding, uitvoering en vervolg: de drie hoofdfases van een digitaal project

Setting up a digital project for your basic services

To properly approach a digital project, you must go through three standard phases: preparation, execution, and follow-up.

The preparation phase includes clearly articulating the 'why' and setting up a project canvas. You can see this as a compact visual representation of a project, where you quickly and clearly structure key elements. This is useful for brainstorming, discussing, and planning your digital project. A project canvas can help you think through the questions you need to answer before starting your digital project.

1. Preparation

De fases van voorbereiding: project canvas, user stories, MoSCoW, Verandermanagement, briefing en techpartij

Jump directly to Execution and Live

a. The project canvas as an instrument for a digital project

Such a project canvas is a tool and a precursor to the briefing you eventually communicate to a technical partner. It's a kind of preliminary research. In a project canvas, you answer questions like: why do you want this digital project, what problems will you solve with the digital project, and for whom is the digital project intended? With DEN's project canvas template and step-by-step plan, you can systematically map out these questions and their answers. This gives you a clear starting point for a digital project.

In the article 'Project canvas: a good start for your digital project' we delve deeper into the theory behind the project canvas.

b. How can user stories help me further?

In a project canvas, you often work with user stories. A user story is literally a user's story. It is a short description of a user's need in the form of a brief narrative. User stories help you identify in advance what exactly you are solving for whom and why with your digital project. Use our template for user stories within a digital project.

In the article 'User stories explained: who are the users of a digital project?' we further explore the theory surrounding user stories.

c. How do I determine what is important in my digital project?

The MoSCoW Method

While creating your project canvas and working with user stories, you will need to prioritize: what is important and what is not? To prioritize well within a digital project, you need to list: which elements are nice to have but not essential? What is desirable but currently at the bottom of the priority list? And what are we consciously leaving out for now?

There is a simple method to distinguish all these things: the MoSCoW method. With this, you distinguish Must have (mandatory), Should have (really should), Could have (nice but not necessarily now), and Won’t have (we'll leave it for now). Here's the difference between these four.

Must have

The Must-have list contains the elements that are crucial to starting the project. For example, hardware or privacy-preserving software.

Should have

The wish list includes items you want to deliver in the (medium) long term. These items are not yet necessary for the first phase of the project (in the short term). For example, using a Large Language Model trained only with proprietary data.

Could have

A Could-have list essentially says: this is nice to have, but perhaps for later. For example, a new CRM system that can 'communicate' with the CMS.

Won’t have

That's clear: not needed (for now). By distinguishing these four, you have a clear view of priorities and know what must and what may. This list also helps in a concrete conversation later with your future technical partner.

d. Change management: how do you involve users in a digital project?

One way to make change easier and more successful is the Prosci method*, a well-known change management method. We guide you step by step through the Prosci method for change management.

Adoptie met of zonder hulp
— 16% of employees adopt new initiatives and practices without assistance

Implementing a new system requires quite a bit of effort. You can create it, but it also needs to be used. How do you ensure that? And how do you reduce or prevent resistance in a digital project? Change management can help. Change management is the point where you actively involve everyone affected by the digital process. We guide you step by step through the Prosci method for change management so your digital project is well-received by all your users.

*Prosci is a globally leading methodology for change management, focused on the human side of change. It uses the well-known ADKAR model (Awareness, Desire, Knowledge, Ability, Reinforcement) to guide individuals and organizations through transformations. 

In the article Implementing digital projects: dealing with change we explain what change management entails and how you can practically get started with the Prosci method and the ADKAR model.

e. How do you write a good briefing?

For virtually all digital projects, you need an external party. A project canvas is usually too concise for a discussion – it is more of a strategic summary. Therefore, it is important to prepare a clear briefing before you start looking for a tech partner. In it, you specify your expectations, estimate the budget, mention a rough deadline, and indicate who should be involved internally.

In this article 'How to write a good briefing for your digital project' we explain what a good briefing should include.

f. How do I choose the right technical partner for my digital project?

Which technical agency would fit your digital project? Ask yourself the following questions during orientation: is this company familiar with your sector, and have they developed a similar product before? Does their way of working fit your organization? Is their project setup approach also suitable for you? Does a large or small agency suit you better?

You can of course work with an agency you already know, but meeting new contenders or organizing a pitch is also an option.

How to best choose a suitable technical partner for a digital project can be read in the article 'How to choose a tech partner for your digital project'.

You've chosen your tech partner, now what?

You have your agency. Now what? Often, you first decide whether to go for an existing or new solution. The first step is deciding whether to choose an existing solution (possibly with adjustments) or a new product; usually, you'll find that the working method is determined by the agency you collaborate with.

They have experience building the product and can determine whether it works well in the context in which you want to use it. Together with your tech partner, you ultimately decide on the final working methods, budget, planning, and project team.

  • The phases of an existing solution

If you choose an existing solution available in the market, you can often first agree on a pilot with your technical supplier. This is a kind of trial period. You don't have to immediately purchase the solution or acquire a long-term license, but you use the software for, say, three months to try it out. After that, you can often tweak and customize it to achieve the optimal result.

  • The phases of a new digital product

Are you building a new digital product? Then you almost always go through four phases: exploration, development, testing, and implementation. But wait, there's a fifth! Adjusting and updating. This is sometimes forgotten but is an integral part of your digital product.

For each phase, it is important to plan measurement points and decision moments. You can document this in a work plan or roadmap. 

2. Execution

Fases van uitvoering: uitvoeringsfases, werkmethode, budget, planning, projectteam, productieproces, implementatie

Jump directly to phase: live

You've chosen the right technical partner, sharpened the briefing, and completed the preparation — time to really get started. In the execution phase, everything comes together: plans become tangible steps, ideas are built, and your collaboration takes shape. Together with your tech partner, you define not only what is being built but also how you will work, with which team, within what budget, and in what timeframe. In the upcoming sections, we guide you step by step through this process, so you make clear choices and maintain control over what happens along the way.

a. What are the phases of executing a digital project?

Exploration

Hide explanationShow explanation

In the exploration phase, you gather information, map out the target audience and requirements, try to refine the problem definition, and explore possible solutions. Much of this has already been done in the project canvas and the briefing, so exploring possible solutions is particularly relevant.

You do this through, for example, research, interviews, brainstorming, and analyzing existing solutions.

Development

Hide explanationShow explanation

During this phase, concepts are elaborated, and initial versions are built. Together with the tech partner, you look at functionalities and structure. You do this by, for example, creating wireframes, setting up technical designs, and building prototypes.

Testing

Hide explanationShow explanation

During the testing phase, you gather feedback from your future users. You identify problems and improvement points and validate assumptions. You do this through, for example, user tests, A/B tests, feedback sessions, and technical tests.

Implementation

Hide explanationShow explanation

During this phase, you actually start using the product. People are trained to use it. Note: this may seem like the final phase, but in practice, you will often still deal with tweaks (adjustments) and bugs ('errors'). You do this by, for example, launching the software, providing manuals and training, carrying out iterations and interventions, and offering support.

Adjusting and updating

Hide explanationShow explanation

When you're done, you're not done. You will always find that some things need to be changed because, for example, needs change or technology evolves. Built systems also need to be regularly updated, set up for even better functionalities, and maintained. Include this in your budget.

b. Determine your working method

As you progress with your digital project, you need to determine how you want to work. There are various project methodologies for your digital project. You can work with the waterfall method, agile/scrum, or a hybrid approach.

What are the different project methodologies (and what is scrum)?

Waterfall

Hide explanationShow explanation

In the Waterfall method, several phases are completed one by one (linearly). That is, step by step, in one direction. Hence the name Waterfall method; because a waterfall flows downward. This means that each phase thoroughly and exhaustively inventories and elaborates all requirements. Only then can you move on to the next step. This also means that the product is only available at the end when it is completely finished, and never partial products.

In a static world, this works excellently. The Waterfall method is therefore best used in environments that change little or not at all: you determine your goal very well at the start and then work towards it very specifically and efficiently. But often, this is not how it works in (digital) practice.

With the Waterfall method, you have to make targeted estimates at the start of the project. In a changing environment, this method carries the risk that the original scope no longer aligns; market, customers, wishes, etc., can change while you were developing.

Iterative / agile

Hide explanationShow explanation

Put simply, while working on a digital project, you'll often find that things need to be adjusted. This fits with 'iterative working': continuously checking if something needs to be different or better.

Iterative, or agile (in English) working, arose from the need to respond better and faster to the changing market and changing needs and wishes. Agile literally means agility, flexibility. When working from the agile methodology, you are aware that circumstances change. The methodology allows for this and encourages testing partial solutions. No large master plan that is executed step by step, but smaller projects that build towards a big goal, with only the outlines agreed upon at the start. In iterative/agile, you often work in small 'sprints' or rounds; this is called the scrum method.

In agile working, several things are central:

  • The world around us changes, so environmental factors that affect our product also change
  • The wishes of stakeholders will change during the project's duration
  • To respond well to changes, you continuously check if the work for the coming period is still the most valuable work
  • To check frequently, you also release (partial) products more often
  • During development, testing occurs, and new insights are immediately incorporated.

Hybrid

Hide explanationShow explanation

Hybrid is a combination of more traditional forms like Waterfall combined with agile: both a fixed linear process and 'moving parts' and short spurts.

In our experience, a hybrid work method works well for most digital projects in the cultural sector. Some things can indeed be predicted and provide a framework, while other parts prioritize flexibility and incorporating new insights. This way, you can remain 'agile' during the project while also working realistically within the organizational structures often present in cultural organizations.

Source: Agile VS Waterfall

What is scrum

Hide explanationShow explanation

Within agile and hybrid work, the scrum method is often used.

Simply put, scrum is:

  • Create a list of what needs to be built
  • Decide what to do this period (the sprint)
  • Meet daily and collaborate
  • Show what you've created at the end
  • Think about how to improve in the next scrum round
  • And start again at point 1
     

Source: Agile VS Waterfall

What if my external supplier wants agile/scrum, but my organization is used to traditional planning?

Discuss with your supplier the possibilities and limitations for your organization. Get informed about the expectations the supplier has of you in an agile/scrum process. Experience shows that a mixed approach often works very well, so Waterfall within your organization and scrum at the design company can work fine as long as the process is discussed beforehand and expectations are clear on both sides. Make sure to document this to avoid misunderstandings.

c. How do I determine the budget for my digital project?

The next step is determining the final budget. How much does a digital project cost? Often, it helps to approach a digital project by reversing the question to ensure it doesn't become endlessly large and complex. The question then becomes: how big is this digital project for your organization, how much budget éand time from the team can you allocate for it? With this question in hand, it becomes much easier to arrive at a budget because it makes the question more concrete and starts from the available resources.

Step-by-step plan to determine your budget

What is essential and what is optional for your digital project?

Hide explanationShow explanation

We already discussed the MoScoW method: Must have, Should have, Could have, Won’t have (for now). While drafting your budget for the project, the Must haves (essential) and Should haves (should have) are, of course, leading. These are placed at the top. The Could haves (nice, but not essential) depend on both budget and priority. The Won’t haves are something that currently has no priority and is left aside. These are important ingredients to determine what must be included in your digital project (MVP: minimal viable product). But what else needs to be determined?

What should you (and your external agency) discuss for the required budget?

Hide explanationShow explanation

The budget determination then depends on the following important factors.

  • Core functionalities
  • Design needs
  • Platforms
  • Integrations (system connections)
  • Is content creation needed? (and who does it: internally or externally?)
  • Development and maintenance

Additionally, there are some questions to discuss with your technical partner/external agency:

  • Are we working with a fixed price? Or do we determine it per step?
  • Which roles need to be fulfilled (explained in the chapter: Assemble your project team), what are the required hours, and what are the costs? (note: internal hours must also be calculated, and external hours are often expensive)
  • Are we going for custom work (and to what extent) or not?
  • Are there licenses that need to be paid?
  • What are the costs for hosting, support, updates, and development after launch? (and other long-term costs?)

NOTE: there are always unforeseen costs. These usually range between 10% and 30%. A realistic estimate is usually 20% on top of the total budget.

How much budget for maintenance and development?

Hide explanationShow explanation

In addition to the budget for developing your digital project, it is also important to allocate a budget for maintenance and further development. This is sometimes overlooked – projects are often seen as end products, while they are only partly so because the world does not stand still. The end product is therefore not the end product.

For successful development of your project, it is important to allocate sufficient time and budget for technical maintenance éand for new insights.

Often, this is higher than you might initially expect; discuss this early with your technical partner.

A good rule of thumb is to reserve at least 20% of the initial budget to spend annually on further development in the following years. For a project budget of, for example, 25,000 euros, this means an annual budget of 5,000 euros. The exact amount strongly depends on which products you have set up and which knowledge you hire and already have in-house. Discussing what your team can do internally and what you need the technical partner for is important, as this greatly influences the budget.

How do you finalize the budget for your digital project, is there a formula for it?

Hide explanationShow explanation

The calculation you ultimately get based on all input:

Hours per role x hourly rate. 
License and/or tool costs
= 
Budget

+
Risk/buffer (20% of budget) 
Further development and maintenance (20% of budget)
=
Total budget for developing a digital project

NOTE: further development and maintenance are calculated with this formula for one year. Each year, the 20% of the initially calculated budget amount is added again!
 

d. Planning

What does a planning look like? In a digital project, there are three components of planning that influence each other:

  1. Time (the amount of time available/can be allocated)
  2. Scope (what you create)
  3. Resources (technology, people)

This is called the scope triangle.

If you change one of the three, it almost always impacts the other two. In an ideal world, time, scope, and resources are always in balance. In practice, one or two of these often take precedence. So keep in mind that there are one or two of these key factors in your project that influence your planning.

How to create a planning is explained in the article 'Creating a digital project plan' with a handy template included.

e. Assemble your project team

How do you assemble a project team for your digital project? In digital projects, there is almost always a project team that operates both inside and outside the organization. We explain how to determine who you need inside and outside the organization. In any case, the roles of product owner, UX/UI designer, developer, content specialist, and tester must always be represented.

What roles are there within a digital project?

Product owner

Hide explanationShow explanation

Determines the direction and priorities within the project and monitors the goals and content. Internal or external: preferably internal, sometimes both.

Scrum master

Hide explanationShow explanation

Ensures in agile projects that the process runs smoothly and removes any obstacles during the process. Internal or external: can be both, but is usually external, depending on the agreements made.

UX/UI designer

Hide explanationShow explanation

Designs the digital product and is responsible for the visual design. Internal or external: usually external.

Developer

Hide explanationShow explanation

Builds the technical solution. Internal or external: external.

Content specialist

Hide explanationShow explanation

Provides text and images (sometimes these roles are divided, or there is a coordinator who manages this). Internal or external: usually internal, in any case, must be internally verified.

Tester(s)

Hide explanationShow explanation

Checks the functionalities, quality, and user-friendliness of the digital product. Internal or external: both, often in small internal teams.

TIP: We have compiled some roles in an agile digital project in an article for you. If you collaborate with a technical partner, it is useful to know these terms in advance.

3. Live

Fases na livegang van een digitaal project: supportgroep, feedback, doorontwikkeling, digitale transformatie & strategie, impact meten

Your digital project has been built, tested, and users can start working with it. What’s the first thing you do after launching your digital project? Celebrate successes! Take a moment to recognize what has been achieved and what positive changes are coming.

There is now a beautiful new system that will help you further in the process of digital transformation. It is important not to see the end of the execution period as the final destination. Therefore, there are a few steps you can (and should) take.

Properly organize your organization to manage and optimize systems. Technical management, an innovation working group, and knowledge building are important.

a. Set up a support system for users

Once your digital project is live, it's important that colleagues know where to go with questions. Not only for technical support but also about the new way of working. Provide a clear contact point or team that answers such questions. Think of: internal colleagues for answering functional questions and an external helpdesk for technical questions. The most important thing is that people know whom to approach with which question. IT systems can support this but are merely a tool; the core is a clear organizational structure for support.

TIP: post a list of FAQs (frequently asked questions) online, providing answers to common questions éand clearly indicating whom to contact with which question if they get stuck.

b. Collect user feedback after going live

There are various ways to collect user feedback. Look primarily at what suits your organization and consider the size of the group you want feedback from.

A small group?

The smaller the group, the better it is to do this orally in a meeting. Prepare your questions in advance. To ensure everyone gets their turn, you can use a tool like Mentimeter (www.mentimeter.com).

A large group?

Is the group large? You can then use an online survey and/or deploy key users or ambassadors: these are delegated colleagues who gather feedback from others.

c. Further development, management, and optimization 

A digital project is never truly finished. Not only must you technically maintain a project (comparison: your phone also regularly needs updates), but you also need to leave room for further development. Needs and possibilities will change over time.

What three aspects should you monitor for management and optimization?

I. Technical management

Hide explanationShow explanation

Technical management is about the daily functioning of your digital product. Things like monitoring, safeguarding performance, security updates, and fixing bugs. Good technical management ensures your digital product remains stable, secure, and reliable. It is a necessary part of ongoing progress. Technical management can be handled internally if the right knowledge is present. Alternatively, you can outsource it to the supplier, in which case you make good long-term agreements. Either way, you will always need to manage, technically maintain, and want to adjust the system.

II. Innovation working group

Hide explanationShow explanation

An innovation working group focuses on future developments. It identifies opportunities, collects ideas, and examines whether new functionalities are interesting. This group also experiments to see if technological developments can contribute to changing user needs. An innovation working group can be internal, external, or a hybrid of both, with the latter being the most successful.

III. Knowledge building

Hide explanationShow explanation

Knowledge building ensures that information about the product is sustainably documented and shared, so it doesn’t become fragmented. Think of documentation, training materials, best practices, and lessons learned. This prevents crucial knowledge from being held by only a few individuals and makes teams more agile and onboarding easier. This knowledge is built both externally and internally, but ensure it is also shared and stored internally.

d. A digital project as part of digital transformation and digital strategy

Your digital project is now live — great job! But of course, this is not the end of your cultural organization’s digital journey. Digital projects contribute to a larger, ongoing process: digital transformation. Digital transformation is a change process in which you continually make choices, learn, and adjust.

Digital transformation means having a vision in which digital projects fit into a broader digital strategy. A good digital strategy has concrete goals that contribute to changes valuable to both the audience and the organization. With a good digital strategy, your cultural organization becomes resilient and future-proof in an ever-changing digital landscape.
 

Want to learn more about digital transformation? In an overview, we tell you everything about digital transformation in culture.

e. How do I measure the impact of my digital project?

It’s logical to wonder about the impact of digital activities; how they contribute to societal, educational, or artistic goals. This too is part of your digital strategy. You define the impact goals for your project or organization in advance.

Then, you determine which (digital) activities contribute to those goals. You measure this impact by testing your assumptions after implementing the new systems. Collect data about your audience, both qualitative and quantitative. For example, age categories and people’s feedback about their experience. This way, you gain insight into what truly works in practice. Based on these insights, you can substantiate strategic choices, make adjustments, and allocate resources more effectively in the future.

Note! Consider this longread as an MVP (a first, working version): very usable, but not yet ‘finished’. We will continue to develop this material and would love to hear your feedback via communicatie@den.nl.

Share this news article

Start your digital project

Want to get started with your digital project? Download all templates that will help you set up a digital project.

This article provides a complete overview of the approach to a digital project with the following phases:

Preparation
a. Project canvas
b. User stories
c. MoSCoW
d. Change management
e. Briefing
f. Tech partner

Execution
a. Execution phase
b. Work method
c. Budget
d. Planning
e. Project team
f. Production process
g. Implementation

Live
a. Support group
b. Feedback
c. Further development
d. Digital transformation and strategy
e. Measuring impact

Note! Consider this longread as an MVP (a first, working version): very usable, but not yet ‘finished’. We will continue to develop this material and would love to hear your feedback via communicatie@den.nl.

Discover the latest digital trends in the cultural sector

Receive our newsletter with tips, knowledge, and inspiration about digital transformation in culture.

This field is required
This field is required
This field is required