I recently wrote an article about why Product Management isn’t embraced everywhere1. In it, I referred to product people as ‘unicorn’ people. Advertising an internal…
Most organisations acknowledge that change is a strategic imperative to stay ahead of new technological and economic developments. As businesses around the world have struggled to navigate pandemic-induced uncertainty and shifting consumer behaviour, it’s understandable why many have pursued organisational transformation in the hope that it’ll enable the business to operate at a higher level—to become more agile, productive, innovative and profitable.
If you work in or with a team or teams who build things, read on. In my experience as a product manager, consultant, and leader, these are five tried and tested tips for amplifying product management adoption. For those of you who read my previous blog and are wondering how to get product management into your organisation, consider the following “guerilla tactics” that might help lead the charge.
As a former product manager, management consultant, agilist, and self-confessed questioner of all things, I sometimes catch myself thinking about big, hairy questions scraped straight from the very bottom of the “too hard” basket. On sensible days, I catch these thoughts, acknowledge their existence, and move swiftly on to the next shiny thing in my vicinity. On less-than-sensible days, I latch onto them — give them attention, time, space, and explore them.
During Covid-19, the need to focus on safe transport accelerated. Transport for NSW saw residents looking for safer transport alternatives, increasingly turning to walking and cycling to move around—and the Active Transport branch was born. Headed up by the Director of Active Transport Portfolio, Data & Analytics at Transport for NSW, Active Transport faced a thrilling challenge—to meet the unprecedented demand for active movement, with infrastructure requirements to match.
Elabor8 was honoured to host Dr. Stephen Mayner in this month’s webinar where he presented key industry insights for ‘Applying the SAFe Dual Operating System to Enable Agility in Government’. In this blog, we revisit some of the highlights. Today, let us revisit some of the highlights in this article.
Whether you are just emerging from traditional project methods, in the throes of an ongoing Scaled Agile Transformation, or just getting settled into your Scaled Agile Framework for Enterprise Transformation, businesses, operations, and technology leaders need to be laser-focused on understanding how to measure predictability in terms of the flow of value through the system.
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.
The inability to effectively fund long lived business technology teams is often the single biggest impediment to making a change within a business. In this blog, David Martin explains how you can move away from a project-based funding model and move into a value stream based funding model – a major rethinking of how funding works with huge benefits.
Having the whole organisation trained in lean/agile ways of working is important because it provides a tangible roadmap for leading organisational change. It bridges the gaps between functional silos with a common organisational language, basic shared skills and common knowledge of the concepts and an understanding of the ‘why’.