Skip to content
IIBA.org Working as a Business Analyst in GIS: Turning Spatial Data Into Business Value

Working as a Business Analyst in GIS: Turning Spatial Data Into Business Value

Key Takeaways

  • Geographic Information Systems (GIS) enable organizations to generate location intelligence and support decisions across planning, operations, and service delivery
  • Business analysts contribute by framing problems clearly, connecting stakeholder needs, and ensuring spatial insights lead to meaningful outcomes
  • GIS initiatives involve diverse stakeholders, specialized terminology, and interconnected data and process challenges that require careful coordination
  • Requirements often involve visual elements and large datasets, which makes collaboration, prototyping, and clarity especially important
  • Solution evaluation includes validating outputs against real geography and confirming performance in the environments where users operate
  • Strong business analysis fundamentals, combined with curiosity about spatial data, support effective work in GIS initiatives
 

Disclaimer: The views and opinions expressed in this article are those of the author and may not reflect the perspectives of IIBA.

There are many different directions a career in business analysis can take, ranging from highly specialized to more general in scope. For some of us, a particular technology becomes central to our careers. In my case, I’ve worked for over twenty years in the field of Geographic Information Systems (GIS), applying business analysis skills and techniques throughout.

Some of you may be interested in GIS, while others might be exposed to it by way of certain projects. Whatever the source of your interest, GIS represents a broad and highly impactful domain where strong business analysis skills are essential. This article introduces GIS from a business analysis professional’s perspective and describes the kinds of work they can expect when supporting GIS-enabled initiatives.

What Is GIS (and Why Business Analysts Should Care)

GIS, or Geographic Information Systems, refers to technology that uses spatial data, which can be mapped or relates to another geographic feature (such as a city, building, or natural feature like a lake or river). While many of us are familiar with consumer tools like online maps or navigation apps, GIS is far more than just maps.

In practice, GIS functions as an enabling technology. It’s why so many organizations, including retailers, banks, pipeline operators, logistics companies, telecommunications firms, government, and law enforcement, to name a few, have invested in GIS. The key point is that everything has a location, and so all organizations need to understand the spatial aspects of what they do. 

What organizations invest in with GIS is actually a capability that we call location intelligence: insights derived from understanding the spatial dimensions of their data.

Organizations use location intelligence to support decisions such as:

  • Selecting new sites or facilities
  • Planning and optimizing networks or routes
  • Responding to emergencies
  • Managing assets in the field
  • Improving service delivery

For business analysis professionals, GIS matters because these decisions are rarely purely technical. They’re tied to business outcomes, stakeholder needs, operational constraints, and data quality—all areas where practitioners play a critical role.

The Role of the Business Analyst in GIS-Enabled Work

Working with GIS doesn’t require business analysis professionals to become GIS specialists or cartographers. Instead, they add value by helping organizations ask the right questions, make sense of complexity, and translate spatial needs into effective solutions.

The following areas illustrate the kinds of work business analysis professionals can expect on GIS initiatives.

Helping Organizations Ask the Right Spatial Questions

A common early challenge in GIS initiatives is clarifying what the organization is trying to achieve with spatial data. GIS enables a wide range of use cases, and it’s often tempting to focus on tools or maps before value is clearly defined.

Business analysis professionals help ground the effort by identifying:

  • The decisions or activities that GIS is intended to support
  • Which patterns of GIS use are relevant (e.g., planning, operational monitoring, emergency response, optimization)
  • How spatial insights will create business value

As future states are defined, business analysis professionals also identify which core capabilities will be affected. GIS frequently cuts across boundaries—planning, engineering, operations, customer service—which makes clear problem framing especially important. Subsequent requirements, process models, and solution evaluations all build on this foundational work.

Making Sense of Complex Stakeholder and Data Landscapes

GIS initiatives typically involve a broad and diverse set of stakeholders, each bringing different perspectives and needs. These may include:

  • Field workers and inspectors
  • GIS analysts and developers
  • Planners and engineers
  • Data stewards and database administrators
  • Cartographers and subject matter experts
  • Managers and customer-facing staff

Business analysis professionals often serve as the crucial communication link among these groups. Understanding when and how to engage stakeholders is just as important as understanding what information they provide. For example:

  • Interface users are key sources of business needs and usability feedback
  • Subject matter experts influence solution design, including map layers and representation
  • Data personnel shape feasibility, integration, and data stewardship considerations

Business analysis professionals also help stakeholders navigate the language of GIS. Terms such as buffer, clip, or geocode have specific meanings in spatial contexts. While business analysis professionals don’t need to be authorities on this terminology, familiarity with it makes collaboration smoother and reduces misunderstanding.

Translating Spatial Needs Into Clear Requirements

Defining requirements for GIS solutions introduces some distinctive considerations that business analysis professionals must be prepared for.

On the functional side, requirements often relate to:

  • Map layers, including not only what data is shown but also how it appears visually
  • Data collection, whether spatial data is captured in the field using GPS, drawn directly on maps, or integrated from other systems
  • Map functions, such as querying, buffering, or spatial selection

Many GIS requirements are visual, making prototyping and collaboration with cartographers and users especially important.

Non-functional considerations are equally critical and may include:

  • Data growth and storage, as spatial datasets expand over time
  • Performance and network load, influenced by data size and map services
  • Wireless coverage, particularly for solutions used by field personnel
  • Coordinate systems, which affect how spatial data is captured, integrated, and interpreted

Business analysis professionals play a key role in ensuring these requirements are documented clearly and aligned with real-world use, rather than treated as purely technical concerns.

Ensuring Solutions Work Where and How They’re Used

Evaluating GIS solutions often requires practitioners to think beyond traditional desktop testing. Many GIS applications are designed for use in the field, under conditions where connectivity may be limited or unreliable.

As a result, effective evaluation may involve:

  • Verifying spatial outputs against known geography
  • Testing workflows in the environments where users actually work
  • Confirming that offline or degraded modes behave as expected

Familiarity with GIS terminology and spatial concepts becomes particularly important during testing, especially when business analysis professionals are responsible for defining test cases or acceptance criteria. In some cases, there’s no substitute for going into the field to validate that a solution truly supports the intended business outcomes.

Why GIS Matters for Business Analysis

GIS is best understood not just as a technology, but as a discipline with unique patterns of use, terminology, and stakeholder complexity. These characteristics have direct implications for business analysis work.

Business analysis professionals who engage with GIS do what they do best: clarify value, navigate complexity, translate needs into requirements, and ensure solutions deliver meaningful outcomes. While there’s a lot to learn, professionals don’t need to master GIS itself to be effective. A solid foundation in business analysis, combined with curiosity about spatial data and its uses, goes a long way.

GIS also highlights something broader about the evolving role of business analysis. As enabling technologies such as cybersecurity tools and AI become more prominent, there’s growing anxiety that practitioners must become deeply technical to remain relevant. In reality, these technologies only succeed when business analysis focuses on how they’re used to support decisions, operations, and outcomes. 

Business analysis professionals serve as sense makers, helping organizations apply powerful technologies appropriately and effectively, and GIS offers a clear example of why that role is more important than ever.

GIS is one example of how business analysis applies across complex and specialized domains. IIBA offers resources, community, and certifications to support you as you continue to grow your practice and apply your skills in different contexts.



About the Author
Raghavendra Shet.jpg

Darren Sutton is a Management Consultant based in Edmonton, Alberta, with a deep background in GIS. Over the past twenty years, he has worked at the intersection of GIS and business analysis in telecommunications, utilities, oil, and gas, and IT services. He has also volunteered his knowledge, serving as a board member with IIBA Edmonton and helping to deliver several webinars.

Must Read Blogs From IIBA

How to Elicit Requirements When Stakeholders Can’t Define What They Want

Eliciting the requirements when the stakeholders won’t tell you what they want—if this is so easy, why isn’t everyone doing it? 

Read the Blog

When Fixing the Problem Isn’t the Problem: A Case for Problem Framing

When a data discrepancy landed on my desk, the obvious move was to fix the number. What I found instead was a lesson every business analyst eventually learns: sometimes the most valuable thing you can do is question whether the problem is worth solving at all.

Read the Blog

The 7 Deadly Sins of Business Analysis (and What to Do Instead)

In this article, Heather Mylan-Mains explores seven common but preventable mistakes that business analysts make—and the practical habits that address them. From unclear problem definition and poor listening to missing context, skipped process analysis, and analysis paralysis, these “deadly sins” reveal patterns that can quietly undermine projects.

Read the Blog