The pressure of navigating the complicated world of software development is certainly something you have experienced before. Building roadmaps, requirements, or user stories often don’t give the business expected outcomes. Misalignment between what the business requires and what the team delivers drives team members nuts. That kills the team's motivation. What if I told you that the military mission command conduct could be the key to inspiring your software teams to reach new heights of efficiency, creativity, and commitment? The key to getting the results that you count from your team?
Mission command centers on a fundamental belief: When armed with a clear mission, your team can decide to move your business forward. Both empowerment and trust are important. When your team members feel that their input is valued and their decisions have an impact, it leads to a surge in motivation. That's the magic of mission command. It is a tool to cultivate team trust and accountability.
Mission command mirrors the principles of agility that so many software teams value: self-organization, quick adaptation, and iterative progress. Of course, mission command doesn't imply a lack of oversight. It's about laying out your mission with crystal clear clarity, supporting your team with the necessary resources, and setting up checkpoints to track progress and offer feedback. It’s about creating space to evaluate team progress and support them when needed.
Let’s see how it works in practice. Considering your own tasks and responsibilities, you should reflect on what is important to you. Based on that, you define your mission by briefly describing the task and purpose. Define how you will measure the success of a mission. Describe additional constraints and unknowns you know when defining the mission. That’s your “What” you need to get done.
Having that mission defined, you go to your team and brief them. The important step to get the alignment is asking ‘How’ they will implement it. It doesn’t have to be in big details. It’s a great moment to identify if the team considered everything in their implementation, their approach and if they are skilled enough to work on your mission. It gives you feedback on how engaged you will be to coach your team once they execute this idea. Sharing an implementation plan is called a back brief. It’s a double check for alignment and mechanism to build trust.
What is the structure of a Mission?
Mission — your ‘What’
- Assumptions - What you know, What you don’t know, Your beliefs and context
- Task + purpose - What is the actual task and why?
- Constraints - What are the boundaries that the owner of the mission can’t cross
- Success metrics - What does success mean for you in a given task? What metrics will you look at?
- Control loops - How will you check in with the mission owner?
What do you get?
The end result? A culture where every team member feels involved, valued, and heard. An understanding between both sides, a clear communication channel. A setup where obstacles are tackled promptly and efficiently.
The beauty of mission command lies in its universality. This method can help you realize the full potential of your software teams, whether you're in charge of a Silicon Valley start-up or a Japanese IT behemoth.
That’s also a great tool for cooperating with external parties. They usually have bigger autonomy in work, so you can leverage from defining clearly what is expected from them and how you will measure their success.
Mission command checklist:
- Define Your Mission Clearly: Be explicit about your team's mission. It should include what you know and what you don’t know. What is the task, and why do you or the organization need it? Constraints should the team consider coming back to you with “How”? Define clear success measures.
- Understand ‘How’ the team wants to deliver: Delegate responsibility and give your team members the autonomy to make decisions. Let them back brief you with details to give feedback ahead. This will boost morale and foster a sense of ownership.
- Ensure Effective Communication: Keep lines of communication open. Share information freely so everyone has the context needed to make informed decisions.
- Provide Necessary Resources: Equip your team with the tools, information, and resources they need to complete their tasks. You will know what they need based on their back brief.
- Foster a Safe Environment: Encourage open discussions, feedback, and disagreements. Your clear mission gives the team ability to feedback to you. They won’t do awesome work if they don’t believe in the work that needs to be done.
- Monitor and Provide Feedback: Regularly review progress and provide constructive feedback. Remember, mission command doesn’t mean a lack of leadership or guidance. It ensures alignment and creates space for feedback.
- Celebrate Successes: Acknowledge achievements, both big and small. This helps boost team morale and drives them to push the boundaries of what they can achieve.
- Stay Patient and Persistent: Changing a team's culture takes time. Be patient, persistent, and consistent in implementing mission command. See what works and what doesn’t.
Tool for communicating business needs
Never forget that technology is ultimately only a tool. How you use it is what counts, after all. And using it wisely, effectively, and in line with your company's strategy is possible with mission command.
You can use mission command to articulate business needs to your software team. That’s a communication bridge between business and technology. Use business metrics to define what success means for you. That will allow them to make better decisions when working on a solution to deliver what is required. They will understand the end goal.
Ready to take the plunge? Embrace mission command and leap toward a more efficient, creative, and fulfilling software development. Software that hits what is required by business when expected and on plan.