fbpx

CategoryBlog

Outside Context Problem

Ian Banks defined an Outside Context Problem as “a problem that hits you not only because no one saw it coming, but because it was so far outside your context that no one could have possibly predicted it.” In business, we see this all the time, we call it a “disruption”. Disruptions are the primary business model for aggressive tech-focused startups. They hit organisations hard because they just can’t see it coming. Not that they don’t see it coming, but they can’t.

Over the last few posts we have been looking at how to set up and fund business technology teams – teams that are directly linked to business functions and provide the technology component of the business as an integral part of the business rather than something provided by a separate IT group. These teams are funded by the business on an ongoing basis in order to deliver business outcomes.

Ditch IT

While the idea of an IT department feels quite modern, the actual idea is pretty old. In the 60s and 70s, these systems were big and complex. Fast-forward 30 years and things are different.

We still talk about “business” and “IT” but that’s no longer really the case. Everything you do in your business relies on IT to happen. IT no longer supports your business. IT is your business.

Lean-Agile Leadership at all levels is about empowering those doing the work

Leadership had to take the wheel immediately.  Working with SAFe Program Consultants (SPCs), a pragmatic curriculum of agile classes were implemented. Over the course of a fiscal quarter, everyone could have productive conversations, plan together and prioritise accordingly to the needs of the enterprise goals and market opportunities. One Product Owner even used her budget to fly dev team members into the PI Planning from across the continent!