[kiloreven]

This was not what I expected when I started reading, but an interesting article nonetheless!

My first reaction is that the article is focusing on a rather specific (while generic) way of conceptualizing knowledge and skills, which are at best fuzzy attributes to start with. However, I don't feel that the specific framework and examples (including IAM roles) can be adopted well as-is; there's a lot of assumptions to the team and org structure surrounding this, along with processes leading up to defining the roles, which I fear can easily lead to cargo-culting.

My takeaway from the article is that it could act as input for teams to better understand their needs and roles, but to not act as a direct blueprint to be implemented :)