Monday morning GIS: why the workshop is not the capability

A good GIS workshop can make everything look easy. The trainer has the right software, the example data is clean, the projector works and somebody has already solved every problem the participants are about to encounter. For a few hours the whole thing feels manageable. Then Monday morning arrives and the participant opens their own computer to discover a different version of the software, messy data, missing permissions, six spellings of the same place and an organisation already asking when the finished map will be ready.

That gap between a successful workshop and useful capability has shaped a great deal of the Māori GIS work I have been involved with. Over time it also changed how I thought about what a wānanga was for. The aim was not simply to transfer a set of technical instructions from the expert to the participant. It was to create enough understanding, confidence and connection that people could carry the mahi forward themselves.

The obvious way to measure training is attendance. Forty people came, ninety people registered, the room was full and the feedback was positive. Those things matter, but they do not tell you what happened later. The better question is what someone could actually do after the event that they could not do before it, and whether they had more control over their own work when they returned home.

This became increasingly obvious through Māori GIS conferences, Managing Māori GIS Projects workshops, geospatial outreach sessions and the Indigenous Mapping Wānanga. Participants often understood the demonstration while the trainer was present. The difficulty came when they tried to apply it to their own project, with their own data, their own organisational constraints and their own responsibilities to the people whose information they were working with.

Real projects are untidy. The names are inconsistent. The source information is incomplete. The geometry does not line up. The laptop is old. Nobody knows whether the layer is allowed to be published. The person doing the GIS also has several other jobs. In Māori settings there may be another layer of questions that a generic software course does not prepare people for: whose authority does the information carry, what can be shared, what should remain local and how do you represent whenua without treating it as nothing more than geometry?

Training therefore has to do more than teach a sequence of clicks. People need enough understanding to diagnose what is happening when the sequence does not work. They need to know where data comes from, how to organise files, what can be shared, what needs further approval and where to go for help. They also need confidence to question the official layer, the software, the trainer and sometimes the assumption that everything useful has to end up on a public map.

That last part is important. The strongest Māori GIS learning I have been involved with has usually contained an element of ako. I may have arrived with technical experience, but participants brought knowledge of their own whenua, histories, organisations and kaupapa that I did not have. The session became more useful when the learning moved in both directions. Someone could correct my assumption, explain why a proposed workflow would not fit local practice or point out that the neat technical solution created a governance problem.

Being corrected is therefore one of the better signs that a workshop is working. It means the relationship is no longer simply expert and recipient. People are becoming confident enough to interrogate the method and adapt it to their own circumstances.

Manaakitanga matters as well, although it is easy to overlook in a technical programme. People need to feel able to ask the question they think might be basic. They need room to arrive with different levels of experience. A participant who has never opened QGIS should not be made to feel that the room belongs more to the person who has used it for ten years. The practical hosting of a wānanga, the tone, support and willingness to stay with a problem all affect whether learning can happen.

This was one reason the work increasingly moved away from one-off presentations toward practical follow-up. In 2013 a geospatial outreach workshop in Wellington drew a waiting list. The demand was not simply for another presentation about what mapping could theoretically do. People wanted hands-on access to tools and support. The Indigenous Mapping Wānanga developed that further by allowing participants to bring real projects and questions rather than requiring everyone to work through the same abstract example.

Ngā Poutama Matawhenua later made regularity part of the model. Instead of expecting people to remember everything from one event, sessions could happen over time. Someone could learn StoryMaps in one session, return later with a QGIS question and join another session about environmental data or local information management. Capability could grow in pieces, more like moving along poutama than completing one course and being declared trained.

That model also respects the fact that not everyone needs to become a professional GIS specialist. A person involved in freshwater monitoring may need enough GIS to collect observations, view catchments and communicate change. Someone working with historic imagery may need to georeference photographs and compare landscapes over time. A hapū may need enough capability to maintain local layers, decide what is public and produce maps when required. Different kaupapa need different levels and forms of capability.

The objective is not to turn everybody into the GIS department. It is to reduce unnecessary dependence and strengthen people's ability to make informed decisions about their own work.

That is where rangatiratanga enters the capability discussion for me. A person who can operate the software but cannot move their data, decide what should be public or challenge an inappropriate platform has only part of the capability. Technical skills are important, but so is the confidence and authority to choose how the technology will be used.

The best sign of progress is often a change in the questions people ask. At first it may be, “Which button do I press?” Later it becomes, “Can I connect to this dataset as a service instead of downloading a copy?” Then, “Who maintains this layer?”, “What authority does this boundary have?” or “Should this information be public?” Those later questions show that the person is no longer simply following instructions. They are making decisions about the work.

Support after the workshop matters because that confidence develops through use. A simple place to ask questions can be more useful than another hundred-page manual. Practitioner networks, online groups, follow-up sessions and recorded examples all help bridge the gap between the controlled training exercise and the untidy real project. They also strengthen whanaungatanga across a practitioner community, so the person with a problem does not have to begin from scratch or solve everything alone.

The workshop is still important. It can create confidence, introduce new possibilities and bring people together. But the workshop is not the capability. Capability is what survives after the projector is turned off, everyone goes home and Monday morning arrives. It is the knowledge people can apply, the relationships they can draw on, the judgement to know when not to map something and the ability to continue the mahi under their own authority.

For the longer history of this shift, see After the mapper leaves and From conferences to wānanga.