Every engagement Digital Missions takes on is a mission.
Each mission has a defined partner, scope, team, timeline, and objective. The work of the company is the running of missions.
From recce to handover.
Five stages, run in sequence, every time. The recce is the gate. Skipping it is how most digital projects in West Africa fail.
A senior recce mission engineer enters the operating environment, embeds lightly with the partner, and produces a recce report.
The recce report informs the mission brief, which scopes the work, the team, the timeline, and the capability transfer plan.
A mission lead and mission engineers are committed and embedded inside the partner institution.
The team builds the systems, transfers capability to local engineers, and operates from the regional base.
The mission report closes the engagement, documents what was delivered, and feeds the annual transparency report.
The recce is what most projects skip. We do not.
Before any commitment, a senior recce mission engineer maps the operating environment, identifies the people who will make or break the work, and surfaces the risks not in the official scope. The recce report decides whether the full mission proceeds and how it is designed.
The language we use is deliberate.
Eleven core terms, plus the team model. Eighty percent local, twenty percent global. Mission teams embed inside ministries from a regional base.
- Mission
- Every engagement Digital Missions takes on is a mission. Each mission has a defined partner, scope, team, timeline, and objective. The work of the company is the running of missions.
- Partner
- The ministry, donor, multilateral, or government entity Digital Missions is working with on a given mission. We use partner rather than client because the work is collaborative, long term, and built on shared accountability rather than a transactional relationship.
- Recce
- The discovery and assessment phase that begins every mission. A recce maps the operating environment, identifies the people and politics that will shape the work, surfaces risks not in the official scope, and produces the recce report. Skipping the recce is how most digital projects in West Africa fail. We do not skip it.
- Recce mission engineer
- The senior specialist who runs the recce phase. Recce mission engineers are experienced operators who can read both the technical and institutional conditions of an engagement. The recce report they produce decides whether the full mission proceeds and how it is designed.
- Recce report
- The output of the recce phase. The document that scopes the full mission, names the risks, identifies the partner counterparts, and recommends the design.
- Mission brief
- The document that defines a confirmed mission. Scope, objective, team, timeline, conditions of success, capability transfer plan, technology choices, and any commitments made under our red lines. The mission brief is the operational contract between Digital Missions and the partner.
- Mission lead
- The senior person accountable for delivering a mission. The mission lead owns the relationship with the partner, the performance of the mission team, and the final mission report.
- Mission engineer
- The technical staff who build the systems during the implementation phase of a mission. Mission engineers report to the mission lead and work alongside counterparts inside the partner institution.
- Mission team
- The full set of people working on a given mission, led by the mission lead and supported by mission engineers and other specialists as the mission requires.
- Mission report
- The document that closes a mission. It captures what was delivered, what was learned, the state of capability transfer at handover, and what should happen next. Mission reports inform our annual transparency report.
- Base
- The physical location where mission teams are housed and supported. Each base supports the missions in its region. Bases are not headquarters and field offices. The base exists to support the missions, not the other way around. Our first bases are in West Africa.
The team model
Local teams are not a marketing claim. They are the only way to do this work well, because the contextual, linguistic, and political knowledge required cannot be flown in. The other twenty percent provide global technical support and connective tissue across countries.
Mission teams operate from regional bases. The base exists to support the missions, not the other way around. Our first bases are in West Africa, with new bases opened as we expand into other regions of the continent.