Skip to main content

How to Successfully Tackle a Digital Project

 

In this publication with templates, we help you set up a digital project within the cultural sector. All 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 understand what we mean by a digital project. The answer is actually quite simple. As soon as the 'end product' of your project includes a digital element, it is considered 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 'long read,' we cover all the steps involved in a digital project within 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 a digital project could be, for example, a new software system, online document management, a collaboration platform, a new (corporate) website, or an administrative system (planning system, accounting system, etc.).

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

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

Setting Up a Digital Project for Your Basic Services

To successfully tackle a digital project, you need to go through three standard phases: preparation, execution, and follow-up.

Preparation involves clearly articulating the "why" and setting up a project canvas. Think of this as a compact visual representation of a project, where you structure key elements quickly and clearly. 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

Go directly to Execution and Live

a. The Project Canvas as a Tool 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 are you solving with it, and who is the digital project intended for? Using 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 dive deeper into the theory behind the project canvas.

b. How Can User Stories Help Me?

In a project canvas, you often work with user stories. A user story is literally: a user’s story. It’s a short description of a user’s need in the form of a brief narrative. User stories help you identify what you’re 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 delve deeper into the theory surrounding user stories.

c. How Do I Determine What’s Important in My Digital Project?

The MoSCoW Method

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

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

Must-have

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

Should-have

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

Could-have

A Could-have list essentially says: it’s nice to have, but maybe something for later. For example, a new CRM system that can ‘talk’ to the CMS.

Won’t-have

This one is clear: (currently) not needed. By distinguishing these four categories, you have clear priorities and know what’s essential and what’s optional. 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 methodology. 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 ways of working without assistance

Implementing a new system takes quite some effort. You can build it, but it also needs to be used. How do you ensure this? 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 trajectory. 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 Digital Projects Implementation: Managing Change, we explain what change management entails and how to practically apply the Prosci method and ADKAR model.

e. How Do You Write a Good Briefing?

For almost all digital projects, you need an external party. A project canvas is usually too brief for a discussion—it’s more of a strategic summary. Therefore, it’s important to create a clear briefing before searching for a tech partner. In it, you specify what you expect, estimate the budget, outline a rough deadline, and indicate who internally needs to be involved.

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 suit 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 align with your organization? Is their approach to setting up projects also suitable for you? Would a large or small agency be a better fit?

You can, of course, work with an agency you already know, but you could also get to know new contenders or organize a pitch.

How to choose the most suitable technical partner for a digital project is explained in the article 'How to Choose a Tech Partner for Your Digital Project'.

You’ve Chosen Your Tech Partner, Now What?

You’ve selected your agency. Now what? Often, you first decide whether to go for an existing solution or a new product. The first step is deciding if you’ll opt for an existing solution (possibly with modifications) or a new product; usually, the working method will be determined by the agency you’re collaborating with.

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

  • The Phases of an Existing Solution

If you choose an existing solution in the market, you can often first agree on a pilot with your technical supplier. This is like a trial period. You don’t have to buy the solution immediately or purchase a long-term license, but you use the software for, say, three months to test it. Afterward, you can often tweak and customize (adjust) 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: exploring, developing, testing, and implementing. But there’s a fifth! Adapting and updating. This is sometimes forgotten but is an integral part of your digital product.

For each phase, it’s important to schedule 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

Go directly to phase: live

You’ve chosen the right technical partner, sharpened the briefing, and completed the preparation—it’s 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’ll work, with which team, what budget, and within what timeframe. In the following sections, we guide you step-by-step through this process so you can make clear choices and maintain control over what happens along the way.

a. What Are the Phases of Executing a Digital Project?

Exploring

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 briefing, so exploring possible solutions is particularly relevant.

You do this through activities like research, interviews, brainstorming, and analyzing existing solutions.

Developing

Hide explanationShow explanation

During this phase, concepts are developed and initial versions are built. Together with the tech partner, you look at functionalities and structure. Activities include creating wireframes, drafting technical designs, and building prototypes.

Testing

Hide explanationShow explanation

During the test phase, you gather feedback from your future users. You identify problems and areas for improvement and validate assumptions. Activities include user tests, A/B tests, feedback sessions, and technical tests.

Implementation

Hide explanationShow explanation

During this phase, the product is actually put into use. People are trained to use it. Note: this seems like the final phase, but afterward, you’ll often need to deal with tweaks and bugs. Activities include launching the software, providing manuals and training, performing iterations and interventions, and offering support.

Adapting and Updating

Hide explanationShow explanation

When you’re finished, you’re not really finished. You’ll always find that things need to be adjusted because needs change or technology evolves. Built systems also need regular updates, better functionalities, and maintenance. Include this in your budget.

b. Determine Your Work Method

As you move forward with your digital project, you’ll need to decide how you want to work. There are various project methodologies for your digital project. You can work with the waterfall method, agile/scrum, or hybrid.

What Are the Different Project Methodologies (and What Is Scrum)?

Waterfall

Hide explanationShow explanation

With the Waterfall method, several phases are completed one by one (linearly). That means step by step, in one direction. Hence the name Waterfall method; because a waterfall flows downward. This means each phase thoroughly and exhaustively inventories and develops all requirements before moving to the next step. This also means the product is only available at the end when it is completely finished, and never as partial products.

In a static world, this works excellently. The Waterfall method is best used in environments that change little or not at all: you determine your goal very well at the beginning and then work toward it very focused and efficiently. But often, it doesn’t work that way in (digital) practice.

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

Iterative / Agile

Hide explanationShow explanation

Simply put, during the work on a digital project, you often realize that things need to be done differently. This is where ‘iterative working’ comes in: constantly checking if something needs to be adjusted or improved.

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. If you work from the agile methodology, you’re aware that circumstances change. The methodology allows for this and even encourages testing partial solutions. No large master plan that is implemented step by step, but smaller projects that build toward a big goal, of which only the outlines were agreed upon at the beginning. In iterative/agile, you often work in small ‘sprints’ or rounds; this is called the scrum method.

Central to agile working are:

  • The world around us changes, so external factors that affect our product also change
  • Stakeholders’ wishes will change during the project’s duration
  • To respond well to changes, you constantly check if the work you’re doing for the upcoming period is still the most valuable work
  • To frequently test, you also release (partial) products more often
  • During development, testing, validating, and incorporating new insights happen continuously.

Hybrid

Hide explanationShow explanation

Hybrid is a combination of more traditional methods like waterfall combined with agile: both a fixed linear process and ‘moving parts’ and short spurts.

In our experience, for most digital projects in the cultural sector, a hybrid work method works well. Some things can be predicted and provide structure, while other parts focus on flexibility and incorporating new insights. This way, you can remain ‘agile’ during the project while 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 working, the scrum method is often used.

Simply put, scrum is:

  • Make a list of what needs to be built
  • Decide what you’ll do this period (the sprint)
  • Meet daily and collaborate
  • Show what you’ve made at the end
  • Think about how it can be improved 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 what the possibilities and limitations are for your organization. Get informed about the expectations the supplier has for you in an agile/scrum trajectory. Experience shows that a mixed form often works well, so waterfall in your organization and scrum at the design company can work fine, as long as the process is well discussed beforehand and expectations are clear. Make sure to document this to avoid misunderstandings.

Your Digital Project: Start Small, Achieve Big Results

Have a good idea for a digital project but aren’t sure if it will resonate with your audience? You don’t have to build everything immediately to find out.

During this free online Lunch & Learn, discover why starting small and testing leads to better digital products. Get practical tools that you can use right away within your own organization.

Sign Up!

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 reverse the question and ensure your request doesn’t become endlessly large and complex. Then the question becomes: how big is this digital project for your organization, how much budget and team time can you allocate to 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 Guide to Determine Your Budget

What Is Essential and What Is Optional for Your Digital Project?

Hide explanationShow explanation

The MoSCoW method was discussed earlier: Must-have, Should-have, Could-have, Won’t-have (for now). When setting your project budget, the Must-haves (essential) and Should-haves (should have) are naturally leading. These are placed at the top. The Could-haves (nice but not necessary) depend on both budget and priority. The Won’t-haves are things that are not a priority now and are 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 Discuss with Your External Agency Regarding the Required Budget?

Hide explanationShow explanation

The budget determination depends on the following key factors:

  • Core functionalities
  • Design needs
  • Platforms
  • Integrations (system linkages)
  • 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 is it determined per step?
  • Which roles need to be fulfilled (explained in the chapter: Assemble Your Project Team), what are the required hours, and what are their costs? (note: internal hours should also be calculated, and external hours are often expensive)
  • Are we opting for custom solutions (and to what extent) or not?
  • Are licenses required that need to be paid for?
  • How much do hosting, support, updates, and development after launch cost? (and other long-term costs?)

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

How Much Budget for Maintenance and Development?

Hide explanationShow explanation

Aside from the budget for developing your digital project, it’s also important to allocate budget for maintenance and development. This is often overlooked—projects are sometimes seen as end products, whereas they are only partially so, as the world doesn’t stand still. The end product is therefore not the end product.

For successful development of your project, it’s important to assign sufficient time and budget for technical maintenance and new insights.

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

A good rule of thumb is to reserve at least 20% of the initial budget for subsequent years (per year!). 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 the products you’ve set up and the expertise you hire or already have in-house. It’s especially important to discuss what your team can do itself and what you need the technical partner for; this has a significant impact on the budget.

How Do You Finalize Your Digital Project Budget? Is There a Formula?

Hide explanationShow explanation

The calculation you ultimately arrive at based on all input:

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

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

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

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’re creating)
  3. Resources (technology, people)

This is known as the scope triangle.

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

Learn how to create a planning in the article 'Creating a Digital Project Planning Step-by-Step', which also includes a useful template.

e. Assemble Your Project Team

How do you assemble a project team for your digital project? In digital projects, there’s almost always a project team that exists both within and outside the organization. We explain how to determine who you need internally and externally. At the very least, the roles of product owner, UX/UI designer, developer, content specialist, and tester should always be represented.

What Roles Exist Within a Digital Project?

Product Owner

Hide explanationShow explanation

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

Scrum Master

Hide explanationShow explanation

Ensures that the process runs smoothly in agile projects 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’s a coordinator managing this). Internal or external: usually internal, at least should be reviewed internally.

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’ve compiled some roles in an agile digital project in an article. If you’re working with a technical partner, it’s helpful 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 your digital project goes live? Celebrate successes! Take a moment to reflect on what has been achieved and the positive changes that will occur.

You now have a great new system that will help you further in the process of digital transformation. It’s important not to view the end of the implementation 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 for colleagues to know where they can go with questions. Not just for technical support but also about the new way of working. Provide a clear point of contact or team to answer 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 who to contact with which question. IT systems can support this, but they are merely tools; the core is a clear organizational structure for support.

TIP: Set up an online FAQ (Frequently Asked Questions) list that provides answers to common questions and clearly indicates who to contact if you can’t find the answer.

b. Collect Feedback from Users After Going Live

There are various ways to collect feedback from users. Focus on 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 verbally in a meeting. Prepare your questions in advance. To ensure everyone has a chance to speak, you can use a tool like Mentimeter (www.mentimeter.com).

A Large Group?

If the group is large, you can use an online survey and/or engage key users or ambassadors: these are representative colleagues who gather feedback from

c. Development, Management, and Optimization

A digital project is never truly finished. You need to not only maintain the project technically (comparison: your phone also regularly receives updates) but also make room for further development. Needs and possibilities will change.

Which Three Aspects Should You Monitor for Management and Optimization?

I. Technical Management

Hide explanationShow explanation

Technical management involves the daily functioning of your digital product. Tasks include monitoring, safeguarding performance, updating security, and fixing bugs. Proper technical management ensures your digital product remains stable, secure, and reliable. It’s a necessary component of progress. Technical management can be handled internally if the right expertise is available. Alternatively, it can be outsourced to the supplier, in which case you make long-term agreements. Either way, you will always need to manage, maintain, and adapt the system technically.

II. Innovation Working Group

Hide explanationShow explanation

An innovation working group focuses on future developments. It identifies opportunities, gathers ideas, and assesses whether new functionalities are interesting. This group also experiments to explore whether technological developments can meet changing user needs. An innovation working group can be internal or external, but the most successful form is usually hybrid: a combination of both.

III. Knowledge Building

Hide explanationShow explanation

Knowledge building ensures that information about the product is sustainably documented and shared, preventing fragmentation. Think of documentation, training materials, best practices, and lessons learned. This prevents crucial knowledge from being concentrated in a small group of people and makes teams more agile and onboarding easier. This knowledge is built both externally and internally, but ensure it is shared and preserved internally.

d. A Digital Project as Part of Digital Transformation and Digital Strategy

Your digital project is now live—great work! But this is, of course, 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 where you continuously make choices, learn, and adjust.

Digital transformation means having a vision where digital projects fit into a broader digital strategy. A good digital strategy has concrete goals that contribute to changes valuable to both the public and the organization. With a well-thought-out 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 natural to wonder about the impact of digital activities; how they contribute to social, educational, or artistic goals. This is also part of your digital strategy. You formulate impact goals for your project or organization in advance.

Next, you determine which (digital) activities contribute to these 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 reactions about their experience. This gives you insight into what truly works in practice. Based on these insights, you can make strategic decisions, adjust, and allocate resources more effectively in the future.

Note! Consider this longread as an MVP (a first, working version): very useful, 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 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. Working 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 useful, 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