Prioritizing Flexibility

Empowered Freedom

Every custom software initiative is different. If it’s all been done already, just buy a solution off the shelf. If it deserves the investment of custom software, it will be solving unprecedented challenges. Cookie-cutter approaches to architecture, team makeup, or delivery methods can contribute to a lower-than-hoped-for return on investment. Instead, having the whole team explore options allows an optimal solution to emerge.

In order to be flexible in the right directions, the team needs vision so that they can focus on what will truly deliver on that vision, rather than getting lost in pet projects (e.g. the new shiny technology or approach). When the whole team shares the vision, it’s safe to give the autonomy to choose the right solution. If the team is well-staffed, with all of the skills necessary to deliver (from architecture to design to business strategy), putting company standards in the way will only slow them down. Teams can still responsibly adhere to company preferences where they don’t interfere with their mission.

Often, the sponsors and stakeholders of the team will kick everything off with a vision of a solution. What can be hard to accept is that most solutions fail. Rather than bringing together a team to implement a solution, provide them with a mandate to solve customer problems. Focus on learning from the customers so that the result is something that truly addresses the team’s mission, not just delivering something which might not be what customers will use in practice.

Follow the customers, not an outdated plan. Build in the flexibility to follow the user research results. It can feel responsible to create an up-front plan, but, remember, if you knew what to do already, you wouldn’t be building custom software. Foster flexibility in the team, leaving space to pivot, reprioritize, and meet the customer where they are. Unbeatable results are found through autonomous teams discovering optimal approaches together.