The 5 reasons why you need a POC at the start of your digital gov project - Skryv
The 5 reasons why you need a POC at the start of your digital gov project

By Anouk De Meester - Marketeer & Business Analyst - 4 months ago

Digital Gov project

The 5 reasons why you need a POC at the start of your digital gov project

The idea of a Proof of Concept (POC) is slowly but surely finding its way to digital government projects. Before you buy or develop a software solution, you test if the project you have in mind is the right answer to your needs. In a limited period of time, you do a dry-run of the project and create a simplified version of the solution. You only focus on the key features, use dummy data, etc.

But why should you consider it? Here are the 5 reasons why you need a POC when initiating a digital government project.

1. Change management

Introducing new software has a big impact on your team, costs, day-to-day work, etc. A POC gives you the chance to involve a mix of people with different responsibilities in the early stage of the project. They can be the ambassadors throughout the project and will help you to make it a success.

2. You’ll have proof

As a result of the POC, you’ll have a working application that shows the potential of digitalisation. It’s tested with the end-users and you can already show the value and impact of the project. It’s proof that will be difficult to argue against. It will help you to convince your head of department, politicians and other stakeholders.

3. Fail fast, learn faster

After the POC, you’ll have a better idea of the constraints and challenges of the project. This is the moment where you can adjust the idea and implementation without any big risks. Should you limit the scope? Did you have the correct IT solution in mind? Adjusting these when the project is up and running will be, as you know, very difficult.

4. Helps you to make your business case

You’ll get a better idea of the priorities and requirements of the solution. During the POC you’ll gather a lot of input to set out the project roadmap and timeline. You’ll get an idea of the feasibility of the project and its costs.

5. Dry-run at a low cost

Avoid spending a lot of money on something that is not viable. If your manager is not completely convinced of the solution, your chances to receive the estimated budget are low. Try to convince him/her to do a dry-run at a low cost. Once you have proof that the solution is viable, you’ll have a leg to stand on during the budget negotiations.

To wrap up: A POC helps you to draw a first project roadmap and cost estimation, reduces the risk of failure of the end-solution and is an important driver for change. All of this reached in a limited period of time and at a low cost.

What do you think?

Is a POC at the start of your project something you would consider? What questions do you have on doing a POC? Send us an email or leave us a message.

Do you need help with testing your idea?

We like to think along during a Think & Try

Related Posts

The head of the department asks you to find a solution for the piling backlog of dossiers. You are excited to get going, but where do you start? Start by finding the root cause of the problem with the 5 whys approach.

3 min read

But why is this still the case? How come that - in the digital age we are living in today - these problems still occur?

4 min read

The call for administrative simplification is everywhere. Governments put it high on their agendas. And for Skryv, it is our purpose. But what does administrative simplification really mean? How to get beyond the buzzword and achieve results?

3 min read