The Go-Bag and Capability-Bag Concept

First, what is a Go-Bag. The purpose of a Go-Bag (or Go-Ruck) is that when the shit hits the fan, you can grab this bag and pretty much have what you need - we are talking bare essentials only - to get the hell out of the area. This is similar to what a GHB, however it's geared toward being either on 1) a non-permissive environment or 2) when an emergency hits and you have no time to go home and get what you need.

A Capability-Bag, on the other hand, contains items that would be unavailable or hard to acquire on-site (usually on less than permissive locations). This bag would be waiting for us when we arrived and would serve also as a minimal Go-Bag.

These two bags provide a glimpse into the adaptability and readiness of small teams. Things don't always go as planned, in fact they rarely do. Having an escape plan is always a good thing. Having a virtual go-bag can provide a good cushion when the project doesn't go as planned or there is a sudden change of direction.
Think about it this way: if you have a disaster recovery plan on your company (network, backups, code redundancy, etc or off-side backups, remote offices, alternate servers, etc), or if you have a secondary set of project guidelines or requirements that were drafted just in case the first one doesn't work or need to be changed (think flexible second set, think bare minimum set that can be adapted to the changed that need to be made) then when the shit hits the fan your team can look at this and escape to a safer place.

The same with the Capability-Bag. If you provide your team with the right set of tools (virtual or physical) in order for them to be effective from the get go, they can start performing at their maximum from the beginning. And having the right tools will also allow for better adaptability if something goes wrong. This usually means also that the team members have to be able to create, write, purchase or otherwise built their own tools too. Everyone can benefit from this.

PACE applies here too:


Note: Originally posted on Small Team Tactics