When we think about improving effectiveness we often focus on team level. The sources of ineffectiveness, however, are often rooted on a different level - in project portfolio. Too many concurrent projects, little knowledge about available capabilities and lack of discussion on cost and value often result in a situation where main decision factor is a gut feeling.
Common approaches to solve the problem are heavy-weight and strongly formalized. On the other hand Portfolio Kanban is a low-friction method that allows tackling the issue steering change at PMO level. As with every Kanban implementation there is little, if any, changes at the very beginning and changes are steered in evolutionary manner.
The picture isn’t rosy though. As long as you can say that there are standard approaches to introducing Kanban on a team level, there are no for portfolio level. As long as the method itself is easy to operate, its implementation is going to be anything but obvious and simple.