How we work
Understand first
A collaboration with Digikwal starts with understanding how your organisation works. Which systems do you use, where do they help, and where do they get in the way?
We look at the whole, make choices together and stay involved when something changes. Not separate solutions that are left to fend for themselves after delivery, but an environment that grows along with how you work.
“Management is the norm. That is how you get oversight, calm and room to look ahead, without having to keep track of everything yourself.”
Digikwal — transparent, effective, predictable.
What we map out
- Domains
- Mailboxes and files
- Users and permissions
- Systems and integrations
- Processes
- Dependencies
An overview of the current environment
How we work
From where you are now to lasting responsibility
Five phases, one route. You move through a single process, not through separate assignments.
-
Understand
How your organisation works, which systems exist and where they pinch.
-
Prepare
Recording choices, arrangements, permissions and security up front.
-
Set up and migrate
Moving over under control and testing together, without bringing the organisation to a halt.
-
Manage
Maintenance, monitoring, incidents and changes arranged structurally.
-
Improve
Developing further when practice changes or something is added.
Through every phase, Digikwal stays the same responsible party within the agreed scope. Questions do not get stuck between suppliers: we watch the coherence and explain what the impact of a choice is.
How Digikwal works
Four principles that apply in every phase
IT often grows step by step, without anyone keeping an overview of the whole.
-
Management as the norm
You are not on your own after delivery. We keep the environment going: maintenance, monitoring, incident handling and further development.
-
A trusted point of contact
You can ask questions without having to understand everything first, and you do not have to keep explaining how your organisation works.
-
Deliberate choices
Software often gets chosen because it solves something quickly. We look at how you work first, so that IT does not become a gamble.
-
Step by step
You do not have to get everything right in one go. The environment may grow along under control: what is needed now first, the rest when it is due.
With IT it is often unclear who is responsible for what: the website belongs to one party, the email to another, and nobody feels responsible for the whole. We look at it from that whole. We work with standard documentation about components, access, backup and recovery, so management can be handed over and does not depend on one person.
Before we replace anything
First look at what can stay
Migration is a means, not a goal. What works and is manageable does not have to go.
Existing choices can sometimes stay, but not when they structurally get in the way of management or security; if those choices cannot be discussed, we cannot take responsibility for the whole. If you keep other suppliers, we agree up front which parts fall within our responsibility and what stays outside it. Projects can be part of the collaboration, but we do not deliver one-off projects without management.
From your current environment to day-to-day use
Set up without bringing the organisation to a halt
-
01
Assess
Map domains, mailboxes, files, users and dependencies.
-
02
Prepare
Agree accounts, permissions, security and the migration plan in advance.
-
03
Migrate
Transfer data in a controlled way and test the new environment together.
-
04
Manage
Arrange user changes, settings and support on an ongoing basis.
The line does not stop at delivery:
- Go-live
- Management and maintenance
- Monitoring and incidents
- Changes
- Further development
Management is mostly about keeping small things from becoming big ones. Much of it happens in the background; when something does change, it helps that there is context and an overview.
A clear scope
What we record up front
The agreed environment
- Systems
- Users
- Processes
- Support
Agreed as standard
- which domains, users and data will be migrated;
- which components and permissions Digikwal manages;
- how change requests are submitted;
- which support and response times apply.
Not automatically included
- unlimited migration or data clean-up;
- management of personal devices or local networks;
- support for systems outside the agreed scope;
- 24/7 availability without an additional SLA.
Digikwal is a Proton partner and uses Proton as its preferred solution when it fits the organisation, the data and the way of working. If Proton does not match a necessary way of working or integration, we discuss that up front. What the organisation needs stays decisive.
Who decides what
You decide. We set up, manage and execute within scope.
You decide
Business choices and priorities, commercial decisions, authorisation where that has been agreed, and policy or choices that fall outside the scope. External suppliers that stay outside the collaboration also remain your choice.
Digikwal is responsible
The IT environment within the agreed scope: setup, management, technical execution, the agreed operational execution, oversight and flagging. We watch the coherence and report what the impact of a change is.
If something goes wrong because of a choice, we look at cause and solution without pointing fingers. That is exactly why we record responsibilities up front, so that recovery and next steps stay predictable.
Your organisation
- Scope
- Arrangements
- Responsibilities
Digikwal
Working together needs clear arrangements.
Working together only becomes pleasant once you know where you stand: who decides what, when you can talk things through, and what to expect when something changes.
That is why we make arrangements up front and stay involved afterwards. Not to lock things down, but to keep the overview when practice changes.