How would Napoleon have approached the 2030 Agenda?
BY Lars Tushuizen | August 25, 2016|Comments 3
For months the trumpets sounded and the drums beat on a new milestone in UN development — a beautiful baby, called Sustainable Development Goals (SDGs), was born. It’s neither a boy nor a girl, it’s gender balanced — a small step for men, but a giant leap for mankind.
So our development problems are solved. We have a “plan”. Which, as we all know, means we are all but there. Or so we would think.
Truth be told — the Millennium Development Goals did address a range of significant development issues and created a common cause that rallied the development world. But there is a thing that bothers me about these sweeping development frameworks. A fundamental thing that few know about and is not even discussed while thinking through implementation of programmes to achieve the SDGs. To address this fundamental notion in development programmes, let’s look back in time.
The Russian Campaign in 1812
During the Russian Campaign in 1812. Napoleon tried to engage the Russian army for a decisive action at the Battle of Maloyaroslavets. His generals were planning their attack (programme) without consulting the logistics officers that needed to aptly plan the logistics and operations support for their plan. His troops exhausted, his operations disarrayed from the start — with few rations and no winter clothing — Napoleon lost and was forced to retreat. His vision was solid but he failed to achieve his objectives and lost 95 per cent of his assets, including his men.
Reflecting on this historical occurrence, let’s add a relative perspective to our action plan with the SDGs. We talk about how we will engage universally with all the people we are to serve, we talk about recruiting the best and the brightest the world has to offer, we talk about using big data and real time data to inform our programmes, and most of all, we talk about impact and results. Don’t get me wrong, the SDGs are a great achievement from a planning, monitoring and evaluation, and reporting perspective. And it will have a great impact if we manage it.
But to achieve these lofty goals, there is very little thinking going on about the need and the resources for business operations to be reformed. Programmes consist for a large part of business operations processes- one way to look at a programme is that it is a collection of procurement of supplies and services, recruitment of the right staff with the right skills, logistics to move people and supplies around to the population that needs it, ICT to support the planning, reporting and collaboration, and increased analysis analysis of ever growing data sets.
If business operations is from Mars, programme is from Venus
There for sure is a fundamental difference between business operations and programme. After all they involve very different skills and expertise. But this does not mean we should approach them as separate areas, where we plan and strategize in a very siloed approach. Especially in an environment where the focus is on integrated programming across agencies and mandates, joint annual planning and advanced collaboration in resource mobilization and implementation. This separation does not have to be. It should not be. We have the instruments to bring operations and programme planning together (as outlined in the Standard Operating Procedures for Delivering as One). Programmes and operations are two sides of the same coin – both are indispensable in delivering development impact. We cannot afford to have separate strategic planning and implementation. They are too closely linked to keep them separate.
There is always more room for improvement
The UN has introduced innovations in business operations through the business operations strategy, which is closely linked to the UNDAF and programme planning. This is a great start and the UNDG outlined quite an ambitious vision for the role of business operations under the SDGs. But what is needed is a change of mindset of both programme and operations staff, both of senior management and our rank and file. Instead of treating business operations to engage once the programme is set and treat them as an external force that needs to deliver services to the programme, business operations needs to be engaged in the projects. What is needed is a change in project development and implementation to ensure business operations as well as programme staff are part of the same team. Some agencies already do this, but there is more room for improvement.
In the end it is like a war, a development war
We think about the attack plan, the maneuvers that will get us to our goal and not to forget, the victory speech we will give to position this development war that ends all development wars (or all development, but that is besides the point). But what war is ever won without ensuring the logistics and operations of the army are developed at par with the strategy so the soldiers of reform and development don’t die from cold at the battlefield?
We all know what happened to Napoleon. He had a plan, but he did not think through the operations and logistics to implement that plan. Based on the epic defeat and learning from his mistakes, how do you think Napoleon would implement the SDGs?
Would we repeat history without learning from key events such as the Russian defeat?
- Natural Language Processing to align national plans in Serbia with Global Goals
- Innovation scaling: It’s not replication. It’s seeing in 3D
- Promise to data: What the SDGs mean for persons with disability in China
- Creating an impact investment culture in Armenia: Our way of doing it
- What Can Ship Identification Systems Tell Us About Development Policy?
- Mounir kleibo On
- Lars Tushuizen On
- Steve O'Malley On
- Philip Dive On
- Yves Sassenrath On