Skip to content
Fast Company Executive Board

The Fast Company Executive Board is a private, fee-based network of influential leaders, experts, executives, and entrepreneurs who share their insights with our audience.

Why developers should exchange a roadmap for a mud map

Most software road maps are, in fact, mud maps—informal guides that allow for the inherent fluctuations in our businesses, and in our world.

[Images: Adobe Stock / DC Studio]

Profile photo of Anthony Smith

How many businesses had to pivot in March 2020? I would venture to guess the answer is nearly all of them.

If the COVID-19 pandemic taught us anything, it’s that businesses that can adapt quickly are in a better growth and sustainability position than those that struggle with change. 

Adaptability is perhaps the most underrated predictor of success.

WHAT WE LEFT IN THE PAST 

I would not characterize software development projects in the 1980s and 1990s as adaptable. 

The long-form documentation that guided software development projects of the past were slow. In fact, they bear little similarity to the agile development processes many companies run today. Some of us may remember the days of sequestering ourselves and writing hundreds of pages of system requirements and functional requirements to signal the start of a software project. Those documents would be reviewed, discussed, revised, and approved before a single line of code was written. 

In the glacial pace of the ’80s and ’90s, this was just fine. Teams took these documents, went off in a vacuum for six to eight months, and came back with working software that met the requirements…kind of. Many misunderstandings and issues were resolved in the famous and shifty ‘warranty’ period and, at some point, the software was deemed good enough and accepted. 

AGILE IS BETTER, BUT STILL HAS FLAWS

For nearly 20 years now, the software development industry has largely practiced Agile software development as a methodology that threw away slow, rigid models in exchange for iteration and adaptability. This method has evolved slightly over the years, but is largely unchanged because it works. Delivering working software incrementally over time, and adapting to the changing needs and feedback of the users during the development process, is clearly more successful. 

The iterative nature of Agile gave birth to the software road map, which is typically a rough plan for what features will be considered to enhance an application in the coming two to four quarters. 

Some brave souls may go out farther than four quarters in their roadmap, but that gets pretty risky when you consider market changes and technological innovations. For example, with the impact that AI made in Q4 of 2023, most software leaders had to adjust their roadmaps to accommodate AI-related features in the coming quarters. Users and consumers demand that kind of quick turnaround, making multi-year road maps almost comical today.

WHY I’VE PIVOTED

Why do I think we need another shift? Hear me out.

Unless we’ve met in person or you’ve heard me speak on a video or audio recording, you might not know that I am Australian. Australia is known for its rugged outback and ‘no rules’ living. These concepts are why the Australian ‘mud map’ is commonly accepted where I’m from, but may be unknown to others outside the region.

According to Wikipedia, “mud map is an Australian term for an informal map, intended to assist, but with no pretensions to accuracy or completeness. The term originates in such a map drawn in mud or dust with a stick, perhaps in response to a query by a stranger.”

I started introducing the mud map concept to my team as a replacement for the road map, and I feel like it has tremendous applicability in today’s fast-paced software development environment.

When I think of a roadmap, I think of clean, crisp, and pristine lines. Routes on a roadmap are drawn with precision to exact specifications, and they take passengers on a journey with a fixed start and end point. 

With this definition in mind, the software roadmap is a complete and utter misnomer. It is not fixed. It is not predictable. In fact, it inherently fluctuates. 

The truth is that most software road maps are, in fact, mud maps—informal guides that keep us moving in the right general direction, but don’t unnecessarily nail developers and businesses down to strict dates and feature delivery deadlines 3-4 quarters out. Rather, they allow for the inherent fluctuations in our businesses, and in our world. They give our customers a glimpse of what’s to come, but let them know that we are willing to adapt and shift as needed to accommodate change.

I’ve always hesitated to share our roadmap with customers since it implies a contract and communicates expectations. However, I’m happy to talk about our mud map and take them on the wild, unpredictable journey with me. After all, that’s why we love the field of technology. Its inherent chaos is what makes it endearing and challenging to us all.

So, have a look at my mud map any time and g’day, mate!